Sep  7 19:50:53 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8379" x-info="http://www.rsyslog.com"] start
Sep  7 19:50:53 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep  7 19:50:53 node-2 rsyslogd: rsyslogd's groupid changed to 104
Sep  7 19:50:53 node-2 rsyslogd: rsyslogd's userid changed to 101
Sep  7 19:50:53 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep  7 19:50:53 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep  7 19:50:53 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep  7 19:50:53 node-2 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep  7 19:50:53 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=46f8d5d6-a4ee-4f0c-afe0-1d52d0af8229 nomdmonddf nomdmonisw
Sep  7 19:50:53 node-2 kernel: [    0.000000] KERNEL supported cpus:
Sep  7 19:50:53 node-2 kernel: [    0.000000]   Intel GenuineIntel
Sep  7 19:50:53 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Sep  7 19:50:53 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Sep  7 19:50:53 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep  7 19:50:53 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep  7 19:50:53 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep  7 19:50:53 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Sep  7 19:50:53 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
Sep  7 19:50:53 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep  7 19:50:53 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep  7 19:50:53 node-2 kernel: [    0.000000] No AGP bridge found
Sep  7 19:50:53 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep  7 19:50:53 node-2 kernel: [    0.000000] MTRR default type: write-back
Sep  7 19:50:53 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep  7 19:50:53 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Sep  7 19:50:53 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep  7 19:50:53 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep  7 19:50:53 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Sep  7 19:50:53 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep  7 19:50:53 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep  7 19:50:53 node-2 kernel: [    0.000000]   2 disabled
Sep  7 19:50:53 node-2 kernel: [    0.000000]   3 disabled
Sep  7 19:50:53 node-2 kernel: [    0.000000]   4 disabled
Sep  7 19:50:53 node-2 kernel: [    0.000000]   5 disabled
Sep  7 19:50:53 node-2 kernel: [    0.000000]   6 disabled
Sep  7 19:50:53 node-2 kernel: [    0.000000]   7 disabled
Sep  7 19:50:53 node-2 kernel: [    0.000000]   8 disabled
Sep  7 19:50:53 node-2 kernel: [    0.000000]   9 disabled
Sep  7 19:50:53 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep  7 19:50:53 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep  7 19:50:53 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep  7 19:50:53 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep  7 19:50:53 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep  7 19:50:53 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Sep  7 19:50:53 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep  7 19:50:53 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep  7 19:50:53 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep  7 19:50:53 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep  7 19:50:53 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep  7 19:50:53 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep  7 19:50:53 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep  7 19:50:53 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep  7 19:50:53 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep  7 19:50:53 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep  7 19:50:53 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep  7 19:50:53 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep  7 19:50:53 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep  7 19:50:53 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep  7 19:50:53 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep  7 19:50:53 node-2 kernel: [    0.000000] Zone ranges:
Sep  7 19:50:53 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] Movable zone start for each node
Sep  7 19:50:53 node-2 kernel: [    0.000000] Early memory node ranges
Sep  7 19:50:53 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep  7 19:50:53 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep  7 19:50:53 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep  7 19:50:53 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep  7 19:50:53 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep  7 19:50:53 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep  7 19:50:53 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep  7 19:50:53 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep  7 19:50:53 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep  7 19:50:53 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep  7 19:50:53 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep  7 19:50:53 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep  7 19:50:53 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep  7 19:50:53 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep  7 19:50:53 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep  7 19:50:53 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep  7 19:50:53 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep  7 19:50:53 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep  7 19:50:53 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep  7 19:50:53 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep  7 19:50:53 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep  7 19:50:53 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep  7 19:50:53 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep  7 19:50:53 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 
Sep  7 19:50:53 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep  7 19:50:53 node-2 kernel: [    0.000000] Policy zone: Normal
Sep  7 19:50:53 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=46f8d5d6-a4ee-4f0c-afe0-1d52d0af8229 nomdmonddf nomdmonisw
Sep  7 19:50:53 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep  7 19:50:53 node-2 kernel: [    0.000000] Checking aperture...
Sep  7 19:50:53 node-2 kernel: [    0.000000] No AGP bridge found
Sep  7 19:50:53 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep  7 19:50:53 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep  7 19:50:53 node-2 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep  7 19:50:53 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep  7 19:50:53 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Sep  7 19:50:53 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep  7 19:50:53 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep  7 19:50:53 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep  7 19:50:53 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep  7 19:50:53 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep  7 19:50:53 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Sep  7 19:50:53 node-2 kernel: [    0.000000] console [tty0] enabled
Sep  7 19:50:53 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep  7 19:50:53 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep  7 19:50:53 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep  7 19:50:53 node-2 kernel: [    0.000000] hpet clockevent registered
Sep  7 19:50:53 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep  7 19:50:53 node-2 kernel: [    0.004000] tsc: Detected 3492.231 MHz processor
Sep  7 19:50:53 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.46 BogoMIPS (lpj=13968924)
Sep  7 19:50:53 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep  7 19:50:53 node-2 kernel: [    0.000043] Security Framework initialized
Sep  7 19:50:53 node-2 kernel: [    0.000061] AppArmor: AppArmor initialized
Sep  7 19:50:53 node-2 kernel: [    0.000062] Yama: becoming mindful.
Sep  7 19:50:53 node-2 kernel: [    0.001463] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.006376] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.008302] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.008330] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.008622] Initializing cgroup subsys memory
Sep  7 19:50:53 node-2 kernel: [    0.008630] Initializing cgroup subsys devices
Sep  7 19:50:53 node-2 kernel: [    0.008632] Initializing cgroup subsys freezer
Sep  7 19:50:53 node-2 kernel: [    0.008634] Initializing cgroup subsys blkio
Sep  7 19:50:53 node-2 kernel: [    0.008635] Initializing cgroup subsys perf_event
Sep  7 19:50:53 node-2 kernel: [    0.008638] Initializing cgroup subsys hugetlb
Sep  7 19:50:53 node-2 kernel: [    0.008658] CPU: Physical Processor ID: 0
Sep  7 19:50:53 node-2 kernel: [    0.008659] CPU: Processor Core ID: 0
Sep  7 19:50:53 node-2 kernel: [    0.008663] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep  7 19:50:53 node-2 kernel: [    0.008663] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep  7 19:50:53 node-2 kernel: [    0.009356] mce: CPU supports 22 MCE banks
Sep  7 19:50:53 node-2 kernel: [    0.009384] CPU0: Thermal monitoring enabled (TM1)
Sep  7 19:50:53 node-2 kernel: [    0.009404] process: using mwait in idle threads
Sep  7 19:50:53 node-2 kernel: [    0.009408] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep  7 19:50:53 node-2 kernel: [    0.009408] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep  7 19:50:53 node-2 kernel: [    0.009408] tlb_flushall_shift: 6
Sep  7 19:50:53 node-2 kernel: [    0.009496] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep  7 19:50:53 node-2 kernel: [    0.010220] ACPI: Core revision 20131115
Sep  7 19:50:53 node-2 kernel: [    0.022888] ACPI: All ACPI Tables successfully acquired
Sep  7 19:50:53 node-2 kernel: [    0.023050] ftrace: allocating 28617 entries in 112 pages
Sep  7 19:50:53 node-2 kernel: [    0.032012] dmar: Host address width 46
Sep  7 19:50:53 node-2 kernel: [    0.032015] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep  7 19:50:53 node-2 kernel: [    0.032021] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep  7 19:50:53 node-2 kernel: [    0.032022] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep  7 19:50:53 node-2 kernel: [    0.032026] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep  7 19:50:53 node-2 kernel: [    0.032028] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep  7 19:50:53 node-2 kernel: [    0.032029] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep  7 19:50:53 node-2 kernel: [    0.032030] dmar: ATSR flags: 0x0
Sep  7 19:50:53 node-2 kernel: [    0.032031] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep  7 19:50:53 node-2 kernel: [    0.032032] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep  7 19:50:53 node-2 kernel: [    0.032147] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep  7 19:50:53 node-2 kernel: [    0.032149] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep  7 19:50:53 node-2 kernel: [    0.032150] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep  7 19:50:53 node-2 kernel: [    0.032151] HPET id 0 under DRHD base 0xc7ffc000
Sep  7 19:50:53 node-2 kernel: [    0.032152] Your BIOS is broken and requested that x2apic be disabled.
Sep  7 19:50:53 node-2 kernel: [    0.032152] This will slightly decrease performance.
Sep  7 19:50:53 node-2 kernel: [    0.032152] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep  7 19:50:53 node-2 kernel: [    0.032584] Enabled IRQ remapping in xapic mode
Sep  7 19:50:53 node-2 kernel: [    0.032586] x2apic not enabled, IRQ remapping is in xapic mode
Sep  7 19:50:53 node-2 kernel: [    0.032589] Switched APIC routing to physical flat.
Sep  7 19:50:53 node-2 kernel: [    0.033216] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep  7 19:50:53 node-2 kernel: [    0.072869] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep  7 19:50:53 node-2 kernel: [    0.072875] TSC deadline timer enabled
Sep  7 19:50:53 node-2 kernel: [    0.072882] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep  7 19:50:53 node-2 kernel: [    0.072888] ... version:                3
Sep  7 19:50:53 node-2 kernel: [    0.072889] ... bit width:              48
Sep  7 19:50:53 node-2 kernel: [    0.072890] ... generic registers:      4
Sep  7 19:50:53 node-2 kernel: [    0.072891] ... value mask:             0000ffffffffffff
Sep  7 19:50:53 node-2 kernel: [    0.072892] ... max period:             0000ffffffffffff
Sep  7 19:50:53 node-2 kernel: [    0.072893] ... fixed-purpose events:   3
Sep  7 19:50:53 node-2 kernel: [    0.072894] ... event mask:             000000070000000f
Sep  7 19:50:53 node-2 kernel: [    0.074273] x86: Booting SMP configuration:
Sep  7 19:50:53 node-2 kernel: [    0.088380] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep  7 19:50:53 node-2 kernel: [    0.074275] .... node  #0, CPUs:        #1  #2  #3
Sep  7 19:50:53 node-2 kernel: [    0.116300] .... node  #1, CPUs:    #4  #5  #6  #7
Sep  7 19:50:53 node-2 kernel: [    0.270446] .... node  #0, CPUs:    #8  #9 #10 #11
Sep  7 19:50:53 node-2 kernel: [    0.326067] .... node  #1, CPUs:   #12 #13 #14 #15
Sep  7 19:50:53 node-2 kernel: [    0.383131] x86: Booted up 2 nodes, 16 CPUs
Sep  7 19:50:53 node-2 kernel: [    0.383134] smpboot: Total of 16 processors activated (111763.96 BogoMIPS)
Sep  7 19:50:53 node-2 kernel: [    0.407237] devtmpfs: initialized
Sep  7 19:50:53 node-2 kernel: [    0.410340] EVM: security.selinux
Sep  7 19:50:53 node-2 kernel: [    0.410342] EVM: security.SMACK64
Sep  7 19:50:53 node-2 kernel: [    0.410343] EVM: security.ima
Sep  7 19:50:53 node-2 kernel: [    0.410344] EVM: security.capability
Sep  7 19:50:53 node-2 kernel: [    0.410394] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.411090] pinctrl core: initialized pinctrl subsystem
Sep  7 19:50:53 node-2 kernel: [    0.411151] regulator-dummy: no parameters
Sep  7 19:50:53 node-2 kernel: [    0.411183] RTC time: 19:50:17, date: 09/07/16
Sep  7 19:50:53 node-2 kernel: [    0.411217] NET: Registered protocol family 16
Sep  7 19:50:53 node-2 kernel: [    0.411302] cpuidle: using governor ladder
Sep  7 19:50:53 node-2 kernel: [    0.411303] cpuidle: using governor menu
Sep  7 19:50:53 node-2 kernel: [    0.411338] ACPI: bus type PCI registered
Sep  7 19:50:53 node-2 kernel: [    0.411340] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep  7 19:50:53 node-2 kernel: [    0.411385] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep  7 19:50:53 node-2 kernel: [    0.411388] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep  7 19:50:53 node-2 kernel: [    0.425121] PCI: Using configuration type 1 for base access
Sep  7 19:50:53 node-2 kernel: [    0.426123] bio: create slab <bio-0> at 0
Sep  7 19:50:53 node-2 kernel: [    0.426398] ACPI: Added _OSI(Module Device)
Sep  7 19:50:53 node-2 kernel: [    0.426399] ACPI: Added _OSI(Processor Device)
Sep  7 19:50:53 node-2 kernel: [    0.426400] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep  7 19:50:53 node-2 kernel: [    0.426401] ACPI: Added _OSI(Processor Aggregator Device)
Sep  7 19:50:53 node-2 kernel: [    0.439062] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep  7 19:50:53 node-2 kernel: [    0.449624] ACPI: Interpreter enabled
Sep  7 19:50:53 node-2 kernel: [    0.449630] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep  7 19:50:53 node-2 kernel: [    0.449634] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep  7 19:50:53 node-2 kernel: [    0.449636] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep  7 19:50:53 node-2 kernel: [    0.449643] ACPI: (supports S0 S4 S5)
Sep  7 19:50:53 node-2 kernel: [    0.449645] ACPI: Using IOAPIC for interrupt routing
Sep  7 19:50:53 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep  7 19:50:53 node-2 kernel: [    0.449686] HEST: Table parsing has been initialized.
Sep  7 19:50:53 node-2 kernel: [    0.449689] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep  7 19:50:53 node-2 kernel: [    0.450243] ACPI: No dock devices found.
Sep  7 19:50:53 node-2 kernel: [    0.461876] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep  7 19:50:53 node-2 kernel: [    0.461881] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  7 19:50:53 node-2 kernel: [    0.461884] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep  7 19:50:53 node-2 kernel: [    0.461911] PCI host bridge to bus 0000:ff
Sep  7 19:50:53 node-2 kernel: [    0.461913] pci_bus 0000:ff: root bus resource [bus ff]
Sep  7 19:50:53 node-2 kernel: [    0.461922] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.461960] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.461991] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462026] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462055] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.462085] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.462115] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462144] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462174] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462203] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462229] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462256] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462287] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462313] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462340] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462367] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462396] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462425] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462452] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.462480] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462507] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.462533] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462559] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462590] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.462626] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462657] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462688] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462719] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462750] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462783] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462817] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462850] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462881] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462913] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462945] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.462976] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463011] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463042] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463070] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463103] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463138] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463179] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463216] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463249] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463281] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463310] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463343] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463376] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463411] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463442] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463475] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463505] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463535] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463565] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463595] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463627] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463659] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463717] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep  7 19:50:53 node-2 kernel: [    0.463720] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  7 19:50:53 node-2 kernel: [    0.463723] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep  7 19:50:53 node-2 kernel: [    0.463740] PCI host bridge to bus 0000:7f
Sep  7 19:50:53 node-2 kernel: [    0.463742] pci_bus 0000:7f: root bus resource [bus 7f]
Sep  7 19:50:53 node-2 kernel: [    0.463747] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463774] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.463802] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463831] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463857] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.463882] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.463908] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463934] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463957] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.463979] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464002] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464024] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464048] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464070] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464094] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464120] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464142] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464164] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464187] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.464211] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464236] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.464260] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464285] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464312] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep  7 19:50:53 node-2 kernel: [    0.464346] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464375] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464404] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464432] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464457] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464486] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464514] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464545] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464573] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464602] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464630] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464659] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464686] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464711] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464736] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464764] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464790] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464818] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464849] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464879] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464906] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464931] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464959] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.464987] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.465014] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.465045] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.465075] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.465102] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.465125] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.465152] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.465178] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.465208] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.465235] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.466494] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep  7 19:50:53 node-2 kernel: [    0.466498] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  7 19:50:53 node-2 kernel: [    0.467615] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep  7 19:50:53 node-2 kernel: [    0.468126] PCI host bridge to bus 0000:00
Sep  7 19:50:53 node-2 kernel: [    0.468129] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep  7 19:50:53 node-2 kernel: [    0.468130] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep  7 19:50:53 node-2 kernel: [    0.468132] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep  7 19:50:53 node-2 kernel: [    0.468133] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep  7 19:50:53 node-2 kernel: [    0.468134] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep  7 19:50:53 node-2 kernel: [    0.468136] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep  7 19:50:53 node-2 kernel: [    0.468137] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep  7 19:50:53 node-2 kernel: [    0.468143] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep  7 19:50:53 node-2 kernel: [    0.468226] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.468257] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.468298] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep  7 19:50:53 node-2 kernel: [    0.468319] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.468348] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.468388] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep  7 19:50:53 node-2 kernel: [    0.468408] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.468437] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.468481] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep  7 19:50:53 node-2 kernel: [    0.468499] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.468570] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.468648] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.468725] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep  7 19:50:53 node-2 kernel: [    0.468730] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep  7 19:50:53 node-2 kernel: [    0.468815] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep  7 19:50:53 node-2 kernel: [    0.468952] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep  7 19:50:53 node-2 kernel: [    0.468970] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep  7 19:50:53 node-2 kernel: [    0.469047] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.469101] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep  7 19:50:53 node-2 kernel: [    0.469124] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.469179] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.469222] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep  7 19:50:53 node-2 kernel: [    0.469251] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.469307] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.469350] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep  7 19:50:53 node-2 kernel: [    0.469375] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep  7 19:50:53 node-2 kernel: [    0.469392] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep  7 19:50:53 node-2 kernel: [    0.469470] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.469519] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep  7 19:50:53 node-2 kernel: [    0.469546] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep  7 19:50:53 node-2 kernel: [    0.469797] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep  7 19:50:53 node-2 kernel: [    0.469803] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep  7 19:50:53 node-2 kernel: [    0.469809] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.469815] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.469823] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep  7 19:50:53 node-2 kernel: [    0.469853] pci 0000:01:00.0: supports D1 D2
Sep  7 19:50:53 node-2 kernel: [    0.479857] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep  7 19:50:53 node-2 kernel: [    0.479863] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep  7 19:50:53 node-2 kernel: [    0.479867] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep  7 19:50:53 node-2 kernel: [    0.480014] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.480048] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep  7 19:50:53 node-2 kernel: [    0.487855] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep  7 19:50:53 node-2 kernel: [    0.487861] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.487865] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  7 19:50:53 node-2 kernel: [    0.487951] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.488047] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.488144] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.488230] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep  7 19:50:53 node-2 kernel: [    0.488234] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.488235] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  7 19:50:53 node-2 kernel: [    0.488289] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.488411] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.488464] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep  7 19:50:53 node-2 kernel: [    0.488467] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.488469] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  7 19:50:53 node-2 kernel: [    0.488518] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.488636] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.488676] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.488797] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.488835] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.488955] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.489011] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep  7 19:50:53 node-2 kernel: [    0.489131] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep  7 19:50:53 node-2 kernel: [    0.489174] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep  7 19:50:53 node-2 kernel: [    0.489177] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.489179] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  7 19:50:53 node-2 kernel: [    0.489239] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep  7 19:50:53 node-2 kernel: [    0.489302] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.489370] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.489412] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep  7 19:50:53 node-2 kernel: [    0.489493] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep  7 19:50:53 node-2 kernel: [    0.489600] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep  7 19:50:53 node-2 kernel: [    0.489602] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.489604] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep  7 19:50:53 node-2 kernel: [    0.489660] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep  7 19:50:53 node-2 kernel: [    0.489713] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.489764] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.489977] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep  7 19:50:53 node-2 kernel: [    0.489981] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep  7 19:50:53 node-2 kernel: [    0.490065] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep  7 19:50:53 node-2 kernel: [    0.490122] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.490171] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.490383] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep  7 19:50:53 node-2 kernel: [    0.490387] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep  7 19:50:53 node-2 kernel: [    0.490446] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep  7 19:50:53 node-2 kernel: [    0.490506] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.490558] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep  7 19:50:53 node-2 kernel: [    0.490780] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep  7 19:50:53 node-2 kernel: [    0.490783] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep  7 19:50:53 node-2 kernel: [    0.490961] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep  7 19:50:53 node-2 kernel: [    0.490999] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep  7 19:50:53 node-2 kernel: [    0.491073] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep  7 19:50:53 node-2 kernel: [    0.491092] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep  7 19:50:53 node-2 kernel: [    0.491105] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep  7 19:50:53 node-2 kernel: [    0.491118] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep  7 19:50:53 node-2 kernel: [    0.491168] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep  7 19:50:53 node-2 kernel: [    0.495862] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep  7 19:50:53 node-2 kernel: [    0.495871] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep  7 19:50:53 node-2 kernel: [    0.495924] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep  7 19:50:53 node-2 kernel: [    0.496458] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep  7 19:50:53 node-2 kernel: [    0.496461] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep  7 19:50:53 node-2 kernel: [    0.496585] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep  7 19:50:53 node-2 kernel: [    0.496690] PCI host bridge to bus 0000:80
Sep  7 19:50:53 node-2 kernel: [    0.496692] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep  7 19:50:53 node-2 kernel: [    0.496694] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep  7 19:50:53 node-2 kernel: [    0.496695] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep  7 19:50:53 node-2 kernel: [    0.496703] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.496767] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.496834] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep  7 19:50:53 node-2 kernel: [    0.496895] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep  7 19:50:53 node-2 kernel: [    0.496901] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep  7 19:50:53 node-2 kernel: [    0.496972] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep  7 19:50:53 node-2 kernel: [    0.497273] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep  7 19:50:53 node-2 kernel: [    0.497304] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep  7 19:50:53 node-2 kernel: [    0.497334] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep  7 19:50:53 node-2 kernel: [    0.497364] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep  7 19:50:53 node-2 kernel: [    0.497393] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  7 19:50:53 node-2 kernel: [    0.497423] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  7 19:50:53 node-2 kernel: [    0.497453] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  7 19:50:53 node-2 kernel: [    0.497483] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep  7 19:50:53 node-2 kernel: [    0.497568] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep  7 19:50:53 node-2 kernel: [    0.497573] ACPI: \_SB_.UNC1: notify handler is installed
Sep  7 19:50:53 node-2 kernel: [    0.497574] ACPI: \_SB_.UNC0: notify handler is installed
Sep  7 19:50:53 node-2 kernel: [    0.497589] ACPI: \_SB_.PCI0: notify handler is installed
Sep  7 19:50:53 node-2 kernel: [    0.497642] ACPI: \_SB_.PCI1: notify handler is installed
Sep  7 19:50:53 node-2 kernel: [    0.497721] Found 4 acpi root devices
Sep  7 19:50:53 node-2 kernel: [    0.497832] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep  7 19:50:53 node-2 kernel: [    0.497834] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep  7 19:50:53 node-2 kernel: [    0.497835] vgaarb: loaded
Sep  7 19:50:53 node-2 kernel: [    0.497836] vgaarb: bridge control possible 0000:0c:00.0
Sep  7 19:50:53 node-2 kernel: [    0.497960] SCSI subsystem initialized
Sep  7 19:50:53 node-2 kernel: [    0.498024] libata version 3.00 loaded.
Sep  7 19:50:53 node-2 kernel: [    0.498039] ACPI: bus type USB registered
Sep  7 19:50:53 node-2 kernel: [    0.498050] usbcore: registered new interface driver usbfs
Sep  7 19:50:53 node-2 kernel: [    0.498055] usbcore: registered new interface driver hub
Sep  7 19:50:53 node-2 kernel: [    0.498079] usbcore: registered new device driver usb
Sep  7 19:50:53 node-2 kernel: [    0.498250] PCI: Using ACPI for IRQ routing
Sep  7 19:50:53 node-2 kernel: [    0.501831] PCI: pci_cache_line_size set to 64 bytes
Sep  7 19:50:53 node-2 kernel: [    0.502049] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep  7 19:50:53 node-2 kernel: [    0.502050] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep  7 19:50:53 node-2 kernel: [    0.502051] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep  7 19:50:53 node-2 kernel: [    0.502117] NetLabel: Initializing
Sep  7 19:50:53 node-2 kernel: [    0.502118] NetLabel:  domain hash size = 128
Sep  7 19:50:53 node-2 kernel: [    0.502119] NetLabel:  protocols = UNLABELED CIPSOv4
Sep  7 19:50:53 node-2 kernel: [    0.502129] NetLabel:  unlabeled traffic allowed by default
Sep  7 19:50:53 node-2 kernel: [    0.502186] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep  7 19:50:53 node-2 kernel: [    0.502190] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep  7 19:50:53 node-2 kernel: [    0.504248] Switched to clocksource hpet
Sep  7 19:50:53 node-2 kernel: [    0.508228] AppArmor: AppArmor Filesystem Enabled
Sep  7 19:50:53 node-2 kernel: [    0.508246] pnp: PnP ACPI init
Sep  7 19:50:53 node-2 kernel: [    0.508253] ACPI: bus type PNP registered
Sep  7 19:50:53 node-2 kernel: [    0.508362] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep  7 19:50:53 node-2 kernel: [    0.508370] pnp 00:01: [dma 4]
Sep  7 19:50:53 node-2 kernel: [    0.508382] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep  7 19:50:53 node-2 kernel: [    0.508408] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep  7 19:50:53 node-2 kernel: [    0.508428] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep  7 19:50:53 node-2 kernel: [    0.508446] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep  7 19:50:53 node-2 kernel: [    0.508479] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep  7 19:50:53 node-2 kernel: [    0.508534] system 00:06: [io  0x0500-0x057f] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508536] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep  7 19:50:53 node-2 kernel: [    0.508538] system 00:06: [io  0x0580-0x059f] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508539] system 00:06: [io  0x0600-0x061f] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508541] system 00:06: [io  0x0880-0x0883] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508545] system 00:06: [io  0x0800-0x081f] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508547] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep  7 19:50:53 node-2 kernel: [    0.508549] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508550] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508552] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508553] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508555] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508556] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep  7 19:50:53 node-2 kernel: [    0.508558] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep  7 19:50:53 node-2 kernel: [    0.508644] pnp 00:07: [dma 0 disabled]
Sep  7 19:50:53 node-2 kernel: [    0.508672] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep  7 19:50:53 node-2 kernel: [    0.508747] pnp 00:08: [dma 0 disabled]
Sep  7 19:50:53 node-2 kernel: [    0.508779] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep  7 19:50:53 node-2 kernel: [    0.508830] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep  7 19:50:53 node-2 kernel: [    0.509180] pnp: PnP ACPI: found 10 devices
Sep  7 19:50:53 node-2 kernel: [    0.509181] ACPI: bus type PNP unregistered
Sep  7 19:50:53 node-2 kernel: [    0.515453] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep  7 19:50:53 node-2 kernel: [    0.515456] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep  7 19:50:53 node-2 kernel: [    0.515459] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep  7 19:50:53 node-2 kernel: [    0.515463] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep  7 19:50:53 node-2 kernel: [    0.515465] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.515479] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515509] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep  7 19:50:53 node-2 kernel: [    0.515523] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515552] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep  7 19:50:53 node-2 kernel: [    0.515567] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep  7 19:50:53 node-2 kernel: [    0.515596] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep  7 19:50:53 node-2 kernel: [    0.515610] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep  7 19:50:53 node-2 kernel: [    0.515639] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep  7 19:50:53 node-2 kernel: [    0.515641] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.515656] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515684] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep  7 19:50:53 node-2 kernel: [    0.515686] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.515701] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515730] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep  7 19:50:53 node-2 kernel: [    0.515731] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.515734] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515738] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep  7 19:50:53 node-2 kernel: [    0.515740] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.515742] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515746] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep  7 19:50:53 node-2 kernel: [    0.515751] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep  7 19:50:53 node-2 kernel: [    0.515758] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep  7 19:50:53 node-2 kernel: [    0.515762] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep  7 19:50:53 node-2 kernel: [    0.515768] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep  7 19:50:53 node-2 kernel: [    0.515769] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep  7 19:50:53 node-2 kernel: [    0.515770] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep  7 19:50:53 node-2 kernel: [    0.515771] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep  7 19:50:53 node-2 kernel: [    0.515772] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep  7 19:50:53 node-2 kernel: [    0.515773] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep  7 19:50:53 node-2 kernel: [    0.515774] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep  7 19:50:53 node-2 kernel: [    0.515774] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep  7 19:50:53 node-2 kernel: [    0.515775] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.515776] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515777] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.515778] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515779] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.515780] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515781] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.515782] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515783] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep  7 19:50:53 node-2 kernel: [    0.515783] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515784] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep  7 19:50:53 node-2 kernel: [    0.515785] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep  7 19:50:53 node-2 kernel: [    0.515786] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep  7 19:50:53 node-2 kernel: [    0.515787] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep  7 19:50:53 node-2 kernel: [    0.515789] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep  7 19:50:53 node-2 kernel: [    0.515790] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep  7 19:50:53 node-2 kernel: [    0.515828] NET: Registered protocol family 2
Sep  7 19:50:53 node-2 kernel: [    0.516090] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.516426] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.516569] TCP: Hash tables configured (established 262144 bind 65536)
Sep  7 19:50:53 node-2 kernel: [    0.516605] TCP: reno registered
Sep  7 19:50:53 node-2 kernel: [    0.516633] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.516729] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.516879] NET: Registered protocol family 1
Sep  7 19:50:53 node-2 kernel: [    0.556350] pci 0000:0c:00.0: Video device with shadowed ROM
Sep  7 19:50:53 node-2 kernel: [    0.556372] PCI: CLS 64 bytes, default 64
Sep  7 19:50:53 node-2 kernel: [    0.556413] Trying to unpack rootfs image as initramfs...
Sep  7 19:50:53 node-2 kernel: [    0.776659] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep  7 19:50:53 node-2 kernel: [    0.776694] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep  7 19:50:53 node-2 kernel: [    0.776696] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep  7 19:50:53 node-2 kernel: [    0.777097] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777103] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777108] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777113] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777122] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777132] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777140] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777148] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777156] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777164] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777170] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777177] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777183] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777191] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777197] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777204] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep  7 19:50:53 node-2 kernel: [    0.777242] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep  7 19:50:53 node-2 kernel: [    0.777246] Scanning for low memory corruption every 60 seconds
Sep  7 19:50:53 node-2 kernel: [    0.777532] Initialise system trusted keyring
Sep  7 19:50:53 node-2 kernel: [    0.777576] audit: initializing netlink socket (disabled)
Sep  7 19:50:53 node-2 kernel: [    0.777585] type=2000 audit(1473277817.732:1): initialized
Sep  7 19:50:53 node-2 kernel: [    0.795356] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep  7 19:50:53 node-2 kernel: [    0.796795] zbud: loaded
Sep  7 19:50:53 node-2 kernel: [    0.796907] VFS: Disk quotas dquot_6.5.2
Sep  7 19:50:53 node-2 kernel: [    0.796949] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep  7 19:50:53 node-2 kernel: [    0.797321] fuse init (API version 7.22)
Sep  7 19:50:53 node-2 kernel: [    0.797377] msgmni has been set to 32768
Sep  7 19:50:53 node-2 kernel: [    0.797421] Key type big_key registered
Sep  7 19:50:53 node-2 kernel: [    0.797926] Key type asymmetric registered
Sep  7 19:50:53 node-2 kernel: [    0.797927] Asymmetric key parser 'x509' registered
Sep  7 19:50:53 node-2 kernel: [    0.797950] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep  7 19:50:53 node-2 kernel: [    0.798008] io scheduler noop registered
Sep  7 19:50:53 node-2 kernel: [    0.798010] io scheduler deadline registered (default)
Sep  7 19:50:53 node-2 kernel: [    0.798026] io scheduler cfq registered
Sep  7 19:50:53 node-2 kernel: [    0.798330] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    0.798421] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    0.798507] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    0.798593] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    0.798688] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    0.798754] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    0.799022] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep  7 19:50:53 node-2 kernel: [    0.799041] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep  7 19:50:53 node-2 kernel: [    0.799053] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep  7 19:50:53 node-2 kernel: [    0.799063] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799065] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799067] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep  7 19:50:53 node-2 kernel: [    0.799071] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799073] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799074] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799075] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799076] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799078] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799079] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799081] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799082] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799084] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799085] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799087] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799089] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep  7 19:50:53 node-2 kernel: [    0.799092] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799095] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep  7 19:50:53 node-2 kernel: [    0.799103] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799106] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep  7 19:50:53 node-2 kernel: [    0.799115] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799117] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep  7 19:50:53 node-2 kernel: [    0.799120] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep  7 19:50:53 node-2 kernel: [    0.799132] ioapic: probe of 0000:00:05.4 failed with error -22
Sep  7 19:50:53 node-2 kernel: [    0.799219] ioapic: probe of 0000:80:05.4 failed with error -22
Sep  7 19:50:53 node-2 kernel: [    0.799223] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep  7 19:50:53 node-2 kernel: [    0.799232] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep  7 19:50:53 node-2 kernel: [    0.799267] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep  7 19:50:53 node-2 kernel: [    0.799268] vesafb: scrolling: redraw
Sep  7 19:50:53 node-2 kernel: [    0.799270] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep  7 19:50:53 node-2 kernel: [    0.819529] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep  7 19:50:53 node-2 kernel: [    0.828040] Console: switching to colour frame buffer device 80x30
Sep  7 19:50:53 node-2 kernel: [    0.836731] fb0: VESA VGA frame buffer device
Sep  7 19:50:53 node-2 kernel: [    0.836929] intel_idle: MWAIT substates: 0x2120
Sep  7 19:50:53 node-2 kernel: [    0.836930] intel_idle: v0.4 model 0x3F
Sep  7 19:50:53 node-2 kernel: [    0.836931] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep  7 19:50:53 node-2 kernel: [    0.837164] ipmi message handler version 39.2
Sep  7 19:50:53 node-2 kernel: [    0.837419] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep  7 19:50:53 node-2 kernel: [    0.837850] ACPI: AC Adapter [P111] (on-line)
Sep  7 19:50:53 node-2 kernel: [    0.843095] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep  7 19:50:53 node-2 kernel: [    0.854138] ACPI: Power Button [PWRB]
Sep  7 19:50:53 node-2 kernel: [    0.859968] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep  7 19:50:53 node-2 kernel: [    0.871734] ACPI: Power Button [PWRF]
Sep  7 19:50:53 node-2 kernel: [    0.897927] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep  7 19:50:53 node-2 kernel: [    0.909734] pstore: Registered erst as persistent store backend
Sep  7 19:50:53 node-2 kernel: [    0.916066] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep  7 19:50:53 node-2 kernel: [    0.928149] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep  7 19:50:53 node-2 kernel: [    0.954908] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep  7 19:50:53 node-2 kernel: [    0.988210] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep  7 19:50:53 node-2 kernel: [    1.002310] Linux agpgart interface v0.103
Sep  7 19:50:53 node-2 kernel: [    1.009999] brd: module loaded
Sep  7 19:50:53 node-2 kernel: [    1.017064] loop: module loaded
Sep  7 19:50:53 node-2 kernel: [    1.023777] libphy: Fixed MDIO Bus: probed
Sep  7 19:50:53 node-2 kernel: [    1.030245] tun: Universal TUN/TAP device driver, 1.6
Sep  7 19:50:53 node-2 kernel: [    1.036719] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep  7 19:50:53 node-2 kernel: [    1.043245] PPP generic driver version 2.4.2
Sep  7 19:50:53 node-2 kernel: [    1.049627] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep  7 19:50:53 node-2 kernel: [    1.056060] ehci-pci: EHCI PCI platform driver
Sep  7 19:50:53 node-2 kernel: [    1.062644] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep  7 19:50:53 node-2 kernel: [    1.069052] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep  7 19:50:53 node-2 kernel: [    1.081574] ehci-pci 0000:00:1a.0: debug port 2
Sep  7 19:50:53 node-2 kernel: [    1.091776] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep  7 19:50:53 node-2 kernel: [    1.091793] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep  7 19:50:53 node-2 kernel: [    1.107742] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep  7 19:50:53 node-2 kernel: [    1.113808] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep  7 19:50:53 node-2 kernel: [    1.119969] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  7 19:50:53 node-2 kernel: [    1.131866] usb usb1: Product: EHCI Host Controller
Sep  7 19:50:53 node-2 kernel: [    1.137896] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep  7 19:50:53 node-2 kernel: [    1.143932] usb usb1: SerialNumber: 0000:00:1a.0
Sep  7 19:50:53 node-2 kernel: [    1.149879] hub 1-0:1.0: USB hub found
Sep  7 19:50:53 node-2 kernel: [    1.155638] hub 1-0:1.0: 2 ports detected
Sep  7 19:50:53 node-2 kernel: [    1.161415] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep  7 19:50:53 node-2 kernel: [    1.166985] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep  7 19:50:53 node-2 kernel: [    1.177843] ehci-pci 0000:00:1d.0: debug port 2
Sep  7 19:50:53 node-2 kernel: [    1.187120] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep  7 19:50:53 node-2 kernel: [    1.187123] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep  7 19:50:53 node-2 kernel: [    1.203660] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep  7 19:50:53 node-2 kernel: [    1.208847] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep  7 19:50:53 node-2 kernel: [    1.214139] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep  7 19:50:53 node-2 kernel: [    1.224712] usb usb2: Product: EHCI Host Controller
Sep  7 19:50:53 node-2 kernel: [    1.230182] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep  7 19:50:53 node-2 kernel: [    1.235721] usb usb2: SerialNumber: 0000:00:1d.0
Sep  7 19:50:53 node-2 kernel: [    1.241228] hub 2-0:1.0: USB hub found
Sep  7 19:50:53 node-2 kernel: [    1.246564] hub 2-0:1.0: 2 ports detected
Sep  7 19:50:53 node-2 kernel: [    1.251853] ehci-platform: EHCI generic platform driver
Sep  7 19:50:53 node-2 kernel: [    1.257072] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep  7 19:50:53 node-2 kernel: [    1.262370] ohci-pci: OHCI PCI platform driver
Sep  7 19:50:53 node-2 kernel: [    1.267662] ohci-platform: OHCI generic platform driver
Sep  7 19:50:53 node-2 kernel: [    1.272844] uhci_hcd: USB Universal Host Controller Interface driver
Sep  7 19:50:53 node-2 kernel: [    1.278167] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep  7 19:50:53 node-2 kernel: [    1.471442] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep  7 19:50:53 node-2 kernel: [    1.631700] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep  7 19:50:53 node-2 kernel: [    1.637193] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep  7 19:50:53 node-2 kernel: [    1.642964] hub 1-1:1.0: USB hub found
Sep  7 19:50:53 node-2 kernel: [    1.648436] hub 1-1:1.0: 6 ports detected
Sep  7 19:50:53 node-2 kernel: [    1.763183] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep  7 19:50:53 node-2 kernel: [    1.775268] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep  7 19:50:53 node-2 kernel: [    2.031362] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep  7 19:50:53 node-2 kernel: [    2.036900] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep  7 19:50:53 node-2 kernel: [    2.042750] hub 2-1:1.0: USB hub found
Sep  7 19:50:53 node-2 kernel: [    2.048347] hub 2-1:1.0: 8 ports detected
Sep  7 19:50:53 node-2 kernel: [    2.319585] i8042: No controller found
Sep  7 19:50:53 node-2 kernel: [    2.324996] mousedev: PS/2 mouse device common for all mice
Sep  7 19:50:53 node-2 kernel: [    2.326785] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep  7 19:50:53 node-2 kernel: [    2.336127] rtc_cmos 00:02: RTC can wake from S4
Sep  7 19:50:53 node-2 kernel: [    2.341877] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep  7 19:50:53 node-2 kernel: [    2.347522] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep  7 19:50:53 node-2 kernel: [    2.358654] device-mapper: uevent: version 1.0.3
Sep  7 19:50:53 node-2 kernel: [    2.364292] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep  7 19:50:53 node-2 kernel: [    2.375495] ledtrig-cpu: registered to indicate activity on CPUs
Sep  7 19:50:53 node-2 kernel: [    2.381412] TCP: cubic registered
Sep  7 19:50:53 node-2 kernel: [    2.387290] NET: Registered protocol family 10
Sep  7 19:50:53 node-2 kernel: [    2.393242] NET: Registered protocol family 17
Sep  7 19:50:53 node-2 kernel: [    2.398907] Key type dns_resolver registered
Sep  7 19:50:53 node-2 kernel: [    2.404884] Loading compiled-in X.509 certificates
Sep  7 19:50:53 node-2 kernel: [    2.411077] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep  7 19:50:53 node-2 kernel: [    2.422490] registered taskstats version 1
Sep  7 19:50:53 node-2 kernel: [    2.430440] Key type trusted registered
Sep  7 19:50:53 node-2 kernel: [    2.437961] Key type encrypted registered
Sep  7 19:50:53 node-2 kernel: [    2.443417] AppArmor: AppArmor sha1 policy hashing enabled
Sep  7 19:50:53 node-2 kernel: [    2.448908] IMA: No TPM chip found, activating TPM-bypass!
Sep  7 19:50:53 node-2 kernel: [    2.455041] regulator-dummy: disabling
Sep  7 19:50:53 node-2 kernel: [    2.459561] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep  7 19:50:53 node-2 kernel: [    2.459562] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep  7 19:50:53 node-2 kernel: [    2.459562] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep  7 19:50:53 node-2 kernel: [    2.459563] usb 2-1.4: Manufacturer: Avocent
Sep  7 19:50:53 node-2 kernel: [    2.459564] usb 2-1.4: SerialNumber: 20111102-00000001
Sep  7 19:50:53 node-2 kernel: [    2.494332]   Magic number: 0:348:849
Sep  7 19:50:53 node-2 kernel: [    2.499915] graphics fbcon: hash matches
Sep  7 19:50:53 node-2 kernel: [    2.505410] pci 0000:ff:16.7: hash matches
Sep  7 19:50:53 node-2 kernel: [    2.510918] processor cpu13: hash matches
Sep  7 19:50:53 node-2 kernel: [    2.516374] rtc_cmos 00:02: setting system clock to 2016-09-07 19:50:19 UTC (1473277819)
Sep  7 19:50:53 node-2 kernel: [    2.528742] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep  7 19:50:53 node-2 kernel: [    2.534281] EDD information not available.
Sep  7 19:50:53 node-2 kernel: [    2.539781] PM: Hibernation image not present or could not be loaded.
Sep  7 19:50:53 node-2 kernel: [    2.540656] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep  7 19:50:53 node-2 kernel: [    2.551567] Write protecting the kernel read-only data: 12288k
Sep  7 19:50:53 node-2 kernel: [    2.557607] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep  7 19:50:53 node-2 kernel: [    2.570133] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep  7 19:50:53 node-2 kernel: [    2.602142] device-mapper: multipath: version 1.6.0 loaded
Sep  7 19:50:53 node-2 kernel: [    2.609896] systemd-udevd[216]: starting version 204
Sep  7 19:50:53 node-2 kernel: [    2.634575] md: linear personality registered for level -1
Sep  7 19:50:53 node-2 kernel: [    2.649370] md: multipath personality registered for level -4
Sep  7 19:50:53 node-2 kernel: [    2.657309] md: raid0 personality registered for level 0
Sep  7 19:50:53 node-2 kernel: [    2.665725] md: raid1 personality registered for level 1
Sep  7 19:50:53 node-2 kernel: [    2.673583] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep  7 19:50:53 node-2 kernel: [    2.679793] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep  7 19:50:53 node-2 kernel: [    2.685974] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep  7 19:50:53 node-2 kernel: [    2.686663] megasas: FW now in Ready state
Sep  7 19:50:53 node-2 kernel: [    2.686745] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.686789] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.686838] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.686874] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.686911] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.686946] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.686980] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.687031] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.687067] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.687108] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.687146] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.687183] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.687232] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.687275] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.687313] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.687351] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.687519] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep  7 19:50:53 node-2 kernel: [    2.710679] hidraw: raw HID events driver (C) Jiri Kosina
Sep  7 19:50:53 node-2 kernel: [    2.718975] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep  7 19:50:53 node-2 kernel: [    2.732158] 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
Sep  7 19:50:53 node-2 kernel: [    2.746018] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  7 19:50:53 node-2 kernel: [    2.750414] raid6: sse2x1    6175 MB/s
Sep  7 19:50:53 node-2 kernel: [    2.759855] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.759861] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.759866] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.759871] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.759915] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  7 19:50:53 node-2 kernel: [    2.774309] usbcore: registered new interface driver usbhid
Sep  7 19:50:53 node-2 kernel: [    2.781133] usbhid: USB HID core driver
Sep  7 19:50:53 node-2 kernel: [    2.782858] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep  7 19:50:53 node-2 kernel: [    2.782859] 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
Sep  7 19:50:53 node-2 kernel: [    2.782861] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  7 19:50:53 node-2 kernel: [    2.818540] raid6: sse2x2    4892 MB/s
Sep  7 19:50:53 node-2 kernel: [    2.886239] raid6: sse2x4    9329 MB/s
Sep  7 19:50:53 node-2 kernel: [    2.958179] raid6: avx2x1   14943 MB/s
Sep  7 19:50:53 node-2 kernel: [    3.030115] raid6: avx2x2   18859 MB/s
Sep  7 19:50:53 node-2 kernel: [    3.102054] raid6: avx2x4   21354 MB/s
Sep  7 19:50:53 node-2 kernel: [    3.108126] raid6: using algorithm avx2x4 (21354 MB/s)
Sep  7 19:50:53 node-2 kernel: [    3.114228] raid6: using avx2x2 recovery algorithm
Sep  7 19:50:53 node-2 kernel: [    3.120398] megasas:IOC Init cmd success
Sep  7 19:50:53 node-2 kernel: [    3.120400] Switched to clocksource tsc
Sep  7 19:50:53 node-2 kernel: [    3.120584] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.120742] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.120910] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.121026] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.121266] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.133607] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep  7 19:50:53 node-2 kernel: [    3.133614] 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
Sep  7 19:50:53 node-2 kernel: [    3.133615] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  7 19:50:53 node-2 kernel: [    3.133740] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.133869] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.133953] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.134077] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.134429] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.150093] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep  7 19:50:53 node-2 kernel: [    3.150134] 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
Sep  7 19:50:53 node-2 kernel: [    3.150153] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep  7 19:50:53 node-2 kernel: [    3.150328] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.150420] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.150534] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.150696] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.150891] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep  7 19:50:53 node-2 kernel: [    3.231828] xor: automatically using best checksumming function:
Sep  7 19:50:53 node-2 kernel: [    3.238129] 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
Sep  7 19:50:53 node-2 kernel: [    3.250376] 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
Sep  7 19:50:53 node-2 kernel: [    3.254007] megasas: INIT adapter done
Sep  7 19:50:53 node-2 kernel: [    3.269147] 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
Sep  7 19:50:53 node-2 kernel: [    3.277975]    avx       : 35725.000 MB/sec
Sep  7 19:50:53 node-2 kernel: [    3.289516] 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
Sep  7 19:50:53 node-2 kernel: [    3.303934] async_tx: api initialized (async)
Sep  7 19:50:53 node-2 kernel: [    3.304094] 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
Sep  7 19:50:53 node-2 kernel: [    3.304627] 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
Sep  7 19:50:53 node-2 kernel: [    3.325904] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep  7 19:50:53 node-2 kernel: [    3.326333] scsi0 : LSI SAS based MegaRAID driver
Sep  7 19:50:53 node-2 kernel: [    3.333433] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep  7 19:50:53 node-2 kernel: [    3.344622] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep  7 19:50:53 node-2 kernel: [    3.348848] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep  7 19:50:53 node-2 kernel: [    3.348898] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep  7 19:50:53 node-2 kernel: [    3.349226] sd 0:2:0:0: [sda] Write Protect is off
Sep  7 19:50:53 node-2 kernel: [    3.349227] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep  7 19:50:53 node-2 kernel: [    3.349281] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep  7 19:50:53 node-2 kernel: [    3.380944]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep  7 19:50:53 node-2 kernel: [    3.381520] sd 0:2:0:0: [sda] Attached SCSI disk
Sep  7 19:50:53 node-2 kernel: [    3.446409] md: raid6 personality registered for level 6
Sep  7 19:50:53 node-2 kernel: [    3.453525] md: raid5 personality registered for level 5
Sep  7 19:50:53 node-2 kernel: [    3.460387] md: raid4 personality registered for level 4
Sep  7 19:50:53 node-2 kernel: [    3.470113] md: raid10 personality registered for level 10
Sep  7 19:50:53 node-2 kernel: [    3.523372] multipathd (359): /proc/359/oom_adj is deprecated, please use /proc/359/oom_score_adj instead.
Sep  7 19:50:53 node-2 kernel: [    3.573868] random: lvm urandom read with 29 bits of entropy available
Sep  7 19:50:53 node-2 kernel: [    3.722768] bio: create slab <bio-1> at 1
Sep  7 19:50:53 node-2 kernel: [    4.425929] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep  7 19:50:53 node-2 kernel: [    5.164002] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep  7 19:50:53 node-2 kernel: [    5.213741] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep  7 19:50:53 node-2 kernel: [    5.413467] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep  7 19:50:53 node-2 kernel: [    5.461319] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep  7 19:50:53 node-2 kernel: [    5.504514] random: nonblocking pool is initialized
Sep  7 19:50:53 node-2 kernel: [    5.537446] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep  7 19:50:53 node-2 kernel: [    5.701789] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep  7 19:50:53 node-2 kernel: [    5.777799] XFS (dm-0): Mounting Filesystem
Sep  7 19:50:53 node-2 kernel: [    6.030951] XFS (dm-0): Ending clean mount
Sep  7 19:50:53 node-2 kernel: [    6.068353] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep  7 19:50:53 node-2 kernel: [    6.121858] XFS (dm-1): Mounting Filesystem
Sep  7 19:50:53 node-2 kernel: [    6.209739] XFS (dm-1): Ending clean mount
Sep  7 19:50:53 node-2 kernel: [    8.025746] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep  7 19:50:53 node-2 kernel: [    8.053110] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep  7 19:50:53 node-2 kernel: [    8.181326] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep  7 19:50:53 node-2 kernel: [    8.181331] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep  7 19:50:53 node-2 kernel: [    8.181334] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep  7 19:50:53 node-2 kernel: [    8.181338] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep  7 19:50:53 node-2 kernel: [    8.215882] systemd-udevd[773]: starting version 204
Sep  7 19:50:53 node-2 kernel: [    8.419861] power_meter ACPI000D:00: Found ACPI power meter.
Sep  7 19:50:53 node-2 kernel: [    8.419911] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep  7 19:50:53 node-2 kernel: [    8.438967] IPMI System Interface driver.
Sep  7 19:50:53 node-2 kernel: [    8.439049] ipmi_si: probing via ACPI
Sep  7 19:50:53 node-2 kernel: [    8.439064] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep  7 19:50:53 node-2 kernel: [    8.439065] ipmi_si: Adding ACPI-specified kcs state machine
Sep  7 19:50:53 node-2 kernel: [    8.439083] ipmi_si: probing via SMBIOS
Sep  7 19:50:53 node-2 kernel: [    8.439084] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep  7 19:50:53 node-2 kernel: [    8.439085] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep  7 19:50:53 node-2 kernel: [    8.439087] ipmi_si: probing via SPMI
Sep  7 19:50:53 node-2 kernel: [    8.439088] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep  7 19:50:53 node-2 kernel: [    8.439089] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep  7 19:50:53 node-2 kernel: [    8.439091] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep  7 19:50:53 node-2 kernel: [    8.453403] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep  7 19:50:53 node-2 kernel: [    8.453411] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep  7 19:50:53 node-2 kernel: [    8.453414] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep  7 19:50:53 node-2 kernel: [    8.453417] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep  7 19:50:53 node-2 kernel: [    8.453444] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep  7 19:50:53 node-2 kernel: [    8.454999] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep  7 19:50:53 node-2 kernel: [    8.458480] wmi: Mapper loaded
Sep  7 19:50:53 node-2 kernel: [    8.537936] systemd-udevd[797]: renamed network interface eth2 to enp8s0
Sep  7 19:50:53 node-2 kernel: [    8.565836] systemd-udevd[791]: renamed network interface eth1 to enp7s0
Sep  7 19:50:53 node-2 kernel: [    8.580801] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep  7 19:50:53 node-2 kernel: [    8.580806] ipmi_si 00:09: IPMI kcs interface initialized
Sep  7 19:50:53 node-2 kernel: [    8.601788] systemd-udevd[815]: renamed network interface eth0 to enp6s0
Sep  7 19:50:53 node-2 kernel: [    8.625823] systemd-udevd[792]: renamed network interface eth3 to enp9s0
Sep  7 19:50:53 node-2 kernel: [    8.911697] type=1400 audit(1473277825.897:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1043 comm="apparmor_parser"
Sep  7 19:50:53 node-2 kernel: [    8.911782] type=1400 audit(1473277825.897:3): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1048 comm="apparmor_parser"
Sep  7 19:50:53 node-2 kernel: [    8.911848] type=1400 audit(1473277825.897:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1043 comm="apparmor_parser"
Sep  7 19:50:53 node-2 kernel: [    8.911931] type=1400 audit(1473277825.897:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1048 comm="apparmor_parser"
Sep  7 19:50:53 node-2 kernel: [    8.911981] type=1400 audit(1473277825.897:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1043 comm="apparmor_parser"
Sep  7 19:50:53 node-2 kernel: [    8.912055] type=1400 audit(1473277825.897:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1048 comm="apparmor_parser"
Sep  7 19:50:53 node-2 kernel: [    8.914460] type=1400 audit(1473277825.901:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1046 comm="apparmor_parser"
Sep  7 19:50:53 node-2 kernel: [    8.914607] type=1400 audit(1473277825.901:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1046 comm="apparmor_parser"
Sep  7 19:50:53 node-2 kernel: [    8.914726] type=1400 audit(1473277825.901:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1046 comm="apparmor_parser"
Sep  7 19:50:53 node-2 kernel: [    8.981301] type=1400 audit(1473277825.969:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1044 comm="apparmor_parser"
Sep  7 19:50:53 node-2 kernel: [    9.406795] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep  7 19:50:53 node-2 kernel: [    9.415294] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep  7 19:50:53 node-2 kernel: [    9.644950] enic 0000:06:00.0 enp6s0: Link UP
Sep  7 19:50:53 node-2 kernel: [    9.646078] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep  7 19:50:53 node-2 kernel: [    9.646083] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep  7 19:50:53 node-2 kernel: [   19.316854] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep  7 19:50:54 node-2 failsafe: Failsafe of 120 seconds reached.
Sep  7 19:50:54 node-2 kernel: [   37.381290] init: failsafe main process (8406) killed by TERM signal
Sep  7 19:50:54 node-2 dbus[8430]: [system] AppArmor D-Bus mediation is enabled
Sep  7 19:50:55 node-2 kernel: [   37.592424] audit_printk_skb: 30 callbacks suppressed
Sep  7 19:50:55 node-2 kernel: [   37.592425] type=1400 audit(1473277855.081:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8531 comm="apparmor_parser"
Sep  7 19:50:55 node-2 kernel: [   37.592430] type=1400 audit(1473277855.081:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8531 comm="apparmor_parser"
Sep  7 19:50:55 node-2 kernel: [   37.592444] type=1400 audit(1473277855.081:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8531 comm="apparmor_parser"
Sep  7 19:50:55 node-2 kernel: [   37.592670] type=1400 audit(1473277855.081:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8531 comm="apparmor_parser"
Sep  7 19:50:55 node-2 kernel: [   37.592672] type=1400 audit(1473277855.081:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8531 comm="apparmor_parser"
Sep  7 19:50:55 node-2 kernel: [   37.592788] type=1400 audit(1473277855.081:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8531 comm="apparmor_parser"
Sep  7 19:50:55 node-2 kernel: [   37.597154] type=1400 audit(1473277855.085:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8532 comm="apparmor_parser"
Sep  7 19:50:55 node-2 kernel: [   37.667612] type=1400 audit(1473277855.153:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8534 comm="apparmor_parser"
Sep  7 19:50:55 node-2 cron[8564]: (CRON) INFO (pidfile fd = 3)
Sep  7 19:50:55 node-2 anacron[8582]: Anacron 2.3 started on 2016-09-07
Sep  7 19:50:55 node-2 cron[8602]: (CRON) STARTUP (fork ok)
Sep  7 19:50:55 node-2 multipathd: path checkers start up
Sep  7 19:50:55 node-2 anacron[8582]: Will run job `cron.daily' in 5 min.
Sep  7 19:50:55 node-2 anacron[8582]: Will run job `cron.weekly' in 10 min.
Sep  7 19:50:55 node-2 anacron[8582]: Will run job `cron.monthly' in 15 min.
Sep  7 19:50:55 node-2 anacron[8582]: Jobs will be executed sequentially
Sep  7 19:50:55 node-2 cron[8602]: (CRON) INFO (Running @reboot jobs)
Sep  7 19:50:55 node-2 postfix/master[8743]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep  7 19:50:58 node-2 puppet-agent[9057]: Reopening log files
Sep  7 19:50:59 node-2 puppet-agent[9057]: Could not request certificate: Connection refused - connect(2)
Sep  7 19:51:01 node-2 CRON[9088]: (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")
Sep  7 19:51:12 node-2 puppet-user[9327]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep  7 19:51:12 node-2 puppet-user[9327]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep  7 19:51:13 node-2 puppet-user[9327]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep  7 19:51:13 node-2 puppet-user[9327]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep  7 19:51:13 node-2 puppet-user[9327]: Finished catalog run in 0.82 seconds
Sep  7 19:51:15 node-2 multipathd: uevent trigger error
Sep  7 19:51:15 node-2 puppet-user[9757]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep  7 19:51:15 node-2 puppet-user[9757]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Sep  7 19:51:15 node-2 puppet-user[9757]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep  7 19:51:15 node-2 puppet-user[9757]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep  7 19:51:15 node-2 puppet-user[9757]: (/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"]'
Sep  7 19:51:15 node-2 puppet-user[9757]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep  7 19:51:15 node-2 puppet-user[9757]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep  7 19:51:15 node-2 puppet-user[9757]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep  7 19:51:15 node-2 puppet-user[9757]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep  7 19:51:15 node-2 puppet-user[9757]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep  7 19:51:15 node-2 puppet-user[9757]: Finished catalog run in 0.06 seconds
Sep  7 19:51:16 node-2 puppet-user[10214]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep  7 19:51:16 node-2 puppet-user[10214]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Sep  7 19:51:17 node-2 puppet-user[10214]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep  7 19:51:17 node-2 puppet-user[10214]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep  7 19:51:17 node-2 puppet-user[10214]: Finished catalog run in 0.04 seconds
Sep  7 19:51:18 node-2 puppet-user[10673]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep  7 19:51:18 node-2 puppet-user[10673]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep  7 19:51:19 node-2 puppet-user[10673]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep  7 19:51:19 node-2 puppet-user[10673]: Finished catalog run in 0.04 seconds
Sep  7 19:51:19 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  7 19:51:19 node-2 nailgun-agent: D, [2016-09-07T19:51:01.541501 #9091] DEBUG -- : Sleep for 18 seconds before sending request
Sep  7 19:51:19 node-2 nailgun-agent: I, [2016-09-07T19:51:19.557807 #9091]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  7 19:51:19 node-2 nailgun-agent: D, [2016-09-07T19:51:19.960689 #9091] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Sep  7 19:51:20 node-2 puppet-user[11130]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep  7 19:51:20 node-2 puppet-user[11130]: Compiled catalog for node-2.domain.tld in environment production in 0.20 seconds
Sep  7 19:51:20 node-2 puppet-user[11130]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep  7 19:51:21 node-2 puppet-user[11130]: (/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
Sep  7 19:51:21 node-2 puppet-user[11130]: Finished catalog run in 0.43 seconds
Sep  7 19:51:22 node-2 kernel: [   64.531779] init: plymouth-upstart-bridge main process ended, respawning
Sep  7 19:51:22 node-2 puppet-agent[9057]: Could not run: SIGTERM
Sep  7 19:51:22 node-2 kernel: [   64.788318] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep  7 19:51:22 node-2 ec2: 
Sep  7 19:51:22 node-2 ec2: #############################################################
Sep  7 19:51:22 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep  7 19:51:22 node-2 ec2: 1024 e7:74:ff:9d:2d:d2:e7:1d:eb:82:55:5f:61:46:c9:63  root@node-2.domain.tld (DSA)
Sep  7 19:51:22 node-2 ec2: 256 1f:44:be:f4:88:a1:60:e7:5b:54:43:a3:8b:ab:77:2e  root@node-2.domain.tld (ECDSA)
Sep  7 19:51:22 node-2 ec2: 256 14:6b:2a:aa:dd:d9:76:0c:94:f2:40:cf:5d:0d:99:e0  root@node-2.domain.tld (ED25519)
Sep  7 19:51:22 node-2 ec2: 2048 ed:88:cb:72:ef:21:3e:1a:b4:39:cf:3c:5e:3c:d5:88  root@node-2.domain.tld (RSA)
Sep  7 19:51:22 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep  7 19:51:22 node-2 ec2: #############################################################
Sep  7 19:51:22 node-2 puppet-user[11742]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep  7 19:51:22 node-2 puppet-user[11742]: Compiled catalog for node-2.domain.tld in environment production in 0.24 seconds
Sep  7 19:51:22 node-2 puppet-user[11742]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep  7 19:51:22 node-2 puppet-user[11742]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep  7 19:51:22 node-2 puppet-user[11742]: (/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
Sep  7 19:51:23 node-2 puppet-user[11742]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep  7 19:51:23 node-2 puppet-user[11742]: Finished catalog run in 0.22 seconds
Sep  7 19:51:24 node-2 puppet-user[12386]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep  7 19:51:24 node-2 puppet-user[12386]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Sep  7 19:51:24 node-2 puppet-user[12386]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep  7 19:51:24 node-2 kernel: [   67.233204] nr_pdflush_threads exported in /proc is scheduled for removal
Sep  7 19:51:24 node-2 kernel: [   67.233251] 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.
Sep  7 19:51:24 node-2 puppet-user[12386]: (/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'
Sep  7 19:51:24 node-2 puppet-user[12386]: Finished catalog run in 0.06 seconds
Sep  7 19:51:26 node-2 puppet-user[12838]: (Scope(Class[main])) MODULAR: sync_time
Sep  7 19:51:26 node-2 puppet-user[12838]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep  7 19:51:26 node-2 ntpdate[13250]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.002188 #9091] DEBUG -- : Trying to find block devices
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.002312 #9091] DEBUG -- : Found block device: sda
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.002370 #9091] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.002406 #9091] DEBUG -- : Trying to get list of physical devices
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.002608 #9091] DEBUG -- : Getting udev properties for device: sda
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.004571 #9091] 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"=>"0x618e72837274ff201cc7880
Sep  7 19:51:32 node-2 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39388", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.004598 #9091] DEBUG -- : Trying to find out if device sda is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.004690 #9091] DEBUG -- : Device sda removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.004706 #9091] DEBUG -- : Device sda seems to be appropriate
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.005172 #9091] DEBUG -- : Getting udev properties for device: dm-0
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.007271 #9091] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-RIxrJieOAX6rrLKExbzUfxZnMPvaaQOe54rjdT311cm2honYh7bHoVoYZCvw0KNA /dev/disk/by-uuid/51fd3155-7864-4185-8703-4fd3d22bb4ee /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-RIxrJieOAX6rrLKExbzUfxZnMPvaaQOe54rjdT311cm2honYh7bHoVoYZCvw0KNA", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"51fd3155-7864-4185-8703-4fd3d22bb4ee", "ID_FS_UUID_ENC"=>"51fd3155-7864-4185-8703-4fd3d22bb4ee", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81126", "nomdmonddf"=>"1", "nomd
Sep  7 19:51:32 node-2 nailgun-agent: monisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.007299 #9091] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.007330 #9091] DEBUG -- : Device dm-0 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.007345 #9091] DEBUG -- : Device dm-0 seems to be appropriate
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.007360 #9091] DEBUG -- : Getting udev properties for device: dm-1
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.009269 #9091] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-CrWFwcG6RDlGexcZp3CFVIX1cL1u1xjJsRCGdm3DbbvxdVwkouXdQVobtEWu1FXa /dev/disk/by-uuid/2f3cc843-da68-4109-8a22-52a2d74a62e7 /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-CrWFwcG6RDlGexcZp3CFVIX1cL1u1xjJsRCGdm3DbbvxdVwkouXdQVobtEWu1FXa", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2f3cc843-da68-4109-8a22-52a2d74a62e7", "ID_FS_UUID_ENC"=>"2f3cc843-da68-4109-8a22-52a2d74a62e7", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34
Sep  7 19:51:32 node-2 nailgun-agent: 954", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.009297 #9091] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.009329 #9091] DEBUG -- : Device dm-1 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.009343 #9091] DEBUG -- : Device dm-1 seems to be appropriate
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.009359 #9091] DEBUG -- : Getting udev properties for device: dm-2
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.011255 #9091] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-axRbIwKEJaeQKrKWQxS8cx23cyiHsLL78xhGC8OiKdRrRvqn0tOsrp5Zr0fhcCpV /dev/disk/by-uuid/ef6cbaed-4efb-4970-9431-d213b47c6a0e /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-axRbIwKEJaeQKrKWQxS8cx23cyiHsLL78xhGC8OiKdRrRvqn0tOsrp5Zr0fhcCpV", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ef6cbaed-4efb-4970-9431-d213b47c6a0e", "ID_FS_UUID_ENC"=>"ef6cbaed-4efb-4970-9431-d213b47c6a0e", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"41142", "nomdmond
Sep  7 19:51:32 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.011293 #9091] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.011323 #9091] DEBUG -- : Device dm-2 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.011337 #9091] DEBUG -- : Device dm-2 seems to be appropriate
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.011353 #9091] DEBUG -- : Getting udev properties for device: dm-3
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.013186 #9091] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-qHqn1wEEgmYbDuDETpVlEVXT36AEiyIgeBRXfwkaadqeBVrA3xgitt7boBCAsUZl /dev/disk/by-uuid/bd29e46e-9bb8-4677-9c95-5aee201b251d /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-qHqn1wEEgmYbDuDETpVlEVXT36AEiyIgeBRXfwkaadqeBVrA3xgitt7boBCAsUZl", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"bd29e46e-9bb8-4677-9c95-5aee201b251d", "ID_FS_UUID_ENC"=>"bd29e46e-9bb8-4677-9c95-5aee201b251d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45582", "nomdmonddf"=>"1", 
Sep  7 19:51:32 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.013234 #9091] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.013266 #9091] DEBUG -- : Device dm-3 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.013280 #9091] DEBUG -- : Device dm-3 seems to be appropriate
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.013296 #9091] DEBUG -- : Getting udev properties for device: dm-4
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.015188 #9091] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-tyYAcuBfRDnZ7tU5E2uSEuS0ySnc7EM7jcRIIGtoGwCY0mJnqrpk9H67fgP8A3SP /dev/disk/by-uuid/46f8d5d6-a4ee-4f0c-afe0-1d52d0af8229 /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-tyYAcuBfRDnZ7tU5E2uSEuS0ySnc7EM7jcRIIGtoGwCY0mJnqrpk9H67fgP8A3SP", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"46f8d5d6-a4ee-4f0c-afe0-1d52d0af8229", "ID_FS_UUID_ENC"=>"46f8d5d6-a4ee-4f0c-afe0-1d52d0af8229", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55774", "nomdmonddf"=>"1", "nomd
Sep  7 19:51:32 node-2 nailgun-agent: monisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.015228 #9091] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.015261 #9091] DEBUG -- : Device dm-4 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.015276 #9091] DEBUG -- : Device dm-4 seems to be appropriate
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.015310 #9091] DEBUG -- : Getting udev properties for device: dm-5
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.017391 #9091] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-tyYAcuBfRDnZ7tU5E2uSEuS0ySnc7EM74S5E55gpRd0OUCHed0i8G26eoBA18fSo /dev/disk/by-uuid/dd5de722-0f67-4e7e-9734-a3aa9e028108 /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-tyYAcuBfRDnZ7tU5E2uSEuS0ySnc7EM74S5E55gpRd0OUCHed0i8G26eoBA18fSo", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"dd5de722-0f67-4e7e-9734-a3aa9e028108", "ID_FS_UUID_ENC"=>"dd5de722-0f67-4e7e-9734-a3aa9e028108", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56278", "nomdmonddf"=>"1", "nomdmonisw"
Sep  7 19:51:32 node-2 nailgun-agent: =>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.017469 #9091] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.017501 #9091] DEBUG -- : Device dm-5 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.017516 #9091] DEBUG -- : Device dm-5 seems to be appropriate
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.017532 #9091] DEBUG -- : Getting udev properties for device: ram0
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.019266 #9091] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15455", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.019292 #9091] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.019333 #9091] DEBUG -- : Device ram0 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.019354 #9091] DEBUG -- : Getting udev properties for device: ram1
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.020973 #9091] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15663", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.020999 #9091] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.021033 #9091] DEBUG -- : Device ram1 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.021056 #9091] DEBUG -- : Getting udev properties for device: ram2
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.022513 #9091] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17260", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.022569 #9091] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.022617 #9091] DEBUG -- : Device ram2 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.022639 #9091] DEBUG -- : Getting udev properties for device: ram3
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.024146 #9091] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17495", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.024191 #9091] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.024231 #9091] DEBUG -- : Device ram3 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.024253 #9091] DEBUG -- : Getting udev properties for device: ram4
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.025699 #9091] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17660", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.025732 #9091] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.025775 #9091] DEBUG -- : Device ram4 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.025797 #9091] DEBUG -- : Getting udev properties for device: ram5
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.027664 #9091] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17886", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.027691 #9091] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.027761 #9091] DEBUG -- : Device ram5 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.027782 #9091] DEBUG -- : Getting udev properties for device: ram6
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.029388 #9091] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18079", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.029416 #9091] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.029470 #9091] DEBUG -- : Device ram6 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.029492 #9091] DEBUG -- : Getting udev properties for device: ram7
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.031365 #9091] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18249", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.031391 #9091] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.031425 #9091] DEBUG -- : Device ram7 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.031463 #9091] DEBUG -- : Getting udev properties for device: ram8
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.033141 #9091] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18525", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.033166 #9091] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.033204 #9091] DEBUG -- : Device ram8 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.033225 #9091] DEBUG -- : Getting udev properties for device: ram9
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.034938 #9091] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18714", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.034964 #9091] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.035002 #9091] DEBUG -- : Device ram9 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.035024 #9091] DEBUG -- : Getting udev properties for device: loop0
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.037152 #9091] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"13847", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.037178 #9091] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.037213 #9091] DEBUG -- : Device loop0 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.037234 #9091] DEBUG -- : Getting udev properties for device: loop1
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.038845 #9091] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14018", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.038871 #9091] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.038922 #9091] DEBUG -- : Device loop1 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.038944 #9091] DEBUG -- : Getting udev properties for device: loop2
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.040693 #9091] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14201", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.040744 #9091] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.040781 #9091] DEBUG -- : Device loop2 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.040803 #9091] DEBUG -- : Getting udev properties for device: loop3
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.042689 #9091] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14334", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.042726 #9091] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.042770 #9091] DEBUG -- : Device loop3 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.042800 #9091] DEBUG -- : Getting udev properties for device: loop4
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.044559 #9091] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14486", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.044585 #9091] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.044666 #9091] DEBUG -- : Device loop4 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.044688 #9091] DEBUG -- : Getting udev properties for device: loop5
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.046248 #9091] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14819", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.046285 #9091] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.046334 #9091] DEBUG -- : Device loop5 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.046356 #9091] DEBUG -- : Getting udev properties for device: loop6
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.047954 #9091] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15024", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.047980 #9091] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.048032 #9091] DEBUG -- : Device loop6 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.048052 #9091] DEBUG -- : Getting udev properties for device: loop7
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.049561 #9091] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15211", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.049586 #9091] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.049625 #9091] DEBUG -- : Device loop7 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.049668 #9091] DEBUG -- : Getting udev properties for device: ram10
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.051186 #9091] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"15900", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.051211 #9091] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.051270 #9091] DEBUG -- : Device ram10 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.051298 #9091] DEBUG -- : Getting udev properties for device: ram11
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.052838 #9091] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16311", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.052863 #9091] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.052902 #9091] DEBUG -- : Device ram11 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.052923 #9091] DEBUG -- : Getting udev properties for device: ram12
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.054481 #9091] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16531", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.054507 #9091] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.054555 #9091] DEBUG -- : Device ram12 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.054575 #9091] DEBUG -- : Getting udev properties for device: ram13
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.056415 #9091] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16725", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.056440 #9091] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.056494 #9091] DEBUG -- : Device ram13 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.056516 #9091] DEBUG -- : Getting udev properties for device: ram14
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.058208 #9091] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"16887", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.058248 #9091] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.058282 #9091] DEBUG -- : Device ram14 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.058321 #9091] DEBUG -- : Getting udev properties for device: ram15
Sep  7 19:51:32 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.060321 #9091] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"17073", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.060360 #9091] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.060422 #9091] DEBUG -- : Device ram15 removable parameter: "0"
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.060458 #9091] 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"}]
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.060510 #9091] DEBUG -- : Block device seems to be physical data storage: sda
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.060543 #9091] DEBUG -- : Found block device: dm-0
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.060559 #9091] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.060590 #9091] DEBUG -- : Found block device: dm-1
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.060604 #9091] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065384 #9091] DEBUG -- : Found block device: dm-2
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065412 #9091] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065426 #9091] DEBUG -- : Found block device: dm-3
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065437 #9091] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065447 #9091] DEBUG -- : Found block device: dm-4
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065459 #9091] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065468 #9091] DEBUG -- : Found block device: dm-5
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065479 #9091] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065488 #9091] DEBUG -- : Found block device: ram0
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065498 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065558 #9091] DEBUG -- : Found block device: ram1
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065569 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065578 #9091] DEBUG -- : Found block device: ram2
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065588 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065597 #9091] DEBUG -- : Found block device: ram3
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065607 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065615 #9091] DEBUG -- : Found block device: ram4
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065624 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065633 #9091] DEBUG -- : Found block device: ram5
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065691 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065701 #9091] DEBUG -- : Found block device: ram6
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065712 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065720 #9091] DEBUG -- : Found block device: ram7
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065731 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065740 #9091] DEBUG -- : Found block device: ram8
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065750 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065758 #9091] DEBUG -- : Found block device: ram9
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065768 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065777 #9091] DEBUG -- : Found block device: loop0
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065838 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065847 #9091] DEBUG -- : Found block device: loop1
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065858 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065867 #9091] DEBUG -- : Found block device: loop2
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065876 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065885 #9091] DEBUG -- : Found block device: loop3
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065895 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065904 #9091] DEBUG -- : Found block device: loop4
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065915 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065970 #9091] DEBUG -- : Found block device: loop5
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065983 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.065992 #9091] DEBUG -- : Found block device: loop6
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066001 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066010 #9091] DEBUG -- : Found block device: loop7
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066019 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066027 #9091] DEBUG -- : Found block device: ram10
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066036 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066044 #9091] DEBUG -- : Found block device: ram11
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066101 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066111 #9091] DEBUG -- : Found block device: ram12
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066122 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066130 #9091] DEBUG -- : Found block device: ram13
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066140 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066149 #9091] DEBUG -- : Found block device: ram14
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066159 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066167 #9091] DEBUG -- : Found block device: ram15
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066177 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.066249 #9091] 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}]
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.170534 #9091] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Sep  7 19:51:32 node-2 nailgun-agent: D, [2016-09-07T19:51:32.170580 #9091] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep  7 19:51:32 node-2 ntpdate[13250]: adjust time server 10.20.0.2 offset 0.000686 sec
Sep  7 19:51:32 node-2 puppet-user[12838]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep  7 19:51:32 node-2 puppet-user[12838]: Finished catalog run in 6.17 seconds
Sep  7 19:51:38 node-2 puppet-user[13632]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep  7 19:51:38 node-2 puppet-user[13632]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Sep  7 19:51:38 node-2 puppet-user[13632]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep  7 19:51:38 node-2 puppet-user[13632]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Sep  7 19:51:38 node-2 puppet-user[13632]: Finished catalog run in 0.07 seconds
Sep  7 19:51:39 node-2 puppet-user[14081]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep  7 19:51:41 node-2 puppet-user[14081]: Compiled catalog for node-2.domain.tld in environment production in 1.37 seconds
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep  7 19:51:41 node-2 puppet-user[14081]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep  7 19:51:41 node-2 puppet-user[14081]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/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
Sep  7 19:51:41 node-2 puppet-user[14081]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep  7 19:51:44 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.327758 #9091] DEBUG -- : Trying to find block devices
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.327845 #9091] DEBUG -- : Found block device: sda
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.327872 #9091] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.327893 #9091] DEBUG -- : Block device seems to be physical data storage: sda
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.327915 #9091] DEBUG -- : Found block device: dm-0
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.327952 #9091] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.327966 #9091] DEBUG -- : Found block device: dm-1
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.327977 #9091] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.327988 #9091] DEBUG -- : Found block device: dm-2
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.327998 #9091] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328009 #9091] DEBUG -- : Found block device: dm-3
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328019 #9091] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328029 #9091] DEBUG -- : Found block device: dm-4
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328040 #9091] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328062 #9091] DEBUG -- : Found block device: dm-5
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328091 #9091] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328102 #9091] DEBUG -- : Found block device: ram0
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328112 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328122 #9091] DEBUG -- : Found block device: ram1
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328133 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328142 #9091] DEBUG -- : Found block device: ram2
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328152 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328162 #9091] DEBUG -- : Found block device: ram3
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328189 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328198 #9091] DEBUG -- : Found block device: ram4
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328208 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328233 #9091] DEBUG -- : Found block device: ram5
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328244 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328254 #9091] DEBUG -- : Found block device: ram6
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328271 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328316 #9091] DEBUG -- : Found block device: ram7
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328328 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328338 #9091] DEBUG -- : Found block device: ram8
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328348 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328373 #9091] DEBUG -- : Found block device: ram9
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328384 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328393 #9091] DEBUG -- : Found block device: loop0
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328404 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328430 #9091] DEBUG -- : Found block device: loop1
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328441 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328451 #9091] DEBUG -- : Found block device: loop2
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328461 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328484 #9091] DEBUG -- : Found block device: loop3
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328495 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328504 #9091] DEBUG -- : Found block device: loop4
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328532 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328544 #9091] DEBUG -- : Found block device: loop5
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328555 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328565 #9091] DEBUG -- : Found block device: loop6
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328587 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328596 #9091] DEBUG -- : Found block device: loop7
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328606 #9091] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328641 #9091] DEBUG -- : Found block device: ram10
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328651 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328661 #9091] DEBUG -- : Found block device: ram11
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328671 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328680 #9091] DEBUG -- : Found block device: ram12
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328690 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328699 #9091] DEBUG -- : Found block device: ram13
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328709 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328719 #9091] DEBUG -- : Found block device: ram14
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328729 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328765 #9091] DEBUG -- : Found block device: ram15
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328776 #9091] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.328807 #9091] 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}]
Sep  7 19:51:44 node-2 nailgun-agent: D, [2016-09-07T19:51:44.465890 #9091] DEBUG -- : Response: status: 200 body: {"id": 2}
Sep  7 19:51:44 node-2 nailgun-agent: I, [2016-09-07T19:51:44.466063 #9091]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Sep  7 19:51:50 node-2 puppet-user[14081]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep  7 19:51:50 node-2 puppet-user[14081]: Finished catalog run in 9.03 seconds
Sep  7 19:51:51 node-2 puppet-user[15000]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep  7 19:51:51 node-2 puppet-user[15000]: Compiled catalog for node-2.domain.tld in environment production in 0.11 seconds
Sep  7 19:51:56 node-2 puppet-user[15000]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep  7 19:52:01 node-2 CRON[16208]: (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")
Sep  7 19:52:24 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep  7 19:52:24 node-2 nailgun-agent: I, [2016-09-07T19:52:24.656119 #16211]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep  7 19:52:25 node-2 puppet-user[15000]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep  7 19:52:25 node-2 puppet-user[15000]: Finished catalog run in 33.68 seconds
Sep  7 19:52:27 node-2 puppet-user[17618]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep  7 19:52:28 node-2 puppet-user[17618]: Compiled catalog for node-2.domain.tld in environment production in 0.55 seconds
Sep  7 19:52:28 node-2 puppet-user[17618]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep  7 19:52:28 node-2 puppet-user[17618]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep  7 19:52:28 node-2 puppet-user[17618]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep  7 19:52:28 node-2 puppet-user[17618]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep  7 19:52:28 node-2 puppet-user[17618]: Finished catalog run in 0.09 seconds
Sep  7 19:52:30 node-2 puppet-user[18076]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep  7 19:52:31 node-2 puppet-user[18076]: Compiled catalog for node-2.domain.tld in environment production in 0.84 seconds
Sep  7 19:52:31 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep  7 19:52:31 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep  7 19:52:31 node-2 crontab[18504]: (root) LIST (root)
Sep  7 19:52:31 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep  7 19:52:31 node-2 crontab[18507]: (root) REPLACE (root)
Sep  7 19:52:33 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep  7 19:52:34 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep  7 19:52:34 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep  7 19:52:34 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep  7 19:52:34 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep  7 19:52:34 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/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
Sep  7 19:52:35 node-2 puppet-user[18076]: (/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
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/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
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/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
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/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
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/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
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/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
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/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
Sep  7 19:52:35 node-2 puppet-user[18076]: (/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
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep  7 19:52:35 node-2 puppet-user[18076]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep  7 19:52:36 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8379" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep  7 19:52:36 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep  7 19:52:37 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:37 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:37 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:37 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:37 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:57 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:57 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:57 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:57 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:59 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:59 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:59 node-2 multipathd: uevent trigger error
<27>Sep  7 19:52:59 node-2 multipathd: uevent trigger error
<27>Sep  7 19:53:01 node-2 multipathd: uevent trigger error
<27>Sep  7 19:53:01 node-2 multipathd: uevent trigger error
<27>Sep  7 19:53:01 node-2 multipathd: uevent trigger error
<27>Sep  7 19:53:01 node-2 multipathd: uevent trigger error
<27>Sep  7 19:53:01 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:01 node-2 ntpdate[30548]: no servers can be used, exiting
<27>Sep  7 19:54:01 node-2 ntpdate[30682]: no servers can be used, exiting
<27>Sep  7 19:54:01 node-2 ntpdate[30857]: no servers can be used, exiting
<27>Sep  7 19:54:32 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:32 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:32 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:32 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:32 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:35 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:35 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:35 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:36 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:36 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:47 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:47 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:47 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:47 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:50 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:50 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:50 node-2 multipathd: uevent trigger error
<27>Sep  7 19:54:50 node-2 multipathd: uevent trigger error
<27>Sep  7 19:55:50 node-2 multipathd: uevent trigger error
<27>Sep  7 19:55:50 node-2 multipathd: uevent trigger error
<27>Sep  7 19:55:50 node-2 multipathd: uevent trigger error
<27>Sep  7 19:55:50 node-2 multipathd: uevent trigger error
<27>Sep  7 19:55:50 node-2 multipathd: uevent trigger error
<27>Sep  7 19:55:58 node-2 multipathd: uevent trigger error
<27>Sep  7 19:55:58 node-2 multipathd: uevent trigger error
<27>Sep  7 19:55:58 node-2 multipathd: uevent trigger error
<27>Sep  7 19:55:58 node-2 multipathd: uevent trigger error
<27>Sep  7 19:55:59 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:01 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  7 19:56:01 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  7 19:56:07 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  7 19:56:07 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  7 19:56:13 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  7 19:56:18 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  7 19:56:18 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep  7 19:56:25 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:25 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:25 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:25 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:25 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:25 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:38 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:38 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:38 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:38 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:38 node-2 multipathd: uevent trigger error
<27>Sep  7 19:56:38 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:11 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:11 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:11 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:11 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:11 node-2 multipathd: uevent trigger error
<129>Sep  7 19:57:14 node-2 haproxy[25326]: Server odl-neutron-endpoint/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 77ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  7 19:57:14 node-2 haproxy[25326]: proxy odl-neutron-endpoint has no server available!
<129>Sep  7 19:57:15 node-2 haproxy[25330]: Server odl-jetty/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 2ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep  7 19:57:15 node-2 haproxy[25330]: proxy odl-jetty has no server available!
<27>Sep  7 19:57:37 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:37 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:37 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:37 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:37 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:37 node-2 multipathd: uevent trigger error
<129>Sep  7 19:57:40 node-2 haproxy[28028]: 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>Sep  7 19:57:40 node-2 haproxy[28028]: 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>Sep  7 19:57:40 node-2 haproxy[28028]: Backup Server mysqld/node-5 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>Sep  7 19:57:40 node-2 haproxy[28028]: proxy mysqld has no server available!
<27>Sep  7 19:57:43 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:43 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:43 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:43 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:46 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:46 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:46 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:46 node-2 multipathd: uevent trigger error
<129>Sep  7 19:57:49 node-2 haproxy[30544]: 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>Sep  7 19:57:49 node-2 haproxy[30544]: 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>Sep  7 19:57:49 node-2 haproxy[30544]: Backup Server mysqld/node-5 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>Sep  7 19:57:49 node-2 haproxy[30544]: proxy mysqld has no server available!
<129>Sep  7 19:57:49 node-2 haproxy[30544]: 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>Sep  7 19:57:50 node-2 haproxy[30548]: 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>Sep  7 19:57:50 node-2 haproxy[30548]: Server object-storage/node-5 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>Sep  7 19:57:50 node-2 haproxy[30548]: proxy object-storage has no server available!
<27>Sep  7 19:57:52 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:52 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:52 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:52 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:52 node-2 multipathd: uevent trigger error
<129>Sep  7 19:57:54 node-2 haproxy[31893]: 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>Sep  7 19:57:54 node-2 haproxy[31893]: 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>Sep  7 19:57:54 node-2 haproxy[31893]: Server neutron/node-5 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>Sep  7 19:57:54 node-2 haproxy[31893]: proxy neutron has no server available!
<129>Sep  7 19:57:55 node-2 haproxy[31902]: 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>Sep  7 19:57:55 node-2 haproxy[31902]: 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>Sep  7 19:57:55 node-2 haproxy[31902]: Backup Server mysqld/node-5 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>Sep  7 19:57:55 node-2 haproxy[31902]: proxy mysqld has no server available!
<129>Sep  7 19:57:55 node-2 haproxy[31902]: 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>Sep  7 19:57:55 node-2 haproxy[31902]: 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>Sep  7 19:57:55 node-2 haproxy[31902]: Server object-storage/node-5 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>Sep  7 19:57:55 node-2 haproxy[31902]: proxy object-storage has no server available!
<27>Sep  7 19:57:57 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:57 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:57 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:57 node-2 multipathd: uevent trigger error
<27>Sep  7 19:57:57 node-2 multipathd: uevent trigger error
<129>Sep  7 19:58:00 node-2 haproxy[850]: 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>Sep  7 19:58:00 node-2 haproxy[850]: Server keystone-1/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>Sep  7 19:58:00 node-2 haproxy[850]: Server keystone-1/node-5 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>Sep  7 19:58:00 node-2 haproxy[850]: proxy keystone-1 has no server available!
<129>Sep  7 19:58:00 node-2 haproxy[850]: 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>Sep  7 19:58:00 node-2 haproxy[850]: Server keystone-2/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>Sep  7 19:58:00 node-2 haproxy[850]: Server keystone-2/node-5 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>Sep  7 19:58:00 node-2 haproxy[850]: proxy keystone-2 has no server available!
<129>Sep  7 19:58:00 node-2 haproxy[850]: 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>Sep  7 19:58:01 node-2 haproxy[854]: 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>Sep  7 19:58:01 node-2 haproxy[854]: Server neutron/node-5 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>Sep  7 19:58:01 node-2 haproxy[854]: proxy neutron has no server available!
<129>Sep  7 19:58:01 node-2 haproxy[854]: 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>Sep  7 19:58:01 node-2 haproxy[854]: 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>Sep  7 19:58:01 node-2 haproxy[854]: Backup Server mysqld/node-5 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>Sep  7 19:58:01 node-2 haproxy[854]: proxy mysqld has no server available!
<129>Sep  7 19:58:01 node-2 haproxy[854]: 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>Sep  7 19:58:01 node-2 haproxy[854]: 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>Sep  7 19:58:01 node-2 haproxy[854]: Server object-storage/node-5 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>Sep  7 19:58:01 node-2 haproxy[854]: proxy object-storage has no server available!
<27>Sep  7 19:58:03 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:03 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:03 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:03 node-2 multipathd: uevent trigger error
<129>Sep  7 19:58:05 node-2 haproxy[2225]: 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>Sep  7 19:58:05 node-2 haproxy[2225]: Server keystone-1/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>Sep  7 19:58:05 node-2 haproxy[2225]: Server keystone-1/node-5 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>Sep  7 19:58:05 node-2 haproxy[2225]: proxy keystone-1 has no server available!
<129>Sep  7 19:58:05 node-2 haproxy[2225]: 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>Sep  7 19:58:05 node-2 haproxy[2225]: Server keystone-2/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>Sep  7 19:58:05 node-2 haproxy[2225]: Server keystone-2/node-5 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>Sep  7 19:58:05 node-2 haproxy[2225]: proxy keystone-2 has no server available!
<129>Sep  7 19:58:06 node-2 haproxy[2229]: 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>Sep  7 19:58:06 node-2 haproxy[2229]: 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>Sep  7 19:58:06 node-2 haproxy[2229]: Server neutron/node-5 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>Sep  7 19:58:06 node-2 haproxy[2229]: proxy neutron has no server available!
<129>Sep  7 19:58:06 node-2 haproxy[2229]: 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>Sep  7 19:58:06 node-2 haproxy[2229]: 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>Sep  7 19:58:06 node-2 haproxy[2229]: Backup Server mysqld/node-5 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>Sep  7 19:58:06 node-2 haproxy[2229]: proxy mysqld has no server available!
<129>Sep  7 19:58:06 node-2 haproxy[2229]: 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>Sep  7 19:58:06 node-2 haproxy[2229]: 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>Sep  7 19:58:06 node-2 haproxy[2229]: Server object-storage/node-5 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>Sep  7 19:58:06 node-2 haproxy[2229]: proxy object-storage has no server available!
<129>Sep  7 19:58:06 node-2 haproxy[2229]: 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>Sep  7 19:58:07 node-2 haproxy[2229]: 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>Sep  7 19:58:07 node-2 haproxy[2229]: Server aodh/node-5 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>Sep  7 19:58:07 node-2 haproxy[2229]: proxy aodh has no server available!
<27>Sep  7 19:58:08 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:08 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:08 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:08 node-2 multipathd: uevent trigger error
<129>Sep  7 19:58:11 node-2 haproxy[3560]: 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>Sep  7 19:58:11 node-2 haproxy[3560]: Server keystone-1/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>Sep  7 19:58:11 node-2 haproxy[3560]: Server keystone-1/node-5 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>Sep  7 19:58:11 node-2 haproxy[3560]: proxy keystone-1 has no server available!
<129>Sep  7 19:58:11 node-2 haproxy[3560]: 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>Sep  7 19:58:11 node-2 haproxy[3560]: Server keystone-2/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>Sep  7 19:58:11 node-2 haproxy[3560]: Server keystone-2/node-5 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>Sep  7 19:58:11 node-2 haproxy[3560]: proxy keystone-2 has no server available!
<129>Sep  7 19:58:11 node-2 haproxy[3560]: 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>Sep  7 19:58:11 node-2 haproxy[3560]: 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>Sep  7 19:58:11 node-2 haproxy[3560]: Server neutron/node-5 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>Sep  7 19:58:11 node-2 haproxy[3560]: proxy neutron has no server available!
<129>Sep  7 19:58:11 node-2 haproxy[3560]: 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>Sep  7 19:58:11 node-2 haproxy[3560]: 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>Sep  7 19:58:11 node-2 haproxy[3560]: Backup Server mysqld/node-5 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>Sep  7 19:58:11 node-2 haproxy[3560]: proxy mysqld has no server available!
<129>Sep  7 19:58:12 node-2 haproxy[3564]: 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>Sep  7 19:58:12 node-2 haproxy[3564]: 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>Sep  7 19:58:12 node-2 haproxy[3564]: Server object-storage/node-5 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>Sep  7 19:58:12 node-2 haproxy[3564]: proxy object-storage has no server available!
<129>Sep  7 19:58:12 node-2 haproxy[3564]: 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>Sep  7 19:58:12 node-2 haproxy[3564]: 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>Sep  7 19:58:12 node-2 haproxy[3564]: Server aodh/node-5 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>Sep  7 19:58:12 node-2 haproxy[3564]: proxy aodh has no server available!
<129>Sep  7 19:58:12 node-2 haproxy[3564]: 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>Sep  7 19:58:12 node-2 haproxy[3564]: 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>Sep  7 19:58:12 node-2 haproxy[3564]: Server ceilometer/node-5 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>Sep  7 19:58:12 node-2 haproxy[3564]: proxy ceilometer has no server available!
<27>Sep  7 19:58:14 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:14 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:14 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:14 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:14 node-2 multipathd: uevent trigger error
<129>Sep  7 19:58:16 node-2 haproxy[4930]: 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>Sep  7 19:58:16 node-2 haproxy[4930]: Server keystone-1/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>Sep  7 19:58:16 node-2 haproxy[4930]: Server keystone-1/node-5 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>Sep  7 19:58:16 node-2 haproxy[4930]: proxy keystone-1 has no server available!
<129>Sep  7 19:58:16 node-2 haproxy[4930]: 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>Sep  7 19:58:16 node-2 haproxy[4930]: Server keystone-2/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>Sep  7 19:58:16 node-2 haproxy[4930]: Server keystone-2/node-5 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>Sep  7 19:58:16 node-2 haproxy[4930]: proxy keystone-2 has no server available!
<129>Sep  7 19:58:17 node-2 haproxy[4937]: 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>Sep  7 19:58:17 node-2 haproxy[4937]: 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>Sep  7 19:58:17 node-2 haproxy[4937]: Server neutron/node-5 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>Sep  7 19:58:17 node-2 haproxy[4937]: proxy neutron has no server available!
<129>Sep  7 19:58:17 node-2 haproxy[4937]: 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>Sep  7 19:58:17 node-2 haproxy[4937]: 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>Sep  7 19:58:17 node-2 haproxy[4937]: Backup Server mysqld/node-5 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>Sep  7 19:58:17 node-2 haproxy[4937]: proxy mysqld has no server available!
<129>Sep  7 19:58:17 node-2 haproxy[4937]: 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>Sep  7 19:58:17 node-2 haproxy[4937]: 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>Sep  7 19:58:17 node-2 haproxy[4937]: Server object-storage/node-5 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>Sep  7 19:58:17 node-2 haproxy[4937]: proxy object-storage has no server available!
<129>Sep  7 19:58:17 node-2 haproxy[4937]: 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>Sep  7 19:58:17 node-2 haproxy[4937]: 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>Sep  7 19:58:17 node-2 haproxy[4937]: Server aodh/node-5 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>Sep  7 19:58:17 node-2 haproxy[4937]: proxy aodh has no server available!
<129>Sep  7 19:58:18 node-2 haproxy[4937]: 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>Sep  7 19:58:18 node-2 haproxy[4937]: 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>Sep  7 19:58:18 node-2 haproxy[4937]: Server ceilometer/node-5 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>Sep  7 19:58:18 node-2 haproxy[4937]: proxy ceilometer has no server available!
<27>Sep  7 19:58:19 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:19 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:19 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:19 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:19 node-2 multipathd: uevent trigger error
<129>Sep  7 19:58:21 node-2 haproxy[6272]: 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>Sep  7 19:58:21 node-2 haproxy[6272]: Server horizon/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>Sep  7 19:58:21 node-2 haproxy[6272]: 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>Sep  7 19:58:22 node-2 haproxy[6276]: Server keystone-1/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>Sep  7 19:58:22 node-2 haproxy[6276]: Server keystone-1/node-5 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>Sep  7 19:58:22 node-2 haproxy[6276]: proxy keystone-1 has no server available!
<129>Sep  7 19:58:22 node-2 haproxy[6276]: 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>Sep  7 19:58:22 node-2 haproxy[6276]: Server keystone-2/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>Sep  7 19:58:22 node-2 haproxy[6276]: Server keystone-2/node-5 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>Sep  7 19:58:22 node-2 haproxy[6276]: proxy keystone-2 has no server available!
<129>Sep  7 19:58:22 node-2 haproxy[6276]: 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>Sep  7 19:58:22 node-2 haproxy[6276]: 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>Sep  7 19:58:22 node-2 haproxy[6276]: Server neutron/node-5 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>Sep  7 19:58:22 node-2 haproxy[6276]: proxy neutron has no server available!
<129>Sep  7 19:58:22 node-2 haproxy[6276]: 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>Sep  7 19:58:22 node-2 haproxy[6276]: 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>Sep  7 19:58:22 node-2 haproxy[6276]: Backup Server mysqld/node-5 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>Sep  7 19:58:22 node-2 haproxy[6276]: proxy mysqld has no server available!
<129>Sep  7 19:58:22 node-2 haproxy[6276]: 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>Sep  7 19:58:22 node-2 haproxy[6276]: 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>Sep  7 19:58:23 node-2 haproxy[6276]: Server object-storage/node-5 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>Sep  7 19:58:23 node-2 haproxy[6276]: proxy object-storage has no server available!
<129>Sep  7 19:58:23 node-2 haproxy[6276]: 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>Sep  7 19:58:23 node-2 haproxy[6276]: 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>Sep  7 19:58:23 node-2 haproxy[6276]: Server aodh/node-5 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>Sep  7 19:58:23 node-2 haproxy[6276]: proxy aodh has no server available!
<129>Sep  7 19:58:23 node-2 haproxy[6276]: 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>Sep  7 19:58:23 node-2 haproxy[6276]: 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>Sep  7 19:58:23 node-2 haproxy[6276]: Server ceilometer/node-5 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>Sep  7 19:58:23 node-2 haproxy[6276]: proxy ceilometer has no server available!
<27>Sep  7 19:58:24 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:24 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:24 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:24 node-2 multipathd: uevent trigger error
<129>Sep  7 19:58:27 node-2 haproxy[7849]: 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>Sep  7 19:58:27 node-2 haproxy[7849]: Server horizon/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>Sep  7 19:58:27 node-2 haproxy[7849]: 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>Sep  7 19:58:27 node-2 haproxy[7849]: Server keystone-1/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>Sep  7 19:58:27 node-2 haproxy[7849]: Server keystone-1/node-5 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>Sep  7 19:58:27 node-2 haproxy[7849]: proxy keystone-1 has no server available!
<129>Sep  7 19:58:27 node-2 haproxy[7849]: 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>Sep  7 19:58:27 node-2 haproxy[7849]: Server keystone-2/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>Sep  7 19:58:27 node-2 haproxy[7849]: Server keystone-2/node-5 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>Sep  7 19:58:27 node-2 haproxy[7849]: proxy keystone-2 has no server available!
<129>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: Server glance-api/node-5 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>Sep  7 19:58:28 node-2 haproxy[7853]: proxy glance-api has no server available!
<129>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: Server glance-glare/node-5 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>Sep  7 19:58:28 node-2 haproxy[7853]: proxy glance-glare has no server available!
<129>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: Server neutron/node-5 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>Sep  7 19:58:28 node-2 haproxy[7853]: proxy neutron has no server available!
<129>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: Server glance-registry/node-5 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>Sep  7 19:58:28 node-2 haproxy[7853]: proxy glance-registry has no server available!
<129>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: Backup Server mysqld/node-5 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>Sep  7 19:58:28 node-2 haproxy[7853]: proxy mysqld has no server available!
<129>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:28 node-2 haproxy[7853]: 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>Sep  7 19:58:29 node-2 haproxy[7853]: Server object-storage/node-5 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>Sep  7 19:58:29 node-2 haproxy[7853]: proxy object-storage has no server available!
<129>Sep  7 19:58:29 node-2 haproxy[7853]: 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>Sep  7 19:58:29 node-2 haproxy[7853]: 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>Sep  7 19:58:29 node-2 haproxy[7853]: Server aodh/node-5 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>Sep  7 19:58:29 node-2 haproxy[7853]: proxy aodh has no server available!
<129>Sep  7 19:58:29 node-2 haproxy[7853]: 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>Sep  7 19:58:29 node-2 haproxy[7853]: 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>Sep  7 19:58:29 node-2 haproxy[7853]: Server ceilometer/node-5 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>Sep  7 19:58:29 node-2 haproxy[7853]: proxy ceilometer has no server available!
<27>Sep  7 19:58:30 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:30 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:30 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:30 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:30 node-2 multipathd: uevent trigger error
<129>Sep  7 19:58:33 node-2 haproxy[9281]: 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>Sep  7 19:58:33 node-2 haproxy[9281]: 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>Sep  7 19:58:33 node-2 haproxy[9281]: Server keystone-1/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>Sep  7 19:58:33 node-2 haproxy[9281]: Server keystone-1/node-5 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>Sep  7 19:58:33 node-2 haproxy[9281]: proxy keystone-1 has no server available!
<129>Sep  7 19:58:33 node-2 haproxy[9281]: 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>Sep  7 19:58:33 node-2 haproxy[9281]: 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>Sep  7 19:58:33 node-2 haproxy[9281]: Server keystone-2/node-5 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>Sep  7 19:58:33 node-2 haproxy[9281]: proxy keystone-2 has no server available!
<129>Sep  7 19:58:33 node-2 haproxy[9281]: 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>Sep  7 19:58:33 node-2 haproxy[9281]: 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>Sep  7 19:58:33 node-2 haproxy[9281]: Server nova-api/node-5 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>Sep  7 19:58:33 node-2 haproxy[9281]: proxy nova-api has no server available!
<129>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: Server nova-metadata-api/node-5 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>Sep  7 19:58:34 node-2 haproxy[9285]: proxy nova-metadata-api has no server available!
<129>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: Server glance-api/node-5 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>Sep  7 19:58:34 node-2 haproxy[9285]: proxy glance-api has no server available!
<129>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: Server glance-glare/node-5 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>Sep  7 19:58:34 node-2 haproxy[9285]: proxy glance-glare has no server available!
<129>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: Server neutron/node-5 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>Sep  7 19:58:34 node-2 haproxy[9285]: proxy neutron has no server available!
<129>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: Server glance-registry/node-5 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>Sep  7 19:58:34 node-2 haproxy[9285]: proxy glance-registry has no server available!
<129>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: Backup Server mysqld/node-5 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>Sep  7 19:58:34 node-2 haproxy[9285]: proxy mysqld has no server available!
<129>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:34 node-2 haproxy[9285]: Server object-storage/node-5 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>Sep  7 19:58:34 node-2 haproxy[9285]: proxy object-storage has no server available!
<129>Sep  7 19:58:34 node-2 haproxy[9285]: 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>Sep  7 19:58:35 node-2 haproxy[9285]: 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>Sep  7 19:58:35 node-2 haproxy[9285]: Server aodh/node-5 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>Sep  7 19:58:35 node-2 haproxy[9285]: proxy aodh has no server available!
<129>Sep  7 19:58:35 node-2 haproxy[9285]: 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>Sep  7 19:58:35 node-2 haproxy[9285]: 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>Sep  7 19:58:35 node-2 haproxy[9285]: Server ceilometer/node-5 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>Sep  7 19:58:35 node-2 haproxy[9285]: proxy ceilometer has no server available!
<129>Sep  7 19:58:35 node-2 haproxy[9285]: 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>Sep  7 19:58:35 node-2 haproxy[9285]: 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>Sep  7 19:58:35 node-2 haproxy[9285]: Server nova-novncproxy/node-5 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>Sep  7 19:58:35 node-2 haproxy[9285]: proxy nova-novncproxy has no server available!
<27>Sep  7 19:58:36 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:36 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:36 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:36 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:36 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:36 node-2 multipathd: uevent trigger error
<129>Sep  7 19:58:39 node-2 haproxy[10832]: 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>Sep  7 19:58:39 node-2 haproxy[10832]: 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>Sep  7 19:58:39 node-2 haproxy[10832]: Server keystone-1/node-5 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>Sep  7 19:58:39 node-2 haproxy[10832]: proxy keystone-1 has no server available!
<129>Sep  7 19:58:39 node-2 haproxy[10832]: 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>Sep  7 19:58:39 node-2 haproxy[10832]: 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>Sep  7 19:58:39 node-2 haproxy[10832]: Server keystone-2/node-5 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>Sep  7 19:58:39 node-2 haproxy[10832]: proxy keystone-2 has no server available!
<129>Sep  7 19:58:39 node-2 haproxy[10832]: 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>Sep  7 19:58:39 node-2 haproxy[10832]: 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>Sep  7 19:58:39 node-2 haproxy[10832]: Server nova-api/node-5 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>Sep  7 19:58:39 node-2 haproxy[10832]: proxy nova-api has no server available!
<129>Sep  7 19:58:39 node-2 haproxy[10832]: 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>Sep  7 19:58:39 node-2 haproxy[10832]: 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>Sep  7 19:58:39 node-2 haproxy[10832]: Server nova-metadata-api/node-5 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>Sep  7 19:58:39 node-2 haproxy[10832]: proxy nova-metadata-api has no server available!
<129>Sep  7 19:58:39 node-2 haproxy[10832]: 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>Sep  7 19:58:39 node-2 haproxy[10832]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: Backup Server cinder-api/node-5 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>Sep  7 19:58:40 node-2 haproxy[10844]: proxy cinder-api has no server available!
<129>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: Server glance-api/node-5 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>Sep  7 19:58:40 node-2 haproxy[10844]: proxy glance-api has no server available!
<129>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: Server glance-glare/node-5 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>Sep  7 19:58:40 node-2 haproxy[10844]: proxy glance-glare has no server available!
<129>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: Server neutron/node-5 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>Sep  7 19:58:40 node-2 haproxy[10844]: proxy neutron has no server available!
<129>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: Server glance-registry/node-5 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>Sep  7 19:58:40 node-2 haproxy[10844]: proxy glance-registry has no server available!
<129>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: Backup Server mysqld/node-5 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>Sep  7 19:58:40 node-2 haproxy[10844]: proxy mysqld has no server available!
<129>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: Server object-storage/node-5 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>Sep  7 19:58:40 node-2 haproxy[10844]: proxy object-storage has no server available!
<129>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: Server aodh/node-5 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>Sep  7 19:58:40 node-2 haproxy[10844]: proxy aodh has no server available!
<129>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:40 node-2 haproxy[10844]: 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>Sep  7 19:58:41 node-2 haproxy[10844]: Server ceilometer/node-5 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>Sep  7 19:58:41 node-2 haproxy[10844]: proxy ceilometer has no server available!
<129>Sep  7 19:58:41 node-2 haproxy[10844]: 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>Sep  7 19:58:41 node-2 haproxy[10844]: 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>Sep  7 19:58:41 node-2 haproxy[10844]: Server nova-novncproxy/node-5 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>Sep  7 19:58:41 node-2 haproxy[10844]: proxy nova-novncproxy has no server available!
<27>Sep  7 19:58:42 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:42 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:42 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:42 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:42 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:42 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:43 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: Server keystone-1/node-5 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>Sep  7 19:58:45 node-2 haproxy[12379]: proxy keystone-1 has no server available!
<129>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: Server keystone-2/node-5 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>Sep  7 19:58:45 node-2 haproxy[12379]: proxy keystone-2 has no server available!
<129>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: Server nova-api/node-5 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>Sep  7 19:58:45 node-2 haproxy[12379]: proxy nova-api has no server available!
<129>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: Server nova-metadata-api/node-5 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>Sep  7 19:58:45 node-2 haproxy[12379]: proxy nova-metadata-api has no server available!
<129>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: 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>Sep  7 19:58:45 node-2 haproxy[12379]: Backup Server cinder-api/node-5 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>Sep  7 19:58:45 node-2 haproxy[12379]: proxy cinder-api has no server available!
<129>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: Server glance-api/node-5 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>Sep  7 19:58:46 node-2 haproxy[12388]: proxy glance-api has no server available!
<129>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: Server glance-glare/node-5 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>Sep  7 19:58:46 node-2 haproxy[12388]: proxy glance-glare has no server available!
<129>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: Server neutron/node-5 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>Sep  7 19:58:46 node-2 haproxy[12388]: proxy neutron has no server available!
<129>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: Server glance-registry/node-5 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>Sep  7 19:58:46 node-2 haproxy[12388]: proxy glance-registry has no server available!
<129>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: Backup Server mysqld/node-5 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>Sep  7 19:58:46 node-2 haproxy[12388]: proxy mysqld has no server available!
<129>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: Server object-storage/node-5 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>Sep  7 19:58:46 node-2 haproxy[12388]: proxy object-storage has no server available!
<129>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: Server aodh/node-5 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>Sep  7 19:58:46 node-2 haproxy[12388]: proxy aodh has no server available!
<129>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: Server ceilometer/node-5 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>Sep  7 19:58:46 node-2 haproxy[12388]: proxy ceilometer has no server available!
<129>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:46 node-2 haproxy[12388]: Server heat-api/node-5 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>Sep  7 19:58:46 node-2 haproxy[12388]: proxy heat-api has no server available!
<129>Sep  7 19:58:46 node-2 haproxy[12388]: 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>Sep  7 19:58:47 node-2 haproxy[12388]: 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>Sep  7 19:58:47 node-2 haproxy[12388]: Server heat-api-cfn/node-5 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>Sep  7 19:58:47 node-2 haproxy[12388]: proxy heat-api-cfn has no server available!
<129>Sep  7 19:58:47 node-2 haproxy[12388]: 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>Sep  7 19:58:47 node-2 haproxy[12388]: 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>Sep  7 19:58:47 node-2 haproxy[12388]: Server heat-api-cloudwatch/node-5 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>Sep  7 19:58:47 node-2 haproxy[12388]: proxy heat-api-cloudwatch has no server available!
<129>Sep  7 19:58:47 node-2 haproxy[12388]: 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>Sep  7 19:58:47 node-2 haproxy[12388]: 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>Sep  7 19:58:47 node-2 haproxy[12388]: Server nova-novncproxy/node-5 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>Sep  7 19:58:47 node-2 haproxy[12388]: proxy nova-novncproxy has no server available!
<27>Sep  7 19:58:48 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:48 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:48 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:48 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:48 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:50 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  7 19:58:52 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:52 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:52 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:52 node-2 multipathd: uevent trigger error
<27>Sep  7 19:58:52 node-2 multipathd: uevent trigger error
<27>Sep  7 19:59:02 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep  7 19:59:27 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>Sep  7 19:59:29 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep  7 20:00:22 node-2 multipathd: uevent trigger error
<27>Sep  7 20:00:22 node-2 multipathd: uevent trigger error
<27>Sep  7 20:00:22 node-2 multipathd: uevent trigger error
<27>Sep  7 20:00:22 node-2 multipathd: uevent trigger error
<27>Sep  7 20:00:22 node-2 multipathd: uevent trigger error
<27>Sep  7 20:02:04 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 20:02:42 node-2 multipathd: uevent trigger error
<27>Sep  7 20:02:42 node-2 multipathd: uevent trigger error
<27>Sep  7 20:02:42 node-2 multipathd: uevent trigger error
<27>Sep  7 20:02:42 node-2 multipathd: uevent trigger error
<27>Sep  7 20:02:42 node-2 multipathd: uevent trigger error
<27>Sep  7 20:02:49 node-2 multipathd: uevent trigger error
<27>Sep  7 20:02:49 node-2 multipathd: uevent trigger error
<27>Sep  7 20:02:49 node-2 multipathd: uevent trigger error
<27>Sep  7 20:02:49 node-2 multipathd: uevent trigger error
<43>Sep  7 20:03:06 node-2 apache2_error [Wed Sep 07 20:03:02.550966 2016] [mpm_event:notice] [pid 24443:tid 140225473849216] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep  7 20:03:06 node-2 apache2_error [Wed Sep 07 20:03:02.551040 2016] [core:notice] [pid 24443:tid 140225473849216] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep  7 20:03:06 node-2 apache2_error [Wed Sep 07 20:03:06.014568 2016] [mpm_event:notice] [pid 24443:tid 140225473849216] AH00491: caught SIGTERM, shutting down
<27>Sep  7 20:03:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:16 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:16 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:16 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:16 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:16 node-2 multipathd: uevent trigger error
<43>Sep  7 20:03:17 node-2 apache2_error [Wed Sep 07 20:03:07.103471 2016] [mpm_worker:notice] [pid 24843:tid 139929924372352] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep  7 20:03:17 node-2 apache2_error [Wed Sep 07 20:03:07.103515 2016] [core:notice] [pid 24843:tid 139929924372352] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 20:03:19 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:19 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:19 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:19 node-2 multipathd: uevent trigger error
<27>Sep  7 20:03:19 node-2 multipathd: uevent trigger error
<43>Sep  7 20:04:37 node-2 apache2_error [Wed Sep 07 20:04:27.259787 2016] [mpm_worker:notice] [pid 24843:tid 139929924372352] AH00295: caught SIGTERM, shutting down
<43>Sep  7 20:04:37 node-2 apache2_error [Wed Sep 07 20:04:28.017236 2016] [mpm_worker:notice] [pid 6238:tid 139778331551616] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  7 20:04:37 node-2 apache2_error [Wed Sep 07 20:04:28.017275 2016] [core:notice] [pid 6238:tid 139778331551616] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 20:05:05 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep  7 20:05:17 node-2 apache2_error [Wed Sep 07 20:05:12.223165 2016] [mpm_worker:notice] [pid 6238:tid 139778331551616] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  7 20:05:17 node-2 apache2_error [Wed Sep 07 20:05:12.415220 2016] [mpm_worker:warn] [pid 6238:tid 139778331551616] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  7 20:05:17 node-2 apache2_error [Wed Sep 07 20:05:12.418099 2016] [mpm_worker:notice] [pid 6238:tid 139778331551616] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  7 20:05:17 node-2 apache2_error [Wed Sep 07 20:05:12.418119 2016] [core:notice] [pid 6238:tid 139778331551616] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 20:05:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:05:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:05:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:05:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:05:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:01 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:01 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:01 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:01 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:01 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:17 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:17 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:17 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:17 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:17 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:43 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:43 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:43 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:43 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:58 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:58 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:58 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:58 node-2 multipathd: uevent trigger error
<27>Sep  7 20:06:58 node-2 multipathd: uevent trigger error
<27>Sep  7 20:07:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:07:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:07:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:07:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:07:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:08:06 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 20:11:08 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 20:13:26 node-2 multipathd: uevent trigger error
<27>Sep  7 20:13:26 node-2 multipathd: uevent trigger error
<27>Sep  7 20:13:26 node-2 multipathd: uevent trigger error
<27>Sep  7 20:13:26 node-2 multipathd: uevent trigger error
<27>Sep  7 20:13:26 node-2 multipathd: uevent trigger error
<27>Sep  7 20:13:26 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:10 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 20:14:25 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:25 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:25 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:25 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:25 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:14:56 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:11 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 20:17:24 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:24 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:24 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:24 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:24 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:39 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:39 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:39 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:39 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:39 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:45 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:45 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:45 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:45 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:17:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:18:13 node-2 multipathd: uevent trigger error
<27>Sep  7 20:18:13 node-2 multipathd: uevent trigger error
<27>Sep  7 20:18:13 node-2 multipathd: uevent trigger error
<27>Sep  7 20:18:13 node-2 multipathd: uevent trigger error
<27>Sep  7 20:18:13 node-2 multipathd: uevent trigger error
<27>Sep  7 20:18:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:18:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:18:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:18:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:18:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:41 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:41 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:41 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:41 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:41 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:41 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:19:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:20:13 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 20:22:22 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:22 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:22 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:22 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:22 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:49 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:49 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:49 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:49 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:55 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:55 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:55 node-2 multipathd: uevent trigger error
<27>Sep  7 20:22:55 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:14 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 20:23:27 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:27 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:27 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:27 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:27 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:32 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:32 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:32 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:32 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:32 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:48 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:48 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:48 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:48 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:48 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:54 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:54 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:54 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:54 node-2 multipathd: uevent trigger error
<27>Sep  7 20:23:54 node-2 multipathd: uevent trigger error
<27>Sep  7 20:24:31 node-2 multipathd: uevent trigger error
<27>Sep  7 20:24:31 node-2 multipathd: uevent trigger error
<27>Sep  7 20:24:31 node-2 multipathd: uevent trigger error
<27>Sep  7 20:24:31 node-2 multipathd: uevent trigger error
<27>Sep  7 20:25:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:25:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:25:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:25:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:25:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:25:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:25:57 node-2 multipathd: uevent trigger error
<27>Sep  7 20:25:57 node-2 multipathd: uevent trigger error
<11>Sep  7 20:26:11 node-2 liberasurecode[3109]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:11 node-2 liberasurecode[3109]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:11 node-2 liberasurecode[3109]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:11 node-2 liberasurecode[3109]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:11 node-2 liberasurecode[3136]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:11 node-2 liberasurecode[3136]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:11 node-2 liberasurecode[3136]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:11 node-2 liberasurecode[3136]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:13 node-2 liberasurecode[3569]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:13 node-2 liberasurecode[3569]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:13 node-2 liberasurecode[3569]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:13 node-2 liberasurecode[3569]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep  7 20:26:16 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Sep  7 20:26:19 node-2 liberasurecode[4429]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4429]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4429]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4429]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4472]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4472]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4472]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4472]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4516]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4516]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4516]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4516]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4580]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4580]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4580]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4580]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4593]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4593]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4593]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4593]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4607]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4607]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4607]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:19 node-2 liberasurecode[4607]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:20 node-2 liberasurecode[4621]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:20 node-2 liberasurecode[4621]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:20 node-2 liberasurecode[4621]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:20 node-2 liberasurecode[4621]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:36 node-2 liberasurecode[7095]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:36 node-2 liberasurecode[7095]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:36 node-2 liberasurecode[7095]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:26:36 node-2 liberasurecode[7095]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep  7 20:26:45 node-2 multipathd: uevent trigger error
<27>Sep  7 20:26:45 node-2 multipathd: uevent trigger error
<27>Sep  7 20:26:45 node-2 multipathd: uevent trigger error
<27>Sep  7 20:26:45 node-2 multipathd: uevent trigger error
<43>Sep  7 20:27:38 node-2 apache2_error [Wed Sep 07 20:27:32.792499 2016] [mpm_worker:notice] [pid 6238:tid 139778331551616] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  7 20:27:38 node-2 apache2_error [Wed Sep 07 20:27:33.177036 2016] [mpm_worker:warn] [pid 6238:tid 139778331551616] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  7 20:27:38 node-2 apache2_error [Wed Sep 07 20:27:33.182439 2016] [mpm_worker:notice] [pid 6238:tid 139778331551616] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  7 20:27:38 node-2 apache2_error [Wed Sep 07 20:27:33.182464 2016] [core:notice] [pid 6238:tid 139778331551616] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 20:28:14 node-2 multipathd: uevent trigger error
<27>Sep  7 20:28:14 node-2 multipathd: uevent trigger error
<27>Sep  7 20:28:14 node-2 multipathd: uevent trigger error
<27>Sep  7 20:28:14 node-2 multipathd: uevent trigger error
<43>Sep  7 20:28:18 node-2 apache2_error [Wed Sep 07 20:28:10.179112 2016] [mpm_worker:notice] [pid 6238:tid 139778331551616] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  7 20:28:18 node-2 apache2_error [Wed Sep 07 20:28:10.375776 2016] [mpm_worker:warn] [pid 6238:tid 139778331551616] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  7 20:28:18 node-2 apache2_error [Wed Sep 07 20:28:10.385612 2016] [mpm_worker:notice] [pid 6238:tid 139778331551616] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  7 20:28:18 node-2 apache2_error [Wed Sep 07 20:28:10.385643 2016] [core:notice] [pid 6238:tid 139778331551616] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 20:28:21 node-2 multipathd: uevent trigger error
<27>Sep  7 20:28:21 node-2 multipathd: uevent trigger error
<27>Sep  7 20:28:21 node-2 multipathd: uevent trigger error
<27>Sep  7 20:28:21 node-2 multipathd: uevent trigger error
<27>Sep  7 20:28:21 node-2 multipathd: uevent trigger error
<27>Sep  7 20:28:21 node-2 multipathd: uevent trigger error
<43>Sep  7 20:28:59 node-2 apache2_error [Wed Sep 07 20:28:55.825121 2016] [mpm_worker:notice] [pid 6238:tid 139778331551616] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep  7 20:28:59 node-2 apache2_error [Wed Sep 07 20:28:56.019056 2016] [mpm_worker:warn] [pid 6238:tid 139778331551616] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep  7 20:28:59 node-2 apache2_error [Wed Sep 07 20:28:56.027275 2016] [mpm_worker:notice] [pid 6238:tid 139778331551616] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep  7 20:28:59 node-2 apache2_error [Wed Sep 07 20:28:56.027315 2016] [core:notice] [pid 6238:tid 139778331551616] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep  7 20:29:00 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:00 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:00 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:00 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:00 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:00 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:06 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:06 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:06 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:06 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:06 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:06 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:17 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:17 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:17 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:17 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:17 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:17 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep  7 20:29:31 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:31 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:31 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:31 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:31 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:52 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:59 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:59 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:59 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:59 node-2 multipathd: uevent trigger error
<27>Sep  7 20:29:59 node-2 multipathd: uevent trigger error
<11>Sep  7 20:30:01 node-2 liberasurecode[17616]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:30:01 node-2 liberasurecode[17616]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:30:01 node-2 liberasurecode[17616]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep  7 20:30:01 node-2 liberasurecode[17616]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep  7 20:30:07 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep  7 20:30:16 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:16 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:16 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:16 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:16 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:21 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:21 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:21 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:21 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:27 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:27 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:27 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:27 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:27 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:38 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:41 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep  7 20:30:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:30:51 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:07 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:07 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:07 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:07 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:07 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:07 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:18 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:18 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:18 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:18 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:18 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:23 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:23 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:23 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:23 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:23 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:31:36 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:06 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:06 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:06 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:06 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:11 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:15 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:15 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:15 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:15 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:15 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:20 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:20 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:20 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:20 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:25 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:25 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:25 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:25 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:25 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:29 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:29 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:29 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:29 node-2 multipathd: uevent trigger error
<27>Sep  7 20:32:30 node-2 multipathd: uevent trigger error
