Oct  9 18:01:49 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8383" x-info="http://www.rsyslog.com"] start
Oct  9 18:01:49 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct  9 18:01:49 node-2 rsyslogd: rsyslogd's groupid changed to 104
Oct  9 18:01:49 node-2 rsyslogd: rsyslogd's userid changed to 101
Oct  9 18:01:49 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct  9 18:01:49 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct  9 18:01:49 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct  9 18:01:49 node-2 kernel: [    0.000000] Linux version 3.13.0-96-generic (buildd@lcy01-09) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 (Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39)
Oct  9 18:01:49 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=38d9f080-1c97-4a0f-b180-1e9822b020eb nomdmonddf nomdmonisw
Oct  9 18:01:49 node-2 kernel: [    0.000000] KERNEL supported cpus:
Oct  9 18:01:49 node-2 kernel: [    0.000000]   Intel GenuineIntel
Oct  9 18:01:49 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Oct  9 18:01:49 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Oct  9 18:01:49 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct  9 18:01:49 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct  9 18:01:49 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct  9 18:01:49 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Oct  9 18:01:49 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
Oct  9 18:01:49 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct  9 18:01:49 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct  9 18:01:49 node-2 kernel: [    0.000000] No AGP bridge found
Oct  9 18:01:49 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct  9 18:01:49 node-2 kernel: [    0.000000] MTRR default type: write-back
Oct  9 18:01:49 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct  9 18:01:49 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Oct  9 18:01:49 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct  9 18:01:49 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct  9 18:01:49 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Oct  9 18:01:49 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct  9 18:01:49 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct  9 18:01:49 node-2 kernel: [    0.000000]   2 disabled
Oct  9 18:01:49 node-2 kernel: [    0.000000]   3 disabled
Oct  9 18:01:49 node-2 kernel: [    0.000000]   4 disabled
Oct  9 18:01:49 node-2 kernel: [    0.000000]   5 disabled
Oct  9 18:01:49 node-2 kernel: [    0.000000]   6 disabled
Oct  9 18:01:49 node-2 kernel: [    0.000000]   7 disabled
Oct  9 18:01:49 node-2 kernel: [    0.000000]   8 disabled
Oct  9 18:01:49 node-2 kernel: [    0.000000]   9 disabled
Oct  9 18:01:49 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct  9 18:01:49 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct  9 18:01:49 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct  9 18:01:49 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct  9 18:01:49 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct  9 18:01:49 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Oct  9 18:01:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct  9 18:01:49 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct  9 18:01:49 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct  9 18:01:49 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct  9 18:01:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct  9 18:01:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct  9 18:01:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct  9 18:01:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct  9 18:01:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct  9 18:01:49 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct  9 18:01:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct  9 18:01:49 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct  9 18:01:49 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct  9 18:01:49 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct  9 18:01:49 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct  9 18:01:49 node-2 kernel: [    0.000000] Zone ranges:
Oct  9 18:01:49 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] Movable zone start for each node
Oct  9 18:01:49 node-2 kernel: [    0.000000] Early memory node ranges
Oct  9 18:01:49 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct  9 18:01:49 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct  9 18:01:49 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct  9 18:01:49 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct  9 18:01:49 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct  9 18:01:49 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct  9 18:01:49 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct  9 18:01:49 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct  9 18:01:49 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct  9 18:01:49 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct  9 18:01:49 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct  9 18:01:49 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct  9 18:01:49 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct  9 18:01:49 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct  9 18:01:49 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct  9 18:01:49 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct  9 18:01:49 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct  9 18:01:49 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct  9 18:01:49 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct  9 18:01:49 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct  9 18:01:49 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct  9 18:01:49 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct  9 18:01:49 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct  9 18:01:49 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 
Oct  9 18:01:49 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct  9 18:01:49 node-2 kernel: [    0.000000] Policy zone: Normal
Oct  9 18:01:49 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-96-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=38d9f080-1c97-4a0f-b180-1e9822b020eb nomdmonddf nomdmonisw
Oct  9 18:01:49 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct  9 18:01:49 node-2 kernel: [    0.000000] Checking aperture...
Oct  9 18:01:49 node-2 kernel: [    0.000000] No AGP bridge found
Oct  9 18:01:49 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct  9 18:01:49 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct  9 18:01:49 node-2 kernel: [    0.000000] Memory: 32653320K/33280496K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Oct  9 18:01:49 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct  9 18:01:49 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Oct  9 18:01:49 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct  9 18:01:49 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct  9 18:01:49 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct  9 18:01:49 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct  9 18:01:49 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct  9 18:01:49 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Oct  9 18:01:49 node-2 kernel: [    0.000000] console [tty0] enabled
Oct  9 18:01:49 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct  9 18:01:49 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct  9 18:01:49 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct  9 18:01:49 node-2 kernel: [    0.000000] hpet clockevent registered
Oct  9 18:01:49 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct  9 18:01:49 node-2 kernel: [    0.004000] tsc: Detected 3491.560 MHz processor
Oct  9 18:01:49 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.12 BogoMIPS (lpj=13966240)
Oct  9 18:01:49 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct  9 18:01:49 node-2 kernel: [    0.000044] Security Framework initialized
Oct  9 18:01:49 node-2 kernel: [    0.000062] AppArmor: AppArmor initialized
Oct  9 18:01:49 node-2 kernel: [    0.000064] Yama: becoming mindful.
Oct  9 18:01:49 node-2 kernel: [    0.001458] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.006337] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.008266] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.008294] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.008586] Initializing cgroup subsys memory
Oct  9 18:01:49 node-2 kernel: [    0.008595] Initializing cgroup subsys devices
Oct  9 18:01:49 node-2 kernel: [    0.008596] Initializing cgroup subsys freezer
Oct  9 18:01:49 node-2 kernel: [    0.008598] Initializing cgroup subsys blkio
Oct  9 18:01:49 node-2 kernel: [    0.008600] Initializing cgroup subsys perf_event
Oct  9 18:01:49 node-2 kernel: [    0.008602] Initializing cgroup subsys hugetlb
Oct  9 18:01:49 node-2 kernel: [    0.008622] CPU: Physical Processor ID: 0
Oct  9 18:01:49 node-2 kernel: [    0.008623] CPU: Processor Core ID: 0
Oct  9 18:01:49 node-2 kernel: [    0.008627] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct  9 18:01:49 node-2 kernel: [    0.008627] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct  9 18:01:49 node-2 kernel: [    0.009320] mce: CPU supports 22 MCE banks
Oct  9 18:01:49 node-2 kernel: [    0.009348] CPU0: Thermal monitoring enabled (TM1)
Oct  9 18:01:49 node-2 kernel: [    0.009368] process: using mwait in idle threads
Oct  9 18:01:49 node-2 kernel: [    0.009371] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct  9 18:01:49 node-2 kernel: [    0.009371] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct  9 18:01:49 node-2 kernel: [    0.009371] tlb_flushall_shift: 6
Oct  9 18:01:49 node-2 kernel: [    0.009460] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct  9 18:01:49 node-2 kernel: [    0.010181] ACPI: Core revision 20131115
Oct  9 18:01:49 node-2 kernel: [    0.022853] ACPI: All ACPI Tables successfully acquired
Oct  9 18:01:49 node-2 kernel: [    0.023013] ftrace: allocating 28614 entries in 112 pages
Oct  9 18:01:49 node-2 kernel: [    0.031713] dmar: Host address width 46
Oct  9 18:01:49 node-2 kernel: [    0.031715] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct  9 18:01:49 node-2 kernel: [    0.031721] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  9 18:01:49 node-2 kernel: [    0.031723] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct  9 18:01:49 node-2 kernel: [    0.031726] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  9 18:01:49 node-2 kernel: [    0.031728] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct  9 18:01:49 node-2 kernel: [    0.031729] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct  9 18:01:49 node-2 kernel: [    0.031730] dmar: ATSR flags: 0x0
Oct  9 18:01:49 node-2 kernel: [    0.031731] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct  9 18:01:49 node-2 kernel: [    0.031733] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct  9 18:01:49 node-2 kernel: [    0.031848] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct  9 18:01:49 node-2 kernel: [    0.031850] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct  9 18:01:49 node-2 kernel: [    0.031851] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct  9 18:01:49 node-2 kernel: [    0.031852] HPET id 0 under DRHD base 0xc7ffc000
Oct  9 18:01:49 node-2 kernel: [    0.031853] Your BIOS is broken and requested that x2apic be disabled.
Oct  9 18:01:49 node-2 kernel: [    0.031853] This will slightly decrease performance.
Oct  9 18:01:49 node-2 kernel: [    0.031853] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct  9 18:01:49 node-2 kernel: [    0.032284] Enabled IRQ remapping in xapic mode
Oct  9 18:01:49 node-2 kernel: [    0.032285] x2apic not enabled, IRQ remapping is in xapic mode
Oct  9 18:01:49 node-2 kernel: [    0.032288] Switched APIC routing to physical flat.
Oct  9 18:01:49 node-2 kernel: [    0.032910] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct  9 18:01:49 node-2 kernel: [    0.072556] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct  9 18:01:49 node-2 kernel: [    0.072561] TSC deadline timer enabled
Oct  9 18:01:49 node-2 kernel: [    0.072568] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct  9 18:01:49 node-2 kernel: [    0.072574] ... version:                3
Oct  9 18:01:49 node-2 kernel: [    0.072575] ... bit width:              48
Oct  9 18:01:49 node-2 kernel: [    0.072576] ... generic registers:      4
Oct  9 18:01:49 node-2 kernel: [    0.072577] ... value mask:             0000ffffffffffff
Oct  9 18:01:49 node-2 kernel: [    0.072578] ... max period:             0000ffffffffffff
Oct  9 18:01:49 node-2 kernel: [    0.072579] ... fixed-purpose events:   3
Oct  9 18:01:49 node-2 kernel: [    0.072580] ... event mask:             000000070000000f
Oct  9 18:01:49 node-2 kernel: [    0.073960] x86: Booting SMP configuration:
Oct  9 18:01:49 node-2 kernel: [    0.088064] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct  9 18:01:49 node-2 kernel: [    0.073962] .... node  #0, CPUs:        #1  #2  #3
Oct  9 18:01:49 node-2 kernel: [    0.115962] .... node  #1, CPUs:    #4  #5  #6  #7
Oct  9 18:01:49 node-2 kernel: [    0.270086] .... node  #0, CPUs:    #8  #9 #10 #11
Oct  9 18:01:49 node-2 kernel: [    0.325702] .... node  #1, CPUs:   #12 #13 #14 #15
Oct  9 18:01:49 node-2 kernel: [    0.382753] x86: Booted up 2 nodes, 16 CPUs
Oct  9 18:01:49 node-2 kernel: [    0.382756] smpboot: Total of 16 processors activated (111742.77 BogoMIPS)
Oct  9 18:01:49 node-2 kernel: [    0.407824] devtmpfs: initialized
Oct  9 18:01:49 node-2 kernel: [    0.410176] EVM: security.selinux
Oct  9 18:01:49 node-2 kernel: [    0.410178] EVM: security.SMACK64
Oct  9 18:01:49 node-2 kernel: [    0.410179] EVM: security.ima
Oct  9 18:01:49 node-2 kernel: [    0.410179] EVM: security.capability
Oct  9 18:01:49 node-2 kernel: [    0.410232] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.410893] pinctrl core: initialized pinctrl subsystem
Oct  9 18:01:49 node-2 kernel: [    0.410955] regulator-dummy: no parameters
Oct  9 18:01:49 node-2 kernel: [    0.410987] RTC time: 18:01:13, date: 10/09/16
Oct  9 18:01:49 node-2 kernel: [    0.411021] NET: Registered protocol family 16
Oct  9 18:01:49 node-2 kernel: [    0.411106] cpuidle: using governor ladder
Oct  9 18:01:49 node-2 kernel: [    0.411107] cpuidle: using governor menu
Oct  9 18:01:49 node-2 kernel: [    0.411142] ACPI: bus type PCI registered
Oct  9 18:01:49 node-2 kernel: [    0.411144] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct  9 18:01:49 node-2 kernel: [    0.411192] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct  9 18:01:49 node-2 kernel: [    0.411194] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct  9 18:01:49 node-2 kernel: [    0.424936] PCI: Using configuration type 1 for base access
Oct  9 18:01:49 node-2 kernel: [    0.425935] bio: create slab <bio-0> at 0
Oct  9 18:01:49 node-2 kernel: [    0.426247] ACPI: Added _OSI(Module Device)
Oct  9 18:01:49 node-2 kernel: [    0.426248] ACPI: Added _OSI(Processor Device)
Oct  9 18:01:49 node-2 kernel: [    0.426249] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct  9 18:01:49 node-2 kernel: [    0.426251] ACPI: Added _OSI(Processor Aggregator Device)
Oct  9 18:01:49 node-2 kernel: [    0.439057] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct  9 18:01:49 node-2 kernel: [    0.449522] ACPI: Interpreter enabled
Oct  9 18:01:49 node-2 kernel: [    0.449527] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct  9 18:01:49 node-2 kernel: [    0.449531] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct  9 18:01:49 node-2 kernel: [    0.449534] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct  9 18:01:49 node-2 kernel: [    0.449541] ACPI: (supports S0 S4 S5)
Oct  9 18:01:49 node-2 kernel: [    0.449542] ACPI: Using IOAPIC for interrupt routing
Oct  9 18:01:49 node-2 kernel: [    0.449585] HEST: Table parsing has been initialized.
Oct  9 18:01:49 node-2 kernel: [    0.449587] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct  9 18:01:49 node-2 kernel: [    0.450145] ACPI: No dock devices found.
Oct  9 18:01:49 node-2 kernel: [    0.461856] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct  9 18:01:49 node-2 kernel: [    0.461861] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  9 18:01:49 node-2 kernel: [    0.461864] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  9 18:01:49 node-2 kernel: [    0.461891] PCI host bridge to bus 0000:ff
Oct  9 18:01:49 node-2 kernel: [    0.461893] pci_bus 0000:ff: root bus resource [bus ff]
Oct  9 18:01:49 node-2 kernel: [    0.461901] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.461939] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.461971] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462006] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462035] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.462065] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.462095] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462124] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462154] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462182] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462209] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462235] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462264] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462290] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462317] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462344] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462372] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462400] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462427] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.462457] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462482] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.462508] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462534] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462565] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.462600] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462631] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462661] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462692] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462724] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462755] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462786] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462817] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462847] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462878] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462911] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462944] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.462978] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463008] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463036] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463069] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463102] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463139] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463173] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463205] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463236] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463265] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463295] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463324] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463355] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463386] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463417] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463446] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463474] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463503] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463532] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463563] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463595] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463652] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct  9 18:01:49 node-2 kernel: [    0.463654] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  9 18:01:49 node-2 kernel: [    0.463657] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  9 18:01:49 node-2 kernel: [    0.463675] PCI host bridge to bus 0000:7f
Oct  9 18:01:49 node-2 kernel: [    0.463677] pci_bus 0000:7f: root bus resource [bus 7f]
Oct  9 18:01:49 node-2 kernel: [    0.463682] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463708] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.463736] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463766] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463788] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.463812] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.463841] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463868] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463892] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463916] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463941] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463965] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.463990] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464014] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464039] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464068] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464089] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464112] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464135] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.464158] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464180] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.464202] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464224] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464250] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct  9 18:01:49 node-2 kernel: [    0.464283] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464309] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464335] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464363] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464388] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464414] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464440] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464467] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464492] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464520] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464547] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464575] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464603] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464629] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464655] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464684] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464710] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464736] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464765] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464791] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464817] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464843] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464869] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464895] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464920] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464946] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.464975] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.465000] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.465022] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.465047] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.465072] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.465102] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.465127] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.466371] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct  9 18:01:49 node-2 kernel: [    0.466375] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  9 18:01:49 node-2 kernel: [    0.467514] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  9 18:01:49 node-2 kernel: [    0.468029] PCI host bridge to bus 0000:00
Oct  9 18:01:49 node-2 kernel: [    0.468031] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct  9 18:01:49 node-2 kernel: [    0.468033] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct  9 18:01:49 node-2 kernel: [    0.468034] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct  9 18:01:49 node-2 kernel: [    0.468036] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct  9 18:01:49 node-2 kernel: [    0.468037] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct  9 18:01:49 node-2 kernel: [    0.468038] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct  9 18:01:49 node-2 kernel: [    0.468040] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct  9 18:01:49 node-2 kernel: [    0.468046] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct  9 18:01:49 node-2 kernel: [    0.468128] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.468159] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.468201] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct  9 18:01:49 node-2 kernel: [    0.468223] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.468252] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.468293] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct  9 18:01:49 node-2 kernel: [    0.468312] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.468342] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.468382] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct  9 18:01:49 node-2 kernel: [    0.468400] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.468469] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.468546] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.468623] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct  9 18:01:49 node-2 kernel: [    0.468628] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct  9 18:01:49 node-2 kernel: [    0.468714] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct  9 18:01:49 node-2 kernel: [    0.468864] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct  9 18:01:49 node-2 kernel: [    0.468882] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct  9 18:01:49 node-2 kernel: [    0.468959] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.469013] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct  9 18:01:49 node-2 kernel: [    0.469036] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.469091] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.469135] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct  9 18:01:49 node-2 kernel: [    0.469164] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.469220] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.469263] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct  9 18:01:49 node-2 kernel: [    0.469286] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct  9 18:01:49 node-2 kernel: [    0.469304] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct  9 18:01:49 node-2 kernel: [    0.469382] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.469432] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct  9 18:01:49 node-2 kernel: [    0.469459] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct  9 18:01:49 node-2 kernel: [    0.469709] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct  9 18:01:49 node-2 kernel: [    0.469715] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct  9 18:01:49 node-2 kernel: [    0.469721] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.469727] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.469734] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct  9 18:01:49 node-2 kernel: [    0.469765] pci 0000:01:00.0: supports D1 D2
Oct  9 18:01:49 node-2 kernel: [    0.479851] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  9 18:01:49 node-2 kernel: [    0.479854] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  9 18:01:49 node-2 kernel: [    0.479856] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  9 18:01:49 node-2 kernel: [    0.479965] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.479999] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct  9 18:01:49 node-2 kernel: [    0.487858] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  9 18:01:49 node-2 kernel: [    0.487864] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.487868] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:49 node-2 kernel: [    0.487953] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.488026] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.488121] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.488203] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  9 18:01:49 node-2 kernel: [    0.488206] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.488208] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:49 node-2 kernel: [    0.488260] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.488420] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.488475] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  9 18:01:49 node-2 kernel: [    0.488478] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.488480] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:49 node-2 kernel: [    0.488531] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.488655] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.488697] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.488823] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.488863] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.488986] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.489029] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct  9 18:01:49 node-2 kernel: [    0.489150] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:49 node-2 kernel: [    0.489193] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  9 18:01:49 node-2 kernel: [    0.489195] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.489197] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:49 node-2 kernel: [    0.489257] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct  9 18:01:49 node-2 kernel: [    0.489324] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.489404] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.489444] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct  9 18:01:49 node-2 kernel: [    0.489523] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct  9 18:01:49 node-2 kernel: [    0.489634] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  9 18:01:49 node-2 kernel: [    0.489637] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.489639] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  9 18:01:49 node-2 kernel: [    0.489695] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct  9 18:01:49 node-2 kernel: [    0.489749] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.489798] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.490014] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  9 18:01:49 node-2 kernel: [    0.490017] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  9 18:01:49 node-2 kernel: [    0.490081] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct  9 18:01:49 node-2 kernel: [    0.490134] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.490182] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.490413] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  9 18:01:49 node-2 kernel: [    0.490417] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  9 18:01:49 node-2 kernel: [    0.490476] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct  9 18:01:49 node-2 kernel: [    0.490539] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.490591] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct  9 18:01:49 node-2 kernel: [    0.490814] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  9 18:01:49 node-2 kernel: [    0.490817] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  9 18:01:49 node-2 kernel: [    0.490995] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  9 18:01:49 node-2 kernel: [    0.491034] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  9 18:01:49 node-2 kernel: [    0.491113] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct  9 18:01:49 node-2 kernel: [    0.491131] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct  9 18:01:49 node-2 kernel: [    0.491145] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct  9 18:01:49 node-2 kernel: [    0.491158] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct  9 18:01:49 node-2 kernel: [    0.491208] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct  9 18:01:49 node-2 kernel: [    0.495862] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  9 18:01:49 node-2 kernel: [    0.495871] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  9 18:01:49 node-2 kernel: [    0.495924] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct  9 18:01:49 node-2 kernel: [    0.496442] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct  9 18:01:49 node-2 kernel: [    0.496445] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  9 18:01:49 node-2 kernel: [    0.496565] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  9 18:01:49 node-2 kernel: [    0.496674] PCI host bridge to bus 0000:80
Oct  9 18:01:49 node-2 kernel: [    0.496676] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct  9 18:01:49 node-2 kernel: [    0.496678] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct  9 18:01:49 node-2 kernel: [    0.496679] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct  9 18:01:49 node-2 kernel: [    0.496687] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.496751] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.496819] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct  9 18:01:49 node-2 kernel: [    0.496882] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct  9 18:01:49 node-2 kernel: [    0.496887] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct  9 18:01:49 node-2 kernel: [    0.496959] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct  9 18:01:49 node-2 kernel: [    0.497258] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct  9 18:01:49 node-2 kernel: [    0.497289] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct  9 18:01:49 node-2 kernel: [    0.497319] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct  9 18:01:49 node-2 kernel: [    0.497348] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct  9 18:01:49 node-2 kernel: [    0.497378] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  9 18:01:49 node-2 kernel: [    0.497408] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  9 18:01:49 node-2 kernel: [    0.497438] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  9 18:01:49 node-2 kernel: [    0.497468] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  9 18:01:49 node-2 kernel: [    0.497554] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct  9 18:01:49 node-2 kernel: [    0.497558] ACPI: \_SB_.UNC1: notify handler is installed
Oct  9 18:01:49 node-2 kernel: [    0.497560] ACPI: \_SB_.UNC0: notify handler is installed
Oct  9 18:01:49 node-2 kernel: [    0.497575] ACPI: \_SB_.PCI0: notify handler is installed
Oct  9 18:01:49 node-2 kernel: [    0.497627] ACPI: \_SB_.PCI1: notify handler is installed
Oct  9 18:01:49 node-2 kernel: [    0.497707] Found 4 acpi root devices
Oct  9 18:01:49 node-2 kernel: [    0.497817] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct  9 18:01:49 node-2 kernel: [    0.497819] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct  9 18:01:49 node-2 kernel: [    0.497821] vgaarb: loaded
Oct  9 18:01:49 node-2 kernel: [    0.497822] vgaarb: bridge control possible 0000:0c:00.0
Oct  9 18:01:49 node-2 kernel: [    0.497941] SCSI subsystem initialized
Oct  9 18:01:49 node-2 kernel: [    0.498008] libata version 3.00 loaded.
Oct  9 18:01:49 node-2 kernel: [    0.498024] ACPI: bus type USB registered
Oct  9 18:01:49 node-2 kernel: [    0.498034] usbcore: registered new interface driver usbfs
Oct  9 18:01:49 node-2 kernel: [    0.498039] usbcore: registered new interface driver hub
Oct  9 18:01:49 node-2 kernel: [    0.498061] usbcore: registered new device driver usb
Oct  9 18:01:49 node-2 kernel: [    0.498241] PCI: Using ACPI for IRQ routing
Oct  9 18:01:49 node-2 kernel: [    0.501839] PCI: pci_cache_line_size set to 64 bytes
Oct  9 18:01:49 node-2 kernel: [    0.502045] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct  9 18:01:49 node-2 kernel: [    0.502047] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct  9 18:01:49 node-2 kernel: [    0.502047] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct  9 18:01:49 node-2 kernel: [    0.502113] NetLabel: Initializing
Oct  9 18:01:49 node-2 kernel: [    0.502114] NetLabel:  domain hash size = 128
Oct  9 18:01:49 node-2 kernel: [    0.502115] NetLabel:  protocols = UNLABELED CIPSOv4
Oct  9 18:01:49 node-2 kernel: [    0.502125] NetLabel:  unlabeled traffic allowed by default
Oct  9 18:01:49 node-2 kernel: [    0.502182] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct  9 18:01:49 node-2 kernel: [    0.502186] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct  9 18:01:49 node-2 kernel: [    0.504254] Switched to clocksource hpet
Oct  9 18:01:49 node-2 kernel: [    0.508131] AppArmor: AppArmor Filesystem Enabled
Oct  9 18:01:49 node-2 kernel: [    0.508145] pnp: PnP ACPI init
Oct  9 18:01:49 node-2 kernel: [    0.508151] ACPI: bus type PNP registered
Oct  9 18:01:49 node-2 kernel: [    0.508276] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct  9 18:01:49 node-2 kernel: [    0.508284] pnp 00:01: [dma 4]
Oct  9 18:01:49 node-2 kernel: [    0.508296] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct  9 18:01:49 node-2 kernel: [    0.508323] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct  9 18:01:49 node-2 kernel: [    0.508342] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct  9 18:01:49 node-2 kernel: [    0.508360] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct  9 18:01:49 node-2 kernel: [    0.508393] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct  9 18:01:49 node-2 kernel: [    0.508444] system 00:06: [io  0x0500-0x057f] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508447] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct  9 18:01:49 node-2 kernel: [    0.508448] system 00:06: [io  0x0580-0x059f] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508450] system 00:06: [io  0x0600-0x061f] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508451] system 00:06: [io  0x0880-0x0883] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508457] system 00:06: [io  0x0800-0x081f] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508460] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct  9 18:01:49 node-2 kernel: [    0.508461] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508463] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508464] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508466] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508467] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508469] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct  9 18:01:49 node-2 kernel: [    0.508471] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct  9 18:01:49 node-2 kernel: [    0.508555] pnp 00:07: [dma 0 disabled]
Oct  9 18:01:49 node-2 kernel: [    0.508584] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  9 18:01:49 node-2 kernel: [    0.508658] pnp 00:08: [dma 0 disabled]
Oct  9 18:01:49 node-2 kernel: [    0.508690] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  9 18:01:49 node-2 kernel: [    0.508740] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct  9 18:01:49 node-2 kernel: [    0.509091] pnp: PnP ACPI: found 10 devices
Oct  9 18:01:49 node-2 kernel: [    0.509093] ACPI: bus type PNP unregistered
Oct  9 18:01:49 node-2 kernel: [    0.515397] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  9 18:01:49 node-2 kernel: [    0.515400] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  9 18:01:49 node-2 kernel: [    0.515403] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  9 18:01:49 node-2 kernel: [    0.515407] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  9 18:01:49 node-2 kernel: [    0.515409] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.515427] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515456] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  9 18:01:49 node-2 kernel: [    0.515470] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515499] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  9 18:01:49 node-2 kernel: [    0.515514] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  9 18:01:49 node-2 kernel: [    0.515543] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  9 18:01:49 node-2 kernel: [    0.515557] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  9 18:01:49 node-2 kernel: [    0.515586] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  9 18:01:49 node-2 kernel: [    0.515588] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.515602] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515631] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  9 18:01:49 node-2 kernel: [    0.515633] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.515648] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515676] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  9 18:01:49 node-2 kernel: [    0.515678] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.515681] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515685] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  9 18:01:49 node-2 kernel: [    0.515687] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.515689] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515693] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  9 18:01:49 node-2 kernel: [    0.515698] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  9 18:01:49 node-2 kernel: [    0.515706] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  9 18:01:49 node-2 kernel: [    0.515709] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  9 18:01:49 node-2 kernel: [    0.515715] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct  9 18:01:49 node-2 kernel: [    0.515716] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct  9 18:01:49 node-2 kernel: [    0.515717] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct  9 18:01:49 node-2 kernel: [    0.515718] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct  9 18:01:49 node-2 kernel: [    0.515719] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct  9 18:01:49 node-2 kernel: [    0.515720] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct  9 18:01:49 node-2 kernel: [    0.515721] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct  9 18:01:49 node-2 kernel: [    0.515722] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct  9 18:01:49 node-2 kernel: [    0.515723] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.515724] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515725] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.515725] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515726] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.515727] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515728] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.515729] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515730] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct  9 18:01:49 node-2 kernel: [    0.515731] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515732] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct  9 18:01:49 node-2 kernel: [    0.515733] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct  9 18:01:49 node-2 kernel: [    0.515734] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct  9 18:01:49 node-2 kernel: [    0.515735] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct  9 18:01:49 node-2 kernel: [    0.515737] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct  9 18:01:49 node-2 kernel: [    0.515738] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct  9 18:01:49 node-2 kernel: [    0.515779] NET: Registered protocol family 2
Oct  9 18:01:49 node-2 kernel: [    0.516036] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.516376] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.516522] TCP: Hash tables configured (established 262144 bind 65536)
Oct  9 18:01:49 node-2 kernel: [    0.516564] TCP: reno registered
Oct  9 18:01:49 node-2 kernel: [    0.516594] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.516692] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.516837] NET: Registered protocol family 1
Oct  9 18:01:49 node-2 kernel: [    0.556355] pci 0000:0c:00.0: Video device with shadowed ROM
Oct  9 18:01:49 node-2 kernel: [    0.556369] PCI: CLS 64 bytes, default 64
Oct  9 18:01:49 node-2 kernel: [    0.556445] Trying to unpack rootfs image as initramfs...
Oct  9 18:01:49 node-2 kernel: [    0.775585] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Oct  9 18:01:49 node-2 kernel: [    0.775633] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct  9 18:01:49 node-2 kernel: [    0.775635] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct  9 18:01:49 node-2 kernel: [    0.776050] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776056] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776061] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776066] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776091] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776102] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776112] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776121] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776129] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776138] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776144] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776150] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776157] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776165] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776172] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776180] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:49 node-2 kernel: [    0.776258] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct  9 18:01:49 node-2 kernel: [    0.776261] Scanning for low memory corruption every 60 seconds
Oct  9 18:01:49 node-2 kernel: [    0.776640] Initialise system trusted keyring
Oct  9 18:01:49 node-2 kernel: [    0.776697] audit: initializing netlink socket (disabled)
Oct  9 18:01:49 node-2 kernel: [    0.776712] type=2000 audit(1476036073.728:1): initialized
Oct  9 18:01:49 node-2 kernel: [    0.794458] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct  9 18:01:49 node-2 kernel: [    0.795980] zbud: loaded
Oct  9 18:01:49 node-2 kernel: [    0.796119] VFS: Disk quotas dquot_6.5.2
Oct  9 18:01:49 node-2 kernel: [    0.796156] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct  9 18:01:49 node-2 kernel: [    0.796528] fuse init (API version 7.22)
Oct  9 18:01:49 node-2 kernel: [    0.796592] msgmni has been set to 32768
Oct  9 18:01:49 node-2 kernel: [    0.796644] Key type big_key registered
Oct  9 18:01:49 node-2 kernel: [    0.797182] Key type asymmetric registered
Oct  9 18:01:49 node-2 kernel: [    0.797184] Asymmetric key parser 'x509' registered
Oct  9 18:01:49 node-2 kernel: [    0.797206] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct  9 18:01:49 node-2 kernel: [    0.797274] io scheduler noop registered
Oct  9 18:01:49 node-2 kernel: [    0.797276] io scheduler deadline registered (default)
Oct  9 18:01:49 node-2 kernel: [    0.797296] io scheduler cfq registered
Oct  9 18:01:49 node-2 kernel: [    0.797813] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    0.797994] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    0.798110] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    0.798222] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    0.798338] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    0.798435] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    0.798842] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct  9 18:01:49 node-2 kernel: [    0.798882] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct  9 18:01:49 node-2 kernel: [    0.798909] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct  9 18:01:49 node-2 kernel: [    0.798927] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798932] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798938] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct  9 18:01:49 node-2 kernel: [    0.798949] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798953] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798956] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798960] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798964] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798967] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798971] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798975] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798979] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798982] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798986] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798990] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.798995] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct  9 18:01:49 node-2 kernel: [    0.799006] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.799011] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct  9 18:01:49 node-2 kernel: [    0.799044] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.799047] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct  9 18:01:49 node-2 kernel: [    0.799057] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.799059] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:49 node-2 kernel: [    0.799062] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct  9 18:01:49 node-2 kernel: [    0.799097] ioapic: probe of 0000:00:05.4 failed with error -22
Oct  9 18:01:49 node-2 kernel: [    0.799103] ioapic: probe of 0000:80:05.4 failed with error -22
Oct  9 18:01:49 node-2 kernel: [    0.799107] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct  9 18:01:49 node-2 kernel: [    0.799117] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct  9 18:01:49 node-2 kernel: [    0.799157] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct  9 18:01:49 node-2 kernel: [    0.799158] vesafb: scrolling: redraw
Oct  9 18:01:49 node-2 kernel: [    0.799160] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct  9 18:01:49 node-2 kernel: [    0.819618] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct  9 18:01:49 node-2 kernel: [    0.828128] Console: switching to colour frame buffer device 80x30
Oct  9 18:01:49 node-2 kernel: [    0.836799] fb0: VESA VGA frame buffer device
Oct  9 18:01:49 node-2 kernel: [    0.836994] intel_idle: MWAIT substates: 0x2120
Oct  9 18:01:49 node-2 kernel: [    0.836995] intel_idle: v0.4 model 0x3F
Oct  9 18:01:49 node-2 kernel: [    0.836996] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct  9 18:01:49 node-2 kernel: [    0.837221] ipmi message handler version 39.2
Oct  9 18:01:49 node-2 kernel: [    0.837493] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  9 18:01:49 node-2 kernel: [    0.837925] ACPI: AC Adapter [P111] (on-line)
Oct  9 18:01:49 node-2 kernel: [    0.843174] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct  9 18:01:49 node-2 kernel: [    0.854213] ACPI: Power Button [PWRB]
Oct  9 18:01:49 node-2 kernel: [    0.859983] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct  9 18:01:49 node-2 kernel: [    0.871644] ACPI: Power Button [PWRF]
Oct  9 18:01:49 node-2 kernel: [    0.897795] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct  9 18:01:49 node-2 kernel: [    0.909461] pstore: Registered erst as persistent store backend
Oct  9 18:01:49 node-2 kernel: [    0.915661] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct  9 18:01:49 node-2 kernel: [    0.927611] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct  9 18:01:49 node-2 kernel: [    0.954373] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct  9 18:01:49 node-2 kernel: [    0.987688] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct  9 18:01:49 node-2 kernel: [    1.001935] Linux agpgart interface v0.103
Oct  9 18:01:49 node-2 kernel: [    1.009629] brd: module loaded
Oct  9 18:01:49 node-2 kernel: [    1.016770] loop: module loaded
Oct  9 18:01:49 node-2 kernel: [    1.023498] libphy: Fixed MDIO Bus: probed
Oct  9 18:01:49 node-2 kernel: [    1.029987] tun: Universal TUN/TAP device driver, 1.6
Oct  9 18:01:49 node-2 kernel: [    1.036479] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct  9 18:01:49 node-2 kernel: [    1.043013] PPP generic driver version 2.4.2
Oct  9 18:01:49 node-2 kernel: [    1.049454] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct  9 18:01:49 node-2 kernel: [    1.055965] ehci-pci: EHCI PCI platform driver
Oct  9 18:01:49 node-2 kernel: [    1.062558] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct  9 18:01:49 node-2 kernel: [    1.069037] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct  9 18:01:49 node-2 kernel: [    1.081619] ehci-pci 0000:00:1a.0: debug port 2
Oct  9 18:01:49 node-2 kernel: [    1.091808] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct  9 18:01:49 node-2 kernel: [    1.091826] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct  9 18:01:49 node-2 kernel: [    1.107745] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct  9 18:01:49 node-2 kernel: [    1.113822] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct  9 18:01:49 node-2 kernel: [    1.119979] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  9 18:01:49 node-2 kernel: [    1.131865] usb usb1: Product: EHCI Host Controller
Oct  9 18:01:49 node-2 kernel: [    1.137892] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  9 18:01:49 node-2 kernel: [    1.143923] usb usb1: SerialNumber: 0000:00:1a.0
Oct  9 18:01:49 node-2 kernel: [    1.149880] hub 1-0:1.0: USB hub found
Oct  9 18:01:49 node-2 kernel: [    1.155640] hub 1-0:1.0: 2 ports detected
Oct  9 18:01:49 node-2 kernel: [    1.161434] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct  9 18:01:49 node-2 kernel: [    1.167015] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct  9 18:01:49 node-2 kernel: [    1.177912] ehci-pci 0000:00:1d.0: debug port 2
Oct  9 18:01:49 node-2 kernel: [    1.187272] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct  9 18:01:49 node-2 kernel: [    1.187275] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct  9 18:01:49 node-2 kernel: [    1.203663] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct  9 18:01:49 node-2 kernel: [    1.208863] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct  9 18:01:49 node-2 kernel: [    1.214162] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  9 18:01:49 node-2 kernel: [    1.224734] usb usb2: Product: EHCI Host Controller
Oct  9 18:01:49 node-2 kernel: [    1.230199] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  9 18:01:49 node-2 kernel: [    1.235751] usb usb2: SerialNumber: 0000:00:1d.0
Oct  9 18:01:49 node-2 kernel: [    1.241260] hub 2-0:1.0: USB hub found
Oct  9 18:01:49 node-2 kernel: [    1.246605] hub 2-0:1.0: 2 ports detected
Oct  9 18:01:49 node-2 kernel: [    1.251895] ehci-platform: EHCI generic platform driver
Oct  9 18:01:49 node-2 kernel: [    1.257127] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct  9 18:01:49 node-2 kernel: [    1.262435] ohci-pci: OHCI PCI platform driver
Oct  9 18:01:49 node-2 kernel: [    1.267745] ohci-platform: OHCI generic platform driver
Oct  9 18:01:49 node-2 kernel: [    1.272928] uhci_hcd: USB Universal Host Controller Interface driver
Oct  9 18:01:49 node-2 kernel: [    1.278257] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct  9 18:01:49 node-2 kernel: [    1.471441] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct  9 18:01:49 node-2 kernel: [    1.771193] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct  9 18:01:49 node-2 kernel: [    1.787584] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct  9 18:01:49 node-2 kernel: [    1.793180] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  9 18:01:49 node-2 kernel: [    1.798852] hub 1-1:1.0: USB hub found
Oct  9 18:01:49 node-2 kernel: [    1.804321] hub 1-1:1.0: 6 ports detected
Oct  9 18:01:49 node-2 kernel: [    1.919074] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct  9 18:01:49 node-2 kernel: [    2.316920] i8042: No controller found
Oct  9 18:01:49 node-2 kernel: [    2.322431] mousedev: PS/2 mouse device common for all mice
Oct  9 18:01:49 node-2 kernel: [    2.328149] rtc_cmos 00:02: RTC can wake from S4
Oct  9 18:01:49 node-2 kernel: [    2.331569] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct  9 18:01:49 node-2 kernel: [    2.331570] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  9 18:01:49 node-2 kernel: [    2.332328] hub 2-1:1.0: USB hub found
Oct  9 18:01:49 node-2 kernel: [    2.332564] hub 2-1:1.0: 8 ports detected
Oct  9 18:01:49 node-2 kernel: [    2.356368] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct  9 18:01:49 node-2 kernel: [    2.362118] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct  9 18:01:49 node-2 kernel: [    2.373409] device-mapper: uevent: version 1.0.3
Oct  9 18:01:49 node-2 kernel: [    2.379116] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct  9 18:01:49 node-2 kernel: [    2.390484] ledtrig-cpu: registered to indicate activity on CPUs
Oct  9 18:01:49 node-2 kernel: [    2.396504] TCP: cubic registered
Oct  9 18:01:49 node-2 kernel: [    2.402394] NET: Registered protocol family 10
Oct  9 18:01:49 node-2 kernel: [    2.408500] NET: Registered protocol family 17
Oct  9 18:01:49 node-2 kernel: [    2.414263] Key type dns_resolver registered
Oct  9 18:01:49 node-2 kernel: [    2.420299] Loading compiled-in X.509 certificates
Oct  9 18:01:49 node-2 kernel: [    2.426500] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct  9 18:01:49 node-2 kernel: [    2.438108] registered taskstats version 1
Oct  9 18:01:49 node-2 kernel: [    2.446145] Key type trusted registered
Oct  9 18:01:49 node-2 kernel: [    2.453727] Key type encrypted registered
Oct  9 18:01:49 node-2 kernel: [    2.459234] AppArmor: AppArmor sha1 policy hashing enabled
Oct  9 18:01:49 node-2 kernel: [    2.464743] IMA: No TPM chip found, activating TPM-bypass!
Oct  9 18:01:49 node-2 kernel: [    2.470845] regulator-dummy: disabling
Oct  9 18:01:49 node-2 kernel: [    2.476349]   Magic number: 4:571:38
Oct  9 18:01:49 node-2 kernel: [    2.481807] bdi 7:3: hash matches
Oct  9 18:01:49 node-2 kernel: [    2.487310] memory memory207: hash matches
Oct  9 18:01:49 node-2 kernel: [    2.492610] memory memory74: hash matches
Oct  9 18:01:49 node-2 kernel: [    2.497857] rtc_cmos 00:02: setting system clock to 2016-10-09 18:01:16 UTC (1476036076)
Oct  9 18:01:49 node-2 kernel: [    2.509828] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct  9 18:01:49 node-2 kernel: [    2.515254] EDD information not available.
Oct  9 18:01:49 node-2 kernel: [    2.520605] PM: Hibernation image not present or could not be loaded.
Oct  9 18:01:49 node-2 kernel: [    2.521470] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct  9 18:01:49 node-2 kernel: [    2.532508] Write protecting the kernel read-only data: 12288k
Oct  9 18:01:49 node-2 kernel: [    2.538669] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct  9 18:01:49 node-2 kernel: [    2.551001] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct  9 18:01:49 node-2 kernel: [    2.583433] device-mapper: multipath: version 1.6.0 loaded
Oct  9 18:01:49 node-2 kernel: [    2.591176] systemd-udevd[217]: starting version 204
Oct  9 18:01:49 node-2 kernel: [    2.610487] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct  9 18:01:49 node-2 kernel: [    2.619777] md: linear personality registered for level -1
Oct  9 18:01:49 node-2 kernel: [    2.634366] md: multipath personality registered for level -4
Oct  9 18:01:49 node-2 kernel: [    2.642318] md: raid0 personality registered for level 0
Oct  9 18:01:49 node-2 kernel: [    2.650264] md: raid1 personality registered for level 1
Oct  9 18:01:49 node-2 kernel: [    2.658801] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct  9 18:01:49 node-2 kernel: [    2.664931] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct  9 18:01:49 node-2 kernel: [    2.665083] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct  9 18:01:49 node-2 kernel: [    2.666295] megasas: FW now in Ready state
Oct  9 18:01:49 node-2 kernel: [    2.666837] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.667011] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.667192] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.667335] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.667481] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.667624] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.667745] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.667887] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.668049] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.668168] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.668217] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.668375] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.668452] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.668591] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.668722] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.668857] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.669428] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct  9 18:01:49 node-2 kernel: [    2.703821] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Oct  9 18:01:49 node-2 kernel: [    2.716940] 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
Oct  9 18:01:49 node-2 kernel: [    2.722702] raid6: sse2x1    2908 MB/s
Oct  9 18:01:49 node-2 kernel: [    2.737604] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  9 18:01:49 node-2 kernel: [    2.744548] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.744552] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.744556] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.744560] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.744604] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  9 18:01:49 node-2 kernel: [    2.754231] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct  9 18:01:49 node-2 kernel: [    2.754243] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  9 18:01:49 node-2 kernel: [    2.754249] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct  9 18:01:49 node-2 kernel: [    2.754256] usb 2-1.4: Manufacturer: Avocent
Oct  9 18:01:49 node-2 kernel: [    2.754258] usb 2-1.4: SerialNumber: 20111102-00000001
Oct  9 18:01:49 node-2 kernel: [    2.790607] raid6: sse2x2     651 MB/s
Oct  9 18:01:49 node-2 kernel: [    2.858271] raid6: sse2x4    8898 MB/s
Oct  9 18:01:49 node-2 kernel: [    2.930207] raid6: avx2x1   14936 MB/s
Oct  9 18:01:49 node-2 kernel: [    3.002145] raid6: avx2x2   18867 MB/s
Oct  9 18:01:49 node-2 kernel: [    3.074093] raid6: avx2x4   21359 MB/s
Oct  9 18:01:49 node-2 kernel: [    3.079695] raid6: using algorithm avx2x4 (21359 MB/s)
Oct  9 18:01:49 node-2 kernel: [    3.085227] raid6: using avx2x2 recovery algorithm
Oct  9 18:01:49 node-2 kernel: [    3.090665] megasas:IOC Init cmd success
Oct  9 18:01:49 node-2 kernel: [    3.090666] Switched to clocksource tsc
Oct  9 18:01:49 node-2 kernel: [    3.100798] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Oct  9 18:01:49 node-2 kernel: [    3.100799] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct  9 18:01:49 node-2 kernel: [    3.100800] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct  9 18:01:49 node-2 kernel: [    3.100870] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.100906] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.100944] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.100966] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.101005] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.101042] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.101144] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.112138] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Oct  9 18:01:49 node-2 kernel: [    3.112139] 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
Oct  9 18:01:49 node-2 kernel: [    3.112140] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  9 18:01:49 node-2 kernel: [    3.112196] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.112232] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.112266] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.112305] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.112389] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.120537] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Oct  9 18:01:49 node-2 kernel: [    3.120538] 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
Oct  9 18:01:49 node-2 kernel: [    3.120539] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  9 18:01:49 node-2 kernel: [    3.120595] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.120626] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.120663] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.120699] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.120778] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  9 18:01:49 node-2 kernel: [    3.168534] hidraw: raw HID events driver (C) Jiri Kosina
Oct  9 18:01:49 node-2 kernel: [    3.209998] megasas: INIT adapter done
Oct  9 18:01:49 node-2 kernel: [    3.220109] xor: automatically using best checksumming function:
Oct  9 18:01:49 node-2 kernel: [    3.240666] usbcore: registered new interface driver usbhid
Oct  9 18:01:49 node-2 kernel: [    3.247192] usbhid: USB HID core driver
Oct  9 18:01:49 node-2 kernel: [    3.254787] 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
Oct  9 18:01:49 node-2 kernel: [    3.258012]    avx       : 37877.000 MB/sec
Oct  9 18:01:49 node-2 kernel: [    3.275238] 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
Oct  9 18:01:49 node-2 kernel: [    3.289272] async_tx: api initialized (async)
Oct  9 18:01:49 node-2 kernel: [    3.289309] 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
Oct  9 18:01:49 node-2 kernel: [    3.289360] 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
Oct  9 18:01:49 node-2 kernel: [    3.289413] 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
Oct  9 18:01:49 node-2 kernel: [    3.289455] 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
Oct  9 18:01:49 node-2 kernel: [    3.298284] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct  9 18:01:49 node-2 kernel: [    3.299923] scsi0 : LSI SAS based MegaRAID driver
Oct  9 18:01:49 node-2 kernel: [    3.307871] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  9 18:01:49 node-2 kernel: [    3.383019] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  9 18:01:49 node-2 kernel: [    3.399086] md: raid6 personality registered for level 6
Oct  9 18:01:49 node-2 kernel: [    3.406129] md: raid5 personality registered for level 5
Oct  9 18:01:49 node-2 kernel: [    3.408457] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct  9 18:01:49 node-2 kernel: [    3.409040] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct  9 18:01:49 node-2 kernel: [    3.410391] sd 0:2:0:0: [sda] Write Protect is off
Oct  9 18:01:49 node-2 kernel: [    3.410403] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct  9 18:01:49 node-2 kernel: [    3.410619] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct  9 18:01:49 node-2 kernel: [    3.437112]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct  9 18:01:49 node-2 kernel: [    3.441604] sd 0:2:0:0: [sda] Attached SCSI disk
Oct  9 18:01:49 node-2 kernel: [    3.468423] md: raid4 personality registered for level 4
Oct  9 18:01:49 node-2 kernel: [    3.478820] md: raid10 personality registered for level 10
Oct  9 18:01:49 node-2 kernel: [    3.533750] multipathd (362): /proc/362/oom_adj is deprecated, please use /proc/362/oom_score_adj instead.
Oct  9 18:01:49 node-2 kernel: [    3.591423] random: lvm urandom read with 33 bits of entropy available
Oct  9 18:01:49 node-2 kernel: [    3.701790] bio: create slab <bio-1> at 1
Oct  9 18:01:49 node-2 kernel: [    4.372198] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct  9 18:01:49 node-2 kernel: [    5.044762] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct  9 18:01:49 node-2 kernel: [    5.078360] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct  9 18:01:49 node-2 kernel: [    5.160725] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct  9 18:01:49 node-2 kernel: [    5.208665] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct  9 18:01:49 node-2 kernel: [    5.290351] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct  9 18:01:49 node-2 kernel: [    5.426115] random: nonblocking pool is initialized
Oct  9 18:01:49 node-2 kernel: [    5.563525] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct  9 18:01:49 node-2 kernel: [    5.601501] XFS (dm-0): Mounting Filesystem
Oct  9 18:01:49 node-2 kernel: [    5.758799] XFS (dm-0): Ending clean mount
Oct  9 18:01:49 node-2 kernel: [    5.829194] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct  9 18:01:49 node-2 kernel: [    5.873207] XFS (dm-1): Mounting Filesystem
Oct  9 18:01:49 node-2 kernel: [    5.981956] XFS (dm-1): Ending clean mount
Oct  9 18:01:49 node-2 kernel: [    7.809965] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct  9 18:01:49 node-2 kernel: [    7.836428] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct  9 18:01:49 node-2 kernel: [    7.969310] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  9 18:01:49 node-2 kernel: [    7.969317] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  9 18:01:49 node-2 kernel: [    7.969322] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct  9 18:01:49 node-2 kernel: [    7.969326] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct  9 18:01:49 node-2 kernel: [    8.005453] systemd-udevd[773]: starting version 204
Oct  9 18:01:49 node-2 kernel: [    8.210413] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct  9 18:01:49 node-2 kernel: [    8.210420] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  9 18:01:49 node-2 kernel: [    8.210423] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct  9 18:01:49 node-2 kernel: [    8.210426] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  9 18:01:49 node-2 kernel: [    8.210494] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct  9 18:01:49 node-2 kernel: [    8.213384] power_meter ACPI000D:00: Found ACPI power meter.
Oct  9 18:01:49 node-2 kernel: [    8.213412] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct  9 18:01:49 node-2 kernel: [    8.230148] wmi: Mapper loaded
Oct  9 18:01:49 node-2 kernel: [    8.230726] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct  9 18:01:49 node-2 kernel: [    8.252503] IPMI System Interface driver.
Oct  9 18:01:49 node-2 kernel: [    8.252541] ipmi_si: probing via ACPI
Oct  9 18:01:49 node-2 kernel: [    8.252552] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct  9 18:01:49 node-2 kernel: [    8.252553] ipmi_si: Adding ACPI-specified kcs state machine
Oct  9 18:01:49 node-2 kernel: [    8.252565] ipmi_si: probing via SMBIOS
Oct  9 18:01:49 node-2 kernel: [    8.252566] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct  9 18:01:49 node-2 kernel: [    8.252567] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct  9 18:01:49 node-2 kernel: [    8.252568] ipmi_si: probing via SPMI
Oct  9 18:01:49 node-2 kernel: [    8.252569] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct  9 18:01:49 node-2 kernel: [    8.252569] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct  9 18:01:49 node-2 kernel: [    8.252570] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct  9 18:01:49 node-2 kernel: [    8.306096] systemd-udevd[791]: renamed network interface eth0 to enp6s0
Oct  9 18:01:49 node-2 kernel: [    8.330000] systemd-udevd[807]: renamed network interface eth1 to enp7s0
Oct  9 18:01:49 node-2 kernel: [    8.382112] systemd-udevd[810]: renamed network interface eth2 to enp8s0
Oct  9 18:01:49 node-2 kernel: [    8.399504] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct  9 18:01:49 node-2 kernel: [    8.399508] ipmi_si 00:09: IPMI kcs interface initialized
Oct  9 18:01:49 node-2 kernel: [    8.413984] systemd-udevd[811]: renamed network interface eth3 to enp9s0
Oct  9 18:01:49 node-2 kernel: [    8.712325] type=1400 audit(1476036082.715:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Oct  9 18:01:49 node-2 kernel: [    8.712478] type=1400 audit(1476036082.715:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1049 comm="apparmor_parser"
Oct  9 18:01:49 node-2 kernel: [    8.712606] type=1400 audit(1476036082.715:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1049 comm="apparmor_parser"
Oct  9 18:01:49 node-2 kernel: [    8.723414] type=1400 audit(1476036082.727:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1052 comm="apparmor_parser"
Oct  9 18:01:49 node-2 kernel: [    8.723559] type=1400 audit(1476036082.727:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1052 comm="apparmor_parser"
Oct  9 18:01:49 node-2 kernel: [    8.723716] type=1400 audit(1476036082.727:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1052 comm="apparmor_parser"
Oct  9 18:01:49 node-2 kernel: [    8.723738] type=1400 audit(1476036082.727:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Oct  9 18:01:49 node-2 kernel: [    8.723905] type=1400 audit(1476036082.727:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1053 comm="apparmor_parser"
Oct  9 18:01:49 node-2 kernel: [    8.724042] type=1400 audit(1476036082.727:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1053 comm="apparmor_parser"
Oct  9 18:01:49 node-2 kernel: [    8.724286] type=1400 audit(1476036082.727:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Oct  9 18:01:49 node-2 kernel: [    9.262604] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct  9 18:01:49 node-2 kernel: [    9.263414] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct  9 18:01:49 node-2 kernel: [    9.424295] enic 0000:06:00.0 enp6s0: Link UP
Oct  9 18:01:49 node-2 kernel: [    9.425649] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct  9 18:01:49 node-2 kernel: [    9.425653] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct  9 18:01:49 node-2 kernel: [   18.924264] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct  9 18:01:49 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct  9 18:01:50 node-2 failsafe: Failsafe of 120 seconds reached.
Oct  9 18:01:50 node-2 kernel: [   37.337197] init: failsafe main process (8410) killed by TERM signal
Oct  9 18:01:51 node-2 dbus[8517]: [system] AppArmor D-Bus mediation is enabled
Oct  9 18:01:51 node-2 kernel: [   37.560878] audit_printk_skb: 30 callbacks suppressed
Oct  9 18:01:51 node-2 kernel: [   37.560880] type=1400 audit(1476036111.154:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8529 comm="apparmor_parser"
Oct  9 18:01:51 node-2 kernel: [   37.560884] type=1400 audit(1476036111.154:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8529 comm="apparmor_parser"
Oct  9 18:01:51 node-2 kernel: [   37.560887] type=1400 audit(1476036111.154:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8529 comm="apparmor_parser"
Oct  9 18:01:51 node-2 kernel: [   37.561110] type=1400 audit(1476036111.154:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8529 comm="apparmor_parser"
Oct  9 18:01:51 node-2 kernel: [   37.561112] type=1400 audit(1476036111.154:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8529 comm="apparmor_parser"
Oct  9 18:01:51 node-2 kernel: [   37.561228] type=1400 audit(1476036111.154:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8529 comm="apparmor_parser"
Oct  9 18:01:51 node-2 kernel: [   37.565991] type=1400 audit(1476036111.158:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8530 comm="apparmor_parser"
Oct  9 18:01:51 node-2 kernel: [   37.633470] type=1400 audit(1476036111.226:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8532 comm="apparmor_parser"
Oct  9 18:01:51 node-2 anacron[8602]: Anacron 2.3 started on 2016-10-09
Oct  9 18:01:51 node-2 cron[8568]: (CRON) INFO (pidfile fd = 3)
Oct  9 18:01:51 node-2 cron[8611]: (CRON) STARTUP (fork ok)
Oct  9 18:01:51 node-2 anacron[8602]: Will run job `cron.daily' in 5 min.
Oct  9 18:01:51 node-2 anacron[8602]: Will run job `cron.weekly' in 10 min.
Oct  9 18:01:51 node-2 anacron[8602]: Will run job `cron.monthly' in 15 min.
Oct  9 18:01:51 node-2 anacron[8602]: Jobs will be executed sequentially
Oct  9 18:01:51 node-2 multipathd: path checkers start up
Oct  9 18:01:51 node-2 cron[8611]: (CRON) INFO (Running @reboot jobs)
Oct  9 18:01:51 node-2 postfix/master[8747]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct  9 18:01:54 node-2 puppet-agent[8931]: Reopening log files
Oct  9 18:01:55 node-2 puppet-agent[8931]: Could not request certificate: Connection refused - connect(2)
Oct  9 18:02:01 node-2 CRON[8962]: (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")
Oct  9 18:02:10 node-2 puppet-user[9021]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct  9 18:02:10 node-2 puppet-user[9021]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Oct  9 18:02:11 node-2 puppet-user[9021]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct  9 18:02:11 node-2 puppet-user[9021]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct  9 18:02:11 node-2 puppet-user[9021]: Finished catalog run in 0.63 seconds
Oct  9 18:02:12 node-2 multipathd: uevent trigger error
Oct  9 18:02:12 node-2 puppet-user[9441]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  9 18:02:12 node-2 puppet-user[9441]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Oct  9 18:02:12 node-2 puppet-user[9441]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct  9 18:02:12 node-2 puppet-user[9441]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct  9 18:02:12 node-2 puppet-user[9441]: (/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"]'
Oct  9 18:02:12 node-2 puppet-user[9441]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct  9 18:02:12 node-2 puppet-user[9441]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct  9 18:02:13 node-2 puppet-user[9441]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct  9 18:02:13 node-2 puppet-user[9441]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct  9 18:02:13 node-2 puppet-user[9441]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct  9 18:02:13 node-2 puppet-user[9441]: Finished catalog run in 0.07 seconds
Oct  9 18:02:14 node-2 puppet-user[10018]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct  9 18:02:14 node-2 puppet-user[10018]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Oct  9 18:02:14 node-2 puppet-user[10018]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct  9 18:02:14 node-2 puppet-user[10018]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct  9 18:02:14 node-2 puppet-user[10018]: Finished catalog run in 0.03 seconds
Oct  9 18:02:16 node-2 puppet-user[10485]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct  9 18:02:16 node-2 puppet-user[10485]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Oct  9 18:02:16 node-2 puppet-user[10485]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct  9 18:02:16 node-2 puppet-user[10485]: Finished catalog run in 0.02 seconds
Oct  9 18:02:17 node-2 puppet-user[10932]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct  9 18:02:17 node-2 puppet-user[10932]: Compiled catalog for node-2.domain.tld in environment production in 0.16 seconds
Oct  9 18:02:17 node-2 puppet-user[10932]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct  9 18:02:18 node-2 puppet-user[10932]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Oct  9 18:02:18 node-2 puppet-user[10932]: Finished catalog run in 0.47 seconds
Oct  9 18:02:19 node-2 puppet-user[11406]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct  9 18:02:19 node-2 puppet-user[11406]: Compiled catalog for node-2.domain.tld in environment production in 0.21 seconds
Oct  9 18:02:19 node-2 puppet-user[11406]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct  9 18:02:19 node-2 puppet-user[11406]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct  9 18:02:19 node-2 puppet-user[11406]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Oct  9 18:02:19 node-2 puppet-user[11406]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct  9 18:02:19 node-2 puppet-user[11406]: Finished catalog run in 0.22 seconds
Oct  9 18:02:21 node-2 puppet-user[11879]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct  9 18:02:21 node-2 puppet-user[11879]: Compiled catalog for node-2.domain.tld in environment production in 0.13 seconds
Oct  9 18:02:21 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  9 18:02:21 node-2 nailgun-agent: D, [2016-10-09T18:02:01.593500 #8965] DEBUG -- : Sleep for 20 seconds before sending request
Oct  9 18:02:21 node-2 nailgun-agent: I, [2016-10-09T18:02:21.613645 #8965]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  9 18:02:21 node-2 puppet-user[11879]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct  9 18:02:21 node-2 kernel: [   68.018916] nr_pdflush_threads exported in /proc is scheduled for removal
Oct  9 18:02:21 node-2 kernel: [   68.018965] 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.
Oct  9 18:02:21 node-2 puppet-user[11879]: (/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'
Oct  9 18:02:21 node-2 puppet-user[11879]: Finished catalog run in 0.05 seconds
Oct  9 18:02:21 node-2 nailgun-agent: D, [2016-10-09T18:02:21.992508 #8965] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct  9 18:02:23 node-2 puppet-user[12465]: (Scope(Class[main])) MODULAR: sync_time
Oct  9 18:02:23 node-2 puppet-user[12465]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Oct  9 18:02:23 node-2 ntpdate[12881]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct  9 18:02:29 node-2 ntpdate[12881]: adjust time server 10.20.0.2 offset 0.001672 sec
Oct  9 18:02:29 node-2 puppet-user[12465]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct  9 18:02:29 node-2 puppet-user[12465]: Finished catalog run in 6.17 seconds
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.922405 #8965] DEBUG -- : Trying to find block devices
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.922485 #8965] DEBUG -- : Found block device: sda
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.922524 #8965] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.922546 #8965] DEBUG -- : Trying to get list of physical devices
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.922716 #8965] DEBUG -- : Getting udev properties for device: sda
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.924410 #8965] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /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"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc7884
Oct  9 18:02:33 node-2 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"93826", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.924480 #8965] DEBUG -- : Trying to find out if device sda is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.924520 #8965] DEBUG -- : Device sda removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.924534 #8965] DEBUG -- : Device sda seems to be appropriate
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.924921 #8965] DEBUG -- : Getting udev properties for device: dm-0
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.926474 #8965] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-dcuDi9b7xnGxedQLTKUzVr4I8kOiYVKedtcw68nz2bJzQddxL3m2FtQhI1SrZOdK /dev/disk/by-uuid/f31ba6bd-717f-49d0-ad95-6d73a6f93d5b /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-dcuDi9b7xnGxedQLTKUzVr4I8kOiYVKedtcw68nz2bJzQddxL3m2FtQhI1SrZOdK", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f31ba6bd-717f-49d0-ad95-6d73a6f93d5b", "ID_FS_UUID_ENC"=>"f31ba6bd-717f-49d0-ad95-6d73a6f93d5b", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56173", "nomdmonddf"=>"1", "nomd
Oct  9 18:02:33 node-2 nailgun-agent: monisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.926498 #8965] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.926538 #8965] DEBUG -- : Device dm-0 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.926565 #8965] DEBUG -- : Device dm-0 seems to be appropriate
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.926580 #8965] DEBUG -- : Getting udev properties for device: dm-1
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.928082 #8965] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-GTWaIhmfPBpB7uviIdeKjo0c7fOBYWxZIViw95Uuc4kltSDw6x7eff7GUzA4R7ht /dev/disk/by-uuid/b79c59e1-d4f6-46ad-a2bb-33d09b51f1f2 /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-GTWaIhmfPBpB7uviIdeKjo0c7fOBYWxZIViw95Uuc4kltSDw6x7eff7GUzA4R7ht", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b79c59e1-d4f6-46ad-a2bb-33d09b51f1f2", "ID_FS_UUID_ENC"=>"b79c59e1-d4f6-46ad-a2bb-33d09b51f1f2", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84
Oct  9 18:02:33 node-2 nailgun-agent: 950", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.928104 #8965] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.928132 #8965] DEBUG -- : Device dm-1 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.928187 #8965] DEBUG -- : Device dm-1 seems to be appropriate
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.928200 #8965] DEBUG -- : Getting udev properties for device: dm-2
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.929752 #8965] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-KvlFvVMdjiA22s0tiC2cNGzRxlhBFNVXELQScFhIaCiu4f5NrJBvksimFF2bPf1d /dev/disk/by-uuid/ecc6c485-77f5-486b-a57b-2d4f759cd002 /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-KvlFvVMdjiA22s0tiC2cNGzRxlhBFNVXELQScFhIaCiu4f5NrJBvksimFF2bPf1d", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ecc6c485-77f5-486b-a57b-2d4f759cd002", "ID_FS_UUID_ENC"=>"ecc6c485-77f5-486b-a57b-2d4f759cd002", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90438", "nomdmond
Oct  9 18:02:33 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.929773 #8965] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.929812 #8965] DEBUG -- : Device dm-2 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.929824 #8965] DEBUG -- : Device dm-2 seems to be appropriate
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.929837 #8965] DEBUG -- : Getting udev properties for device: dm-3
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.931342 #8965] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-Jnpxhu2y61UeZ4TcHEP2x3enrrjUO9OkdE4TxMi0sxvVh6w5tkZrkf74Be5Gxwi1 /dev/disk/by-uuid/3890fb44-0cd2-46e2-ab9c-3fff8b7c1536 /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-Jnpxhu2y61UeZ4TcHEP2x3enrrjUO9OkdE4TxMi0sxvVh6w5tkZrkf74Be5Gxwi1", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"3890fb44-0cd2-46e2-ab9c-3fff8b7c1536", "ID_FS_UUID_ENC"=>"3890fb44-0cd2-46e2-ab9c-3fff8b7c1536", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"91801", "nomdmonddf"=>"1", 
Oct  9 18:02:33 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.931364 #8965] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.931401 #8965] DEBUG -- : Device dm-3 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.931423 #8965] DEBUG -- : Device dm-3 seems to be appropriate
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.931436 #8965] DEBUG -- : Getting udev properties for device: dm-4
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.932941 #8965] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-rwBfTZM1fQX23bf4cMowzZQYnz46Woz2b5szskCfl5hT59sk7EKn7QtwzfdFhJeZ /dev/disk/by-uuid/38d9f080-1c97-4a0f-b180-1e9822b020eb /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-rwBfTZM1fQX23bf4cMowzZQYnz46Woz2b5szskCfl5hT59sk7EKn7QtwzfdFhJeZ", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"38d9f080-1c97-4a0f-b180-1e9822b020eb", "ID_FS_UUID_ENC"=>"38d9f080-1c97-4a0f-b180-1e9822b020eb", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95360", "nomdmonddf"=>"1", "nomd
Oct  9 18:02:33 node-2 nailgun-agent: monisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.932963 #8965] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.933000 #8965] DEBUG -- : Device dm-4 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.933012 #8965] DEBUG -- : Device dm-4 seems to be appropriate
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.933038 #8965] DEBUG -- : Getting udev properties for device: dm-5
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.934520 #8965] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-rwBfTZM1fQX23bf4cMowzZQYnz46Woz2nG22oo4AoJ84cL8QpVgkxVEbvF7cDTcf /dev/disk/by-uuid/f8a1ced3-83d7-40e4-a124-0b247c1fac19 /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-rwBfTZM1fQX23bf4cMowzZQYnz46Woz2nG22oo4AoJ84cL8QpVgkxVEbvF7cDTcf", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"f8a1ced3-83d7-40e4-a124-0b247c1fac19", "ID_FS_UUID_ENC"=>"f8a1ced3-83d7-40e4-a124-0b247c1fac19", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95724", "nomdmonddf"=>"1", "nomdmonisw"
Oct  9 18:02:33 node-2 nailgun-agent: =>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.934542 #8965] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.934569 #8965] DEBUG -- : Device dm-5 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.934581 #8965] DEBUG -- : Device dm-5 seems to be appropriate
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.934625 #8965] DEBUG -- : Getting udev properties for device: ram0
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.936026 #8965] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54076", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.936046 #8965] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.936082 #8965] DEBUG -- : Device ram0 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.936107 #8965] DEBUG -- : Getting udev properties for device: ram1
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.937488 #8965] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54087", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.937508 #8965] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.937547 #8965] DEBUG -- : Device ram1 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.937576 #8965] DEBUG -- : Getting udev properties for device: ram2
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.938950 #8965] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54190", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.938970 #8965] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.939009 #8965] DEBUG -- : Device ram2 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.939026 #8965] DEBUG -- : Getting udev properties for device: ram3
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.940397 #8965] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54313", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.940416 #8965] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.940462 #8965] DEBUG -- : Device ram3 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.940479 #8965] DEBUG -- : Getting udev properties for device: ram4
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.941879 #8965] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54332", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.941899 #8965] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.941929 #8965] DEBUG -- : Device ram4 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.941947 #8965] DEBUG -- : Getting udev properties for device: ram5
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.943304 #8965] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54350", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.943324 #8965] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.943352 #8965] DEBUG -- : Device ram5 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.943396 #8965] DEBUG -- : Getting udev properties for device: ram6
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.944777 #8965] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54366", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.944797 #8965] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.944827 #8965] DEBUG -- : Device ram6 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.944843 #8965] DEBUG -- : Getting udev properties for device: ram7
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.946209 #8965] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54383", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.946230 #8965] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.946266 #8965] DEBUG -- : Device ram7 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.946291 #8965] DEBUG -- : Getting udev properties for device: ram8
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.947646 #8965] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54497", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.947677 #8965] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.947706 #8965] DEBUG -- : Device ram8 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.947724 #8965] DEBUG -- : Getting udev properties for device: ram9
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.949093 #8965] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54522", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.949133 #8965] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.949182 #8965] DEBUG -- : Device ram9 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.949200 #8965] DEBUG -- : Getting udev properties for device: loop0
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.950585 #8965] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53979", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.950619 #8965] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.950653 #8965] DEBUG -- : Device loop0 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.950680 #8965] DEBUG -- : Getting udev properties for device: loop1
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.952065 #8965] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53992", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.952090 #8965] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.952124 #8965] DEBUG -- : Device loop1 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.952143 #8965] DEBUG -- : Getting udev properties for device: loop2
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.953562 #8965] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54005", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.953594 #8965] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.953626 #8965] DEBUG -- : Device loop2 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.953650 #8965] DEBUG -- : Getting udev properties for device: loop3
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.955039 #8965] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54018", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.955076 #8965] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.955110 #8965] DEBUG -- : Device loop3 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.955128 #8965] DEBUG -- : Getting udev properties for device: loop4
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.956539 #8965] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54029", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.956572 #8965] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.956616 #8965] DEBUG -- : Device loop4 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.956645 #8965] DEBUG -- : Getting udev properties for device: loop5
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.958025 #8965] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54042", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.958061 #8965] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.958092 #8965] DEBUG -- : Device loop5 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.958111 #8965] DEBUG -- : Getting udev properties for device: loop6
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.959507 #8965] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54053", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.959531 #8965] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.959570 #8965] DEBUG -- : Device loop6 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.959600 #8965] DEBUG -- : Getting udev properties for device: loop7
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.964594 #8965] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54063", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.964625 #8965] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.964664 #8965] DEBUG -- : Device loop7 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.964682 #8965] DEBUG -- : Getting udev properties for device: ram10
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.966188 #8965] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54098", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.966212 #8965] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.966251 #8965] DEBUG -- : Device ram10 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.966270 #8965] DEBUG -- : Getting udev properties for device: ram11
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.967673 #8965] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54108", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.967717 #8965] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.967750 #8965] DEBUG -- : Device ram11 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.967768 #8965] DEBUG -- : Getting udev properties for device: ram12
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.969128 #8965] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54124", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.969156 #8965] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.969218 #8965] DEBUG -- : Device ram12 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.969235 #8965] DEBUG -- : Getting udev properties for device: ram13
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.970572 #8965] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54141", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.970592 #8965] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.970618 #8965] DEBUG -- : Device ram13 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.970635 #8965] DEBUG -- : Getting udev properties for device: ram14
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.972007 #8965] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54158", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.972026 #8965] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.972054 #8965] DEBUG -- : Device ram14 removable parameter: "0"
Oct  9 18:02:33 node-2 nailgun-agent: D, [2016-10-09T18:02:33.972073 #8965] DEBUG -- : Getting udev properties for device: ram15
Oct  9 18:02:34 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973397 #8965] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54174", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973417 #8965] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973445 #8965] DEBUG -- : Device ram15 removable parameter: "0"
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973476 #8965] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973489 #8965] DEBUG -- : Block device seems to be physical data storage: sda
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973530 #8965] DEBUG -- : Found block device: dm-0
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973569 #8965] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973581 #8965] DEBUG -- : Found block device: dm-1
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973592 #8965] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973602 #8965] DEBUG -- : Found block device: dm-2
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973622 #8965] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973630 #8965] DEBUG -- : Found block device: dm-3
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973638 #8965] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973646 #8965] DEBUG -- : Found block device: dm-4
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973655 #8965] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973663 #8965] DEBUG -- : Found block device: dm-5
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973695 #8965] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973703 #8965] DEBUG -- : Found block device: ram0
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973712 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973720 #8965] DEBUG -- : Found block device: ram1
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973730 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973738 #8965] DEBUG -- : Found block device: ram2
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973746 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973755 #8965] DEBUG -- : Found block device: ram3
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973763 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973771 #8965] DEBUG -- : Found block device: ram4
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973811 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973819 #8965] DEBUG -- : Found block device: ram5
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973830 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973837 #8965] DEBUG -- : Found block device: ram6
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973846 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973854 #8965] DEBUG -- : Found block device: ram7
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973864 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973872 #8965] DEBUG -- : Found block device: ram8
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973880 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973888 #8965] DEBUG -- : Found block device: ram9
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973932 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973941 #8965] DEBUG -- : Found block device: loop0
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973950 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973959 #8965] DEBUG -- : Found block device: loop1
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973968 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973976 #8965] DEBUG -- : Found block device: loop2
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973985 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.973993 #8965] DEBUG -- : Found block device: loop3
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974002 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974051 #8965] DEBUG -- : Found block device: loop4
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974061 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974070 #8965] DEBUG -- : Found block device: loop5
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974079 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974086 #8965] DEBUG -- : Found block device: loop6
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974096 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974104 #8965] DEBUG -- : Found block device: loop7
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974112 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974120 #8965] DEBUG -- : Found block device: ram10
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974168 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974177 #8965] DEBUG -- : Found block device: ram11
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974186 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974194 #8965] DEBUG -- : Found block device: ram12
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974202 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974209 #8965] DEBUG -- : Found block device: ram13
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974220 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974228 #8965] DEBUG -- : Found block device: ram14
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974237 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974286 #8965] DEBUG -- : Found block device: ram15
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974296 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:33.974322 #8965] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:34.068757 #8965] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct  9 18:02:34 node-2 nailgun-agent: D, [2016-10-09T18:02:34.068805 #8965] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct  9 18:02:35 node-2 puppet-user[13433]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  9 18:02:35 node-2 puppet-user[13433]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Oct  9 18:02:35 node-2 puppet-user[13433]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct  9 18:02:35 node-2 puppet-user[13433]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Oct  9 18:02:35 node-2 puppet-user[13433]: Finished catalog run in 0.06 seconds
Oct  9 18:02:36 node-2 puppet-user[13882]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct  9 18:02:37 node-2 puppet-user[13882]: Compiled catalog for node-2.domain.tld in environment production in 0.52 seconds
Oct  9 18:02:37 node-2 puppet-user[13882]: (/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
Oct  9 18:02:37 node-2 puppet-user[13882]: (/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
Oct  9 18:02:37 node-2 puppet-user[13882]: (/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
Oct  9 18:02:37 node-2 puppet-user[13882]: (/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
Oct  9 18:02:37 node-2 puppet-user[13882]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct  9 18:02:37 node-2 puppet-user[13882]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct  9 18:02:37 node-2 puppet-user[13882]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct  9 18:02:37 node-2 puppet-user[13882]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct  9 18:02:37 node-2 puppet-user[13882]: (/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
Oct  9 18:02:37 node-2 puppet-user[13882]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct  9 18:02:37 node-2 kernel: [   84.266177] init: plymouth-upstart-bridge main process ended, respawning
Oct  9 18:02:38 node-2 puppet-agent[8931]: Could not run: SIGTERM
Oct  9 18:02:38 node-2 kernel: [   84.546470] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct  9 18:02:38 node-2 puppet-user[13882]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct  9 18:02:38 node-2 ec2: 
Oct  9 18:02:38 node-2 ec2: #############################################################
Oct  9 18:02:38 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct  9 18:02:38 node-2 ec2: 1024 5a:60:13:13:56:48:3a:a9:5e:73:c7:7d:e2:18:f5:5b  root@node-2.domain.tld (DSA)
Oct  9 18:02:38 node-2 ec2: 256 57:77:71:94:f9:89:e0:e5:4d:c7:8e:dd:16:b7:3e:7a  root@node-2.domain.tld (ECDSA)
Oct  9 18:02:38 node-2 ec2: 256 9b:6e:34:8f:49:7e:d9:ec:0d:98:b0:66:f2:e7:f5:38  root@node-2.domain.tld (ED25519)
Oct  9 18:02:38 node-2 ec2: 2048 9f:6e:d8:e2:d3:e4:0e:36:7e:90:80:d3:d9:a0:11:7d  root@node-2.domain.tld (RSA)
Oct  9 18:02:38 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct  9 18:02:38 node-2 ec2: #############################################################
Oct  9 18:02:38 node-2 puppet-user[13882]: Finished catalog run in 0.76 seconds
Oct  9 18:02:39 node-2 puppet-user[14557]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct  9 18:02:39 node-2 puppet-user[14557]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Oct  9 18:02:43 node-2 puppet-user[14557]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct  9 18:02:46 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214067 #8965] DEBUG -- : Trying to find block devices
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214137 #8965] DEBUG -- : Found block device: sda
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214208 #8965] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214230 #8965] DEBUG -- : Block device seems to be physical data storage: sda
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214282 #8965] DEBUG -- : Found block device: dm-0
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214295 #8965] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214305 #8965] DEBUG -- : Found block device: dm-1
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214315 #8965] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214324 #8965] DEBUG -- : Found block device: dm-2
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214333 #8965] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214341 #8965] DEBUG -- : Found block device: dm-3
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214350 #8965] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214358 #8965] DEBUG -- : Found block device: dm-4
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214367 #8965] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214376 #8965] DEBUG -- : Found block device: dm-5
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214405 #8965] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214414 #8965] DEBUG -- : Found block device: ram0
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214423 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214432 #8965] DEBUG -- : Found block device: ram1
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214440 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214449 #8965] DEBUG -- : Found block device: ram2
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214458 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214466 #8965] DEBUG -- : Found block device: ram3
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214476 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214484 #8965] DEBUG -- : Found block device: ram4
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214492 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214516 #8965] DEBUG -- : Found block device: ram5
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214525 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214533 #8965] DEBUG -- : Found block device: ram6
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214541 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214550 #8965] DEBUG -- : Found block device: ram7
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214558 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214566 #8965] DEBUG -- : Found block device: ram8
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214585 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214594 #8965] DEBUG -- : Found block device: ram9
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214603 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214610 #8965] DEBUG -- : Found block device: loop0
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214630 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214638 #8965] DEBUG -- : Found block device: loop1
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214648 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214655 #8965] DEBUG -- : Found block device: loop2
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214672 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214680 #8965] DEBUG -- : Found block device: loop3
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214690 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214709 #8965] DEBUG -- : Found block device: loop4
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214719 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214728 #8965] DEBUG -- : Found block device: loop5
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214736 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214744 #8965] DEBUG -- : Found block device: loop6
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214763 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214771 #8965] DEBUG -- : Found block device: loop7
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214780 #8965] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214788 #8965] DEBUG -- : Found block device: ram10
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214808 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214816 #8965] DEBUG -- : Found block device: ram11
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214826 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214833 #8965] DEBUG -- : Found block device: ram12
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214857 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214866 #8965] DEBUG -- : Found block device: ram13
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214874 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214883 #8965] DEBUG -- : Found block device: ram14
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214892 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214928 #8965] DEBUG -- : Found block device: ram15
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214938 #8965] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.214966 #8965] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Oct  9 18:02:46 node-2 nailgun-agent: D, [2016-10-09T18:02:46.419063 #8965] DEBUG -- : Response: status: 200 body: {"id": 2}
Oct  9 18:02:46 node-2 nailgun-agent: I, [2016-10-09T18:02:46.421879 #8965]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct  9 18:03:01 node-2 CRON[16330]: (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")
Oct  9 18:03:10 node-2 puppet-user[14557]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct  9 18:03:10 node-2 puppet-user[14557]: Finished catalog run in 30.58 seconds
Oct  9 18:03:12 node-2 puppet-user[17101]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct  9 18:03:13 node-2 puppet-user[17101]: Compiled catalog for node-2.domain.tld in environment production in 0.63 seconds
Oct  9 18:03:13 node-2 puppet-user[17101]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct  9 18:03:13 node-2 puppet-user[17101]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct  9 18:03:13 node-2 puppet-user[17101]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct  9 18:03:13 node-2 puppet-user[17101]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct  9 18:03:13 node-2 puppet-user[17101]: Finished catalog run in 0.08 seconds
Oct  9 18:03:15 node-2 puppet-user[17560]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct  9 18:03:16 node-2 puppet-user[17560]: Compiled catalog for node-2.domain.tld in environment production in 0.93 seconds
Oct  9 18:03:16 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct  9 18:03:16 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct  9 18:03:16 node-2 crontab[18006]: (root) LIST (root)
Oct  9 18:03:16 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct  9 18:03:16 node-2 crontab[18007]: (root) REPLACE (root)
Oct  9 18:03:17 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/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
Oct  9 18:03:18 node-2 puppet-user[17560]: (/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
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/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
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/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
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct  9 18:03:18 node-2 puppet-user[17560]: (/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
Oct  9 18:03:18 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/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
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/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
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/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
Oct  9 18:03:19 node-2 puppet-user[17560]: (/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
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct  9 18:03:19 node-2 puppet-user[17560]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct  9 18:03:19 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8383" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:19 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct  9 18:03:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:33 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:33 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:33 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:33 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:33 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:35 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:35 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:35 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:35 node-2 multipathd: uevent trigger error
<27>Oct  9 18:03:35 node-2 multipathd: uevent trigger error
<27>Oct  9 18:04:30 node-2 ntpdate[29190]: no servers can be used, exiting
<27>Oct  9 18:04:30 node-2 ntpdate[29306]: no servers can be used, exiting
<27>Oct  9 18:04:31 node-2 ntpdate[29478]: no servers can be used, exiting
<27>Oct  9 18:05:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:05 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:05 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:05 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:05 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:05 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:05 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:17 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:17 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:17 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:17 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:17 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-2 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:22 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:22 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:23 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:23 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:23 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:25 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  9 18:06:25 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  9 18:06:31 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  9 18:06:31 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  9 18:06:36 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  9 18:06:42 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  9 18:06:42 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  9 18:06:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:06:51 node-2 ntpdate[14145]: the NTP socket is in use, exiting
<27>Oct  9 18:07:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:02 node-2 multipathd: uevent trigger error
<129>Oct  9 18:07:05 node-2 haproxy[16911]: 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>Oct  9 18:07:05 node-2 haproxy[16911]: Backup Server mysqld/node-4 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>Oct  9 18:07:06 node-2 haproxy[16917]: 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>Oct  9 18:07:06 node-2 haproxy[16917]: proxy mysqld has no server available!
<27>Oct  9 18:07:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:11 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:11 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:11 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:11 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:11 node-2 multipathd: uevent trigger error
<129>Oct  9 18:07:14 node-2 haproxy[19500]: 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>Oct  9 18:07:14 node-2 haproxy[19500]: Backup Server mysqld/node-4 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>Oct  9 18:07:14 node-2 haproxy[19500]: 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>Oct  9 18:07:14 node-2 haproxy[19500]: proxy mysqld has no server available!
<129>Oct  9 18:07:15 node-2 haproxy[19504]: 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>Oct  9 18:07:15 node-2 haproxy[19504]: Server object-storage/node-4 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>Oct  9 18:07:15 node-2 haproxy[19504]: 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>Oct  9 18:07:15 node-2 haproxy[19504]: proxy object-storage has no server available!
<27>Oct  9 18:07:17 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:17 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:17 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:17 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:17 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:17 node-2 multipathd: uevent trigger error
<129>Oct  9 18:07:19 node-2 haproxy[21017]: 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>Oct  9 18:07:19 node-2 haproxy[21017]: Server neutron/node-4 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>Oct  9 18:07:19 node-2 haproxy[21017]: 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>Oct  9 18:07:19 node-2 haproxy[21017]: proxy neutron has no server available!
<129>Oct  9 18:07:20 node-2 haproxy[21021]: 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>Oct  9 18:07:20 node-2 haproxy[21021]: Backup Server mysqld/node-4 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>Oct  9 18:07:20 node-2 haproxy[21021]: 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>Oct  9 18:07:20 node-2 haproxy[21021]: proxy mysqld has no server available!
<129>Oct  9 18:07:20 node-2 haproxy[21021]: 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>Oct  9 18:07:20 node-2 haproxy[21021]: Server object-storage/node-4 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>Oct  9 18:07:21 node-2 haproxy[21021]: 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>Oct  9 18:07:21 node-2 haproxy[21021]: proxy object-storage has no server available!
<27>Oct  9 18:07:22 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:22 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:22 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:22 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:22 node-2 multipathd: uevent trigger error
<129>Oct  9 18:07:24 node-2 haproxy[22381]: 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>Oct  9 18:07:24 node-2 haproxy[22381]: Server keystone-1/node-4 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>Oct  9 18:07:25 node-2 haproxy[22390]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:07:25 node-2 haproxy[22390]: proxy keystone-1 has no server available!
<129>Oct  9 18:07:25 node-2 haproxy[22390]: 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>Oct  9 18:07:25 node-2 haproxy[22390]: Server keystone-2/node-4 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>Oct  9 18:07:25 node-2 haproxy[22390]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:07:25 node-2 haproxy[22390]: proxy keystone-2 has no server available!
<129>Oct  9 18:07:25 node-2 haproxy[22390]: 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>Oct  9 18:07:25 node-2 haproxy[22390]: Server neutron/node-4 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>Oct  9 18:07:25 node-2 haproxy[22390]: 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>Oct  9 18:07:25 node-2 haproxy[22390]: proxy neutron has no server available!
<129>Oct  9 18:07:26 node-2 haproxy[22390]: 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>Oct  9 18:07:26 node-2 haproxy[22390]: Backup Server mysqld/node-4 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>Oct  9 18:07:26 node-2 haproxy[22390]: 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>Oct  9 18:07:26 node-2 haproxy[22390]: proxy mysqld has no server available!
<129>Oct  9 18:07:26 node-2 haproxy[22390]: 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>Oct  9 18:07:26 node-2 haproxy[22390]: Server object-storage/node-4 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>Oct  9 18:07:26 node-2 haproxy[22390]: 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>Oct  9 18:07:26 node-2 haproxy[22390]: proxy object-storage has no server available!
<27>Oct  9 18:07:28 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:28 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:28 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:28 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:28 node-2 multipathd: uevent trigger error
<129>Oct  9 18:07:30 node-2 haproxy[23882]: 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>Oct  9 18:07:30 node-2 haproxy[23882]: Server keystone-1/node-4 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>Oct  9 18:07:30 node-2 haproxy[23882]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:07:30 node-2 haproxy[23882]: proxy keystone-1 has no server available!
<129>Oct  9 18:07:30 node-2 haproxy[23882]: 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>Oct  9 18:07:30 node-2 haproxy[23882]: Server keystone-2/node-4 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>Oct  9 18:07:30 node-2 haproxy[23882]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:07:30 node-2 haproxy[23882]: proxy keystone-2 has no server available!
<129>Oct  9 18:07:30 node-2 haproxy[23882]: 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>Oct  9 18:07:30 node-2 haproxy[23882]: Server neutron/node-4 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>Oct  9 18:07:30 node-2 haproxy[23882]: 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>Oct  9 18:07:30 node-2 haproxy[23882]: proxy neutron has no server available!
<129>Oct  9 18:07:31 node-2 haproxy[23886]: 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>Oct  9 18:07:31 node-2 haproxy[23886]: Backup Server mysqld/node-4 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>Oct  9 18:07:31 node-2 haproxy[23886]: 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>Oct  9 18:07:31 node-2 haproxy[23886]: proxy mysqld has no server available!
<129>Oct  9 18:07:31 node-2 haproxy[23886]: 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>Oct  9 18:07:31 node-2 haproxy[23886]: Server object-storage/node-4 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>Oct  9 18:07:31 node-2 haproxy[23886]: 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>Oct  9 18:07:31 node-2 haproxy[23886]: proxy object-storage has no server available!
<129>Oct  9 18:07:31 node-2 haproxy[23886]: 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>Oct  9 18:07:31 node-2 haproxy[23886]: Server aodh/node-4 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>Oct  9 18:07:31 node-2 haproxy[23886]: 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>Oct  9 18:07:31 node-2 haproxy[23886]: proxy aodh has no server available!
<27>Oct  9 18:07:33 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:33 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:33 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:33 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:33 node-2 multipathd: uevent trigger error
<129>Oct  9 18:07:35 node-2 haproxy[25229]: 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>Oct  9 18:07:35 node-2 haproxy[25229]: Server keystone-1/node-4 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>Oct  9 18:07:35 node-2 haproxy[25229]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:07:35 node-2 haproxy[25229]: proxy keystone-1 has no server available!
<129>Oct  9 18:07:35 node-2 haproxy[25229]: 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>Oct  9 18:07:36 node-2 haproxy[25233]: Server keystone-2/node-4 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>Oct  9 18:07:36 node-2 haproxy[25233]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:07:36 node-2 haproxy[25233]: proxy keystone-2 has no server available!
<129>Oct  9 18:07:36 node-2 haproxy[25233]: 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>Oct  9 18:07:36 node-2 haproxy[25233]: Server neutron/node-4 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>Oct  9 18:07:36 node-2 haproxy[25233]: 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>Oct  9 18:07:36 node-2 haproxy[25233]: proxy neutron has no server available!
<129>Oct  9 18:07:36 node-2 haproxy[25233]: 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>Oct  9 18:07:36 node-2 haproxy[25233]: Backup Server mysqld/node-4 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>Oct  9 18:07:36 node-2 haproxy[25233]: 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>Oct  9 18:07:36 node-2 haproxy[25233]: proxy mysqld has no server available!
<129>Oct  9 18:07:36 node-2 haproxy[25233]: 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>Oct  9 18:07:36 node-2 haproxy[25233]: Server object-storage/node-4 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>Oct  9 18:07:36 node-2 haproxy[25233]: 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>Oct  9 18:07:36 node-2 haproxy[25233]: proxy object-storage has no server available!
<129>Oct  9 18:07:37 node-2 haproxy[25233]: 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>Oct  9 18:07:37 node-2 haproxy[25233]: Server aodh/node-4 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>Oct  9 18:07:37 node-2 haproxy[25233]: 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>Oct  9 18:07:37 node-2 haproxy[25233]: proxy aodh has no server available!
<129>Oct  9 18:07:37 node-2 haproxy[25233]: 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>Oct  9 18:07:37 node-2 haproxy[25233]: Server ceilometer/node-4 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>Oct  9 18:07:37 node-2 haproxy[25233]: 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>Oct  9 18:07:37 node-2 haproxy[25233]: proxy ceilometer has no server available!
<27>Oct  9 18:07:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:39 node-2 multipathd: uevent trigger error
<129>Oct  9 18:07:41 node-2 haproxy[26569]: 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>Oct  9 18:07:41 node-2 haproxy[26569]: Server keystone-1/node-4 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>Oct  9 18:07:41 node-2 haproxy[26569]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:07:41 node-2 haproxy[26569]: proxy keystone-1 has no server available!
<129>Oct  9 18:07:41 node-2 haproxy[26569]: 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>Oct  9 18:07:41 node-2 haproxy[26569]: Server keystone-2/node-4 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>Oct  9 18:07:41 node-2 haproxy[26569]: 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>Oct  9 18:07:41 node-2 haproxy[26569]: proxy keystone-2 has no server available!
<129>Oct  9 18:07:41 node-2 haproxy[26569]: 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>Oct  9 18:07:41 node-2 haproxy[26569]: Server neutron/node-4 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>Oct  9 18:07:41 node-2 haproxy[26569]: 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>Oct  9 18:07:41 node-2 haproxy[26569]: proxy neutron has no server available!
<129>Oct  9 18:07:41 node-2 haproxy[26569]: 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>Oct  9 18:07:42 node-2 haproxy[26578]: Backup Server mysqld/node-4 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>Oct  9 18:07:42 node-2 haproxy[26578]: 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>Oct  9 18:07:42 node-2 haproxy[26578]: proxy mysqld has no server available!
<129>Oct  9 18:07:42 node-2 haproxy[26578]: 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>Oct  9 18:07:42 node-2 haproxy[26578]: Server object-storage/node-4 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>Oct  9 18:07:42 node-2 haproxy[26578]: 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>Oct  9 18:07:42 node-2 haproxy[26578]: proxy object-storage has no server available!
<129>Oct  9 18:07:42 node-2 haproxy[26578]: 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>Oct  9 18:07:42 node-2 haproxy[26578]: Server aodh/node-4 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>Oct  9 18:07:42 node-2 haproxy[26578]: 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>Oct  9 18:07:42 node-2 haproxy[26578]: proxy aodh has no server available!
<129>Oct  9 18:07:42 node-2 haproxy[26578]: 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>Oct  9 18:07:42 node-2 haproxy[26578]: Server ceilometer/node-4 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>Oct  9 18:07:42 node-2 haproxy[26578]: 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>Oct  9 18:07:42 node-2 haproxy[26578]: proxy ceilometer has no server available!
<27>Oct  9 18:07:44 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:44 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:44 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:44 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:44 node-2 multipathd: uevent trigger error
<129>Oct  9 18:07:46 node-2 haproxy[27922]: 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>Oct  9 18:07:46 node-2 haproxy[27922]: 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>Oct  9 18:07:46 node-2 haproxy[27922]: Server keystone-1/node-4 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>Oct  9 18:07:46 node-2 haproxy[27922]: 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>Oct  9 18:07:46 node-2 haproxy[27922]: proxy keystone-1 has no server available!
<129>Oct  9 18:07:46 node-2 haproxy[27922]: 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>Oct  9 18:07:46 node-2 haproxy[27922]: Server keystone-2/node-4 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>Oct  9 18:07:47 node-2 haproxy[27939]: 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>Oct  9 18:07:47 node-2 haproxy[27939]: proxy keystone-2 has no server available!
<129>Oct  9 18:07:47 node-2 haproxy[27939]: 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>Oct  9 18:07:47 node-2 haproxy[27939]: Server neutron/node-4 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>Oct  9 18:07:47 node-2 haproxy[27939]: 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>Oct  9 18:07:47 node-2 haproxy[27939]: proxy neutron has no server available!
<129>Oct  9 18:07:47 node-2 haproxy[27939]: 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>Oct  9 18:07:47 node-2 haproxy[27939]: Backup Server mysqld/node-4 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>Oct  9 18:07:47 node-2 haproxy[27939]: 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>Oct  9 18:07:47 node-2 haproxy[27939]: proxy mysqld has no server available!
<129>Oct  9 18:07:47 node-2 haproxy[27939]: 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>Oct  9 18:07:47 node-2 haproxy[27939]: Server object-storage/node-4 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>Oct  9 18:07:47 node-2 haproxy[27939]: 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>Oct  9 18:07:47 node-2 haproxy[27939]: proxy object-storage has no server available!
<129>Oct  9 18:07:47 node-2 haproxy[27939]: 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>Oct  9 18:07:47 node-2 haproxy[27939]: Server aodh/node-4 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>Oct  9 18:07:48 node-2 haproxy[27939]: 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>Oct  9 18:07:48 node-2 haproxy[27939]: proxy aodh has no server available!
<129>Oct  9 18:07:48 node-2 haproxy[27939]: 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>Oct  9 18:07:48 node-2 haproxy[27939]: Server ceilometer/node-4 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>Oct  9 18:07:48 node-2 haproxy[27939]: 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>Oct  9 18:07:48 node-2 haproxy[27939]: proxy ceilometer has no server available!
<27>Oct  9 18:07:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:49 node-2 multipathd: uevent trigger error
<129>Oct  9 18:07:52 node-2 haproxy[29315]: 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>Oct  9 18:07:52 node-2 haproxy[29315]: 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>Oct  9 18:07:52 node-2 haproxy[29315]: Server keystone-1/node-4 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>Oct  9 18:07:52 node-2 haproxy[29315]: 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>Oct  9 18:07:52 node-2 haproxy[29315]: proxy keystone-1 has no server available!
<129>Oct  9 18:07:52 node-2 haproxy[29315]: 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>Oct  9 18:07:52 node-2 haproxy[29315]: Server keystone-2/node-4 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>Oct  9 18:07:52 node-2 haproxy[29315]: 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>Oct  9 18:07:52 node-2 haproxy[29315]: proxy keystone-2 has no server available!
<129>Oct  9 18:07:52 node-2 haproxy[29315]: 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>Oct  9 18:07:52 node-2 haproxy[29315]: Server glance-api/node-4 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>Oct  9 18:07:52 node-2 haproxy[29315]: 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>Oct  9 18:07:52 node-2 haproxy[29315]: proxy glance-api has no server available!
<129>Oct  9 18:07:52 node-2 haproxy[29315]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: Server glance-glare/node-4 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>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: proxy glance-glare has no server available!
<129>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: Server neutron/node-4 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>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: proxy neutron has no server available!
<129>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: Server glance-registry/node-4 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>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: proxy glance-registry has no server available!
<129>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: Backup Server mysqld/node-4 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>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: proxy mysqld has no server available!
<129>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: Server object-storage/node-4 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>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: proxy object-storage has no server available!
<129>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: Server aodh/node-4 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>Oct  9 18:07:53 node-2 haproxy[29319]: 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>Oct  9 18:07:53 node-2 haproxy[29319]: proxy aodh has no server available!
<129>Oct  9 18:07:54 node-2 haproxy[29319]: 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>Oct  9 18:07:54 node-2 haproxy[29319]: Server ceilometer/node-4 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>Oct  9 18:07:54 node-2 haproxy[29319]: 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>Oct  9 18:07:54 node-2 haproxy[29319]: proxy ceilometer has no server available!
<27>Oct  9 18:07:55 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:55 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:55 node-2 multipathd: uevent trigger error
<27>Oct  9 18:07:55 node-2 multipathd: uevent trigger error
<129>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: Server keystone-1/node-4 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>Oct  9 18:07:58 node-2 haproxy[30728]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:07:58 node-2 haproxy[30728]: proxy keystone-1 has no server available!
<129>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: Server keystone-2/node-4 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>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: proxy keystone-2 has no server available!
<129>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: Server nova-api/node-4 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>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: proxy nova-api has no server available!
<129>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: Server nova-metadata-api/node-4 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>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: proxy nova-metadata-api has no server available!
<129>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: Server glance-api/node-4 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>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: proxy glance-api has no server available!
<129>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: Server glance-glare/node-4 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>Oct  9 18:07:58 node-2 haproxy[30728]: 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>Oct  9 18:07:58 node-2 haproxy[30728]: proxy glance-glare has no server available!
<129>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: Server neutron/node-4 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>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: proxy neutron has no server available!
<129>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: Server glance-registry/node-4 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>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: proxy glance-registry has no server available!
<129>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: Backup Server mysqld/node-4 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>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: proxy mysqld has no server available!
<129>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: Server object-storage/node-4 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>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: proxy object-storage has no server available!
<129>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: Server aodh/node-4 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>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: proxy aodh has no server available!
<129>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: Server ceilometer/node-4 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>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: proxy ceilometer has no server available!
<129>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: Server nova-novncproxy/node-4 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>Oct  9 18:07:59 node-2 haproxy[30732]: 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>Oct  9 18:07:59 node-2 haproxy[30732]: proxy nova-novncproxy has no server available!
<27>Oct  9 18:08:01 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:01 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:01 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:01 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:01 node-2 multipathd: uevent trigger error
<129>Oct  9 18:08:03 node-2 haproxy[32081]: 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>Oct  9 18:08:03 node-2 haproxy[32081]: 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>Oct  9 18:08:03 node-2 haproxy[32081]: Server keystone-1/node-4 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>Oct  9 18:08:03 node-2 haproxy[32081]: 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>Oct  9 18:08:03 node-2 haproxy[32081]: proxy keystone-1 has no server available!
<129>Oct  9 18:08:03 node-2 haproxy[32081]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: Server keystone-2/node-4 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>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: proxy keystone-2 has no server available!
<129>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: Server nova-api/node-4 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>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: proxy nova-api has no server available!
<129>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: Server nova-metadata-api/node-4 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>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: proxy nova-metadata-api has no server available!
<129>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: Backup Server cinder-api/node-4 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>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: proxy cinder-api has no server available!
<129>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: Server glance-api/node-4 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>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: proxy glance-api has no server available!
<129>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: Server glance-glare/node-4 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>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: proxy glance-glare has no server available!
<129>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: Server neutron/node-4 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>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: proxy neutron has no server available!
<129>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: Server glance-registry/node-4 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>Oct  9 18:08:04 node-2 haproxy[32085]: 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>Oct  9 18:08:04 node-2 haproxy[32085]: proxy glance-registry has no server available!
<129>Oct  9 18:08:05 node-2 haproxy[32085]: 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>Oct  9 18:08:05 node-2 haproxy[32085]: Backup Server mysqld/node-4 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>Oct  9 18:08:05 node-2 haproxy[32085]: 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>Oct  9 18:08:05 node-2 haproxy[32085]: proxy mysqld has no server available!
<129>Oct  9 18:08:05 node-2 haproxy[32085]: 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>Oct  9 18:08:05 node-2 haproxy[32085]: Server object-storage/node-4 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>Oct  9 18:08:05 node-2 haproxy[32085]: 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>Oct  9 18:08:05 node-2 haproxy[32085]: proxy object-storage has no server available!
<129>Oct  9 18:08:05 node-2 haproxy[32085]: 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>Oct  9 18:08:05 node-2 haproxy[32085]: Server aodh/node-4 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>Oct  9 18:08:05 node-2 haproxy[32085]: 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>Oct  9 18:08:05 node-2 haproxy[32085]: proxy aodh has no server available!
<129>Oct  9 18:08:05 node-2 haproxy[32085]: 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>Oct  9 18:08:05 node-2 haproxy[32085]: Server ceilometer/node-4 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>Oct  9 18:08:05 node-2 haproxy[32085]: 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>Oct  9 18:08:05 node-2 haproxy[32085]: proxy ceilometer has no server available!
<129>Oct  9 18:08:05 node-2 haproxy[32085]: 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>Oct  9 18:08:05 node-2 haproxy[32085]: Server nova-novncproxy/node-4 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>Oct  9 18:08:05 node-2 haproxy[32085]: 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>Oct  9 18:08:05 node-2 haproxy[32085]: proxy nova-novncproxy has no server available!
<27>Oct  9 18:08:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:06 node-2 multipathd: uevent trigger error
<129>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: Server keystone-1/node-4 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>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: proxy keystone-1 has no server available!
<129>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: Server keystone-2/node-4 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>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: proxy keystone-2 has no server available!
<129>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: Server nova-api/node-4 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>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: proxy nova-api has no server available!
<129>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: Server nova-metadata-api/node-4 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>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: proxy nova-metadata-api has no server available!
<129>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: Backup Server cinder-api/node-4 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>Oct  9 18:08:09 node-2 haproxy[1033]: 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>Oct  9 18:08:09 node-2 haproxy[1033]: proxy cinder-api has no server available!
<129>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: Server glance-api/node-4 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>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: proxy glance-api has no server available!
<129>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: Server glance-glare/node-4 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>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: proxy glance-glare has no server available!
<129>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: Server neutron/node-4 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>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: proxy neutron has no server available!
<129>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: Server glance-registry/node-4 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>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: proxy glance-registry has no server available!
<129>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: Backup Server mysqld/node-4 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>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: proxy mysqld has no server available!
<129>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: Server object-storage/node-4 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>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: proxy object-storage has no server available!
<129>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: Server aodh/node-4 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>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: proxy aodh has no server available!
<129>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: Server ceilometer/node-4 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>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: proxy ceilometer has no server available!
<129>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: Server heat-api/node-4 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>Oct  9 18:08:10 node-2 haproxy[1037]: 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>Oct  9 18:08:10 node-2 haproxy[1037]: proxy heat-api has no server available!
<129>Oct  9 18:08:11 node-2 haproxy[1037]: 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>Oct  9 18:08:11 node-2 haproxy[1037]: Server heat-api-cfn/node-4 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>Oct  9 18:08:11 node-2 haproxy[1037]: 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>Oct  9 18:08:11 node-2 haproxy[1037]: proxy heat-api-cfn has no server available!
<129>Oct  9 18:08:11 node-2 haproxy[1037]: 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>Oct  9 18:08:11 node-2 haproxy[1037]: Server heat-api-cloudwatch/node-4 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>Oct  9 18:08:11 node-2 haproxy[1037]: 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>Oct  9 18:08:11 node-2 haproxy[1037]: proxy heat-api-cloudwatch has no server available!
<129>Oct  9 18:08:11 node-2 haproxy[1037]: 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>Oct  9 18:08:11 node-2 haproxy[1037]: Server nova-novncproxy/node-4 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>Oct  9 18:08:11 node-2 haproxy[1037]: 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>Oct  9 18:08:11 node-2 haproxy[1037]: proxy nova-novncproxy has no server available!
<27>Oct  9 18:08:12 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:12 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:12 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:12 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:12 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:16 node-2 multipathd: uevent trigger error
<27>Oct  9 18:08:22 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  9 18:08:46 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>Oct  9 18:08:48 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct  9 18:09:15 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  9 18:09:18 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  9 18:09:39 node-2 multipathd: uevent trigger error
<27>Oct  9 18:09:39 node-2 multipathd: uevent trigger error
<27>Oct  9 18:09:39 node-2 multipathd: uevent trigger error
<27>Oct  9 18:09:39 node-2 multipathd: uevent trigger error
<27>Oct  9 18:09:39 node-2 multipathd: uevent trigger error
<27>Oct  9 18:11:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:11:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:11:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:11:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:11:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:16 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct  9 18:12:20 node-2 apache2_error [Sun Oct 09 18:12:19.445064 2016] [mpm_event:notice] [pid 11030:tid 139689641637760] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  9 18:12:20 node-2 apache2_error [Sun Oct 09 18:12:19.445207 2016] [core:notice] [pid 11030:tid 139689641637760] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:12:28 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:28 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:28 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:28 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:28 node-2 multipathd: uevent trigger error
<43>Oct  9 18:12:30 node-2 apache2_error [Sun Oct 09 18:12:22.540328 2016] [mpm_event:notice] [pid 11030:tid 139689641637760] AH00491: caught SIGTERM, shutting down
<43>Oct  9 18:12:30 node-2 apache2_error [Sun Oct 09 18:12:23.651063 2016] [mpm_worker:notice] [pid 11409:tid 140400326829952] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  9 18:12:30 node-2 apache2_error [Sun Oct 09 18:12:23.651127 2016] [core:notice] [pid 11409:tid 140400326829952] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:12:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:12:31 node-2 multipathd: uevent trigger error
<43>Oct  9 18:13:40 node-2 apache2_error [Sun Oct 09 18:13:32.939905 2016] [mpm_worker:notice] [pid 11409:tid 140400326829952] AH00295: caught SIGTERM, shutting down
<43>Oct  9 18:13:40 node-2 apache2_error [Sun Oct 09 18:13:33.688014 2016] [mpm_worker:notice] [pid 23053:tid 140058882197376] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  9 18:13:40 node-2 apache2_error [Sun Oct 09 18:13:33.688058 2016] [core:notice] [pid 23053:tid 140058882197376] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  9 18:14:20 node-2 apache2_error [Sun Oct 09 18:14:17.819006 2016] [mpm_worker:notice] [pid 23053:tid 140058882197376] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  9 18:14:20 node-2 apache2_error [Sun Oct 09 18:14:18.201917 2016] [mpm_worker:warn] [pid 23053:tid 140058882197376] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  9 18:14:20 node-2 apache2_error [Sun Oct 09 18:14:18.204417 2016] [mpm_worker:notice] [pid 23053:tid 140058882197376] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  9 18:14:20 node-2 apache2_error [Sun Oct 09 18:14:18.204434 2016] [core:notice] [pid 23053:tid 140058882197376] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:15:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:12 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:12 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:12 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:12 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:12 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:20 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  9 18:15:27 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:27 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:27 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:27 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:27 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:52 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:52 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:52 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:52 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:52 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:52 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:57 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:57 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:57 node-2 multipathd: uevent trigger error
<27>Oct  9 18:15:57 node-2 multipathd: uevent trigger error
<27>Oct  9 18:16:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:16:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:16:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:16:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:16:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:17:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:17:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:17:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:17:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:17:03 node-2 multipathd: uevent trigger error
<27>Oct  9 18:18:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:18:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:18:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:18:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:18:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:18:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:18:28 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  9 18:19:10 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:10 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:10 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:10 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:32 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:32 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:32 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:32 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:19:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:21:29 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  9 18:21:59 node-2 multipathd: uevent trigger error
<27>Oct  9 18:21:59 node-2 multipathd: uevent trigger error
<27>Oct  9 18:21:59 node-2 multipathd: uevent trigger error
<27>Oct  9 18:21:59 node-2 multipathd: uevent trigger error
<27>Oct  9 18:21:59 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:20 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:20 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:20 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:20 node-2 multipathd: uevent trigger error
<27>Oct  9 18:22:20 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:00 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:00 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:00 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:00 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:00 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:00 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:27 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:27 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:27 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:27 node-2 multipathd: uevent trigger error
<27>Oct  9 18:23:27 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:13 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:13 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:13 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:13 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:13 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct  9 18:24:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct  9 18:24:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct  9 18:24:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Oct  9 18:24:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Oct  9 18:24:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:21 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:31 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  9 18:24:35 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:35 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:35 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:35 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:35 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:24:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:25:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:25:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:25:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:25:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:25:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:25:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:25 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:25 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:25 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:25 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:33 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  9 18:27:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:49 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:55 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:55 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:55 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:55 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:55 node-2 multipathd: uevent trigger error
<27>Oct  9 18:27:55 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:30 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:30 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:30 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:30 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:30 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:30 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:34 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:34 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:34 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:34 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:38 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:44 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:44 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:44 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:44 node-2 multipathd: uevent trigger error
<27>Oct  9 18:28:44 node-2 multipathd: uevent trigger error
<27>Oct  9 18:29:36 node-2 multipathd: uevent trigger error
<27>Oct  9 18:29:36 node-2 multipathd: uevent trigger error
<27>Oct  9 18:29:36 node-2 multipathd: uevent trigger error
<27>Oct  9 18:29:36 node-2 multipathd: uevent trigger error
<27>Oct  9 18:29:36 node-2 multipathd: uevent trigger error
<27>Oct  9 18:30:34 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  9 18:30:42 node-2 multipathd: uevent trigger error
<27>Oct  9 18:30:42 node-2 multipathd: uevent trigger error
<27>Oct  9 18:30:42 node-2 multipathd: uevent trigger error
<27>Oct  9 18:30:42 node-2 multipathd: uevent trigger error
<27>Oct  9 18:30:42 node-2 multipathd: uevent trigger error
<27>Oct  9 18:30:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:30:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:30:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:30:58 node-2 multipathd: uevent trigger error
<11>Oct  9 18:31:10 node-2 liberasurecode[10061]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:10 node-2 liberasurecode[10061]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:10 node-2 liberasurecode[10061]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:10 node-2 liberasurecode[10061]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:11 node-2 liberasurecode[10085]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:11 node-2 liberasurecode[10085]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:11 node-2 liberasurecode[10085]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:11 node-2 liberasurecode[10085]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:12 node-2 liberasurecode[11294]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:12 node-2 liberasurecode[11294]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:12 node-2 liberasurecode[11294]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:12 node-2 liberasurecode[11294]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:16 node-2 liberasurecode[12782]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:16 node-2 liberasurecode[12782]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:16 node-2 liberasurecode[12782]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:16 node-2 liberasurecode[12782]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:16 node-2 liberasurecode[12823]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:16 node-2 liberasurecode[12823]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:16 node-2 liberasurecode[12823]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:16 node-2 liberasurecode[12823]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12872]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12872]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12872]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12872]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12958]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12958]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12958]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12958]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12970]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12970]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12970]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12970]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12983]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12983]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12983]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[12983]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[13003]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[13003]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[13003]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:17 node-2 liberasurecode[13003]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:34 node-2 liberasurecode[13961]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:34 node-2 liberasurecode[13961]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:34 node-2 liberasurecode[13961]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:34 node-2 liberasurecode[13961]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  9 18:31:42 node-2 multipathd: uevent trigger error
<27>Oct  9 18:31:42 node-2 multipathd: uevent trigger error
<27>Oct  9 18:31:42 node-2 multipathd: uevent trigger error
<27>Oct  9 18:31:42 node-2 multipathd: uevent trigger error
<43>Oct  9 18:32:31 node-2 apache2_error [Sun Oct 09 18:32:30.108442 2016] [mpm_worker:notice] [pid 23053:tid 140058882197376] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  9 18:32:31 node-2 apache2_error [Sun Oct 09 18:32:30.489842 2016] [mpm_worker:warn] [pid 23053:tid 140058882197376] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  9 18:32:31 node-2 apache2_error [Sun Oct 09 18:32:30.493672 2016] [mpm_worker:notice] [pid 23053:tid 140058882197376] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  9 18:32:31 node-2 apache2_error [Sun Oct 09 18:32:30.493690 2016] [core:notice] [pid 23053:tid 140058882197376] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:33:11 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:11 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:11 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:11 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:11 node-2 multipathd: uevent trigger error
<43>Oct  9 18:33:11 node-2 apache2_error [Sun Oct 09 18:33:07.289960 2016] [mpm_worker:notice] [pid 23053:tid 140058882197376] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  9 18:33:11 node-2 apache2_error [Sun Oct 09 18:33:07.486038 2016] [mpm_worker:warn] [pid 23053:tid 140058882197376] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  9 18:33:11 node-2 apache2_error [Sun Oct 09 18:33:07.495406 2016] [mpm_worker:notice] [pid 23053:tid 140058882197376] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  9 18:33:11 node-2 apache2_error [Sun Oct 09 18:33:07.495440 2016] [core:notice] [pid 23053:tid 140058882197376] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:33:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:36 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  9 18:33:57 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:57 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:57 node-2 multipathd: uevent trigger error
<27>Oct  9 18:33:57 node-2 multipathd: uevent trigger error
<43>Oct  9 18:34:02 node-2 apache2_error [Sun Oct 09 18:33:53.118349 2016] [mpm_worker:notice] [pid 23053:tid 140058882197376] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  9 18:34:02 node-2 apache2_error [Sun Oct 09 18:33:53.505648 2016] [mpm_worker:warn] [pid 23053:tid 140058882197376] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  9 18:34:02 node-2 apache2_error [Sun Oct 09 18:33:53.515668 2016] [mpm_worker:notice] [pid 23053:tid 140058882197376] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  9 18:34:02 node-2 apache2_error [Sun Oct 09 18:33:53.515701 2016] [core:notice] [pid 23053:tid 140058882197376] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:34:04 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:04 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:04 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:04 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:04 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:08 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:09 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:09 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:09 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:14 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:34:52 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:00 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:00 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:00 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:00 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:00 node-2 multipathd: uevent trigger error
<11>Oct  9 18:35:01 node-2 liberasurecode[26980]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:35:01 node-2 liberasurecode[26980]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:35:01 node-2 liberasurecode[26980]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:35:01 node-2 liberasurecode[26980]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  9 18:35:06 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct  9 18:35:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:15 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:19 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:19 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:19 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:19 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:19 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:25 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:25 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:25 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:25 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:25 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:39 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:39 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:39 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:39 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:39 node-2 multipathd: uevent trigger error
<27>Oct  9 18:35:41 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  9 18:36:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:06 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:13 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:13 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:13 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:13 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:18 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:31 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:36 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:36 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:36 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:36 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:48 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:48 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:48 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:48 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:48 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:53 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:53 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:53 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:53 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:53 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:36:58 node-2 multipathd: uevent trigger error
<27>Oct  9 18:37:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:37:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:37:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:37:02 node-2 multipathd: uevent trigger error
<27>Oct  9 18:37:03 node-2 multipathd: uevent trigger error
