Oct  9 18:01:53 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8427" x-info="http://www.rsyslog.com"] start
Oct  9 18:01:53 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct  9 18:01:53 node-5 rsyslogd: rsyslogd's groupid changed to 104
Oct  9 18:01:53 node-5 rsyslogd: rsyslogd's userid changed to 101
Oct  9 18:01:53 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct  9 18:01:53 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct  9 18:01:53 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct  9 18:01:53 node-5 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:53 node-5 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:53 node-5 kernel: [    0.000000] KERNEL supported cpus:
Oct  9 18:01:53 node-5 kernel: [    0.000000]   Intel GenuineIntel
Oct  9 18:01:53 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Oct  9 18:01:53 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Oct  9 18:01:53 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct  9 18:01:53 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct  9 18:01:53 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct  9 18:01:53 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Oct  9 18:01:53 node-5 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:53 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct  9 18:01:53 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct  9 18:01:53 node-5 kernel: [    0.000000] No AGP bridge found
Oct  9 18:01:53 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct  9 18:01:53 node-5 kernel: [    0.000000] MTRR default type: write-back
Oct  9 18:01:53 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct  9 18:01:53 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Oct  9 18:01:53 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct  9 18:01:53 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct  9 18:01:53 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Oct  9 18:01:53 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct  9 18:01:53 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct  9 18:01:53 node-5 kernel: [    0.000000]   2 disabled
Oct  9 18:01:53 node-5 kernel: [    0.000000]   3 disabled
Oct  9 18:01:53 node-5 kernel: [    0.000000]   4 disabled
Oct  9 18:01:53 node-5 kernel: [    0.000000]   5 disabled
Oct  9 18:01:53 node-5 kernel: [    0.000000]   6 disabled
Oct  9 18:01:53 node-5 kernel: [    0.000000]   7 disabled
Oct  9 18:01:53 node-5 kernel: [    0.000000]   8 disabled
Oct  9 18:01:53 node-5 kernel: [    0.000000]   9 disabled
Oct  9 18:01:53 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct  9 18:01:53 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct  9 18:01:53 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct  9 18:01:53 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct  9 18:01:53 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct  9 18:01:53 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Oct  9 18:01:53 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct  9 18:01:53 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct  9 18:01:53 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct  9 18:01:53 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct  9 18:01:53 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct  9 18:01:53 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct  9 18:01:53 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct  9 18:01:53 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct  9 18:01:53 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct  9 18:01:53 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct  9 18:01:53 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct  9 18:01:53 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct  9 18:01:53 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct  9 18:01:53 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct  9 18:01:53 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct  9 18:01:53 node-5 kernel: [    0.000000] Zone ranges:
Oct  9 18:01:53 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] Movable zone start for each node
Oct  9 18:01:53 node-5 kernel: [    0.000000] Early memory node ranges
Oct  9 18:01:53 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct  9 18:01:53 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct  9 18:01:53 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct  9 18:01:53 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct  9 18:01:53 node-5 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct  9 18:01:53 node-5 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct  9 18:01:53 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct  9 18:01:53 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct  9 18:01:53 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct  9 18:01:53 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct  9 18:01:53 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct  9 18:01:53 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct  9 18:01:53 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct  9 18:01:53 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct  9 18:01:53 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct  9 18:01:53 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct  9 18:01:53 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct  9 18:01:53 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct  9 18:01:53 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct  9 18:01:53 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct  9 18:01:53 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct  9 18:01:53 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct  9 18:01:53 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct  9 18:01:53 node-5 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:53 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct  9 18:01:53 node-5 kernel: [    0.000000] Policy zone: Normal
Oct  9 18:01:53 node-5 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:53 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct  9 18:01:53 node-5 kernel: [    0.000000] Checking aperture...
Oct  9 18:01:53 node-5 kernel: [    0.000000] No AGP bridge found
Oct  9 18:01:53 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct  9 18:01:53 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct  9 18:01:53 node-5 kernel: [    0.000000] Memory: 32653320K/33280496K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Oct  9 18:01:53 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct  9 18:01:53 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Oct  9 18:01:53 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct  9 18:01:53 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct  9 18:01:53 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct  9 18:01:53 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct  9 18:01:53 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct  9 18:01:53 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Oct  9 18:01:53 node-5 kernel: [    0.000000] console [tty0] enabled
Oct  9 18:01:53 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct  9 18:01:53 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct  9 18:01:53 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct  9 18:01:53 node-5 kernel: [    0.000000] hpet clockevent registered
Oct  9 18:01:53 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct  9 18:01:53 node-5 kernel: [    0.004000] tsc: Detected 3492.208 MHz processor
Oct  9 18:01:53 node-5 kernel: [    0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.41 BogoMIPS (lpj=13968832)
Oct  9 18:01:53 node-5 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct  9 18:01:53 node-5 kernel: [    0.000043] Security Framework initialized
Oct  9 18:01:53 node-5 kernel: [    0.000071] AppArmor: AppArmor initialized
Oct  9 18:01:53 node-5 kernel: [    0.000072] Yama: becoming mindful.
Oct  9 18:01:53 node-5 kernel: [    0.001446] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.006274] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.008197] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.008225] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.008498] Initializing cgroup subsys memory
Oct  9 18:01:53 node-5 kernel: [    0.008506] Initializing cgroup subsys devices
Oct  9 18:01:53 node-5 kernel: [    0.008508] Initializing cgroup subsys freezer
Oct  9 18:01:53 node-5 kernel: [    0.008510] Initializing cgroup subsys blkio
Oct  9 18:01:53 node-5 kernel: [    0.008511] Initializing cgroup subsys perf_event
Oct  9 18:01:53 node-5 kernel: [    0.008513] Initializing cgroup subsys hugetlb
Oct  9 18:01:53 node-5 kernel: [    0.008533] CPU: Physical Processor ID: 0
Oct  9 18:01:53 node-5 kernel: [    0.008534] CPU: Processor Core ID: 0
Oct  9 18:01:53 node-5 kernel: [    0.008537] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct  9 18:01:53 node-5 kernel: [    0.008537] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct  9 18:01:53 node-5 kernel: [    0.009231] mce: CPU supports 22 MCE banks
Oct  9 18:01:53 node-5 kernel: [    0.009259] CPU0: Thermal monitoring enabled (TM1)
Oct  9 18:01:53 node-5 kernel: [    0.009280] process: using mwait in idle threads
Oct  9 18:01:53 node-5 kernel: [    0.009283] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct  9 18:01:53 node-5 kernel: [    0.009283] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct  9 18:01:53 node-5 kernel: [    0.009283] tlb_flushall_shift: 6
Oct  9 18:01:53 node-5 kernel: [    0.009371] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct  9 18:01:53 node-5 kernel: [    0.010096] ACPI: Core revision 20131115
Oct  9 18:01:53 node-5 kernel: [    0.022774] ACPI: All ACPI Tables successfully acquired
Oct  9 18:01:53 node-5 kernel: [    0.022934] ftrace: allocating 28614 entries in 112 pages
Oct  9 18:01:53 node-5 kernel: [    0.031644] dmar: Host address width 46
Oct  9 18:01:53 node-5 kernel: [    0.031647] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct  9 18:01:53 node-5 kernel: [    0.031652] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  9 18:01:53 node-5 kernel: [    0.031654] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct  9 18:01:53 node-5 kernel: [    0.031658] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  9 18:01:53 node-5 kernel: [    0.031660] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct  9 18:01:53 node-5 kernel: [    0.031661] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct  9 18:01:53 node-5 kernel: [    0.031662] dmar: ATSR flags: 0x0
Oct  9 18:01:53 node-5 kernel: [    0.031663] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct  9 18:01:53 node-5 kernel: [    0.031664] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct  9 18:01:53 node-5 kernel: [    0.031780] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct  9 18:01:53 node-5 kernel: [    0.031781] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct  9 18:01:53 node-5 kernel: [    0.031782] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct  9 18:01:53 node-5 kernel: [    0.031783] HPET id 0 under DRHD base 0xc7ffc000
Oct  9 18:01:53 node-5 kernel: [    0.031784] Your BIOS is broken and requested that x2apic be disabled.
Oct  9 18:01:53 node-5 kernel: [    0.031784] This will slightly decrease performance.
Oct  9 18:01:53 node-5 kernel: [    0.031784] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct  9 18:01:53 node-5 kernel: [    0.032214] Enabled IRQ remapping in xapic mode
Oct  9 18:01:53 node-5 kernel: [    0.032216] x2apic not enabled, IRQ remapping is in xapic mode
Oct  9 18:01:53 node-5 kernel: [    0.032219] Switched APIC routing to physical flat.
Oct  9 18:01:53 node-5 kernel: [    0.032833] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct  9 18:01:53 node-5 kernel: [    0.072486] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct  9 18:01:53 node-5 kernel: [    0.072492] TSC deadline timer enabled
Oct  9 18:01:53 node-5 kernel: [    0.072500] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct  9 18:01:53 node-5 kernel: [    0.072506] ... version:                3
Oct  9 18:01:53 node-5 kernel: [    0.072507] ... bit width:              48
Oct  9 18:01:53 node-5 kernel: [    0.072508] ... generic registers:      4
Oct  9 18:01:53 node-5 kernel: [    0.072509] ... value mask:             0000ffffffffffff
Oct  9 18:01:53 node-5 kernel: [    0.072509] ... max period:             0000ffffffffffff
Oct  9 18:01:53 node-5 kernel: [    0.072510] ... fixed-purpose events:   3
Oct  9 18:01:53 node-5 kernel: [    0.072511] ... event mask:             000000070000000f
Oct  9 18:01:53 node-5 kernel: [    0.073901] x86: Booting SMP configuration:
Oct  9 18:01:53 node-5 kernel: [    0.088004] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct  9 18:01:53 node-5 kernel: [    0.073903] .... node  #0, CPUs:        #1  #2  #3
Oct  9 18:01:53 node-5 kernel: [    0.115916] .... node  #1, CPUs:    #4  #5  #6  #7
Oct  9 18:01:53 node-5 kernel: [    0.269764] .... node  #0, CPUs:    #8  #9 #10 #11
Oct  9 18:01:53 node-5 kernel: [    0.325379] .... node  #1, CPUs:   #12 #13 #14 #15
Oct  9 18:01:53 node-5 kernel: [    0.382241] x86: Booted up 2 nodes, 16 CPUs
Oct  9 18:01:53 node-5 kernel: [    0.382245] smpboot: Total of 16 processors activated (111763.57 BogoMIPS)
Oct  9 18:01:53 node-5 kernel: [    0.406420] devtmpfs: initialized
Oct  9 18:01:53 node-5 kernel: [    0.408928] EVM: security.selinux
Oct  9 18:01:53 node-5 kernel: [    0.408929] EVM: security.SMACK64
Oct  9 18:01:53 node-5 kernel: [    0.408930] EVM: security.ima
Oct  9 18:01:53 node-5 kernel: [    0.408931] EVM: security.capability
Oct  9 18:01:53 node-5 kernel: [    0.408994] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.409634] pinctrl core: initialized pinctrl subsystem
Oct  9 18:01:53 node-5 kernel: [    0.409696] regulator-dummy: no parameters
Oct  9 18:01:53 node-5 kernel: [    0.409727] RTC time: 18:01:14, date: 10/09/16
Oct  9 18:01:53 node-5 kernel: [    0.409760] NET: Registered protocol family 16
Oct  9 18:01:53 node-5 kernel: [    0.409844] cpuidle: using governor ladder
Oct  9 18:01:53 node-5 kernel: [    0.409846] cpuidle: using governor menu
Oct  9 18:01:53 node-5 kernel: [    0.409880] ACPI: bus type PCI registered
Oct  9 18:01:53 node-5 kernel: [    0.409882] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct  9 18:01:53 node-5 kernel: [    0.409941] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct  9 18:01:53 node-5 kernel: [    0.409944] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct  9 18:01:53 node-5 kernel: [    0.423667] PCI: Using configuration type 1 for base access
Oct  9 18:01:53 node-5 kernel: [    0.424668] bio: create slab <bio-0> at 0
Oct  9 18:01:53 node-5 kernel: [    0.424945] ACPI: Added _OSI(Module Device)
Oct  9 18:01:53 node-5 kernel: [    0.424946] ACPI: Added _OSI(Processor Device)
Oct  9 18:01:53 node-5 kernel: [    0.424948] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct  9 18:01:53 node-5 kernel: [    0.424949] ACPI: Added _OSI(Processor Aggregator Device)
Oct  9 18:01:53 node-5 kernel: [    0.437765] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct  9 18:01:53 node-5 kernel: [    0.448323] ACPI: Interpreter enabled
Oct  9 18:01:53 node-5 kernel: [    0.448328] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct  9 18:01:53 node-5 kernel: [    0.448332] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct  9 18:01:53 node-5 kernel: [    0.448334] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct  9 18:01:53 node-5 kernel: [    0.448341] ACPI: (supports S0 S4 S5)
Oct  9 18:01:53 node-5 kernel: [    0.448342] ACPI: Using IOAPIC for interrupt routing
Oct  9 18:01:53 node-5 kernel: [    0.448383] HEST: Table parsing has been initialized.
Oct  9 18:01:53 node-5 kernel: [    0.448386] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct  9 18:01:53 node-5 kernel: [    0.448945] ACPI: No dock devices found.
Oct  9 18:01:53 node-5 kernel: [    0.460625] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct  9 18:01:53 node-5 kernel: [    0.460630] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  9 18:01:53 node-5 kernel: [    0.460633] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  9 18:01:53 node-5 kernel: [    0.460662] PCI host bridge to bus 0000:ff
Oct  9 18:01:53 node-5 kernel: [    0.460664] pci_bus 0000:ff: root bus resource [bus ff]
Oct  9 18:01:53 node-5 kernel: [    0.460672] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.460710] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.460741] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.460777] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.460806] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.460836] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.460868] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.460897] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.460928] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.460956] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.460983] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461011] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461040] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461066] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461093] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461120] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461149] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461177] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461204] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.461233] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461259] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.461285] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461311] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461341] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.461375] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461406] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461436] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461467] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461497] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461528] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461559] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461589] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461620] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461653] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461685] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461717] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461750] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461781] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461808] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461840] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461872] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461908] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct  9 18:01:53 node-5 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:53 node-5 kernel: [    0.461941] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.461974] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462003] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462032] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462062] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462091] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462122] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462153] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462184] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462214] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462243] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462272] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462302] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462334] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462366] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462424] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct  9 18:01:53 node-5 kernel: [    0.462427] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  9 18:01:53 node-5 kernel: [    0.462429] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  9 18:01:53 node-5 kernel: [    0.462448] PCI host bridge to bus 0000:7f
Oct  9 18:01:53 node-5 kernel: [    0.462449] pci_bus 0000:7f: root bus resource [bus 7f]
Oct  9 18:01:53 node-5 kernel: [    0.462454] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462482] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.462511] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462541] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462568] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.462593] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.462622] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462649] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462671] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462694] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462717] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462739] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462763] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462785] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462809] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462836] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462858] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462881] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462904] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.462930] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.462955] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.462979] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463004] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463033] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct  9 18:01:53 node-5 kernel: [    0.463067] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463093] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463120] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463146] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463172] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463198] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463224] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463252] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463277] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463306] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463334] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463363] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463392] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463418] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463448] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463476] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463502] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463528] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463556] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463583] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463608] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463635] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463661] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463688] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463713] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463740] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463771] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463795] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463817] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463842] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463868] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463898] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.463925] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.465185] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct  9 18:01:53 node-5 kernel: [    0.465188] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  9 18:01:53 node-5 kernel: [    0.466327] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  9 18:01:53 node-5 kernel: [    0.466837] PCI host bridge to bus 0000:00
Oct  9 18:01:53 node-5 kernel: [    0.466840] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct  9 18:01:53 node-5 kernel: [    0.466841] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct  9 18:01:53 node-5 kernel: [    0.466843] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct  9 18:01:53 node-5 kernel: [    0.466844] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct  9 18:01:53 node-5 kernel: [    0.466845] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct  9 18:01:53 node-5 kernel: [    0.466847] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct  9 18:01:53 node-5 kernel: [    0.466848] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct  9 18:01:53 node-5 kernel: [    0.466854] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct  9 18:01:53 node-5 kernel: [    0.466937] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.466968] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.467009] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct  9 18:01:53 node-5 kernel: [    0.467029] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.467058] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.467099] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct  9 18:01:53 node-5 kernel: [    0.467116] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.467145] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.467189] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct  9 18:01:53 node-5 kernel: [    0.467204] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.467275] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.467352] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.467433] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct  9 18:01:53 node-5 kernel: [    0.467438] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct  9 18:01:53 node-5 kernel: [    0.467524] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct  9 18:01:53 node-5 kernel: [    0.467672] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct  9 18:01:53 node-5 kernel: [    0.467689] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct  9 18:01:53 node-5 kernel: [    0.467766] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.467822] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct  9 18:01:53 node-5 kernel: [    0.467844] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.467900] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.467943] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct  9 18:01:53 node-5 kernel: [    0.467972] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.468028] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.468071] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct  9 18:01:53 node-5 kernel: [    0.468096] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct  9 18:01:53 node-5 kernel: [    0.468114] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct  9 18:01:53 node-5 kernel: [    0.468191] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.468241] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct  9 18:01:53 node-5 kernel: [    0.468268] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct  9 18:01:53 node-5 kernel: [    0.468518] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct  9 18:01:53 node-5 kernel: [    0.468524] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct  9 18:01:53 node-5 kernel: [    0.468530] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.468536] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.468543] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct  9 18:01:53 node-5 kernel: [    0.468573] pci 0000:01:00.0: supports D1 D2
Oct  9 18:01:53 node-5 kernel: [    0.478562] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  9 18:01:53 node-5 kernel: [    0.478569] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  9 18:01:53 node-5 kernel: [    0.478573] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  9 18:01:53 node-5 kernel: [    0.478710] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.478744] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct  9 18:01:53 node-5 kernel: [    0.486560] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  9 18:01:53 node-5 kernel: [    0.486567] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.486571] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:53 node-5 kernel: [    0.486656] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.486729] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.486820] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.486866] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  9 18:01:53 node-5 kernel: [    0.486869] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.486871] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:53 node-5 kernel: [    0.486924] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.487050] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.487104] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  9 18:01:53 node-5 kernel: [    0.487107] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.487109] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:53 node-5 kernel: [    0.487158] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.487277] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.487317] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.487458] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.487495] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.487614] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.487651] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct  9 18:01:53 node-5 kernel: [    0.487770] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct  9 18:01:53 node-5 kernel: [    0.487812] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  9 18:01:53 node-5 kernel: [    0.487815] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.487817] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:53 node-5 kernel: [    0.487876] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct  9 18:01:53 node-5 kernel: [    0.487941] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.487993] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.488035] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct  9 18:01:53 node-5 kernel: [    0.488117] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct  9 18:01:53 node-5 kernel: [    0.488222] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  9 18:01:53 node-5 kernel: [    0.488224] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.488226] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  9 18:01:53 node-5 kernel: [    0.488283] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct  9 18:01:53 node-5 kernel: [    0.488336] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.488410] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.488622] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  9 18:01:53 node-5 kernel: [    0.488625] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  9 18:01:53 node-5 kernel: [    0.488687] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct  9 18:01:53 node-5 kernel: [    0.488740] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.488789] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.488998] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  9 18:01:53 node-5 kernel: [    0.489002] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  9 18:01:53 node-5 kernel: [    0.489061] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct  9 18:01:53 node-5 kernel: [    0.489120] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.489173] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct  9 18:01:53 node-5 kernel: [    0.489414] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  9 18:01:53 node-5 kernel: [    0.489417] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  9 18:01:53 node-5 kernel: [    0.489595] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  9 18:01:53 node-5 kernel: [    0.489633] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  9 18:01:53 node-5 kernel: [    0.489707] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct  9 18:01:53 node-5 kernel: [    0.489725] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct  9 18:01:53 node-5 kernel: [    0.489738] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct  9 18:01:53 node-5 kernel: [    0.489752] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct  9 18:01:53 node-5 kernel: [    0.489802] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct  9 18:01:53 node-5 kernel: [    0.494567] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  9 18:01:53 node-5 kernel: [    0.494576] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  9 18:01:53 node-5 kernel: [    0.494629] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct  9 18:01:53 node-5 kernel: [    0.495366] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct  9 18:01:53 node-5 kernel: [    0.495369] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  9 18:01:53 node-5 kernel: [    0.495493] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  9 18:01:53 node-5 kernel: [    0.495601] PCI host bridge to bus 0000:80
Oct  9 18:01:53 node-5 kernel: [    0.495603] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct  9 18:01:53 node-5 kernel: [    0.495604] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct  9 18:01:53 node-5 kernel: [    0.495605] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct  9 18:01:53 node-5 kernel: [    0.495614] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.495675] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.495744] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct  9 18:01:53 node-5 kernel: [    0.495806] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct  9 18:01:53 node-5 kernel: [    0.495811] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct  9 18:01:53 node-5 kernel: [    0.495881] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct  9 18:01:53 node-5 kernel: [    0.496183] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct  9 18:01:53 node-5 kernel: [    0.496215] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct  9 18:01:53 node-5 kernel: [    0.496245] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct  9 18:01:53 node-5 kernel: [    0.496274] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct  9 18:01:53 node-5 kernel: [    0.496303] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  9 18:01:53 node-5 kernel: [    0.496333] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  9 18:01:53 node-5 kernel: [    0.496363] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  9 18:01:53 node-5 kernel: [    0.496393] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  9 18:01:53 node-5 kernel: [    0.496478] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct  9 18:01:53 node-5 kernel: [    0.496482] ACPI: \_SB_.UNC1: notify handler is installed
Oct  9 18:01:53 node-5 kernel: [    0.496483] ACPI: \_SB_.UNC0: notify handler is installed
Oct  9 18:01:53 node-5 kernel: [    0.496499] ACPI: \_SB_.PCI0: notify handler is installed
Oct  9 18:01:53 node-5 kernel: [    0.496552] ACPI: \_SB_.PCI1: notify handler is installed
Oct  9 18:01:53 node-5 kernel: [    0.496631] Found 4 acpi root devices
Oct  9 18:01:53 node-5 kernel: [    0.496738] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct  9 18:01:53 node-5 kernel: [    0.496740] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct  9 18:01:53 node-5 kernel: [    0.496742] vgaarb: loaded
Oct  9 18:01:53 node-5 kernel: [    0.496743] vgaarb: bridge control possible 0000:0c:00.0
Oct  9 18:01:53 node-5 kernel: [    0.496858] SCSI subsystem initialized
Oct  9 18:01:53 node-5 kernel: [    0.496923] libata version 3.00 loaded.
Oct  9 18:01:53 node-5 kernel: [    0.496938] ACPI: bus type USB registered
Oct  9 18:01:53 node-5 kernel: [    0.496948] usbcore: registered new interface driver usbfs
Oct  9 18:01:53 node-5 kernel: [    0.496953] usbcore: registered new interface driver hub
Oct  9 18:01:53 node-5 kernel: [    0.496977] usbcore: registered new device driver usb
Oct  9 18:01:53 node-5 kernel: [    0.497138] PCI: Using ACPI for IRQ routing
Oct  9 18:01:53 node-5 kernel: [    0.500745] PCI: pci_cache_line_size set to 64 bytes
Oct  9 18:01:53 node-5 kernel: [    0.500957] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct  9 18:01:53 node-5 kernel: [    0.500958] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct  9 18:01:53 node-5 kernel: [    0.500959] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct  9 18:01:53 node-5 kernel: [    0.501023] NetLabel: Initializing
Oct  9 18:01:53 node-5 kernel: [    0.501024] NetLabel:  domain hash size = 128
Oct  9 18:01:53 node-5 kernel: [    0.501025] NetLabel:  protocols = UNLABELED CIPSOv4
Oct  9 18:01:53 node-5 kernel: [    0.501035] NetLabel:  unlabeled traffic allowed by default
Oct  9 18:01:53 node-5 kernel: [    0.501093] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct  9 18:01:53 node-5 kernel: [    0.501097] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct  9 18:01:53 node-5 kernel: [    0.503157] Switched to clocksource hpet
Oct  9 18:01:53 node-5 kernel: [    0.506986] AppArmor: AppArmor Filesystem Enabled
Oct  9 18:01:53 node-5 kernel: [    0.507002] pnp: PnP ACPI init
Oct  9 18:01:53 node-5 kernel: [    0.507008] ACPI: bus type PNP registered
Oct  9 18:01:53 node-5 kernel: [    0.507127] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct  9 18:01:53 node-5 kernel: [    0.507135] pnp 00:01: [dma 4]
Oct  9 18:01:53 node-5 kernel: [    0.507147] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct  9 18:01:53 node-5 kernel: [    0.507179] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct  9 18:01:53 node-5 kernel: [    0.507199] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct  9 18:01:53 node-5 kernel: [    0.507216] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct  9 18:01:53 node-5 kernel: [    0.507249] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct  9 18:01:53 node-5 kernel: [    0.507301] system 00:06: [io  0x0500-0x057f] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507304] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct  9 18:01:53 node-5 kernel: [    0.507305] system 00:06: [io  0x0580-0x059f] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507307] system 00:06: [io  0x0600-0x061f] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507308] system 00:06: [io  0x0880-0x0883] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507313] system 00:06: [io  0x0800-0x081f] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507315] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct  9 18:01:53 node-5 kernel: [    0.507317] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507318] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507320] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507321] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507323] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507324] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct  9 18:01:53 node-5 kernel: [    0.507326] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct  9 18:01:53 node-5 kernel: [    0.507410] pnp 00:07: [dma 0 disabled]
Oct  9 18:01:53 node-5 kernel: [    0.507438] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  9 18:01:53 node-5 kernel: [    0.507513] pnp 00:08: [dma 0 disabled]
Oct  9 18:01:53 node-5 kernel: [    0.507546] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  9 18:01:53 node-5 kernel: [    0.507596] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct  9 18:01:53 node-5 kernel: [    0.507951] pnp: PnP ACPI: found 10 devices
Oct  9 18:01:53 node-5 kernel: [    0.507953] ACPI: bus type PNP unregistered
Oct  9 18:01:53 node-5 kernel: [    0.514241] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  9 18:01:53 node-5 kernel: [    0.514244] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  9 18:01:53 node-5 kernel: [    0.514247] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  9 18:01:53 node-5 kernel: [    0.514251] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  9 18:01:53 node-5 kernel: [    0.514253] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.514268] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514300] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  9 18:01:53 node-5 kernel: [    0.514314] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514358] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  9 18:01:53 node-5 kernel: [    0.514372] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  9 18:01:53 node-5 kernel: [    0.514401] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  9 18:01:53 node-5 kernel: [    0.514416] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  9 18:01:53 node-5 kernel: [    0.514444] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  9 18:01:53 node-5 kernel: [    0.514446] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.514461] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514489] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  9 18:01:53 node-5 kernel: [    0.514491] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.514506] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514535] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  9 18:01:53 node-5 kernel: [    0.514536] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.514539] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514543] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  9 18:01:53 node-5 kernel: [    0.514545] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.514547] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514551] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  9 18:01:53 node-5 kernel: [    0.514556] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  9 18:01:53 node-5 kernel: [    0.514564] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  9 18:01:53 node-5 kernel: [    0.514567] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  9 18:01:53 node-5 kernel: [    0.514574] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct  9 18:01:53 node-5 kernel: [    0.514574] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct  9 18:01:53 node-5 kernel: [    0.514575] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct  9 18:01:53 node-5 kernel: [    0.514576] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct  9 18:01:53 node-5 kernel: [    0.514577] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct  9 18:01:53 node-5 kernel: [    0.514578] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct  9 18:01:53 node-5 kernel: [    0.514579] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct  9 18:01:53 node-5 kernel: [    0.514580] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct  9 18:01:53 node-5 kernel: [    0.514581] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.514582] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514583] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.514583] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514584] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.514585] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514586] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.514587] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514588] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct  9 18:01:53 node-5 kernel: [    0.514589] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514590] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct  9 18:01:53 node-5 kernel: [    0.514591] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct  9 18:01:53 node-5 kernel: [    0.514592] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct  9 18:01:53 node-5 kernel: [    0.514593] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct  9 18:01:53 node-5 kernel: [    0.514595] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct  9 18:01:53 node-5 kernel: [    0.514596] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct  9 18:01:53 node-5 kernel: [    0.514637] NET: Registered protocol family 2
Oct  9 18:01:53 node-5 kernel: [    0.514892] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.515228] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.515373] TCP: Hash tables configured (established 262144 bind 65536)
Oct  9 18:01:53 node-5 kernel: [    0.515415] TCP: reno registered
Oct  9 18:01:53 node-5 kernel: [    0.515443] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.515539] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.515693] NET: Registered protocol family 1
Oct  9 18:01:53 node-5 kernel: [    0.551271] pci 0000:0c:00.0: Video device with shadowed ROM
Oct  9 18:01:53 node-5 kernel: [    0.551278] PCI: CLS 64 bytes, default 64
Oct  9 18:01:53 node-5 kernel: [    0.551319] Trying to unpack rootfs image as initramfs...
Oct  9 18:01:53 node-5 kernel: [    0.770123] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Oct  9 18:01:53 node-5 kernel: [    0.770170] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct  9 18:01:53 node-5 kernel: [    0.770172] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct  9 18:01:53 node-5 kernel: [    0.770568] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770574] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770578] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770584] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770596] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770612] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770640] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770649] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770656] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770665] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770671] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770677] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770684] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770692] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770699] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770706] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct  9 18:01:53 node-5 kernel: [    0.770785] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct  9 18:01:53 node-5 kernel: [    0.770788] Scanning for low memory corruption every 60 seconds
Oct  9 18:01:53 node-5 kernel: [    0.771182] Initialise system trusted keyring
Oct  9 18:01:53 node-5 kernel: [    0.771235] audit: initializing netlink socket (disabled)
Oct  9 18:01:53 node-5 kernel: [    0.771251] type=2000 audit(1476036073.720:1): initialized
Oct  9 18:01:53 node-5 kernel: [    0.789020] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct  9 18:01:53 node-5 kernel: [    0.790580] zbud: loaded
Oct  9 18:01:53 node-5 kernel: [    0.790706] VFS: Disk quotas dquot_6.5.2
Oct  9 18:01:53 node-5 kernel: [    0.790746] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct  9 18:01:53 node-5 kernel: [    0.791128] fuse init (API version 7.22)
Oct  9 18:01:53 node-5 kernel: [    0.791190] msgmni has been set to 32768
Oct  9 18:01:53 node-5 kernel: [    0.791238] Key type big_key registered
Oct  9 18:01:53 node-5 kernel: [    0.791778] Key type asymmetric registered
Oct  9 18:01:53 node-5 kernel: [    0.791784] Asymmetric key parser 'x509' registered
Oct  9 18:01:53 node-5 kernel: [    0.791809] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct  9 18:01:53 node-5 kernel: [    0.791889] io scheduler noop registered
Oct  9 18:01:53 node-5 kernel: [    0.791891] io scheduler deadline registered (default)
Oct  9 18:01:53 node-5 kernel: [    0.791910] io scheduler cfq registered
Oct  9 18:01:53 node-5 kernel: [    0.792310] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    0.792444] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    0.792560] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    0.792672] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    0.792788] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    0.792896] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    0.793281] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct  9 18:01:53 node-5 kernel: [    0.793307] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct  9 18:01:53 node-5 kernel: [    0.793323] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct  9 18:01:53 node-5 kernel: [    0.793332] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793334] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793337] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct  9 18:01:53 node-5 kernel: [    0.793342] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793344] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793345] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793347] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793348] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793350] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793351] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793352] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793354] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793355] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793357] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793358] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793361] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct  9 18:01:53 node-5 kernel: [    0.793366] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793368] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct  9 18:01:53 node-5 kernel: [    0.793383] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793386] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct  9 18:01:53 node-5 kernel: [    0.793397] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793398] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct  9 18:01:53 node-5 kernel: [    0.793401] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct  9 18:01:53 node-5 kernel: [    0.793437] ioapic: probe of 0000:00:05.4 failed with error -22
Oct  9 18:01:53 node-5 kernel: [    0.793443] ioapic: probe of 0000:80:05.4 failed with error -22
Oct  9 18:01:53 node-5 kernel: [    0.793448] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct  9 18:01:53 node-5 kernel: [    0.793457] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct  9 18:01:53 node-5 kernel: [    0.793498] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct  9 18:01:53 node-5 kernel: [    0.793500] vesafb: scrolling: redraw
Oct  9 18:01:53 node-5 kernel: [    0.793501] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct  9 18:01:53 node-5 kernel: [    0.814157] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct  9 18:01:53 node-5 kernel: [    0.822664] Console: switching to colour frame buffer device 80x30
Oct  9 18:01:53 node-5 kernel: [    0.831349] fb0: VESA VGA frame buffer device
Oct  9 18:01:53 node-5 kernel: [    0.831546] intel_idle: MWAIT substates: 0x2120
Oct  9 18:01:53 node-5 kernel: [    0.831547] intel_idle: v0.4 model 0x3F
Oct  9 18:01:53 node-5 kernel: [    0.831548] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct  9 18:01:53 node-5 kernel: [    0.831782] ipmi message handler version 39.2
Oct  9 18:01:53 node-5 kernel: [    0.832054] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  9 18:01:53 node-5 kernel: [    0.832487] ACPI: AC Adapter [P111] (on-line)
Oct  9 18:01:53 node-5 kernel: [    0.837726] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct  9 18:01:53 node-5 kernel: [    0.848769] ACPI: Power Button [PWRB]
Oct  9 18:01:53 node-5 kernel: [    0.854617] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct  9 18:01:53 node-5 kernel: [    0.866277] ACPI: Power Button [PWRF]
Oct  9 18:01:53 node-5 kernel: [    0.892703] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct  9 18:01:53 node-5 kernel: [    0.904386] pstore: Registered erst as persistent store backend
Oct  9 18:01:53 node-5 kernel: [    0.910605] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct  9 18:01:53 node-5 kernel: [    0.922578] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct  9 18:01:53 node-5 kernel: [    0.949342] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct  9 18:01:53 node-5 kernel: [    0.982648] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct  9 18:01:53 node-5 kernel: [    0.996738] Linux agpgart interface v0.103
Oct  9 18:01:53 node-5 kernel: [    1.004361] brd: module loaded
Oct  9 18:01:53 node-5 kernel: [    1.011406] loop: module loaded
Oct  9 18:01:53 node-5 kernel: [    1.018149] libphy: Fixed MDIO Bus: probed
Oct  9 18:01:53 node-5 kernel: [    1.024616] tun: Universal TUN/TAP device driver, 1.6
Oct  9 18:01:53 node-5 kernel: [    1.031108] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct  9 18:01:53 node-5 kernel: [    1.037652] PPP generic driver version 2.4.2
Oct  9 18:01:53 node-5 kernel: [    1.044096] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct  9 18:01:53 node-5 kernel: [    1.050576] ehci-pci: EHCI PCI platform driver
Oct  9 18:01:53 node-5 kernel: [    1.057113] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct  9 18:01:53 node-5 kernel: [    1.063560] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct  9 18:01:53 node-5 kernel: [    1.076152] ehci-pci 0000:00:1a.0: debug port 2
Oct  9 18:01:53 node-5 kernel: [    1.086400] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct  9 18:01:53 node-5 kernel: [    1.086418] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct  9 18:01:53 node-5 kernel: [    1.102654] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct  9 18:01:53 node-5 kernel: [    1.108813] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct  9 18:01:53 node-5 kernel: [    1.115114] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  9 18:01:53 node-5 kernel: [    1.127129] usb usb1: Product: EHCI Host Controller
Oct  9 18:01:53 node-5 kernel: [    1.133189] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  9 18:01:53 node-5 kernel: [    1.139266] usb usb1: SerialNumber: 0000:00:1a.0
Oct  9 18:01:53 node-5 kernel: [    1.145244] hub 1-0:1.0: USB hub found
Oct  9 18:01:53 node-5 kernel: [    1.151046] hub 1-0:1.0: 2 ports detected
Oct  9 18:01:53 node-5 kernel: [    1.156873] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct  9 18:01:53 node-5 kernel: [    1.162496] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct  9 18:01:53 node-5 kernel: [    1.173521] ehci-pci 0000:00:1d.0: debug port 2
Oct  9 18:01:53 node-5 kernel: [    1.182903] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct  9 18:01:53 node-5 kernel: [    1.182906] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct  9 18:01:53 node-5 kernel: [    1.198572] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct  9 18:01:53 node-5 kernel: [    1.203774] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct  9 18:01:53 node-5 kernel: [    1.209088] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  9 18:01:53 node-5 kernel: [    1.219659] usb usb2: Product: EHCI Host Controller
Oct  9 18:01:53 node-5 kernel: [    1.225127] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  9 18:01:53 node-5 kernel: [    1.230674] usb usb2: SerialNumber: 0000:00:1d.0
Oct  9 18:01:53 node-5 kernel: [    1.236192] hub 2-0:1.0: USB hub found
Oct  9 18:01:53 node-5 kernel: [    1.241544] hub 2-0:1.0: 2 ports detected
Oct  9 18:01:53 node-5 kernel: [    1.246842] ehci-platform: EHCI generic platform driver
Oct  9 18:01:53 node-5 kernel: [    1.252070] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct  9 18:01:53 node-5 kernel: [    1.257378] ohci-pci: OHCI PCI platform driver
Oct  9 18:01:53 node-5 kernel: [    1.262675] ohci-platform: OHCI generic platform driver
Oct  9 18:01:53 node-5 kernel: [    1.267879] uhci_hcd: USB Universal Host Controller Interface driver
Oct  9 18:01:53 node-5 kernel: [    1.273202] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct  9 18:01:53 node-5 kernel: [    1.466349] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct  9 18:01:53 node-5 kernel: [    1.626509] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct  9 18:01:53 node-5 kernel: [    1.632021] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  9 18:01:53 node-5 kernel: [    1.637776] hub 1-1:1.0: USB hub found
Oct  9 18:01:53 node-5 kernel: [    1.643247] hub 1-1:1.0: 6 ports detected
Oct  9 18:01:53 node-5 kernel: [    1.758096] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct  9 18:01:53 node-5 kernel: [    1.766154] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct  9 18:01:53 node-5 kernel: [    2.026170] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct  9 18:01:53 node-5 kernel: [    2.031715] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  9 18:01:53 node-5 kernel: [    2.037563] hub 2-1:1.0: USB hub found
Oct  9 18:01:53 node-5 kernel: [    2.043157] hub 2-1:1.0: 8 ports detected
Oct  9 18:01:53 node-5 kernel: [    2.314919] i8042: No controller found
Oct  9 18:01:53 node-5 kernel: [    2.320346] mousedev: PS/2 mouse device common for all mice
Oct  9 18:01:53 node-5 kernel: [    2.321741] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct  9 18:01:53 node-5 kernel: [    2.331502] rtc_cmos 00:02: RTC can wake from S4
Oct  9 18:01:53 node-5 kernel: [    2.337310] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct  9 18:01:53 node-5 kernel: [    2.342984] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct  9 18:01:53 node-5 kernel: [    2.354078] device-mapper: uevent: version 1.0.3
Oct  9 18:01:53 node-5 kernel: [    2.359719] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct  9 18:01:53 node-5 kernel: [    2.371029] ledtrig-cpu: registered to indicate activity on CPUs
Oct  9 18:01:53 node-5 kernel: [    2.376943] TCP: cubic registered
Oct  9 18:01:53 node-5 kernel: [    2.382829] NET: Registered protocol family 10
Oct  9 18:01:53 node-5 kernel: [    2.388821] NET: Registered protocol family 17
Oct  9 18:01:53 node-5 kernel: [    2.394478] Key type dns_resolver registered
Oct  9 18:01:53 node-5 kernel: [    2.400448] Loading compiled-in X.509 certificates
Oct  9 18:01:53 node-5 kernel: [    2.406605] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct  9 18:01:53 node-5 kernel: [    2.417980] registered taskstats version 1
Oct  9 18:01:53 node-5 kernel: [    2.425921] Key type trusted registered
Oct  9 18:01:53 node-5 kernel: [    2.433462] Key type encrypted registered
Oct  9 18:01:53 node-5 kernel: [    2.438915] AppArmor: AppArmor sha1 policy hashing enabled
Oct  9 18:01:53 node-5 kernel: [    2.444398] IMA: No TPM chip found, activating TPM-bypass!
Oct  9 18:01:53 node-5 kernel: [    2.450527] regulator-dummy: disabling
Oct  9 18:01:53 node-5 kernel: [    2.456102]   Magic number: 4:571:38
Oct  9 18:01:53 node-5 kernel: [    2.457998] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct  9 18:01:53 node-5 kernel: [    2.457999] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  9 18:01:53 node-5 kernel: [    2.458000] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct  9 18:01:53 node-5 kernel: [    2.458001] usb 2-1.4: Manufacturer: Avocent
Oct  9 18:01:53 node-5 kernel: [    2.458001] usb 2-1.4: SerialNumber: 20111102-00000001
Oct  9 18:01:53 node-5 kernel: [    2.494899] bdi 7:3: hash matches
Oct  9 18:01:53 node-5 kernel: [    2.500464] memory memory207: hash matches
Oct  9 18:01:53 node-5 kernel: [    2.505827] memory memory74: hash matches
Oct  9 18:01:53 node-5 kernel: [    2.511198] rtc_cmos 00:02: setting system clock to 2016-10-09 18:01:16 UTC (1476036076)
Oct  9 18:01:53 node-5 kernel: [    2.523377] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct  9 18:01:53 node-5 kernel: [    2.528847] EDD information not available.
Oct  9 18:01:53 node-5 kernel: [    2.534273] PM: Hibernation image not present or could not be loaded.
Oct  9 18:01:53 node-5 kernel: [    2.535128] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct  9 18:01:53 node-5 kernel: [    2.545869] Write protecting the kernel read-only data: 12288k
Oct  9 18:01:53 node-5 kernel: [    2.551831] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct  9 18:01:53 node-5 kernel: [    2.564206] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct  9 18:01:53 node-5 kernel: [    2.596216] device-mapper: multipath: version 1.6.0 loaded
Oct  9 18:01:53 node-5 kernel: [    2.604123] systemd-udevd[215]: starting version 204
Oct  9 18:01:53 node-5 kernel: [    2.624374] md: linear personality registered for level -1
Oct  9 18:01:53 node-5 kernel: [    2.638879] md: multipath personality registered for level -4
Oct  9 18:01:53 node-5 kernel: [    2.646994] md: raid0 personality registered for level 0
Oct  9 18:01:53 node-5 kernel: [    2.655397] md: raid1 personality registered for level 1
Oct  9 18:01:53 node-5 kernel: [    2.661630] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct  9 18:01:53 node-5 kernel: [    2.667810] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct  9 18:01:53 node-5 kernel: [    2.675728] hidraw: raw HID events driver (C) Jiri Kosina
Oct  9 18:01:53 node-5 kernel: [    2.677064] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Oct  9 18:01:53 node-5 kernel: [    2.677065] 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:53 node-5 kernel: [    2.677066] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  9 18:01:53 node-5 kernel: [    2.677138] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.677178] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.677214] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.677248] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.677386] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.678601] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct  9 18:01:53 node-5 kernel: [    2.678954] megasas: FW now in Ready state
Oct  9 18:01:53 node-5 kernel: [    2.679006] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679043] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679080] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679116] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679151] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679189] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679213] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679250] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679283] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679323] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679361] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679399] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679436] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679473] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679509] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679543] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.679709] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct  9 18:01:53 node-5 kernel: [    2.688418] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Oct  9 18:01:53 node-5 kernel: [    2.688420] 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:53 node-5 kernel: [    2.688420] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct  9 18:01:53 node-5 kernel: [    2.688478] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.688513] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.688551] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.688585] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.688623] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.688660] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.688765] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.697859] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Oct  9 18:01:53 node-5 kernel: [    2.697860] 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:53 node-5 kernel: [    2.697861] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  9 18:01:53 node-5 kernel: [    2.697928] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.697962] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.698013] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.698052] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.698136] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.704762] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Oct  9 18:01:53 node-5 kernel: [    2.704764] 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:53 node-5 kernel: [    2.704764] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  9 18:01:53 node-5 kernel: [    2.704824] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.704855] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.704892] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.704930] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.705017] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  9 18:01:53 node-5 kernel: [    2.741332] raid6: sse2x1   11123 MB/s
Oct  9 18:01:53 node-5 kernel: [    2.809372] raid6: sse2x2   10683 MB/s
Oct  9 18:01:53 node-5 kernel: [    2.877454] raid6: sse2x4    9564 MB/s
Oct  9 18:01:53 node-5 kernel: [    2.945102] raid6: avx2x1   14437 MB/s
Oct  9 18:01:53 node-5 kernel: [    3.017032] raid6: avx2x2   18862 MB/s
Oct  9 18:01:53 node-5 kernel: [    3.088986] raid6: avx2x4   21403 MB/s
Oct  9 18:01:53 node-5 kernel: [    3.095005] raid6: using algorithm avx2x4 (21403 MB/s)
Oct  9 18:01:53 node-5 kernel: [    3.101023] raid6: using avx2x2 recovery algorithm
Oct  9 18:01:53 node-5 kernel: [    3.106860] Switched to clocksource tsc
Oct  9 18:01:53 node-5 kernel: [    3.113254] xor: automatically using best checksumming function:
Oct  9 18:01:53 node-5 kernel: [    3.120916] usbcore: registered new interface driver usbhid
Oct  9 18:01:53 node-5 kernel: [    3.126543] usbhid: USB HID core driver
Oct  9 18:01:53 node-5 kernel: [    3.137713] 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:53 node-5 kernel: [    3.149054] 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:53 node-5 kernel: [    3.156953]    avx       : 36232.000 MB/sec
Oct  9 18:01:53 node-5 kernel: [    3.160898] megasas:IOC Init cmd success
Oct  9 18:01:53 node-5 kernel: [    3.172198] 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:53 node-5 kernel: [    3.183643] async_tx: api initialized (async)
Oct  9 18:01:53 node-5 kernel: [    3.183669] 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:53 node-5 kernel: [    3.183725] 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:53 node-5 kernel: [    3.183761] 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:53 node-5 kernel: [    3.185330] megasas: INIT adapter done
Oct  9 18:01:53 node-5 kernel: [    3.234255] md: raid6 personality registered for level 6
Oct  9 18:01:53 node-5 kernel: [    3.240207] md: raid5 personality registered for level 5
Oct  9 18:01:53 node-5 kernel: [    3.246063] md: raid4 personality registered for level 4
Oct  9 18:01:53 node-5 kernel: [    3.254997] md: raid10 personality registered for level 10
Oct  9 18:01:53 node-5 kernel: [    3.280822] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct  9 18:01:53 node-5 kernel: [    3.281211] scsi0 : LSI SAS based MegaRAID driver
Oct  9 18:01:53 node-5 kernel: [    3.288296] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  9 18:01:53 node-5 kernel: [    3.299811] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  9 18:01:53 node-5 kernel: [    3.304081] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct  9 18:01:53 node-5 kernel: [    3.304185] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct  9 18:01:53 node-5 kernel: [    3.304426] sd 0:2:0:0: [sda] Write Protect is off
Oct  9 18:01:53 node-5 kernel: [    3.304427] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct  9 18:01:53 node-5 kernel: [    3.304498] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct  9 18:01:53 node-5 kernel: [    3.331225]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct  9 18:01:53 node-5 kernel: [    3.333468] sd 0:2:0:0: [sda] Attached SCSI disk
Oct  9 18:01:53 node-5 kernel: [    3.407548] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Oct  9 18:01:53 node-5 kernel: [    3.476345] random: lvm urandom read with 27 bits of entropy available
Oct  9 18:01:53 node-5 kernel: [    3.643245] bio: create slab <bio-1> at 1
Oct  9 18:01:53 node-5 kernel: [    4.423780] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Oct  9 18:01:53 node-5 kernel: [    5.118668] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Oct  9 18:01:53 node-5 kernel: [    5.159071] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct  9 18:01:53 node-5 kernel: [    5.356188] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct  9 18:01:53 node-5 kernel: [    5.386111] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct  9 18:01:53 node-5 kernel: [    5.432527] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct  9 18:01:53 node-5 kernel: [    5.554287] random: nonblocking pool is initialized
Oct  9 18:01:53 node-5 kernel: [    5.632471] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct  9 18:01:53 node-5 kernel: [    5.662097] XFS (dm-1): Mounting Filesystem
Oct  9 18:01:53 node-5 kernel: [    5.913712] XFS (dm-1): Ending clean mount
Oct  9 18:01:53 node-5 kernel: [    5.986929] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct  9 18:01:53 node-5 kernel: [    6.012428] XFS (dm-2): Mounting Filesystem
Oct  9 18:01:53 node-5 kernel: [    6.115930] XFS (dm-2): Ending clean mount
Oct  9 18:01:53 node-5 kernel: [    6.287978] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Oct  9 18:01:53 node-5 kernel: [    8.464994] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  9 18:01:53 node-5 kernel: [    8.479154] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  9 18:01:53 node-5 kernel: [    8.645290] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  9 18:01:53 node-5 kernel: [    8.645296] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  9 18:01:53 node-5 kernel: [    8.645300] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct  9 18:01:53 node-5 kernel: [    8.645305] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct  9 18:01:53 node-5 kernel: [    8.681363] systemd-udevd[797]: starting version 204
Oct  9 18:01:53 node-5 kernel: [    8.908060] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct  9 18:01:53 node-5 kernel: [    8.908066] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  9 18:01:53 node-5 kernel: [    8.908069] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct  9 18:01:53 node-5 kernel: [    8.908070] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  9 18:01:53 node-5 kernel: [    8.908115] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct  9 18:01:53 node-5 kernel: [    8.910592] power_meter ACPI000D:00: Found ACPI power meter.
Oct  9 18:01:53 node-5 kernel: [    8.910614] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct  9 18:01:53 node-5 kernel: [    8.929193] wmi: Mapper loaded
Oct  9 18:01:53 node-5 kernel: [    8.938977] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct  9 18:01:53 node-5 kernel: [    8.945875] IPMI System Interface driver.
Oct  9 18:01:53 node-5 kernel: [    8.945953] ipmi_si: probing via ACPI
Oct  9 18:01:53 node-5 kernel: [    8.945967] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct  9 18:01:53 node-5 kernel: [    8.945969] ipmi_si: Adding ACPI-specified kcs state machine
Oct  9 18:01:53 node-5 kernel: [    8.945985] ipmi_si: probing via SMBIOS
Oct  9 18:01:53 node-5 kernel: [    8.945986] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct  9 18:01:53 node-5 kernel: [    8.945987] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct  9 18:01:53 node-5 kernel: [    8.945989] ipmi_si: probing via SPMI
Oct  9 18:01:53 node-5 kernel: [    8.945990] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct  9 18:01:53 node-5 kernel: [    8.945991] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct  9 18:01:53 node-5 kernel: [    8.945993] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct  9 18:01:53 node-5 kernel: [    9.004433] systemd-udevd[844]: renamed network interface eth3 to enp9s0
Oct  9 18:01:53 node-5 kernel: [    9.028299] systemd-udevd[853]: renamed network interface eth1 to enp7s0
Oct  9 18:01:53 node-5 kernel: [    9.060312] systemd-udevd[836]: renamed network interface eth0 to enp6s0
Oct  9 18:01:53 node-5 kernel: [    9.084312] systemd-udevd[838]: renamed network interface eth2 to enp8s0
Oct  9 18:01:53 node-5 kernel: [    9.147493] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct  9 18:01:53 node-5 kernel: [    9.147498] ipmi_si 00:09: IPMI kcs interface initialized
Oct  9 18:01:53 node-5 kernel: [    9.392859] type=1400 audit(1476036083.385:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1081 comm="apparmor_parser"
Oct  9 18:01:53 node-5 kernel: [    9.393003] type=1400 audit(1476036083.385:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1081 comm="apparmor_parser"
Oct  9 18:01:53 node-5 kernel: [    9.393124] type=1400 audit(1476036083.385:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1081 comm="apparmor_parser"
Oct  9 18:01:53 node-5 kernel: [    9.403634] type=1400 audit(1476036083.397:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1078 comm="apparmor_parser"
Oct  9 18:01:53 node-5 kernel: [    9.403765] type=1400 audit(1476036083.397:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1078 comm="apparmor_parser"
Oct  9 18:01:53 node-5 kernel: [    9.403876] type=1400 audit(1476036083.397:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1078 comm="apparmor_parser"
Oct  9 18:01:53 node-5 kernel: [    9.410010] type=1400 audit(1476036083.401:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1089 comm="apparmor_parser"
Oct  9 18:01:53 node-5 kernel: [    9.410158] type=1400 audit(1476036083.401:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1089 comm="apparmor_parser"
Oct  9 18:01:53 node-5 kernel: [    9.410275] type=1400 audit(1476036083.401:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1089 comm="apparmor_parser"
Oct  9 18:01:53 node-5 kernel: [    9.411112] type=1400 audit(1476036083.401:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1087 comm="apparmor_parser"
Oct  9 18:01:53 node-5 kernel: [   10.128128] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  9 18:01:53 node-5 kernel: [   10.128867] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  9 18:01:53 node-5 kernel: [   10.369763] enic 0000:06:00.0 enp6s0: Link UP
Oct  9 18:01:53 node-5 kernel: [   10.370203] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct  9 18:01:53 node-5 kernel: [   10.370212] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct  9 18:01:53 node-5 kernel: [   21.423195] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct  9 18:01:54 node-5 failsafe: Failsafe of 120 seconds reached.
Oct  9 18:01:54 node-5 kernel: [   40.946416] init: failsafe main process (8454) killed by TERM signal
Oct  9 18:01:54 node-5 dbus[8517]: [system] AppArmor D-Bus mediation is enabled
Oct  9 18:01:54 node-5 kernel: [   41.199847] audit_printk_skb: 30 callbacks suppressed
Oct  9 18:01:54 node-5 kernel: [   41.199848] type=1400 audit(1476036114.551:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8576 comm="apparmor_parser"
Oct  9 18:01:54 node-5 kernel: [   41.203448] type=1400 audit(1476036114.555:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8575 comm="apparmor_parser"
Oct  9 18:01:54 node-5 kernel: [   41.203454] type=1400 audit(1476036114.555:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8575 comm="apparmor_parser"
Oct  9 18:01:54 node-5 kernel: [   41.203457] type=1400 audit(1476036114.555:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8575 comm="apparmor_parser"
Oct  9 18:01:54 node-5 kernel: [   41.203679] type=1400 audit(1476036114.555:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8575 comm="apparmor_parser"
Oct  9 18:01:54 node-5 kernel: [   41.203682] type=1400 audit(1476036114.555:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8575 comm="apparmor_parser"
Oct  9 18:01:54 node-5 kernel: [   41.203796] type=1400 audit(1476036114.555:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8575 comm="apparmor_parser"
Oct  9 18:01:54 node-5 kernel: [   41.298364] type=1400 audit(1476036114.651:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8578 comm="apparmor_parser"
Oct  9 18:01:54 node-5 cron[8611]: (CRON) INFO (pidfile fd = 3)
Oct  9 18:01:54 node-5 anacron[8647]: Anacron 2.3 started on 2016-10-09
Oct  9 18:01:54 node-5 cron[8650]: (CRON) STARTUP (fork ok)
Oct  9 18:01:54 node-5 cron[8650]: (CRON) INFO (Running @reboot jobs)
Oct  9 18:01:54 node-5 multipathd: path checkers start up
Oct  9 18:01:54 node-5 anacron[8647]: Will run job `cron.daily' in 5 min.
Oct  9 18:01:54 node-5 anacron[8647]: Will run job `cron.weekly' in 10 min.
Oct  9 18:01:54 node-5 anacron[8647]: Will run job `cron.monthly' in 15 min.
Oct  9 18:01:54 node-5 anacron[8647]: Jobs will be executed sequentially
Oct  9 18:01:55 node-5 postfix/master[8791]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct  9 18:01:58 node-5 puppet-agent[8976]: Reopening log files
Oct  9 18:02:00 node-5 puppet-agent[8976]: Could not request certificate: Connection refused - connect(2)
Oct  9 18:02:02 node-5 CRON[9007]: (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-5 puppet-user[9066]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct  9 18:02:10 node-5 puppet-user[9066]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Oct  9 18:02:11 node-5 puppet-user[9066]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct  9 18:02:11 node-5 puppet-user[9066]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct  9 18:02:11 node-5 puppet-user[9066]: Finished catalog run in 0.46 seconds
Oct  9 18:02:12 node-5 multipathd: uevent trigger error
Oct  9 18:02:12 node-5 puppet-user[9615]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  9 18:02:12 node-5 puppet-user[9615]: Compiled catalog for node-5.domain.tld in environment production in 0.08 seconds
Oct  9 18:02:13 node-5 puppet-user[9615]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct  9 18:02:13 node-5 puppet-user[9615]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct  9 18:02:13 node-5 puppet-user[9615]: (/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:13 node-5 puppet-user[9615]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct  9 18:02:13 node-5 puppet-user[9615]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct  9 18:02:13 node-5 puppet-user[9615]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct  9 18:02:13 node-5 puppet-user[9615]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct  9 18:02:13 node-5 puppet-user[9615]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct  9 18:02:13 node-5 puppet-user[9615]: Finished catalog run in 0.06 seconds
Oct  9 18:02:14 node-5 puppet-user[10078]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct  9 18:02:14 node-5 puppet-user[10078]: Compiled catalog for node-5.domain.tld in environment production in 0.07 seconds
Oct  9 18:02:14 node-5 puppet-user[10078]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct  9 18:02:14 node-5 puppet-user[10078]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct  9 18:02:14 node-5 puppet-user[10078]: Finished catalog run in 0.04 seconds
Oct  9 18:02:16 node-5 puppet-user[10542]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct  9 18:02:16 node-5 puppet-user[10542]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Oct  9 18:02:16 node-5 puppet-user[10542]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct  9 18:02:16 node-5 puppet-user[10542]: Finished catalog run in 0.03 seconds
Oct  9 18:02:17 node-5 puppet-user[10996]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct  9 18:02:18 node-5 puppet-user[10996]: Compiled catalog for node-5.domain.tld in environment production in 0.21 seconds
Oct  9 18:02:18 node-5 puppet-user[10996]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct  9 18:02:18 node-5 puppet-user[10996]: (/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-5 puppet-user[10996]: Finished catalog run in 0.48 seconds
Oct  9 18:02:19 node-5 puppet-user[11485]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct  9 18:02:20 node-5 puppet-user[11485]: Compiled catalog for node-5.domain.tld in environment production in 0.20 seconds
Oct  9 18:02:20 node-5 puppet-user[11485]: (/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:20 node-5 puppet-user[11485]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct  9 18:02:20 node-5 puppet-user[11485]: (/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:20 node-5 puppet-user[11485]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct  9 18:02:20 node-5 puppet-user[11485]: Finished catalog run in 0.28 seconds
Oct  9 18:02:21 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  9 18:02:21 node-5 nailgun-agent: D, [2016-10-09T18:02:02.321916 #9010] DEBUG -- : Sleep for 19 seconds before sending request
Oct  9 18:02:21 node-5 nailgun-agent: I, [2016-10-09T18:02:21.335659 #9010]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  9 18:02:21 node-5 nailgun-agent: D, [2016-10-09T18:02:21.745078 #9010] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Oct  9 18:02:22 node-5 puppet-user[11976]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct  9 18:02:22 node-5 puppet-user[11976]: Compiled catalog for node-5.domain.tld in environment production in 0.17 seconds
Oct  9 18:02:22 node-5 puppet-user[11976]: (/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:22 node-5 kernel: [   68.668468] nr_pdflush_threads exported in /proc is scheduled for removal
Oct  9 18:02:22 node-5 kernel: [   68.668522] 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:22 node-5 puppet-user[11976]: (/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:22 node-5 puppet-user[11976]: Finished catalog run in 0.08 seconds
Oct  9 18:02:24 node-5 puppet-user[12750]: (Scope(Class[main])) MODULAR: sync_time
Oct  9 18:02:24 node-5 puppet-user[12750]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Oct  9 18:02:24 node-5 ntpdate[13173]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct  9 18:02:30 node-5 ntpdate[13173]: adjust time server 10.20.0.2 offset 0.000663 sec
Oct  9 18:02:30 node-5 puppet-user[12750]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct  9 18:02:30 node-5 puppet-user[12750]: Finished catalog run in 6.19 seconds
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.598496 #9010] DEBUG -- : Trying to find block devices
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.598577 #9010] DEBUG -- : Found block device: sda
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.598642 #9010] 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-5 nailgun-agent: D, [2016-10-09T18:02:33.598665 #9010] DEBUG -- : Trying to get list of physical devices
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.598819 #9010] DEBUG -- : Getting udev properties for device: sda
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.600613 #9010] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc7880
Oct  9 18:02:33 node-5 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84658", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.600637 #9010] DEBUG -- : Trying to find out if device sda is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.600675 #9010] DEBUG -- : Device sda removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.600689 #9010] DEBUG -- : Device sda seems to be appropriate
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.601144 #9010] DEBUG -- : Getting udev properties for device: dm-0
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.602644 #9010] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-eW8mgWh5PwFUSb0V9jpSj7TgXFeXEPPemHGM8htNT3TGePFWq7LoyYtRO4WrFCjk /dev/disk/by-uuid/03c516ee-d83e-477f-b915-e285caa0f46a /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "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-eW8mgWh5PwFUSb0V9jpSj7TgXFeXEPPemHGM8htNT3TGePFWq7LoyYtRO4WrFCjk", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"03c516ee-d83e-477f-b915-e285caa0f46a", "ID_FS_UUID_ENC"=>"03c516ee-d83e-477f-b915-e285caa0f46a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"94
Oct  9 18:02:33 node-5 nailgun-agent: 652", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.602692 #9010] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.602732 #9010] DEBUG -- : Device dm-0 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.602745 #9010] DEBUG -- : Device dm-0 seems to be appropriate
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.602759 #9010] DEBUG -- : Getting udev properties for device: dm-1
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.604289 #9010] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-CERxUUl0hFHCqP2GGDEsLFfH9zqRzBGfViOopS1vZ2c7h11Ye3GCc4DzYzyvzIJM /dev/disk/by-uuid/37603162-3e8a-495e-99a2-65f1f01abb0e /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "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-CERxUUl0hFHCqP2GGDEsLFfH9zqRzBGfViOopS1vZ2c7h11Ye3GCc4DzYzyvzIJM", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"37603162-3e8a-495e-99a2-65f1f01abb0e", "ID_FS_UUID_ENC"=>"37603162-3e8a-495e-99a2-65f1f01abb0e", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"25140", "nomdmonddf"=>"1", "nomd
Oct  9 18:02:33 node-5 nailgun-agent: monisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.604322 #9010] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.604349 #9010] DEBUG -- : Device dm-1 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.604362 #9010] DEBUG -- : Device dm-1 seems to be appropriate
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.604374 #9010] DEBUG -- : Getting udev properties for device: dm-2
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.605843 #9010] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-Adxc2mZ19nZivAuCd55Vy6706YBzI3pUgtDXJLsqS2bmup7hNLsxFd5aIEWb3cBq /dev/disk/by-uuid/8df8316e-4496-4c70-bb96-9a7c855db9c3 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "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-Adxc2mZ19nZivAuCd55Vy6706YBzI3pUgtDXJLsqS2bmup7hNLsxFd5aIEWb3cBq", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8df8316e-4496-4c70-bb96-9a7c855db9c3", "ID_FS_UUID_ENC"=>"8df8316e-4496-4c70-bb96-9a7c855db9c3", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"36
Oct  9 18:02:33 node-5 nailgun-agent: 737", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.605867 #9010] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.605896 #9010] DEBUG -- : Device dm-2 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.605935 #9010] DEBUG -- : Device dm-2 seems to be appropriate
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.605947 #9010] DEBUG -- : Getting udev properties for device: dm-3
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.607445 #9010] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-kCphwOQ4gh1BWQfyPI3BltwDI12VBf6uEk2UXoIB2xCOnv2BX7i6PuXmcLpxVVxa /dev/disk/by-uuid/b2d320ca-b48b-4c56-a418-e7710bd4a9b4 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "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-kCphwOQ4gh1BWQfyPI3BltwDI12VBf6uEk2UXoIB2xCOnv2BX7i6PuXmcLpxVVxa", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b2d320ca-b48b-4c56-a418-e7710bd4a9b4", "ID_FS_UUID_ENC"=>"b2d320ca-b48b-4c56-a418-e7710bd4a9b4", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37115", "nomdmond
Oct  9 18:02:33 node-5 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.607467 #9010] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.607506 #9010] DEBUG -- : Device dm-3 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.607519 #9010] DEBUG -- : Device dm-3 seems to be appropriate
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.607551 #9010] DEBUG -- : Getting udev properties for device: dm-4
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.609039 #9010] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-h7EmiA3h3SVPQWv53FEI1s2JppQNsehBhZ4ddLdjGSsXMzbyQwuI0oyB7OZcKxyx /dev/disk/by-uuid/9e77a487-d74d-473a-b77f-dcda6b4937b8 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "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-h7EmiA3h3SVPQWv53FEI1s2JppQNsehBhZ4ddLdjGSsXMzbyQwuI0oyB7OZcKxyx", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9e77a487-d74d-473a-b77f-dcda6b4937b8", "ID_FS_UUID_ENC"=>"9e77a487-d74d-473a-b77f-dcda6b4937b8", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"35551", "nomdmonddf"=>"1", 
Oct  9 18:02:33 node-5 nailgun-agent: "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.609061 #9010] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.609091 #9010] DEBUG -- : Device dm-4 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.609115 #9010] DEBUG -- : Device dm-4 seems to be appropriate
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.609129 #9010] DEBUG -- : Getting udev properties for device: dm-5
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.610692 #9010] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-xQug0nlOrWTxVNpacUydUZnAD865X93y32SumJucTfZ7VC1dZ0bGLPD8xhcThjUM /dev/disk/by-uuid/38d9f080-1c97-4a0f-b180-1e9822b020eb /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "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-xQug0nlOrWTxVNpacUydUZnAD865X93y32SumJucTfZ7VC1dZ0bGLPD8xhcThjUM", "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"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39783", "nomdmonddf"=>"1", "nomd
Oct  9 18:02:33 node-5 nailgun-agent: monisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.610715 #9010] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.610773 #9010] DEBUG -- : Device dm-5 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.610806 #9010] DEBUG -- : Device dm-5 seems to be appropriate
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.610833 #9010] DEBUG -- : Getting udev properties for device: dm-6
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.612348 #9010] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-xQug0nlOrWTxVNpacUydUZnAD865X93yTfpsRtgcgH2GJ0I2J1U1Dz6oFmHdkxjm /dev/disk/by-uuid/48735431-db3a-4db5-9f30-9962356adf79 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "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-xQug0nlOrWTxVNpacUydUZnAD865X93yTfpsRtgcgH2GJ0I2J1U1Dz6oFmHdkxjm", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"48735431-db3a-4db5-9f30-9962356adf79", "ID_FS_UUID_ENC"=>"48735431-db3a-4db5-9f30-9962356adf79", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"40195", "nomdmonddf"=>"1", "nomdmonisw"
Oct  9 18:02:33 node-5 nailgun-agent: =>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.612369 #9010] DEBUG -- : Trying to find out if device dm-6 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.612408 #9010] DEBUG -- : Device dm-6 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.612432 #9010] DEBUG -- : Device dm-6 seems to be appropriate
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.612445 #9010] DEBUG -- : Getting udev properties for device: ram0
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.613834 #9010] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77806", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.613856 #9010] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.613888 #9010] DEBUG -- : Device ram0 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.613921 #9010] DEBUG -- : Getting udev properties for device: ram1
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.615263 #9010] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77869", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.615299 #9010] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.615334 #9010] DEBUG -- : Device ram1 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.615351 #9010] DEBUG -- : Getting udev properties for device: ram2
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.616706 #9010] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78446", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.616726 #9010] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.616753 #9010] DEBUG -- : Device ram2 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.616777 #9010] DEBUG -- : Getting udev properties for device: ram3
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.618158 #9010] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78583", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.618195 #9010] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.618233 #9010] DEBUG -- : Device ram3 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.618259 #9010] DEBUG -- : Getting udev properties for device: ram4
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.619636 #9010] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78740", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.619655 #9010] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.619683 #9010] DEBUG -- : Device ram4 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.619707 #9010] DEBUG -- : Getting udev properties for device: ram5
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.621092 #9010] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78876", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.621115 #9010] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.621152 #9010] DEBUG -- : Device ram5 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.621176 #9010] DEBUG -- : Getting udev properties for device: ram6
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.622523 #9010] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78959", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.622544 #9010] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.622588 #9010] DEBUG -- : Device ram6 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.622606 #9010] DEBUG -- : Getting udev properties for device: ram7
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.623971 #9010] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79058", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.623991 #9010] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.624031 #9010] DEBUG -- : Device ram7 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.624048 #9010] DEBUG -- : Getting udev properties for device: ram8
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.625422 #9010] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79227", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.625449 #9010] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.625487 #9010] DEBUG -- : Device ram8 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.625512 #9010] DEBUG -- : Getting udev properties for device: ram9
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.626871 #9010] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79319", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.626891 #9010] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.626941 #9010] DEBUG -- : Device ram9 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.626967 #9010] DEBUG -- : Getting udev properties for device: loop0
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.628330 #9010] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77593", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.628361 #9010] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.628392 #9010] DEBUG -- : Device loop0 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.628429 #9010] DEBUG -- : Getting udev properties for device: loop1
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.629799 #9010] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77601", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.629821 #9010] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.629851 #9010] DEBUG -- : Device loop1 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.629875 #9010] DEBUG -- : Getting udev properties for device: loop2
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.631260 #9010] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77609", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.631284 #9010] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.631326 #9010] DEBUG -- : Device loop2 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.631349 #9010] DEBUG -- : Getting udev properties for device: loop3
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.635729 #9010] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77621", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.635755 #9010] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.635791 #9010] DEBUG -- : Device loop3 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.635809 #9010] DEBUG -- : Getting udev properties for device: loop4
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.637326 #9010] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77730", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.637346 #9010] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.637379 #9010] DEBUG -- : Device loop4 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.637397 #9010] DEBUG -- : Getting udev properties for device: loop5
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.638777 #9010] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77753", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.638797 #9010] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.638831 #9010] DEBUG -- : Device loop5 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.638849 #9010] DEBUG -- : Getting udev properties for device: loop6
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.640226 #9010] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77760", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.640246 #9010] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.640280 #9010] DEBUG -- : Device loop6 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.640298 #9010] DEBUG -- : Getting udev properties for device: loop7
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.641642 #9010] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77766", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.641665 #9010] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.641736 #9010] DEBUG -- : Device loop7 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.641754 #9010] DEBUG -- : Getting udev properties for device: ram10
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.643103 #9010] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77936", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.643123 #9010] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.643150 #9010] DEBUG -- : Device ram10 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.643191 #9010] DEBUG -- : Getting udev properties for device: ram11
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.644525 #9010] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"77981", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.644544 #9010] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.644571 #9010] DEBUG -- : Device ram11 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.644589 #9010] DEBUG -- : Getting udev properties for device: ram12
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.645933 #9010] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78033", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.645954 #9010] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.645981 #9010] DEBUG -- : Device ram12 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.645999 #9010] DEBUG -- : Getting udev properties for device: ram13
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.647352 #9010] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78121", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.647371 #9010] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.647401 #9010] DEBUG -- : Device ram13 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.647418 #9010] DEBUG -- : Getting udev properties for device: ram14
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.648772 #9010] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78258", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.648794 #9010] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.648826 #9010] DEBUG -- : Device ram14 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.648844 #9010] DEBUG -- : Getting udev properties for device: ram15
Oct  9 18:02:33 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650227 #9010] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78354", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650248 #9010] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650279 #9010] DEBUG -- : Device ram15 removable parameter: "0"
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650310 #9010] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650324 #9010] DEBUG -- : Block device seems to be physical data storage: sda
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650357 #9010] DEBUG -- : Found block device: dm-0
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650370 #9010] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650393 #9010] DEBUG -- : Found block device: dm-1
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650405 #9010] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650447 #9010] DEBUG -- : Found block device: dm-2
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650458 #9010] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650466 #9010] DEBUG -- : Found block device: dm-3
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650476 #9010] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650485 #9010] DEBUG -- : Found block device: dm-4
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650495 #9010] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650504 #9010] DEBUG -- : Found block device: dm-5
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650513 #9010] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650522 #9010] DEBUG -- : Found block device: dm-6
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650533 #9010] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650542 #9010] DEBUG -- : Found block device: ram0
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650594 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650603 #9010] DEBUG -- : Found block device: ram1
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650613 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650621 #9010] DEBUG -- : Found block device: ram2
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650631 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650639 #9010] DEBUG -- : Found block device: ram3
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650649 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650657 #9010] DEBUG -- : Found block device: ram4
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650703 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650713 #9010] DEBUG -- : Found block device: ram5
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650723 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650731 #9010] DEBUG -- : Found block device: ram6
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650741 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650749 #9010] DEBUG -- : Found block device: ram7
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650758 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650766 #9010] DEBUG -- : Found block device: ram8
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650776 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650784 #9010] DEBUG -- : Found block device: ram9
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650835 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650844 #9010] DEBUG -- : Found block device: loop0
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650853 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650862 #9010] DEBUG -- : Found block device: loop1
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650872 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650880 #9010] DEBUG -- : Found block device: loop2
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650889 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650897 #9010] DEBUG -- : Found block device: loop3
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650948 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650957 #9010] DEBUG -- : Found block device: loop4
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650966 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650975 #9010] DEBUG -- : Found block device: loop5
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650984 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.650992 #9010] DEBUG -- : Found block device: loop6
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651001 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651010 #9010] DEBUG -- : Found block device: loop7
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651019 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651059 #9010] DEBUG -- : Found block device: ram10
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651069 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651078 #9010] DEBUG -- : Found block device: ram11
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651087 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651095 #9010] DEBUG -- : Found block device: ram12
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651104 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651112 #9010] DEBUG -- : Found block device: ram13
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651123 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651131 #9010] DEBUG -- : Found block device: ram14
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651178 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651187 #9010] DEBUG -- : Found block device: ram15
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651197 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.651225 #9010] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.748409 #9010] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Oct  9 18:02:33 node-5 nailgun-agent: D, [2016-10-09T18:02:33.748462 #9010] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct  9 18:02:35 node-5 kernel: [   81.358999] init: plymouth-upstart-bridge main process ended, respawning
Oct  9 18:02:35 node-5 puppet-agent[8976]: Could not run: SIGTERM
Oct  9 18:02:35 node-5 kernel: [   81.633180] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct  9 18:02:35 node-5 ec2: 
Oct  9 18:02:35 node-5 ec2: #############################################################
Oct  9 18:02:35 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct  9 18:02:35 node-5 ec2: 1024 b0:26:ac:38:dc:55:a9:04:de:9a:eb:93:63:c0:53:d8  root@node-5.domain.tld (DSA)
Oct  9 18:02:35 node-5 ec2: 256 61:87:6c:c3:50:98:0b:e1:f5:b2:5e:7a:a9:13:ec:8a  root@node-5.domain.tld (ECDSA)
Oct  9 18:02:35 node-5 ec2: 256 23:25:7c:8e:d8:36:70:d9:7f:85:4b:64:10:90:2f:87  root@node-5.domain.tld (ED25519)
Oct  9 18:02:35 node-5 ec2: 2048 cc:f9:60:9f:fa:b7:84:2a:d3:a4:b5:26:d8:00:f9:27  root@node-5.domain.tld (RSA)
Oct  9 18:02:35 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct  9 18:02:35 node-5 ec2: #############################################################
Oct  9 18:02:35 node-5 puppet-user[13542]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  9 18:02:35 node-5 puppet-user[13542]: Compiled catalog for node-5.domain.tld in environment production in 0.27 seconds
Oct  9 18:02:35 node-5 puppet-user[13542]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct  9 18:02:35 node-5 puppet-user[13542]: (/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-5 puppet-user[13542]: Finished catalog run in 0.07 seconds
Oct  9 18:02:37 node-5 puppet-user[14172]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct  9 18:02:37 node-5 puppet-user[14172]: Compiled catalog for node-5.domain.tld in environment production in 0.51 seconds
Oct  9 18:02:37 node-5 puppet-user[14172]: (/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-5 puppet-user[14172]: (/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-5 puppet-user[14172]: (/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-5 puppet-user[14172]: (/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-5 puppet-user[14172]: (/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-5 puppet-user[14172]: (/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-5 puppet-user[14172]: (/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-5 puppet-user[14172]: (/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-5 puppet-user[14172]: (/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-5 puppet-user[14172]: (/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:38 node-5 puppet-user[14172]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct  9 18:02:38 node-5 puppet-user[14172]: Finished catalog run in 0.82 seconds
Oct  9 18:02:40 node-5 puppet-user[14679]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct  9 18:02:40 node-5 puppet-user[14679]: Compiled catalog for node-5.domain.tld in environment production in 0.10 seconds
Oct  9 18:02:43 node-5 puppet-user[14679]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct  9 18:02:46 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.014791 #9010] DEBUG -- : Trying to find block devices
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.014901 #9010] DEBUG -- : Found block device: sda
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.014964 #9010] 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-5 nailgun-agent: D, [2016-10-09T18:02:46.014987 #9010] DEBUG -- : Block device seems to be physical data storage: sda
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015010 #9010] DEBUG -- : Found block device: dm-0
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015023 #9010] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015035 #9010] DEBUG -- : Found block device: dm-1
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015047 #9010] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015057 #9010] DEBUG -- : Found block device: dm-2
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015069 #9010] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015104 #9010] DEBUG -- : Found block device: dm-3
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015116 #9010] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015126 #9010] DEBUG -- : Found block device: dm-4
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015137 #9010] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015145 #9010] DEBUG -- : Found block device: dm-5
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015155 #9010] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015165 #9010] DEBUG -- : Found block device: dm-6
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015174 #9010] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015184 #9010] DEBUG -- : Found block device: ram0
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015218 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015229 #9010] DEBUG -- : Found block device: ram1
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015239 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015248 #9010] DEBUG -- : Found block device: ram2
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015258 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015267 #9010] DEBUG -- : Found block device: ram3
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015277 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015314 #9010] DEBUG -- : Found block device: ram4
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015324 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015333 #9010] DEBUG -- : Found block device: ram5
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015344 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015365 #9010] DEBUG -- : Found block device: ram6
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015387 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015395 #9010] DEBUG -- : Found block device: ram7
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015450 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015461 #9010] DEBUG -- : Found block device: ram8
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015472 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015481 #9010] DEBUG -- : Found block device: ram9
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015492 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015501 #9010] DEBUG -- : Found block device: loop0
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015513 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015522 #9010] DEBUG -- : Found block device: loop1
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015532 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015541 #9010] DEBUG -- : Found block device: loop2
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015578 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015589 #9010] DEBUG -- : Found block device: loop3
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015600 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015608 #9010] DEBUG -- : Found block device: loop4
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015618 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015638 #9010] DEBUG -- : Found block device: loop5
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015647 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015656 #9010] DEBUG -- : Found block device: loop6
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015665 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015673 #9010] DEBUG -- : Found block device: loop7
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015712 #9010] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015721 #9010] DEBUG -- : Found block device: ram10
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015731 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015739 #9010] DEBUG -- : Found block device: ram11
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015748 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015756 #9010] DEBUG -- : Found block device: ram12
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015766 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015774 #9010] DEBUG -- : Found block device: ram13
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015783 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015818 #9010] DEBUG -- : Found block device: ram14
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015828 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015836 #9010] DEBUG -- : Found block device: ram15
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015846 #9010] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.015875 #9010] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Oct  9 18:02:46 node-5 nailgun-agent: D, [2016-10-09T18:02:46.191181 #9010] DEBUG -- : Response: status: 200 body: {"id": 5}
Oct  9 18:02:46 node-5 nailgun-agent: I, [2016-10-09T18:02:46.191349 #9010]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Oct  9 18:03:01 node-5 CRON[16446]: (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:14 node-5 puppet-user[14679]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct  9 18:03:14 node-5 puppet-user[14679]: Finished catalog run in 34.18 seconds
Oct  9 18:03:15 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  9 18:03:15 node-5 nailgun-agent: I, [2016-10-09T18:03:15.368286 #16449]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  9 18:03:16 node-5 puppet-user[17292]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct  9 18:03:16 node-5 puppet-user[17292]: Compiled catalog for node-5.domain.tld in environment production in 0.60 seconds
Oct  9 18:03:17 node-5 puppet-user[17292]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct  9 18:03:17 node-5 puppet-user[17292]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct  9 18:03:17 node-5 puppet-user[17292]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct  9 18:03:17 node-5 puppet-user[17292]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct  9 18:03:17 node-5 puppet-user[17292]: Finished catalog run in 0.08 seconds
Oct  9 18:03:18 node-5 puppet-user[17891]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct  9 18:03:19 node-5 puppet-user[17891]: Compiled catalog for node-5.domain.tld in environment production in 0.84 seconds
Oct  9 18:03:20 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct  9 18:03:20 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct  9 18:03:20 node-5 crontab[18322]: (root) LIST (root)
Oct  9 18:03:20 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct  9 18:03:20 node-5 crontab[18323]: (root) REPLACE (root)
Oct  9 18:03:21 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct  9 18:03:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/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:22 node-5 puppet-user[17891]: (/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:23 node-5 puppet-user[17891]: (/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:23 node-5 puppet-user[17891]: (/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:23 node-5 puppet-user[17891]: (/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:23 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct  9 18:03:23 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct  9 18:03:23 node-5 puppet-user[17891]: (/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:23 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct  9 18:03:23 node-5 puppet-user[17891]: (/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:23 node-5 puppet-user[17891]: (/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:23 node-5 puppet-user[17891]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct  9 18:03:23 node-5 puppet-user[17891]: (/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:23 node-5 puppet-user[17891]: (/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:23 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8427" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  9 18:03:23 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct  9 18:03:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:03:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:03:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:03:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:03:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:03:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:03:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:03:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:03:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:03:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:03:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:04:34 node-5 ntpdate[28937]: no servers can be used, exiting
<27>Oct  9 18:05:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:29 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:29 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:29 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:29 node-5 multipathd: uevent trigger error
<27>Oct  9 18:05:29 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:31 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:31 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:31 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:31 node-5 multipathd: uevent trigger error
<27>Oct  9 18:06:31 node-5 multipathd: uevent trigger error
<43>Oct  9 18:06:33 node-5 apache2_error [Sun Oct 09 18:06:25.003036 2016] [mpm_event:notice] [pid 9157:tid 140432698730368] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  9 18:06:33 node-5 apache2_error [Sun Oct 09 18:06:25.003126 2016] [core:notice] [pid 9157:tid 140432698730368] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  9 18:06:33 node-5 apache2_error [Sun Oct 09 18:06:27.113449 2016] [mpm_event:notice] [pid 9157:tid 140432698730368] AH00491: caught SIGTERM, shutting down
<43>Oct  9 18:06:33 node-5 apache2_error [Sun Oct 09 18:06:28.188691 2016] [mpm_worker:notice] [pid 9471:tid 139930820851584] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  9 18:06:33 node-5 apache2_error [Sun Oct 09 18:06:28.188741 2016] [core:notice] [pid 9471:tid 139930820851584] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:07:05 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Oct  9 18:07:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:10 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:10 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:10 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:28 node-5 multipathd: uevent trigger error
<129>Oct  9 18:07:31 node-5 haproxy[19999]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:07:33 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:33 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:33 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:33 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:33 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:36 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:36 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:36 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:36 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:36 node-5 multipathd: uevent trigger error
<129>Oct  9 18:07:39 node-5 haproxy[22327]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:07:40 node-5 haproxy[22331]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:07:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:42 node-5 multipathd: uevent trigger error
<129>Oct  9 18:07:44 node-5 haproxy[23499]: Server neutron/node-5 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:45 node-5 haproxy[23503]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:07:46 node-5 haproxy[23503]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:07:47 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:47 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:47 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:47 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:47 node-5 multipathd: uevent trigger error
<129>Oct  9 18:07:49 node-5 haproxy[24643]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:07:50 node-5 haproxy[24650]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:07:50 node-5 haproxy[24650]: Server neutron/node-5 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:51 node-5 haproxy[24650]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:07:51 node-5 haproxy[24650]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:07:52 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:52 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:52 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:52 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:52 node-5 multipathd: uevent trigger error
<129>Oct  9 18:07:55 node-5 haproxy[25778]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:07:55 node-5 haproxy[25778]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:07:55 node-5 haproxy[25778]: Server neutron/node-5 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:56 node-5 haproxy[25778]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:07:56 node-5 haproxy[25778]: Server object-storage/node-5 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:56 node-5 haproxy[25778]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:07:57 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:57 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:57 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:57 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:57 node-5 multipathd: uevent trigger error
<27>Oct  9 18:07:57 node-5 multipathd: uevent trigger error
<129>Oct  9 18:07:58 node-5 haproxy[25778]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:07:58 node-5 haproxy[25778]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:07:58 node-5 haproxy[25778]: proxy aodh has no server available!
<129>Oct  9 18:08:00 node-5 haproxy[26918]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:00 node-5 haproxy[26918]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:00 node-5 haproxy[26918]: Server neutron/node-5 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:01 node-5 haproxy[26922]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:01 node-5 haproxy[26922]: Server object-storage/node-5 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:01 node-5 haproxy[26922]: Server aodh/node-5 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:01 node-5 haproxy[26922]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:08:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:03 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:03 node-5 haproxy[26922]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:03 node-5 haproxy[26922]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:03 node-5 haproxy[26922]: proxy aodh has no server available!
<129>Oct  9 18:08:03 node-5 haproxy[26922]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:03 node-5 haproxy[26922]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:03 node-5 haproxy[26922]: proxy ceilometer has no server available!
<129>Oct  9 18:08:05 node-5 haproxy[28040]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-5 haproxy[28040]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:06 node-5 haproxy[28044]: Server neutron/node-5 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:06 node-5 haproxy[28044]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:06 node-5 haproxy[28044]: Server object-storage/node-5 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:06 node-5 haproxy[28044]: Server aodh/node-5 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:07 node-5 haproxy[28044]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:08:08 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:08 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:08 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:08 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:08 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:08 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:08 node-5 haproxy[28044]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:08 node-5 haproxy[28044]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:08 node-5 haproxy[28044]: proxy aodh has no server available!
<129>Oct  9 18:08:09 node-5 haproxy[28044]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:09 node-5 haproxy[28044]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:09 node-5 haproxy[28044]: proxy ceilometer has no server available!
<129>Oct  9 18:08:10 node-5 haproxy[29161]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-5 haproxy[29165]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", 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-5 haproxy[29165]: Server neutron/node-5 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-5 haproxy[29165]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:11 node-5 haproxy[29165]: Server object-storage/node-5 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:12 node-5 haproxy[29165]: Server aodh/node-5 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:12 node-5 haproxy[29165]: Server ceilometer/node-5 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:12 node-5 haproxy[29165]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:12 node-5 haproxy[29165]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:08:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:13 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:13 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:13 node-5 haproxy[29165]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:13 node-5 haproxy[29165]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:13 node-5 haproxy[29165]: proxy aodh has no server available!
<129>Oct  9 18:08:14 node-5 haproxy[29165]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:14 node-5 haproxy[29165]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:14 node-5 haproxy[29165]: proxy ceilometer has no server available!
<129>Oct  9 18:08:16 node-5 haproxy[30330]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:16 node-5 haproxy[30330]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:16 node-5 haproxy[30330]: Server glance-api/node-5 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:17 node-5 haproxy[30334]: Server glance-glare/node-5 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:17 node-5 haproxy[30334]: Server neutron/node-5 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:17 node-5 haproxy[30334]: Server glance-registry/node-5 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:17 node-5 haproxy[30334]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:17 node-5 haproxy[30334]: Server object-storage/node-5 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:17 node-5 haproxy[30334]: Server aodh/node-5 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:18 node-5 haproxy[30334]: Server ceilometer/node-5 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:18 node-5 haproxy[30334]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:18 node-5 haproxy[30334]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:19 node-5 haproxy[30334]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:08:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:19 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:19 node-5 haproxy[30334]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:19 node-5 haproxy[30334]: proxy glance-registry has no server available!
<27>Oct  9 18:08:19 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:19 node-5 haproxy[30334]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:19 node-5 haproxy[30334]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:19 node-5 haproxy[30334]: proxy aodh has no server available!
<129>Oct  9 18:08:20 node-5 haproxy[30334]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:20 node-5 haproxy[30334]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:20 node-5 haproxy[30334]: proxy ceilometer has no server available!
<129>Oct  9 18:08:22 node-5 haproxy[31539]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:22 node-5 haproxy[31539]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:22 node-5 haproxy[31539]: Server nova-api/node-5 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:22 node-5 haproxy[31539]: Server nova-metadata-api/node-5 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:22 node-5 haproxy[31539]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:08:22 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Oct  9 18:08:23 node-5 haproxy[31543]: Server glance-glare/node-5 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:23 node-5 haproxy[31543]: Server neutron/node-5 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:23 node-5 haproxy[31543]: Server glance-registry/node-5 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:23 node-5 haproxy[31543]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:23 node-5 haproxy[31543]: Server object-storage/node-5 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:23 node-5 haproxy[31543]: Server aodh/node-5 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:23 node-5 haproxy[31543]: Server ceilometer/node-5 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:24 node-5 haproxy[31543]: Server nova-novncproxy/node-5 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:24 node-5 haproxy[31543]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:24 node-5 haproxy[31543]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:08:25 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:25 node-5 haproxy[31543]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:08:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:25 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:25 node-5 haproxy[31543]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:25 node-5 haproxy[31543]: proxy glance-registry has no server available!
<27>Oct  9 18:08:25 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:25 node-5 haproxy[31543]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:25 node-5 haproxy[31543]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:25 node-5 haproxy[31543]: proxy aodh has no server available!
<129>Oct  9 18:08:25 node-5 haproxy[31543]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:25 node-5 haproxy[31543]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:25 node-5 haproxy[31543]: proxy ceilometer has no server available!
<129>Oct  9 18:08:25 node-5 haproxy[31543]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:25 node-5 haproxy[31543]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:25 node-5 haproxy[31543]: proxy nova-novncproxy has no server available!
<129>Oct  9 18:08:27 node-5 haproxy[420]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:27 node-5 haproxy[420]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:27 node-5 haproxy[420]: Server nova-api/node-5 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:28 node-5 haproxy[428]: Server nova-metadata-api/node-5 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:28 node-5 haproxy[428]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:28 node-5 haproxy[428]: Server glance-api/node-5 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:28 node-5 haproxy[428]: Server glance-glare/node-5 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:28 node-5 haproxy[428]: Server neutron/node-5 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:28 node-5 haproxy[428]: Server glance-registry/node-5 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:28 node-5 haproxy[428]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:29 node-5 haproxy[428]: Server object-storage/node-5 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:29 node-5 haproxy[428]: Server aodh/node-5 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:29 node-5 haproxy[428]: Server ceilometer/node-5 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:29 node-5 haproxy[428]: Server nova-novncproxy/node-5 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:29 node-5 haproxy[428]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:29 node-5 haproxy[428]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:08:30 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:30 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:30 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:30 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:30 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:30 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:30 node-5 haproxy[428]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:30 node-5 haproxy[428]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:30 node-5 haproxy[428]: proxy glance-registry has no server available!
<129>Oct  9 18:08:31 node-5 haproxy[428]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:31 node-5 haproxy[428]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:31 node-5 haproxy[428]: proxy aodh has no server available!
<129>Oct  9 18:08:31 node-5 haproxy[428]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:31 node-5 haproxy[428]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:31 node-5 haproxy[428]: proxy ceilometer has no server available!
<129>Oct  9 18:08:31 node-5 haproxy[428]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:31 node-5 haproxy[428]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:31 node-5 haproxy[428]: proxy nova-novncproxy has no server available!
<129>Oct  9 18:08:33 node-5 haproxy[1657]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:33 node-5 haproxy[1657]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:33 node-5 haproxy[1657]: Server nova-api/node-5 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:33 node-5 haproxy[1657]: Server nova-metadata-api/node-5 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:33 node-5 haproxy[1657]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:33 node-5 haproxy[1657]: Server glance-api/node-5 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:33 node-5 haproxy[1657]: Server glance-glare/node-5 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:33 node-5 haproxy[1657]: Server neutron/node-5 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:33 node-5 haproxy[1657]: Server glance-registry/node-5 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:34 node-5 haproxy[1657]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:34 node-5 haproxy[1657]: Server object-storage/node-5 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:34 node-5 haproxy[1657]: Server aodh/node-5 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:34 node-5 haproxy[1657]: Server ceilometer/node-5 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:34 node-5 haproxy[1657]: Server heat-api/node-5 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:34 node-5 haproxy[1657]: Server heat-api-cfn/node-5 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:34 node-5 haproxy[1657]: Server heat-api-cloudwatch/node-5 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:34 node-5 haproxy[1657]: Server nova-novncproxy/node-5 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:34 node-5 haproxy[1657]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:34 node-5 haproxy[1657]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:35 node-5 haproxy[1657]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Oct  9 18:08:35 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:35 node-5 haproxy[1657]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:35 node-5 haproxy[1657]: proxy glance-registry has no server available!
<27>Oct  9 18:08:35 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:35 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:35 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:35 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:36 node-5 haproxy[1657]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:36 node-5 haproxy[1657]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:36 node-5 haproxy[1657]: proxy aodh has no server available!
<129>Oct  9 18:08:36 node-5 haproxy[1657]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:36 node-5 haproxy[1657]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:36 node-5 haproxy[1657]: proxy ceilometer has no server available!
<129>Oct  9 18:08:36 node-5 haproxy[1657]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:36 node-5 haproxy[1657]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:36 node-5 haproxy[1657]: proxy nova-novncproxy has no server available!
<27>Oct  9 18:08:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:08:42 node-5 multipathd: uevent trigger error
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server keystone-1/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server keystone-1/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:43 node-5 haproxy[1657]: proxy keystone-1 has no server available!
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server keystone-2/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server keystone-2/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:43 node-5 haproxy[1657]: proxy keystone-2 has no server available!
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server nova-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server nova-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:43 node-5 haproxy[1657]: proxy nova-api has no server available!
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:43 node-5 haproxy[1657]: proxy nova-metadata-api has no server available!
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server cinder-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:43 node-5 haproxy[1657]: proxy cinder-api has no server available!
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server glance-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server glance-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:43 node-5 haproxy[1657]: proxy glance-api has no server available!
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server glance-glare/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server glance-glare/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:43 node-5 haproxy[1657]: proxy glance-glare has no server available!
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server neutron/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:43 node-5 haproxy[1657]: Server neutron/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:43 node-5 haproxy[1657]: proxy neutron has no server available!
<129>Oct  9 18:08:44 node-5 haproxy[1657]: Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:44 node-5 haproxy[1657]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:44 node-5 haproxy[1657]: proxy mysqld has no server available!
<129>Oct  9 18:08:44 node-5 haproxy[1657]: Server object-storage/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:44 node-5 haproxy[1657]: Server object-storage/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:44 node-5 haproxy[1657]: proxy object-storage has no server available!
<129>Oct  9 18:08:44 node-5 haproxy[1657]: Server heat-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:44 node-5 haproxy[1657]: Server heat-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:44 node-5 haproxy[1657]: proxy heat-api has no server available!
<129>Oct  9 18:08:44 node-5 haproxy[1657]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:44 node-5 haproxy[1657]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 timeout, check duration: 10002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:44 node-5 haproxy[1657]: proxy heat-api-cfn has no server available!
<129>Oct  9 18:08:44 node-5 haproxy[1657]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  9 18:08:44 node-5 haproxy[1657]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  9 18:08:44 node-5 haproxy[1657]: proxy heat-api-cloudwatch has no server available!
<27>Oct  9 18:09:15 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  9 18:09:15 node-5 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  9 18:09:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:23 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:23 node-5 multipathd: uevent trigger error
<43>Oct  9 18:09:23 node-5 apache2_error [Sun Oct 09 18:09:15.906018 2016] [mpm_worker:notice] [pid 9471:tid 139930820851584] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  9 18:09:23 node-5 apache2_error [Sun Oct 09 18:09:15.911195 2016] [mpm_worker:warn] [pid 9471:tid 139930820851584] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  9 18:09:23 node-5 apache2_error [Sun Oct 09 18:09:15.911615 2016] [mpm_worker:notice] [pid 9471:tid 139930820851584] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  9 18:09:23 node-5 apache2_error [Sun Oct 09 18:09:15.911622 2016] [core:notice] [pid 9471:tid 139930820851584] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:09:44 node-5 multipathd: uevent trigger error
<27>Oct  9 18:09:53 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  9 18:10:48 node-5 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:10:50 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct  9 18:12:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:12:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:12:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:12:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:12:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:12:16 node-5 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  9 18:13:27 node-5 multipathd: uevent trigger error
<27>Oct  9 18:13:27 node-5 multipathd: uevent trigger error
<27>Oct  9 18:13:27 node-5 multipathd: uevent trigger error
<27>Oct  9 18:13:27 node-5 multipathd: uevent trigger error
<27>Oct  9 18:13:27 node-5 multipathd: uevent trigger error
<27>Oct  9 18:13:33 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct  9 18:13:40 node-5 multipathd: uevent trigger error
<27>Oct  9 18:13:40 node-5 multipathd: uevent trigger error
<27>Oct  9 18:13:40 node-5 multipathd: uevent trigger error
<27>Oct  9 18:13:40 node-5 multipathd: uevent trigger error
<27>Oct  9 18:13:40 node-5 multipathd: uevent trigger error
<27>Oct  9 18:15:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:15:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:15:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:15:03 node-5 multipathd: uevent trigger error
<27>Oct  9 18:15:03 node-5 multipathd: uevent trigger error
<43>Oct  9 18:16:14 node-5 apache2_error [Sun Oct 09 18:16:12.231861 2016] [mpm_worker:notice] [pid 9471:tid 139930820851584] AH00295: caught SIGTERM, shutting down
<43>Oct  9 18:16:14 node-5 apache2_error [Sun Oct 09 18:16:12.985416 2016] [mpm_worker:notice] [pid 6274:tid 139742964979584] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  9 18:16:14 node-5 apache2_error [Sun Oct 09 18:16:12.985445 2016] [core:notice] [pid 6274:tid 139742964979584] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:16:50 node-5 multipathd: uevent trigger error
<27>Oct  9 18:16:50 node-5 multipathd: uevent trigger error
<27>Oct  9 18:16:50 node-5 multipathd: uevent trigger error
<27>Oct  9 18:16:50 node-5 multipathd: uevent trigger error
<27>Oct  9 18:16:51 node-5 multipathd: uevent trigger error
<43>Oct  9 18:16:54 node-5 apache2_error [Sun Oct 09 18:16:44.833479 2016] [mpm_worker:notice] [pid 6274:tid 139742964979584] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  9 18:16:54 node-5 apache2_error [Sun Oct 09 18:16:44.838426 2016] [mpm_worker:warn] [pid 6274:tid 139742964979584] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  9 18:16:54 node-5 apache2_error [Sun Oct 09 18:16:44.843350 2016] [mpm_worker:notice] [pid 6274:tid 139742964979584] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  9 18:16:54 node-5 apache2_error [Sun Oct 09 18:16:44.843382 2016] [core:notice] [pid 6274:tid 139742964979584] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:17:47 node-5 multipathd: uevent trigger error
<27>Oct  9 18:17:47 node-5 multipathd: uevent trigger error
<27>Oct  9 18:17:47 node-5 multipathd: uevent trigger error
<27>Oct  9 18:17:47 node-5 multipathd: uevent trigger error
<27>Oct  9 18:17:47 node-5 multipathd: uevent trigger error
<27>Oct  9 18:19:01 node-5 multipathd: uevent trigger error
<27>Oct  9 18:19:01 node-5 multipathd: uevent trigger error
<27>Oct  9 18:19:01 node-5 multipathd: uevent trigger error
<27>Oct  9 18:19:01 node-5 multipathd: uevent trigger error
<27>Oct  9 18:19:01 node-5 multipathd: uevent trigger error
<27>Oct  9 18:23:27 node-5 multipathd: uevent trigger error
<27>Oct  9 18:23:27 node-5 multipathd: uevent trigger error
<27>Oct  9 18:23:27 node-5 multipathd: uevent trigger error
<27>Oct  9 18:23:27 node-5 multipathd: uevent trigger error
<27>Oct  9 18:23:27 node-5 multipathd: uevent trigger error
<27>Oct  9 18:25:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:25:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:25:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:25:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:25:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:25:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:26:41 node-5 multipathd: uevent trigger error
<27>Oct  9 18:26:41 node-5 multipathd: uevent trigger error
<27>Oct  9 18:26:41 node-5 multipathd: uevent trigger error
<27>Oct  9 18:26:41 node-5 multipathd: uevent trigger error
<27>Oct  9 18:26:41 node-5 multipathd: uevent trigger error
<27>Oct  9 18:26:41 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:36 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct  9 18:27:36 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct  9 18:27:37 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct  9 18:27:38 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Oct  9 18:27:38 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Oct  9 18:27:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:39 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:56 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:56 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:56 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:56 node-5 multipathd: uevent trigger error
<27>Oct  9 18:27:56 node-5 multipathd: uevent trigger error
<27>Oct  9 18:28:01 node-5 multipathd: uevent trigger error
<27>Oct  9 18:28:01 node-5 multipathd: uevent trigger error
<27>Oct  9 18:28:01 node-5 multipathd: uevent trigger error
<27>Oct  9 18:28:01 node-5 multipathd: uevent trigger error
<27>Oct  9 18:28:01 node-5 multipathd: uevent trigger error
<27>Oct  9 18:28:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:28:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:28:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:28:28 node-5 multipathd: uevent trigger error
<43>Oct  9 18:29:15 node-5 apache2_error [Sun Oct 09 18:29:13.228378 2016] [mpm_worker:notice] [pid 6274:tid 139742964979584] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  9 18:29:15 node-5 apache2_error [Sun Oct 09 18:29:13.614061 2016] [mpm_worker:warn] [pid 6274:tid 139742964979584] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  9 18:29:15 node-5 apache2_error [Sun Oct 09 18:29:13.619048 2016] [mpm_worker:notice] [pid 6274:tid 139742964979584] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  9 18:29:15 node-5 apache2_error [Sun Oct 09 18:29:13.619072 2016] [core:notice] [pid 6274:tid 139742964979584] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:29:55 node-5 multipathd: uevent trigger error
<27>Oct  9 18:29:55 node-5 multipathd: uevent trigger error
<27>Oct  9 18:29:55 node-5 multipathd: uevent trigger error
<27>Oct  9 18:29:55 node-5 multipathd: uevent trigger error
<43>Oct  9 18:29:55 node-5 apache2_error [Sun Oct 09 18:29:50.527280 2016] [mpm_worker:notice] [pid 6274:tid 139742964979584] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  9 18:29:55 node-5 apache2_error [Sun Oct 09 18:29:50.909943 2016] [mpm_worker:warn] [pid 6274:tid 139742964979584] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  9 18:29:55 node-5 apache2_error [Sun Oct 09 18:29:50.918062 2016] [mpm_worker:notice] [pid 6274:tid 139742964979584] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  9 18:29:55 node-5 apache2_error [Sun Oct 09 18:29:50.918103 2016] [core:notice] [pid 6274:tid 139742964979584] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  9 18:29:59 node-5 multipathd: uevent trigger error
<27>Oct  9 18:29:59 node-5 multipathd: uevent trigger error
<27>Oct  9 18:29:59 node-5 multipathd: uevent trigger error
<27>Oct  9 18:29:59 node-5 multipathd: uevent trigger error
<27>Oct  9 18:29:59 node-5 multipathd: uevent trigger error
<27>Oct  9 18:30:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:30:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:30:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:30:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:30:42 node-5 multipathd: uevent trigger error
<27>Oct  9 18:31:30 node-5 multipathd: uevent trigger error
<27>Oct  9 18:31:30 node-5 multipathd: uevent trigger error
<27>Oct  9 18:31:31 node-5 multipathd: uevent trigger error
<27>Oct  9 18:31:31 node-5 multipathd: uevent trigger error
<27>Oct  9 18:31:31 node-5 multipathd: uevent trigger error
<27>Oct  9 18:31:41 node-5 multipathd: uevent trigger error
<27>Oct  9 18:31:41 node-5 multipathd: uevent trigger error
<27>Oct  9 18:31:41 node-5 multipathd: uevent trigger error
<27>Oct  9 18:31:41 node-5 multipathd: uevent trigger error
<27>Oct  9 18:31:41 node-5 multipathd: uevent trigger error
<11>Oct  9 18:31:50 node-5 liberasurecode[21844]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:50 node-5 liberasurecode[21844]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:50 node-5 liberasurecode[21844]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:50 node-5 liberasurecode[21844]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:50 node-5 liberasurecode[21893]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:50 node-5 liberasurecode[21893]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:50 node-5 liberasurecode[21893]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:50 node-5 liberasurecode[21893]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:52 node-5 liberasurecode[23016]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:52 node-5 liberasurecode[23016]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:52 node-5 liberasurecode[23016]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:52 node-5 liberasurecode[23016]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:56 node-5 liberasurecode[25011]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:56 node-5 liberasurecode[25011]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:56 node-5 liberasurecode[25011]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:56 node-5 liberasurecode[25011]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25052]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25052]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25052]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25052]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25270]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25270]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25270]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25270]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25368]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25368]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25368]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25368]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25383]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25383]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25383]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25383]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25399]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25399]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25399]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25399]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25524]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25524]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25524]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  9 18:31:57 node-5 liberasurecode[25524]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  9 18:32:04 node-5 multipathd: uevent trigger error
<27>Oct  9 18:32:04 node-5 multipathd: uevent trigger error
<27>Oct  9 18:32:04 node-5 multipathd: uevent trigger error
<27>Oct  9 18:32:04 node-5 multipathd: uevent trigger error
<27>Oct  9 18:32:04 node-5 multipathd: uevent trigger error
<27>Oct  9 18:32:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:32:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:32:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:32:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:32:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:32:09 node-5 multipathd: uevent trigger error
<27>Oct  9 18:33:18 node-5 multipathd: uevent trigger error
<27>Oct  9 18:33:18 node-5 multipathd: uevent trigger error
<27>Oct  9 18:33:18 node-5 multipathd: uevent trigger error
<27>Oct  9 18:33:18 node-5 multipathd: uevent trigger error
<27>Oct  9 18:33:18 node-5 multipathd: uevent trigger error
<11>Oct  9 18:35:01 node-5 liberasurecode[17742]: 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-5 liberasurecode[17742]: 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-5 liberasurecode[17742]: 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-5 liberasurecode[17742]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  9 18:35:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:20 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:25 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:38 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:44 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:44 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:44 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:44 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:44 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:58 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:58 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:58 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:58 node-5 multipathd: uevent trigger error
<27>Oct  9 18:35:58 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:06 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:10 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:10 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:10 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:10 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:10 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:15 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:19 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:24 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:24 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:24 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:24 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:24 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:28 node-5 multipathd: uevent trigger error
<27>Oct  9 18:36:42 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  9 18:36:42 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
