Oct  4 22:32:22 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8434" x-info="http://www.rsyslog.com"] start
Oct  4 22:32:22 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct  4 22:32:22 node-5 rsyslogd: rsyslogd's groupid changed to 104
Oct  4 22:32:22 node-5 rsyslogd: rsyslogd's userid changed to 101
Oct  4 22:32:22 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct  4 22:32:22 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct  4 22:32:22 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct  4 22:32:22 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  4 22:32:22 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=ac438202-8ef3-48c5-aa27-c9eceb43ff95 nomdmonddf nomdmonisw
Oct  4 22:32:22 node-5 kernel: [    0.000000] KERNEL supported cpus:
Oct  4 22:32:22 node-5 kernel: [    0.000000]   Intel GenuineIntel
Oct  4 22:32:22 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Oct  4 22:32:22 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Oct  4 22:32:22 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct  4 22:32:22 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct  4 22:32:22 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct  4 22:32:22 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Oct  4 22:32:22 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  4 22:32:22 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct  4 22:32:22 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct  4 22:32:22 node-5 kernel: [    0.000000] No AGP bridge found
Oct  4 22:32:22 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct  4 22:32:22 node-5 kernel: [    0.000000] MTRR default type: write-back
Oct  4 22:32:22 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct  4 22:32:22 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Oct  4 22:32:22 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct  4 22:32:22 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct  4 22:32:22 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Oct  4 22:32:22 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct  4 22:32:22 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct  4 22:32:22 node-5 kernel: [    0.000000]   2 disabled
Oct  4 22:32:22 node-5 kernel: [    0.000000]   3 disabled
Oct  4 22:32:22 node-5 kernel: [    0.000000]   4 disabled
Oct  4 22:32:22 node-5 kernel: [    0.000000]   5 disabled
Oct  4 22:32:22 node-5 kernel: [    0.000000]   6 disabled
Oct  4 22:32:22 node-5 kernel: [    0.000000]   7 disabled
Oct  4 22:32:22 node-5 kernel: [    0.000000]   8 disabled
Oct  4 22:32:22 node-5 kernel: [    0.000000]   9 disabled
Oct  4 22:32:22 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct  4 22:32:22 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct  4 22:32:22 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct  4 22:32:22 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct  4 22:32:22 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct  4 22:32:22 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Oct  4 22:32:22 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct  4 22:32:22 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct  4 22:32:22 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct  4 22:32:22 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct  4 22:32:22 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct  4 22:32:22 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct  4 22:32:22 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct  4 22:32:22 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct  4 22:32:22 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct  4 22:32:22 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct  4 22:32:22 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct  4 22:32:22 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct  4 22:32:22 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct  4 22:32:22 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct  4 22:32:22 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct  4 22:32:22 node-5 kernel: [    0.000000] Zone ranges:
Oct  4 22:32:22 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] Movable zone start for each node
Oct  4 22:32:22 node-5 kernel: [    0.000000] Early memory node ranges
Oct  4 22:32:22 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct  4 22:32:22 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct  4 22:32:22 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct  4 22:32:22 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct  4 22:32:22 node-5 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct  4 22:32:22 node-5 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct  4 22:32:22 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct  4 22:32:22 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct  4 22:32:22 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct  4 22:32:22 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct  4 22:32:22 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct  4 22:32:22 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct  4 22:32:22 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct  4 22:32:22 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct  4 22:32:22 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct  4 22:32:22 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct  4 22:32:22 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct  4 22:32:22 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct  4 22:32:22 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct  4 22:32:22 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct  4 22:32:22 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct  4 22:32:22 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct  4 22:32:22 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct  4 22:32:22 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  4 22:32:22 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct  4 22:32:22 node-5 kernel: [    0.000000] Policy zone: Normal
Oct  4 22:32:22 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=ac438202-8ef3-48c5-aa27-c9eceb43ff95 nomdmonddf nomdmonisw
Oct  4 22:32:22 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct  4 22:32:22 node-5 kernel: [    0.000000] Checking aperture...
Oct  4 22:32:22 node-5 kernel: [    0.000000] No AGP bridge found
Oct  4 22:32:22 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct  4 22:32:22 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct  4 22:32:22 node-5 kernel: [    0.000000] Memory: 32653312K/33280496K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Oct  4 22:32:22 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct  4 22:32:22 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Oct  4 22:32:22 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct  4 22:32:22 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct  4 22:32:22 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct  4 22:32:22 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct  4 22:32:22 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct  4 22:32:22 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Oct  4 22:32:22 node-5 kernel: [    0.000000] console [tty0] enabled
Oct  4 22:32:22 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct  4 22:32:22 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct  4 22:32:22 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct  4 22:32:22 node-5 kernel: [    0.000000] hpet clockevent registered
Oct  4 22:32:22 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct  4 22:32:22 node-5 kernel: [    0.004000] tsc: Detected 3491.982 MHz processor
Oct  4 22:32:22 node-5 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.96 BogoMIPS (lpj=13967928)
Oct  4 22:32:22 node-5 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct  4 22:32:22 node-5 kernel: [    0.000043] Security Framework initialized
Oct  4 22:32:22 node-5 kernel: [    0.000061] AppArmor: AppArmor initialized
Oct  4 22:32:22 node-5 kernel: [    0.000062] Yama: becoming mindful.
Oct  4 22:32:22 node-5 kernel: [    0.001443] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.006356] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.008288] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.008315] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.008604] Initializing cgroup subsys memory
Oct  4 22:32:22 node-5 kernel: [    0.008612] Initializing cgroup subsys devices
Oct  4 22:32:22 node-5 kernel: [    0.008614] Initializing cgroup subsys freezer
Oct  4 22:32:22 node-5 kernel: [    0.008616] Initializing cgroup subsys blkio
Oct  4 22:32:22 node-5 kernel: [    0.008617] Initializing cgroup subsys perf_event
Oct  4 22:32:22 node-5 kernel: [    0.008620] Initializing cgroup subsys hugetlb
Oct  4 22:32:22 node-5 kernel: [    0.008640] CPU: Physical Processor ID: 0
Oct  4 22:32:22 node-5 kernel: [    0.008641] CPU: Processor Core ID: 0
Oct  4 22:32:22 node-5 kernel: [    0.008645] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct  4 22:32:22 node-5 kernel: [    0.008645] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct  4 22:32:22 node-5 kernel: [    0.009338] mce: CPU supports 22 MCE banks
Oct  4 22:32:22 node-5 kernel: [    0.009366] CPU0: Thermal monitoring enabled (TM1)
Oct  4 22:32:22 node-5 kernel: [    0.009387] process: using mwait in idle threads
Oct  4 22:32:22 node-5 kernel: [    0.009390] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct  4 22:32:22 node-5 kernel: [    0.009390] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct  4 22:32:22 node-5 kernel: [    0.009390] tlb_flushall_shift: 6
Oct  4 22:32:22 node-5 kernel: [    0.009479] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct  4 22:32:22 node-5 kernel: [    0.010202] ACPI: Core revision 20131115
Oct  4 22:32:22 node-5 kernel: [    0.022860] ACPI: All ACPI Tables successfully acquired
Oct  4 22:32:22 node-5 kernel: [    0.023021] ftrace: allocating 28614 entries in 112 pages
Oct  4 22:32:22 node-5 kernel: [    0.031736] dmar: Host address width 46
Oct  4 22:32:22 node-5 kernel: [    0.031738] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct  4 22:32:22 node-5 kernel: [    0.031744] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  4 22:32:22 node-5 kernel: [    0.031746] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct  4 22:32:22 node-5 kernel: [    0.031750] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  4 22:32:22 node-5 kernel: [    0.031751] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct  4 22:32:22 node-5 kernel: [    0.031753] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct  4 22:32:22 node-5 kernel: [    0.031754] dmar: ATSR flags: 0x0
Oct  4 22:32:22 node-5 kernel: [    0.031755] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct  4 22:32:22 node-5 kernel: [    0.031756] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct  4 22:32:22 node-5 kernel: [    0.031872] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct  4 22:32:22 node-5 kernel: [    0.031873] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct  4 22:32:22 node-5 kernel: [    0.031874] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct  4 22:32:22 node-5 kernel: [    0.031875] HPET id 0 under DRHD base 0xc7ffc000
Oct  4 22:32:22 node-5 kernel: [    0.031876] Your BIOS is broken and requested that x2apic be disabled.
Oct  4 22:32:22 node-5 kernel: [    0.031876] This will slightly decrease performance.
Oct  4 22:32:22 node-5 kernel: [    0.031876] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct  4 22:32:22 node-5 kernel: [    0.032308] Enabled IRQ remapping in xapic mode
Oct  4 22:32:22 node-5 kernel: [    0.032309] x2apic not enabled, IRQ remapping is in xapic mode
Oct  4 22:32:22 node-5 kernel: [    0.032313] Switched APIC routing to physical flat.
Oct  4 22:32:22 node-5 kernel: [    0.032935] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct  4 22:32:22 node-5 kernel: [    0.072585] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct  4 22:32:22 node-5 kernel: [    0.072591] TSC deadline timer enabled
Oct  4 22:32:22 node-5 kernel: [    0.072598] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct  4 22:32:22 node-5 kernel: [    0.072604] ... version:                3
Oct  4 22:32:22 node-5 kernel: [    0.072605] ... bit width:              48
Oct  4 22:32:22 node-5 kernel: [    0.072606] ... generic registers:      4
Oct  4 22:32:22 node-5 kernel: [    0.072607] ... value mask:             0000ffffffffffff
Oct  4 22:32:22 node-5 kernel: [    0.072608] ... max period:             0000ffffffffffff
Oct  4 22:32:22 node-5 kernel: [    0.072609] ... fixed-purpose events:   3
Oct  4 22:32:22 node-5 kernel: [    0.072610] ... event mask:             000000070000000f
Oct  4 22:32:22 node-5 kernel: [    0.074016] x86: Booting SMP configuration:
Oct  4 22:32:22 node-5 kernel: [    0.088122] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct  4 22:32:22 node-5 kernel: [    0.074018] .... node  #0, CPUs:        #1  #2  #3
Oct  4 22:32:22 node-5 kernel: [    0.116035] .... node  #1, CPUs:    #4  #5  #6  #7
Oct  4 22:32:22 node-5 kernel: [    0.270197] .... node  #0, CPUs:    #8  #9 #10 #11
Oct  4 22:32:22 node-5 kernel: [    0.325867] .... node  #1, CPUs:   #12 #13 #14 #15
Oct  4 22:32:22 node-5 kernel: [    0.382930] x86: Booted up 2 nodes, 16 CPUs
Oct  4 22:32:22 node-5 kernel: [    0.382934] smpboot: Total of 16 processors activated (111755.48 BogoMIPS)
Oct  4 22:32:22 node-5 kernel: [    0.407294] devtmpfs: initialized
Oct  4 22:32:22 node-5 kernel: [    0.409644] EVM: security.selinux
Oct  4 22:32:22 node-5 kernel: [    0.409646] EVM: security.SMACK64
Oct  4 22:32:22 node-5 kernel: [    0.409647] EVM: security.ima
Oct  4 22:32:22 node-5 kernel: [    0.409648] EVM: security.capability
Oct  4 22:32:22 node-5 kernel: [    0.409699] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.410360] pinctrl core: initialized pinctrl subsystem
Oct  4 22:32:22 node-5 kernel: [    0.410420] regulator-dummy: no parameters
Oct  4 22:32:22 node-5 kernel: [    0.410451] RTC time: 22:31:45, date: 10/04/16
Oct  4 22:32:22 node-5 kernel: [    0.410486] NET: Registered protocol family 16
Oct  4 22:32:22 node-5 kernel: [    0.410569] cpuidle: using governor ladder
Oct  4 22:32:22 node-5 kernel: [    0.410570] cpuidle: using governor menu
Oct  4 22:32:22 node-5 kernel: [    0.410606] ACPI: bus type PCI registered
Oct  4 22:32:22 node-5 kernel: [    0.410607] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct  4 22:32:22 node-5 kernel: [    0.410652] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct  4 22:32:22 node-5 kernel: [    0.410655] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct  4 22:32:22 node-5 kernel: [    0.424403] PCI: Using configuration type 1 for base access
Oct  4 22:32:22 node-5 kernel: [    0.425408] bio: create slab <bio-0> at 0
Oct  4 22:32:22 node-5 kernel: [    0.425676] ACPI: Added _OSI(Module Device)
Oct  4 22:32:22 node-5 kernel: [    0.425678] ACPI: Added _OSI(Processor Device)
Oct  4 22:32:22 node-5 kernel: [    0.425679] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct  4 22:32:22 node-5 kernel: [    0.425680] ACPI: Added _OSI(Processor Aggregator Device)
Oct  4 22:32:22 node-5 kernel: [    0.438454] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct  4 22:32:22 node-5 kernel: [    0.449105] ACPI: Interpreter enabled
Oct  4 22:32:22 node-5 kernel: [    0.449110] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct  4 22:32:22 node-5 kernel: [    0.449114] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct  4 22:32:22 node-5 kernel: [    0.449117] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct  4 22:32:22 node-5 kernel: [    0.449124] ACPI: (supports S0 S4 S5)
Oct  4 22:32:22 node-5 kernel: [    0.449125] ACPI: Using IOAPIC for interrupt routing
Oct  4 22:32:22 node-5 kernel: [    0.449168] HEST: Table parsing has been initialized.
Oct  4 22:32:22 node-5 kernel: [    0.449171] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct  4 22:32:22 node-5 kernel: [    0.449747] ACPI: No dock devices found.
Oct  4 22:32:22 node-5 kernel: [    0.461873] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct  4 22:32:22 node-5 kernel: [    0.461877] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  4 22:32:22 node-5 kernel: [    0.461881] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  4 22:32:22 node-5 kernel: [    0.461911] PCI host bridge to bus 0000:ff
Oct  4 22:32:22 node-5 kernel: [    0.461914] pci_bus 0000:ff: root bus resource [bus ff]
Oct  4 22:32:22 node-5 kernel: [    0.461922] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.461961] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.461991] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462026] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462056] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.462086] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.462118] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462147] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462178] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462206] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462232] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462259] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462288] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462314] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462341] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462368] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462396] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462424] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462451] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.462479] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462505] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.462531] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462557] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462587] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.462622] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462653] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462683] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462714] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462745] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462776] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462808] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462841] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462872] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462907] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462941] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.462974] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463008] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463039] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463066] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463100] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463136] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463173] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463209] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463243] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463273] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463304] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463335] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463366] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463398] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463428] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463460] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463488] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463517] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463545] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463575] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463606] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463636] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463694] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct  4 22:32:22 node-5 kernel: [    0.463697] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  4 22:32:22 node-5 kernel: [    0.463700] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  4 22:32:22 node-5 kernel: [    0.463718] PCI host bridge to bus 0000:7f
Oct  4 22:32:22 node-5 kernel: [    0.463719] pci_bus 0000:7f: root bus resource [bus 7f]
Oct  4 22:32:22 node-5 kernel: [    0.463724] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463751] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.463779] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463809] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463831] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.463855] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.463881] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463906] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463930] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463955] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.463979] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464003] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464029] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464051] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464074] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464099] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464121] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464144] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464166] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.464190] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464212] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.464234] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464256] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464282] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct  4 22:32:22 node-5 kernel: [    0.464315] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464341] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464367] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464393] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464418] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464444] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464470] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464497] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464522] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464548] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464574] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464601] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464629] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464655] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464683] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464711] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464736] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464762] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464790] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464816] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464840] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464865] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464890] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464917] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464943] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464970] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.464999] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.465022] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.465044] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.465069] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.465093] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.465122] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.465147] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.466399] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct  4 22:32:22 node-5 kernel: [    0.466403] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  4 22:32:22 node-5 kernel: [    0.467539] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  4 22:32:22 node-5 kernel: [    0.468048] PCI host bridge to bus 0000:00
Oct  4 22:32:22 node-5 kernel: [    0.468050] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct  4 22:32:22 node-5 kernel: [    0.468052] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct  4 22:32:22 node-5 kernel: [    0.468053] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct  4 22:32:22 node-5 kernel: [    0.468054] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct  4 22:32:22 node-5 kernel: [    0.468056] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct  4 22:32:22 node-5 kernel: [    0.468057] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct  4 22:32:22 node-5 kernel: [    0.468058] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct  4 22:32:22 node-5 kernel: [    0.468064] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct  4 22:32:22 node-5 kernel: [    0.468146] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.468177] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.468219] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct  4 22:32:22 node-5 kernel: [    0.468238] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.468267] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.468308] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct  4 22:32:22 node-5 kernel: [    0.468326] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.468356] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.468396] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct  4 22:32:22 node-5 kernel: [    0.468412] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.468482] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.468558] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.468635] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct  4 22:32:22 node-5 kernel: [    0.468640] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct  4 22:32:22 node-5 kernel: [    0.468725] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct  4 22:32:22 node-5 kernel: [    0.468873] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct  4 22:32:22 node-5 kernel: [    0.468891] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct  4 22:32:22 node-5 kernel: [    0.468969] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.469022] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct  4 22:32:22 node-5 kernel: [    0.469044] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.469099] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.469143] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct  4 22:32:22 node-5 kernel: [    0.469170] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.469226] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.469269] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct  4 22:32:22 node-5 kernel: [    0.469293] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct  4 22:32:22 node-5 kernel: [    0.469310] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct  4 22:32:22 node-5 kernel: [    0.469388] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.469438] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct  4 22:32:22 node-5 kernel: [    0.469463] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct  4 22:32:22 node-5 kernel: [    0.469710] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct  4 22:32:22 node-5 kernel: [    0.469716] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct  4 22:32:22 node-5 kernel: [    0.469722] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.469728] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.469735] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct  4 22:32:22 node-5 kernel: [    0.469766] pci 0000:01:00.0: supports D1 D2
Oct  4 22:32:22 node-5 kernel: [    0.475255] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  4 22:32:22 node-5 kernel: [    0.475261] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  4 22:32:22 node-5 kernel: [    0.475265] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  4 22:32:22 node-5 kernel: [    0.475530] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.475590] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct  4 22:32:22 node-5 kernel: [    0.483251] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  4 22:32:22 node-5 kernel: [    0.483257] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.483261] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:22 node-5 kernel: [    0.483346] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.483436] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.483533] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.483593] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  4 22:32:22 node-5 kernel: [    0.483596] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.483598] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:22 node-5 kernel: [    0.483650] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.483773] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.483826] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  4 22:32:22 node-5 kernel: [    0.483828] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.483831] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:22 node-5 kernel: [    0.483880] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.484003] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.484044] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.484163] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.484202] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.484322] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.484360] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct  4 22:32:22 node-5 kernel: [    0.484499] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct  4 22:32:22 node-5 kernel: [    0.484543] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  4 22:32:22 node-5 kernel: [    0.484545] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.484547] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:22 node-5 kernel: [    0.484607] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct  4 22:32:22 node-5 kernel: [    0.484671] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.484723] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.484764] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct  4 22:32:22 node-5 kernel: [    0.484846] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct  4 22:32:22 node-5 kernel: [    0.484953] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  4 22:32:22 node-5 kernel: [    0.484956] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.484958] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  4 22:32:22 node-5 kernel: [    0.485014] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct  4 22:32:22 node-5 kernel: [    0.485067] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.485116] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.485327] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  4 22:32:22 node-5 kernel: [    0.485330] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  4 22:32:22 node-5 kernel: [    0.485405] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct  4 22:32:22 node-5 kernel: [    0.485466] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.485514] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.485724] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  4 22:32:22 node-5 kernel: [    0.485728] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  4 22:32:22 node-5 kernel: [    0.485787] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct  4 22:32:22 node-5 kernel: [    0.485847] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.485899] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct  4 22:32:22 node-5 kernel: [    0.486123] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  4 22:32:22 node-5 kernel: [    0.486126] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  4 22:32:22 node-5 kernel: [    0.486301] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  4 22:32:22 node-5 kernel: [    0.486339] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  4 22:32:22 node-5 kernel: [    0.486418] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct  4 22:32:22 node-5 kernel: [    0.486436] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct  4 22:32:22 node-5 kernel: [    0.486449] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct  4 22:32:22 node-5 kernel: [    0.486463] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct  4 22:32:22 node-5 kernel: [    0.486513] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct  4 22:32:22 node-5 kernel: [    0.491258] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  4 22:32:22 node-5 kernel: [    0.491267] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  4 22:32:22 node-5 kernel: [    0.491319] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct  4 22:32:22 node-5 kernel: [    0.492077] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct  4 22:32:22 node-5 kernel: [    0.492080] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  4 22:32:22 node-5 kernel: [    0.492200] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  4 22:32:22 node-5 kernel: [    0.492312] PCI host bridge to bus 0000:80
Oct  4 22:32:22 node-5 kernel: [    0.492314] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct  4 22:32:22 node-5 kernel: [    0.492315] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct  4 22:32:22 node-5 kernel: [    0.492317] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct  4 22:32:22 node-5 kernel: [    0.492325] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.492389] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.492457] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct  4 22:32:22 node-5 kernel: [    0.492519] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct  4 22:32:22 node-5 kernel: [    0.492524] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct  4 22:32:22 node-5 kernel: [    0.492595] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct  4 22:32:22 node-5 kernel: [    0.492894] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct  4 22:32:22 node-5 kernel: [    0.492925] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct  4 22:32:22 node-5 kernel: [    0.492955] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct  4 22:32:22 node-5 kernel: [    0.492984] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct  4 22:32:22 node-5 kernel: [    0.493014] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  4 22:32:22 node-5 kernel: [    0.493044] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  4 22:32:22 node-5 kernel: [    0.493074] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  4 22:32:22 node-5 kernel: [    0.493103] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  4 22:32:22 node-5 kernel: [    0.493191] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct  4 22:32:22 node-5 kernel: [    0.493196] ACPI: \_SB_.UNC1: notify handler is installed
Oct  4 22:32:22 node-5 kernel: [    0.493197] ACPI: \_SB_.UNC0: notify handler is installed
Oct  4 22:32:22 node-5 kernel: [    0.493212] ACPI: \_SB_.PCI0: notify handler is installed
Oct  4 22:32:22 node-5 kernel: [    0.493265] ACPI: \_SB_.PCI1: notify handler is installed
Oct  4 22:32:22 node-5 kernel: [    0.493344] Found 4 acpi root devices
Oct  4 22:32:22 node-5 kernel: [    0.493453] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct  4 22:32:22 node-5 kernel: [    0.493455] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct  4 22:32:22 node-5 kernel: [    0.493457] vgaarb: loaded
Oct  4 22:32:22 node-5 kernel: [    0.493458] vgaarb: bridge control possible 0000:0c:00.0
Oct  4 22:32:22 node-5 kernel: [    0.493576] SCSI subsystem initialized
Oct  4 22:32:22 node-5 kernel: [    0.493640] libata version 3.00 loaded.
Oct  4 22:32:22 node-5 kernel: [    0.493656] ACPI: bus type USB registered
Oct  4 22:32:22 node-5 kernel: [    0.493666] usbcore: registered new interface driver usbfs
Oct  4 22:32:22 node-5 kernel: [    0.493671] usbcore: registered new interface driver hub
Oct  4 22:32:22 node-5 kernel: [    0.493694] usbcore: registered new device driver usb
Oct  4 22:32:22 node-5 kernel: [    0.493856] PCI: Using ACPI for IRQ routing
Oct  4 22:32:22 node-5 kernel: [    0.497449] PCI: pci_cache_line_size set to 64 bytes
Oct  4 22:32:22 node-5 kernel: [    0.497652] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct  4 22:32:22 node-5 kernel: [    0.497654] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct  4 22:32:22 node-5 kernel: [    0.497654] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct  4 22:32:22 node-5 kernel: [    0.497718] NetLabel: Initializing
Oct  4 22:32:22 node-5 kernel: [    0.497719] NetLabel:  domain hash size = 128
Oct  4 22:32:22 node-5 kernel: [    0.497720] NetLabel:  protocols = UNLABELED CIPSOv4
Oct  4 22:32:22 node-5 kernel: [    0.497730] NetLabel:  unlabeled traffic allowed by default
Oct  4 22:32:22 node-5 kernel: [    0.497787] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct  4 22:32:22 node-5 kernel: [    0.497791] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct  4 22:32:22 node-5 kernel: [    0.499860] Switched to clocksource hpet
Oct  4 22:32:22 node-5 kernel: [    0.504260] AppArmor: AppArmor Filesystem Enabled
Oct  4 22:32:22 node-5 kernel: [    0.504298] pnp: PnP ACPI init
Oct  4 22:32:22 node-5 kernel: [    0.504310] ACPI: bus type PNP registered
Oct  4 22:32:22 node-5 kernel: [    0.504490] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct  4 22:32:22 node-5 kernel: [    0.504501] pnp 00:01: [dma 4]
Oct  4 22:32:22 node-5 kernel: [    0.504520] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct  4 22:32:22 node-5 kernel: [    0.504554] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct  4 22:32:22 node-5 kernel: [    0.504580] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct  4 22:32:22 node-5 kernel: [    0.504601] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct  4 22:32:22 node-5 kernel: [    0.504648] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct  4 22:32:22 node-5 kernel: [    0.504760] system 00:06: [io  0x0500-0x057f] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504762] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct  4 22:32:22 node-5 kernel: [    0.504764] system 00:06: [io  0x0580-0x059f] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504765] system 00:06: [io  0x0600-0x061f] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504767] system 00:06: [io  0x0880-0x0883] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504768] system 00:06: [io  0x0800-0x081f] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504772] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct  4 22:32:22 node-5 kernel: [    0.504773] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504775] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504777] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504778] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504780] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504781] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct  4 22:32:22 node-5 kernel: [    0.504783] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct  4 22:32:22 node-5 kernel: [    0.504888] pnp 00:07: [dma 0 disabled]
Oct  4 22:32:22 node-5 kernel: [    0.504921] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  4 22:32:22 node-5 kernel: [    0.505003] pnp 00:08: [dma 0 disabled]
Oct  4 22:32:22 node-5 kernel: [    0.505039] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  4 22:32:22 node-5 kernel: [    0.505097] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct  4 22:32:22 node-5 kernel: [    0.505547] pnp: PnP ACPI: found 10 devices
Oct  4 22:32:22 node-5 kernel: [    0.505549] ACPI: bus type PNP unregistered
Oct  4 22:32:22 node-5 kernel: [    0.511544] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  4 22:32:22 node-5 kernel: [    0.511548] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  4 22:32:22 node-5 kernel: [    0.511551] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  4 22:32:22 node-5 kernel: [    0.511556] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  4 22:32:22 node-5 kernel: [    0.511558] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.511579] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511608] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  4 22:32:22 node-5 kernel: [    0.511622] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511651] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  4 22:32:22 node-5 kernel: [    0.511665] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  4 22:32:22 node-5 kernel: [    0.511694] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  4 22:32:22 node-5 kernel: [    0.511708] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  4 22:32:22 node-5 kernel: [    0.511740] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  4 22:32:22 node-5 kernel: [    0.511742] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.511757] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511786] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  4 22:32:22 node-5 kernel: [    0.511788] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.511803] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511831] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  4 22:32:22 node-5 kernel: [    0.511838] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.511841] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511845] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  4 22:32:22 node-5 kernel: [    0.511847] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.511850] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511854] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  4 22:32:22 node-5 kernel: [    0.511860] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  4 22:32:22 node-5 kernel: [    0.511869] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  4 22:32:22 node-5 kernel: [    0.511873] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  4 22:32:22 node-5 kernel: [    0.511880] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct  4 22:32:22 node-5 kernel: [    0.511881] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct  4 22:32:22 node-5 kernel: [    0.511882] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct  4 22:32:22 node-5 kernel: [    0.511883] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct  4 22:32:22 node-5 kernel: [    0.511884] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct  4 22:32:22 node-5 kernel: [    0.511885] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct  4 22:32:22 node-5 kernel: [    0.511886] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct  4 22:32:22 node-5 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct  4 22:32:22 node-5 kernel: [    0.511886] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct  4 22:32:22 node-5 kernel: [    0.511887] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.511888] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511890] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.511890] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511892] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.511892] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511893] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.511894] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511895] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct  4 22:32:22 node-5 kernel: [    0.511896] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511897] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct  4 22:32:22 node-5 kernel: [    0.511899] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct  4 22:32:22 node-5 kernel: [    0.511900] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct  4 22:32:22 node-5 kernel: [    0.511901] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct  4 22:32:22 node-5 kernel: [    0.511904] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct  4 22:32:22 node-5 kernel: [    0.511905] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct  4 22:32:22 node-5 kernel: [    0.511945] NET: Registered protocol family 2
Oct  4 22:32:22 node-5 kernel: [    0.512257] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.512636] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.512800] TCP: Hash tables configured (established 262144 bind 65536)
Oct  4 22:32:22 node-5 kernel: [    0.512845] TCP: reno registered
Oct  4 22:32:22 node-5 kernel: [    0.512875] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.512980] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.513145] NET: Registered protocol family 1
Oct  4 22:32:22 node-5 kernel: [    0.551956] pci 0000:0c:00.0: Video device with shadowed ROM
Oct  4 22:32:22 node-5 kernel: [    0.551972] PCI: CLS 64 bytes, default 64
Oct  4 22:32:22 node-5 kernel: [    0.552056] Trying to unpack rootfs image as initramfs...
Oct  4 22:32:22 node-5 kernel: [    0.773323] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Oct  4 22:32:22 node-5 kernel: [    0.773372] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct  4 22:32:22 node-5 kernel: [    0.773374] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct  4 22:32:22 node-5 kernel: [    0.773807] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773821] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773835] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773847] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773860] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773867] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773873] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773879] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773888] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773900] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773915] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773927] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773937] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773945] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773951] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.773956] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct  4 22:32:22 node-5 kernel: [    0.774024] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct  4 22:32:22 node-5 kernel: [    0.774026] Scanning for low memory corruption every 60 seconds
Oct  4 22:32:22 node-5 kernel: [    0.774333] Initialise system trusted keyring
Oct  4 22:32:22 node-5 kernel: [    0.774381] audit: initializing netlink socket (disabled)
Oct  4 22:32:22 node-5 kernel: [    0.774399] type=2000 audit(1475620305.724:1): initialized
Oct  4 22:32:22 node-5 kernel: [    0.792163] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct  4 22:32:22 node-5 kernel: [    0.793616] zbud: loaded
Oct  4 22:32:22 node-5 kernel: [    0.793734] VFS: Disk quotas dquot_6.5.2
Oct  4 22:32:22 node-5 kernel: [    0.793770] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct  4 22:32:22 node-5 kernel: [    0.794116] fuse init (API version 7.22)
Oct  4 22:32:22 node-5 kernel: [    0.794176] msgmni has been set to 32768
Oct  4 22:32:22 node-5 kernel: [    0.794222] Key type big_key registered
Oct  4 22:32:22 node-5 kernel: [    0.794774] Key type asymmetric registered
Oct  4 22:32:22 node-5 kernel: [    0.794776] Asymmetric key parser 'x509' registered
Oct  4 22:32:22 node-5 kernel: [    0.794799] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct  4 22:32:22 node-5 kernel: [    0.794868] io scheduler noop registered
Oct  4 22:32:22 node-5 kernel: [    0.794869] io scheduler deadline registered (default)
Oct  4 22:32:22 node-5 kernel: [    0.794888] io scheduler cfq registered
Oct  4 22:32:22 node-5 kernel: [    0.795427] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    0.795628] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    0.795745] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    0.795858] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    0.795972] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    0.796066] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    0.796512] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct  4 22:32:22 node-5 kernel: [    0.796551] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct  4 22:32:22 node-5 kernel: [    0.796578] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct  4 22:32:22 node-5 kernel: [    0.796610] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796612] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796615] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct  4 22:32:22 node-5 kernel: [    0.796620] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796622] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796623] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796624] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796626] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796627] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796628] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796630] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796631] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796632] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796634] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796635] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796638] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct  4 22:32:22 node-5 kernel: [    0.796651] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796653] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct  4 22:32:22 node-5 kernel: [    0.796664] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796667] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct  4 22:32:22 node-5 kernel: [    0.796678] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796680] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct  4 22:32:22 node-5 kernel: [    0.796683] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct  4 22:32:22 node-5 kernel: [    0.796710] ioapic: probe of 0000:00:05.4 failed with error -22
Oct  4 22:32:22 node-5 kernel: [    0.796715] ioapic: probe of 0000:80:05.4 failed with error -22
Oct  4 22:32:22 node-5 kernel: [    0.796719] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct  4 22:32:22 node-5 kernel: [    0.796728] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct  4 22:32:22 node-5 kernel: [    0.796766] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct  4 22:32:22 node-5 kernel: [    0.796767] vesafb: scrolling: redraw
Oct  4 22:32:22 node-5 kernel: [    0.796769] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct  4 22:32:22 node-5 kernel: [    0.817443] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct  4 22:32:22 node-5 kernel: [    0.825969] Console: switching to colour frame buffer device 80x30
Oct  4 22:32:22 node-5 kernel: [    0.834657] fb0: VESA VGA frame buffer device
Oct  4 22:32:22 node-5 kernel: [    0.834852] intel_idle: MWAIT substates: 0x2120
Oct  4 22:32:22 node-5 kernel: [    0.834853] intel_idle: v0.4 model 0x3F
Oct  4 22:32:22 node-5 kernel: [    0.834854] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct  4 22:32:22 node-5 kernel: [    0.835078] ipmi message handler version 39.2
Oct  4 22:32:22 node-5 kernel: [    0.835354] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  4 22:32:22 node-5 kernel: [    0.835793] ACPI: AC Adapter [P111] (on-line)
Oct  4 22:32:22 node-5 kernel: [    0.841027] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct  4 22:32:22 node-5 kernel: [    0.852047] ACPI: Power Button [PWRB]
Oct  4 22:32:22 node-5 kernel: [    0.857825] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct  4 22:32:22 node-5 kernel: [    0.869545] ACPI: Power Button [PWRF]
Oct  4 22:32:22 node-5 kernel: [    0.885321] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct  4 22:32:22 node-5 kernel: [    0.896964] pstore: Registered erst as persistent store backend
Oct  4 22:32:22 node-5 kernel: [    0.903147] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct  4 22:32:22 node-5 kernel: [    0.915120] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct  4 22:32:22 node-5 kernel: [    0.941877] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct  4 22:32:22 node-5 kernel: [    0.975181] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct  4 22:32:22 node-5 kernel: [    0.989303] Linux agpgart interface v0.103
Oct  4 22:32:22 node-5 kernel: [    0.997037] brd: module loaded
Oct  4 22:32:22 node-5 kernel: [    1.004184] loop: module loaded
Oct  4 22:32:22 node-5 kernel: [    1.010913] libphy: Fixed MDIO Bus: probed
Oct  4 22:32:22 node-5 kernel: [    1.017430] tun: Universal TUN/TAP device driver, 1.6
Oct  4 22:32:22 node-5 kernel: [    1.023951] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct  4 22:32:22 node-5 kernel: [    1.030518] PPP generic driver version 2.4.2
Oct  4 22:32:22 node-5 kernel: [    1.036950] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct  4 22:32:22 node-5 kernel: [    1.043438] ehci-pci: EHCI PCI platform driver
Oct  4 22:32:22 node-5 kernel: [    1.050001] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct  4 22:32:22 node-5 kernel: [    1.056441] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct  4 22:32:22 node-5 kernel: [    1.069040] ehci-pci 0000:00:1a.0: debug port 2
Oct  4 22:32:22 node-5 kernel: [    1.079281] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct  4 22:32:22 node-5 kernel: [    1.079299] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct  4 22:32:22 node-5 kernel: [    1.095347] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct  4 22:32:22 node-5 kernel: [    1.101448] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct  4 22:32:22 node-5 kernel: [    1.107652] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  4 22:32:22 node-5 kernel: [    1.119640] usb usb1: Product: EHCI Host Controller
Oct  4 22:32:22 node-5 kernel: [    1.125723] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  4 22:32:22 node-5 kernel: [    1.131844] usb usb1: SerialNumber: 0000:00:1a.0
Oct  4 22:32:22 node-5 kernel: [    1.137902] hub 1-0:1.0: USB hub found
Oct  4 22:32:22 node-5 kernel: [    1.143772] hub 1-0:1.0: 2 ports detected
Oct  4 22:32:22 node-5 kernel: [    1.149661] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct  4 22:32:22 node-5 kernel: [    1.155295] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct  4 22:32:22 node-5 kernel: [    1.166247] ehci-pci 0000:00:1d.0: debug port 2
Oct  4 22:32:22 node-5 kernel: [    1.175569] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct  4 22:32:22 node-5 kernel: [    1.175571] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct  4 22:32:22 node-5 kernel: [    1.191266] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct  4 22:32:22 node-5 kernel: [    1.196475] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct  4 22:32:22 node-5 kernel: [    1.201776] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  4 22:32:22 node-5 kernel: [    1.212357] usb usb2: Product: EHCI Host Controller
Oct  4 22:32:22 node-5 kernel: [    1.217837] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  4 22:32:22 node-5 kernel: [    1.223386] usb usb2: SerialNumber: 0000:00:1d.0
Oct  4 22:32:22 node-5 kernel: [    1.228927] hub 2-0:1.0: USB hub found
Oct  4 22:32:22 node-5 kernel: [    1.234274] hub 2-0:1.0: 2 ports detected
Oct  4 22:32:22 node-5 kernel: [    1.239577] ehci-platform: EHCI generic platform driver
Oct  4 22:32:22 node-5 kernel: [    1.244803] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct  4 22:32:22 node-5 kernel: [    1.250117] ohci-pci: OHCI PCI platform driver
Oct  4 22:32:22 node-5 kernel: [    1.255414] ohci-platform: OHCI generic platform driver
Oct  4 22:32:22 node-5 kernel: [    1.260617] uhci_hcd: USB Universal Host Controller Interface driver
Oct  4 22:32:22 node-5 kernel: [    1.265949] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct  4 22:32:22 node-5 kernel: [    1.459046] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct  4 22:32:22 node-5 kernel: [    1.631238] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct  4 22:32:22 node-5 kernel: [    1.636762] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  4 22:32:22 node-5 kernel: [    1.642505] hub 1-1:1.0: USB hub found
Oct  4 22:32:22 node-5 kernel: [    1.647975] hub 1-1:1.0: 6 ports detected
Oct  4 22:32:22 node-5 kernel: [    1.762779] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct  4 22:32:22 node-5 kernel: [    1.770804] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct  4 22:32:22 node-5 kernel: [    2.030900] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct  4 22:32:22 node-5 kernel: [    2.036426] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  4 22:32:22 node-5 kernel: [    2.042289] hub 2-1:1.0: USB hub found
Oct  4 22:32:22 node-5 kernel: [    2.047886] hub 2-1:1.0: 8 ports detected
Oct  4 22:32:22 node-5 kernel: [    2.307664] i8042: No controller found
Oct  4 22:32:22 node-5 kernel: [    2.313181] mousedev: PS/2 mouse device common for all mice
Oct  4 22:32:22 node-5 kernel: [    2.318676] rtc_cmos 00:02: RTC can wake from S4
Oct  4 22:32:22 node-5 kernel: [    2.324258] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct  4 22:32:22 node-5 kernel: [    2.326373] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct  4 22:32:22 node-5 kernel: [    2.335377] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct  4 22:32:22 node-5 kernel: [    2.346439] device-mapper: uevent: version 1.0.3
Oct  4 22:32:22 node-5 kernel: [    2.352067] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct  4 22:32:22 node-5 kernel: [    2.363284] ledtrig-cpu: registered to indicate activity on CPUs
Oct  4 22:32:22 node-5 kernel: [    2.369197] TCP: cubic registered
Oct  4 22:32:22 node-5 kernel: [    2.375076] NET: Registered protocol family 10
Oct  4 22:32:22 node-5 kernel: [    2.381056] NET: Registered protocol family 17
Oct  4 22:32:22 node-5 kernel: [    2.386735] Key type dns_resolver registered
Oct  4 22:32:22 node-5 kernel: [    2.392714] Loading compiled-in X.509 certificates
Oct  4 22:32:22 node-5 kernel: [    2.398883] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct  4 22:32:22 node-5 kernel: [    2.410259] registered taskstats version 1
Oct  4 22:32:22 node-5 kernel: [    2.418182] Key type trusted registered
Oct  4 22:32:22 node-5 kernel: [    2.425769] Key type encrypted registered
Oct  4 22:32:22 node-5 kernel: [    2.431208] AppArmor: AppArmor sha1 policy hashing enabled
Oct  4 22:32:22 node-5 kernel: [    2.436670] IMA: No TPM chip found, activating TPM-bypass!
Oct  4 22:32:22 node-5 kernel: [    2.442828] regulator-dummy: disabling
Oct  4 22:32:22 node-5 kernel: [    2.448359]   Magic number: 4:138:552
Oct  4 22:32:22 node-5 kernel: [    2.453752] tty ttyS28: hash matches
Oct  4 22:32:22 node-5 kernel: [    2.459017] clockevents clockevent3: hash matches
Oct  4 22:32:22 node-5 kernel: [    2.464316] pci 0000:08:00.0: hash matches
Oct  4 22:32:22 node-5 kernel: [    2.467090] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct  4 22:32:22 node-5 kernel: [    2.467091] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  4 22:32:22 node-5 kernel: [    2.467092] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct  4 22:32:22 node-5 kernel: [    2.467092] usb 2-1.4: Manufacturer: Avocent
Oct  4 22:32:22 node-5 kernel: [    2.467093] usb 2-1.4: SerialNumber: 20111102-00000001
Oct  4 22:32:22 node-5 kernel: [    2.502271] acpi PNP0C0F:03: hash matches
Oct  4 22:32:22 node-5 kernel: [    2.507578] acpi device:138: hash matches
Oct  4 22:32:22 node-5 kernel: [    2.512685] acpi device:10b: hash matches
Oct  4 22:32:22 node-5 kernel: [    2.517843] rtc_cmos 00:02: setting system clock to 2016-10-04 22:31:47 UTC (1475620307)
Oct  4 22:32:22 node-5 kernel: [    2.529329] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct  4 22:32:22 node-5 kernel: [    2.534389] EDD information not available.
Oct  4 22:32:22 node-5 kernel: [    2.539402] PM: Hibernation image not present or could not be loaded.
Oct  4 22:32:22 node-5 kernel: [    2.540236] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct  4 22:32:22 node-5 kernel: [    2.550651] Write protecting the kernel read-only data: 12288k
Oct  4 22:32:22 node-5 kernel: [    2.556637] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct  4 22:32:22 node-5 kernel: [    2.568713] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct  4 22:32:22 node-5 kernel: [    2.600396] device-mapper: multipath: version 1.6.0 loaded
Oct  4 22:32:22 node-5 kernel: [    2.608192] systemd-udevd[218]: starting version 204
Oct  4 22:32:22 node-5 kernel: [    2.632977] md: linear personality registered for level -1
Oct  4 22:32:22 node-5 kernel: [    2.646265] md: multipath personality registered for level -4
Oct  4 22:32:22 node-5 kernel: [    2.654203] md: raid0 personality registered for level 0
Oct  4 22:32:22 node-5 kernel: [    2.662147] md: raid1 personality registered for level 1
Oct  4 22:32:22 node-5 kernel: [    2.670617] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct  4 22:32:22 node-5 kernel: [    2.676770] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct  4 22:32:22 node-5 kernel: [    2.676777] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct  4 22:32:22 node-5 kernel: [    2.677260] megasas: FW now in Ready state
Oct  4 22:32:22 node-5 kernel: [    2.677327] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677363] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677403] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677441] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677474] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677512] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677546] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677582] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677614] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677653] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677694] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677729] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677765] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677803] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677841] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.677876] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.678086] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct  4 22:32:22 node-5 kernel: [    2.707427] hidraw: raw HID events driver (C) Jiri Kosina
Oct  4 22:32:22 node-5 kernel: [    2.715284] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Oct  4 22:32:22 node-5 kernel: [    2.728198] 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  4 22:32:22 node-5 kernel: [    2.738002] raid6: sse2x1    7358 MB/s
Oct  4 22:32:22 node-5 kernel: [    2.748639] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  4 22:32:22 node-5 kernel: [    2.755524] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.755532] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.755537] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.755541] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.755578] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  4 22:32:22 node-5 kernel: [    2.770094] usbcore: registered new interface driver usbhid
Oct  4 22:32:22 node-5 kernel: [    2.776696] usbhid: USB HID core driver
Oct  4 22:32:22 node-5 kernel: [    2.779733] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Oct  4 22:32:22 node-5 kernel: [    2.779756] 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  4 22:32:22 node-5 kernel: [    2.779799] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct  4 22:32:22 node-5 kernel: [    2.806208] raid6: sse2x2     874 MB/s
Oct  4 22:32:22 node-5 kernel: [    2.873848] raid6: sse2x4    8418 MB/s
Oct  4 22:32:22 node-5 kernel: [    2.945787] raid6: avx2x1   14946 MB/s
Oct  4 22:32:22 node-5 kernel: [    3.017727] raid6: avx2x2   18892 MB/s
Oct  4 22:32:22 node-5 kernel: [    3.089665] raid6: avx2x4   21226 MB/s
Oct  4 22:32:22 node-5 kernel: [    3.095565] raid6: using algorithm avx2x4 (21226 MB/s)
Oct  4 22:32:22 node-5 kernel: [    3.101474] raid6: using avx2x2 recovery algorithm
Oct  4 22:32:22 node-5 kernel: [    3.107488] megasas:IOC Init cmd success
Oct  4 22:32:22 node-5 kernel: [    3.107490] Switched to clocksource tsc
Oct  4 22:32:22 node-5 kernel: [    3.108135] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.108206] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.108255] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.108346] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.108424] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.108518] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.108932] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.126382] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Oct  4 22:32:22 node-5 kernel: [    3.126393] 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  4 22:32:22 node-5 kernel: [    3.126414] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  4 22:32:22 node-5 kernel: [    3.126633] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.126724] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.126783] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.126859] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.127171] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.142519] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Oct  4 22:32:22 node-5 kernel: [    3.142523] 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  4 22:32:22 node-5 kernel: [    3.142548] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  4 22:32:22 node-5 kernel: [    3.142827] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.142890] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.143050] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.143115] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.143421] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  4 22:32:22 node-5 kernel: [    3.215552] xor: automatically using best checksumming function:
Oct  4 22:32:22 node-5 kernel: [    3.221750] 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  4 22:32:22 node-5 kernel: [    3.233897] 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  4 22:32:22 node-5 kernel: [    3.238053] megasas: INIT adapter done
Oct  4 22:32:22 node-5 kernel: [    3.252486] 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  4 22:32:22 node-5 kernel: [    3.261498]    avx       : 35726.000 MB/sec
Oct  4 22:32:22 node-5 kernel: [    3.272733] 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  4 22:32:22 node-5 kernel: [    3.287060] async_tx: api initialized (async)
Oct  4 22:32:22 node-5 kernel: [    3.287067] 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  4 22:32:22 node-5 kernel: [    3.287112] 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  4 22:32:22 node-5 kernel: [    3.309465] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct  4 22:32:22 node-5 kernel: [    3.309833] scsi0 : LSI SAS based MegaRAID driver
Oct  4 22:32:22 node-5 kernel: [    3.317065] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  4 22:32:22 node-5 kernel: [    3.328469] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  4 22:32:22 node-5 kernel: [    3.332655] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct  4 22:32:22 node-5 kernel: [    3.332776] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct  4 22:32:22 node-5 kernel: [    3.333081] sd 0:2:0:0: [sda] Write Protect is off
Oct  4 22:32:22 node-5 kernel: [    3.333082] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct  4 22:32:22 node-5 kernel: [    3.333145] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct  4 22:32:22 node-5 kernel: [    3.365220]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct  4 22:32:22 node-5 kernel: [    3.365827] sd 0:2:0:0: [sda] Attached SCSI disk
Oct  4 22:32:22 node-5 kernel: [    3.430176] md: raid6 personality registered for level 6
Oct  4 22:32:22 node-5 kernel: [    3.437331] md: raid5 personality registered for level 5
Oct  4 22:32:22 node-5 kernel: [    3.444244] md: raid4 personality registered for level 4
Oct  4 22:32:22 node-5 kernel: [    3.453970] md: raid10 personality registered for level 10
Oct  4 22:32:22 node-5 kernel: [    3.507120] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Oct  4 22:32:22 node-5 kernel: [    3.557427] random: lvm urandom read with 30 bits of entropy available
Oct  4 22:32:22 node-5 kernel: [    3.701594] bio: create slab <bio-1> at 1
Oct  4 22:32:22 node-5 kernel: [    4.516551] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Oct  4 22:32:22 node-5 kernel: [    5.105580] init: plymouth-upstart-bridge main process (570) terminated with status 1
Oct  4 22:32:22 node-5 kernel: [    5.117948] init: plymouth-upstart-bridge main process ended, respawning
Oct  4 22:32:22 node-5 kernel: [    5.238409] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Oct  4 22:32:22 node-5 kernel: [    5.308055] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct  4 22:32:22 node-5 kernel: [    5.348216] random: nonblocking pool is initialized
Oct  4 22:32:22 node-5 kernel: [    5.515873] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct  4 22:32:22 node-5 kernel: [    5.551814] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct  4 22:32:22 node-5 kernel: [    5.609482] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct  4 22:32:22 node-5 kernel: [    5.752136] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct  4 22:32:22 node-5 kernel: [    5.785848] XFS (dm-1): Mounting Filesystem
Oct  4 22:32:22 node-5 kernel: [    5.994257] XFS (dm-1): Ending clean mount
Oct  4 22:32:22 node-5 kernel: [    6.052715] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct  4 22:32:22 node-5 kernel: [    6.089435] XFS (dm-2): Mounting Filesystem
Oct  4 22:32:22 node-5 kernel: [    6.229452] XFS (dm-2): Ending clean mount
Oct  4 22:32:22 node-5 kernel: [    6.355420] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Oct  4 22:32:22 node-5 kernel: [    8.312537] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  4 22:32:22 node-5 kernel: [    8.326926] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  4 22:32:22 node-5 kernel: [    8.487921] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  4 22:32:22 node-5 kernel: [    8.487926] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  4 22:32:22 node-5 kernel: [    8.487930] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct  4 22:32:22 node-5 kernel: [    8.487935] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct  4 22:32:22 node-5 kernel: [    8.510603] systemd-udevd[801]: starting version 204
Oct  4 22:32:22 node-5 kernel: [    8.723541] IPMI System Interface driver.
Oct  4 22:32:22 node-5 kernel: [    8.723584] ipmi_si: probing via ACPI
Oct  4 22:32:22 node-5 kernel: [    8.723599] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct  4 22:32:22 node-5 kernel: [    8.723601] ipmi_si: Adding ACPI-specified kcs state machine
Oct  4 22:32:22 node-5 kernel: [    8.723610] ipmi_si: probing via SMBIOS
Oct  4 22:32:22 node-5 kernel: [    8.723611] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct  4 22:32:22 node-5 kernel: [    8.723612] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct  4 22:32:22 node-5 kernel: [    8.723614] ipmi_si: probing via SPMI
Oct  4 22:32:22 node-5 kernel: [    8.723614] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct  4 22:32:22 node-5 kernel: [    8.723615] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct  4 22:32:22 node-5 kernel: [    8.723616] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct  4 22:32:22 node-5 kernel: [    8.731491] power_meter ACPI000D:00: Found ACPI power meter.
Oct  4 22:32:22 node-5 kernel: [    8.731500] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct  4 22:32:22 node-5 kernel: [    8.739405] wmi: Mapper loaded
Oct  4 22:32:22 node-5 kernel: [    8.752135] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct  4 22:32:22 node-5 kernel: [    8.752140] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  4 22:32:22 node-5 kernel: [    8.752142] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct  4 22:32:22 node-5 kernel: [    8.752144] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  4 22:32:22 node-5 kernel: [    8.752161] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct  4 22:32:22 node-5 kernel: [    8.757196] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct  4 22:32:22 node-5 kernel: [    8.833251] systemd-udevd[848]: renamed network interface eth1 to enp7s0
Oct  4 22:32:22 node-5 kernel: [    8.869346] systemd-udevd[819]: renamed network interface eth0 to enp6s0
Oct  4 22:32:22 node-5 kernel: [    8.895529] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct  4 22:32:22 node-5 kernel: [    8.895538] ipmi_si 00:09: IPMI kcs interface initialized
Oct  4 22:32:22 node-5 kernel: [    8.909131] systemd-udevd[851]: renamed network interface eth2 to enp8s0
Oct  4 22:32:22 node-5 kernel: [    8.949084] systemd-udevd[818]: renamed network interface eth3 to enp9s0
Oct  4 22:32:22 node-5 kernel: [    9.201648] type=1400 audit(1475620314.184:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1078 comm="apparmor_parser"
Oct  4 22:32:22 node-5 kernel: [    9.201797] type=1400 audit(1475620314.184:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1078 comm="apparmor_parser"
Oct  4 22:32:22 node-5 kernel: [    9.201922] type=1400 audit(1475620314.184:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1078 comm="apparmor_parser"
Oct  4 22:32:22 node-5 kernel: [    9.202315] type=1400 audit(1475620314.184:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1059 comm="apparmor_parser"
Oct  4 22:32:22 node-5 kernel: [    9.202465] type=1400 audit(1475620314.184:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1059 comm="apparmor_parser"
Oct  4 22:32:22 node-5 kernel: [    9.202585] type=1400 audit(1475620314.184:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1059 comm="apparmor_parser"
Oct  4 22:32:22 node-5 kernel: [    9.203504] type=1400 audit(1475620314.184:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1100 comm="apparmor_parser"
Oct  4 22:32:22 node-5 kernel: [    9.203647] type=1400 audit(1475620314.184:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1100 comm="apparmor_parser"
Oct  4 22:32:22 node-5 kernel: [    9.203768] type=1400 audit(1475620314.184:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1100 comm="apparmor_parser"
Oct  4 22:32:22 node-5 kernel: [    9.208156] type=1400 audit(1475620314.188:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1083 comm="apparmor_parser"
Oct  4 22:32:22 node-5 kernel: [    9.832435] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  4 22:32:22 node-5 kernel: [    9.845100] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  4 22:32:22 node-5 kernel: [   10.157489] enic 0000:06:00.0 enp6s0: Link UP
Oct  4 22:32:22 node-5 kernel: [   10.157902] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct  4 22:32:22 node-5 kernel: [   10.157915] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct  4 22:32:22 node-5 kernel: [   20.158234] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct  4 22:32:23 node-5 failsafe: Failsafe of 120 seconds reached.
Oct  4 22:32:23 node-5 kernel: [   38.500170] init: failsafe main process (8461) killed by TERM signal
Oct  4 22:32:23 node-5 dbus[8500]: [system] AppArmor D-Bus mediation is enabled
Oct  4 22:32:24 node-5 kernel: [   38.751957] audit_printk_skb: 30 callbacks suppressed
Oct  4 22:32:24 node-5 kernel: [   38.751959] type=1400 audit(1475620344.198:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8587 comm="apparmor_parser"
Oct  4 22:32:24 node-5 kernel: [   38.752174] type=1400 audit(1475620344.198:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8586 comm="apparmor_parser"
Oct  4 22:32:24 node-5 kernel: [   38.752179] type=1400 audit(1475620344.198:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8586 comm="apparmor_parser"
Oct  4 22:32:24 node-5 kernel: [   38.752182] type=1400 audit(1475620344.198:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8586 comm="apparmor_parser"
Oct  4 22:32:24 node-5 kernel: [   38.752424] type=1400 audit(1475620344.198:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8586 comm="apparmor_parser"
Oct  4 22:32:24 node-5 kernel: [   38.752426] type=1400 audit(1475620344.198:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8586 comm="apparmor_parser"
Oct  4 22:32:24 node-5 kernel: [   38.752551] type=1400 audit(1475620344.198:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8586 comm="apparmor_parser"
Oct  4 22:32:24 node-5 kernel: [   38.847450] type=1400 audit(1475620344.294:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8589 comm="apparmor_parser"
Oct  4 22:32:24 node-5 anacron[8656]: Anacron 2.3 started on 2016-10-04
Oct  4 22:32:24 node-5 anacron[8656]: Will run job `cron.daily' in 5 min.
Oct  4 22:32:24 node-5 anacron[8656]: Will run job `cron.weekly' in 10 min.
Oct  4 22:32:24 node-5 anacron[8656]: Will run job `cron.monthly' in 15 min.
Oct  4 22:32:24 node-5 anacron[8656]: Jobs will be executed sequentially
Oct  4 22:32:24 node-5 cron[8620]: (CRON) INFO (pidfile fd = 3)
Oct  4 22:32:24 node-5 multipathd: path checkers start up
Oct  4 22:32:24 node-5 cron[8690]: (CRON) STARTUP (fork ok)
Oct  4 22:32:24 node-5 cron[8690]: (CRON) INFO (Running @reboot jobs)
Oct  4 22:32:24 node-5 postfix/master[8798]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct  4 22:32:28 node-5 puppet-agent[8982]: Reopening log files
Oct  4 22:32:29 node-5 puppet-agent[8982]: Could not request certificate: Connection refused - connect(2)
Oct  4 22:32:42 node-5 puppet-user[9190]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct  4 22:32:42 node-5 puppet-user[9190]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Oct  4 22:32:42 node-5 puppet-user[9190]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct  4 22:32:42 node-5 puppet-user[9190]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct  4 22:32:42 node-5 puppet-user[9190]: Finished catalog run in 0.42 seconds
Oct  4 22:32:44 node-5 multipathd: uevent trigger error
Oct  4 22:32:44 node-5 puppet-user[9620]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  4 22:32:44 node-5 puppet-user[9620]: Compiled catalog for node-5.domain.tld in environment production in 0.08 seconds
Oct  4 22:32:44 node-5 puppet-user[9620]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct  4 22:32:44 node-5 puppet-user[9620]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct  4 22:32:44 node-5 puppet-user[9620]: (/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  4 22:32:44 node-5 puppet-user[9620]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct  4 22:32:44 node-5 puppet-user[9620]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct  4 22:32:44 node-5 puppet-user[9620]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct  4 22:32:44 node-5 puppet-user[9620]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct  4 22:32:44 node-5 puppet-user[9620]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct  4 22:32:44 node-5 puppet-user[9620]: Finished catalog run in 0.05 seconds
Oct  4 22:32:46 node-5 puppet-user[10088]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct  4 22:32:46 node-5 puppet-user[10088]: Compiled catalog for node-5.domain.tld in environment production in 0.07 seconds
Oct  4 22:32:46 node-5 puppet-user[10088]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct  4 22:32:46 node-5 puppet-user[10088]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct  4 22:32:46 node-5 puppet-user[10088]: Finished catalog run in 0.03 seconds
Oct  4 22:32:48 node-5 puppet-user[10735]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct  4 22:32:48 node-5 puppet-user[10735]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Oct  4 22:32:48 node-5 puppet-user[10735]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct  4 22:32:48 node-5 puppet-user[10735]: Finished catalog run in 0.04 seconds
Oct  4 22:32:50 node-5 puppet-user[11202]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct  4 22:32:50 node-5 puppet-user[11202]: Compiled catalog for node-5.domain.tld in environment production in 0.18 seconds
Oct  4 22:32:50 node-5 puppet-user[11202]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct  4 22:32:50 node-5 kernel: [   64.969218] nr_pdflush_threads exported in /proc is scheduled for removal
Oct  4 22:32:50 node-5 kernel: [   64.969269] 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  4 22:32:50 node-5 puppet-user[11202]: (/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  4 22:32:50 node-5 puppet-user[11202]: Finished catalog run in 0.05 seconds
Oct  4 22:32:52 node-5 puppet-user[11655]: (Scope(Class[main])) MODULAR: sync_time
Oct  4 22:32:52 node-5 puppet-user[11655]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Oct  4 22:32:52 node-5 ntpdate[12077]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Oct  4 22:32:58 node-5 kernel: [   72.863226] init: plymouth-upstart-bridge main process ended, respawning
Oct  4 22:32:58 node-5 ntpdate[12077]: adjust time server 10.20.0.2 offset -0.214498 sec
Oct  4 22:32:58 node-5 puppet-user[11655]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct  4 22:32:58 node-5 puppet-user[11655]: Finished catalog run in 6.20 seconds
Oct  4 22:32:58 node-5 puppet-agent[8982]: Could not run: SIGTERM
Oct  4 22:32:58 node-5 kernel: [   73.309510] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct  4 22:32:58 node-5 ec2: 
Oct  4 22:32:58 node-5 ec2: #############################################################
Oct  4 22:32:58 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct  4 22:32:58 node-5 ec2: 1024 e7:ef:fa:af:1c:13:c4:3c:9e:23:15:16:15:41:fb:ba  root@node-5.domain.tld (DSA)
Oct  4 22:32:58 node-5 ec2: 256 5c:09:b8:62:e2:d1:e8:d9:3c:de:a0:4a:65:6e:74:df  root@node-5.domain.tld (ECDSA)
Oct  4 22:32:58 node-5 ec2: 256 b2:42:03:c4:d2:d4:91:1c:00:a8:ca:52:f0:98:7d:c8  root@node-5.domain.tld (ED25519)
Oct  4 22:32:58 node-5 ec2: 2048 64:23:73:2f:23:79:65:23:11:a9:28:b6:9e:ba:4f:46  root@node-5.domain.tld (RSA)
Oct  4 22:32:58 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct  4 22:32:58 node-5 ec2: #############################################################
Oct  4 22:33:01 node-5 CRON[12404]: (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  4 22:33:04 node-5 puppet-user[12461]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  4 22:33:04 node-5 puppet-user[12461]: Compiled catalog for node-5.domain.tld in environment production in 0.10 seconds
Oct  4 22:33:04 node-5 puppet-user[12461]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct  4 22:33:04 node-5 puppet-user[12461]: Finished catalog run in 0.08 seconds
Oct  4 22:33:05 node-5 puppet-user[12919]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct  4 22:33:06 node-5 puppet-user[12919]: Compiled catalog for node-5.domain.tld in environment production in 0.49 seconds
Oct  4 22:33:06 node-5 puppet-user[12919]: (/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  4 22:33:06 node-5 puppet-user[12919]: (/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  4 22:33:06 node-5 puppet-user[12919]: (/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  4 22:33:06 node-5 puppet-user[12919]: (/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  4 22:33:06 node-5 puppet-user[12919]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct  4 22:33:06 node-5 puppet-user[12919]: (/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  4 22:33:06 node-5 puppet-user[12919]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct  4 22:33:06 node-5 puppet-user[12919]: (/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  4 22:33:06 node-5 puppet-user[12919]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct  4 22:33:06 node-5 puppet-user[12919]: (/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  4 22:33:06 node-5 puppet-user[12919]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct  4 22:33:06 node-5 puppet-user[12919]: (/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  4 22:33:07 node-5 puppet-user[12919]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct  4 22:33:07 node-5 puppet-user[12919]: Finished catalog run in 0.83 seconds
Oct  4 22:33:08 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  4 22:33:08 node-5 nailgun-agent: I, [2016-10-04T22:33:08.749598 #12407]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  4 22:33:08 node-5 puppet-user[13430]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct  4 22:33:08 node-5 puppet-user[13430]: Compiled catalog for node-5.domain.tld in environment production in 0.11 seconds
Oct  4 22:33:12 node-5 puppet-user[13430]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct  4 22:33:21 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  4 22:33:21 node-5 nailgun-agent: I, [2016-10-04T22:33:21.456675 #12407]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Oct  4 22:33:42 node-5 puppet-user[13430]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct  4 22:33:42 node-5 puppet-user[13430]: Finished catalog run in 33.60 seconds
Oct  4 22:33:44 node-5 puppet-user[16292]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct  4 22:33:45 node-5 puppet-user[16292]: Compiled catalog for node-5.domain.tld in environment production in 0.63 seconds
Oct  4 22:33:45 node-5 puppet-user[16292]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct  4 22:33:45 node-5 puppet-user[16292]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct  4 22:33:45 node-5 puppet-user[16292]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct  4 22:33:45 node-5 puppet-user[16292]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct  4 22:33:45 node-5 puppet-user[16292]: Finished catalog run in 0.17 seconds
Oct  4 22:33:47 node-5 puppet-user[16771]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct  4 22:33:47 node-5 puppet-user[16771]: Compiled catalog for node-5.domain.tld in environment production in 0.83 seconds
Oct  4 22:33:48 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct  4 22:33:48 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct  4 22:33:48 node-5 crontab[17207]: (root) LIST (root)
Oct  4 22:33:48 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct  4 22:33:48 node-5 crontab[17208]: (root) REPLACE (root)
Oct  4 22:33:49 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/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  4 22:33:50 node-5 puppet-user[16771]: (/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  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/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  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct  4 22:33:50 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/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  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/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  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/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  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/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  4 22:33:51 node-5 puppet-user[16771]: (/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  4 22:33:51 node-5 puppet-user[16771]: (/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  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/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  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/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  4 22:33:51 node-5 puppet-user[16771]: (/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  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct  4 22:33:51 node-5 puppet-user[16771]: (/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  4 22:33:51 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8434" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  4 22:33:51 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct  4 22:33:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:33:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:33:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:33:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:33:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:33:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:34:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:34:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:34:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:34:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:34:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:02 node-5 ntpdate[27633]: no servers can be used, exiting
<27>Oct  4 22:35:02 node-5 ntpdate[27742]: no servers can be used, exiting
<27>Oct  4 22:35:02 node-5 ntpdate[27958]: no servers can be used, exiting
<27>Oct  4 22:35:34 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:34 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:34 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:34 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:34 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:34 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:36 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:36 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:36 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:36 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:36 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:50 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:50 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:50 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:50 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:50 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:50 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:53 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:58 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:58 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:58 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:58 node-5 multipathd: uevent trigger error
<27>Oct  4 22:35:58 node-5 multipathd: uevent trigger error
<27>Oct  4 22:36:39 node-5 multipathd: uevent trigger error
<27>Oct  4 22:36:39 node-5 multipathd: uevent trigger error
<27>Oct  4 22:36:39 node-5 multipathd: uevent trigger error
<27>Oct  4 22:36:39 node-5 multipathd: uevent trigger error
<27>Oct  4 22:36:39 node-5 multipathd: uevent trigger error
<43>Oct  4 22:36:51 node-5 apache2_error [Tue Oct 04 22:36:51.067913 2016] [mpm_event:notice] [pid 7885:tid 140119973640064] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  4 22:36:51 node-5 apache2_error [Tue Oct 04 22:36:51.068073 2016] [core:notice] [pid 7885:tid 140119973640064] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  4 22:36:59 node-5 multipathd: uevent trigger error
<27>Oct  4 22:36:59 node-5 multipathd: uevent trigger error
<27>Oct  4 22:36:59 node-5 multipathd: uevent trigger error
<27>Oct  4 22:36:59 node-5 multipathd: uevent trigger error
<27>Oct  4 22:36:59 node-5 multipathd: uevent trigger error
<27>Oct  4 22:36:59 node-5 multipathd: uevent trigger error
<43>Oct  4 22:37:01 node-5 apache2_error [Tue Oct 04 22:36:54.158929 2016] [mpm_event:notice] [pid 7885:tid 140119973640064] AH00491: caught SIGTERM, shutting down
<43>Oct  4 22:37:01 node-5 apache2_error [Tue Oct 04 22:36:55.253181 2016] [mpm_worker:notice] [pid 8221:tid 140373197518720] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  4 22:37:01 node-5 apache2_error [Tue Oct 04 22:36:55.253234 2016] [core:notice] [pid 8221:tid 140373197518720] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  4 22:37:32 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Oct  4 22:37:37 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:37 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:37 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:37 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:37 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:37 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:41 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:41 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:41 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:41 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:41 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:41 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:48 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:48 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:48 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:48 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:48 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:48 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:37:55 node-5 multipathd: uevent trigger error
<129>Oct  4 22:37:59 node-5 haproxy[18883]: 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  4 22:38:01 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:01 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:01 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:01 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:01 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:01 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:04 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:04 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:04 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:04 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:04 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:04 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:04 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:04 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:07 node-5 haproxy[21029]: 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  4 22:38:08 node-5 haproxy[21029]: 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  4 22:38:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:09 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:12 node-5 haproxy[22170]: 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  4 22:38:13 node-5 haproxy[22170]: 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  4 22:38:13 node-5 haproxy[22170]: 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  4 22:38:14 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:14 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:14 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:14 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:14 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:17 node-5 haproxy[23434]: 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  4 22:38:17 node-5 haproxy[23434]: 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  4 22:38:18 node-5 haproxy[23438]: 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  4 22:38:18 node-5 haproxy[23438]: 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  4 22:38:19 node-5 haproxy[23438]: 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  4 22:38:20 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:20 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:20 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:20 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:20 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:20 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:22 node-5 haproxy[24559]: 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  4 22:38:22 node-5 haproxy[24559]: 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  4 22:38:23 node-5 haproxy[24568]: 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  4 22:38:23 node-5 haproxy[24568]: 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  4 22:38:23 node-5 haproxy[24568]: 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  4 22:38:24 node-5 haproxy[24568]: 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  4 22:38:25 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:25 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:25 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:25 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:25 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:25 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:26 node-5 haproxy[24568]: Server aodh/node-1 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  4 22:38:26 node-5 haproxy[24568]: 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  4 22:38:26 node-5 haproxy[24568]: proxy aodh has no server available!
<129>Oct  4 22:38:27 node-5 haproxy[25868]: 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  4 22:38:28 node-5 haproxy[25883]: 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  4 22:38:28 node-5 haproxy[25883]: 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  4 22:38:28 node-5 haproxy[25883]: 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  4 22:38:29 node-5 haproxy[25883]: 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  4 22:38:29 node-5 haproxy[25883]: 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  4 22:38:29 node-5 haproxy[25883]: 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  4 22:38:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:30 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:31 node-5 haproxy[25883]: Server aodh/node-1 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  4 22:38:31 node-5 haproxy[25883]: 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  4 22:38:31 node-5 haproxy[25883]: proxy aodh has no server available!
<129>Oct  4 22:38:31 node-5 haproxy[25883]: Server ceilometer/node-1 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  4 22:38:31 node-5 haproxy[25883]: 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  4 22:38:31 node-5 haproxy[25883]: proxy ceilometer has no server available!
<129>Oct  4 22:38:33 node-5 haproxy[26998]: 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  4 22:38:33 node-5 haproxy[26998]: 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  4 22:38:33 node-5 haproxy[26998]: 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  4 22:38:34 node-5 haproxy[27002]: 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  4 22:38:34 node-5 haproxy[27002]: 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  4 22:38:34 node-5 haproxy[27002]: 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  4 22:38:34 node-5 haproxy[27002]: 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  4 22:38:35 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:35 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:36 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:36 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:36 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:36 node-5 haproxy[27002]: Server aodh/node-1 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  4 22:38:36 node-5 haproxy[27002]: 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  4 22:38:36 node-5 haproxy[27002]: proxy aodh has no server available!
<129>Oct  4 22:38:36 node-5 haproxy[27002]: Server ceilometer/node-1 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  4 22:38:36 node-5 haproxy[27002]: 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  4 22:38:36 node-5 haproxy[27002]: proxy ceilometer has no server available!
<129>Oct  4 22:38:38 node-5 haproxy[28114]: 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  4 22:38:38 node-5 haproxy[28114]: 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  4 22:38:39 node-5 haproxy[28118]: 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  4 22:38:39 node-5 haproxy[28118]: 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  4 22:38:39 node-5 haproxy[28118]: 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  4 22:38:39 node-5 haproxy[28118]: 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  4 22:38:40 node-5 haproxy[28118]: 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  4 22:38:40 node-5 haproxy[28118]: Server horizon/node-1 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  4 22:38:40 node-5 haproxy[28118]: 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  4 22:38:41 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:41 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:41 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:41 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:41 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:41 node-5 haproxy[28118]: Server aodh/node-1 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  4 22:38:41 node-5 haproxy[28118]: 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  4 22:38:41 node-5 haproxy[28118]: proxy aodh has no server available!
<129>Oct  4 22:38:41 node-5 haproxy[28118]: Server ceilometer/node-1 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  4 22:38:42 node-5 haproxy[28118]: 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  4 22:38:42 node-5 haproxy[28118]: proxy ceilometer has no server available!
<129>Oct  4 22:38:44 node-5 haproxy[29276]: 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  4 22:38:44 node-5 haproxy[29276]: 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  4 22:38:44 node-5 haproxy[29276]: 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  4 22:38:44 node-5 haproxy[29276]: 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  4 22:38:44 node-5 haproxy[29276]: 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  4 22:38:44 node-5 haproxy[29276]: 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  4 22:38:45 node-5 haproxy[29276]: 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  4 22:38:45 node-5 haproxy[29276]: 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  4 22:38:45 node-5 haproxy[29276]: 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  4 22:38:45 node-5 haproxy[29276]: 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  4 22:38:45 node-5 haproxy[29276]: Server horizon/node-1 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  4 22:38:45 node-5 haproxy[29276]: 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.
<129>Oct  4 22:38:46 node-5 haproxy[29276]: Server glance-registry/node-1 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  4 22:38:46 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:46 node-5 haproxy[29276]: 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  4 22:38:46 node-5 haproxy[29276]: proxy glance-registry has no server available!
<27>Oct  4 22:38:46 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:46 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:46 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:46 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:47 node-5 haproxy[29276]: Server aodh/node-1 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  4 22:38:47 node-5 haproxy[29276]: 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  4 22:38:47 node-5 haproxy[29276]: proxy aodh has no server available!
<129>Oct  4 22:38:47 node-5 haproxy[29276]: Server ceilometer/node-1 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  4 22:38:47 node-5 haproxy[29276]: 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  4 22:38:47 node-5 haproxy[29276]: proxy ceilometer has no server available!
<129>Oct  4 22:38:49 node-5 haproxy[30444]: 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  4 22:38:50 node-5 haproxy[30448]: 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  4 22:38:50 node-5 haproxy[30448]: 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  4 22:38:50 node-5 haproxy[30448]: 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  4 22:38:50 node-5 haproxy[30448]: 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  4 22:38:50 node-5 haproxy[30448]: 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.
<27>Oct  4 22:38:50 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Oct  4 22:38:50 node-5 haproxy[30448]: 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  4 22:38:50 node-5 haproxy[30448]: 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  4 22:38:51 node-5 haproxy[30448]: 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  4 22:38:51 node-5 haproxy[30448]: 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  4 22:38:51 node-5 haproxy[30448]: 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  4 22:38:51 node-5 haproxy[30448]: 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  4 22:38:51 node-5 haproxy[30448]: 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  4 22:38:51 node-5 haproxy[30448]: Server horizon/node-1 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  4 22:38:51 node-5 haproxy[30448]: 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  4 22:38:52 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:52 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:52 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:52 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:52 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:52 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:52 node-5 haproxy[30448]: Server glance-registry/node-1 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  4 22:38:52 node-5 haproxy[30448]: 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  4 22:38:52 node-5 haproxy[30448]: proxy glance-registry has no server available!
<129>Oct  4 22:38:53 node-5 haproxy[30448]: Server aodh/node-1 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  4 22:38:53 node-5 haproxy[30448]: 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  4 22:38:53 node-5 haproxy[30448]: proxy aodh has no server available!
<129>Oct  4 22:38:53 node-5 haproxy[30448]: Server ceilometer/node-1 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  4 22:38:53 node-5 haproxy[30448]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  4 22:38:53 node-5 haproxy[30448]: proxy ceilometer has no server available!
<129>Oct  4 22:38:53 node-5 haproxy[30448]: Server nova-novncproxy/node-1 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  4 22:38:53 node-5 haproxy[30448]: Server nova-novncproxy/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  4 22:38:53 node-5 haproxy[30448]: proxy nova-novncproxy has no server available!
<129>Oct  4 22:38:55 node-5 haproxy[31614]: 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  4 22:38:55 node-5 haproxy[31614]: 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  4 22:38:55 node-5 haproxy[31614]: 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  4 22:38:55 node-5 haproxy[31614]: 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  4 22:38:55 node-5 haproxy[31614]: 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  4 22:38:55 node-5 haproxy[31614]: 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  4 22:38:56 node-5 haproxy[31618]: 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  4 22:38:56 node-5 haproxy[31618]: 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  4 22:38:56 node-5 haproxy[31618]: 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  4 22:38:56 node-5 haproxy[31618]: 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  4 22:38:56 node-5 haproxy[31618]: 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  4 22:38:56 node-5 haproxy[31618]: 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  4 22:38:56 node-5 haproxy[31618]: 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  4 22:38:56 node-5 haproxy[31618]: 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  4 22:38:57 node-5 haproxy[31618]: Server horizon/node-1 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  4 22:38:57 node-5 haproxy[31618]: 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  4 22:38:58 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:58 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:58 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:58 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:58 node-5 multipathd: uevent trigger error
<27>Oct  4 22:38:58 node-5 multipathd: uevent trigger error
<129>Oct  4 22:38:58 node-5 haproxy[31618]: Server glance-registry/node-1 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  4 22:38:58 node-5 haproxy[31618]: 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  4 22:38:58 node-5 haproxy[31618]: proxy glance-registry has no server available!
<129>Oct  4 22:38:58 node-5 haproxy[31618]: Server aodh/node-1 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  4 22:38:58 node-5 haproxy[31618]: 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  4 22:38:58 node-5 haproxy[31618]: proxy aodh has no server available!
<129>Oct  4 22:38:58 node-5 haproxy[31618]: Server ceilometer/node-1 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  4 22:38:58 node-5 haproxy[31618]: 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  4 22:38:58 node-5 haproxy[31618]: proxy ceilometer has no server available!
<129>Oct  4 22:38:58 node-5 haproxy[31618]: Server nova-novncproxy/node-1 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  4 22:38:58 node-5 haproxy[31618]: Server nova-novncproxy/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  4 22:38:58 node-5 haproxy[31618]: proxy nova-novncproxy has no server available!
<129>Oct  4 22:39:00 node-5 haproxy[350]: 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  4 22:39:01 node-5 haproxy[356]: 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  4 22:39:01 node-5 haproxy[356]: 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  4 22:39:01 node-5 haproxy[356]: 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  4 22:39:01 node-5 haproxy[356]: 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  4 22:39:01 node-5 haproxy[356]: 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  4 22:39:01 node-5 haproxy[356]: 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  4 22:39:01 node-5 haproxy[356]: 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  4 22:39:01 node-5 haproxy[356]: 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  4 22:39:01 node-5 haproxy[356]: 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  4 22:39:02 node-5 haproxy[356]: 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  4 22:39:02 node-5 haproxy[356]: 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  4 22:39:02 node-5 haproxy[356]: 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  4 22:39:02 node-5 haproxy[356]: 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  4 22:39:02 node-5 haproxy[356]: 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  4 22:39:02 node-5 haproxy[356]: 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  4 22:39:02 node-5 haproxy[356]: 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  4 22:39:02 node-5 haproxy[356]: Server horizon/node-1 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  4 22:39:02 node-5 haproxy[356]: 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.
<129>Oct  4 22:39:03 node-5 haproxy[356]: Server glance-registry/node-1 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  4 22:39:03 node-5 haproxy[356]: 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  4 22:39:03 node-5 haproxy[356]: proxy glance-registry has no server available!
<27>Oct  4 22:39:03 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:03 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:03 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:03 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:03 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:03 node-5 multipathd: uevent trigger error
<129>Oct  4 22:39:04 node-5 haproxy[356]: Server aodh/node-1 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  4 22:39:04 node-5 haproxy[356]: 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  4 22:39:04 node-5 haproxy[356]: proxy aodh has no server available!
<129>Oct  4 22:39:04 node-5 haproxy[356]: Server ceilometer/node-1 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  4 22:39:04 node-5 haproxy[356]: 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  4 22:39:04 node-5 haproxy[356]: proxy ceilometer has no server available!
<129>Oct  4 22:39:04 node-5 haproxy[356]: Server nova-novncproxy/node-1 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  4 22:39:04 node-5 haproxy[356]: 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  4 22:39:04 node-5 haproxy[356]: proxy nova-novncproxy has no server available!
<27>Oct  4 22:39:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:10 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:10 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:10 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:10 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:10 node-5 multipathd: uevent trigger error
<129>Oct  4 22:39:10 node-5 haproxy[356]: Server keystone-1/node-1 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  4 22:39:10 node-5 haproxy[356]: Server keystone-1/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  4 22:39:10 node-5 haproxy[356]: proxy keystone-1 has no server available!
<129>Oct  4 22:39:10 node-5 haproxy[356]: Server keystone-2/node-1 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  4 22:39:11 node-5 haproxy[356]: 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  4 22:39:11 node-5 haproxy[356]: proxy keystone-2 has no server available!
<129>Oct  4 22:39:11 node-5 haproxy[356]: Server nova-api/node-1 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  4 22:39:11 node-5 haproxy[356]: 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  4 22:39:11 node-5 haproxy[356]: proxy nova-api has no server available!
<129>Oct  4 22:39:11 node-5 haproxy[356]: Server nova-metadata-api/node-1 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  4 22:39:11 node-5 haproxy[356]: Server nova-metadata-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  4 22:39:11 node-5 haproxy[356]: proxy nova-metadata-api has no server available!
<129>Oct  4 22:39:11 node-5 haproxy[356]: Server cinder-api/node-1 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  4 22:39:11 node-5 haproxy[356]: 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  4 22:39:11 node-5 haproxy[356]: proxy cinder-api has no server available!
<129>Oct  4 22:39:11 node-5 haproxy[356]: Server glance-api/node-1 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  4 22:39:11 node-5 haproxy[356]: 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  4 22:39:11 node-5 haproxy[356]: proxy glance-api has no server available!
<129>Oct  4 22:39:11 node-5 haproxy[356]: Server glance-glare/node-1 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  4 22:39:11 node-5 haproxy[356]: 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  4 22:39:11 node-5 haproxy[356]: proxy glance-glare has no server available!
<129>Oct  4 22:39:11 node-5 haproxy[356]: Server neutron/node-1 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  4 22:39:11 node-5 haproxy[356]: 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  4 22:39:11 node-5 haproxy[356]: proxy neutron has no server available!
<129>Oct  4 22:39:11 node-5 haproxy[356]: Server mysqld/node-1 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  4 22:39:11 node-5 haproxy[356]: 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  4 22:39:11 node-5 haproxy[356]: proxy mysqld has no server available!
<129>Oct  4 22:39:11 node-5 haproxy[356]: Server object-storage/node-1 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  4 22:39:12 node-5 haproxy[356]: Server object-storage/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  4 22:39:12 node-5 haproxy[356]: proxy object-storage has no server available!
<129>Oct  4 22:39:12 node-5 haproxy[356]: Server heat-api/node-1 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  4 22:39:12 node-5 haproxy[356]: 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  4 22:39:12 node-5 haproxy[356]: proxy heat-api has no server available!
<129>Oct  4 22:39:12 node-5 haproxy[356]: Server heat-api-cfn/node-1 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  4 22:39:12 node-5 haproxy[356]: Server heat-api-cfn/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  4 22:39:12 node-5 haproxy[356]: proxy heat-api-cfn has no server available!
<129>Oct  4 22:39:12 node-5 haproxy[356]: Server heat-api-cloudwatch/node-1 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  4 22:39:12 node-5 haproxy[356]: Server heat-api-cloudwatch/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  4 22:39:12 node-5 haproxy[356]: proxy heat-api-cloudwatch has no server available!
<27>Oct  4 22:39:44 node-5 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  4 22:39:44 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  4 22:39:47 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:47 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:47 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:47 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:47 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:51 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:51 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:51 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:51 node-5 multipathd: uevent trigger error
<27>Oct  4 22:39:51 node-5 multipathd: uevent trigger error
<43>Oct  4 22:39:51 node-5 apache2_error [Tue Oct 04 22:39:44.083441 2016] [mpm_worker:notice] [pid 8221:tid 140373197518720] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  4 22:39:51 node-5 apache2_error [Tue Oct 04 22:39:44.092744 2016] [mpm_worker:warn] [pid 8221:tid 140373197518720] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  4 22:39:51 node-5 apache2_error [Tue Oct 04 22:39:44.093487 2016] [mpm_worker:notice] [pid 8221:tid 140373197518720] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  4 22:39:51 node-5 apache2_error [Tue Oct 04 22:39:44.093499 2016] [core:notice] [pid 8221:tid 140373197518720] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  4 22:40:12 node-5 multipathd: uevent trigger error
<27>Oct  4 22:40:21 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  4 22:41:16 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  4 22:41:18 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct  4 22:42:31 node-5 multipathd: uevent trigger error
<27>Oct  4 22:42:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:42:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:42:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:42:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:42:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:42:47 node-5 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  4 22:43:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:43:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:43:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:43:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:43:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:43:55 node-5 multipathd: uevent trigger error
<27>Oct  4 22:44:01 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct  4 22:44:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:44:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:44:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:44:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:44:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:45:35 node-5 multipathd: uevent trigger error
<27>Oct  4 22:45:35 node-5 multipathd: uevent trigger error
<27>Oct  4 22:45:35 node-5 multipathd: uevent trigger error
<27>Oct  4 22:45:35 node-5 multipathd: uevent trigger error
<27>Oct  4 22:45:35 node-5 multipathd: uevent trigger error
<43>Oct  4 22:46:52 node-5 apache2_error [Tue Oct 04 22:46:44.553191 2016] [mpm_worker:notice] [pid 8221:tid 140373197518720] AH00295: caught SIGTERM, shutting down
<43>Oct  4 22:46:52 node-5 apache2_error [Tue Oct 04 22:46:45.308016 2016] [mpm_worker:notice] [pid 6855:tid 140398320969600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  4 22:46:52 node-5 apache2_error [Tue Oct 04 22:46:45.308059 2016] [core:notice] [pid 6855:tid 140398320969600] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  4 22:47:22 node-5 apache2_error [Tue Oct 04 22:47:17.197458 2016] [mpm_worker:notice] [pid 6855:tid 140398320969600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  4 22:47:22 node-5 apache2_error [Tue Oct 04 22:47:17.201860 2016] [mpm_worker:warn] [pid 6855:tid 140398320969600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  4 22:47:22 node-5 apache2_error [Tue Oct 04 22:47:17.208061 2016] [mpm_worker:notice] [pid 6855:tid 140398320969600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  4 22:47:22 node-5 apache2_error [Tue Oct 04 22:47:17.208114 2016] [core:notice] [pid 6855:tid 140398320969600] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  4 22:47:22 node-5 multipathd: uevent trigger error
<27>Oct  4 22:47:22 node-5 multipathd: uevent trigger error
<27>Oct  4 22:47:22 node-5 multipathd: uevent trigger error
<27>Oct  4 22:47:22 node-5 multipathd: uevent trigger error
<27>Oct  4 22:47:22 node-5 multipathd: uevent trigger error
<27>Oct  4 22:48:18 node-5 multipathd: uevent trigger error
<27>Oct  4 22:48:18 node-5 multipathd: uevent trigger error
<27>Oct  4 22:48:18 node-5 multipathd: uevent trigger error
<27>Oct  4 22:48:18 node-5 multipathd: uevent trigger error
<27>Oct  4 22:48:18 node-5 multipathd: uevent trigger error
<27>Oct  4 22:49:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:49:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:49:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:49:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:49:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:49:32 node-5 multipathd: uevent trigger error
<27>Oct  4 22:53:59 node-5 multipathd: uevent trigger error
<27>Oct  4 22:53:59 node-5 multipathd: uevent trigger error
<27>Oct  4 22:54:00 node-5 multipathd: uevent trigger error
<27>Oct  4 22:54:00 node-5 multipathd: uevent trigger error
<27>Oct  4 22:54:00 node-5 multipathd: uevent trigger error
<27>Oct  4 22:54:00 node-5 multipathd: uevent trigger error
<27>Oct  4 22:56:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:56:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:56:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:56:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:56:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:56:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:56:09 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:11 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:11 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:11 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:11 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:11 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:11 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:44 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:44 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:44 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:44 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:44 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:44 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:44 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:44 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:54 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:54 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:54 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:54 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:54 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:54 node-5 multipathd: uevent trigger error
<27>Oct  4 22:57:54 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:05 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct  4 22:58:05 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct  4 22:58:06 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct  4 22:58:06 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Oct  4 22:58:07 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Oct  4 22:58:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:07 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:24 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:24 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:24 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:24 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:24 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:30 node-5 multipathd: uevent trigger error
<27>Oct  4 22:58:30 node-5 multipathd: uevent trigger error
<43>Oct  4 22:59:23 node-5 apache2_error [Tue Oct 04 22:59:15.255146 2016] [mpm_worker:notice] [pid 6855:tid 140398320969600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  4 22:59:23 node-5 apache2_error [Tue Oct 04 22:59:15.641161 2016] [mpm_worker:warn] [pid 6855:tid 140398320969600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  4 22:59:23 node-5 apache2_error [Tue Oct 04 22:59:15.644874 2016] [mpm_worker:notice] [pid 6855:tid 140398320969600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  4 22:59:23 node-5 apache2_error [Tue Oct 04 22:59:15.644895 2016] [core:notice] [pid 6855:tid 140398320969600] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  4 22:59:53 node-5 apache2_error [Tue Oct 04 22:59:52.217312 2016] [mpm_worker:notice] [pid 6855:tid 140398320969600] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  4 22:59:53 node-5 apache2_error [Tue Oct 04 22:59:52.977718 2016] [mpm_worker:warn] [pid 6855:tid 140398320969600] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  4 22:59:53 node-5 apache2_error [Tue Oct 04 22:59:52.988840 2016] [mpm_worker:notice] [pid 6855:tid 140398320969600] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  4 22:59:53 node-5 apache2_error [Tue Oct 04 22:59:52.988873 2016] [core:notice] [pid 6855:tid 140398320969600] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  4 22:59:56 node-5 multipathd: uevent trigger error
<27>Oct  4 22:59:56 node-5 multipathd: uevent trigger error
<27>Oct  4 22:59:56 node-5 multipathd: uevent trigger error
<27>Oct  4 22:59:56 node-5 multipathd: uevent trigger error
<27>Oct  4 23:00:33 node-5 multipathd: uevent trigger error
<27>Oct  4 23:00:33 node-5 multipathd: uevent trigger error
<27>Oct  4 23:00:33 node-5 multipathd: uevent trigger error
<27>Oct  4 23:00:33 node-5 multipathd: uevent trigger error
<27>Oct  4 23:00:33 node-5 multipathd: uevent trigger error
<27>Oct  4 23:00:45 node-5 multipathd: uevent trigger error
<27>Oct  4 23:00:45 node-5 multipathd: uevent trigger error
<27>Oct  4 23:00:45 node-5 multipathd: uevent trigger error
<27>Oct  4 23:00:45 node-5 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-5 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-5 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-5 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-5 multipathd: uevent trigger error
<27>Oct  4 23:02:19 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:06 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:06 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:06 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:06 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:06 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:16 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:16 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:16 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:16 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:16 node-5 multipathd: uevent trigger error
<11>Oct  4 23:03:25 node-5 liberasurecode[29681]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:25 node-5 liberasurecode[29681]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:25 node-5 liberasurecode[29681]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:25 node-5 liberasurecode[29681]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:25 node-5 liberasurecode[29714]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:25 node-5 liberasurecode[29714]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:25 node-5 liberasurecode[29714]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:25 node-5 liberasurecode[29714]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:27 node-5 liberasurecode[30137]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:27 node-5 liberasurecode[30137]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:27 node-5 liberasurecode[30137]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:27 node-5 liberasurecode[30137]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30806]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30806]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30806]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30806]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30847]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30847]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30847]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30847]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30914]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30914]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30914]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30914]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30984]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30984]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30984]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:31 node-5 liberasurecode[30984]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[30998]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[30998]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[30998]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[30998]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[31035]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[31035]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[31035]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[31035]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[31021]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[31021]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[31021]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:03:32 node-5 liberasurecode[31021]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  4 23:03:38 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:38 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:38 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:38 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:38 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:43 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:43 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:43 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:43 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:43 node-5 multipathd: uevent trigger error
<27>Oct  4 23:03:43 node-5 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-5 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-5 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-5 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-5 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-5 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-5 multipathd: uevent trigger error
<27>Oct  4 23:04:48 node-5 multipathd: uevent trigger error
<11>Oct  4 23:05:01 node-5 liberasurecode[14744]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:05:01 node-5 liberasurecode[14744]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:05:01 node-5 liberasurecode[14744]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:05:01 node-5 liberasurecode[14744]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  4 23:06:56 node-5 multipathd: uevent trigger error
<27>Oct  4 23:06:56 node-5 multipathd: uevent trigger error
<27>Oct  4 23:06:56 node-5 multipathd: uevent trigger error
<27>Oct  4 23:06:56 node-5 multipathd: uevent trigger error
<27>Oct  4 23:06:56 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:02 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:02 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:02 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:02 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:15 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:19 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:19 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:19 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:19 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:33 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:33 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:33 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:33 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:33 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:40 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:40 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:40 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:40 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:40 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:40 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:44 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:44 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:44 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:44 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:44 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:49 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:49 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:49 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:49 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:49 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:49 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:54 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:54 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:54 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:54 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:54 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:54 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:59 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:59 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:59 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:59 node-5 multipathd: uevent trigger error
<27>Oct  4 23:07:59 node-5 multipathd: uevent trigger error
<27>Oct  4 23:08:03 node-5 multipathd: uevent trigger error
<27>Oct  4 23:08:03 node-5 multipathd: uevent trigger error
<27>Oct  4 23:08:03 node-5 multipathd: uevent trigger error
<27>Oct  4 23:08:03 node-5 multipathd: uevent trigger error
<27>Oct  4 23:08:03 node-5 multipathd: uevent trigger error
<27>Oct  4 23:08:37 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  4 23:08:37 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Oct  4 23:10:01 node-5 liberasurecode[3332]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:10:01 node-5 liberasurecode[3332]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:10:01 node-5 liberasurecode[3332]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  4 23:10:01 node-5 liberasurecode[3332]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
