Jul 31 15:15:39 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8372" x-info="http://www.rsyslog.com"] start
Jul 31 15:15:39 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 31 15:15:39 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 31 15:15:39 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 31 15:15:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 31 15:15:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 31 15:15:39 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 31 15:15:39 node-2 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 31 15:15:39 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=fe0d3e4f-03b6-453d-86c1-1ef15305bfcf nomdmonddf nomdmonisw
Jul 31 15:15:39 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 31 15:15:39 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 31 15:15:39 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 31 15:15:39 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 31 15:15:39 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 31 15:15:39 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 31 15:15:39 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 31 15:15:39 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 31 15:15:39 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 31 15:15:39 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 31 15:15:39 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 31 15:15:39 node-2 kernel: [    0.000000] No AGP bridge found
Jul 31 15:15:39 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 31 15:15:39 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 31 15:15:39 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 31 15:15:39 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 31 15:15:39 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 31 15:15:39 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 31 15:15:39 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 31 15:15:39 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 31 15:15:39 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 31 15:15:39 node-2 kernel: [    0.000000]   2 disabled
Jul 31 15:15:39 node-2 kernel: [    0.000000]   3 disabled
Jul 31 15:15:39 node-2 kernel: [    0.000000]   4 disabled
Jul 31 15:15:39 node-2 kernel: [    0.000000]   5 disabled
Jul 31 15:15:39 node-2 kernel: [    0.000000]   6 disabled
Jul 31 15:15:39 node-2 kernel: [    0.000000]   7 disabled
Jul 31 15:15:39 node-2 kernel: [    0.000000]   8 disabled
Jul 31 15:15:39 node-2 kernel: [    0.000000]   9 disabled
Jul 31 15:15:39 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 31 15:15:39 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 31 15:15:39 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 31 15:15:39 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 31 15:15:39 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 31 15:15:39 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 31 15:15:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 31 15:15:39 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 31 15:15:39 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 31 15:15:39 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 31 15:15:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 31 15:15:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 31 15:15:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 31 15:15:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 31 15:15:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 31 15:15:39 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 31 15:15:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 31 15:15:39 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 31 15:15:39 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 31 15:15:39 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 31 15:15:39 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 31 15:15:39 node-2 kernel: [    0.000000] Zone ranges:
Jul 31 15:15:39 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 31 15:15:39 node-2 kernel: [    0.000000] Early memory node ranges
Jul 31 15:15:39 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 31 15:15:39 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 31 15:15:39 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 31 15:15:39 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 31 15:15:39 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 31 15:15:39 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 31 15:15:39 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 31 15:15:39 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 31 15:15:39 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 31 15:15:39 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 31 15:15:39 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 31 15:15:39 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 31 15:15:39 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 31 15:15:39 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 31 15:15:39 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 31 15:15:39 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 31 15:15:39 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 31 15:15:39 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 31 15:15:39 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 31 15:15:39 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 31 15:15:39 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 31 15:15:39 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 31 15:15:39 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 31 15:15:39 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 31 15:15:39 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 31 15:15:39 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 31 15:15:39 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=fe0d3e4f-03b6-453d-86c1-1ef15305bfcf nomdmonddf nomdmonisw
Jul 31 15:15:39 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 31 15:15:39 node-2 kernel: [    0.000000] Checking aperture...
Jul 31 15:15:39 node-2 kernel: [    0.000000] No AGP bridge found
Jul 31 15:15:39 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 31 15:15:39 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 31 15:15:39 node-2 kernel: [    0.000000] Memory: 32653312K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Jul 31 15:15:39 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 31 15:15:39 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 31 15:15:39 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 31 15:15:39 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 31 15:15:39 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 31 15:15:39 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 31 15:15:39 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 31 15:15:39 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 31 15:15:39 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 31 15:15:39 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 31 15:15:39 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 31 15:15:39 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 31 15:15:39 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 31 15:15:39 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 31 15:15:39 node-2 kernel: [    0.004000] tsc: Detected 3492.275 MHz processor
Jul 31 15:15:39 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.55 BogoMIPS (lpj=13969100)
Jul 31 15:15:39 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 31 15:15:39 node-2 kernel: [    0.000043] Security Framework initialized
Jul 31 15:15:39 node-2 kernel: [    0.000063] AppArmor: AppArmor initialized
Jul 31 15:15:39 node-2 kernel: [    0.000064] Yama: becoming mindful.
Jul 31 15:15:39 node-2 kernel: [    0.001464] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.006416] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.008342] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.008370] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.008650] Initializing cgroup subsys memory
Jul 31 15:15:39 node-2 kernel: [    0.008657] Initializing cgroup subsys devices
Jul 31 15:15:39 node-2 kernel: [    0.008659] Initializing cgroup subsys freezer
Jul 31 15:15:39 node-2 kernel: [    0.008661] Initializing cgroup subsys blkio
Jul 31 15:15:39 node-2 kernel: [    0.008663] Initializing cgroup subsys perf_event
Jul 31 15:15:39 node-2 kernel: [    0.008665] Initializing cgroup subsys hugetlb
Jul 31 15:15:39 node-2 kernel: [    0.008685] CPU: Physical Processor ID: 0
Jul 31 15:15:39 node-2 kernel: [    0.008686] CPU: Processor Core ID: 0
Jul 31 15:15:39 node-2 kernel: [    0.008690] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 31 15:15:39 node-2 kernel: [    0.008690] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 31 15:15:39 node-2 kernel: [    0.009383] mce: CPU supports 22 MCE banks
Jul 31 15:15:39 node-2 kernel: [    0.009411] CPU0: Thermal monitoring enabled (TM1)
Jul 31 15:15:39 node-2 kernel: [    0.009431] process: using mwait in idle threads
Jul 31 15:15:39 node-2 kernel: [    0.009434] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 31 15:15:39 node-2 kernel: [    0.009434] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 31 15:15:39 node-2 kernel: [    0.009434] tlb_flushall_shift: 6
Jul 31 15:15:39 node-2 kernel: [    0.009523] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 31 15:15:39 node-2 kernel: [    0.010248] ACPI: Core revision 20131115
Jul 31 15:15:39 node-2 kernel: [    0.022916] ACPI: All ACPI Tables successfully acquired
Jul 31 15:15:39 node-2 kernel: [    0.023079] ftrace: allocating 28617 entries in 112 pages
Jul 31 15:15:39 node-2 kernel: [    0.031896] dmar: Host address width 46
Jul 31 15:15:39 node-2 kernel: [    0.031898] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 31 15:15:39 node-2 kernel: [    0.031904] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 31 15:15:39 node-2 kernel: [    0.031906] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 31 15:15:39 node-2 kernel: [    0.031910] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 31 15:15:39 node-2 kernel: [    0.031912] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 31 15:15:39 node-2 kernel: [    0.031913] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 31 15:15:39 node-2 kernel: [    0.031914] dmar: ATSR flags: 0x0
Jul 31 15:15:39 node-2 kernel: [    0.031915] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 31 15:15:39 node-2 kernel: [    0.031916] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 31 15:15:39 node-2 kernel: [    0.032032] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 31 15:15:39 node-2 kernel: [    0.032034] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 31 15:15:39 node-2 kernel: [    0.032035] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 31 15:15:39 node-2 kernel: [    0.032036] HPET id 0 under DRHD base 0xc7ffc000
Jul 31 15:15:39 node-2 kernel: [    0.032037] Your BIOS is broken and requested that x2apic be disabled.
Jul 31 15:15:39 node-2 kernel: [    0.032037] This will slightly decrease performance.
Jul 31 15:15:39 node-2 kernel: [    0.032037] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 31 15:15:39 node-2 kernel: [    0.032468] Enabled IRQ remapping in xapic mode
Jul 31 15:15:39 node-2 kernel: [    0.032470] x2apic not enabled, IRQ remapping is in xapic mode
Jul 31 15:15:39 node-2 kernel: [    0.032473] Switched APIC routing to physical flat.
Jul 31 15:15:39 node-2 kernel: [    0.033093] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 31 15:15:39 node-2 kernel: [    0.072748] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 31 15:15:39 node-2 kernel: [    0.072754] TSC deadline timer enabled
Jul 31 15:15:39 node-2 kernel: [    0.072761] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 31 15:15:39 node-2 kernel: [    0.072767] ... version:                3
Jul 31 15:15:39 node-2 kernel: [    0.072768] ... bit width:              48
Jul 31 15:15:39 node-2 kernel: [    0.072769] ... generic registers:      4
Jul 31 15:15:39 node-2 kernel: [    0.072770] ... value mask:             0000ffffffffffff
Jul 31 15:15:39 node-2 kernel: [    0.072771] ... max period:             0000ffffffffffff
Jul 31 15:15:39 node-2 kernel: [    0.072772] ... fixed-purpose events:   3
Jul 31 15:15:39 node-2 kernel: [    0.072773] ... event mask:             000000070000000f
Jul 31 15:15:39 node-2 kernel: [    0.074196] x86: Booting SMP configuration:
Jul 31 15:15:39 node-2 kernel: [    0.088303] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 31 15:15:39 node-2 kernel: [    0.074198] .... node  #0, CPUs:        #1  #2  #3
Jul 31 15:15:39 node-2 kernel: [    0.116213] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 31 15:15:39 node-2 kernel: [    0.270377] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 31 15:15:39 node-2 kernel: [    0.325996] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 31 15:15:39 node-2 kernel: [    0.382857] x86: Booted up 2 nodes, 16 CPUs
Jul 31 15:15:39 node-2 kernel: [    0.382861] smpboot: Total of 16 processors activated (111764.56 BogoMIPS)
Jul 31 15:15:39 node-2 kernel: [    0.407123] devtmpfs: initialized
Jul 31 15:15:39 node-2 kernel: [    0.410224] EVM: security.selinux
Jul 31 15:15:39 node-2 kernel: [    0.410226] EVM: security.SMACK64
Jul 31 15:15:39 node-2 kernel: [    0.410227] EVM: security.ima
Jul 31 15:15:39 node-2 kernel: [    0.410228] EVM: security.capability
Jul 31 15:15:39 node-2 kernel: [    0.410276] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.410950] pinctrl core: initialized pinctrl subsystem
Jul 31 15:15:39 node-2 kernel: [    0.411009] regulator-dummy: no parameters
Jul 31 15:15:39 node-2 kernel: [    0.411039] RTC time: 15:14:59, date: 07/31/16
Jul 31 15:15:39 node-2 kernel: [    0.411073] NET: Registered protocol family 16
Jul 31 15:15:39 node-2 kernel: [    0.411155] cpuidle: using governor ladder
Jul 31 15:15:39 node-2 kernel: [    0.411157] cpuidle: using governor menu
Jul 31 15:15:39 node-2 kernel: [    0.411191] ACPI: bus type PCI registered
Jul 31 15:15:39 node-2 kernel: [    0.411192] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 31 15:15:39 node-2 kernel: [    0.411240] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 31 15:15:39 node-2 kernel: [    0.411242] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 31 15:15:39 node-2 kernel: [    0.424976] PCI: Using configuration type 1 for base access
Jul 31 15:15:39 node-2 kernel: [    0.425967] bio: create slab <bio-0> at 0
Jul 31 15:15:39 node-2 kernel: [    0.426246] ACPI: Added _OSI(Module Device)
Jul 31 15:15:39 node-2 kernel: [    0.426247] ACPI: Added _OSI(Processor Device)
Jul 31 15:15:39 node-2 kernel: [    0.426249] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 31 15:15:39 node-2 kernel: [    0.426250] ACPI: Added _OSI(Processor Aggregator Device)
Jul 31 15:15:39 node-2 kernel: [    0.438916] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 31 15:15:39 node-2 kernel: [    0.449527] ACPI: Interpreter enabled
Jul 31 15:15:39 node-2 kernel: [    0.449533] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 31 15:15:39 node-2 kernel: [    0.449537] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 31 15:15:39 node-2 kernel: [    0.449539] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 31 15:15:39 node-2 kernel: [    0.449546] ACPI: (supports S0 S4 S5)
Jul 31 15:15:39 node-2 kernel: [    0.449547] ACPI: Using IOAPIC for interrupt routing
Jul 31 15:15:39 node-2 kernel: [    0.449589] HEST: Table parsing has been initialized.
Jul 31 15:15:39 node-2 kernel: [    0.449592] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 31 15:15:39 node-2 kernel: [    0.450145] ACPI: No dock devices found.
Jul 31 15:15:39 node-2 kernel: [    0.461635] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 31 15:15:39 node-2 kernel: [    0.461639] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 15:15:39 node-2 kernel: [    0.461643] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 31 15:15:39 node-2 kernel: [    0.461669] PCI host bridge to bus 0000:ff
Jul 31 15:15:39 node-2 kernel: [    0.461671] pci_bus 0000:ff: root bus resource [bus ff]
Jul 31 15:15:39 node-2 kernel: [    0.461680] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.461717] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.461747] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.461782] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.461811] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.461840] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.461870] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.461898] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.461928] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.461955] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.461982] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462008] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462036] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462062] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462088] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462114] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462143] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462173] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462199] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.462228] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462253] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.462279] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462305] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462335] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.462370] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462401] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462430] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462461] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462492] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462523] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462553] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462583] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462614] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462648] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462680] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462713] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462746] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462777] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462805] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462838] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462872] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462913] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462948] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.462981] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463012] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463041] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463071] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463102] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463135] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463166] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463198] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463227] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463257] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463287] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463316] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463347] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463380] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463437] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 31 15:15:39 node-2 kernel: [    0.463440] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 15:15:39 node-2 kernel: [    0.463443] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 31 15:15:39 node-2 kernel: [    0.463461] PCI host bridge to bus 0000:7f
Jul 31 15:15:39 node-2 kernel: [    0.463462] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 31 15:15:39 node-2 kernel: [    0.463467] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463495] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.463522] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463553] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463574] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.463599] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.463626] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463653] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463677] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463700] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463727] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463751] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463776] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463798] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463822] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463848] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463869] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463892] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463915] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.463938] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.463960] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.463983] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464005] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464031] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 31 15:15:39 node-2 kernel: [    0.464065] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464091] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464118] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464144] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464168] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464197] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464225] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464253] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464280] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464308] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464336] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464364] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464393] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464417] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464442] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464470] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464495] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464521] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464550] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464576] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464603] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464628] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464654] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464680] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464707] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464734] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464763] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464789] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464811] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464837] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464863] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464892] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.464919] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.466164] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 31 15:15:39 node-2 kernel: [    0.466167] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 15:15:39 node-2 kernel: [    0.467288] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 31 15:15:39 node-2 kernel: [    0.467805] PCI host bridge to bus 0000:00
Jul 31 15:15:39 node-2 kernel: [    0.467808] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 31 15:15:39 node-2 kernel: [    0.467809] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 31 15:15:39 node-2 kernel: [    0.467811] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 31 15:15:39 node-2 kernel: [    0.467812] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 31 15:15:39 node-2 kernel: [    0.467813] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 31 15:15:39 node-2 kernel: [    0.467815] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 31 15:15:39 node-2 kernel: [    0.467816] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 31 15:15:39 node-2 kernel: [    0.467822] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 31 15:15:39 node-2 kernel: [    0.467905] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.467936] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.467977] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 31 15:15:39 node-2 kernel: [    0.467997] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.468026] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.468066] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 31 15:15:39 node-2 kernel: [    0.468085] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.468115] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.468160] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 31 15:15:39 node-2 kernel: [    0.468178] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.468249] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.468327] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.468402] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 31 15:15:39 node-2 kernel: [    0.468407] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 31 15:15:39 node-2 kernel: [    0.468490] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 31 15:15:39 node-2 kernel: [    0.468632] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 31 15:15:39 node-2 kernel: [    0.468650] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 31 15:15:39 node-2 kernel: [    0.468727] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.468781] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 31 15:15:39 node-2 kernel: [    0.468803] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.468859] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.468902] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 31 15:15:39 node-2 kernel: [    0.468930] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.468987] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.469029] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 31 15:15:39 node-2 kernel: [    0.469054] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 31 15:15:39 node-2 kernel: [    0.469072] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 31 15:15:39 node-2 kernel: [    0.469150] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.469199] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 31 15:15:39 node-2 kernel: [    0.469224] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 31 15:15:39 node-2 kernel: [    0.469473] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 31 15:15:39 node-2 kernel: [    0.469479] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 31 15:15:39 node-2 kernel: [    0.469484] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.469490] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.469497] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 31 15:15:39 node-2 kernel: [    0.469528] pci 0000:01:00.0: supports D1 D2
Jul 31 15:15:39 node-2 kernel: [    0.479720] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 31 15:15:39 node-2 kernel: [    0.479727] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 31 15:15:39 node-2 kernel: [    0.479731] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 31 15:15:39 node-2 kernel: [    0.479956] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.479989] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 31 15:15:39 node-2 kernel: [    0.491726] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 31 15:15:39 node-2 kernel: [    0.491732] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.491736] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 15:15:39 node-2 kernel: [    0.491820] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.491893] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.492003] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.492075] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 31 15:15:39 node-2 kernel: [    0.492079] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.492080] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 15:15:39 node-2 kernel: [    0.492133] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.492256] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.492310] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 31 15:15:39 node-2 kernel: [    0.492313] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.492315] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 15:15:39 node-2 kernel: [    0.492364] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.492483] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.492522] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.492641] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.492677] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.492797] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.492833] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 31 15:15:39 node-2 kernel: [    0.492968] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 31 15:15:39 node-2 kernel: [    0.493010] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 31 15:15:39 node-2 kernel: [    0.493013] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.493015] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 15:15:39 node-2 kernel: [    0.493075] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 31 15:15:39 node-2 kernel: [    0.493138] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.493190] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.493232] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 31 15:15:39 node-2 kernel: [    0.493314] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 31 15:15:39 node-2 kernel: [    0.493419] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 31 15:15:39 node-2 kernel: [    0.493422] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.493424] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 31 15:15:39 node-2 kernel: [    0.493480] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 31 15:15:39 node-2 kernel: [    0.493533] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.493581] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.493794] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 31 15:15:39 node-2 kernel: [    0.493797] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 31 15:15:39 node-2 kernel: [    0.493860] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 31 15:15:39 node-2 kernel: [    0.493913] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.493988] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.494199] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 31 15:15:39 node-2 kernel: [    0.494202] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 31 15:15:39 node-2 kernel: [    0.494261] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 31 15:15:39 node-2 kernel: [    0.494321] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.494374] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 31 15:15:39 node-2 kernel: [    0.494597] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 31 15:15:39 node-2 kernel: [    0.494601] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 31 15:15:39 node-2 kernel: [    0.494775] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 31 15:15:39 node-2 kernel: [    0.494813] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 31 15:15:39 node-2 kernel: [    0.494889] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 31 15:15:39 node-2 kernel: [    0.494908] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 31 15:15:39 node-2 kernel: [    0.494921] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 31 15:15:39 node-2 kernel: [    0.494934] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 31 15:15:39 node-2 kernel: [    0.494984] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 31 15:15:39 node-2 kernel: [    0.503732] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 31 15:15:39 node-2 kernel: [    0.503741] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 31 15:15:39 node-2 kernel: [    0.503793] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 31 15:15:39 node-2 kernel: [    0.504411] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 31 15:15:39 node-2 kernel: [    0.504414] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 15:15:39 node-2 kernel: [    0.504538] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 31 15:15:39 node-2 kernel: [    0.504646] PCI host bridge to bus 0000:80
Jul 31 15:15:39 node-2 kernel: [    0.504648] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 31 15:15:39 node-2 kernel: [    0.504650] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 31 15:15:39 node-2 kernel: [    0.504651] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 31 15:15:39 node-2 kernel: [    0.504659] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.504722] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.504790] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 31 15:15:39 node-2 kernel: [    0.504853] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 31 15:15:39 node-2 kernel: [    0.504858] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 31 15:15:39 node-2 kernel: [    0.504929] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 31 15:15:39 node-2 kernel: [    0.505229] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 31 15:15:39 node-2 kernel: [    0.505260] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 31 15:15:39 node-2 kernel: [    0.505290] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 31 15:15:39 node-2 kernel: [    0.505319] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 31 15:15:39 node-2 kernel: [    0.505348] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 15:15:39 node-2 kernel: [    0.505377] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 15:15:39 node-2 kernel: [    0.505407] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 15:15:39 node-2 kernel: [    0.505436] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 15:15:39 node-2 kernel: [    0.505522] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 31 15:15:39 node-2 kernel: [    0.505527] ACPI: \_SB_.UNC1: notify handler is installed
Jul 31 15:15:39 node-2 kernel: [    0.505528] ACPI: \_SB_.UNC0: notify handler is installed
Jul 31 15:15:39 node-2 kernel: [    0.505543] ACPI: \_SB_.PCI0: notify handler is installed
Jul 31 15:15:39 node-2 kernel: [    0.505596] ACPI: \_SB_.PCI1: notify handler is installed
Jul 31 15:15:39 node-2 kernel: [    0.505675] Found 4 acpi root devices
Jul 31 15:15:39 node-2 kernel: [    0.505785] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 31 15:15:39 node-2 kernel: [    0.505787] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 31 15:15:39 node-2 kernel: [    0.505789] vgaarb: loaded
Jul 31 15:15:39 node-2 kernel: [    0.505790] vgaarb: bridge control possible 0000:0c:00.0
Jul 31 15:15:39 node-2 kernel: [    0.505908] SCSI subsystem initialized
Jul 31 15:15:39 node-2 kernel: [    0.505971] libata version 3.00 loaded.
Jul 31 15:15:39 node-2 kernel: [    0.505987] ACPI: bus type USB registered
Jul 31 15:15:39 node-2 kernel: [    0.505998] usbcore: registered new interface driver usbfs
Jul 31 15:15:39 node-2 kernel: [    0.506002] usbcore: registered new interface driver hub
Jul 31 15:15:39 node-2 kernel: [    0.506026] usbcore: registered new device driver usb
Jul 31 15:15:39 node-2 kernel: [    0.506195] PCI: Using ACPI for IRQ routing
Jul 31 15:15:39 node-2 kernel: [    0.509816] PCI: pci_cache_line_size set to 64 bytes
Jul 31 15:15:39 node-2 kernel: [    0.510022] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 31 15:15:39 node-2 kernel: [    0.510023] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 31 15:15:39 node-2 kernel: [    0.510024] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 31 15:15:39 node-2 kernel: [    0.510090] NetLabel: Initializing
Jul 31 15:15:39 node-2 kernel: [    0.510091] NetLabel:  domain hash size = 128
Jul 31 15:15:39 node-2 kernel: [    0.510092] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 31 15:15:39 node-2 kernel: [    0.510101] NetLabel:  unlabeled traffic allowed by default
Jul 31 15:15:39 node-2 kernel: [    0.510158] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 31 15:15:39 node-2 kernel: [    0.510162] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 31 15:15:39 node-2 kernel: [    0.512219] Switched to clocksource hpet
Jul 31 15:15:39 node-2 kernel: [    0.516187] AppArmor: AppArmor Filesystem Enabled
Jul 31 15:15:39 node-2 kernel: [    0.516202] pnp: PnP ACPI init
Jul 31 15:15:39 node-2 kernel: [    0.516208] ACPI: bus type PNP registered
Jul 31 15:15:39 node-2 kernel: [    0.516322] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 31 15:15:39 node-2 kernel: [    0.516330] pnp 00:01: [dma 4]
Jul 31 15:15:39 node-2 kernel: [    0.516342] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 31 15:15:39 node-2 kernel: [    0.516368] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 31 15:15:39 node-2 kernel: [    0.516387] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 31 15:15:39 node-2 kernel: [    0.516405] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 31 15:15:39 node-2 kernel: [    0.516438] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 31 15:15:39 node-2 kernel: [    0.516490] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516492] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 31 15:15:39 node-2 kernel: [    0.516494] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516496] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516497] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516501] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516503] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 31 15:15:39 node-2 kernel: [    0.516505] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516506] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516508] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516509] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516511] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516512] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 31 15:15:39 node-2 kernel: [    0.516515] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 31 15:15:39 node-2 kernel: [    0.516599] pnp 00:07: [dma 0 disabled]
Jul 31 15:15:39 node-2 kernel: [    0.516627] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 31 15:15:39 node-2 kernel: [    0.516701] pnp 00:08: [dma 0 disabled]
Jul 31 15:15:39 node-2 kernel: [    0.516732] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 31 15:15:39 node-2 kernel: [    0.516783] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 31 15:15:39 node-2 kernel: [    0.517128] pnp: PnP ACPI: found 10 devices
Jul 31 15:15:39 node-2 kernel: [    0.517130] ACPI: bus type PNP unregistered
Jul 31 15:15:39 node-2 kernel: [    0.523483] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 31 15:15:39 node-2 kernel: [    0.523486] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 31 15:15:39 node-2 kernel: [    0.523489] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 31 15:15:39 node-2 kernel: [    0.523493] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 31 15:15:39 node-2 kernel: [    0.523495] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.523510] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523539] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 31 15:15:39 node-2 kernel: [    0.523553] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523582] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 31 15:15:39 node-2 kernel: [    0.523596] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 31 15:15:39 node-2 kernel: [    0.523625] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 31 15:15:39 node-2 kernel: [    0.523639] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 31 15:15:39 node-2 kernel: [    0.523668] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 31 15:15:39 node-2 kernel: [    0.523670] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.523685] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523717] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 31 15:15:39 node-2 kernel: [    0.523719] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.523733] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523762] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 31 15:15:39 node-2 kernel: [    0.523764] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.523767] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523771] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 31 15:15:39 node-2 kernel: [    0.523772] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.523775] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523779] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 31 15:15:39 node-2 kernel: [    0.523783] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 31 15:15:39 node-2 kernel: [    0.523791] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 31 15:15:39 node-2 kernel: [    0.523795] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 31 15:15:39 node-2 kernel: [    0.523801] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 31 15:15:39 node-2 kernel: [    0.523802] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 31 15:15:39 node-2 kernel: [    0.523803] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 31 15:15:39 node-2 kernel: [    0.523804] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 31 15:15:39 node-2 kernel: [    0.523805] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 31 15:15:39 node-2 kernel: [    0.523806] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 31 15:15:39 node-2 kernel: [    0.523807] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 31 15:15:39 node-2 kernel: [    0.523808] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 31 15:15:39 node-2 kernel: [    0.523808] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.523809] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523810] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.523811] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523812] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.523813] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523814] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.523815] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523816] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 31 15:15:39 node-2 kernel: [    0.523817] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523818] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 31 15:15:39 node-2 kernel: [    0.523819] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 31 15:15:39 node-2 kernel: [    0.523820] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 31 15:15:39 node-2 kernel: [    0.523821] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 31 15:15:39 node-2 kernel: [    0.523823] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 31 15:15:39 node-2 kernel: [    0.523823] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 31 15:15:39 node-2 kernel: [    0.523865] NET: Registered protocol family 2
Jul 31 15:15:39 node-2 kernel: [    0.524124] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.524458] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.524601] TCP: Hash tables configured (established 262144 bind 65536)
Jul 31 15:15:39 node-2 kernel: [    0.524644] TCP: reno registered
Jul 31 15:15:39 node-2 kernel: [    0.524676] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.524769] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.524915] NET: Registered protocol family 1
Jul 31 15:15:39 node-2 kernel: [    0.564326] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 31 15:15:39 node-2 kernel: [    0.564333] PCI: CLS 64 bytes, default 64
Jul 31 15:15:39 node-2 kernel: [    0.564374] Trying to unpack rootfs image as initramfs...
Jul 31 15:15:39 node-2 kernel: [    0.783554] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Jul 31 15:15:39 node-2 kernel: [    0.783585] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 31 15:15:39 node-2 kernel: [    0.783588] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 31 15:15:39 node-2 kernel: [    0.784013] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784019] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784024] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784030] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784055] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784066] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784075] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784084] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784092] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784102] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784108] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784115] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784121] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784129] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784137] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784144] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 15:15:39 node-2 kernel: [    0.784222] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 31 15:15:39 node-2 kernel: [    0.784225] Scanning for low memory corruption every 60 seconds
Jul 31 15:15:39 node-2 kernel: [    0.784599] Initialise system trusted keyring
Jul 31 15:15:39 node-2 kernel: [    0.784651] audit: initializing netlink socket (disabled)
Jul 31 15:15:39 node-2 kernel: [    0.784667] type=2000 audit(1469978098.740:1): initialized
Jul 31 15:15:39 node-2 kernel: [    0.802582] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 31 15:15:39 node-2 kernel: [    0.804124] zbud: loaded
Jul 31 15:15:39 node-2 kernel: [    0.804261] VFS: Disk quotas dquot_6.5.2
Jul 31 15:15:39 node-2 kernel: [    0.804297] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 31 15:15:39 node-2 kernel: [    0.804659] fuse init (API version 7.22)
Jul 31 15:15:39 node-2 kernel: [    0.804723] msgmni has been set to 32768
Jul 31 15:15:39 node-2 kernel: [    0.804774] Key type big_key registered
Jul 31 15:15:39 node-2 kernel: [    0.805317] Key type asymmetric registered
Jul 31 15:15:39 node-2 kernel: [    0.805319] Asymmetric key parser 'x509' registered
Jul 31 15:15:39 node-2 kernel: [    0.805341] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 31 15:15:39 node-2 kernel: [    0.805412] io scheduler noop registered
Jul 31 15:15:39 node-2 kernel: [    0.805414] io scheduler deadline registered (default)
Jul 31 15:15:39 node-2 kernel: [    0.805434] io scheduler cfq registered
Jul 31 15:15:39 node-2 kernel: [    0.805964] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    0.806148] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    0.806265] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    0.806376] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    0.806491] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    0.806589] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    0.806974] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 31 15:15:39 node-2 kernel: [    0.807000] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 31 15:15:39 node-2 kernel: [    0.807017] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 31 15:15:39 node-2 kernel: [    0.807026] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807028] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807031] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 31 15:15:39 node-2 kernel: [    0.807036] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807038] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807040] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807041] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807043] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807045] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807046] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807048] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807049] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807051] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807052] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807054] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807057] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 31 15:15:39 node-2 kernel: [    0.807063] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807065] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 31 15:15:39 node-2 kernel: [    0.807080] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807083] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 31 15:15:39 node-2 kernel: [    0.807095] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807096] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 31 15:15:39 node-2 kernel: [    0.807100] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 31 15:15:39 node-2 kernel: [    0.807138] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 31 15:15:39 node-2 kernel: [    0.807144] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 31 15:15:39 node-2 kernel: [    0.807148] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 31 15:15:39 node-2 kernel: [    0.807157] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 31 15:15:39 node-2 kernel: [    0.807198] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 31 15:15:39 node-2 kernel: [    0.807199] vesafb: scrolling: redraw
Jul 31 15:15:39 node-2 kernel: [    0.807201] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 31 15:15:39 node-2 kernel: [    0.827887] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 31 15:15:39 node-2 kernel: [    0.836420] Console: switching to colour frame buffer device 80x30
Jul 31 15:15:39 node-2 kernel: [    0.845111] fb0: VESA VGA frame buffer device
Jul 31 15:15:39 node-2 kernel: [    0.845317] intel_idle: MWAIT substates: 0x2120
Jul 31 15:15:39 node-2 kernel: [    0.845318] intel_idle: v0.4 model 0x3F
Jul 31 15:15:39 node-2 kernel: [    0.845318] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 31 15:15:39 node-2 kernel: [    0.845547] ipmi message handler version 39.2
Jul 31 15:15:39 node-2 kernel: [    0.845826] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 31 15:15:39 node-2 kernel: [    0.846265] ACPI: AC Adapter [P111] (on-line)
Jul 31 15:15:39 node-2 kernel: [    0.851497] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 31 15:15:39 node-2 kernel: [    0.862570] ACPI: Power Button [PWRB]
Jul 31 15:15:39 node-2 kernel: [    0.868357] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 31 15:15:39 node-2 kernel: [    0.879997] ACPI: Power Button [PWRF]
Jul 31 15:15:39 node-2 kernel: [    0.905761] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 31 15:15:39 node-2 kernel: [    0.917426] pstore: Registered erst as persistent store backend
Jul 31 15:15:39 node-2 kernel: [    0.923650] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 31 15:15:39 node-2 kernel: [    0.935623] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 31 15:15:39 node-2 kernel: [    0.962376] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 31 15:15:39 node-2 kernel: [    0.995739] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 31 15:15:39 node-2 kernel: [    1.010002] Linux agpgart interface v0.103
Jul 31 15:15:39 node-2 kernel: [    1.017721] brd: module loaded
Jul 31 15:15:39 node-2 kernel: [    1.024870] loop: module loaded
Jul 31 15:15:39 node-2 kernel: [    1.031683] libphy: Fixed MDIO Bus: probed
Jul 31 15:15:39 node-2 kernel: [    1.038261] tun: Universal TUN/TAP device driver, 1.6
Jul 31 15:15:39 node-2 kernel: [    1.044808] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 31 15:15:39 node-2 kernel: [    1.051430] PPP generic driver version 2.4.2
Jul 31 15:15:39 node-2 kernel: [    1.057903] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 31 15:15:39 node-2 kernel: [    1.064383] ehci-pci: EHCI PCI platform driver
Jul 31 15:15:39 node-2 kernel: [    1.070970] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 31 15:15:39 node-2 kernel: [    1.077406] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 31 15:15:39 node-2 kernel: [    1.090000] ehci-pci 0000:00:1a.0: debug port 2
Jul 31 15:15:39 node-2 kernel: [    1.100227] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 31 15:15:39 node-2 kernel: [    1.100246] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 31 15:15:39 node-2 kernel: [    1.115734] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 31 15:15:39 node-2 kernel: [    1.121890] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 31 15:15:39 node-2 kernel: [    1.128154] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 15:15:39 node-2 kernel: [    1.140158] usb usb1: Product: EHCI Host Controller
Jul 31 15:15:39 node-2 kernel: [    1.146227] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 31 15:15:39 node-2 kernel: [    1.152257] usb usb1: SerialNumber: 0000:00:1a.0
Jul 31 15:15:39 node-2 kernel: [    1.158234] hub 1-0:1.0: USB hub found
Jul 31 15:15:39 node-2 kernel: [    1.164056] hub 1-0:1.0: 2 ports detected
Jul 31 15:15:39 node-2 kernel: [    1.169856] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 31 15:15:39 node-2 kernel: [    1.175420] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 31 15:15:39 node-2 kernel: [    1.186283] ehci-pci 0000:00:1d.0: debug port 2
Jul 31 15:15:39 node-2 kernel: [    1.195573] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 31 15:15:39 node-2 kernel: [    1.195576] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 31 15:15:39 node-2 kernel: [    1.211655] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 31 15:15:39 node-2 kernel: [    1.216844] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 31 15:15:39 node-2 kernel: [    1.222133] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 15:15:39 node-2 kernel: [    1.232700] usb usb2: Product: EHCI Host Controller
Jul 31 15:15:39 node-2 kernel: [    1.238162] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 31 15:15:39 node-2 kernel: [    1.243702] usb usb2: SerialNumber: 0000:00:1d.0
Jul 31 15:15:39 node-2 kernel: [    1.249222] hub 2-0:1.0: USB hub found
Jul 31 15:15:39 node-2 kernel: [    1.254567] hub 2-0:1.0: 2 ports detected
Jul 31 15:15:39 node-2 kernel: [    1.259867] ehci-platform: EHCI generic platform driver
Jul 31 15:15:39 node-2 kernel: [    1.265084] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 31 15:15:39 node-2 kernel: [    1.270397] ohci-pci: OHCI PCI platform driver
Jul 31 15:15:39 node-2 kernel: [    1.275679] ohci-platform: OHCI generic platform driver
Jul 31 15:15:39 node-2 kernel: [    1.280855] uhci_hcd: USB Universal Host Controller Interface driver
Jul 31 15:15:39 node-2 kernel: [    1.286170] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 31 15:15:39 node-2 kernel: [    1.479433] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 31 15:15:39 node-2 kernel: [    1.779227] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 31 15:15:39 node-2 kernel: [    1.799554] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 31 15:15:39 node-2 kernel: [    1.805139] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 15:15:39 node-2 kernel: [    1.810822] hub 1-1:1.0: USB hub found
Jul 31 15:15:39 node-2 kernel: [    1.816415] hub 1-1:1.0: 6 ports detected
Jul 31 15:15:39 node-2 kernel: [    1.931029] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 31 15:15:39 node-2 kernel: [    2.324982] i8042: No controller found
Jul 31 15:15:39 node-2 kernel: [    2.330508] mousedev: PS/2 mouse device common for all mice
Jul 31 15:15:39 node-2 kernel: [    2.336215] rtc_cmos 00:02: RTC can wake from S4
Jul 31 15:15:39 node-2 kernel: [    2.339550] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 31 15:15:39 node-2 kernel: [    2.339551] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 15:15:39 node-2 kernel: [    2.340319] hub 2-1:1.0: USB hub found
Jul 31 15:15:39 node-2 kernel: [    2.340538] hub 2-1:1.0: 8 ports detected
Jul 31 15:15:39 node-2 kernel: [    2.364475] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 31 15:15:39 node-2 kernel: [    2.370231] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 31 15:15:39 node-2 kernel: [    2.381528] device-mapper: uevent: version 1.0.3
Jul 31 15:15:39 node-2 kernel: [    2.387241] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 31 15:15:39 node-2 kernel: [    2.398615] ledtrig-cpu: registered to indicate activity on CPUs
Jul 31 15:15:39 node-2 kernel: [    2.404593] TCP: cubic registered
Jul 31 15:15:39 node-2 kernel: [    2.410477] NET: Registered protocol family 10
Jul 31 15:15:39 node-2 kernel: [    2.416557] NET: Registered protocol family 17
Jul 31 15:15:39 node-2 kernel: [    2.422349] Key type dns_resolver registered
Jul 31 15:15:39 node-2 kernel: [    2.428414] Loading compiled-in X.509 certificates
Jul 31 15:15:39 node-2 kernel: [    2.434634] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 31 15:15:39 node-2 kernel: [    2.446318] registered taskstats version 1
Jul 31 15:15:39 node-2 kernel: [    2.454505] Key type trusted registered
Jul 31 15:15:39 node-2 kernel: [    2.462719] Key type encrypted registered
Jul 31 15:15:39 node-2 kernel: [    2.468239] AppArmor: AppArmor sha1 policy hashing enabled
Jul 31 15:15:39 node-2 kernel: [    2.473756] IMA: No TPM chip found, activating TPM-bypass!
Jul 31 15:15:39 node-2 kernel: [    2.479856] regulator-dummy: disabling
Jul 31 15:15:39 node-2 kernel: [    2.485383]   Magic number: 8:96:236
Jul 31 15:15:39 node-2 kernel: [    2.491053] memory memory114: hash matches
Jul 31 15:15:39 node-2 kernel: [    2.496563] rtc_cmos 00:02: setting system clock to 2016-07-31 15:15:01 UTC (1469978101)
Jul 31 15:15:39 node-2 kernel: [    2.508922] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 31 15:15:39 node-2 kernel: [    2.514533] EDD information not available.
Jul 31 15:15:39 node-2 kernel: [    2.520074] PM: Hibernation image not present or could not be loaded.
Jul 31 15:15:39 node-2 kernel: [    2.520926] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 31 15:15:39 node-2 kernel: [    2.532228] Write protecting the kernel read-only data: 12288k
Jul 31 15:15:39 node-2 kernel: [    2.538646] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 31 15:15:39 node-2 kernel: [    2.551455] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 31 15:15:39 node-2 kernel: [    2.584330] device-mapper: multipath: version 1.6.0 loaded
Jul 31 15:15:39 node-2 kernel: [    2.592231] systemd-udevd[220]: starting version 204
Jul 31 15:15:39 node-2 kernel: [    2.617309] md: linear personality registered for level -1
Jul 31 15:15:39 node-2 kernel: [    2.618573] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 31 15:15:39 node-2 kernel: [    2.637241] md: multipath personality registered for level -4
Jul 31 15:15:39 node-2 kernel: [    2.645219] md: raid0 personality registered for level 0
Jul 31 15:15:39 node-2 kernel: [    2.653708] md: raid1 personality registered for level 1
Jul 31 15:15:39 node-2 kernel: [    2.661548] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 31 15:15:39 node-2 kernel: [    2.667766] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 31 15:15:39 node-2 kernel: [    2.674100] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 31 15:15:39 node-2 kernel: [    2.674841] megasas: FW now in Ready state
Jul 31 15:15:39 node-2 kernel: [    2.674949] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.674992] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675035] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675086] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675132] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675171] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675217] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675262] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675313] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675359] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675413] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675473] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675515] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675576] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675616] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675666] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.675826] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 31 15:15:39 node-2 kernel: [    2.707840] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 31 15:15:39 node-2 kernel: [    2.721142] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 31 15:15:39 node-2 kernel: [    2.735085] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 15:15:39 node-2 kernel: [    2.738615] raid6: sse2x1    5660 MB/s
Jul 31 15:15:39 node-2 kernel: [    2.749010] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.749015] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.749019] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.749022] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.749061] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 15:15:39 node-2 kernel: [    2.773352] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 31 15:15:39 node-2 kernel: [    2.787199] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 31 15:15:39 node-2 kernel: [    2.801293] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 15:15:39 node-2 kernel: [    2.806548] raid6: sse2x2   12373 MB/s
Jul 31 15:15:39 node-2 kernel: [    2.874233] raid6: sse2x4   10057 MB/s
Jul 31 15:15:39 node-2 kernel: [    2.946172] raid6: avx2x1   14924 MB/s
Jul 31 15:15:39 node-2 kernel: [    3.018113] raid6: avx2x2   18854 MB/s
Jul 31 15:15:39 node-2 kernel: [    3.090051] raid6: avx2x4   21344 MB/s
Jul 31 15:15:39 node-2 kernel: [    3.096299] raid6: using algorithm avx2x4 (21344 MB/s)
Jul 31 15:15:39 node-2 kernel: [    3.102489] raid6: using avx2x2 recovery algorithm
Jul 31 15:15:39 node-2 kernel: [    3.108562] megasas:IOC Init cmd success
Jul 31 15:15:39 node-2 kernel: [    3.108563] Switched to clocksource tsc
Jul 31 15:15:39 node-2 kernel: [    3.108591] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.108608] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.108647] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.108672] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.108754] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.117179] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 31 15:15:39 node-2 kernel: [    3.117180] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 31 15:15:39 node-2 kernel: [    3.117181] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 15:15:39 node-2 kernel: [    3.117236] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.117264] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.117303] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.117341] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.117415] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.130290] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 31 15:15:39 node-2 kernel: [    3.130291] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 31 15:15:39 node-2 kernel: [    3.130292] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 15:15:39 node-2 kernel: [    3.130356] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.130394] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.130429] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.130468] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.130531] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 15:15:39 node-2 kernel: [    3.135838] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 31 15:15:39 node-2 kernel: [    3.135840] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 31 15:15:39 node-2 kernel: [    3.135842] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 31 15:15:39 node-2 kernel: [    3.135844] usb 2-1.4: Manufacturer: Avocent
Jul 31 15:15:39 node-2 kernel: [    3.135845] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 31 15:15:39 node-2 kernel: [    3.254971] hidraw: raw HID events driver (C) Jiri Kosina
Jul 31 15:15:39 node-2 kernel: [    3.261025] xor: automatically using best checksumming function:
Jul 31 15:15:39 node-2 kernel: [    3.268974] usbcore: registered new interface driver usbhid
Jul 31 15:15:39 node-2 kernel: [    3.275258] usbhid: USB HID core driver
Jul 31 15:15:39 node-2 kernel: [    3.281539] megasas: INIT adapter done
Jul 31 15:15:39 node-2 kernel: [    3.288660] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 31 15:15:39 node-2 kernel: [    3.301871] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 31 15:15:39 node-2 kernel: [    3.305842]    avx       : 36723.000 MB/sec
Jul 31 15:15:39 node-2 kernel: [    3.322082] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 31 15:15:39 node-2 kernel: [    3.335506] async_tx: api initialized (async)
Jul 31 15:15:39 node-2 kernel: [    3.335681] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 31 15:15:39 node-2 kernel: [    3.335738] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 31 15:15:39 node-2 kernel: [    3.336034] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 31 15:15:39 node-2 kernel: [    3.369813] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 31 15:15:39 node-2 kernel: [    3.370140] scsi0 : LSI SAS based MegaRAID driver
Jul 31 15:15:39 node-2 kernel: [    3.377204] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 31 15:15:39 node-2 kernel: [    3.388679] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 31 15:15:39 node-2 kernel: [    3.392887] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 31 15:15:39 node-2 kernel: [    3.393224] sd 0:2:0:0: [sda] Write Protect is off
Jul 31 15:15:39 node-2 kernel: [    3.393225] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 31 15:15:39 node-2 kernel: [    3.393232] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 31 15:15:39 node-2 kernel: [    3.393398] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 31 15:15:39 node-2 kernel: [    3.417085]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 31 15:15:39 node-2 kernel: [    3.418354] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 31 15:15:39 node-2 kernel: [    3.484649] md: raid6 personality registered for level 6
Jul 31 15:15:39 node-2 kernel: [    3.491857] md: raid5 personality registered for level 5
Jul 31 15:15:39 node-2 kernel: [    3.498849] md: raid4 personality registered for level 4
Jul 31 15:15:39 node-2 kernel: [    3.508651] md: raid10 personality registered for level 10
Jul 31 15:15:39 node-2 kernel: [    3.563192] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Jul 31 15:15:39 node-2 kernel: [    3.616355] random: lvm urandom read with 31 bits of entropy available
Jul 31 15:15:39 node-2 kernel: [    3.728786] bio: create slab <bio-1> at 1
Jul 31 15:15:39 node-2 kernel: [    4.470017] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 15:15:39 node-2 kernel: [    5.151128] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 31 15:15:39 node-2 kernel: [    5.193156] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 31 15:15:39 node-2 kernel: [    5.328500] random: nonblocking pool is initialized
Jul 31 15:15:39 node-2 kernel: [    5.400551] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 31 15:15:39 node-2 kernel: [    5.430536] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 31 15:15:39 node-2 kernel: [    5.530617] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 15:15:39 node-2 kernel: [    5.690002] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 31 15:15:39 node-2 kernel: [    5.718341] XFS (dm-0): Mounting Filesystem
Jul 31 15:15:39 node-2 kernel: [    5.976101] XFS (dm-0): Ending clean mount
Jul 31 15:15:39 node-2 kernel: [    6.073500] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 15:15:39 node-2 kernel: [    6.104276] XFS (dm-1): Mounting Filesystem
Jul 31 15:15:39 node-2 kernel: [    6.215031] XFS (dm-1): Ending clean mount
Jul 31 15:15:39 node-2 kernel: [    7.924335] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 31 15:15:39 node-2 kernel: [    7.950552] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 31 15:15:39 node-2 kernel: [    8.106029] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 31 15:15:39 node-2 kernel: [    8.106035] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 31 15:15:39 node-2 kernel: [    8.106040] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 31 15:15:39 node-2 kernel: [    8.106043] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 31 15:15:39 node-2 kernel: [    8.137067] systemd-udevd[775]: starting version 204
Jul 31 15:15:39 node-2 kernel: [    8.354183] power_meter ACPI000D:00: Found ACPI power meter.
Jul 31 15:15:39 node-2 kernel: [    8.354239] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 31 15:15:39 node-2 kernel: [    8.373375] IPMI System Interface driver.
Jul 31 15:15:39 node-2 kernel: [    8.373447] ipmi_si: probing via ACPI
Jul 31 15:15:39 node-2 kernel: [    8.373465] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 31 15:15:39 node-2 kernel: [    8.373466] ipmi_si: Adding ACPI-specified kcs state machine
Jul 31 15:15:39 node-2 kernel: [    8.373484] ipmi_si: probing via SMBIOS
Jul 31 15:15:39 node-2 kernel: [    8.373485] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 31 15:15:39 node-2 kernel: [    8.373486] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 31 15:15:39 node-2 kernel: [    8.373487] ipmi_si: probing via SPMI
Jul 31 15:15:39 node-2 kernel: [    8.373488] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 31 15:15:39 node-2 kernel: [    8.373489] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 31 15:15:39 node-2 kernel: [    8.373490] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 31 15:15:39 node-2 kernel: [    8.377238] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 31 15:15:39 node-2 kernel: [    8.377243] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 31 15:15:39 node-2 kernel: [    8.377246] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 31 15:15:39 node-2 kernel: [    8.377249] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 31 15:15:39 node-2 kernel: [    8.377300] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 31 15:15:39 node-2 kernel: [    8.379500] wmi: Mapper loaded
Jul 31 15:15:39 node-2 kernel: [    8.387208] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 31 15:15:39 node-2 kernel: [    8.453980] systemd-udevd[820]: renamed network interface eth2 to enp8s0
Jul 31 15:15:39 node-2 kernel: [    8.486477] systemd-udevd[822]: renamed network interface eth0 to enp6s0
Jul 31 15:15:39 node-2 kernel: [    8.509848] systemd-udevd[829]: renamed network interface eth1 to enp7s0
Jul 31 15:15:39 node-2 kernel: [    8.537788] systemd-udevd[793]: renamed network interface eth3 to enp9s0
Jul 31 15:15:39 node-2 kernel: [    8.567494] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 31 15:15:39 node-2 kernel: [    8.567500] ipmi_si 00:09: IPMI kcs interface initialized
Jul 31 15:15:39 node-2 kernel: [    8.790636] type=1400 audit(1469978107.794:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1058 comm="apparmor_parser"
Jul 31 15:15:39 node-2 kernel: [    8.790784] type=1400 audit(1469978107.794:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1058 comm="apparmor_parser"
Jul 31 15:15:39 node-2 kernel: [    8.790913] type=1400 audit(1469978107.794:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1058 comm="apparmor_parser"
Jul 31 15:15:39 node-2 kernel: [    8.793973] type=1400 audit(1469978107.798:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1054 comm="apparmor_parser"
Jul 31 15:15:39 node-2 kernel: [    8.794112] type=1400 audit(1469978107.798:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1054 comm="apparmor_parser"
Jul 31 15:15:39 node-2 kernel: [    8.794235] type=1400 audit(1469978107.798:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1054 comm="apparmor_parser"
Jul 31 15:15:39 node-2 kernel: [    8.813884] type=1400 audit(1469978107.818:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1057 comm="apparmor_parser"
Jul 31 15:15:39 node-2 kernel: [    8.814033] type=1400 audit(1469978107.818:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1057 comm="apparmor_parser"
Jul 31 15:15:39 node-2 kernel: [    8.814150] type=1400 audit(1469978107.818:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1057 comm="apparmor_parser"
Jul 31 15:15:39 node-2 kernel: [    8.824304] type=1400 audit(1469978107.826:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1056 comm="apparmor_parser"
Jul 31 15:15:39 node-2 kernel: [    9.270584] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 31 15:15:39 node-2 kernel: [    9.271314] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 31 15:15:39 node-2 kernel: [    9.461725] enic 0000:06:00.0 enp6s0: Link UP
Jul 31 15:15:39 node-2 kernel: [    9.462252] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 31 15:15:39 node-2 kernel: [    9.462258] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 31 15:15:39 node-2 kernel: [   18.755111] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 31 15:15:39 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 31 15:15:40 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 31 15:15:40 node-2 kernel: [   41.855241] init: failsafe main process (8399) killed by TERM signal
Jul 31 15:15:40 node-2 dbus[8431]: [system] AppArmor D-Bus mediation is enabled
Jul 31 15:15:41 node-2 kernel: [   42.168274] audit_printk_skb: 30 callbacks suppressed
Jul 31 15:15:41 node-2 kernel: [   42.168276] type=1400 audit(1469978141.112:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8524 comm="apparmor_parser"
Jul 31 15:15:41 node-2 kernel: [   42.168281] type=1400 audit(1469978141.112:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8524 comm="apparmor_parser"
Jul 31 15:15:41 node-2 kernel: [   42.168284] type=1400 audit(1469978141.112:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8524 comm="apparmor_parser"
Jul 31 15:15:41 node-2 kernel: [   42.168529] type=1400 audit(1469978141.112:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8524 comm="apparmor_parser"
Jul 31 15:15:41 node-2 kernel: [   42.168533] type=1400 audit(1469978141.116:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8524 comm="apparmor_parser"
Jul 31 15:15:41 node-2 kernel: [   42.168651] type=1400 audit(1469978141.116:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8524 comm="apparmor_parser"
Jul 31 15:15:41 node-2 kernel: [   42.173240] type=1400 audit(1469978141.120:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8525 comm="apparmor_parser"
Jul 31 15:15:41 node-2 kernel: [   42.237501] type=1400 audit(1469978141.184:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8527 comm="apparmor_parser"
Jul 31 15:15:41 node-2 anacron[8591]: Anacron 2.3 started on 2016-07-31
Jul 31 15:15:41 node-2 cron[8557]: (CRON) INFO (pidfile fd = 3)
Jul 31 15:15:41 node-2 cron[8593]: (CRON) STARTUP (fork ok)
Jul 31 15:15:41 node-2 anacron[8591]: Will run job `cron.daily' in 5 min.
Jul 31 15:15:41 node-2 anacron[8591]: Will run job `cron.weekly' in 10 min.
Jul 31 15:15:41 node-2 anacron[8591]: Will run job `cron.monthly' in 15 min.
Jul 31 15:15:41 node-2 anacron[8591]: Jobs will be executed sequentially
Jul 31 15:15:41 node-2 cron[8593]: (CRON) INFO (Running @reboot jobs)
Jul 31 15:15:41 node-2 multipathd: path checkers start up
Jul 31 15:15:41 node-2 postfix/master[8736]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 31 15:15:44 node-2 puppet-agent[9050]: Reopening log files
Jul 31 15:15:45 node-2 puppet-agent[9050]: Could not request certificate: Connection refused - connect(2)
Jul 31 15:15:55 node-2 puppet-user[9129]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 31 15:15:55 node-2 puppet-user[9129]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 31 15:15:55 node-2 puppet-user[9129]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 31 15:15:55 node-2 puppet-user[9129]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 31 15:15:55 node-2 puppet-user[9129]: Finished catalog run in 0.74 seconds
Jul 31 15:15:57 node-2 multipathd: uevent trigger error
Jul 31 15:15:57 node-2 puppet-user[9544]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 31 15:15:57 node-2 puppet-user[9544]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Jul 31 15:15:57 node-2 puppet-user[9544]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 31 15:15:57 node-2 puppet-user[9544]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 31 15:15:57 node-2 puppet-user[9544]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 31 15:15:57 node-2 puppet-user[9544]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 31 15:15:57 node-2 puppet-user[9544]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 31 15:15:57 node-2 puppet-user[9544]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 31 15:15:57 node-2 puppet-user[9544]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 31 15:15:57 node-2 puppet-user[9544]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 31 15:15:57 node-2 puppet-user[9544]: Finished catalog run in 0.05 seconds
Jul 31 15:15:58 node-2 puppet-user[10181]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 31 15:15:58 node-2 puppet-user[10181]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 31 15:15:58 node-2 puppet-user[10181]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 31 15:15:58 node-2 puppet-user[10181]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 31 15:15:58 node-2 puppet-user[10181]: Finished catalog run in 0.03 seconds
Jul 31 15:16:00 node-2 puppet-user[10634]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 31 15:16:00 node-2 puppet-user[10634]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 31 15:16:00 node-2 puppet-user[10634]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 31 15:16:00 node-2 puppet-user[10634]: Finished catalog run in 0.05 seconds
Jul 31 15:16:01 node-2 CRON[11275]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 31 15:16:01 node-2 puppet-user[11072]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 31 15:16:01 node-2 puppet-user[11072]: Compiled catalog for node-2.domain.tld in environment production in 0.16 seconds
Jul 31 15:16:01 node-2 puppet-user[11072]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 31 15:16:02 node-2 puppet-user[11072]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 31 15:16:02 node-2 puppet-user[11072]: Finished catalog run in 0.43 seconds
Jul 31 15:16:03 node-2 puppet-user[11557]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 31 15:16:03 node-2 puppet-user[11557]: Compiled catalog for node-2.domain.tld in environment production in 0.19 seconds
Jul 31 15:16:03 node-2 puppet-user[11557]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 31 15:16:03 node-2 puppet-user[11557]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 31 15:16:03 node-2 puppet-user[11557]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 31 15:16:04 node-2 puppet-user[11557]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 31 15:16:04 node-2 puppet-user[11557]: Finished catalog run in 0.22 seconds
Jul 31 15:16:04 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 15:16:04 node-2 nailgun-agent: D, [2016-07-31T15:16:01.563722 #11278] DEBUG -- : Sleep for 3 seconds before sending request
Jul 31 15:16:04 node-2 nailgun-agent: I, [2016-07-31T15:16:04.578349 #11278]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 31 15:16:05 node-2 nailgun-agent: D, [2016-07-31T15:16:05.068162 #11278] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 31 15:16:05 node-2 puppet-user[12025]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 31 15:16:05 node-2 puppet-user[12025]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Jul 31 15:16:05 node-2 puppet-user[12025]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 31 15:16:05 node-2 kernel: [   66.875796] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 31 15:16:05 node-2 kernel: [   66.875847] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 31 15:16:05 node-2 puppet-user[12025]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 31 15:16:05 node-2 puppet-user[12025]: Finished catalog run in 0.05 seconds
Jul 31 15:16:07 node-2 puppet-user[12621]: (Scope(Class[main])) MODULAR: sync_time
Jul 31 15:16:07 node-2 puppet-user[12621]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 31 15:16:07 node-2 ntpdate[13032]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 31 15:16:09 node-2 kernel: [   70.393134] init: plymouth-upstart-bridge main process ended, respawning
Jul 31 15:16:09 node-2 puppet-agent[9050]: Could not run: SIGTERM
Jul 31 15:16:09 node-2 kernel: [   70.643182] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 31 15:16:09 node-2 ec2: 
Jul 31 15:16:09 node-2 ec2: #############################################################
Jul 31 15:16:09 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 31 15:16:09 node-2 ec2: 1024 71:cc:41:de:a0:d3:05:4d:ad:a0:93:cc:55:26:b7:51  root@node-2.domain.tld (DSA)
Jul 31 15:16:09 node-2 ec2: 256 e8:8e:c5:de:d5:9c:9f:c5:d4:bf:69:b6:50:0c:ae:5a  root@node-2.domain.tld (ECDSA)
Jul 31 15:16:09 node-2 ec2: 256 ab:74:04:7c:70:51:7c:86:17:fe:0e:46:90:09:09:08  root@node-2.domain.tld (ED25519)
Jul 31 15:16:09 node-2 ec2: 2048 1d:6f:dd:6e:87:8c:b7:4b:54:56:b1:f0:f5:28:34:83  root@node-2.domain.tld (RSA)
Jul 31 15:16:09 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 31 15:16:09 node-2 ec2: #############################################################
Jul 31 15:16:13 node-2 ntpdate[13032]: adjust time server 10.20.0.2 offset 0.000384 sec
Jul 31 15:16:13 node-2 puppet-user[12621]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 31 15:16:13 node-2 puppet-user[12621]: Finished catalog run in 6.21 seconds
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.313149 #11278] DEBUG -- : Trying to find block devices
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.313258 #11278] DEBUG -- : Found block device: sda
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.313316 #11278] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.313385 #11278] DEBUG -- : Trying to get list of physical devices
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.313536 #11278] DEBUG -- : Getting udev properties for device: sda
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.315430 #11278] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc788
Jul 31 15:16:17 node-2 nailgun-agent: 0a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"76313", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.315455 #11278] DEBUG -- : Trying to find out if device sda is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.315548 #11278] DEBUG -- : Device sda removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.315563 #11278] DEBUG -- : Device sda seems to be appropriate
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.316002 #11278] DEBUG -- : Getting udev properties for device: dm-0
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.317753 #11278] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-1N7vKPJ1bjsbA3OGLOrxEHXAzcLRvrylgnC4kqf1GkLILgVNSeTv0ewqdMuVgslg /dev/disk/by-uuid/8d00f876-1506-4d04-a684-a83f1c11c892 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-1N7vKPJ1bjsbA3OGLOrxEHXAzcLRvrylgnC4kqf1GkLILgVNSeTv0ewqdMuVgslg", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8d00f876-1506-4d04-a684-a83f1c11c892", "ID_FS_UUID_ENC"=>"8d00f876-1506-4d04-a684-a83f1c11c892", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"87237", "nomdmonddf"=>"1", "nom
Jul 31 15:16:17 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.317794 #11278] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.317824 #11278] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.317838 #11278] DEBUG -- : Device dm-0 seems to be appropriate
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.317852 #11278] DEBUG -- : Getting udev properties for device: dm-1
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.319778 #11278] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-eTHWmGCkkaJT311yv5YqCaZ7k0jiUH6EBJXphV1e9lK2vAfSurkeThLjAzOcuQNi /dev/disk/by-uuid/b5bd7386-738a-40fe-9e4b-992f633d1c7e /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-eTHWmGCkkaJT311yv5YqCaZ7k0jiUH6EBJXphV1e9lK2vAfSurkeThLjAzOcuQNi", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b5bd7386-738a-40fe-9e4b-992f633d1c7e", "ID_FS_UUID_ENC"=>"b5bd7386-738a-40fe-9e4b-992f633d1c7e", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2
Jul 31 15:16:17 node-2 nailgun-agent: 2400", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.319806 #11278] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.319848 #11278] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.319863 #11278] DEBUG -- : Device dm-1 seems to be appropriate
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.319902 #11278] DEBUG -- : Getting udev properties for device: dm-2
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.321608 #11278] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-SQxjgFBPF72bANwr1jmubwpYGuQkcHBpikprqqmJI1JkwO0T0LzcrhC32759ab9j /dev/disk/by-uuid/a18bd265-04eb-44e3-9e69-0ea0689d31bc /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-SQxjgFBPF72bANwr1jmubwpYGuQkcHBpikprqqmJI1JkwO0T0LzcrhC32759ab9j", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a18bd265-04eb-44e3-9e69-0ea0689d31bc", "ID_FS_UUID_ENC"=>"a18bd265-04eb-44e3-9e69-0ea0689d31bc", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16197", "nomdmon
Jul 31 15:16:17 node-2 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.321665 #11278] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.321693 #11278] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.321706 #11278] DEBUG -- : Device dm-2 seems to be appropriate
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.321719 #11278] DEBUG -- : Getting udev properties for device: dm-3
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.323568 #11278] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-dBkOOfvxy2lV22gtdhyelODYUk2SfEhyOLlBx51WY9Gip5k27oxDlj2SdlkD4wdY /dev/disk/by-uuid/9d22d348-273b-4f2c-a020-8651f72e61a3 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-dBkOOfvxy2lV22gtdhyelODYUk2SfEhyOLlBx51WY9Gip5k27oxDlj2SdlkD4wdY", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9d22d348-273b-4f2c-a020-8651f72e61a3", "ID_FS_UUID_ENC"=>"9d22d348-273b-4f2c-a020-8651f72e61a3", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21408", "nomdmonddf"=>"1",
Jul 31 15:16:17 node-2 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.323596 #11278] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.323656 #11278] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.323670 #11278] DEBUG -- : Device dm-3 seems to be appropriate
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.323684 #11278] DEBUG -- : Getting udev properties for device: dm-4
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.325406 #11278] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-AWZ4pLndPpnjGpvlStQwrM3CeuA1m29y1YNt5K0Y1TED3Xo25oSFMhFGirmrBiwO /dev/disk/by-uuid/fe0d3e4f-03b6-453d-86c1-1ef15305bfcf /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-AWZ4pLndPpnjGpvlStQwrM3CeuA1m29y1YNt5K0Y1TED3Xo25oSFMhFGirmrBiwO", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"fe0d3e4f-03b6-453d-86c1-1ef15305bfcf", "ID_FS_UUID_ENC"=>"fe0d3e4f-03b6-453d-86c1-1ef15305bfcf", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"24960", "nomdmonddf"=>"1", "nom
Jul 31 15:16:17 node-2 nailgun-agent: dmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.325468 #11278] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.325497 #11278] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.325529 #11278] DEBUG -- : Device dm-4 seems to be appropriate
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.325542 #11278] DEBUG -- : Getting udev properties for device: dm-5
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.327288 #11278] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-AWZ4pLndPpnjGpvlStQwrM3CeuA1m29yhs3rDm2cxzvmHG1zIeVf7Dtx1O60drBU /dev/disk/by-uuid/fc020f77-6d44-45cc-a06b-604ab7aafcb9 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-AWZ4pLndPpnjGpvlStQwrM3CeuA1m29yhs3rDm2cxzvmHG1zIeVf7Dtx1O60drBU", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"fc020f77-6d44-45cc-a06b-604ab7aafcb9", "ID_FS_UUID_ENC"=>"fc020f77-6d44-45cc-a06b-604ab7aafcb9", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"25587", "nomdmonddf"=>"1", "nomdmonisw
Jul 31 15:16:17 node-2 nailgun-agent: "=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.327310 #11278] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.327339 #11278] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.327368 #11278] DEBUG -- : Device dm-5 seems to be appropriate
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.327382 #11278] DEBUG -- : Getting udev properties for device: ram0
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.329132 #11278] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63456", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.329153 #11278] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.329190 #11278] DEBUG -- : Device ram0 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.329220 #11278] DEBUG -- : Getting udev properties for device: ram1
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.330824 #11278] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63468", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.330849 #11278] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.330901 #11278] DEBUG -- : Device ram1 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.330922 #11278] DEBUG -- : Getting udev properties for device: ram2
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.332489 #11278] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63577", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.332515 #11278] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.332552 #11278] DEBUG -- : Device ram2 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.332572 #11278] DEBUG -- : Getting udev properties for device: ram3
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.334059 #11278] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63591", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.334080 #11278] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.334113 #11278] DEBUG -- : Device ram3 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.334130 #11278] DEBUG -- : Getting udev properties for device: ram4
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.335716 #11278] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63605", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.335755 #11278] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.335789 #11278] DEBUG -- : Device ram4 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.335819 #11278] DEBUG -- : Getting udev properties for device: ram5
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.337366 #11278] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63618", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.337387 #11278] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.337419 #11278] DEBUG -- : Device ram5 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.337462 #11278] DEBUG -- : Getting udev properties for device: ram6
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.339003 #11278] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63631", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.339032 #11278] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.339076 #11278] DEBUG -- : Device ram6 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.339095 #11278] DEBUG -- : Getting udev properties for device: ram7
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.340776 #11278] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63642", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.340799 #11278] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.340832 #11278] DEBUG -- : Device ram7 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.340849 #11278] DEBUG -- : Getting udev properties for device: ram8
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.342470 #11278] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63655", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.342499 #11278] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.342527 #11278] DEBUG -- : Device ram8 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.342558 #11278] DEBUG -- : Getting udev properties for device: ram9
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.344176 #11278] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63667", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.344201 #11278] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.344262 #11278] DEBUG -- : Device ram9 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.344281 #11278] DEBUG -- : Getting udev properties for device: loop0
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.345792 #11278] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63352", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.345812 #11278] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.345855 #11278] DEBUG -- : Device loop0 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.345874 #11278] DEBUG -- : Getting udev properties for device: loop1
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.347767 #11278] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63364", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.347801 #11278] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.347853 #11278] DEBUG -- : Device loop1 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.347872 #11278] DEBUG -- : Getting udev properties for device: loop2
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.349384 #11278] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63377", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.349405 #11278] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.349436 #11278] DEBUG -- : Device loop2 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.349496 #11278] DEBUG -- : Getting udev properties for device: loop3
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.351036 #11278] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63392", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.351069 #11278] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.351102 #11278] DEBUG -- : Device loop3 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.351120 #11278] DEBUG -- : Getting udev properties for device: loop4
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.352947 #11278] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63403", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.352995 #11278] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.353032 #11278] DEBUG -- : Device loop4 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.353049 #11278] DEBUG -- : Getting udev properties for device: loop5
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.354741 #11278] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63414", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.354765 #11278] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.354820 #11278] DEBUG -- : Device loop5 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.354840 #11278] DEBUG -- : Getting udev properties for device: loop6
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.356485 #11278] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63427", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.356509 #11278] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.356561 #11278] DEBUG -- : Device loop6 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.356580 #11278] DEBUG -- : Getting udev properties for device: loop7
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.363558 #11278] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63438", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.363589 #11278] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.363631 #11278] DEBUG -- : Device loop7 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.363649 #11278] DEBUG -- : Getting udev properties for device: ram10
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.365536 #11278] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63485", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.365597 #11278] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.365639 #11278] DEBUG -- : Device ram10 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.365656 #11278] DEBUG -- : Getting udev properties for device: ram11
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.367539 #11278] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63501", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.367564 #11278] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.367642 #11278] DEBUG -- : Device ram11 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.367660 #11278] DEBUG -- : Getting udev properties for device: ram12
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.369235 #11278] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63516", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.369256 #11278] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.369284 #11278] DEBUG -- : Device ram12 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.369340 #11278] DEBUG -- : Getting udev properties for device: ram13
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.370896 #11278] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63530", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.370917 #11278] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.370945 #11278] DEBUG -- : Device ram13 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.370962 #11278] DEBUG -- : Getting udev properties for device: ram14
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.372547 #11278] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63542", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.372571 #11278] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.372606 #11278] DEBUG -- : Device ram14 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.372627 #11278] DEBUG -- : Getting udev properties for device: ram15
Jul 31 15:16:17 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374273 #11278] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63555", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374293 #11278] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374327 #11278] DEBUG -- : Device ram15 removable parameter: "0"
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374360 #11278] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374375 #11278] DEBUG -- : Block device seems to be physical data storage: sda
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374412 #11278] DEBUG -- : Found block device: dm-0
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374425 #11278] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374488 #11278] DEBUG -- : Found block device: dm-1
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374499 #11278] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374508 #11278] DEBUG -- : Found block device: dm-2
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374518 #11278] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374526 #11278] DEBUG -- : Found block device: dm-3
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374535 #11278] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374543 #11278] DEBUG -- : Found block device: dm-4
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374553 #11278] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374561 #11278] DEBUG -- : Found block device: dm-5
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374573 #11278] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374608 #11278] DEBUG -- : Found block device: ram0
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374618 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374627 #11278] DEBUG -- : Found block device: ram1
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374637 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374645 #11278] DEBUG -- : Found block device: ram2
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374654 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374663 #11278] DEBUG -- : Found block device: ram3
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374672 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374680 #11278] DEBUG -- : Found block device: ram4
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374689 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374698 #11278] DEBUG -- : Found block device: ram5
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374734 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374742 #11278] DEBUG -- : Found block device: ram6
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374752 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374760 #11278] DEBUG -- : Found block device: ram7
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374771 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374779 #11278] DEBUG -- : Found block device: ram8
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374789 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374797 #11278] DEBUG -- : Found block device: ram9
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374806 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374814 #11278] DEBUG -- : Found block device: loop0
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374892 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374904 #11278] DEBUG -- : Found block device: loop1
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374914 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374922 #11278] DEBUG -- : Found block device: loop2
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374931 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374939 #11278] DEBUG -- : Found block device: loop3
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374949 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374957 #11278] DEBUG -- : Found block device: loop4
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374965 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.374974 #11278] DEBUG -- : Found block device: loop5
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375034 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375043 #11278] DEBUG -- : Found block device: loop6
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375053 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375061 #11278] DEBUG -- : Found block device: loop7
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375070 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375078 #11278] DEBUG -- : Found block device: ram10
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375089 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375097 #11278] DEBUG -- : Found block device: ram11
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375107 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375190 #11278] DEBUG -- : Found block device: ram12
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375205 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375214 #11278] DEBUG -- : Found block device: ram13
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375224 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375232 #11278] DEBUG -- : Found block device: ram14
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375242 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375250 #11278] DEBUG -- : Found block device: ram15
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375260 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.375290 #11278] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.446289 #11278] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 31 15:16:17 node-2 nailgun-agent: D, [2016-07-31T15:16:17.446333 #11278] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 31 15:16:20 node-2 puppet-user[13574]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 31 15:16:20 node-2 puppet-user[13574]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 31 15:16:20 node-2 puppet-user[13574]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 31 15:16:20 node-2 puppet-user[13574]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 31 15:16:20 node-2 puppet-user[13574]: Finished catalog run in 0.06 seconds
Jul 31 15:16:21 node-2 puppet-user[14027]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 31 15:16:22 node-2 puppet-user[14027]: Compiled catalog for node-2.domain.tld in environment production in 0.88 seconds
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 31 15:16:22 node-2 puppet-user[14027]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 31 15:16:29 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578595 #11278] DEBUG -- : Trying to find block devices
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578710 #11278] DEBUG -- : Found block device: sda
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578741 #11278] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578770 #11278] DEBUG -- : Block device seems to be physical data storage: sda
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578791 #11278] DEBUG -- : Found block device: dm-0
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578803 #11278] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578838 #11278] DEBUG -- : Found block device: dm-1
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578854 #11278] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578889 #11278] DEBUG -- : Found block device: dm-2
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578904 #11278] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578915 #11278] DEBUG -- : Found block device: dm-3
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578925 #11278] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578933 #11278] DEBUG -- : Found block device: dm-4
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578942 #11278] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578951 #11278] DEBUG -- : Found block device: dm-5
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578960 #11278] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578968 #11278] DEBUG -- : Found block device: ram0
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.578996 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579005 #11278] DEBUG -- : Found block device: ram1
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579015 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579023 #11278] DEBUG -- : Found block device: ram2
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579032 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579054 #11278] DEBUG -- : Found block device: ram3
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579065 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579073 #11278] DEBUG -- : Found block device: ram4
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579082 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579102 #11278] DEBUG -- : Found block device: ram5
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579112 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579120 #11278] DEBUG -- : Found block device: ram6
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579130 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579164 #11278] DEBUG -- : Found block device: ram7
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579174 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579182 #11278] DEBUG -- : Found block device: ram8
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579191 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579198 #11278] DEBUG -- : Found block device: ram9
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579217 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579225 #11278] DEBUG -- : Found block device: loop0
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579234 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579254 #11278] DEBUG -- : Found block device: loop1
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579264 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579271 #11278] DEBUG -- : Found block device: loop2
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579280 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579299 #11278] DEBUG -- : Found block device: loop3
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579309 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579316 #11278] DEBUG -- : Found block device: loop4
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579325 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579344 #11278] DEBUG -- : Found block device: loop5
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579354 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579362 #11278] DEBUG -- : Found block device: loop6
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579371 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579379 #11278] DEBUG -- : Found block device: loop7
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579387 #11278] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579395 #11278] DEBUG -- : Found block device: ram10
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579430 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579438 #11278] DEBUG -- : Found block device: ram11
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579448 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579456 #11278] DEBUG -- : Found block device: ram12
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579465 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579472 #11278] DEBUG -- : Found block device: ram13
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579481 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579489 #11278] DEBUG -- : Found block device: ram14
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579498 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579506 #11278] DEBUG -- : Found block device: ram15
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579542 #11278] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.579572 #11278] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 31 15:16:29 node-2 nailgun-agent: D, [2016-07-31T15:16:29.790501 #11278] DEBUG -- : Response: status: 200 body: {"id": 2}
Jul 31 15:16:29 node-2 nailgun-agent: I, [2016-07-31T15:16:29.790690 #11278]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 31 15:16:36 node-2 puppet-user[14027]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 31 15:16:36 node-2 puppet-user[14027]: Finished catalog run in 13.90 seconds
Jul 31 15:16:37 node-2 puppet-user[15080]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 31 15:16:37 node-2 puppet-user[15080]: Compiled catalog for node-2.domain.tld in environment production in 0.11 seconds
Jul 31 15:16:42 node-2 puppet-user[15080]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 31 15:17:01 node-2 CRON[16723]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 31 15:17:01 node-2 CRON[16732]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 31 15:17:03 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 15:17:03 node-2 nailgun-agent: I, [2016-07-31T15:17:03.977008 #16727]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 31 15:17:13 node-2 puppet-user[15080]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 31 15:17:13 node-2 puppet-user[15080]: Finished catalog run in 35.14 seconds
Jul 31 15:17:15 node-2 puppet-user[17681]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 31 15:17:15 node-2 puppet-user[17681]: Compiled catalog for node-2.domain.tld in environment production in 0.52 seconds
Jul 31 15:17:15 node-2 puppet-user[17681]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 31 15:17:15 node-2 puppet-user[17681]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 31 15:17:15 node-2 puppet-user[17681]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 31 15:17:15 node-2 puppet-user[17681]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 31 15:17:15 node-2 puppet-user[17681]: Finished catalog run in 0.08 seconds
Jul 31 15:17:16 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 15:17:17 node-2 nailgun-agent: I, [2016-07-31T15:17:17.035725 #16727]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 31 15:17:17 node-2 puppet-user[18139]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 31 15:17:18 node-2 puppet-user[18139]: Compiled catalog for node-2.domain.tld in environment production in 0.87 seconds
Jul 31 15:17:19 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 31 15:17:19 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 31 15:17:19 node-2 crontab[18753]: (root) LIST (root)
Jul 31 15:17:19 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 31 15:17:19 node-2 crontab[18754]: (root) REPLACE (root)
Jul 31 15:17:21 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 31 15:17:22 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 31 15:17:23 node-2 puppet-user[18139]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 31 15:17:23 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8372" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 15:17:23 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 31 15:17:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:44 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:44 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:44 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:44 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:47 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:47 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:47 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:47 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:47 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:47 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:49 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:49 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:49 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:49 node-2 multipathd: uevent trigger error
<27>Jul 31 15:17:49 node-2 multipathd: uevent trigger error
<27>Jul 31 15:18:50 node-2 ntpdate[30011]: no servers can be used, exiting
<27>Jul 31 15:18:50 node-2 ntpdate[30344]: no servers can be used, exiting
<27>Jul 31 15:19:21 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:21 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:21 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:21 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:21 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:39 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:39 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:39 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:39 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:19:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:20:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:20:51 node-2 multipathd: uevent trigger error
<27>Jul 31 15:20:51 node-2 multipathd: uevent trigger error
<27>Jul 31 15:20:51 node-2 multipathd: uevent trigger error
<27>Jul 31 15:20:51 node-2 multipathd: uevent trigger error
<27>Jul 31 15:20:54 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 15:20:54 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 15:21:00 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 15:21:00 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 15:21:06 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 15:21:11 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 15:21:11 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 15:21:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:21:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:21:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:21:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:21:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:21:31 node-2 multipathd: uevent trigger error
<27>Jul 31 15:21:31 node-2 multipathd: uevent trigger error
<27>Jul 31 15:21:31 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:04 node-2 multipathd: uevent trigger error
<129>Jul 31 15:22:07 node-2 haproxy[24418]: Server odl-neutron-endpoint/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 63ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:07 node-2 haproxy[24418]: proxy odl-neutron-endpoint has no server available!
<129>Jul 31 15:22:07 node-2 haproxy[24418]: Server odl-jetty/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:07 node-2 haproxy[24418]: proxy odl-jetty has no server available!
<27>Jul 31 15:22:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:30 node-2 multipathd: uevent trigger error
<129>Jul 31 15:22:32 node-2 haproxy[27165]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:33 node-2 haproxy[27174]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:33 node-2 haproxy[27174]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:33 node-2 haproxy[27174]: proxy mysqld has no server available!
<27>Jul 31 15:22:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:39 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:39 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:39 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:39 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:39 node-2 multipathd: uevent trigger error
<129>Jul 31 15:22:41 node-2 haproxy[29841]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:42 node-2 haproxy[29845]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:42 node-2 haproxy[29845]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:42 node-2 haproxy[29845]: proxy mysqld has no server available!
<129>Jul 31 15:22:42 node-2 haproxy[29845]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:42 node-2 haproxy[29845]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:43 node-2 haproxy[29845]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:43 node-2 haproxy[29845]: proxy object-storage has no server available!
<27>Jul 31 15:22:44 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:45 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:45 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:45 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:45 node-2 multipathd: uevent trigger error
<129>Jul 31 15:22:47 node-2 haproxy[31240]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:47 node-2 haproxy[31240]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:47 node-2 haproxy[31240]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:47 node-2 haproxy[31240]: proxy neutron has no server available!
<129>Jul 31 15:22:47 node-2 haproxy[31240]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:48 node-2 haproxy[31247]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:48 node-2 haproxy[31247]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:48 node-2 haproxy[31247]: proxy mysqld has no server available!
<129>Jul 31 15:22:48 node-2 haproxy[31247]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:48 node-2 haproxy[31247]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:48 node-2 haproxy[31247]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:48 node-2 haproxy[31247]: proxy object-storage has no server available!
<27>Jul 31 15:22:50 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:50 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:50 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:50 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:50 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:50 node-2 multipathd: uevent trigger error
<129>Jul 31 15:22:52 node-2 haproxy[32665]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:53 node-2 haproxy[32669]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:53 node-2 haproxy[32669]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:53 node-2 haproxy[32669]: proxy keystone-1 has no server available!
<129>Jul 31 15:22:53 node-2 haproxy[32669]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:53 node-2 haproxy[32669]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:53 node-2 haproxy[32669]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:53 node-2 haproxy[32669]: proxy keystone-2 has no server available!
<129>Jul 31 15:22:53 node-2 haproxy[32669]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:53 node-2 haproxy[32669]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:53 node-2 haproxy[32669]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:53 node-2 haproxy[32669]: proxy neutron has no server available!
<129>Jul 31 15:22:54 node-2 haproxy[32669]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:54 node-2 haproxy[32669]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:54 node-2 haproxy[32669]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:54 node-2 haproxy[32669]: proxy mysqld has no server available!
<129>Jul 31 15:22:54 node-2 haproxy[32669]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:54 node-2 haproxy[32669]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:54 node-2 haproxy[32669]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:54 node-2 haproxy[32669]: proxy object-storage has no server available!
<27>Jul 31 15:22:56 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:56 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:56 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:56 node-2 multipathd: uevent trigger error
<27>Jul 31 15:22:56 node-2 multipathd: uevent trigger error
<129>Jul 31 15:22:58 node-2 haproxy[1648]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:58 node-2 haproxy[1648]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:58 node-2 haproxy[1648]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:58 node-2 haproxy[1648]: proxy keystone-1 has no server available!
<129>Jul 31 15:22:58 node-2 haproxy[1648]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:58 node-2 haproxy[1648]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:59 node-2 haproxy[1652]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:59 node-2 haproxy[1652]: proxy keystone-2 has no server available!
<129>Jul 31 15:22:59 node-2 haproxy[1652]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:59 node-2 haproxy[1652]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:59 node-2 haproxy[1652]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:59 node-2 haproxy[1652]: proxy neutron has no server available!
<129>Jul 31 15:22:59 node-2 haproxy[1652]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:59 node-2 haproxy[1652]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:59 node-2 haproxy[1652]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:59 node-2 haproxy[1652]: proxy mysqld has no server available!
<129>Jul 31 15:22:59 node-2 haproxy[1652]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:59 node-2 haproxy[1652]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:22:59 node-2 haproxy[1652]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:22:59 node-2 haproxy[1652]: proxy object-storage has no server available!
<129>Jul 31 15:23:00 node-2 haproxy[1652]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:00 node-2 haproxy[1652]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:00 node-2 haproxy[1652]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:00 node-2 haproxy[1652]: proxy aodh has no server available!
<27>Jul 31 15:23:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:01 node-2 multipathd: uevent trigger error
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:04 node-2 haproxy[3038]: proxy keystone-1 has no server available!
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:04 node-2 haproxy[3038]: proxy keystone-2 has no server available!
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:04 node-2 haproxy[3038]: proxy neutron has no server available!
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:04 node-2 haproxy[3038]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:05 node-2 haproxy[3042]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:05 node-2 haproxy[3042]: proxy mysqld has no server available!
<129>Jul 31 15:23:05 node-2 haproxy[3042]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:05 node-2 haproxy[3042]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:05 node-2 haproxy[3042]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:05 node-2 haproxy[3042]: proxy object-storage has no server available!
<129>Jul 31 15:23:05 node-2 haproxy[3042]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:05 node-2 haproxy[3042]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:05 node-2 haproxy[3042]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:05 node-2 haproxy[3042]: proxy aodh has no server available!
<129>Jul 31 15:23:05 node-2 haproxy[3042]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:05 node-2 haproxy[3042]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:05 node-2 haproxy[3042]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:05 node-2 haproxy[3042]: proxy ceilometer has no server available!
<27>Jul 31 15:23:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:07 node-2 multipathd: uevent trigger error
<129>Jul 31 15:23:09 node-2 haproxy[4446]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:09 node-2 haproxy[4446]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:09 node-2 haproxy[4446]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:09 node-2 haproxy[4446]: proxy keystone-1 has no server available!
<129>Jul 31 15:23:09 node-2 haproxy[4446]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:09 node-2 haproxy[4446]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:09 node-2 haproxy[4446]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:09 node-2 haproxy[4446]: proxy keystone-2 has no server available!
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:10 node-2 haproxy[4450]: proxy neutron has no server available!
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:10 node-2 haproxy[4450]: proxy mysqld has no server available!
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:10 node-2 haproxy[4450]: proxy object-storage has no server available!
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:10 node-2 haproxy[4450]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:10 node-2 haproxy[4450]: proxy aodh has no server available!
<129>Jul 31 15:23:11 node-2 haproxy[4450]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:11 node-2 haproxy[4450]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:11 node-2 haproxy[4450]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:11 node-2 haproxy[4450]: proxy ceilometer has no server available!
<27>Jul 31 15:23:12 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:12 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:12 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:12 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:12 node-2 multipathd: uevent trigger error
<129>Jul 31 15:23:14 node-2 haproxy[5869]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:15 node-2 haproxy[5873]: proxy keystone-1 has no server available!
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:15 node-2 haproxy[5873]: proxy keystone-2 has no server available!
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:15 node-2 haproxy[5873]: proxy neutron has no server available!
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:15 node-2 haproxy[5873]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:15 node-2 haproxy[5873]: proxy mysqld has no server available!
<129>Jul 31 15:23:16 node-2 haproxy[5873]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:16 node-2 haproxy[5873]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:16 node-2 haproxy[5873]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:16 node-2 haproxy[5873]: proxy object-storage has no server available!
<129>Jul 31 15:23:16 node-2 haproxy[5873]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:16 node-2 haproxy[5873]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:16 node-2 haproxy[5873]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:16 node-2 haproxy[5873]: proxy aodh has no server available!
<129>Jul 31 15:23:16 node-2 haproxy[5873]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:16 node-2 haproxy[5873]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:16 node-2 haproxy[5873]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:16 node-2 haproxy[5873]: proxy ceilometer has no server available!
<27>Jul 31 15:23:17 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:17 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:17 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:17 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:17 node-2 multipathd: uevent trigger error
<129>Jul 31 15:23:20 node-2 haproxy[7385]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:20 node-2 haproxy[7385]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:21 node-2 haproxy[7389]: proxy keystone-1 has no server available!
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:21 node-2 haproxy[7389]: proxy keystone-2 has no server available!
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:21 node-2 haproxy[7389]: proxy glance-api has no server available!
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:21 node-2 haproxy[7389]: proxy glance-glare has no server available!
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:21 node-2 haproxy[7389]: proxy neutron has no server available!
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:21 node-2 haproxy[7389]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:21 node-2 haproxy[7389]: proxy glance-registry has no server available!
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:22 node-2 haproxy[7389]: proxy mysqld has no server available!
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:22 node-2 haproxy[7389]: proxy object-storage has no server available!
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:22 node-2 haproxy[7389]: proxy aodh has no server available!
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:22 node-2 haproxy[7389]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:22 node-2 haproxy[7389]: proxy ceilometer has no server available!
<27>Jul 31 15:23:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:24 node-2 multipathd: uevent trigger error
<129>Jul 31 15:23:26 node-2 haproxy[8922]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:27 node-2 haproxy[8926]: proxy keystone-1 has no server available!
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:27 node-2 haproxy[8926]: proxy keystone-2 has no server available!
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:27 node-2 haproxy[8926]: proxy nova-api has no server available!
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:27 node-2 haproxy[8926]: proxy nova-metadata-api has no server available!
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:27 node-2 haproxy[8926]: proxy glance-api has no server available!
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:27 node-2 haproxy[8926]: proxy glance-glare has no server available!
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:27 node-2 haproxy[8926]: proxy neutron has no server available!
<129>Jul 31 15:23:27 node-2 haproxy[8926]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:28 node-2 haproxy[8926]: proxy glance-registry has no server available!
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:28 node-2 haproxy[8926]: proxy mysqld has no server available!
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:28 node-2 haproxy[8926]: proxy object-storage has no server available!
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:28 node-2 haproxy[8926]: proxy aodh has no server available!
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:28 node-2 haproxy[8926]: proxy ceilometer has no server available!
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:28 node-2 haproxy[8926]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:28 node-2 haproxy[8926]: proxy nova-novncproxy has no server available!
<27>Jul 31 15:23:29 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:29 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:30 node-2 multipathd: uevent trigger error
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:32 node-2 haproxy[10514]: proxy keystone-1 has no server available!
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:32 node-2 haproxy[10514]: proxy keystone-2 has no server available!
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:32 node-2 haproxy[10514]: proxy nova-api has no server available!
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:32 node-2 haproxy[10514]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:32 node-2 haproxy[10514]: proxy nova-metadata-api has no server available!
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:33 node-2 haproxy[10518]: proxy cinder-api has no server available!
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:33 node-2 haproxy[10518]: proxy glance-api has no server available!
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:33 node-2 haproxy[10518]: proxy glance-glare has no server available!
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:33 node-2 haproxy[10518]: proxy neutron has no server available!
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:33 node-2 haproxy[10518]: proxy glance-registry has no server available!
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:33 node-2 haproxy[10518]: proxy mysqld has no server available!
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:33 node-2 haproxy[10518]: proxy object-storage has no server available!
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:33 node-2 haproxy[10518]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:33 node-2 haproxy[10518]: proxy aodh has no server available!
<129>Jul 31 15:23:34 node-2 haproxy[10518]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:34 node-2 haproxy[10518]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:34 node-2 haproxy[10518]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:34 node-2 haproxy[10518]: proxy ceilometer has no server available!
<129>Jul 31 15:23:34 node-2 haproxy[10518]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:34 node-2 haproxy[10518]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:34 node-2 haproxy[10518]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:34 node-2 haproxy[10518]: proxy nova-novncproxy has no server available!
<27>Jul 31 15:23:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:35 node-2 multipathd: uevent trigger error
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:38 node-2 haproxy[12007]: proxy keystone-1 has no server available!
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:38 node-2 haproxy[12007]: proxy keystone-2 has no server available!
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:38 node-2 haproxy[12007]: proxy nova-api has no server available!
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 31 15:23:38 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:38 node-2 haproxy[12007]: proxy nova-metadata-api has no server available!
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:38 node-2 haproxy[12007]: proxy cinder-api has no server available!
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:38 node-2 haproxy[12007]: proxy glance-api has no server available!
<129>Jul 31 15:23:38 node-2 haproxy[12007]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:39 node-2 haproxy[12011]: proxy glance-glare has no server available!
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:39 node-2 haproxy[12011]: proxy neutron has no server available!
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:39 node-2 haproxy[12011]: proxy glance-registry has no server available!
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:39 node-2 haproxy[12011]: proxy mysqld has no server available!
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:39 node-2 haproxy[12011]: proxy object-storage has no server available!
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:39 node-2 haproxy[12011]: proxy aodh has no server available!
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:39 node-2 haproxy[12011]: proxy ceilometer has no server available!
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:39 node-2 haproxy[12011]: proxy heat-api has no server available!
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:39 node-2 haproxy[12011]: proxy heat-api-cfn has no server available!
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:39 node-2 haproxy[12011]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:40 node-2 haproxy[12011]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:40 node-2 haproxy[12011]: proxy heat-api-cloudwatch has no server available!
<129>Jul 31 15:23:40 node-2 haproxy[12011]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:40 node-2 haproxy[12011]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 15:23:40 node-2 haproxy[12011]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 31 15:23:40 node-2 haproxy[12011]: proxy nova-novncproxy has no server available!
<27>Jul 31 15:23:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:44 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:44 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:44 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:44 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:44 node-2 multipathd: uevent trigger error
<27>Jul 31 15:23:45 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 15:23:54 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 31 15:24:19 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 31 15:24:21 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 31 15:25:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:25:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:25:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:25:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:25:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:02 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 15:27:45 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:45 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:45 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:45 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:45 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:45 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:52 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:52 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:52 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:52 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:52 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:57 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:57 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:57 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:57 node-2 multipathd: uevent trigger error
<27>Jul 31 15:27:57 node-2 multipathd: uevent trigger error
<43>Jul 31 15:28:14 node-2 apache2_error [Sun Jul 31 15:28:10.247243 2016] [mpm_event:notice] [pid 25440:tid 140532239918976] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 15:28:14 node-2 apache2_error [Sun Jul 31 15:28:10.247377 2016] [core:notice] [pid 25440:tid 140532239918976] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 15:28:14 node-2 apache2_error [Sun Jul 31 15:28:13.384405 2016] [mpm_event:notice] [pid 25440:tid 140532239918976] AH00491: caught SIGTERM, shutting down
<43>Jul 31 15:28:14 node-2 apache2_error [Sun Jul 31 15:28:14.471928 2016] [mpm_worker:notice] [pid 25817:tid 139744788674432] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 15:28:14 node-2 apache2_error [Sun Jul 31 15:28:14.471971 2016] [core:notice] [pid 25817:tid 139744788674432] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 15:28:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:28:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:28:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:28:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:28:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:28:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:28:22 node-2 multipathd: uevent trigger error
<27>Jul 31 15:28:22 node-2 multipathd: uevent trigger error
<27>Jul 31 15:28:22 node-2 multipathd: uevent trigger error
<27>Jul 31 15:28:22 node-2 multipathd: uevent trigger error
<27>Jul 31 15:28:22 node-2 multipathd: uevent trigger error
<43>Jul 31 15:29:34 node-2 apache2_error [Sun Jul 31 15:29:31.008636 2016] [mpm_worker:notice] [pid 25817:tid 139744788674432] AH00295: caught SIGTERM, shutting down
<43>Jul 31 15:29:34 node-2 apache2_error [Sun Jul 31 15:29:31.754096 2016] [mpm_worker:notice] [pid 7273:tid 140001620445056] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 15:29:34 node-2 apache2_error [Sun Jul 31 15:29:31.754144 2016] [core:notice] [pid 7273:tid 140001620445056] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 15:30:13 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 31 15:30:24 node-2 apache2_error [Sun Jul 31 15:30:15.607630 2016] [mpm_worker:notice] [pid 7273:tid 140001620445056] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 15:30:24 node-2 apache2_error [Sun Jul 31 15:30:15.802594 2016] [mpm_worker:warn] [pid 7273:tid 140001620445056] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 15:30:24 node-2 apache2_error [Sun Jul 31 15:30:15.805974 2016] [mpm_worker:notice] [pid 7273:tid 140001620445056] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 15:30:24 node-2 apache2_error [Sun Jul 31 15:30:15.805989 2016] [core:notice] [pid 7273:tid 140001620445056] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 15:31:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:38 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:38 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:38 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:38 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:38 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:31:43 node-2 multipathd: uevent trigger error
<27>Jul 31 15:32:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:32:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:32:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:32:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:32:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:32:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:32:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:32:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:32:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:32:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:33:15 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 15:34:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:34:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:34:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:34:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:12 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:12 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:12 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:12 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:12 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:34 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:34 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:34 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:34 node-2 multipathd: uevent trigger error
<27>Jul 31 15:35:34 node-2 multipathd: uevent trigger error
<27>Jul 31 15:36:17 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 15:38:02 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:02 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:02 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:02 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:02 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:02 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:18 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:29 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:29 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:29 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:29 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:29 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:29 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:29 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:50 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:50 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:50 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:50 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:50 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:38:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:39:19 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 15:39:40 node-2 multipathd: uevent trigger error
<27>Jul 31 15:39:40 node-2 multipathd: uevent trigger error
<27>Jul 31 15:39:40 node-2 multipathd: uevent trigger error
<27>Jul 31 15:39:40 node-2 multipathd: uevent trigger error
<27>Jul 31 15:39:40 node-2 multipathd: uevent trigger error
<27>Jul 31 15:40:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:40:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:40:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:40:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:40:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:40:40 node-2 multipathd: uevent trigger error
<27>Jul 31 15:40:40 node-2 multipathd: uevent trigger error
<27>Jul 31 15:40:40 node-2 multipathd: uevent trigger error
<27>Jul 31 15:40:40 node-2 multipathd: uevent trigger error
<27>Jul 31 15:42:20 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 15:43:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:04 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:42 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:42 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:42 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:42 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:42 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:48 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:48 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:48 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:48 node-2 multipathd: uevent trigger error
<27>Jul 31 15:43:48 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:32 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:32 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:32 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:32 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:37 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:37 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:37 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:37 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:37 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:44:54 node-2 multipathd: uevent trigger error
<27>Jul 31 15:45:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:45:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:45:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:45:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:45:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:45:22 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 15:45:34 node-2 multipathd: uevent trigger error
<27>Jul 31 15:45:34 node-2 multipathd: uevent trigger error
<27>Jul 31 15:45:34 node-2 multipathd: uevent trigger error
<27>Jul 31 15:45:34 node-2 multipathd: uevent trigger error
<27>Jul 31 15:45:34 node-2 multipathd: uevent trigger error
<27>Jul 31 15:46:42 node-2 multipathd: uevent trigger error
<27>Jul 31 15:46:42 node-2 multipathd: uevent trigger error
<27>Jul 31 15:46:42 node-2 multipathd: uevent trigger error
<27>Jul 31 15:46:42 node-2 multipathd: uevent trigger error
<27>Jul 31 15:46:42 node-2 multipathd: uevent trigger error
<27>Jul 31 15:47:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:47:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:47:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:47:01 node-2 multipathd: uevent trigger error
<11>Jul 31 15:47:15 node-2 liberasurecode[21165]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:15 node-2 liberasurecode[21165]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:15 node-2 liberasurecode[21165]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:15 node-2 liberasurecode[21165]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:15 node-2 liberasurecode[21189]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:15 node-2 liberasurecode[21189]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:15 node-2 liberasurecode[21189]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:15 node-2 liberasurecode[21189]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:17 node-2 liberasurecode[21824]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:17 node-2 liberasurecode[21824]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:17 node-2 liberasurecode[21824]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:17 node-2 liberasurecode[21824]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22475]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22475]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22475]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22475]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22514]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22514]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22514]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22514]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22573]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22573]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22573]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22573]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22661]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22661]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22661]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22661]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22688]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22688]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22688]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22688]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22673]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22673]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22673]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:23 node-2 liberasurecode[22673]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:24 node-2 liberasurecode[22712]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:24 node-2 liberasurecode[22712]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:24 node-2 liberasurecode[22712]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:24 node-2 liberasurecode[22712]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:32 node-2 liberasurecode[25160]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:32 node-2 liberasurecode[25160]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:32 node-2 liberasurecode[25160]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:47:32 node-2 liberasurecode[25160]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 15:47:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:47:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:47:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:47:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:47:41 node-2 multipathd: uevent trigger error
<27>Jul 31 15:48:24 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 31 15:48:36 node-2 apache2_error [Sun Jul 31 15:48:27.988762 2016] [mpm_worker:notice] [pid 7273:tid 140001620445056] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 15:48:36 node-2 apache2_error [Sun Jul 31 15:48:28.370096 2016] [mpm_worker:warn] [pid 7273:tid 140001620445056] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 15:48:36 node-2 apache2_error [Sun Jul 31 15:48:28.373102 2016] [mpm_worker:notice] [pid 7273:tid 140001620445056] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 15:48:36 node-2 apache2_error [Sun Jul 31 15:48:28.373123 2016] [core:notice] [pid 7273:tid 140001620445056] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 15:49:06 node-2 apache2_error [Sun Jul 31 15:49:05.590441 2016] [mpm_worker:notice] [pid 7273:tid 140001620445056] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 15:49:06 node-2 apache2_error [Sun Jul 31 15:49:05.785081 2016] [mpm_worker:warn] [pid 7273:tid 140001620445056] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 15:49:06 node-2 apache2_error [Sun Jul 31 15:49:05.795423 2016] [mpm_worker:notice] [pid 7273:tid 140001620445056] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 15:49:06 node-2 apache2_error [Sun Jul 31 15:49:05.795456 2016] [core:notice] [pid 7273:tid 140001620445056] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 15:49:09 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:09 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:09 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:09 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:09 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:15 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:15 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:15 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:15 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:21 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:21 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:21 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:21 node-2 multipathd: uevent trigger error
<27>Jul 31 15:49:21 node-2 multipathd: uevent trigger error
<43>Jul 31 15:49:56 node-2 apache2_error [Sun Jul 31 15:49:56.059866 2016] [mpm_worker:notice] [pid 7273:tid 140001620445056] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 15:49:56 node-2 apache2_error [Sun Jul 31 15:49:56.254556 2016] [mpm_worker:warn] [pid 7273:tid 140001620445056] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 15:49:56 node-2 apache2_error [Sun Jul 31 15:49:56.265401 2016] [mpm_worker:notice] [pid 7273:tid 140001620445056] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 15:49:56 node-2 apache2_error [Sun Jul 31 15:49:56.265443 2016] [core:notice] [pid 7273:tid 140001620445056] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 15:50:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:00 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:00 node-2 multipathd: uevent trigger error
<11>Jul 31 15:50:01 node-2 liberasurecode[17443]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:50:01 node-2 liberasurecode[17443]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:50:01 node-2 liberasurecode[17443]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:50:01 node-2 liberasurecode[17443]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 15:50:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:07 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:13 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:13 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:13 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:13 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:13 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:36 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:36 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:36 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:36 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:36 node-2 multipathd: uevent trigger error
<27>Jul 31 15:50:58 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:06 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 31 15:51:14 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:14 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:14 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:14 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:14 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:19 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:24 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:38 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:38 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:38 node-2 multipathd: uevent trigger error
<27>Jul 31 15:51:38 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:00 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 15:52:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:13 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:13 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:13 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:13 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:17 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:17 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:17 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:17 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:17 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:30 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:35 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:47 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:47 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:47 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:48 node-2 multipathd: uevent trigger error
<27>Jul 31 15:52:48 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:01 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:06 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:11 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:11 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:11 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:11 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:16 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:16 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:16 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:16 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:16 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:20 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:25 node-2 multipathd: uevent trigger error
<27>Jul 31 15:53:25 node-2 multipathd: uevent trigger error
<11>Jul 31 15:55:01 node-2 liberasurecode[21910]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:55:01 node-2 liberasurecode[21910]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:55:01 node-2 liberasurecode[21910]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 15:55:01 node-2 liberasurecode[21910]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
