Oct  8 18:02:28 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8384" x-info="http://www.rsyslog.com"] start
Oct  8 18:02:28 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct  8 18:02:28 node-4 rsyslogd: rsyslogd's groupid changed to 104
Oct  8 18:02:28 node-4 rsyslogd: rsyslogd's userid changed to 101
Oct  8 18:02:28 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct  8 18:02:28 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct  8 18:02:28 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct  8 18:02:28 node-4 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  8 18:02:28 node-4 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=5c5df0ad-046e-4ac5-9606-180b017ab4ac nomdmonddf nomdmonisw
Oct  8 18:02:28 node-4 kernel: [    0.000000] KERNEL supported cpus:
Oct  8 18:02:28 node-4 kernel: [    0.000000]   Intel GenuineIntel
Oct  8 18:02:28 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Oct  8 18:02:28 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Oct  8 18:02:28 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct  8 18:02:28 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct  8 18:02:28 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct  8 18:02:28 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Oct  8 18:02:28 node-4 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Oct  8 18:02:28 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct  8 18:02:28 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct  8 18:02:28 node-4 kernel: [    0.000000] No AGP bridge found
Oct  8 18:02:28 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct  8 18:02:28 node-4 kernel: [    0.000000] MTRR default type: write-back
Oct  8 18:02:28 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct  8 18:02:28 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Oct  8 18:02:28 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct  8 18:02:28 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct  8 18:02:28 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Oct  8 18:02:28 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct  8 18:02:28 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct  8 18:02:28 node-4 kernel: [    0.000000]   2 disabled
Oct  8 18:02:28 node-4 kernel: [    0.000000]   3 disabled
Oct  8 18:02:28 node-4 kernel: [    0.000000]   4 disabled
Oct  8 18:02:28 node-4 kernel: [    0.000000]   5 disabled
Oct  8 18:02:28 node-4 kernel: [    0.000000]   6 disabled
Oct  8 18:02:28 node-4 kernel: [    0.000000]   7 disabled
Oct  8 18:02:28 node-4 kernel: [    0.000000]   8 disabled
Oct  8 18:02:28 node-4 kernel: [    0.000000]   9 disabled
Oct  8 18:02:28 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct  8 18:02:28 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct  8 18:02:28 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct  8 18:02:28 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct  8 18:02:28 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct  8 18:02:28 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Oct  8 18:02:28 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct  8 18:02:28 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct  8 18:02:28 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct  8 18:02:28 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct  8 18:02:28 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct  8 18:02:28 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct  8 18:02:28 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct  8 18:02:28 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct  8 18:02:28 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct  8 18:02:28 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct  8 18:02:28 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct  8 18:02:28 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct  8 18:02:28 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct  8 18:02:28 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct  8 18:02:28 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct  8 18:02:28 node-4 kernel: [    0.000000] Zone ranges:
Oct  8 18:02:28 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] Movable zone start for each node
Oct  8 18:02:28 node-4 kernel: [    0.000000] Early memory node ranges
Oct  8 18:02:28 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct  8 18:02:28 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct  8 18:02:28 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct  8 18:02:28 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct  8 18:02:28 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct  8 18:02:28 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct  8 18:02:28 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct  8 18:02:28 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct  8 18:02:28 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct  8 18:02:28 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct  8 18:02:28 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct  8 18:02:28 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct  8 18:02:28 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct  8 18:02:28 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct  8 18:02:28 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct  8 18:02:28 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct  8 18:02:28 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct  8 18:02:28 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct  8 18:02:28 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct  8 18:02:28 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct  8 18:02:28 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct  8 18:02:28 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct  8 18:02:28 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct  8 18:02:28 node-4 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Oct  8 18:02:28 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct  8 18:02:28 node-4 kernel: [    0.000000] Policy zone: Normal
Oct  8 18:02:28 node-4 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=5c5df0ad-046e-4ac5-9606-180b017ab4ac nomdmonddf nomdmonisw
Oct  8 18:02:28 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct  8 18:02:28 node-4 kernel: [    0.000000] Checking aperture...
Oct  8 18:02:28 node-4 kernel: [    0.000000] No AGP bridge found
Oct  8 18:02:28 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct  8 18:02:28 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct  8 18:02:28 node-4 kernel: [    0.000000] Memory: 32653312K/33280496K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Oct  8 18:02:28 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct  8 18:02:28 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Oct  8 18:02:28 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct  8 18:02:28 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct  8 18:02:28 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct  8 18:02:28 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct  8 18:02:28 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct  8 18:02:28 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Oct  8 18:02:28 node-4 kernel: [    0.000000] console [tty0] enabled
Oct  8 18:02:28 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct  8 18:02:28 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct  8 18:02:28 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct  8 18:02:28 node-4 kernel: [    0.000000] hpet clockevent registered
Oct  8 18:02:28 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct  8 18:02:28 node-4 kernel: [    0.004000] tsc: Detected 3492.165 MHz processor
Oct  8 18:02:28 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.33 BogoMIPS (lpj=13968660)
Oct  8 18:02:28 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct  8 18:02:28 node-4 kernel: [    0.000045] Security Framework initialized
Oct  8 18:02:28 node-4 kernel: [    0.000064] AppArmor: AppArmor initialized
Oct  8 18:02:28 node-4 kernel: [    0.000066] Yama: becoming mindful.
Oct  8 18:02:28 node-4 kernel: [    0.001456] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.006342] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.008275] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.008303] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.008593] Initializing cgroup subsys memory
Oct  8 18:02:28 node-4 kernel: [    0.008600] Initializing cgroup subsys devices
Oct  8 18:02:28 node-4 kernel: [    0.008602] Initializing cgroup subsys freezer
Oct  8 18:02:28 node-4 kernel: [    0.008604] Initializing cgroup subsys blkio
Oct  8 18:02:28 node-4 kernel: [    0.008605] Initializing cgroup subsys perf_event
Oct  8 18:02:28 node-4 kernel: [    0.008608] Initializing cgroup subsys hugetlb
Oct  8 18:02:28 node-4 kernel: [    0.008627] CPU: Physical Processor ID: 0
Oct  8 18:02:28 node-4 kernel: [    0.008628] CPU: Processor Core ID: 0
Oct  8 18:02:28 node-4 kernel: [    0.008632] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct  8 18:02:28 node-4 kernel: [    0.008632] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct  8 18:02:28 node-4 kernel: [    0.009326] mce: CPU supports 22 MCE banks
Oct  8 18:02:28 node-4 kernel: [    0.009353] CPU0: Thermal monitoring enabled (TM1)
Oct  8 18:02:28 node-4 kernel: [    0.009374] process: using mwait in idle threads
Oct  8 18:02:28 node-4 kernel: [    0.009377] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct  8 18:02:28 node-4 kernel: [    0.009377] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct  8 18:02:28 node-4 kernel: [    0.009377] tlb_flushall_shift: 6
Oct  8 18:02:28 node-4 kernel: [    0.009467] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct  8 18:02:28 node-4 kernel: [    0.010189] ACPI: Core revision 20131115
Oct  8 18:02:28 node-4 kernel: [    0.022865] ACPI: All ACPI Tables successfully acquired
Oct  8 18:02:28 node-4 kernel: [    0.023023] ftrace: allocating 28614 entries in 112 pages
Oct  8 18:02:28 node-4 kernel: [    0.031727] dmar: Host address width 46
Oct  8 18:02:28 node-4 kernel: [    0.031730] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct  8 18:02:28 node-4 kernel: [    0.031736] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  8 18:02:28 node-4 kernel: [    0.031737] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct  8 18:02:28 node-4 kernel: [    0.031741] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  8 18:02:28 node-4 kernel: [    0.031743] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct  8 18:02:28 node-4 kernel: [    0.031744] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct  8 18:02:28 node-4 kernel: [    0.031745] dmar: ATSR flags: 0x0
Oct  8 18:02:28 node-4 kernel: [    0.031746] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct  8 18:02:28 node-4 kernel: [    0.031747] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct  8 18:02:28 node-4 kernel: [    0.031863] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct  8 18:02:28 node-4 kernel: [    0.031864] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct  8 18:02:28 node-4 kernel: [    0.031865] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct  8 18:02:28 node-4 kernel: [    0.031866] HPET id 0 under DRHD base 0xc7ffc000
Oct  8 18:02:28 node-4 kernel: [    0.031867] Your BIOS is broken and requested that x2apic be disabled.
Oct  8 18:02:28 node-4 kernel: [    0.031867] This will slightly decrease performance.
Oct  8 18:02:28 node-4 kernel: [    0.031867] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct  8 18:02:28 node-4 kernel: [    0.032300] Enabled IRQ remapping in xapic mode
Oct  8 18:02:28 node-4 kernel: [    0.032301] x2apic not enabled, IRQ remapping is in xapic mode
Oct  8 18:02:28 node-4 kernel: [    0.032305] Switched APIC routing to physical flat.
Oct  8 18:02:28 node-4 kernel: [    0.032925] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct  8 18:02:28 node-4 kernel: [    0.072578] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct  8 18:02:28 node-4 kernel: [    0.072584] TSC deadline timer enabled
Oct  8 18:02:28 node-4 kernel: [    0.072591] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct  8 18:02:28 node-4 kernel: [    0.072597] ... version:                3
Oct  8 18:02:28 node-4 kernel: [    0.072598] ... bit width:              48
Oct  8 18:02:28 node-4 kernel: [    0.072599] ... generic registers:      4
Oct  8 18:02:28 node-4 kernel: [    0.072600] ... value mask:             0000ffffffffffff
Oct  8 18:02:28 node-4 kernel: [    0.072601] ... max period:             0000ffffffffffff
Oct  8 18:02:28 node-4 kernel: [    0.072602] ... fixed-purpose events:   3
Oct  8 18:02:28 node-4 kernel: [    0.072603] ... event mask:             000000070000000f
Oct  8 18:02:28 node-4 kernel: [    0.073974] x86: Booting SMP configuration:
Oct  8 18:02:28 node-4 kernel: [    0.088078] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct  8 18:02:28 node-4 kernel: [    0.073976] .... node  #0, CPUs:        #1  #2  #3
Oct  8 18:02:28 node-4 kernel: [    0.115989] .... node  #1, CPUs:    #4  #5  #6  #7
Oct  8 18:02:28 node-4 kernel: [    0.269856] .... node  #0, CPUs:    #8  #9 #10 #11
Oct  8 18:02:28 node-4 kernel: [    0.325473] .... node  #1, CPUs:   #12 #13 #14 #15
Oct  8 18:02:28 node-4 kernel: [    0.382122] x86: Booted up 2 nodes, 16 CPUs
Oct  8 18:02:28 node-4 kernel: [    0.382126] smpboot: Total of 16 processors activated (111762.05 BogoMIPS)
Oct  8 18:02:28 node-4 kernel: [    0.405861] devtmpfs: initialized
Oct  8 18:02:28 node-4 kernel: [    0.408601] EVM: security.selinux
Oct  8 18:02:28 node-4 kernel: [    0.408603] EVM: security.SMACK64
Oct  8 18:02:28 node-4 kernel: [    0.408603] EVM: security.ima
Oct  8 18:02:28 node-4 kernel: [    0.408604] EVM: security.capability
Oct  8 18:02:28 node-4 kernel: [    0.408657] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.409313] pinctrl core: initialized pinctrl subsystem
Oct  8 18:02:28 node-4 kernel: [    0.409390] regulator-dummy: no parameters
Oct  8 18:02:28 node-4 kernel: [    0.409421] RTC time: 18:01:53, date: 10/08/16
Oct  8 18:02:28 node-4 kernel: [    0.409456] NET: Registered protocol family 16
Oct  8 18:02:28 node-4 kernel: [    0.409541] cpuidle: using governor ladder
Oct  8 18:02:28 node-4 kernel: [    0.409542] cpuidle: using governor menu
Oct  8 18:02:28 node-4 kernel: [    0.409577] ACPI: bus type PCI registered
Oct  8 18:02:28 node-4 kernel: [    0.409579] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct  8 18:02:28 node-4 kernel: [    0.409623] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct  8 18:02:28 node-4 kernel: [    0.409626] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct  8 18:02:28 node-4 kernel: [    0.423323] PCI: Using configuration type 1 for base access
Oct  8 18:02:28 node-4 kernel: [    0.424316] bio: create slab <bio-0> at 0
Oct  8 18:02:28 node-4 kernel: [    0.424604] ACPI: Added _OSI(Module Device)
Oct  8 18:02:28 node-4 kernel: [    0.424605] ACPI: Added _OSI(Processor Device)
Oct  8 18:02:28 node-4 kernel: [    0.424606] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct  8 18:02:28 node-4 kernel: [    0.424607] ACPI: Added _OSI(Processor Aggregator Device)
Oct  8 18:02:28 node-4 kernel: [    0.437383] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct  8 18:02:28 node-4 kernel: [    0.447928] ACPI: Interpreter enabled
Oct  8 18:02:28 node-4 kernel: [    0.447934] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct  8 18:02:28 node-4 kernel: [    0.447938] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct  8 18:02:28 node-4 kernel: [    0.447940] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct  8 18:02:28 node-4 kernel: [    0.447947] ACPI: (supports S0 S4 S5)
Oct  8 18:02:28 node-4 kernel: [    0.447948] ACPI: Using IOAPIC for interrupt routing
Oct  8 18:02:28 node-4 kernel: [    0.447991] HEST: Table parsing has been initialized.
Oct  8 18:02:28 node-4 kernel: [    0.447993] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct  8 18:02:28 node-4 kernel: [    0.448553] ACPI: No dock devices found.
Oct  8 18:02:28 node-4 kernel: [    0.460166] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct  8 18:02:28 node-4 kernel: [    0.460171] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  8 18:02:28 node-4 kernel: [    0.460174] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  8 18:02:28 node-4 kernel: [    0.460203] PCI host bridge to bus 0000:ff
Oct  8 18:02:28 node-4 kernel: [    0.460205] pci_bus 0000:ff: root bus resource [bus ff]
Oct  8 18:02:28 node-4 kernel: [    0.460213] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460250] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.460280] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460315] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460343] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.460372] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.460402] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460430] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460459] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460487] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460513] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460539] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460566] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460592] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460618] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460644] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460672] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460699] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460725] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.460753] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460778] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.460803] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460829] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460858] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.460892] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460923] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460952] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.460982] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461013] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461043] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461073] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461103] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461133] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461165] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461195] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461225] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461257] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461285] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461312] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461344] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461377] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461413] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461447] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461480] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461508] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461537] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461566] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461595] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461625] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461654] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461685] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461714] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461741] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461770] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461799] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461829] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461860] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461916] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct  8 18:02:28 node-4 kernel: [    0.461919] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  8 18:02:28 node-4 kernel: [    0.461922] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  8 18:02:28 node-4 kernel: [    0.461939] PCI host bridge to bus 0000:7f
Oct  8 18:02:28 node-4 kernel: [    0.461941] pci_bus 0000:7f: root bus resource [bus 7f]
Oct  8 18:02:28 node-4 kernel: [    0.461946] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.461973] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.462001] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462030] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462051] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.462075] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.462101] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462125] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462147] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462174] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462198] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462223] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462249] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462274] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462299] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462327] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462349] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462371] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462394] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.462418] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462440] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.462462] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462485] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462513] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct  8 18:02:28 node-4 kernel: [    0.462547] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462573] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462601] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462630] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462655] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462683] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462711] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462740] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462765] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462793] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462820] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462848] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462877] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462902] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462926] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462953] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.462978] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463005] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463033] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463059] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463083] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463108] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463133] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463160] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463186] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463212] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463241] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463265] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463287] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463311] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463336] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463365] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.463390] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.464633] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct  8 18:02:28 node-4 kernel: [    0.464636] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  8 18:02:28 node-4 kernel: [    0.465775] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  8 18:02:28 node-4 kernel: [    0.466288] PCI host bridge to bus 0000:00
Oct  8 18:02:28 node-4 kernel: [    0.466291] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct  8 18:02:28 node-4 kernel: [    0.466293] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct  8 18:02:28 node-4 kernel: [    0.466294] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct  8 18:02:28 node-4 kernel: [    0.466295] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct  8 18:02:28 node-4 kernel: [    0.466297] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct  8 18:02:28 node-4 kernel: [    0.466298] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct  8 18:02:28 node-4 kernel: [    0.466300] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct  8 18:02:28 node-4 kernel: [    0.466305] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct  8 18:02:28 node-4 kernel: [    0.466387] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.466418] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.466460] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct  8 18:02:28 node-4 kernel: [    0.466479] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.466509] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.466549] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct  8 18:02:28 node-4 kernel: [    0.466568] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.466598] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.466641] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct  8 18:02:28 node-4 kernel: [    0.466657] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.466727] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.466805] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.466883] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct  8 18:02:28 node-4 kernel: [    0.466888] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct  8 18:02:28 node-4 kernel: [    0.466972] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct  8 18:02:28 node-4 kernel: [    0.467116] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct  8 18:02:28 node-4 kernel: [    0.467133] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct  8 18:02:28 node-4 kernel: [    0.467211] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.467267] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct  8 18:02:28 node-4 kernel: [    0.467288] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.467343] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.467387] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct  8 18:02:28 node-4 kernel: [    0.467414] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.467470] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.467513] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct  8 18:02:28 node-4 kernel: [    0.467537] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct  8 18:02:28 node-4 kernel: [    0.467554] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct  8 18:02:28 node-4 kernel: [    0.467632] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.467682] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct  8 18:02:28 node-4 kernel: [    0.467710] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct  8 18:02:28 node-4 kernel: [    0.467958] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct  8 18:02:28 node-4 kernel: [    0.467964] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct  8 18:02:28 node-4 kernel: [    0.467971] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.467976] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.467983] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct  8 18:02:28 node-4 kernel: [    0.468014] pci 0000:01:00.0: supports D1 D2
Oct  8 18:02:28 node-4 kernel: [    0.474182] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  8 18:02:28 node-4 kernel: [    0.474185] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  8 18:02:28 node-4 kernel: [    0.474187] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  8 18:02:28 node-4 kernel: [    0.474294] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.474328] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct  8 18:02:28 node-4 kernel: [    0.482196] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  8 18:02:28 node-4 kernel: [    0.482198] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.482200] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  8 18:02:28 node-4 kernel: [    0.482255] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.482322] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.482399] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.482443] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  8 18:02:28 node-4 kernel: [    0.482447] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.482448] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  8 18:02:28 node-4 kernel: [    0.482500] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.482623] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.482675] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  8 18:02:28 node-4 kernel: [    0.482678] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.482680] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  8 18:02:28 node-4 kernel: [    0.482729] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.482848] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.482889] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.483008] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.483050] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.483174] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.483211] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct  8 18:02:28 node-4 kernel: [    0.483330] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct  8 18:02:28 node-4 kernel: [    0.483373] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  8 18:02:28 node-4 kernel: [    0.483375] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.483377] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  8 18:02:28 node-4 kernel: [    0.483437] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct  8 18:02:28 node-4 kernel: [    0.483499] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.483552] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.483593] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct  8 18:02:28 node-4 kernel: [    0.483677] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct  8 18:02:28 node-4 kernel: [    0.483783] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  8 18:02:28 node-4 kernel: [    0.483785] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.483787] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  8 18:02:28 node-4 kernel: [    0.483843] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct  8 18:02:28 node-4 kernel: [    0.483897] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.483946] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.484192] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  8 18:02:28 node-4 kernel: [    0.484196] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  8 18:02:28 node-4 kernel: [    0.484258] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct  8 18:02:28 node-4 kernel: [    0.484312] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.484360] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.484569] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  8 18:02:28 node-4 kernel: [    0.484573] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  8 18:02:28 node-4 kernel: [    0.484631] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct  8 18:02:28 node-4 kernel: [    0.484690] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.484745] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct  8 18:02:28 node-4 kernel: [    0.484966] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  8 18:02:28 node-4 kernel: [    0.484969] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  8 18:02:28 node-4 kernel: [    0.485165] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  8 18:02:28 node-4 kernel: [    0.485203] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  8 18:02:28 node-4 kernel: [    0.485279] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct  8 18:02:28 node-4 kernel: [    0.485298] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct  8 18:02:28 node-4 kernel: [    0.485311] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct  8 18:02:28 node-4 kernel: [    0.485324] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct  8 18:02:28 node-4 kernel: [    0.485375] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct  8 18:02:28 node-4 kernel: [    0.490196] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  8 18:02:28 node-4 kernel: [    0.490205] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  8 18:02:28 node-4 kernel: [    0.490257] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct  8 18:02:28 node-4 kernel: [    0.490907] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct  8 18:02:28 node-4 kernel: [    0.490910] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  8 18:02:28 node-4 kernel: [    0.491034] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  8 18:02:28 node-4 kernel: [    0.491142] PCI host bridge to bus 0000:80
Oct  8 18:02:28 node-4 kernel: [    0.491144] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct  8 18:02:28 node-4 kernel: [    0.491145] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct  8 18:02:28 node-4 kernel: [    0.491147] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct  8 18:02:28 node-4 kernel: [    0.491155] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.491219] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.491287] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct  8 18:02:28 node-4 kernel: [    0.491349] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct  8 18:02:28 node-4 kernel: [    0.491355] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct  8 18:02:28 node-4 kernel: [    0.491429] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct  8 18:02:28 node-4 kernel: [    0.491730] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct  8 18:02:28 node-4 kernel: [    0.491762] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct  8 18:02:28 node-4 kernel: [    0.491791] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct  8 18:02:28 node-4 kernel: [    0.491821] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct  8 18:02:28 node-4 kernel: [    0.491850] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  8 18:02:28 node-4 kernel: [    0.491880] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  8 18:02:28 node-4 kernel: [    0.491910] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  8 18:02:28 node-4 kernel: [    0.491940] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  8 18:02:28 node-4 kernel: [    0.492025] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct  8 18:02:28 node-4 kernel: [    0.492030] ACPI: \_SB_.UNC1: notify handler is installed
Oct  8 18:02:28 node-4 kernel: [    0.492031] ACPI: \_SB_.UNC0: notify handler is installed
Oct  8 18:02:28 node-4 kernel: [    0.492046] ACPI: \_SB_.PCI0: notify handler is installed
Oct  8 18:02:28 node-4 kernel: [    0.492099] ACPI: \_SB_.PCI1: notify handler is installed
Oct  8 18:02:28 node-4 kernel: [    0.492179] Found 4 acpi root devices
Oct  8 18:02:28 node-4 kernel: [    0.492290] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct  8 18:02:28 node-4 kernel: [    0.492293] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct  8 18:02:28 node-4 kernel: [    0.492294] vgaarb: loaded
Oct  8 18:02:28 node-4 kernel: [    0.492295] vgaarb: bridge control possible 0000:0c:00.0
Oct  8 18:02:28 node-4 kernel: [    0.492419] SCSI subsystem initialized
Oct  8 18:02:28 node-4 kernel: [    0.492482] libata version 3.00 loaded.
Oct  8 18:02:28 node-4 kernel: [    0.492498] ACPI: bus type USB registered
Oct  8 18:02:28 node-4 kernel: [    0.492508] usbcore: registered new interface driver usbfs
Oct  8 18:02:28 node-4 kernel: [    0.492513] usbcore: registered new interface driver hub
Oct  8 18:02:28 node-4 kernel: [    0.492536] usbcore: registered new device driver usb
Oct  8 18:02:28 node-4 kernel: [    0.492705] PCI: Using ACPI for IRQ routing
Oct  8 18:02:28 node-4 kernel: [    0.496299] PCI: pci_cache_line_size set to 64 bytes
Oct  8 18:02:28 node-4 kernel: [    0.496509] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct  8 18:02:28 node-4 kernel: [    0.496510] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct  8 18:02:28 node-4 kernel: [    0.496511] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct  8 18:02:28 node-4 kernel: [    0.496577] NetLabel: Initializing
Oct  8 18:02:28 node-4 kernel: [    0.496578] NetLabel:  domain hash size = 128
Oct  8 18:02:28 node-4 kernel: [    0.496579] NetLabel:  protocols = UNLABELED CIPSOv4
Oct  8 18:02:28 node-4 kernel: [    0.496589] NetLabel:  unlabeled traffic allowed by default
Oct  8 18:02:28 node-4 kernel: [    0.496645] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct  8 18:02:28 node-4 kernel: [    0.496649] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct  8 18:02:28 node-4 kernel: [    0.498718] Switched to clocksource hpet
Oct  8 18:02:28 node-4 kernel: [    0.503137] AppArmor: AppArmor Filesystem Enabled
Oct  8 18:02:28 node-4 kernel: [    0.503174] pnp: PnP ACPI init
Oct  8 18:02:28 node-4 kernel: [    0.503187] ACPI: bus type PNP registered
Oct  8 18:02:28 node-4 kernel: [    0.503368] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct  8 18:02:28 node-4 kernel: [    0.503379] pnp 00:01: [dma 4]
Oct  8 18:02:28 node-4 kernel: [    0.503397] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct  8 18:02:28 node-4 kernel: [    0.503432] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct  8 18:02:28 node-4 kernel: [    0.503457] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct  8 18:02:28 node-4 kernel: [    0.503478] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct  8 18:02:28 node-4 kernel: [    0.503525] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct  8 18:02:28 node-4 kernel: [    0.503635] system 00:06: [io  0x0500-0x057f] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503638] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct  8 18:02:28 node-4 kernel: [    0.503639] system 00:06: [io  0x0580-0x059f] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503641] system 00:06: [io  0x0600-0x061f] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503642] system 00:06: [io  0x0880-0x0883] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503644] system 00:06: [io  0x0800-0x081f] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503647] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct  8 18:02:28 node-4 kernel: [    0.503649] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503650] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503652] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503653] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503655] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503656] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct  8 18:02:28 node-4 kernel: [    0.503659] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct  8 18:02:28 node-4 kernel: [    0.503758] pnp 00:07: [dma 0 disabled]
Oct  8 18:02:28 node-4 kernel: [    0.503791] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  8 18:02:28 node-4 kernel: [    0.503873] pnp 00:08: [dma 0 disabled]
Oct  8 18:02:28 node-4 kernel: [    0.503909] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  8 18:02:28 node-4 kernel: [    0.503967] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct  8 18:02:28 node-4 kernel: [    0.504412] pnp: PnP ACPI: found 10 devices
Oct  8 18:02:28 node-4 kernel: [    0.504414] ACPI: bus type PNP unregistered
Oct  8 18:02:28 node-4 kernel: [    0.510428] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  8 18:02:28 node-4 kernel: [    0.510432] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  8 18:02:28 node-4 kernel: [    0.510435] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  8 18:02:28 node-4 kernel: [    0.510440] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  8 18:02:28 node-4 kernel: [    0.510442] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.510457] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510486] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  8 18:02:28 node-4 kernel: [    0.510501] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510530] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  8 18:02:28 node-4 kernel: [    0.510545] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  8 18:02:28 node-4 kernel: [    0.510574] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  8 18:02:28 node-4 kernel: [    0.510592] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  8 18:02:28 node-4 kernel: [    0.510621] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  8 18:02:28 node-4 kernel: [    0.510623] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.510637] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510666] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  8 18:02:28 node-4 kernel: [    0.510668] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.510683] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510716] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  8 18:02:28 node-4 kernel: [    0.510718] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.510721] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510726] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  8 18:02:28 node-4 kernel: [    0.510727] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.510730] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510734] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  8 18:02:28 node-4 kernel: [    0.510740] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  8 18:02:28 node-4 kernel: [    0.510749] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  8 18:02:28 node-4 kernel: [    0.510753] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  8 18:02:28 node-4 kernel: [    0.510760] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct  8 18:02:28 node-4 kernel: [    0.510761] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct  8 18:02:28 node-4 kernel: [    0.510762] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct  8 18:02:28 node-4 kernel: [    0.510763] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct  8 18:02:28 node-4 kernel: [    0.510764] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct  8 18:02:28 node-4 kernel: [    0.510765] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct  8 18:02:28 node-4 kernel: [    0.510766] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct  8 18:02:28 node-4 kernel: [    0.510767] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct  8 18:02:28 node-4 kernel: [    0.510768] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.510769] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510770] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.510771] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510772] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.510773] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510774] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.510774] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510776] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct  8 18:02:28 node-4 kernel: [    0.510776] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510778] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct  8 18:02:28 node-4 kernel: [    0.510779] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct  8 18:02:28 node-4 kernel: [    0.510780] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct  8 18:02:28 node-4 kernel: [    0.510781] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct  8 18:02:28 node-4 kernel: [    0.510784] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct  8 18:02:28 node-4 kernel: [    0.510785] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct  8 18:02:28 node-4 kernel: [    0.510826] NET: Registered protocol family 2
Oct  8 18:02:28 node-4 kernel: [    0.511124] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.511489] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.511663] TCP: Hash tables configured (established 262144 bind 65536)
Oct  8 18:02:28 node-4 kernel: [    0.511707] TCP: reno registered
Oct  8 18:02:28 node-4 kernel: [    0.511738] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.511845] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.512016] NET: Registered protocol family 1
Oct  8 18:02:28 node-4 kernel: [    0.546818] pci 0000:0c:00.0: Video device with shadowed ROM
Oct  8 18:02:28 node-4 kernel: [    0.546833] PCI: CLS 64 bytes, default 64
Oct  8 18:02:28 node-4 kernel: [    0.546924] Trying to unpack rootfs image as initramfs...
Oct  8 18:02:28 node-4 kernel: [    0.768127] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Oct  8 18:02:28 node-4 kernel: [    0.768184] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct  8 18:02:28 node-4 kernel: [    0.768194] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct  8 18:02:28 node-4 kernel: [    0.768773] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768778] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768785] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768791] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768803] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768816] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768831] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768846] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768858] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768865] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768872] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768877] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768886] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768898] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768909] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768921] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct  8 18:02:28 node-4 kernel: [    0.768990] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct  8 18:02:28 node-4 kernel: [    0.768994] Scanning for low memory corruption every 60 seconds
Oct  8 18:02:28 node-4 kernel: [    0.769312] Initialise system trusted keyring
Oct  8 18:02:28 node-4 kernel: [    0.769357] audit: initializing netlink socket (disabled)
Oct  8 18:02:28 node-4 kernel: [    0.769370] type=2000 audit(1475949712.720:1): initialized
Oct  8 18:02:28 node-4 kernel: [    0.787019] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct  8 18:02:28 node-4 kernel: [    0.788483] zbud: loaded
Oct  8 18:02:28 node-4 kernel: [    0.788597] VFS: Disk quotas dquot_6.5.2
Oct  8 18:02:28 node-4 kernel: [    0.788630] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct  8 18:02:28 node-4 kernel: [    0.788995] fuse init (API version 7.22)
Oct  8 18:02:28 node-4 kernel: [    0.789053] msgmni has been set to 32768
Oct  8 18:02:28 node-4 kernel: [    0.789097] Key type big_key registered
Oct  8 18:02:28 node-4 kernel: [    0.789597] Key type asymmetric registered
Oct  8 18:02:28 node-4 kernel: [    0.789599] Asymmetric key parser 'x509' registered
Oct  8 18:02:28 node-4 kernel: [    0.789619] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct  8 18:02:28 node-4 kernel: [    0.789671] io scheduler noop registered
Oct  8 18:02:28 node-4 kernel: [    0.789672] io scheduler deadline registered (default)
Oct  8 18:02:28 node-4 kernel: [    0.789691] io scheduler cfq registered
Oct  8 18:02:28 node-4 kernel: [    0.789987] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    0.790084] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    0.790173] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    0.790261] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    0.790356] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    0.790419] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    0.790678] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct  8 18:02:28 node-4 kernel: [    0.790697] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct  8 18:02:28 node-4 kernel: [    0.790717] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct  8 18:02:28 node-4 kernel: [    0.790728] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790730] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790732] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct  8 18:02:28 node-4 kernel: [    0.790736] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790738] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790739] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790740] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790742] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790743] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790745] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790746] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790747] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790749] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790750] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790752] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790754] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct  8 18:02:28 node-4 kernel: [    0.790758] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790760] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct  8 18:02:28 node-4 kernel: [    0.790770] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790773] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct  8 18:02:28 node-4 kernel: [    0.790786] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790787] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct  8 18:02:28 node-4 kernel: [    0.790790] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct  8 18:02:28 node-4 kernel: [    0.790802] ioapic: probe of 0000:00:05.4 failed with error -22
Oct  8 18:02:28 node-4 kernel: [    0.790885] ioapic: probe of 0000:80:05.4 failed with error -22
Oct  8 18:02:28 node-4 kernel: [    0.790890] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct  8 18:02:28 node-4 kernel: [    0.790898] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct  8 18:02:28 node-4 kernel: [    0.790934] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct  8 18:02:28 node-4 kernel: [    0.790936] vesafb: scrolling: redraw
Oct  8 18:02:28 node-4 kernel: [    0.790937] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct  8 18:02:28 node-4 kernel: [    0.810483] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct  8 18:02:28 node-4 kernel: [    0.819008] Console: switching to colour frame buffer device 80x30
Oct  8 18:02:28 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct  8 18:02:28 node-4 kernel: [    0.827704] fb0: VESA VGA frame buffer device
Oct  8 18:02:28 node-4 kernel: [    0.827903] intel_idle: MWAIT substates: 0x2120
Oct  8 18:02:28 node-4 kernel: [    0.827904] intel_idle: v0.4 model 0x3F
Oct  8 18:02:28 node-4 kernel: [    0.827904] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct  8 18:02:28 node-4 kernel: [    0.828132] ipmi message handler version 39.2
Oct  8 18:02:28 node-4 kernel: [    0.828383] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  8 18:02:28 node-4 kernel: [    0.828814] ACPI: AC Adapter [P111] (on-line)
Oct  8 18:02:28 node-4 kernel: [    0.834039] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct  8 18:02:28 node-4 kernel: [    0.845046] ACPI: Power Button [PWRB]
Oct  8 18:02:28 node-4 kernel: [    0.850809] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct  8 18:02:28 node-4 kernel: [    0.862438] ACPI: Power Button [PWRF]
Oct  8 18:02:28 node-4 kernel: [    0.880267] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct  8 18:02:28 node-4 kernel: [    0.891924] pstore: Registered erst as persistent store backend
Oct  8 18:02:28 node-4 kernel: [    0.898114] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct  8 18:02:28 node-4 kernel: [    0.910064] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct  8 18:02:28 node-4 kernel: [    0.936811] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct  8 18:02:28 node-4 kernel: [    0.970100] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct  8 18:02:28 node-4 kernel: [    0.984169] Linux agpgart interface v0.103
Oct  8 18:02:28 node-4 kernel: [    0.991823] brd: module loaded
Oct  8 18:02:28 node-4 kernel: [    0.998960] loop: module loaded
Oct  8 18:02:28 node-4 kernel: [    1.005778] libphy: Fixed MDIO Bus: probed
Oct  8 18:02:28 node-4 kernel: [    1.012238] tun: Universal TUN/TAP device driver, 1.6
Oct  8 18:02:28 node-4 kernel: [    1.018715] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct  8 18:02:28 node-4 kernel: [    1.025217] PPP generic driver version 2.4.2
Oct  8 18:02:28 node-4 kernel: [    1.031597] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct  8 18:02:28 node-4 kernel: [    1.038026] ehci-pci: EHCI PCI platform driver
Oct  8 18:02:28 node-4 kernel: [    1.044549] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct  8 18:02:28 node-4 kernel: [    1.051020] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct  8 18:02:28 node-4 kernel: [    1.063540] ehci-pci 0000:00:1a.0: debug port 2
Oct  8 18:02:28 node-4 kernel: [    1.073728] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct  8 18:02:28 node-4 kernel: [    1.073753] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct  8 18:02:28 node-4 kernel: [    1.090208] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct  8 18:02:28 node-4 kernel: [    1.096275] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct  8 18:02:28 node-4 kernel: [    1.102432] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  8 18:02:28 node-4 kernel: [    1.114403] usb usb1: Product: EHCI Host Controller
Oct  8 18:02:28 node-4 kernel: [    1.120428] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  8 18:02:28 node-4 kernel: [    1.126463] usb usb1: SerialNumber: 0000:00:1a.0
Oct  8 18:02:28 node-4 kernel: [    1.132406] hub 1-0:1.0: USB hub found
Oct  8 18:02:28 node-4 kernel: [    1.138164] hub 1-0:1.0: 2 ports detected
Oct  8 18:02:28 node-4 kernel: [    1.143951] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct  8 18:02:28 node-4 kernel: [    1.149537] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct  8 18:02:28 node-4 kernel: [    1.160422] ehci-pci 0000:00:1d.0: debug port 2
Oct  8 18:02:28 node-4 kernel: [    1.169712] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct  8 18:02:28 node-4 kernel: [    1.169714] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct  8 18:02:28 node-4 kernel: [    1.186127] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct  8 18:02:28 node-4 kernel: [    1.191317] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct  8 18:02:28 node-4 kernel: [    1.196608] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  8 18:02:28 node-4 kernel: [    1.207170] usb usb2: Product: EHCI Host Controller
Oct  8 18:02:28 node-4 kernel: [    1.212617] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  8 18:02:28 node-4 kernel: [    1.218156] usb usb2: SerialNumber: 0000:00:1d.0
Oct  8 18:02:28 node-4 kernel: [    1.223655] hub 2-0:1.0: USB hub found
Oct  8 18:02:28 node-4 kernel: [    1.228993] hub 2-0:1.0: 2 ports detected
Oct  8 18:02:28 node-4 kernel: [    1.234289] ehci-platform: EHCI generic platform driver
Oct  8 18:02:28 node-4 kernel: [    1.239512] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct  8 18:02:28 node-4 kernel: [    1.244817] ohci-pci: OHCI PCI platform driver
Oct  8 18:02:28 node-4 kernel: [    1.250104] ohci-platform: OHCI generic platform driver
Oct  8 18:02:28 node-4 kernel: [    1.255290] uhci_hcd: USB Universal Host Controller Interface driver
Oct  8 18:02:28 node-4 kernel: [    1.260637] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct  8 18:02:28 node-4 kernel: [    1.453909] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct  8 18:02:28 node-4 kernel: [    1.626148] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct  8 18:02:28 node-4 kernel: [    1.631663] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  8 18:02:28 node-4 kernel: [    1.637416] hub 1-1:1.0: USB hub found
Oct  8 18:02:28 node-4 kernel: [    1.642885] hub 1-1:1.0: 6 ports detected
Oct  8 18:02:28 node-4 kernel: [    1.757640] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct  8 18:02:28 node-4 kernel: [    1.785614] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct  8 18:02:28 node-4 kernel: [    2.025809] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct  8 18:02:28 node-4 kernel: [    2.031348] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  8 18:02:28 node-4 kernel: [    2.037198] hub 2-1:1.0: USB hub found
Oct  8 18:02:28 node-4 kernel: [    2.042796] hub 2-1:1.0: 8 ports detected
Oct  8 18:02:28 node-4 kernel: [    2.302280] i8042: No controller found
Oct  8 18:02:28 node-4 kernel: [    2.307673] mousedev: PS/2 mouse device common for all mice
Oct  8 18:02:28 node-4 kernel: [    2.313171] rtc_cmos 00:02: RTC can wake from S4
Oct  8 18:02:28 node-4 kernel: [    2.318737] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct  8 18:02:28 node-4 kernel: [    2.321233] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct  8 18:02:28 node-4 kernel: [    2.329852] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct  8 18:02:28 node-4 kernel: [    2.340959] device-mapper: uevent: version 1.0.3
Oct  8 18:02:28 node-4 kernel: [    2.346583] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct  8 18:02:28 node-4 kernel: [    2.357814] ledtrig-cpu: registered to indicate activity on CPUs
Oct  8 18:02:28 node-4 kernel: [    2.363787] TCP: cubic registered
Oct  8 18:02:28 node-4 kernel: [    2.369694] NET: Registered protocol family 10
Oct  8 18:02:28 node-4 kernel: [    2.375682] NET: Registered protocol family 17
Oct  8 18:02:28 node-4 kernel: [    2.381392] Key type dns_resolver registered
Oct  8 18:02:28 node-4 kernel: [    2.387352] Loading compiled-in X.509 certificates
Oct  8 18:02:28 node-4 kernel: [    2.393555] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct  8 18:02:28 node-4 kernel: [    2.404988] registered taskstats version 1
Oct  8 18:02:28 node-4 kernel: [    2.412929] Key type trusted registered
Oct  8 18:02:28 node-4 kernel: [    2.420531] Key type encrypted registered
Oct  8 18:02:28 node-4 kernel: [    2.425967] AppArmor: AppArmor sha1 policy hashing enabled
Oct  8 18:02:28 node-4 kernel: [    2.431445] IMA: No TPM chip found, activating TPM-bypass!
Oct  8 18:02:28 node-4 kernel: [    2.437596] regulator-dummy: disabling
Oct  8 18:02:28 node-4 kernel: [    2.443116]   Magic number: 4:496:38
Oct  8 18:02:28 node-4 kernel: [    2.448496] bdi 7:3: hash matches
Oct  8 18:02:28 node-4 kernel: [    2.453915] memory memory207: hash matches
Oct  8 18:02:28 node-4 kernel: [    2.457766] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct  8 18:02:28 node-4 kernel: [    2.457767] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  8 18:02:28 node-4 kernel: [    2.457768] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct  8 18:02:28 node-4 kernel: [    2.457768] usb 2-1.4: Manufacturer: Avocent
Oct  8 18:02:28 node-4 kernel: [    2.457769] usb 2-1.4: SerialNumber: 20111102-00000001
Oct  8 18:02:28 node-4 kernel: [    2.491958] memory memory74: hash matches
Oct  8 18:02:28 node-4 kernel: [    2.497428] rtc_cmos 00:02: setting system clock to 2016-10-08 18:01:55 UTC (1475949715)
Oct  8 18:02:28 node-4 kernel: [    2.509642] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct  8 18:02:28 node-4 kernel: [    2.515169] EDD information not available.
Oct  8 18:02:28 node-4 kernel: [    2.520665] PM: Hibernation image not present or could not be loaded.
Oct  8 18:02:28 node-4 kernel: [    2.521534] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct  8 18:02:28 node-4 kernel: [    2.532473] Write protecting the kernel read-only data: 12288k
Oct  8 18:02:28 node-4 kernel: [    2.538536] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct  8 18:02:28 node-4 kernel: [    2.551044] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct  8 18:02:28 node-4 kernel: [    2.583399] device-mapper: multipath: version 1.6.0 loaded
Oct  8 18:02:28 node-4 kernel: [    2.591350] systemd-udevd[218]: starting version 204
Oct  8 18:02:28 node-4 kernel: [    2.615208] md: linear personality registered for level -1
Oct  8 18:02:28 node-4 kernel: [    2.628928] md: multipath personality registered for level -4
Oct  8 18:02:28 node-4 kernel: [    2.637810] md: raid0 personality registered for level 0
Oct  8 18:02:28 node-4 kernel: [    2.645845] md: raid1 personality registered for level 1
Oct  8 18:02:28 node-4 kernel: [    2.652212] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct  8 18:02:28 node-4 kernel: [    2.658447] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct  8 18:02:28 node-4 kernel: [    2.659101] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct  8 18:02:28 node-4 kernel: [    2.660963] megasas: FW now in Ready state
Oct  8 18:02:28 node-4 kernel: [    2.661023] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661061] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661096] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661134] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661171] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661210] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661240] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661276] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661316] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661353] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661366] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661393] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661429] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661466] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661504] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661513] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.661670] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct  8 18:02:28 node-4 kernel: [    2.690526] hidraw: raw HID events driver (C) Jiri Kosina
Oct  8 18:02:28 node-4 kernel: [    2.698776] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Oct  8 18:02:28 node-4 kernel: [    2.712077] 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  8 18:02:28 node-4 kernel: [    2.725800] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  8 18:02:28 node-4 kernel: [    2.732729] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.732733] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.732737] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.732741] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.732783] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.746528] usbcore: registered new interface driver usbhid
Oct  8 18:02:28 node-4 kernel: [    2.753219] usbhid: USB HID core driver
Oct  8 18:02:28 node-4 kernel: [    2.757078] raid6: sse2x1    1506 MB/s
Oct  8 18:02:28 node-4 kernel: [    2.761219] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Oct  8 18:02:28 node-4 kernel: [    2.761236] 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  8 18:02:28 node-4 kernel: [    2.761251] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct  8 18:02:28 node-4 kernel: [    2.762256] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.762300] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.762410] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.762556] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.762693] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.762787] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.763156] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.786770] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Oct  8 18:02:28 node-4 kernel: [    2.786813] 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  8 18:02:28 node-4 kernel: [    2.786823] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  8 18:02:28 node-4 kernel: [    2.787319] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.787645] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    2.824997] raid6: sse2x2     554 MB/s
Oct  8 18:02:28 node-4 kernel: [    2.892686] raid6: sse2x4    7038 MB/s
Oct  8 18:02:28 node-4 kernel: [    2.964631] raid6: avx2x1   14948 MB/s
Oct  8 18:02:28 node-4 kernel: [    3.036558] raid6: avx2x2   18916 MB/s
Oct  8 18:02:28 node-4 kernel: [    3.108496] raid6: avx2x4   21342 MB/s
Oct  8 18:02:28 node-4 kernel: [    3.114699] raid6: using algorithm avx2x4 (21342 MB/s)
Oct  8 18:02:28 node-4 kernel: [    3.120837] raid6: using avx2x2 recovery algorithm
Oct  8 18:02:28 node-4 kernel: [    3.126871] megasas:IOC Init cmd success
Oct  8 18:02:28 node-4 kernel: [    3.126873] Switched to clocksource tsc
Oct  8 18:02:28 node-4 kernel: [    3.127130] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    3.127227] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    3.127499] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  8 18:02:28 node-4 kernel: [    3.141267] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Oct  8 18:02:28 node-4 kernel: [    3.141296] 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  8 18:02:28 node-4 kernel: [    3.141311] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  8 18:02:28 node-4 kernel: [    3.141607] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    3.141674] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    3.141764] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    3.141825] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct  8 18:02:28 node-4 kernel: [    3.142116] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  8 18:02:28 node-4 kernel: [    3.148596] megasas: INIT adapter done
Oct  8 18:02:28 node-4 kernel: [    3.197968] xor: automatically using best checksumming function:
Oct  8 18:02:28 node-4 kernel: [    3.198147] 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  8 18:02:28 node-4 kernel: [    3.198219] 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  8 18:02:28 node-4 kernel: [    3.198279] 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  8 18:02:28 node-4 kernel: [    3.198336] 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  8 18:02:28 node-4 kernel: [    3.198389] 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  8 18:02:28 node-4 kernel: [    3.198567] 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  8 18:02:28 node-4 kernel: [    3.244569] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct  8 18:02:28 node-4 kernel: [    3.246755] scsi0 : LSI SAS based MegaRAID driver
Oct  8 18:02:28 node-4 kernel: [    3.254431] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  8 18:02:28 node-4 kernel: [    3.309882] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  8 18:02:28 node-4 kernel: [    3.327217] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct  8 18:02:28 node-4 kernel: [    3.334732] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct  8 18:02:28 node-4 kernel: [    3.344321]    avx       : 36313.000 MB/sec
Oct  8 18:02:28 node-4 kernel: [    3.356882] sd 0:2:0:0: [sda] Write Protect is off
Oct  8 18:02:28 node-4 kernel: [    3.364024] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct  8 18:02:28 node-4 kernel: [    3.364054] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct  8 18:02:28 node-4 kernel: [    3.378109] async_tx: api initialized (async)
Oct  8 18:02:28 node-4 kernel: [    3.389019] md: raid6 personality registered for level 6
Oct  8 18:02:28 node-4 kernel: [    3.396096] md: raid5 personality registered for level 5
Oct  8 18:02:28 node-4 kernel: [    3.402752]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct  8 18:02:28 node-4 kernel: [    3.408781] sd 0:2:0:0: [sda] Attached SCSI disk
Oct  8 18:02:28 node-4 kernel: [    3.416915] md: raid4 personality registered for level 4
Oct  8 18:02:28 node-4 kernel: [    3.426951] md: raid10 personality registered for level 10
Oct  8 18:02:28 node-4 kernel: [    3.480672] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Oct  8 18:02:28 node-4 kernel: [    3.548319] random: lvm urandom read with 28 bits of entropy available
Oct  8 18:02:28 node-4 kernel: [    3.664629] bio: create slab <bio-1> at 1
Oct  8 18:02:28 node-4 kernel: [    4.320109] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct  8 18:02:28 node-4 kernel: [    4.887774] init: plymouth-upstart-bridge main process (548) terminated with status 1
Oct  8 18:02:28 node-4 kernel: [    4.900099] init: plymouth-upstart-bridge main process ended, respawning
Oct  8 18:02:28 node-4 kernel: [    5.065681] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct  8 18:02:28 node-4 kernel: [    5.093119] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct  8 18:02:28 node-4 kernel: [    5.193642] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct  8 18:02:28 node-4 kernel: [    5.223556] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct  8 18:02:28 node-4 kernel: [    5.281237] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct  8 18:02:28 node-4 kernel: [    5.447023] random: nonblocking pool is initialized
Oct  8 18:02:28 node-4 kernel: [    5.505561] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct  8 18:02:28 node-4 kernel: [    5.543313] XFS (dm-0): Mounting Filesystem
Oct  8 18:02:28 node-4 kernel: [    5.893315] XFS (dm-0): Ending clean mount
Oct  8 18:02:28 node-4 kernel: [    5.945821] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct  8 18:02:28 node-4 kernel: [    5.982531] XFS (dm-1): Mounting Filesystem
Oct  8 18:02:28 node-4 kernel: [    6.056666] XFS (dm-1): Ending clean mount
Oct  8 18:02:28 node-4 kernel: [    7.871602] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct  8 18:02:28 node-4 kernel: [    7.899213] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct  8 18:02:28 node-4 kernel: [    8.033764] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  8 18:02:28 node-4 kernel: [    8.033782] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  8 18:02:28 node-4 kernel: [    8.033785] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct  8 18:02:28 node-4 kernel: [    8.033788] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct  8 18:02:28 node-4 kernel: [    8.066800] systemd-udevd[773]: starting version 204
Oct  8 18:02:28 node-4 kernel: [    8.279721] IPMI System Interface driver.
Oct  8 18:02:28 node-4 kernel: [    8.279777] ipmi_si: probing via ACPI
Oct  8 18:02:28 node-4 kernel: [    8.279794] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct  8 18:02:28 node-4 kernel: [    8.279795] ipmi_si: Adding ACPI-specified kcs state machine
Oct  8 18:02:28 node-4 kernel: [    8.279807] ipmi_si: probing via SMBIOS
Oct  8 18:02:28 node-4 kernel: [    8.279808] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct  8 18:02:28 node-4 kernel: [    8.279808] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct  8 18:02:28 node-4 kernel: [    8.279810] ipmi_si: probing via SPMI
Oct  8 18:02:28 node-4 kernel: [    8.279811] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct  8 18:02:28 node-4 kernel: [    8.279811] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct  8 18:02:28 node-4 kernel: [    8.279812] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct  8 18:02:28 node-4 kernel: [    8.288568] power_meter ACPI000D:00: Found ACPI power meter.
Oct  8 18:02:28 node-4 kernel: [    8.288641] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct  8 18:02:28 node-4 kernel: [    8.295890] wmi: Mapper loaded
Oct  8 18:02:28 node-4 kernel: [    8.297134] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct  8 18:02:28 node-4 kernel: [    8.297140] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  8 18:02:28 node-4 kernel: [    8.297143] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct  8 18:02:28 node-4 kernel: [    8.297146] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  8 18:02:28 node-4 kernel: [    8.297197] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct  8 18:02:28 node-4 kernel: [    8.305997] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct  8 18:02:28 node-4 kernel: [    8.356551] systemd-udevd[792]: renamed network interface eth0 to enp6s0
Oct  8 18:02:28 node-4 kernel: [    8.393409] systemd-udevd[797]: renamed network interface eth1 to enp7s0
Oct  8 18:02:28 node-4 kernel: [    8.420383] systemd-udevd[802]: renamed network interface eth2 to enp8s0
Oct  8 18:02:28 node-4 kernel: [    8.421703] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct  8 18:02:28 node-4 kernel: [    8.421708] ipmi_si 00:09: IPMI kcs interface initialized
Oct  8 18:02:28 node-4 kernel: [    8.440486] systemd-udevd[790]: renamed network interface eth3 to enp9s0
Oct  8 18:02:28 node-4 kernel: [    8.680941] type=1400 audit(1475949721.684:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1051 comm="apparmor_parser"
Oct  8 18:02:28 node-4 kernel: [    8.681096] type=1400 audit(1475949721.684:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1051 comm="apparmor_parser"
Oct  8 18:02:28 node-4 kernel: [    8.681225] type=1400 audit(1475949721.684:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1051 comm="apparmor_parser"
Oct  8 18:02:28 node-4 kernel: [    8.688502] type=1400 audit(1475949721.692:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Oct  8 18:02:28 node-4 kernel: [    8.688641] type=1400 audit(1475949721.692:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1050 comm="apparmor_parser"
Oct  8 18:02:28 node-4 kernel: [    8.688766] type=1400 audit(1475949721.692:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1050 comm="apparmor_parser"
Oct  8 18:02:28 node-4 kernel: [    8.692327] type=1400 audit(1475949721.696:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1041 comm="apparmor_parser"
Oct  8 18:02:28 node-4 kernel: [    8.692464] type=1400 audit(1475949721.696:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1041 comm="apparmor_parser"
Oct  8 18:02:28 node-4 kernel: [    8.692584] type=1400 audit(1475949721.696:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1041 comm="apparmor_parser"
Oct  8 18:02:28 node-4 kernel: [    8.693409] type=1400 audit(1475949721.696:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1036 comm="apparmor_parser"
Oct  8 18:02:28 node-4 kernel: [    9.235764] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct  8 18:02:28 node-4 kernel: [    9.241074] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct  8 18:02:28 node-4 kernel: [    9.427663] enic 0000:06:00.0 enp6s0: Link UP
Oct  8 18:02:28 node-4 kernel: [    9.428211] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct  8 18:02:28 node-4 kernel: [    9.428221] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct  8 18:02:28 node-4 kernel: [   18.166718] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct  8 18:02:29 node-4 failsafe: Failsafe of 120 seconds reached.
Oct  8 18:02:29 node-4 kernel: [   36.856533] init: failsafe main process (8411) killed by TERM signal
Oct  8 18:02:29 node-4 dbus[8478]: [system] AppArmor D-Bus mediation is enabled
Oct  8 18:02:29 node-4 kernel: [   37.104894] audit_printk_skb: 30 callbacks suppressed
Oct  8 18:02:29 node-4 kernel: [   37.104896] type=1400 audit(1475949749.991:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8528 comm="apparmor_parser"
Oct  8 18:02:29 node-4 kernel: [   37.104900] type=1400 audit(1475949749.991:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8528 comm="apparmor_parser"
Oct  8 18:02:29 node-4 kernel: [   37.104903] type=1400 audit(1475949749.991:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8528 comm="apparmor_parser"
Oct  8 18:02:29 node-4 kernel: [   37.105120] type=1400 audit(1475949749.991:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8528 comm="apparmor_parser"
Oct  8 18:02:29 node-4 kernel: [   37.105122] type=1400 audit(1475949749.991:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8528 comm="apparmor_parser"
Oct  8 18:02:29 node-4 kernel: [   37.105234] type=1400 audit(1475949749.991:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8528 comm="apparmor_parser"
Oct  8 18:02:30 node-4 kernel: [   37.107385] type=1400 audit(1475949749.995:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8529 comm="apparmor_parser"
Oct  8 18:02:30 node-4 kernel: [   37.193776] type=1400 audit(1475949750.079:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8531 comm="apparmor_parser"
Oct  8 18:02:30 node-4 anacron[8604]: Anacron 2.3 started on 2016-10-08
Oct  8 18:02:30 node-4 anacron[8604]: Will run job `cron.daily' in 5 min.
Oct  8 18:02:30 node-4 anacron[8604]: Will run job `cron.weekly' in 10 min.
Oct  8 18:02:30 node-4 anacron[8604]: Will run job `cron.monthly' in 15 min.
Oct  8 18:02:30 node-4 anacron[8604]: Jobs will be executed sequentially
Oct  8 18:02:30 node-4 cron[8569]: (CRON) INFO (pidfile fd = 3)
Oct  8 18:02:30 node-4 cron[8618]: (CRON) STARTUP (fork ok)
Oct  8 18:02:30 node-4 multipathd: path checkers start up
Oct  8 18:02:30 node-4 cron[8618]: (CRON) INFO (Running @reboot jobs)
Oct  8 18:02:30 node-4 postfix/master[8748]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct  8 18:02:33 node-4 puppet-agent[8932]: Reopening log files
Oct  8 18:02:33 node-4 puppet-agent[8932]: Could not request certificate: Connection refused - connect(2)
Oct  8 18:02:49 node-4 puppet-user[9140]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct  8 18:02:49 node-4 puppet-user[9140]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Oct  8 18:02:50 node-4 puppet-user[9140]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct  8 18:02:50 node-4 puppet-user[9140]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct  8 18:02:50 node-4 puppet-user[9140]: Finished catalog run in 0.56 seconds
Oct  8 18:02:51 node-4 multipathd: uevent trigger error
Oct  8 18:02:51 node-4 puppet-user[9570]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  8 18:02:51 node-4 puppet-user[9570]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Oct  8 18:02:51 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct  8 18:02:51 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct  8 18:02:51 node-4 puppet-user[9570]: (/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  8 18:02:51 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct  8 18:02:51 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct  8 18:02:51 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct  8 18:02:51 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct  8 18:02:51 node-4 puppet-user[9570]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct  8 18:02:51 node-4 puppet-user[9570]: Finished catalog run in 0.06 seconds
Oct  8 18:02:52 node-4 puppet-user[10027]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct  8 18:02:52 node-4 puppet-user[10027]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Oct  8 18:02:53 node-4 puppet-user[10027]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct  8 18:02:53 node-4 puppet-user[10027]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct  8 18:02:53 node-4 puppet-user[10027]: Finished catalog run in 0.03 seconds
Oct  8 18:02:54 node-4 puppet-user[10485]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct  8 18:02:54 node-4 puppet-user[10485]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Oct  8 18:02:54 node-4 puppet-user[10485]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct  8 18:02:54 node-4 puppet-user[10485]: Finished catalog run in 0.03 seconds
Oct  8 18:02:55 node-4 puppet-user[10927]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct  8 18:02:55 node-4 puppet-user[10927]: Compiled catalog for node-4.domain.tld in environment production in 0.17 seconds
Oct  8 18:02:56 node-4 puppet-user[10927]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct  8 18:02:56 node-4 puppet-user[10927]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Oct  8 18:02:56 node-4 puppet-user[10927]: Finished catalog run in 0.51 seconds
Oct  8 18:02:57 node-4 puppet-user[11586]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct  8 18:02:57 node-4 puppet-user[11586]: Compiled catalog for node-4.domain.tld in environment production in 0.19 seconds
Oct  8 18:02:58 node-4 puppet-user[11586]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct  8 18:02:58 node-4 puppet-user[11586]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct  8 18:02:58 node-4 puppet-user[11586]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Oct  8 18:02:58 node-4 puppet-user[11586]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct  8 18:02:58 node-4 puppet-user[11586]: Finished catalog run in 0.30 seconds
Oct  8 18:02:59 node-4 puppet-user[12064]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct  8 18:02:59 node-4 puppet-user[12064]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Oct  8 18:03:00 node-4 puppet-user[12064]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct  8 18:03:00 node-4 kernel: [   67.154584] nr_pdflush_threads exported in /proc is scheduled for removal
Oct  8 18:03:00 node-4 kernel: [   67.154633] 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  8 18:03:00 node-4 puppet-user[12064]: (/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  8 18:03:00 node-4 puppet-user[12064]: Finished catalog run in 0.05 seconds
Oct  8 18:03:01 node-4 CRON[12534]: (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  8 18:03:02 node-4 puppet-user[12531]: (Scope(Class[main])) MODULAR: sync_time
Oct  8 18:03:02 node-4 puppet-user[12531]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Oct  8 18:03:02 node-4 ntpdate[12953]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct  8 18:03:07 node-4 kernel: [   75.038190] init: plymouth-upstart-bridge main process ended, respawning
Oct  8 18:03:08 node-4 puppet-agent[8932]: Could not run: SIGTERM
Oct  8 18:03:08 node-4 kernel: [   75.300689] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct  8 18:03:08 node-4 ntpdate[12953]: adjust time server 10.20.0.2 offset 0.069113 sec
Oct  8 18:03:08 node-4 puppet-user[12531]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct  8 18:03:08 node-4 ec2: 
Oct  8 18:03:08 node-4 ec2: #############################################################
Oct  8 18:03:08 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct  8 18:03:08 node-4 ec2: 1024 0f:16:fe:06:53:dc:37:20:1c:0a:37:4d:6e:39:e4:a7  root@node-4.domain.tld (DSA)
Oct  8 18:03:08 node-4 ec2: 256 61:37:3a:18:11:9b:df:c0:33:55:68:33:cd:14:60:10  root@node-4.domain.tld (ECDSA)
Oct  8 18:03:08 node-4 ec2: 256 9f:18:4e:d0:06:aa:58:18:85:96:f8:ed:4b:22:0a:9d  root@node-4.domain.tld (ED25519)
Oct  8 18:03:08 node-4 ec2: 2048 77:12:e2:6c:40:89:79:5c:cb:62:94:33:2b:26:59:15  root@node-4.domain.tld (RSA)
Oct  8 18:03:08 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct  8 18:03:08 node-4 ec2: #############################################################
Oct  8 18:03:08 node-4 puppet-user[12531]: Finished catalog run in 6.17 seconds
Oct  8 18:03:10 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  8 18:03:10 node-4 nailgun-agent: D, [2016-10-08T18:03:01.435382 #12537] DEBUG -- : Sleep for 9 seconds before sending request
Oct  8 18:03:10 node-4 nailgun-agent: I, [2016-10-08T18:03:10.448113 #12537]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  8 18:03:10 node-4 nailgun-agent: D, [2016-10-08T18:03:10.864451 #12537] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Oct  8 18:03:15 node-4 puppet-user[13455]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  8 18:03:15 node-4 puppet-user[13455]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Oct  8 18:03:15 node-4 puppet-user[13455]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct  8 18:03:15 node-4 puppet-user[13455]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Oct  8 18:03:15 node-4 puppet-user[13455]: Finished catalog run in 0.06 seconds
Oct  8 18:03:17 node-4 puppet-user[13913]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct  8 18:03:17 node-4 puppet-user[13913]: Compiled catalog for node-4.domain.tld in environment production in 0.39 seconds
Oct  8 18:03:17 node-4 puppet-user[13913]: (/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  8 18:03:17 node-4 puppet-user[13913]: (/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  8 18:03:17 node-4 puppet-user[13913]: (/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  8 18:03:17 node-4 puppet-user[13913]: (/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  8 18:03:17 node-4 puppet-user[13913]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct  8 18:03:17 node-4 puppet-user[13913]: (/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  8 18:03:17 node-4 puppet-user[13913]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct  8 18:03:17 node-4 puppet-user[13913]: (/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  8 18:03:17 node-4 puppet-user[13913]: (/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  8 18:03:17 node-4 puppet-user[13913]: (/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  8 18:03:18 node-4 puppet-user[13913]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct  8 18:03:18 node-4 puppet-user[13913]: Finished catalog run in 0.76 seconds
Oct  8 18:03:19 node-4 puppet-user[14419]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct  8 18:03:20 node-4 puppet-user[14419]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.805114 #12537] DEBUG -- : Trying to find block devices
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.805231 #12537] DEBUG -- : Found block device: sda
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.805282 #12537] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.805351 #12537] DEBUG -- : Trying to get list of physical devices
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.805506 #12537] DEBUG -- : Getting udev properties for device: sda
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.807769 #12537] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc788
Oct  8 18:03:22 node-4 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62791", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.807799 #12537] DEBUG -- : Trying to find out if device sda is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.807841 #12537] DEBUG -- : Device sda removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.807857 #12537] DEBUG -- : Device sda seems to be appropriate
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.808321 #12537] DEBUG -- : Getting udev properties for device: dm-0
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.809987 #12537] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-hsOPGXEqI0dJkBaEiUFoSelOzXhLSbxRjK7Vsfz7QJP8YHEeQEkKqlxdqpKk1dSO /dev/disk/by-uuid/c74a21e8-2902-4cc7-bd46-0b43cb068fa9 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-hsOPGXEqI0dJkBaEiUFoSelOzXhLSbxRjK7Vsfz7QJP8YHEeQEkKqlxdqpKk1dSO", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c74a21e8-2902-4cc7-bd46-0b43cb068fa9", "ID_FS_UUID_ENC"=>"c74a21e8-2902-4cc7-bd46-0b43cb068fa9", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"20506", "nomdmonddf"=>"1", "nom
Oct  8 18:03:22 node-4 nailgun-agent: dmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.810030 #12537] DEBUG -- : Trying to find out if device dm-0 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.810073 #12537] DEBUG -- : Device dm-0 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.810087 #12537] DEBUG -- : Device dm-0 seems to be appropriate
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.810104 #12537] DEBUG -- : Getting udev properties for device: dm-1
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.811829 #12537] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-OmA85OBczJD0FRiUBGVvKXaI0PyKTTFf8Tnf45PDsHmPKVbcDwWtQryi3jO7D8E9 /dev/disk/by-uuid/e6336c0c-fb31-45cd-aee8-48031e8fe930 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-OmA85OBczJD0FRiUBGVvKXaI0PyKTTFf8Tnf45PDsHmPKVbcDwWtQryi3jO7D8E9", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e6336c0c-fb31-45cd-aee8-48031e8fe930", "ID_FS_UUID_ENC"=>"e6336c0c-fb31-45cd-aee8-48031e8fe930", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4
Oct  8 18:03:22 node-4 nailgun-agent: 7121", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.811856 #12537] DEBUG -- : Trying to find out if device dm-1 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.811909 #12537] DEBUG -- : Device dm-1 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.811923 #12537] DEBUG -- : Device dm-1 seems to be appropriate
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.811949 #12537] DEBUG -- : Getting udev properties for device: dm-2
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.813648 #12537] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-HNGc8WN1S7mcumwDd45sKufTaIzNctfqkhnCMEUeemrdthJFbX3gcn57kfscW61R /dev/disk/by-uuid/c1fa5568-809d-4e29-a906-415df65f5986 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-HNGc8WN1S7mcumwDd45sKufTaIzNctfqkhnCMEUeemrdthJFbX3gcn57kfscW61R", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c1fa5568-809d-4e29-a906-415df65f5986", "ID_FS_UUID_ENC"=>"c1fa5568-809d-4e29-a906-415df65f5986", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38755", "nomdmon
Oct  8 18:03:22 node-4 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.813683 #12537] DEBUG -- : Trying to find out if device dm-2 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.813711 #12537] DEBUG -- : Device dm-2 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.813738 #12537] DEBUG -- : Device dm-2 seems to be appropriate
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.813753 #12537] DEBUG -- : Getting udev properties for device: dm-3
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.815825 #12537] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-hMmk2XP6MxkFghIYxtjXPvGYSwqZnQENHbPjHXztHfOQHr8JPz11VlDrpQTp0hE6 /dev/disk/by-uuid/58ad04ad-ad9a-4cf4-8a42-a6b7e2efa91d /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-hMmk2XP6MxkFghIYxtjXPvGYSwqZnQENHbPjHXztHfOQHr8JPz11VlDrpQTp0hE6", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"58ad04ad-ad9a-4cf4-8a42-a6b7e2efa91d", "ID_FS_UUID_ENC"=>"58ad04ad-ad9a-4cf4-8a42-a6b7e2efa91d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"43877", "nomdmonddf"=>"1",
Oct  8 18:03:22 node-4 nailgun-agent:  "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.815861 #12537] DEBUG -- : Trying to find out if device dm-3 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.815913 #12537] DEBUG -- : Device dm-3 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.815927 #12537] DEBUG -- : Device dm-3 seems to be appropriate
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.815943 #12537] DEBUG -- : Getting udev properties for device: dm-4
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.817644 #12537] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-i4l0nw6xsRT6O6g6anAjqaHu3hYgubPx7T6fjYxKQbTwd8MbLpIuToex72qsiKu9 /dev/disk/by-uuid/5c5df0ad-046e-4ac5-9606-180b017ab4ac /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-i4l0nw6xsRT6O6g6anAjqaHu3hYgubPx7T6fjYxKQbTwd8MbLpIuToex72qsiKu9", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"5c5df0ad-046e-4ac5-9606-180b017ab4ac", "ID_FS_UUID_ENC"=>"5c5df0ad-046e-4ac5-9606-180b017ab4ac", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"40598", "nomdmonddf"=>"1", "nom
Oct  8 18:03:22 node-4 nailgun-agent: dmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.817670 #12537] DEBUG -- : Trying to find out if device dm-4 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.817710 #12537] DEBUG -- : Device dm-4 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.817723 #12537] DEBUG -- : Device dm-4 seems to be appropriate
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.817750 #12537] DEBUG -- : Getting udev properties for device: dm-5
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.819671 #12537] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-i4l0nw6xsRT6O6g6anAjqaHu3hYgubPxW7vdtbYDNgS5xa8xyKx8iYzdyGFagOe7 /dev/disk/by-uuid/5c605090-017e-4a15-8b7b-0b928b09296d /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-i4l0nw6xsRT6O6g6anAjqaHu3hYgubPxW7vdtbYDNgS5xa8xyKx8iYzdyGFagOe7", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"5c605090-017e-4a15-8b7b-0b928b09296d", "ID_FS_UUID_ENC"=>"5c605090-017e-4a15-8b7b-0b928b09296d", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"41012", "nomdmonddf"=>"1", "nomdmonisw
Oct  8 18:03:22 node-4 nailgun-agent: "=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.819700 #12537] DEBUG -- : Trying to find out if device dm-5 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.819743 #12537] DEBUG -- : Device dm-5 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.819795 #12537] DEBUG -- : Device dm-5 seems to be appropriate
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.819811 #12537] DEBUG -- : Getting udev properties for device: ram0
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.821521 #12537] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98128", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.821547 #12537] DEBUG -- : Trying to find out if device ram0 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.821582 #12537] DEBUG -- : Device ram0 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.821617 #12537] DEBUG -- : Getting udev properties for device: ram1
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.823211 #12537] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98221", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.823236 #12537] DEBUG -- : Trying to find out if device ram1 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.823298 #12537] DEBUG -- : Device ram1 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.823318 #12537] DEBUG -- : Getting udev properties for device: ram2
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.824914 #12537] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98959", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.824964 #12537] DEBUG -- : Trying to find out if device ram2 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.825023 #12537] DEBUG -- : Device ram2 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.825043 #12537] DEBUG -- : Getting udev properties for device: ram3
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.826705 #12537] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99039", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.826738 #12537] DEBUG -- : Trying to find out if device ram3 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.826772 #12537] DEBUG -- : Device ram3 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.826807 #12537] DEBUG -- : Getting udev properties for device: ram4
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.828273 #12537] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99122", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.828299 #12537] DEBUG -- : Trying to find out if device ram4 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.828333 #12537] DEBUG -- : Device ram4 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.828353 #12537] DEBUG -- : Getting udev properties for device: ram5
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.829877 #12537] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99196", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.829902 #12537] DEBUG -- : Trying to find out if device ram5 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.829981 #12537] DEBUG -- : Device ram5 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.830000 #12537] DEBUG -- : Getting udev properties for device: ram6
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.831488 #12537] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99320", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.831514 #12537] DEBUG -- : Trying to find out if device ram6 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.831546 #12537] DEBUG -- : Device ram6 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.831577 #12537] DEBUG -- : Getting udev properties for device: ram7
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.833185 #12537] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99420", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.833210 #12537] DEBUG -- : Trying to find out if device ram7 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.833242 #12537] DEBUG -- : Device ram7 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.833261 #12537] DEBUG -- : Getting udev properties for device: ram8
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.834828 #12537] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99488", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.834851 #12537] DEBUG -- : Trying to find out if device ram8 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.834882 #12537] DEBUG -- : Device ram8 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.834911 #12537] DEBUG -- : Getting udev properties for device: ram9
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.836381 #12537] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99598", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.836420 #12537] DEBUG -- : Trying to find out if device ram9 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.836456 #12537] DEBUG -- : Device ram9 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.836487 #12537] DEBUG -- : Getting udev properties for device: loop0
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.838124 #12537] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97409", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.838145 #12537] DEBUG -- : Trying to find out if device loop0 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.838183 #12537] DEBUG -- : Device loop0 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.838204 #12537] DEBUG -- : Getting udev properties for device: loop1
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.839896 #12537] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97501", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.839922 #12537] DEBUG -- : Trying to find out if device loop1 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.839971 #12537] DEBUG -- : Device loop1 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.839990 #12537] DEBUG -- : Getting udev properties for device: loop2
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.841436 #12537] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97595", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.841462 #12537] DEBUG -- : Trying to find out if device loop2 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.841496 #12537] DEBUG -- : Device loop2 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.841523 #12537] DEBUG -- : Getting udev properties for device: loop3
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.842996 #12537] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97702", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.843038 #12537] DEBUG -- : Trying to find out if device loop3 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.843075 #12537] DEBUG -- : Device loop3 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.843093 #12537] DEBUG -- : Getting udev properties for device: loop4
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.844791 #12537] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97798", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.844827 #12537] DEBUG -- : Trying to find out if device loop4 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.844878 #12537] DEBUG -- : Device loop4 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.844909 #12537] DEBUG -- : Getting udev properties for device: loop5
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.846539 #12537] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97874", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.846563 #12537] DEBUG -- : Trying to find out if device loop5 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.846627 #12537] DEBUG -- : Device loop5 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.846665 #12537] DEBUG -- : Getting udev properties for device: loop6
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.848230 #12537] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97943", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.848263 #12537] DEBUG -- : Trying to find out if device loop6 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.848296 #12537] DEBUG -- : Device loop6 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.848322 #12537] DEBUG -- : Getting udev properties for device: loop7
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.849899 #12537] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98043", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.849927 #12537] DEBUG -- : Trying to find out if device loop7 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.849959 #12537] DEBUG -- : Device loop7 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.849990 #12537] DEBUG -- : Getting udev properties for device: ram10
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.851613 #12537] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98313", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.851652 #12537] DEBUG -- : Trying to find out if device ram10 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.851697 #12537] DEBUG -- : Device ram10 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.851716 #12537] DEBUG -- : Getting udev properties for device: ram11
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.853414 #12537] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98438", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.858595 #12537] DEBUG -- : Trying to find out if device ram11 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.858653 #12537] DEBUG -- : Device ram11 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.858672 #12537] DEBUG -- : Getting udev properties for device: ram12
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.860438 #12537] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98547", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.860464 #12537] DEBUG -- : Trying to find out if device ram12 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.860526 #12537] DEBUG -- : Device ram12 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.860544 #12537] DEBUG -- : Getting udev properties for device: ram13
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.862157 #12537] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98635", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.862183 #12537] DEBUG -- : Trying to find out if device ram13 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.862218 #12537] DEBUG -- : Device ram13 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.862266 #12537] DEBUG -- : Getting udev properties for device: ram14
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.863698 #12537] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98776", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.863725 #12537] DEBUG -- : Trying to find out if device ram14 is removable or not
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.863757 #12537] DEBUG -- : Device ram14 removable parameter: "0"
Oct  8 18:03:22 node-4 nailgun-agent: D, [2016-10-08T18:03:22.863777 #12537] DEBUG -- : Getting udev properties for device: ram15
Oct  8 18:03:22 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  8 18:03:23 node-4 puppet-user[14419]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865277 #12537] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98867", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865303 #12537] DEBUG -- : Trying to find out if device ram15 is removable or not
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865348 #12537] DEBUG -- : Device ram15 removable parameter: "0"
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865384 #12537] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865400 #12537] DEBUG -- : Block device seems to be physical data storage: sda
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865493 #12537] DEBUG -- : Found block device: dm-0
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865507 #12537] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865520 #12537] DEBUG -- : Found block device: dm-1
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865531 #12537] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865540 #12537] DEBUG -- : Found block device: dm-2
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865550 #12537] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865560 #12537] DEBUG -- : Found block device: dm-3
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865570 #12537] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865643 #12537] DEBUG -- : Found block device: dm-4
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865655 #12537] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865675 #12537] DEBUG -- : Found block device: dm-5
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865685 #12537] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865694 #12537] DEBUG -- : Found block device: ram0
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865704 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865712 #12537] DEBUG -- : Found block device: ram1
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865722 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865776 #12537] DEBUG -- : Found block device: ram2
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865787 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865795 #12537] DEBUG -- : Found block device: ram3
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865805 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865813 #12537] DEBUG -- : Found block device: ram4
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865825 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865834 #12537] DEBUG -- : Found block device: ram5
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865845 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865854 #12537] DEBUG -- : Found block device: ram6
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865913 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865922 #12537] DEBUG -- : Found block device: ram7
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865932 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865941 #12537] DEBUG -- : Found block device: ram8
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865951 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865960 #12537] DEBUG -- : Found block device: ram9
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865970 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.865979 #12537] DEBUG -- : Found block device: loop0
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866040 #12537] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866050 #12537] DEBUG -- : Found block device: loop1
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866060 #12537] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866069 #12537] DEBUG -- : Found block device: loop2
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866080 #12537] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866088 #12537] DEBUG -- : Found block device: loop3
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866098 #12537] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866107 #12537] DEBUG -- : Found block device: loop4
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866117 #12537] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866170 #12537] DEBUG -- : Found block device: loop5
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866181 #12537] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866203 #12537] DEBUG -- : Found block device: loop6
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866227 #12537] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866238 #12537] DEBUG -- : Found block device: loop7
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866249 #12537] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866258 #12537] DEBUG -- : Found block device: ram10
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866268 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866278 #12537] DEBUG -- : Found block device: ram11
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866323 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866333 #12537] DEBUG -- : Found block device: ram12
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866343 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866352 #12537] DEBUG -- : Found block device: ram13
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866362 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866371 #12537] DEBUG -- : Found block device: ram14
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866391 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866400 #12537] DEBUG -- : Found block device: ram15
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866410 #12537] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:22.866464 #12537] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Oct  8 18:03:23 node-4 nailgun-agent: D, [2016-10-08T18:03:23.062395 #12537] DEBUG -- : Response: status: 200 body: {"id": 4}
Oct  8 18:03:23 node-4 nailgun-agent: I, [2016-10-08T18:03:23.062683 #12537]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Oct  8 18:03:50 node-4 puppet-user[14419]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct  8 18:03:50 node-4 puppet-user[14419]: Finished catalog run in 30.53 seconds
Oct  8 18:03:52 node-4 puppet-user[17059]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct  8 18:03:53 node-4 puppet-user[17059]: Compiled catalog for node-4.domain.tld in environment production in 0.59 seconds
Oct  8 18:03:53 node-4 puppet-user[17059]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct  8 18:03:53 node-4 puppet-user[17059]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct  8 18:03:53 node-4 puppet-user[17059]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct  8 18:03:53 node-4 puppet-user[17059]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct  8 18:03:53 node-4 puppet-user[17059]: Finished catalog run in 0.09 seconds
Oct  8 18:03:55 node-4 puppet-user[17513]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct  8 18:03:56 node-4 puppet-user[17513]: Compiled catalog for node-4.domain.tld in environment production in 0.94 seconds
Oct  8 18:03:56 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct  8 18:03:56 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct  8 18:03:56 node-4 crontab[17955]: (root) LIST (root)
Oct  8 18:03:56 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct  8 18:03:56 node-4 crontab[17956]: (root) REPLACE (root)
Oct  8 18:03:57 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/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  8 18:03:58 node-4 puppet-user[17513]: (/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  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/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  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct  8 18:03:58 node-4 puppet-user[17513]: (/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  8 18:03:58 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct  8 18:03:59 node-4 puppet-user[17513]: (/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  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct  8 18:03:59 node-4 puppet-user[17513]: (/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  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct  8 18:03:59 node-4 puppet-user[17513]: (/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  8 18:03:59 node-4 puppet-user[17513]: (/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  8 18:03:59 node-4 puppet-user[17513]: (/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  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct  8 18:03:59 node-4 puppet-user[17513]: (/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  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct  8 18:03:59 node-4 puppet-user[17513]: (/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  8 18:03:59 node-4 puppet-user[17513]: (/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  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct  8 18:03:59 node-4 puppet-user[17513]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct  8 18:03:59 node-4 puppet-user[17513]: (/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  8 18:03:59 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8384" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  8 18:03:59 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct  8 18:04:01 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:01 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:01 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:01 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:01 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:14 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:14 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:14 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:14 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:16 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:16 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:16 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:16 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:16 node-4 multipathd: uevent trigger error
<27>Oct  8 18:04:16 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:11 node-4 ntpdate[28993]: no servers can be used, exiting
<27>Oct  8 18:05:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:46 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:46 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:46 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:46 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:46 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:57 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:57 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:57 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:57 node-4 multipathd: uevent trigger error
<27>Oct  8 18:05:57 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:05 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:05 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:05 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:05 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:05 node-4 multipathd: uevent trigger error
<43>Oct  8 18:06:19 node-4 apache2_error [Sat Oct 08 18:06:15.821043 2016] [mpm_event:notice] [pid 6674:tid 139802837075840] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  8 18:06:19 node-4 apache2_error [Sat Oct 08 18:06:15.821130 2016] [core:notice] [pid 6674:tid 139802837075840] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  8 18:06:19 node-4 apache2_error [Sat Oct 08 18:06:18.645609 2016] [mpm_event:notice] [pid 6674:tid 139802837075840] AH00491: caught SIGTERM, shutting down
<27>Oct  8 18:06:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:06:23 node-4 multipathd: uevent trigger error
<43>Oct  8 18:06:29 node-4 apache2_error [Sat Oct 08 18:06:19.734336 2016] [mpm_worker:notice] [pid 7029:tid 140424414463872] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  8 18:06:29 node-4 apache2_error [Sat Oct 08 18:06:19.734385 2016] [core:notice] [pid 7029:tid 140424414463872] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  8 18:06:59 node-4 apache2_error [Sat Oct 08 18:06:57.177011 2016] [mpm_worker:notice] [pid 7029:tid 140424414463872] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  8 18:06:59 node-4 apache2_error [Sat Oct 08 18:06:57.185135 2016] [mpm_worker:warn] [pid 7029:tid 140424414463872] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  8 18:06:59 node-4 apache2_error [Sat Oct 08 18:06:57.185906 2016] [mpm_worker:notice] [pid 7029:tid 140424414463872] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  8 18:06:59 node-4 apache2_error [Sat Oct 08 18:06:57.185921 2016] [core:notice] [pid 7029:tid 140424414463872] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  8 18:07:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:00 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:34 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:34 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:34 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:34 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:34 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:36 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Oct  8 18:07:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:07:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:01 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:08 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:08 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:08 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:08 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:08 node-4 multipathd: uevent trigger error
<129>Oct  8 18:08:11 node-4 haproxy[23805]: Backup Server mysqld/node-4 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  8 18:08:13 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:13 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:13 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:13 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:13 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:16 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:16 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:16 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:16 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:16 node-4 multipathd: uevent trigger error
<129>Oct  8 18:08:19 node-4 haproxy[26003]: Backup Server mysqld/node-4 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  8 18:08:20 node-4 haproxy[26012]: Server object-storage/node-4 is DOWN, reason: Layer4 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  8 18:08:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:22 node-4 multipathd: uevent trigger error
<129>Oct  8 18:08:24 node-4 haproxy[27310]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:25 node-4 haproxy[27319]: Backup Server mysqld/node-4 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  8 18:08:26 node-4 haproxy[27319]: Server object-storage/node-4 is DOWN, reason: Layer4 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  8 18:08:27 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:27 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:27 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:27 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:27 node-4 multipathd: uevent trigger error
<129>Oct  8 18:08:29 node-4 haproxy[28457]: Server keystone-1/node-4 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  8 18:08:30 node-4 haproxy[28471]: Server keystone-2/node-4 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  8 18:08:30 node-4 haproxy[28471]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:30 node-4 haproxy[28471]: Backup Server mysqld/node-4 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  8 18:08:31 node-4 haproxy[28471]: Server object-storage/node-4 is DOWN, reason: Layer4 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  8 18:08:32 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:32 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:32 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:32 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:32 node-4 multipathd: uevent trigger error
<129>Oct  8 18:08:35 node-4 haproxy[29583]: Server keystone-1/node-4 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  8 18:08:35 node-4 haproxy[29583]: Server keystone-2/node-4 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  8 18:08:35 node-4 haproxy[29583]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:36 node-4 haproxy[29583]: Backup Server mysqld/node-4 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  8 18:08:36 node-4 haproxy[29583]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:36 node-4 haproxy[29583]: Server aodh/node-4 is DOWN, reason: Layer4 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  8 18:08:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:37 node-4 multipathd: uevent trigger error
<129>Oct  8 18:08:38 node-4 haproxy[29583]: 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  8 18:08:38 node-4 haproxy[29583]: Server aodh/node-3 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  8 18:08:38 node-4 haproxy[29583]: proxy aodh has no server available!
<129>Oct  8 18:08:40 node-4 haproxy[30733]: Server keystone-1/node-4 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  8 18:08:40 node-4 haproxy[30733]: Server keystone-2/node-4 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  8 18:08:40 node-4 haproxy[30733]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:41 node-4 haproxy[30744]: Backup Server mysqld/node-4 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  8 18:08:41 node-4 haproxy[30744]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:41 node-4 haproxy[30744]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:42 node-4 haproxy[30744]: Server ceilometer/node-4 is DOWN, reason: Layer4 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  8 18:08:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:43 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:43 node-4 multipathd: uevent trigger error
<129>Oct  8 18:08:43 node-4 haproxy[30744]: 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  8 18:08:43 node-4 haproxy[30744]: Server aodh/node-3 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  8 18:08:43 node-4 haproxy[30744]: proxy aodh has no server available!
<129>Oct  8 18:08:43 node-4 haproxy[30744]: 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  8 18:08:44 node-4 haproxy[30744]: Server ceilometer/node-3 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  8 18:08:44 node-4 haproxy[30744]: proxy ceilometer has no server available!
<129>Oct  8 18:08:45 node-4 haproxy[31859]: Server keystone-1/node-4 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  8 18:08:45 node-4 haproxy[31859]: Server keystone-2/node-4 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  8 18:08:46 node-4 haproxy[31868]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:46 node-4 haproxy[31868]: Backup Server mysqld/node-4 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  8 18:08:46 node-4 haproxy[31868]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:47 node-4 haproxy[31868]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:47 node-4 haproxy[31868]: Server ceilometer/node-4 is DOWN, reason: Layer4 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  8 18:08:48 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:48 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:48 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:48 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:48 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:48 node-4 multipathd: uevent trigger error
<129>Oct  8 18:08:48 node-4 haproxy[31868]: 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  8 18:08:49 node-4 haproxy[31868]: Server aodh/node-3 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  8 18:08:49 node-4 haproxy[31868]: proxy aodh has no server available!
<129>Oct  8 18:08:49 node-4 haproxy[31868]: 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  8 18:08:49 node-4 haproxy[31868]: Server ceilometer/node-3 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  8 18:08:49 node-4 haproxy[31868]: proxy ceilometer has no server available!
<129>Oct  8 18:08:51 node-4 haproxy[552]: Server keystone-1/node-4 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  8 18:08:51 node-4 haproxy[552]: Server keystone-2/node-4 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  8 18:08:51 node-4 haproxy[552]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:51 node-4 haproxy[552]: Backup Server mysqld/node-4 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  8 18:08:52 node-4 haproxy[552]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:52 node-4 haproxy[552]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:52 node-4 haproxy[552]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:52 node-4 haproxy[552]: 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  8 18:08:52 node-4 haproxy[552]: Server horizon/node-3 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  8 18:08:53 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:53 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:53 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:53 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:53 node-4 multipathd: uevent trigger error
<129>Oct  8 18:08:54 node-4 haproxy[552]: 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  8 18:08:54 node-4 haproxy[552]: Server aodh/node-3 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  8 18:08:54 node-4 haproxy[552]: proxy aodh has no server available!
<129>Oct  8 18:08:54 node-4 haproxy[552]: 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  8 18:08:54 node-4 haproxy[552]: Server ceilometer/node-3 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  8 18:08:54 node-4 haproxy[552]: proxy ceilometer has no server available!
<129>Oct  8 18:08:56 node-4 haproxy[1745]: Server keystone-1/node-4 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  8 18:08:56 node-4 haproxy[1745]: Server keystone-2/node-4 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  8 18:08:56 node-4 haproxy[1745]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:57 node-4 haproxy[1754]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:57 node-4 haproxy[1754]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:57 node-4 haproxy[1754]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:57 node-4 haproxy[1754]: Backup Server mysqld/node-4 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  8 18:08:57 node-4 haproxy[1754]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:57 node-4 haproxy[1754]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:58 node-4 haproxy[1754]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  8 18:08:58 node-4 haproxy[1754]: 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  8 18:08:58 node-4 haproxy[1754]: Server horizon/node-3 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  8 18:08:59 node-4 haproxy[1754]: 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.
<27>Oct  8 18:08:59 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:59 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:59 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:59 node-4 multipathd: uevent trigger error
<27>Oct  8 18:08:59 node-4 multipathd: uevent trigger error
<129>Oct  8 18:08:59 node-4 haproxy[1754]: Server glance-registry/node-3 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  8 18:08:59 node-4 haproxy[1754]: proxy glance-registry has no server available!
<129>Oct  8 18:08:59 node-4 haproxy[1754]: 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  8 18:08:59 node-4 haproxy[1754]: Server aodh/node-3 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  8 18:08:59 node-4 haproxy[1754]: proxy aodh has no server available!
<129>Oct  8 18:08:59 node-4 haproxy[1754]: 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  8 18:09:00 node-4 haproxy[1754]: Server ceilometer/node-3 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  8 18:09:00 node-4 haproxy[1754]: proxy ceilometer has no server available!
<129>Oct  8 18:09:02 node-4 haproxy[2989]: Server keystone-1/node-4 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  8 18:09:02 node-4 haproxy[2989]: Server keystone-2/node-4 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  8 18:09:02 node-4 haproxy[2989]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:02 node-4 haproxy[2989]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:02 node-4 haproxy[2989]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:02 node-4 haproxy[2989]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:02 node-4 haproxy[2989]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:03 node-4 haproxy[2989]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:03 node-4 haproxy[2989]: Backup Server mysqld/node-4 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  8 18:09:03 node-4 haproxy[2989]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:03 node-4 haproxy[2989]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:03 node-4 haproxy[2989]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:03 node-4 haproxy[2989]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:03 node-4 haproxy[2989]: 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  8 18:09:03 node-4 haproxy[2989]: Server horizon/node-3 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  8 18:09:04 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:04 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:04 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:04 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:04 node-4 multipathd: uevent trigger error
<129>Oct  8 18:09:05 node-4 haproxy[2989]: 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  8 18:09:05 node-4 haproxy[2989]: Server glance-registry/node-3 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  8 18:09:05 node-4 haproxy[2989]: proxy glance-registry has no server available!
<129>Oct  8 18:09:05 node-4 haproxy[2989]: 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  8 18:09:05 node-4 haproxy[2989]: Server aodh/node-3 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  8 18:09:05 node-4 haproxy[2989]: proxy aodh has no server available!
<129>Oct  8 18:09:05 node-4 haproxy[2989]: 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  8 18:09:05 node-4 haproxy[2989]: Server ceilometer/node-3 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  8 18:09:05 node-4 haproxy[2989]: proxy ceilometer has no server available!
<129>Oct  8 18:09:05 node-4 haproxy[2989]: 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  8 18:09:05 node-4 haproxy[2989]: Server nova-novncproxy/node-3 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  8 18:09:05 node-4 haproxy[2989]: proxy nova-novncproxy has no server available!
<129>Oct  8 18:09:07 node-4 haproxy[4276]: Server keystone-1/node-4 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  8 18:09:07 node-4 haproxy[4276]: Server keystone-2/node-4 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.
<27>Oct  8 18:09:07 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Oct  8 18:09:07 node-4 haproxy[4276]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:07 node-4 haproxy[4276]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:07 node-4 haproxy[4276]: Backup Server cinder-api/node-4 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  8 18:09:07 node-4 haproxy[4276]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:08 node-4 haproxy[4276]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:08 node-4 haproxy[4276]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:08 node-4 haproxy[4276]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:08 node-4 haproxy[4276]: Backup Server mysqld/node-4 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  8 18:09:08 node-4 haproxy[4276]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:08 node-4 haproxy[4276]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:08 node-4 haproxy[4276]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:08 node-4 haproxy[4276]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:08 node-4 haproxy[4276]: 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  8 18:09:09 node-4 haproxy[4276]: Server horizon/node-3 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  8 18:09:10 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:10 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:10 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:10 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:10 node-4 multipathd: uevent trigger error
<129>Oct  8 18:09:10 node-4 haproxy[4276]: 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  8 18:09:10 node-4 haproxy[4276]: Server glance-registry/node-3 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  8 18:09:10 node-4 haproxy[4276]: proxy glance-registry has no server available!
<129>Oct  8 18:09:10 node-4 haproxy[4276]: 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  8 18:09:10 node-4 haproxy[4276]: Server aodh/node-3 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  8 18:09:10 node-4 haproxy[4276]: proxy aodh has no server available!
<129>Oct  8 18:09:10 node-4 haproxy[4276]: 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  8 18:09:10 node-4 haproxy[4276]: Server ceilometer/node-3 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  8 18:09:10 node-4 haproxy[4276]: proxy ceilometer has no server available!
<129>Oct  8 18:09:10 node-4 haproxy[4276]: 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  8 18:09:10 node-4 haproxy[4276]: Server nova-novncproxy/node-3 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  8 18:09:10 node-4 haproxy[4276]: proxy nova-novncproxy has no server available!
<129>Oct  8 18:09:12 node-4 haproxy[5467]: Server keystone-1/node-4 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  8 18:09:12 node-4 haproxy[5467]: Server keystone-2/node-4 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  8 18:09:12 node-4 haproxy[5467]: Server nova-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:13 node-4 haproxy[5476]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:13 node-4 haproxy[5476]: Backup Server cinder-api/node-4 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  8 18:09:13 node-4 haproxy[5476]: Server glance-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:13 node-4 haproxy[5476]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:13 node-4 haproxy[5476]: Server neutron/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:13 node-4 haproxy[5476]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:13 node-4 haproxy[5476]: Backup Server mysqld/node-4 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  8 18:09:13 node-4 haproxy[5476]: Server object-storage/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:13 node-4 haproxy[5476]: Server aodh/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:14 node-4 haproxy[5476]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:14 node-4 haproxy[5476]: Server heat-api/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:14 node-4 haproxy[5476]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:14 node-4 haproxy[5476]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:14 node-4 haproxy[5476]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection 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  8 18:09:14 node-4 haproxy[5476]: 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  8 18:09:14 node-4 haproxy[5476]: Server horizon/node-3 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  8 18:09:15 node-4 haproxy[5476]: 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  8 18:09:15 node-4 haproxy[5476]: Server glance-registry/node-3 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  8 18:09:15 node-4 haproxy[5476]: proxy glance-registry has no server available!
<27>Oct  8 18:09:15 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:15 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:15 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:15 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:15 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:15 node-4 multipathd: uevent trigger error
<129>Oct  8 18:09:15 node-4 haproxy[5476]: 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  8 18:09:15 node-4 haproxy[5476]: Server aodh/node-3 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  8 18:09:15 node-4 haproxy[5476]: proxy aodh has no server available!
<129>Oct  8 18:09:15 node-4 haproxy[5476]: 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  8 18:09:16 node-4 haproxy[5476]: Server ceilometer/node-3 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  8 18:09:16 node-4 haproxy[5476]: proxy ceilometer has no server available!
<129>Oct  8 18:09:16 node-4 haproxy[5476]: 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  8 18:09:16 node-4 haproxy[5476]: Server nova-novncproxy/node-3 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  8 18:09:16 node-4 haproxy[5476]: proxy nova-novncproxy has no server available!
<27>Oct  8 18:09:18 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:18 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:19 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:19 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:19 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:22 node-4 multipathd: uevent trigger error
<129>Oct  8 18:09:22 node-4 haproxy[5476]: 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  8 18:09:22 node-4 haproxy[5476]: Server keystone-1/node-3 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  8 18:09:22 node-4 haproxy[5476]: proxy keystone-1 has no server available!
<129>Oct  8 18:09:22 node-4 haproxy[5476]: 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  8 18:09:22 node-4 haproxy[5476]: Server keystone-2/node-3 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  8 18:09:22 node-4 haproxy[5476]: proxy keystone-2 has no server available!
<129>Oct  8 18:09:22 node-4 haproxy[5476]: Server nova-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  8 18:09:22 node-4 haproxy[5476]: Server nova-api/node-3 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  8 18:09:22 node-4 haproxy[5476]: proxy nova-api has no server available!
<129>Oct  8 18:09:22 node-4 haproxy[5476]: Server nova-metadata-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  8 18:09:23 node-4 haproxy[5476]: Server nova-metadata-api/node-3 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  8 18:09:23 node-4 haproxy[5476]: proxy nova-metadata-api has no server available!
<129>Oct  8 18:09:23 node-4 haproxy[5476]: 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  8 18:09:23 node-4 haproxy[5476]: Backup Server cinder-api/node-3 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  8 18:09:23 node-4 haproxy[5476]: proxy cinder-api has no server available!
<129>Oct  8 18:09:23 node-4 haproxy[5476]: 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  8 18:09:23 node-4 haproxy[5476]: Server glance-api/node-3 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  8 18:09:23 node-4 haproxy[5476]: proxy glance-api has no server available!
<129>Oct  8 18:09:23 node-4 haproxy[5476]: 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  8 18:09:23 node-4 haproxy[5476]: Server glance-glare/node-3 is DOWN, reason: Layer4 timeout, check duration: 10002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  8 18:09:23 node-4 haproxy[5476]: proxy glance-glare has no server available!
<129>Oct  8 18:09:23 node-4 haproxy[5476]: 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  8 18:09:23 node-4 haproxy[5476]: Server neutron/node-3 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  8 18:09:23 node-4 haproxy[5476]: proxy neutron has no server available!
<129>Oct  8 18:09:23 node-4 haproxy[5476]: Server mysqld/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  8 18:09:23 node-4 haproxy[5476]: Backup Server mysqld/node-3 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  8 18:09:23 node-4 haproxy[5476]: proxy mysqld has no server available!
<129>Oct  8 18:09:23 node-4 haproxy[5476]: Server object-storage/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  8 18:09:23 node-4 haproxy[5476]: Server object-storage/node-3 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  8 18:09:23 node-4 haproxy[5476]: proxy object-storage has no server available!
<129>Oct  8 18:09:24 node-4 haproxy[5476]: 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  8 18:09:24 node-4 haproxy[5476]: Server heat-api/node-3 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  8 18:09:24 node-4 haproxy[5476]: proxy heat-api has no server available!
<129>Oct  8 18:09:24 node-4 haproxy[5476]: 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  8 18:09:24 node-4 haproxy[5476]: Server heat-api-cfn/node-3 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  8 18:09:24 node-4 haproxy[5476]: proxy heat-api-cfn has no server available!
<129>Oct  8 18:09:24 node-4 haproxy[5476]: 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  8 18:09:24 node-4 haproxy[5476]: Server heat-api-cloudwatch/node-3 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  8 18:09:24 node-4 haproxy[5476]: proxy heat-api-cloudwatch has no server available!
<27>Oct  8 18:09:26 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:26 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:26 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:26 node-4 multipathd: uevent trigger error
<27>Oct  8 18:09:26 node-4 multipathd: uevent trigger error
<27>Oct  8 18:10:03 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  8 18:10:03 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct  8 18:10:30 node-4 multipathd: uevent trigger error
<27>Oct  8 18:10:30 node-4 multipathd: uevent trigger error
<27>Oct  8 18:10:30 node-4 multipathd: uevent trigger error
<27>Oct  8 18:10:30 node-4 multipathd: uevent trigger error
<27>Oct  8 18:10:30 node-4 multipathd: uevent trigger error
<27>Oct  8 18:11:33 node-4 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  8 18:11:35 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct  8 18:12:48 node-4 multipathd: uevent trigger error
<27>Oct  8 18:12:48 node-4 multipathd: uevent trigger error
<27>Oct  8 18:12:48 node-4 multipathd: uevent trigger error
<27>Oct  8 18:12:48 node-4 multipathd: uevent trigger error
<27>Oct  8 18:12:48 node-4 multipathd: uevent trigger error
<27>Oct  8 18:15:53 node-4 multipathd: uevent trigger error
<27>Oct  8 18:15:53 node-4 multipathd: uevent trigger error
<27>Oct  8 18:15:53 node-4 multipathd: uevent trigger error
<27>Oct  8 18:15:53 node-4 multipathd: uevent trigger error
<27>Oct  8 18:15:53 node-4 multipathd: uevent trigger error
<43>Oct  8 18:17:00 node-4 apache2_error [Sat Oct 08 18:16:56.118862 2016] [mpm_worker:notice] [pid 7029:tid 140424414463872] AH00295: caught SIGTERM, shutting down
<43>Oct  8 18:17:00 node-4 apache2_error [Sat Oct 08 18:16:56.864536 2016] [mpm_worker:notice] [pid 3598:tid 140604937807744] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  8 18:17:00 node-4 apache2_error [Sat Oct 08 18:16:56.864566 2016] [core:notice] [pid 3598:tid 140604937807744] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  8 18:17:30 node-4 apache2_error [Sat Oct 08 18:17:28.667810 2016] [mpm_worker:notice] [pid 3598:tid 140604937807744] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  8 18:17:30 node-4 apache2_error [Sat Oct 08 18:17:28.678915 2016] [mpm_worker:warn] [pid 3598:tid 140604937807744] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  8 18:17:30 node-4 apache2_error [Sat Oct 08 18:17:28.686557 2016] [mpm_worker:notice] [pid 3598:tid 140604937807744] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  8 18:17:30 node-4 apache2_error [Sat Oct 08 18:17:28.686581 2016] [core:notice] [pid 3598:tid 140604937807744] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  8 18:17:34 node-4 multipathd: uevent trigger error
<27>Oct  8 18:17:34 node-4 multipathd: uevent trigger error
<27>Oct  8 18:17:34 node-4 multipathd: uevent trigger error
<27>Oct  8 18:17:34 node-4 multipathd: uevent trigger error
<27>Oct  8 18:17:34 node-4 multipathd: uevent trigger error
<27>Oct  8 18:18:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:18:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:18:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:18:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:18:22 node-4 multipathd: uevent trigger error
<27>Oct  8 18:19:32 node-4 multipathd: uevent trigger error
<27>Oct  8 18:19:32 node-4 multipathd: uevent trigger error
<27>Oct  8 18:19:32 node-4 multipathd: uevent trigger error
<27>Oct  8 18:19:32 node-4 multipathd: uevent trigger error
<27>Oct  8 18:25:01 node-4 multipathd: uevent trigger error
<27>Oct  8 18:25:01 node-4 multipathd: uevent trigger error
<27>Oct  8 18:25:01 node-4 multipathd: uevent trigger error
<27>Oct  8 18:25:02 node-4 multipathd: uevent trigger error
<27>Oct  8 18:25:02 node-4 multipathd: uevent trigger error
<27>Oct  8 18:27:08 node-4 multipathd: uevent trigger error
<27>Oct  8 18:27:08 node-4 multipathd: uevent trigger error
<27>Oct  8 18:27:08 node-4 multipathd: uevent trigger error
<27>Oct  8 18:27:08 node-4 multipathd: uevent trigger error
<27>Oct  8 18:27:08 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:09 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:09 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:09 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:09 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:09 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:42 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:42 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:42 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:42 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:42 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:42 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:50 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:50 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:50 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:50 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:50 node-4 multipathd: uevent trigger error
<27>Oct  8 18:28:50 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:07 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct  8 18:29:07 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct  8 18:29:08 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct  8 18:29:09 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Oct  8 18:29:09 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Oct  8 18:29:09 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:09 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:09 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:09 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:09 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:26 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:26 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:26 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:26 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:26 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:31 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:31 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:31 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:31 node-4 multipathd: uevent trigger error
<27>Oct  8 18:29:31 node-4 multipathd: uevent trigger error
<43>Oct  8 18:30:21 node-4 apache2_error [Sat Oct 08 18:30:17.115960 2016] [mpm_worker:notice] [pid 3598:tid 140604937807744] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  8 18:30:21 node-4 apache2_error [Sat Oct 08 18:30:17.501207 2016] [mpm_worker:warn] [pid 3598:tid 140604937807744] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  8 18:30:21 node-4 apache2_error [Sat Oct 08 18:30:17.505248 2016] [mpm_worker:notice] [pid 3598:tid 140604937807744] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  8 18:30:21 node-4 apache2_error [Sat Oct 08 18:30:17.505263 2016] [core:notice] [pid 3598:tid 140604937807744] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  8 18:30:58 node-4 multipathd: uevent trigger error
<27>Oct  8 18:30:58 node-4 multipathd: uevent trigger error
<27>Oct  8 18:30:58 node-4 multipathd: uevent trigger error
<27>Oct  8 18:30:58 node-4 multipathd: uevent trigger error
<27>Oct  8 18:30:58 node-4 multipathd: uevent trigger error
<43>Oct  8 18:31:01 node-4 apache2_error [Sat Oct 08 18:30:54.113783 2016] [mpm_worker:notice] [pid 3598:tid 140604937807744] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  8 18:31:01 node-4 apache2_error [Sat Oct 08 18:30:55.625943 2016] [mpm_worker:warn] [pid 3598:tid 140604937807744] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  8 18:31:01 node-4 apache2_error [Sat Oct 08 18:30:55.639609 2016] [mpm_worker:notice] [pid 3598:tid 140604937807744] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  8 18:31:01 node-4 apache2_error [Sat Oct 08 18:30:55.639651 2016] [core:notice] [pid 3598:tid 140604937807744] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  8 18:31:36 node-4 multipathd: uevent trigger error
<27>Oct  8 18:31:36 node-4 multipathd: uevent trigger error
<27>Oct  8 18:31:36 node-4 multipathd: uevent trigger error
<27>Oct  8 18:31:36 node-4 multipathd: uevent trigger error
<27>Oct  8 18:31:40 node-4 multipathd: uevent trigger error
<27>Oct  8 18:31:40 node-4 multipathd: uevent trigger error
<27>Oct  8 18:31:40 node-4 multipathd: uevent trigger error
<27>Oct  8 18:31:40 node-4 multipathd: uevent trigger error
<27>Oct  8 18:32:36 node-4 multipathd: uevent trigger error
<27>Oct  8 18:32:36 node-4 multipathd: uevent trigger error
<27>Oct  8 18:32:36 node-4 multipathd: uevent trigger error
<27>Oct  8 18:32:36 node-4 multipathd: uevent trigger error
<27>Oct  8 18:32:36 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:37 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:37 node-4 multipathd: uevent trigger error
<11>Oct  8 18:33:46 node-4 liberasurecode[28066]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:46 node-4 liberasurecode[28066]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:46 node-4 liberasurecode[28066]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:46 node-4 liberasurecode[28066]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:46 node-4 liberasurecode[28090]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:46 node-4 liberasurecode[28090]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:46 node-4 liberasurecode[28090]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:46 node-4 liberasurecode[28090]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:47 node-4 liberasurecode[28489]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:47 node-4 liberasurecode[28489]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:47 node-4 liberasurecode[28489]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:47 node-4 liberasurecode[28489]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29058]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29058]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29058]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29058]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29097]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29097]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29097]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29097]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29137]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29137]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29137]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29137]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29195]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29195]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29195]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29195]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29208]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29208]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29208]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29208]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29221]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29221]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29221]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29221]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29238]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29238]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29238]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:33:52 node-4 liberasurecode[29238]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  8 18:33:59 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:59 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:59 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:59 node-4 multipathd: uevent trigger error
<27>Oct  8 18:33:59 node-4 multipathd: uevent trigger error
<27>Oct  8 18:34:04 node-4 multipathd: uevent trigger error
<27>Oct  8 18:34:04 node-4 multipathd: uevent trigger error
<27>Oct  8 18:34:04 node-4 multipathd: uevent trigger error
<27>Oct  8 18:34:04 node-4 multipathd: uevent trigger error
<27>Oct  8 18:34:04 node-4 multipathd: uevent trigger error
<11>Oct  8 18:35:01 node-4 liberasurecode[9287]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:35:01 node-4 liberasurecode[9287]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:35:01 node-4 liberasurecode[9287]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:35:01 node-4 liberasurecode[9287]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  8 18:35:15 node-4 multipathd: uevent trigger error
<27>Oct  8 18:35:15 node-4 multipathd: uevent trigger error
<27>Oct  8 18:35:15 node-4 multipathd: uevent trigger error
<27>Oct  8 18:35:15 node-4 multipathd: uevent trigger error
<27>Oct  8 18:35:15 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:20 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:20 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:20 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:20 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:20 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:25 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:25 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:25 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:25 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:38 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:38 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:38 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:38 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:38 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:38 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:51 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:51 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:51 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:51 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:51 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:56 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:56 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:56 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:56 node-4 multipathd: uevent trigger error
<27>Oct  8 18:37:56 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:14 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:14 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:14 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:14 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:14 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:17 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  8 18:38:17 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  8 18:38:19 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:19 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:19 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:19 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:19 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:23 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:28 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:28 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:28 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:28 node-4 multipathd: uevent trigger error
<27>Oct  8 18:38:28 node-4 multipathd: uevent trigger error
<11>Oct  8 18:40:01 node-4 liberasurecode[27540]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:40:01 node-4 liberasurecode[27540]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:40:01 node-4 liberasurecode[27540]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  8 18:40:01 node-4 liberasurecode[27540]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
