Sep 28 21:08:01 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8425" x-info="http://www.rsyslog.com"] start
Sep 28 21:08:00 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 28 21:08:01 node-4 rsyslogd: rsyslogd's groupid changed to 104
Sep 28 21:08:01 node-4 rsyslogd: rsyslogd's userid changed to 101
Sep 28 21:08:01 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 28 21:08:01 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 28 21:08:01 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 28 21:08:01 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)
Sep 28 21:08:01 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=8794acbd-9b52-4f2a-b81a-40c9a16fc08a nomdmonddf nomdmonisw
Sep 28 21:08:01 node-4 kernel: [    0.000000] KERNEL supported cpus:
Sep 28 21:08:01 node-4 kernel: [    0.000000]   Intel GenuineIntel
Sep 28 21:08:01 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Sep 28 21:08:01 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Sep 28 21:08:01 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 28 21:08:01 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 28 21:08:01 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 28 21:08:01 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 28 21:08:01 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
Sep 28 21:08:01 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 28 21:08:01 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 28 21:08:01 node-4 kernel: [    0.000000] No AGP bridge found
Sep 28 21:08:01 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 28 21:08:01 node-4 kernel: [    0.000000] MTRR default type: write-back
Sep 28 21:08:01 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 28 21:08:01 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Sep 28 21:08:01 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 28 21:08:01 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 28 21:08:01 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 28 21:08:01 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 28 21:08:01 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 28 21:08:01 node-4 kernel: [    0.000000]   2 disabled
Sep 28 21:08:01 node-4 kernel: [    0.000000]   3 disabled
Sep 28 21:08:01 node-4 kernel: [    0.000000]   4 disabled
Sep 28 21:08:01 node-4 kernel: [    0.000000]   5 disabled
Sep 28 21:08:01 node-4 kernel: [    0.000000]   6 disabled
Sep 28 21:08:01 node-4 kernel: [    0.000000]   7 disabled
Sep 28 21:08:01 node-4 kernel: [    0.000000]   8 disabled
Sep 28 21:08:01 node-4 kernel: [    0.000000]   9 disabled
Sep 28 21:08:01 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 28 21:08:01 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 28 21:08:01 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 28 21:08:01 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 28 21:08:01 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 28 21:08:01 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Sep 28 21:08:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 28 21:08:01 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 28 21:08:01 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 28 21:08:01 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 28 21:08:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 28 21:08:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 28 21:08:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 28 21:08:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 28 21:08:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 28 21:08:01 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 28 21:08:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 28 21:08:01 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 28 21:08:01 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 28 21:08:01 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 28 21:08:01 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 28 21:08:01 node-4 kernel: [    0.000000] Zone ranges:
Sep 28 21:08:01 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] Movable zone start for each node
Sep 28 21:08:01 node-4 kernel: [    0.000000] Early memory node ranges
Sep 28 21:08:01 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 28 21:08:01 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 28 21:08:01 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 28 21:08:01 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 28 21:08:01 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 28 21:08:01 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 28 21:08:01 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 28 21:08:01 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 28 21:08:01 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 28 21:08:01 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 28 21:08:01 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 28 21:08:01 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 28 21:08:01 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 28 21:08:01 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 28 21:08:01 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 28 21:08:01 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 28 21:08:01 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 28 21:08:01 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 28 21:08:01 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 28 21:08:01 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 28 21:08:01 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 28 21:08:01 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 28 21:08:01 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 28 21:08:01 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 
Sep 28 21:08:01 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 28 21:08:01 node-4 kernel: [    0.000000] Policy zone: Normal
Sep 28 21:08:01 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=8794acbd-9b52-4f2a-b81a-40c9a16fc08a nomdmonddf nomdmonisw
Sep 28 21:08:01 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 28 21:08:01 node-4 kernel: [    0.000000] Checking aperture...
Sep 28 21:08:01 node-4 kernel: [    0.000000] No AGP bridge found
Sep 28 21:08:01 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 28 21:08:01 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 28 21:08:01 node-4 kernel: [    0.000000] Memory: 32653316K/33280496K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep 28 21:08:01 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 28 21:08:01 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 28 21:08:01 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 28 21:08:01 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 28 21:08:01 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 28 21:08:01 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 28 21:08:01 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 28 21:08:01 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 28 21:08:01 node-4 kernel: [    0.000000] console [tty0] enabled
Sep 28 21:08:01 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 28 21:08:01 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 28 21:08:01 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 28 21:08:01 node-4 kernel: [    0.000000] hpet clockevent registered
Sep 28 21:08:01 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 28 21:08:01 node-4 kernel: [    0.004000] tsc: Detected 3491.844 MHz processor
Sep 28 21:08:01 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.68 BogoMIPS (lpj=13967376)
Sep 28 21:08:01 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 28 21:08:01 node-4 kernel: [    0.000044] Security Framework initialized
Sep 28 21:08:01 node-4 kernel: [    0.000062] AppArmor: AppArmor initialized
Sep 28 21:08:01 node-4 kernel: [    0.000063] Yama: becoming mindful.
Sep 28 21:08:01 node-4 kernel: [    0.001446] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.006332] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.008257] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.008285] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.008575] Initializing cgroup subsys memory
Sep 28 21:08:01 node-4 kernel: [    0.008584] Initializing cgroup subsys devices
Sep 28 21:08:01 node-4 kernel: [    0.008586] Initializing cgroup subsys freezer
Sep 28 21:08:01 node-4 kernel: [    0.008587] Initializing cgroup subsys blkio
Sep 28 21:08:01 node-4 kernel: [    0.008589] Initializing cgroup subsys perf_event
Sep 28 21:08:01 node-4 kernel: [    0.008591] Initializing cgroup subsys hugetlb
Sep 28 21:08:01 node-4 kernel: [    0.008611] CPU: Physical Processor ID: 0
Sep 28 21:08:01 node-4 kernel: [    0.008612] CPU: Processor Core ID: 0
Sep 28 21:08:01 node-4 kernel: [    0.008616] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 28 21:08:01 node-4 kernel: [    0.008616] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 28 21:08:01 node-4 kernel: [    0.009309] mce: CPU supports 22 MCE banks
Sep 28 21:08:01 node-4 kernel: [    0.009337] CPU0: Thermal monitoring enabled (TM1)
Sep 28 21:08:01 node-4 kernel: [    0.009357] process: using mwait in idle threads
Sep 28 21:08:01 node-4 kernel: [    0.009360] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 28 21:08:01 node-4 kernel: [    0.009360] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 28 21:08:01 node-4 kernel: [    0.009360] tlb_flushall_shift: 6
Sep 28 21:08:01 node-4 kernel: [    0.009449] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 28 21:08:01 node-4 kernel: [    0.010171] ACPI: Core revision 20131115
Sep 28 21:08:01 node-4 kernel: [    0.022854] ACPI: All ACPI Tables successfully acquired
Sep 28 21:08:01 node-4 kernel: [    0.023015] ftrace: allocating 28614 entries in 112 pages
Sep 28 21:08:01 node-4 kernel: [    0.031708] dmar: Host address width 46
Sep 28 21:08:01 node-4 kernel: [    0.031710] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 28 21:08:01 node-4 kernel: [    0.031716] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 28 21:08:01 node-4 kernel: [    0.031718] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 28 21:08:01 node-4 kernel: [    0.031722] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 28 21:08:01 node-4 kernel: [    0.031723] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 28 21:08:01 node-4 kernel: [    0.031725] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 28 21:08:01 node-4 kernel: [    0.031726] dmar: ATSR flags: 0x0
Sep 28 21:08:01 node-4 kernel: [    0.031727] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 28 21:08:01 node-4 kernel: [    0.031728] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 28 21:08:01 node-4 kernel: [    0.031843] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 28 21:08:01 node-4 kernel: [    0.031844] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 28 21:08:01 node-4 kernel: [    0.031845] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 28 21:08:01 node-4 kernel: [    0.031846] HPET id 0 under DRHD base 0xc7ffc000
Sep 28 21:08:01 node-4 kernel: [    0.031847] Your BIOS is broken and requested that x2apic be disabled.
Sep 28 21:08:01 node-4 kernel: [    0.031847] This will slightly decrease performance.
Sep 28 21:08:01 node-4 kernel: [    0.031847] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 28 21:08:01 node-4 kernel: [    0.032280] Enabled IRQ remapping in xapic mode
Sep 28 21:08:01 node-4 kernel: [    0.032281] x2apic not enabled, IRQ remapping is in xapic mode
Sep 28 21:08:01 node-4 kernel: [    0.032284] Switched APIC routing to physical flat.
Sep 28 21:08:01 node-4 kernel: [    0.032906] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 28 21:08:01 node-4 kernel: [    0.072554] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 28 21:08:01 node-4 kernel: [    0.072560] TSC deadline timer enabled
Sep 28 21:08:01 node-4 kernel: [    0.072568] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 28 21:08:01 node-4 kernel: [    0.072574] ... version:                3
Sep 28 21:08:01 node-4 kernel: [    0.072575] ... bit width:              48
Sep 28 21:08:01 node-4 kernel: [    0.072576] ... generic registers:      4
Sep 28 21:08:01 node-4 kernel: [    0.072577] ... value mask:             0000ffffffffffff
Sep 28 21:08:01 node-4 kernel: [    0.072577] ... max period:             0000ffffffffffff
Sep 28 21:08:01 node-4 kernel: [    0.072578] ... fixed-purpose events:   3
Sep 28 21:08:01 node-4 kernel: [    0.072579] ... event mask:             000000070000000f
Sep 28 21:08:01 node-4 kernel: [    0.073971] x86: Booting SMP configuration:
Sep 28 21:08:01 node-4 kernel: [    0.088085] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 28 21:08:01 node-4 kernel: [    0.073972] .... node  #0, CPUs:        #1  #2  #3
Sep 28 21:08:01 node-4 kernel: [    0.115991] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 28 21:08:01 node-4 kernel: [    0.270155] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 28 21:08:01 node-4 kernel: [    0.325774] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 28 21:08:01 node-4 kernel: [    0.382629] x86: Booted up 2 nodes, 16 CPUs
Sep 28 21:08:01 node-4 kernel: [    0.382633] smpboot: Total of 16 processors activated (111751.11 BogoMIPS)
Sep 28 21:08:01 node-4 kernel: [    0.406485] devtmpfs: initialized
Sep 28 21:08:01 node-4 kernel: [    0.408837] EVM: security.selinux
Sep 28 21:08:01 node-4 kernel: [    0.408839] EVM: security.SMACK64
Sep 28 21:08:01 node-4 kernel: [    0.408839] EVM: security.ima
Sep 28 21:08:01 node-4 kernel: [    0.408840] EVM: security.capability
Sep 28 21:08:01 node-4 kernel: [    0.408890] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.409542] pinctrl core: initialized pinctrl subsystem
Sep 28 21:08:01 node-4 kernel: [    0.409604] regulator-dummy: no parameters
Sep 28 21:08:01 node-4 kernel: [    0.409636] RTC time: 21:07:23, date: 09/28/16
Sep 28 21:08:01 node-4 kernel: [    0.409670] NET: Registered protocol family 16
Sep 28 21:08:01 node-4 kernel: [    0.409757] cpuidle: using governor ladder
Sep 28 21:08:01 node-4 kernel: [    0.409759] cpuidle: using governor menu
Sep 28 21:08:01 node-4 kernel: [    0.409795] ACPI: bus type PCI registered
Sep 28 21:08:01 node-4 kernel: [    0.409797] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 28 21:08:01 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 28 21:08:01 node-4 kernel: [    0.409843] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 28 21:08:01 node-4 kernel: [    0.409845] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 28 21:08:01 node-4 kernel: [    0.423614] PCI: Using configuration type 1 for base access
Sep 28 21:08:01 node-4 kernel: [    0.424612] bio: create slab <bio-0> at 0
Sep 28 21:08:01 node-4 kernel: [    0.424922] ACPI: Added _OSI(Module Device)
Sep 28 21:08:01 node-4 kernel: [    0.424924] ACPI: Added _OSI(Processor Device)
Sep 28 21:08:01 node-4 kernel: [    0.424925] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 28 21:08:01 node-4 kernel: [    0.424926] ACPI: Added _OSI(Processor Aggregator Device)
Sep 28 21:08:01 node-4 kernel: [    0.437743] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 28 21:08:01 node-4 kernel: [    0.448351] ACPI: Interpreter enabled
Sep 28 21:08:01 node-4 kernel: [    0.448357] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 28 21:08:01 node-4 kernel: [    0.448360] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 28 21:08:01 node-4 kernel: [    0.448363] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 28 21:08:01 node-4 kernel: [    0.448370] ACPI: (supports S0 S4 S5)
Sep 28 21:08:01 node-4 kernel: [    0.448372] ACPI: Using IOAPIC for interrupt routing
Sep 28 21:08:01 node-4 kernel: [    0.448413] HEST: Table parsing has been initialized.
Sep 28 21:08:01 node-4 kernel: [    0.448416] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 28 21:08:01 node-4 kernel: [    0.448991] ACPI: No dock devices found.
Sep 28 21:08:01 node-4 kernel: [    0.461097] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 28 21:08:01 node-4 kernel: [    0.461102] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 28 21:08:01 node-4 kernel: [    0.461105] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 28 21:08:01 node-4 kernel: [    0.461131] PCI host bridge to bus 0000:ff
Sep 28 21:08:01 node-4 kernel: [    0.461134] pci_bus 0000:ff: root bus resource [bus ff]
Sep 28 21:08:01 node-4 kernel: [    0.461142] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461180] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.461210] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461245] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461277] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.461306] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.461336] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461363] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461393] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461421] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461447] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461474] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461502] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461528] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461555] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461582] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461610] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461638] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461664] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.461692] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461719] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.461745] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461773] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461803] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.461838] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461870] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461900] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461931] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461962] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.461993] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462023] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462054] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462085] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462116] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462147] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462178] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462210] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462239] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462266] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462297] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462331] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462370] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462406] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462439] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462470] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462502] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462539] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462571] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462604] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462635] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462666] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462695] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462723] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462752] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462781] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462812] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462843] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462901] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 28 21:08:01 node-4 kernel: [    0.462904] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 28 21:08:01 node-4 kernel: [    0.462907] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 28 21:08:01 node-4 kernel: [    0.462925] PCI host bridge to bus 0000:7f
Sep 28 21:08:01 node-4 kernel: [    0.462926] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 28 21:08:01 node-4 kernel: [    0.462931] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.462958] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.462985] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463013] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463035] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.463058] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.463084] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463109] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463131] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463154] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463176] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463198] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463222] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463243] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463267] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463292] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463313] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463336] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463359] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.463382] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463404] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.463427] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463449] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463475] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 28 21:08:01 node-4 kernel: [    0.463508] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463534] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463560] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463586] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463611] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463639] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463666] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463694] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463719] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463745] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463773] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463800] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463829] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463855] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463880] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463908] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463933] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463959] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.463987] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464014] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464038] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464063] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464088] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464114] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464139] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464165] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464194] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464218] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464241] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464265] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464290] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464321] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.464346] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.465588] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 28 21:08:01 node-4 kernel: [    0.465592] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 28 21:08:01 node-4 kernel: [    0.466728] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 28 21:08:01 node-4 kernel: [    0.467237] PCI host bridge to bus 0000:00
Sep 28 21:08:01 node-4 kernel: [    0.467240] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 28 21:08:01 node-4 kernel: [    0.467241] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 28 21:08:01 node-4 kernel: [    0.467242] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 28 21:08:01 node-4 kernel: [    0.467244] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 28 21:08:01 node-4 kernel: [    0.467245] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 28 21:08:01 node-4 kernel: [    0.467246] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 28 21:08:01 node-4 kernel: [    0.467248] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 28 21:08:01 node-4 kernel: [    0.467253] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 28 21:08:01 node-4 kernel: [    0.467336] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.467367] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.467409] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 28 21:08:01 node-4 kernel: [    0.467428] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.467457] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.467497] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 28 21:08:01 node-4 kernel: [    0.467515] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.467545] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.467585] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 28 21:08:01 node-4 kernel: [    0.467602] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.467672] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.467748] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.467823] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 28 21:08:01 node-4 kernel: [    0.467828] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 28 21:08:01 node-4 kernel: [    0.467913] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 28 21:08:01 node-4 kernel: [    0.468056] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 28 21:08:01 node-4 kernel: [    0.468074] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 28 21:08:01 node-4 kernel: [    0.468151] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.468206] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 28 21:08:01 node-4 kernel: [    0.468228] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.468283] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.468327] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 28 21:08:01 node-4 kernel: [    0.468354] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.468410] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.468453] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 28 21:08:01 node-4 kernel: [    0.468477] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 28 21:08:01 node-4 kernel: [    0.468495] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 28 21:08:01 node-4 kernel: [    0.468572] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.468622] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 28 21:08:01 node-4 kernel: [    0.468648] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 28 21:08:01 node-4 kernel: [    0.468895] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 28 21:08:01 node-4 kernel: [    0.468901] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 28 21:08:01 node-4 kernel: [    0.468907] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.468913] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.468920] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 28 21:08:01 node-4 kernel: [    0.468951] pci 0000:01:00.0: supports D1 D2
Sep 28 21:08:01 node-4 kernel: [    0.478534] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 28 21:08:01 node-4 kernel: [    0.478540] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 28 21:08:01 node-4 kernel: [    0.478544] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 28 21:08:01 node-4 kernel: [    0.478809] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.478870] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 28 21:08:01 node-4 kernel: [    0.486531] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 28 21:08:01 node-4 kernel: [    0.486538] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.486542] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 28 21:08:01 node-4 kernel: [    0.486626] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.486699] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.486794] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.486876] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 28 21:08:01 node-4 kernel: [    0.486884] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.486888] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 28 21:08:01 node-4 kernel: [    0.486977] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.487100] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.487153] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 28 21:08:01 node-4 kernel: [    0.487156] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.487158] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 28 21:08:01 node-4 kernel: [    0.487206] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.487326] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.487363] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.487482] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.487520] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.487661] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.487699] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 28 21:08:01 node-4 kernel: [    0.487818] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 28 21:08:01 node-4 kernel: [    0.487860] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 28 21:08:01 node-4 kernel: [    0.487863] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.487865] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 28 21:08:01 node-4 kernel: [    0.487923] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 28 21:08:01 node-4 kernel: [    0.487986] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.488038] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.488083] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 28 21:08:01 node-4 kernel: [    0.488165] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 28 21:08:01 node-4 kernel: [    0.488271] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 28 21:08:01 node-4 kernel: [    0.488274] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.488276] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 28 21:08:01 node-4 kernel: [    0.488332] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 28 21:08:01 node-4 kernel: [    0.488385] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.488433] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.488668] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 28 21:08:01 node-4 kernel: [    0.488672] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 28 21:08:01 node-4 kernel: [    0.488734] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 28 21:08:01 node-4 kernel: [    0.488791] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.488839] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.489049] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 28 21:08:01 node-4 kernel: [    0.489053] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 28 21:08:01 node-4 kernel: [    0.489111] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 28 21:08:01 node-4 kernel: [    0.489173] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.489226] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 28 21:08:01 node-4 kernel: [    0.489448] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 28 21:08:01 node-4 kernel: [    0.489451] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 28 21:08:01 node-4 kernel: [    0.489627] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 28 21:08:01 node-4 kernel: [    0.489665] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 28 21:08:01 node-4 kernel: [    0.489741] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 28 21:08:01 node-4 kernel: [    0.489760] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 28 21:08:01 node-4 kernel: [    0.489773] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 28 21:08:01 node-4 kernel: [    0.489786] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 28 21:08:01 node-4 kernel: [    0.489836] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 28 21:08:01 node-4 kernel: [    0.494537] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 28 21:08:01 node-4 kernel: [    0.494546] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 28 21:08:01 node-4 kernel: [    0.494599] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 28 21:08:01 node-4 kernel: [    0.495347] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 28 21:08:01 node-4 kernel: [    0.495350] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 28 21:08:01 node-4 kernel: [    0.495469] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 28 21:08:01 node-4 kernel: [    0.495577] PCI host bridge to bus 0000:80
Sep 28 21:08:01 node-4 kernel: [    0.495579] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 28 21:08:01 node-4 kernel: [    0.495580] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 28 21:08:01 node-4 kernel: [    0.495582] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 28 21:08:01 node-4 kernel: [    0.495590] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.495653] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.495720] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 28 21:08:01 node-4 kernel: [    0.495782] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 28 21:08:01 node-4 kernel: [    0.495787] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 28 21:08:01 node-4 kernel: [    0.495860] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 28 21:08:01 node-4 kernel: [    0.496159] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 28 21:08:01 node-4 kernel: [    0.496190] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 28 21:08:01 node-4 kernel: [    0.496220] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 28 21:08:01 node-4 kernel: [    0.496249] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 28 21:08:01 node-4 kernel: [    0.496279] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 28 21:08:01 node-4 kernel: [    0.496309] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 28 21:08:01 node-4 kernel: [    0.496339] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 28 21:08:01 node-4 kernel: [    0.496369] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 28 21:08:01 node-4 kernel: [    0.496453] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 28 21:08:01 node-4 kernel: [    0.496458] ACPI: \_SB_.UNC1: notify handler is installed
Sep 28 21:08:01 node-4 kernel: [    0.496459] ACPI: \_SB_.UNC0: notify handler is installed
Sep 28 21:08:01 node-4 kernel: [    0.496474] ACPI: \_SB_.PCI0: notify handler is installed
Sep 28 21:08:01 node-4 kernel: [    0.496527] ACPI: \_SB_.PCI1: notify handler is installed
Sep 28 21:08:01 node-4 kernel: [    0.496607] Found 4 acpi root devices
Sep 28 21:08:01 node-4 kernel: [    0.496715] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 28 21:08:01 node-4 kernel: [    0.496717] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 28 21:08:01 node-4 kernel: [    0.496718] vgaarb: loaded
Sep 28 21:08:01 node-4 kernel: [    0.496720] vgaarb: bridge control possible 0000:0c:00.0
Sep 28 21:08:01 node-4 kernel: [    0.496837] SCSI subsystem initialized
Sep 28 21:08:01 node-4 kernel: [    0.496902] libata version 3.00 loaded.
Sep 28 21:08:01 node-4 kernel: [    0.496917] ACPI: bus type USB registered
Sep 28 21:08:01 node-4 kernel: [    0.496927] usbcore: registered new interface driver usbfs
Sep 28 21:08:01 node-4 kernel: [    0.496932] usbcore: registered new interface driver hub
Sep 28 21:08:01 node-4 kernel: [    0.496956] usbcore: registered new device driver usb
Sep 28 21:08:01 node-4 kernel: [    0.497121] PCI: Using ACPI for IRQ routing
Sep 28 21:08:01 node-4 kernel: [    0.500717] PCI: pci_cache_line_size set to 64 bytes
Sep 28 21:08:01 node-4 kernel: [    0.500918] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 28 21:08:01 node-4 kernel: [    0.500920] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 28 21:08:01 node-4 kernel: [    0.500920] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 28 21:08:01 node-4 kernel: [    0.500984] NetLabel: Initializing
Sep 28 21:08:01 node-4 kernel: [    0.500986] NetLabel:  domain hash size = 128
Sep 28 21:08:01 node-4 kernel: [    0.500986] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 28 21:08:01 node-4 kernel: [    0.500996] NetLabel:  unlabeled traffic allowed by default
Sep 28 21:08:01 node-4 kernel: [    0.501051] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 28 21:08:01 node-4 kernel: [    0.501055] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 28 21:08:01 node-4 kernel: [    0.503114] Switched to clocksource hpet
Sep 28 21:08:01 node-4 kernel: [    0.507017] AppArmor: AppArmor Filesystem Enabled
Sep 28 21:08:01 node-4 kernel: [    0.507030] pnp: PnP ACPI init
Sep 28 21:08:01 node-4 kernel: [    0.507036] ACPI: bus type PNP registered
Sep 28 21:08:01 node-4 kernel: [    0.507163] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 28 21:08:01 node-4 kernel: [    0.507171] pnp 00:01: [dma 4]
Sep 28 21:08:01 node-4 kernel: [    0.507182] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 28 21:08:01 node-4 kernel: [    0.507208] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 28 21:08:01 node-4 kernel: [    0.507228] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 28 21:08:01 node-4 kernel: [    0.507246] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 28 21:08:01 node-4 kernel: [    0.507278] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 28 21:08:01 node-4 kernel: [    0.507330] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507332] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 28 21:08:01 node-4 kernel: [    0.507334] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507335] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507337] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507342] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507344] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 28 21:08:01 node-4 kernel: [    0.507345] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507347] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507349] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507350] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507351] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507353] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 28 21:08:01 node-4 kernel: [    0.507355] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 28 21:08:01 node-4 kernel: [    0.507439] pnp 00:07: [dma 0 disabled]
Sep 28 21:08:01 node-4 kernel: [    0.507468] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 28 21:08:01 node-4 kernel: [    0.507543] pnp 00:08: [dma 0 disabled]
Sep 28 21:08:01 node-4 kernel: [    0.507576] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 28 21:08:01 node-4 kernel: [    0.507627] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 28 21:08:01 node-4 kernel: [    0.507976] pnp: PnP ACPI: found 10 devices
Sep 28 21:08:01 node-4 kernel: [    0.507978] ACPI: bus type PNP unregistered
Sep 28 21:08:01 node-4 kernel: [    0.514333] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 28 21:08:01 node-4 kernel: [    0.514336] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 28 21:08:01 node-4 kernel: [    0.514339] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 28 21:08:01 node-4 kernel: [    0.514343] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 28 21:08:01 node-4 kernel: [    0.514345] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.514360] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514389] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 28 21:08:01 node-4 kernel: [    0.514403] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514432] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 28 21:08:01 node-4 kernel: [    0.514450] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 28 21:08:01 node-4 kernel: [    0.514479] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 28 21:08:01 node-4 kernel: [    0.514494] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 28 21:08:01 node-4 kernel: [    0.514522] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 28 21:08:01 node-4 kernel: [    0.514524] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.514539] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514582] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 28 21:08:01 node-4 kernel: [    0.514584] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.514599] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514628] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 28 21:08:01 node-4 kernel: [    0.514629] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.514632] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514636] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 28 21:08:01 node-4 kernel: [    0.514638] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.514640] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514644] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 28 21:08:01 node-4 kernel: [    0.514649] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 28 21:08:01 node-4 kernel: [    0.514657] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 28 21:08:01 node-4 kernel: [    0.514660] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 28 21:08:01 node-4 kernel: [    0.514667] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 28 21:08:01 node-4 kernel: [    0.514668] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 28 21:08:01 node-4 kernel: [    0.514668] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 28 21:08:01 node-4 kernel: [    0.514669] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 28 21:08:01 node-4 kernel: [    0.514670] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 28 21:08:01 node-4 kernel: [    0.514671] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 28 21:08:01 node-4 kernel: [    0.514672] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 28 21:08:01 node-4 kernel: [    0.514673] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 28 21:08:01 node-4 kernel: [    0.514674] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.514675] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514676] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.514677] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514677] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.514678] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514679] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.514680] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514681] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 28 21:08:01 node-4 kernel: [    0.514682] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514683] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 28 21:08:01 node-4 kernel: [    0.514684] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 28 21:08:01 node-4 kernel: [    0.514685] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 28 21:08:01 node-4 kernel: [    0.514686] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 28 21:08:01 node-4 kernel: [    0.514688] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 28 21:08:01 node-4 kernel: [    0.514689] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 28 21:08:01 node-4 kernel: [    0.514728] NET: Registered protocol family 2
Sep 28 21:08:01 node-4 kernel: [    0.514998] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.515334] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.515475] TCP: Hash tables configured (established 262144 bind 65536)
Sep 28 21:08:01 node-4 kernel: [    0.515518] TCP: reno registered
Sep 28 21:08:01 node-4 kernel: [    0.515546] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.515641] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.515786] NET: Registered protocol family 1
Sep 28 21:08:01 node-4 kernel: [    0.555213] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 28 21:08:01 node-4 kernel: [    0.555228] PCI: CLS 64 bytes, default 64
Sep 28 21:08:01 node-4 kernel: [    0.555306] Trying to unpack rootfs image as initramfs...
Sep 28 21:08:01 node-4 kernel: [    0.774000] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep 28 21:08:01 node-4 kernel: [    0.774053] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 28 21:08:01 node-4 kernel: [    0.774056] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 28 21:08:01 node-4 kernel: [    0.774464] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774470] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774474] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774480] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774491] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774508] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774523] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774538] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774550] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774559] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774565] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774572] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774580] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774602] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774610] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774617] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 28 21:08:01 node-4 kernel: [    0.774691] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 28 21:08:01 node-4 kernel: [    0.774694] Scanning for low memory corruption every 60 seconds
Sep 28 21:08:01 node-4 kernel: [    0.775088] Initialise system trusted keyring
Sep 28 21:08:01 node-4 kernel: [    0.775139] audit: initializing netlink socket (disabled)
Sep 28 21:08:01 node-4 kernel: [    0.775155] type=2000 audit(1475096843.728:1): initialized
Sep 28 21:08:01 node-4 kernel: [    0.792897] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 28 21:08:01 node-4 kernel: [    0.794405] zbud: loaded
Sep 28 21:08:01 node-4 kernel: [    0.794530] VFS: Disk quotas dquot_6.5.2
Sep 28 21:08:01 node-4 kernel: [    0.794565] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 28 21:08:01 node-4 kernel: [    0.794961] fuse init (API version 7.22)
Sep 28 21:08:01 node-4 kernel: [    0.795021] msgmni has been set to 32768
Sep 28 21:08:01 node-4 kernel: [    0.795073] Key type big_key registered
Sep 28 21:08:01 node-4 kernel: [    0.795600] Key type asymmetric registered
Sep 28 21:08:01 node-4 kernel: [    0.795602] Asymmetric key parser 'x509' registered
Sep 28 21:08:01 node-4 kernel: [    0.795624] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 28 21:08:01 node-4 kernel: [    0.795689] io scheduler noop registered
Sep 28 21:08:01 node-4 kernel: [    0.795691] io scheduler deadline registered (default)
Sep 28 21:08:01 node-4 kernel: [    0.795710] io scheduler cfq registered
Sep 28 21:08:01 node-4 kernel: [    0.796224] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    0.796399] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    0.796512] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    0.796629] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    0.796745] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    0.796842] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    0.797232] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 28 21:08:01 node-4 kernel: [    0.797258] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 28 21:08:01 node-4 kernel: [    0.797274] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 28 21:08:01 node-4 kernel: [    0.797284] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797286] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797289] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 28 21:08:01 node-4 kernel: [    0.797294] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797295] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797297] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797298] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797299] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797301] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797302] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797303] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797305] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797306] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797307] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797309] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797311] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 28 21:08:01 node-4 kernel: [    0.797323] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797325] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 28 21:08:01 node-4 kernel: [    0.797341] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797344] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 28 21:08:01 node-4 kernel: [    0.797354] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797356] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 28 21:08:01 node-4 kernel: [    0.797359] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 28 21:08:01 node-4 kernel: [    0.797397] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 28 21:08:01 node-4 kernel: [    0.797404] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 28 21:08:01 node-4 kernel: [    0.797408] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 28 21:08:01 node-4 kernel: [    0.797418] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 28 21:08:01 node-4 kernel: [    0.797458] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 28 21:08:01 node-4 kernel: [    0.797460] vesafb: scrolling: redraw
Sep 28 21:08:01 node-4 kernel: [    0.797461] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 28 21:08:01 node-4 kernel: [    0.818316] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 28 21:08:01 node-4 kernel: [    0.826817] Console: switching to colour frame buffer device 80x30
Sep 28 21:08:01 node-4 kernel: [    0.835490] fb0: VESA VGA frame buffer device
Sep 28 21:08:01 node-4 kernel: [    0.835687] intel_idle: MWAIT substates: 0x2120
Sep 28 21:08:01 node-4 kernel: [    0.835688] intel_idle: v0.4 model 0x3F
Sep 28 21:08:01 node-4 kernel: [    0.835689] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 28 21:08:01 node-4 kernel: [    0.835927] ipmi message handler version 39.2
Sep 28 21:08:01 node-4 kernel: [    0.836201] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 28 21:08:01 node-4 kernel: [    0.836634] ACPI: AC Adapter [P111] (on-line)
Sep 28 21:08:01 node-4 kernel: [    0.841848] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 28 21:08:01 node-4 kernel: [    0.852865] ACPI: Power Button [PWRB]
Sep 28 21:08:01 node-4 kernel: [    0.858628] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 28 21:08:01 node-4 kernel: [    0.870255] ACPI: Power Button [PWRF]
Sep 28 21:08:01 node-4 kernel: [    0.896639] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 28 21:08:01 node-4 kernel: [    0.908289] pstore: Registered erst as persistent store backend
Sep 28 21:08:01 node-4 kernel: [    0.914489] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 28 21:08:01 node-4 kernel: [    0.926410] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 28 21:08:01 node-4 kernel: [    0.953160] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 28 21:08:01 node-4 kernel: [    0.986419] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 28 21:08:01 node-4 kernel: [    1.000450] Linux agpgart interface v0.103
Sep 28 21:08:01 node-4 kernel: [    1.008065] brd: module loaded
Sep 28 21:08:01 node-4 kernel: [    1.015094] loop: module loaded
Sep 28 21:08:01 node-4 kernel: [    1.021812] libphy: Fixed MDIO Bus: probed
Sep 28 21:08:01 node-4 kernel: [    1.028338] tun: Universal TUN/TAP device driver, 1.6
Sep 28 21:08:01 node-4 kernel: [    1.034887] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 28 21:08:01 node-4 kernel: [    1.041392] PPP generic driver version 2.4.2
Sep 28 21:08:01 node-4 kernel: [    1.047760] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 28 21:08:01 node-4 kernel: [    1.054197] ehci-pci: EHCI PCI platform driver
Sep 28 21:08:01 node-4 kernel: [    1.060697] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 28 21:08:01 node-4 kernel: [    1.067084] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 28 21:08:01 node-4 kernel: [    1.079559] ehci-pci 0000:00:1a.0: debug port 2
Sep 28 21:08:01 node-4 kernel: [    1.089728] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 28 21:08:01 node-4 kernel: [    1.089747] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 28 21:08:01 node-4 kernel: [    1.106603] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 28 21:08:01 node-4 kernel: [    1.112655] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 28 21:08:01 node-4 kernel: [    1.118812] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 28 21:08:01 node-4 kernel: [    1.130674] usb usb1: Product: EHCI Host Controller
Sep 28 21:08:01 node-4 kernel: [    1.136700] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Sep 28 21:08:01 node-4 kernel: [    1.142734] usb usb1: SerialNumber: 0000:00:1a.0
Sep 28 21:08:01 node-4 kernel: [    1.148663] hub 1-0:1.0: USB hub found
Sep 28 21:08:01 node-4 kernel: [    1.154408] hub 1-0:1.0: 2 ports detected
Sep 28 21:08:01 node-4 kernel: [    1.160181] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 28 21:08:01 node-4 kernel: [    1.165749] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 28 21:08:01 node-4 kernel: [    1.176621] ehci-pci 0000:00:1d.0: debug port 2
Sep 28 21:08:01 node-4 kernel: [    1.185894] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 28 21:08:01 node-4 kernel: [    1.185900] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 28 21:08:01 node-4 kernel: [    1.202522] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 28 21:08:01 node-4 kernel: [    1.207735] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 28 21:08:01 node-4 kernel: [    1.213038] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 28 21:08:01 node-4 kernel: [    1.223616] usb usb2: Product: EHCI Host Controller
Sep 28 21:08:01 node-4 kernel: [    1.229083] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Sep 28 21:08:01 node-4 kernel: [    1.234628] usb usb2: SerialNumber: 0000:00:1d.0
Sep 28 21:08:01 node-4 kernel: [    1.240149] hub 2-0:1.0: USB hub found
Sep 28 21:08:01 node-4 kernel: [    1.245503] hub 2-0:1.0: 2 ports detected
Sep 28 21:08:01 node-4 kernel: [    1.250808] ehci-platform: EHCI generic platform driver
Sep 28 21:08:01 node-4 kernel: [    1.256056] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 28 21:08:01 node-4 kernel: [    1.261376] ohci-pci: OHCI PCI platform driver
Sep 28 21:08:01 node-4 kernel: [    1.266677] ohci-platform: OHCI generic platform driver
Sep 28 21:08:01 node-4 kernel: [    1.271883] uhci_hcd: USB Universal Host Controller Interface driver
Sep 28 21:08:01 node-4 kernel: [    1.277225] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 28 21:08:01 node-4 kernel: [    1.474296] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 28 21:08:01 node-4 kernel: [    1.770054] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 28 21:08:01 node-4 kernel: [    1.786371] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 28 21:08:01 node-4 kernel: [    1.791981] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 28 21:08:01 node-4 kernel: [    1.797764] hub 1-1:1.0: USB hub found
Sep 28 21:08:01 node-4 kernel: [    1.803358] hub 1-1:1.0: 6 ports detected
Sep 28 21:08:01 node-4 kernel: [    1.917938] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 28 21:08:01 node-4 kernel: [    2.315893] i8042: No controller found
Sep 28 21:08:01 node-4 kernel: [    2.321416] mousedev: PS/2 mouse device common for all mice
Sep 28 21:08:01 node-4 kernel: [    2.327132] rtc_cmos 00:02: RTC can wake from S4
Sep 28 21:08:01 node-4 kernel: [    2.330350] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 28 21:08:01 node-4 kernel: [    2.330351] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 28 21:08:01 node-4 kernel: [    2.330998] hub 2-1:1.0: USB hub found
Sep 28 21:08:01 node-4 kernel: [    2.331230] hub 2-1:1.0: 8 ports detected
Sep 28 21:08:01 node-4 kernel: [    2.355375] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 28 21:08:01 node-4 kernel: [    2.361124] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 28 21:08:01 node-4 kernel: [    2.372434] device-mapper: uevent: version 1.0.3
Sep 28 21:08:01 node-4 kernel: [    2.378144] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 28 21:08:01 node-4 kernel: [    2.389508] ledtrig-cpu: registered to indicate activity on CPUs
Sep 28 21:08:01 node-4 kernel: [    2.395474] TCP: cubic registered
Sep 28 21:08:01 node-4 kernel: [    2.401345] NET: Registered protocol family 10
Sep 28 21:08:01 node-4 kernel: [    2.407413] NET: Registered protocol family 17
Sep 28 21:08:01 node-4 kernel: [    2.413176] Key type dns_resolver registered
Sep 28 21:08:01 node-4 kernel: [    2.419222] Loading compiled-in X.509 certificates
Sep 28 21:08:01 node-4 kernel: [    2.425439] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Sep 28 21:08:01 node-4 kernel: [    2.437073] registered taskstats version 1
Sep 28 21:08:01 node-4 kernel: [    2.445122] Key type trusted registered
Sep 28 21:08:01 node-4 kernel: [    2.452728] Key type encrypted registered
Sep 28 21:08:01 node-4 kernel: [    2.458238] AppArmor: AppArmor sha1 policy hashing enabled
Sep 28 21:08:01 node-4 kernel: [    2.463757] IMA: No TPM chip found, activating TPM-bypass!
Sep 28 21:08:01 node-4 kernel: [    2.469869] regulator-dummy: disabling
Sep 28 21:08:01 node-4 kernel: [    2.475352]   Magic number: 0:417:147
Sep 28 21:08:01 node-4 kernel: [    2.480938] acpi device:18: hash matches
Sep 28 21:08:01 node-4 kernel: [    2.486491] rtc_cmos 00:02: setting system clock to 2016-09-28 21:07:25 UTC (1475096845)
Sep 28 21:08:01 node-4 kernel: [    2.498872] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 28 21:08:01 node-4 kernel: [    2.504493] EDD information not available.
Sep 28 21:08:01 node-4 kernel: [    2.510029] PM: Hibernation image not present or could not be loaded.
Sep 28 21:08:01 node-4 kernel: [    2.510903] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 28 21:08:01 node-4 kernel: [    2.522130] Write protecting the kernel read-only data: 12288k
Sep 28 21:08:01 node-4 kernel: [    2.528493] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 28 21:08:01 node-4 kernel: [    2.541304] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 28 21:08:01 node-4 kernel: [    2.573908] device-mapper: multipath: version 1.6.0 loaded
Sep 28 21:08:01 node-4 kernel: [    2.581677] systemd-udevd[216]: starting version 204
Sep 28 21:08:01 node-4 kernel: [    2.605201] md: linear personality registered for level -1
Sep 28 21:08:01 node-4 kernel: [    2.613497] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 28 21:08:01 node-4 kernel: [    2.625867] md: multipath personality registered for level -4
Sep 28 21:08:01 node-4 kernel: [    2.634146] md: raid0 personality registered for level 0
Sep 28 21:08:01 node-4 kernel: [    2.642470] md: raid1 personality registered for level 1
Sep 28 21:08:01 node-4 kernel: [    2.650648] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 28 21:08:01 node-4 kernel: [    2.657001] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 28 21:08:01 node-4 kernel: [    2.663264] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 28 21:08:01 node-4 kernel: [    2.669778] megasas: FW now in Ready state
Sep 28 21:08:01 node-4 kernel: [    2.676191] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676195] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676199] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676204] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676208] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676213] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676217] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676221] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676225] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676229] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676234] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676238] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676247] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676252] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676256] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676262] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.676300] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 28 21:08:01 node-4 kernel: [    2.682292] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Sep 28 21:08:01 node-4 kernel: [    2.682304] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 28 21:08:01 node-4 kernel: [    2.682305] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 28 21:08:01 node-4 kernel: [    2.682823] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.682983] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.683051] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.683243] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.683436] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.701821] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Sep 28 21:08:01 node-4 kernel: [    2.701822] 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
Sep 28 21:08:01 node-4 kernel: [    2.701823] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 28 21:08:01 node-4 kernel: [    2.702158] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.702294] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.702449] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.702653] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.702738] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.702869] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.703117] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.720581] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Sep 28 21:08:01 node-4 kernel: [    2.720598] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 28 21:08:01 node-4 kernel: [    2.720617] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 28 21:08:01 node-4 kernel: [    2.721023] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.721171] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.722842] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.723021] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.723508] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.729411] raid6: sse2x1    3329 MB/s
Sep 28 21:08:01 node-4 kernel: [    2.740987] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Sep 28 21:08:01 node-4 kernel: [    2.740988] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Sep 28 21:08:01 node-4 kernel: [    2.740990] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 28 21:08:01 node-4 kernel: [    2.759464] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.759499] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.759545] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.759601] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.759695] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 28 21:08:01 node-4 kernel: [    2.797459] raid6: sse2x2   10961 MB/s
Sep 28 21:08:01 node-4 kernel: [    2.865351] raid6: sse2x4    9542 MB/s
Sep 28 21:08:01 node-4 kernel: [    2.933062] raid6: avx2x1   14373 MB/s
Sep 28 21:08:01 node-4 kernel: [    3.004999] raid6: avx2x2   18870 MB/s
Sep 28 21:08:01 node-4 kernel: [    3.076947] raid6: avx2x4   21381 MB/s
Sep 28 21:08:01 node-4 kernel: [    3.082843] raid6: using algorithm avx2x4 (21381 MB/s)
Sep 28 21:08:01 node-4 kernel: [    3.088882] raid6: using avx2x2 recovery algorithm
Sep 28 21:08:01 node-4 kernel: [    3.094782] Switched to clocksource tsc
Sep 28 21:08:01 node-4 kernel: [    3.101283] xor: automatically using best checksumming function:
Sep 28 21:08:01 node-4 kernel: [    3.144863]    avx       : 35726.000 MB/sec
Sep 28 21:08:01 node-4 kernel: [    3.149001] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 28 21:08:01 node-4 kernel: [    3.149002] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 28 21:08:01 node-4 kernel: [    3.149003] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 28 21:08:01 node-4 kernel: [    3.149003] usb 2-1.4: Manufacturer: Avocent
Sep 28 21:08:01 node-4 kernel: [    3.149004] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 28 21:08:01 node-4 kernel: [    3.184040] hidraw: raw HID events driver (C) Jiri Kosina
Sep 28 21:08:01 node-4 kernel: [    3.189381] async_tx: api initialized (async)
Sep 28 21:08:01 node-4 kernel: [    3.196345] usbcore: registered new interface driver usbhid
Sep 28 21:08:01 node-4 kernel: [    3.201501] usbhid: USB HID core driver
Sep 28 21:08:01 node-4 kernel: [    3.207608] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Sep 28 21:08:01 node-4 kernel: [    3.218411] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Sep 28 21:08:01 node-4 kernel: [    3.218548] md: raid6 personality registered for level 6
Sep 28 21:08:01 node-4 kernel: [    3.218549] md: raid5 personality registered for level 5
Sep 28 21:08:01 node-4 kernel: [    3.218549] md: raid4 personality registered for level 4
Sep 28 21:08:01 node-4 kernel: [    3.245240] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Sep 28 21:08:01 node-4 kernel: [    3.255734] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Sep 28 21:08:01 node-4 kernel: [    3.266812] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Sep 28 21:08:01 node-4 kernel: [    3.278717] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Sep 28 21:08:01 node-4 kernel: [    3.291509] md: raid10 personality registered for level 10
Sep 28 21:08:01 node-4 kernel: [    3.346602] multipathd (356): /proc/356/oom_adj is deprecated, please use /proc/356/oom_score_adj instead.
Sep 28 21:08:01 node-4 kernel: [    3.456649] megasas:IOC Init cmd success
Sep 28 21:08:01 node-4 kernel: [    3.484644] megasas: INIT adapter done
Sep 28 21:08:01 node-4 kernel: [    3.584545] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 28 21:08:01 node-4 kernel: [    3.591507] scsi0 : LSI SAS based MegaRAID driver
Sep 28 21:08:01 node-4 kernel: [    3.599000] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 28 21:08:01 node-4 kernel: [    3.625176] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 28 21:08:01 node-4 kernel: [    3.640973] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 28 21:08:01 node-4 kernel: [    3.647498] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 28 21:08:01 node-4 kernel: [    3.661072] sd 0:2:0:0: [sda] Write Protect is off
Sep 28 21:08:01 node-4 kernel: [    3.667806] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 28 21:08:01 node-4 kernel: [    3.667826] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 28 21:08:01 node-4 kernel: [    3.707816]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 28 21:08:01 node-4 kernel: [    3.714910] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 28 21:08:01 node-4 kernel: [    3.837261] random: lvm urandom read with 27 bits of entropy available
Sep 28 21:08:01 node-4 kernel: [    3.988609] bio: create slab <bio-1> at 1
Sep 28 21:08:01 node-4 kernel: [    4.881393] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Sep 28 21:08:01 node-4 kernel: [    5.622506] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Sep 28 21:08:01 node-4 kernel: [    5.649815] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 28 21:08:01 node-4 kernel: [    5.662195] random: nonblocking pool is initialized
Sep 28 21:08:01 node-4 kernel: [    5.798257] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 28 21:08:01 node-4 kernel: [    5.852136] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 28 21:08:01 node-4 kernel: [    5.933770] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 28 21:08:01 node-4 kernel: [    6.120407] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 28 21:08:01 node-4 kernel: [    6.152372] XFS (dm-1): Mounting Filesystem
Sep 28 21:08:01 node-4 kernel: [    6.473987] XFS (dm-1): Ending clean mount
Sep 28 21:08:01 node-4 kernel: [    6.520580] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 28 21:08:01 node-4 kernel: [    6.563631] XFS (dm-2): Mounting Filesystem
Sep 28 21:08:01 node-4 kernel: [    6.643992] XFS (dm-2): Ending clean mount
Sep 28 21:08:01 node-4 kernel: [    6.751612] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Sep 28 21:08:01 node-4 kernel: [    8.409584] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 28 21:08:01 node-4 kernel: [    8.424311] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 28 21:08:01 node-4 kernel: [    8.552476] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 28 21:08:01 node-4 kernel: [    8.552482] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 28 21:08:01 node-4 kernel: [    8.552486] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 28 21:08:01 node-4 kernel: [    8.552490] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 28 21:08:01 node-4 kernel: [    8.579938] systemd-udevd[803]: starting version 204
Sep 28 21:08:01 node-4 kernel: [    8.777986] power_meter ACPI000D:00: Found ACPI power meter.
Sep 28 21:08:01 node-4 kernel: [    8.778002] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 28 21:08:01 node-4 kernel: [    8.793896] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 28 21:08:01 node-4 kernel: [    8.793901] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 28 21:08:01 node-4 kernel: [    8.793904] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 28 21:08:01 node-4 kernel: [    8.793906] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 28 21:08:01 node-4 kernel: [    8.793918] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 28 21:08:01 node-4 kernel: [    8.799212] IPMI System Interface driver.
Sep 28 21:08:01 node-4 kernel: [    8.799245] ipmi_si: probing via ACPI
Sep 28 21:08:01 node-4 kernel: [    8.799264] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 28 21:08:01 node-4 kernel: [    8.799265] ipmi_si: Adding ACPI-specified kcs state machine
Sep 28 21:08:01 node-4 kernel: [    8.799274] ipmi_si: probing via SMBIOS
Sep 28 21:08:01 node-4 kernel: [    8.799275] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 28 21:08:01 node-4 kernel: [    8.799275] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 28 21:08:01 node-4 kernel: [    8.799277] ipmi_si: probing via SPMI
Sep 28 21:08:01 node-4 kernel: [    8.799278] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 28 21:08:01 node-4 kernel: [    8.799278] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 28 21:08:01 node-4 kernel: [    8.799279] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 28 21:08:01 node-4 kernel: [    8.809029] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 28 21:08:01 node-4 kernel: [    8.814359] wmi: Mapper loaded
Sep 28 21:08:01 node-4 kernel: [    8.872494] systemd-udevd[824]: renamed network interface eth0 to enp6s0
Sep 28 21:08:01 node-4 kernel: [    8.904363] systemd-udevd[853]: renamed network interface eth3 to enp9s0
Sep 28 21:08:01 node-4 kernel: [    8.940388] systemd-udevd[852]: renamed network interface eth1 to enp7s0
Sep 28 21:08:01 node-4 kernel: [    8.943172] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 28 21:08:01 node-4 kernel: [    8.943177] ipmi_si 00:09: IPMI kcs interface initialized
Sep 28 21:08:01 node-4 kernel: [    8.964313] systemd-udevd[854]: renamed network interface eth2 to enp8s0
Sep 28 21:08:01 node-4 kernel: [    9.205896] type=1400 audit(1475096852.221:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1070 comm="apparmor_parser"
Sep 28 21:08:01 node-4 kernel: [    9.206054] type=1400 audit(1475096852.221:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1070 comm="apparmor_parser"
Sep 28 21:08:01 node-4 kernel: [    9.206185] type=1400 audit(1475096852.221:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1070 comm="apparmor_parser"
Sep 28 21:08:01 node-4 kernel: [    9.213052] type=1400 audit(1475096852.229:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1071 comm="apparmor_parser"
Sep 28 21:08:01 node-4 kernel: [    9.213197] type=1400 audit(1475096852.229:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1071 comm="apparmor_parser"
Sep 28 21:08:01 node-4 kernel: [    9.213320] type=1400 audit(1475096852.229:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1071 comm="apparmor_parser"
Sep 28 21:08:01 node-4 kernel: [    9.218527] type=1400 audit(1475096852.233:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1072 comm="apparmor_parser"
Sep 28 21:08:01 node-4 kernel: [    9.218666] type=1400 audit(1475096852.233:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1072 comm="apparmor_parser"
Sep 28 21:08:01 node-4 kernel: [    9.218787] type=1400 audit(1475096852.233:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1072 comm="apparmor_parser"
Sep 28 21:08:01 node-4 kernel: [    9.226048] type=1400 audit(1475096852.241:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1069 comm="apparmor_parser"
Sep 28 21:08:01 node-4 kernel: [    9.726032] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 28 21:08:01 node-4 kernel: [    9.734705] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 28 21:08:01 node-4 kernel: [    9.938995] enic 0000:06:00.0 enp6s0: Link UP
Sep 28 21:08:01 node-4 kernel: [    9.939932] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 28 21:08:01 node-4 kernel: [    9.939942] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 28 21:08:01 node-4 kernel: [   20.147415] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 28 21:08:01 node-4 failsafe: Failsafe of 120 seconds reached.
Sep 28 21:08:02 node-4 kernel: [   38.817935] init: failsafe main process (8452) killed by TERM signal
Sep 28 21:08:02 node-4 dbus[8484]: [system] AppArmor D-Bus mediation is enabled
Sep 28 21:08:02 node-4 kernel: [   39.024950] audit_printk_skb: 30 callbacks suppressed
Sep 28 21:08:02 node-4 kernel: [   39.024950] type=1400 audit(1475096882.231:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8580 comm="apparmor_parser"
Sep 28 21:08:02 node-4 kernel: [   39.025037] type=1400 audit(1475096882.231:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8579 comm="apparmor_parser"
Sep 28 21:08:02 node-4 kernel: [   39.025040] type=1400 audit(1475096882.231:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8579 comm="apparmor_parser"
Sep 28 21:08:02 node-4 kernel: [   39.025042] type=1400 audit(1475096882.231:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8579 comm="apparmor_parser"
Sep 28 21:08:02 node-4 kernel: [   39.025261] type=1400 audit(1475096882.231:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8579 comm="apparmor_parser"
Sep 28 21:08:02 node-4 kernel: [   39.025263] type=1400 audit(1475096882.231:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8579 comm="apparmor_parser"
Sep 28 21:08:02 node-4 kernel: [   39.025387] type=1400 audit(1475096882.231:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8579 comm="apparmor_parser"
Sep 28 21:08:02 node-4 kernel: [   39.116667] type=1400 audit(1475096882.323:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8582 comm="apparmor_parser"
Sep 28 21:08:02 node-4 anacron[8644]: Anacron 2.3 started on 2016-09-28
Sep 28 21:08:02 node-4 anacron[8644]: Will run job `cron.daily' in 5 min.
Sep 28 21:08:02 node-4 anacron[8644]: Will run job `cron.weekly' in 10 min.
Sep 28 21:08:02 node-4 anacron[8644]: Will run job `cron.monthly' in 15 min.
Sep 28 21:08:02 node-4 anacron[8644]: Jobs will be executed sequentially
Sep 28 21:08:02 node-4 cron[8610]: (CRON) INFO (pidfile fd = 3)
Sep 28 21:08:02 node-4 cron[8652]: (CRON) STARTUP (fork ok)
Sep 28 21:08:02 node-4 multipathd: path checkers start up
Sep 28 21:08:02 node-4 cron[8652]: (CRON) INFO (Running @reboot jobs)
Sep 28 21:08:02 node-4 postfix/master[8789]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 28 21:08:06 node-4 puppet-agent[8973]: Reopening log files
Sep 28 21:08:07 node-4 puppet-agent[8973]: Could not request certificate: Connection refused - connect(2)
Sep 28 21:08:18 node-4 puppet-user[9052]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 28 21:08:18 node-4 puppet-user[9052]: Compiled catalog for node-4.domain.tld in environment production in 0.05 seconds
Sep 28 21:08:19 node-4 puppet-user[9052]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 28 21:08:19 node-4 puppet-user[9052]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 28 21:08:19 node-4 puppet-user[9052]: Finished catalog run in 0.45 seconds
Sep 28 21:08:20 node-4 multipathd: uevent trigger error
Sep 28 21:08:20 node-4 puppet-user[9606]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 28 21:08:20 node-4 puppet-user[9606]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Sep 28 21:08:21 node-4 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 28 21:08:21 node-4 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 28 21:08:21 node-4 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Sep 28 21:08:21 node-4 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 28 21:08:21 node-4 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 28 21:08:21 node-4 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 28 21:08:21 node-4 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 28 21:08:21 node-4 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 28 21:08:21 node-4 puppet-user[9606]: Finished catalog run in 0.09 seconds
Sep 28 21:08:22 node-4 puppet-user[10074]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 28 21:08:22 node-4 puppet-user[10074]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Sep 28 21:08:22 node-4 puppet-user[10074]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 28 21:08:22 node-4 puppet-user[10074]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 28 21:08:22 node-4 puppet-user[10074]: Finished catalog run in 0.04 seconds
Sep 28 21:08:24 node-4 puppet-user[10539]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 28 21:08:24 node-4 puppet-user[10539]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Sep 28 21:08:24 node-4 puppet-user[10539]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 28 21:08:24 node-4 puppet-user[10539]: Finished catalog run in 0.03 seconds
Sep 28 21:08:26 node-4 puppet-user[11000]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 28 21:08:26 node-4 puppet-user[11000]: Compiled catalog for node-4.domain.tld in environment production in 0.20 seconds
Sep 28 21:08:26 node-4 puppet-user[11000]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 28 21:08:26 node-4 kernel: [   63.257299] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 28 21:08:26 node-4 kernel: [   63.257351] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Sep 28 21:08:26 node-4 puppet-user[11000]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Sep 28 21:08:26 node-4 puppet-user[11000]: Finished catalog run in 0.05 seconds
Sep 28 21:08:28 node-4 puppet-user[11472]: (Scope(Class[main])) MODULAR: sync_time
Sep 28 21:08:28 node-4 puppet-user[11472]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Sep 28 21:08:28 node-4 ntpdate[11889]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 28 21:08:34 node-4 ntpdate[11889]: adjust time server 10.20.0.2 offset -0.073097 sec
Sep 28 21:08:34 node-4 puppet-user[11472]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 28 21:08:34 node-4 puppet-user[11472]: Finished catalog run in 6.19 seconds
Sep 28 21:08:40 node-4 puppet-user[12269]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 28 21:08:40 node-4 puppet-user[12269]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Sep 28 21:08:41 node-4 puppet-user[12269]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 28 21:08:41 node-4 puppet-user[12269]: Finished catalog run in 0.06 seconds
Sep 28 21:08:42 node-4 puppet-user[12723]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 28 21:08:43 node-4 puppet-user[12723]: Compiled catalog for node-4.domain.tld in environment production in 0.55 seconds
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 28 21:08:43 node-4 puppet-user[12723]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 28 21:08:43 node-4 kernel: [   80.348321] init: plymouth-upstart-bridge main process ended, respawning
Sep 28 21:08:43 node-4 puppet-agent[8973]: Could not run: SIGTERM
Sep 28 21:08:43 node-4 kernel: [   80.621751] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 28 21:08:43 node-4 ec2: 
Sep 28 21:08:43 node-4 ec2: #############################################################
Sep 28 21:08:43 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 28 21:08:43 node-4 ec2: 1024 b1:2d:f6:84:1c:93:76:ec:45:5a:77:62:d5:53:d2:0e  root@node-4.domain.tld (DSA)
Sep 28 21:08:43 node-4 ec2: 256 5e:a5:ef:be:85:37:2a:41:49:ea:2a:ba:21:f3:cf:d2  root@node-4.domain.tld (ECDSA)
Sep 28 21:08:43 node-4 ec2: 256 3a:0a:ac:29:df:4e:a9:e1:18:01:e9:84:95:7d:f6:20  root@node-4.domain.tld (ED25519)
Sep 28 21:08:43 node-4 ec2: 2048 3c:70:89:f5:d0:72:3e:b8:43:ad:18:a0:f0:39:70:21  root@node-4.domain.tld (RSA)
Sep 28 21:08:43 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 28 21:08:43 node-4 ec2: #############################################################
Sep 28 21:08:44 node-4 puppet-user[12723]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 28 21:08:44 node-4 puppet-user[12723]: Finished catalog run in 0.91 seconds
Sep 28 21:08:45 node-4 puppet-user[13404]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 28 21:08:45 node-4 puppet-user[13404]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Sep 28 21:08:49 node-4 puppet-user[13404]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 28 21:09:01 node-4 CRON[14961]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Sep 28 21:09:18 node-4 puppet-user[13404]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 28 21:09:18 node-4 puppet-user[13404]: Finished catalog run in 32.57 seconds
Sep 28 21:09:20 node-4 puppet-user[15882]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 28 21:09:20 node-4 puppet-user[15882]: Compiled catalog for node-4.domain.tld in environment production in 0.61 seconds
Sep 28 21:09:21 node-4 puppet-user[15882]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 28 21:09:21 node-4 puppet-user[15882]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 28 21:09:21 node-4 puppet-user[15882]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 28 21:09:21 node-4 puppet-user[15882]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 28 21:09:21 node-4 puppet-user[15882]: Finished catalog run in 0.10 seconds
Sep 28 21:09:22 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 28 21:09:22 node-4 nailgun-agent: I, [2016-09-28T21:09:22.715013 #14964]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 28 21:09:22 node-4 puppet-user[16352]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 28 21:09:23 node-4 puppet-user[16352]: Compiled catalog for node-4.domain.tld in environment production in 0.88 seconds
Sep 28 21:09:24 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 28 21:09:24 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 28 21:09:24 node-4 crontab[16910]: (root) LIST (root)
Sep 28 21:09:24 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 28 21:09:24 node-4 crontab[16911]: (root) REPLACE (root)
Sep 28 21:09:25 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 28 21:09:26 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 28 21:09:27 node-4 puppet-user[16352]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 28 21:09:27 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8425" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 28 21:09:27 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 28 21:09:29 node-4 multipathd: uevent trigger error
<27>Sep 28 21:09:29 node-4 multipathd: uevent trigger error
<27>Sep 28 21:09:29 node-4 multipathd: uevent trigger error
<27>Sep 28 21:09:29 node-4 multipathd: uevent trigger error
<27>Sep 28 21:09:29 node-4 multipathd: uevent trigger error
<27>Sep 28 21:09:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:09:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:09:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:09:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:09:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:09:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:10:38 node-4 ntpdate[27375]: no servers can be used, exiting
<27>Sep 28 21:10:38 node-4 ntpdate[27624]: no servers can be used, exiting
<27>Sep 28 21:11:10 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:10 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:10 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:10 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:10 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:10 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:13 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:13 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:13 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:13 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:13 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:28 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:28 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:28 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:28 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:33 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:33 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:33 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:33 node-4 multipathd: uevent trigger error
<27>Sep 28 21:11:33 node-4 multipathd: uevent trigger error
<27>Sep 28 21:12:14 node-4 multipathd: uevent trigger error
<27>Sep 28 21:12:14 node-4 multipathd: uevent trigger error
<27>Sep 28 21:12:14 node-4 multipathd: uevent trigger error
<27>Sep 28 21:12:14 node-4 multipathd: uevent trigger error
<27>Sep 28 21:12:14 node-4 multipathd: uevent trigger error
<43>Sep 28 21:12:27 node-4 apache2_error [Wed Sep 28 21:12:26.356203 2016] [mpm_event:notice] [pid 7852:tid 140449129088896] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 28 21:12:27 node-4 apache2_error [Wed Sep 28 21:12:26.356342 2016] [core:notice] [pid 7852:tid 140449129088896] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 21:12:34 node-4 multipathd: uevent trigger error
<27>Sep 28 21:12:34 node-4 multipathd: uevent trigger error
<27>Sep 28 21:12:34 node-4 multipathd: uevent trigger error
<27>Sep 28 21:12:34 node-4 multipathd: uevent trigger error
<27>Sep 28 21:12:34 node-4 multipathd: uevent trigger error
<43>Sep 28 21:12:37 node-4 apache2_error [Wed Sep 28 21:12:29.408228 2016] [mpm_event:notice] [pid 7852:tid 140449129088896] AH00491: caught SIGTERM, shutting down
<43>Sep 28 21:12:37 node-4 apache2_error [Wed Sep 28 21:12:30.502374 2016] [mpm_worker:notice] [pid 8192:tid 140178977306496] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 28 21:12:37 node-4 apache2_error [Wed Sep 28 21:12:30.502416 2016] [core:notice] [pid 8192:tid 140178977306496] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 21:13:08 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Sep 28 21:13:12 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:12 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:12 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:12 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:12 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:29 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:29 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:29 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:29 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:29 node-4 multipathd: uevent trigger error
<129>Sep 28 21:13:32 node-4 haproxy[18748]: 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>Sep 28 21:13:35 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:35 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:35 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:35 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:35 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:38 node-4 multipathd: uevent trigger error
<129>Sep 28 21:13:41 node-4 haproxy[20905]: 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>Sep 28 21:13:42 node-4 haproxy[20909]: 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>Sep 28 21:13:44 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:44 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:44 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:44 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:44 node-4 multipathd: uevent trigger error
<129>Sep 28 21:13:46 node-4 haproxy[22077]: 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>Sep 28 21:13:47 node-4 haproxy[22081]: 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>Sep 28 21:13:47 node-4 haproxy[22081]: 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>Sep 28 21:13:49 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:49 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:49 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:49 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:49 node-4 multipathd: uevent trigger error
<129>Sep 28 21:13:51 node-4 haproxy[23226]: 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>Sep 28 21:13:52 node-4 haproxy[23230]: 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>Sep 28 21:13:52 node-4 haproxy[23230]: 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>Sep 28 21:13:52 node-4 haproxy[23230]: 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>Sep 28 21:13:53 node-4 haproxy[23230]: 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>Sep 28 21:13:54 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:54 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:54 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:54 node-4 multipathd: uevent trigger error
<27>Sep 28 21:13:54 node-4 multipathd: uevent trigger error
<129>Sep 28 21:13:56 node-4 haproxy[24357]: 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>Sep 28 21:13:57 node-4 haproxy[24361]: 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>Sep 28 21:13:57 node-4 haproxy[24361]: 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>Sep 28 21:13:57 node-4 haproxy[24361]: 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>Sep 28 21:13:58 node-4 haproxy[24361]: 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>Sep 28 21:13:58 node-4 haproxy[24361]: 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>Sep 28 21:14:00 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:00 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:00 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:00 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:00 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:00 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:00 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:00 node-4 multipathd: uevent trigger error
<129>Sep 28 21:14:00 node-4 haproxy[24361]: 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>Sep 28 21:14:00 node-4 haproxy[24361]: Server aodh/node-5 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>Sep 28 21:14:00 node-4 haproxy[24361]: proxy aodh has no server available!
<129>Sep 28 21:14:02 node-4 haproxy[25654]: 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>Sep 28 21:14:02 node-4 haproxy[25654]: 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>Sep 28 21:14:02 node-4 haproxy[25654]: 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>Sep 28 21:14:03 node-4 haproxy[25658]: 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>Sep 28 21:14:03 node-4 haproxy[25658]: 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>Sep 28 21:14:03 node-4 haproxy[25658]: 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>Sep 28 21:14:04 node-4 haproxy[25658]: 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>Sep 28 21:14:05 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:05 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:05 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:05 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:05 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:05 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:05 node-4 multipathd: uevent trigger error
<129>Sep 28 21:14:05 node-4 haproxy[25658]: 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>Sep 28 21:14:05 node-4 haproxy[25658]: Server aodh/node-5 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>Sep 28 21:14:05 node-4 haproxy[25658]: proxy aodh has no server available!
<129>Sep 28 21:14:06 node-4 haproxy[25658]: 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>Sep 28 21:14:06 node-4 haproxy[25658]: Server ceilometer/node-5 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>Sep 28 21:14:06 node-4 haproxy[25658]: proxy ceilometer has no server available!
<129>Sep 28 21:14:07 node-4 haproxy[26773]: 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>Sep 28 21:14:07 node-4 haproxy[26773]: 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>Sep 28 21:14:08 node-4 haproxy[26777]: 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>Sep 28 21:14:08 node-4 haproxy[26777]: 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>Sep 28 21:14:08 node-4 haproxy[26777]: 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>Sep 28 21:14:09 node-4 haproxy[26777]: 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>Sep 28 21:14:09 node-4 haproxy[26777]: 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>Sep 28 21:14:10 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:10 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:10 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:10 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:10 node-4 multipathd: uevent trigger error
<129>Sep 28 21:14:10 node-4 haproxy[26777]: 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>Sep 28 21:14:11 node-4 haproxy[26777]: Server aodh/node-5 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>Sep 28 21:14:11 node-4 haproxy[26777]: proxy aodh has no server available!
<129>Sep 28 21:14:11 node-4 haproxy[26777]: 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>Sep 28 21:14:11 node-4 haproxy[26777]: Server ceilometer/node-5 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>Sep 28 21:14:11 node-4 haproxy[26777]: proxy ceilometer has no server available!
<129>Sep 28 21:14:12 node-4 haproxy[27886]: 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>Sep 28 21:14:12 node-4 haproxy[27886]: 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>Sep 28 21:14:13 node-4 haproxy[27893]: 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>Sep 28 21:14:13 node-4 haproxy[27893]: 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>Sep 28 21:14:13 node-4 haproxy[27893]: 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>Sep 28 21:14:13 node-4 haproxy[27893]: 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>Sep 28 21:14:14 node-4 haproxy[27893]: 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>Sep 28 21:14:14 node-4 haproxy[27893]: 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>Sep 28 21:14:14 node-4 haproxy[27893]: Server horizon/node-5 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>Sep 28 21:14:15 node-4 haproxy[27893]: 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>Sep 28 21:14:16 node-4 haproxy[27893]: Server aodh/node-5 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>Sep 28 21:14:16 node-4 haproxy[27893]: proxy aodh has no server available!
<129>Sep 28 21:14:16 node-4 haproxy[27893]: 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>Sep 28 21:14:16 node-4 haproxy[27893]: Server ceilometer/node-5 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>Sep 28 21:14:16 node-4 haproxy[27893]: proxy ceilometer has no server available!
<27>Sep 28 21:14:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:16 node-4 multipathd: uevent trigger error
<129>Sep 28 21:14:19 node-4 haproxy[29233]: 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>Sep 28 21:14:19 node-4 haproxy[29233]: 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>Sep 28 21:14:19 node-4 haproxy[29233]: 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>Sep 28 21:14:19 node-4 haproxy[29233]: 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>Sep 28 21:14:20 node-4 haproxy[29239]: 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>Sep 28 21:14:20 node-4 haproxy[29239]: 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>Sep 28 21:14:20 node-4 haproxy[29239]: 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>Sep 28 21:14:20 node-4 haproxy[29239]: 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>Sep 28 21:14:20 node-4 haproxy[29239]: 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>Sep 28 21:14:20 node-4 haproxy[29239]: 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>Sep 28 21:14:21 node-4 haproxy[29239]: 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>Sep 28 21:14:21 node-4 haproxy[29239]: Server horizon/node-5 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>Sep 28 21:14:22 node-4 haproxy[29239]: 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>Sep 28 21:14:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:22 node-4 multipathd: uevent trigger error
<129>Sep 28 21:14:22 node-4 haproxy[29239]: Server glance-registry/node-5 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>Sep 28 21:14:22 node-4 haproxy[29239]: proxy glance-registry has no server available!
<27>Sep 28 21:14:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:22 node-4 multipathd: uevent trigger error
<129>Sep 28 21:14:22 node-4 haproxy[29239]: 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>Sep 28 21:14:22 node-4 haproxy[29239]: Server aodh/node-5 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>Sep 28 21:14:22 node-4 haproxy[29239]: proxy aodh has no server available!
<129>Sep 28 21:14:22 node-4 haproxy[29239]: 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>Sep 28 21:14:22 node-4 haproxy[29239]: Server ceilometer/node-5 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>Sep 28 21:14:22 node-4 haproxy[29239]: proxy ceilometer has no server available!
<129>Sep 28 21:14:25 node-4 haproxy[30410]: 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>Sep 28 21:14:25 node-4 haproxy[30410]: 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>Sep 28 21:14:25 node-4 haproxy[30410]: 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>Sep 28 21:14:25 node-4 haproxy[30410]: 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>Sep 28 21:14:25 node-4 haproxy[30410]: 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>Sep 28 21:14:25 node-4 haproxy[30410]: 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>Sep 28 21:14:25 node-4 haproxy[30410]: 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>Sep 28 21:14:26 node-4 haproxy[30410]: 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>Sep 28 21:14:26 node-4 haproxy[30410]: 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>Sep 28 21:14:26 node-4 haproxy[30410]: 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>Sep 28 21:14:26 node-4 haproxy[30410]: 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>Sep 28 21:14:26 node-4 haproxy[30410]: 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>Sep 28 21:14:26 node-4 haproxy[30410]: 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>Sep 28 21:14:26 node-4 haproxy[30410]: 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>Sep 28 21:14:27 node-4 haproxy[30410]: Server horizon/node-5 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>Sep 28 21:14:28 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:28 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:28 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:28 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:28 node-4 multipathd: uevent trigger error
<129>Sep 28 21:14:28 node-4 haproxy[30410]: 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>Sep 28 21:14:28 node-4 haproxy[30410]: Server glance-registry/node-5 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>Sep 28 21:14:28 node-4 haproxy[30410]: proxy glance-registry has no server available!
<129>Sep 28 21:14:28 node-4 haproxy[30410]: 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>Sep 28 21:14:28 node-4 haproxy[30410]: Server aodh/node-5 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>Sep 28 21:14:28 node-4 haproxy[30410]: proxy aodh has no server available!
<129>Sep 28 21:14:28 node-4 haproxy[30410]: 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.
<27>Sep 28 21:14:28 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Sep 28 21:14:28 node-4 haproxy[30410]: Server ceilometer/node-5 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>Sep 28 21:14:28 node-4 haproxy[30410]: proxy ceilometer has no server available!
<129>Sep 28 21:14:28 node-4 haproxy[30410]: 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>Sep 28 21:14:28 node-4 haproxy[30410]: Server nova-novncproxy/node-5 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>Sep 28 21:14:28 node-4 haproxy[30410]: proxy nova-novncproxy has no server available!
<129>Sep 28 21:14:30 node-4 haproxy[31580]: 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>Sep 28 21:14:30 node-4 haproxy[31580]: 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>Sep 28 21:14:30 node-4 haproxy[31580]: 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>Sep 28 21:14:30 node-4 haproxy[31580]: 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>Sep 28 21:14:30 node-4 haproxy[31580]: 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>Sep 28 21:14:31 node-4 haproxy[31584]: 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>Sep 28 21:14:31 node-4 haproxy[31584]: 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>Sep 28 21:14:31 node-4 haproxy[31584]: 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>Sep 28 21:14:31 node-4 haproxy[31584]: 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>Sep 28 21:14:31 node-4 haproxy[31584]: 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>Sep 28 21:14:31 node-4 haproxy[31584]: 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>Sep 28 21:14:31 node-4 haproxy[31584]: 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>Sep 28 21:14:32 node-4 haproxy[31584]: 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>Sep 28 21:14:32 node-4 haproxy[31584]: 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>Sep 28 21:14:32 node-4 haproxy[31584]: 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>Sep 28 21:14:32 node-4 haproxy[31584]: Server horizon/node-5 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>Sep 28 21:14:33 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:33 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:33 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:33 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:33 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:33 node-4 multipathd: uevent trigger error
<129>Sep 28 21:14:33 node-4 haproxy[31584]: 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>Sep 28 21:14:33 node-4 haproxy[31584]: Server glance-registry/node-5 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>Sep 28 21:14:33 node-4 haproxy[31584]: proxy glance-registry has no server available!
<129>Sep 28 21:14:33 node-4 haproxy[31584]: 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>Sep 28 21:14:33 node-4 haproxy[31584]: Server aodh/node-5 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>Sep 28 21:14:33 node-4 haproxy[31584]: proxy aodh has no server available!
<129>Sep 28 21:14:34 node-4 haproxy[31584]: 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>Sep 28 21:14:34 node-4 haproxy[31584]: Server ceilometer/node-5 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>Sep 28 21:14:34 node-4 haproxy[31584]: proxy ceilometer has no server available!
<129>Sep 28 21:14:34 node-4 haproxy[31584]: 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>Sep 28 21:14:34 node-4 haproxy[31584]: Server nova-novncproxy/node-5 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>Sep 28 21:14:34 node-4 haproxy[31584]: proxy nova-novncproxy has no server available!
<129>Sep 28 21:14:36 node-4 haproxy[315]: 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>Sep 28 21:14:36 node-4 haproxy[315]: 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>Sep 28 21:14:36 node-4 haproxy[315]: 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>Sep 28 21:14:36 node-4 haproxy[315]: 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>Sep 28 21:14:36 node-4 haproxy[315]: 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>Sep 28 21:14:36 node-4 haproxy[315]: 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>Sep 28 21:14:36 node-4 haproxy[315]: 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>Sep 28 21:14:36 node-4 haproxy[315]: 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>Sep 28 21:14:36 node-4 haproxy[315]: 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>Sep 28 21:14:37 node-4 haproxy[315]: 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>Sep 28 21:14:37 node-4 haproxy[315]: 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>Sep 28 21:14:37 node-4 haproxy[315]: 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>Sep 28 21:14:37 node-4 haproxy[315]: 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>Sep 28 21:14:37 node-4 haproxy[315]: 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>Sep 28 21:14:37 node-4 haproxy[315]: 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>Sep 28 21:14:37 node-4 haproxy[315]: 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>Sep 28 21:14:37 node-4 haproxy[315]: 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>Sep 28 21:14:37 node-4 haproxy[315]: 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>Sep 28 21:14:37 node-4 haproxy[315]: Server horizon/node-5 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>Sep 28 21:14:38 node-4 haproxy[315]: 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>Sep 28 21:14:38 node-4 haproxy[315]: Server glance-registry/node-5 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>Sep 28 21:14:38 node-4 haproxy[315]: proxy glance-registry has no server available!
<27>Sep 28 21:14:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:39 node-4 multipathd: uevent trigger error
<129>Sep 28 21:14:39 node-4 haproxy[315]: 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>Sep 28 21:14:39 node-4 haproxy[315]: Server aodh/node-5 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>Sep 28 21:14:39 node-4 haproxy[315]: proxy aodh has no server available!
<129>Sep 28 21:14:39 node-4 haproxy[315]: 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>Sep 28 21:14:39 node-4 haproxy[315]: Server ceilometer/node-5 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>Sep 28 21:14:39 node-4 haproxy[315]: proxy ceilometer has no server available!
<129>Sep 28 21:14:39 node-4 haproxy[315]: 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>Sep 28 21:14:39 node-4 haproxy[315]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 28 21:14:39 node-4 haproxy[315]: proxy nova-novncproxy has no server available!
<27>Sep 28 21:14:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:42 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:45 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:45 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:45 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:45 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:45 node-4 multipathd: uevent trigger error
<27>Sep 28 21:14:45 node-4 multipathd: uevent trigger error
<129>Sep 28 21:14:45 node-4 haproxy[315]: Server keystone-1/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>Sep 28 21:14:46 node-4 haproxy[315]: Server keystone-1/node-5 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>Sep 28 21:14:46 node-4 haproxy[315]: proxy keystone-1 has no server available!
<129>Sep 28 21:14:46 node-4 haproxy[315]: 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>Sep 28 21:14:46 node-4 haproxy[315]: Server keystone-2/node-5 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>Sep 28 21:14:46 node-4 haproxy[315]: proxy keystone-2 has no server available!
<129>Sep 28 21:14:46 node-4 haproxy[315]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 21:14:46 node-4 haproxy[315]: Server nova-api/node-5 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>Sep 28 21:14:46 node-4 haproxy[315]: proxy nova-api has no server available!
<129>Sep 28 21:14:46 node-4 haproxy[315]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 21:14:46 node-4 haproxy[315]: Server nova-metadata-api/node-5 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>Sep 28 21:14:46 node-4 haproxy[315]: proxy nova-metadata-api has no server available!
<129>Sep 28 21:14:46 node-4 haproxy[315]: 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>Sep 28 21:14:46 node-4 haproxy[315]: Backup Server cinder-api/node-5 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>Sep 28 21:14:46 node-4 haproxy[315]: proxy cinder-api has no server available!
<129>Sep 28 21:14:46 node-4 haproxy[315]: Server glance-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>Sep 28 21:14:46 node-4 haproxy[315]: Server glance-api/node-5 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>Sep 28 21:14:46 node-4 haproxy[315]: proxy glance-api has no server available!
<129>Sep 28 21:14:46 node-4 haproxy[315]: 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>Sep 28 21:14:46 node-4 haproxy[315]: Server glance-glare/node-5 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>Sep 28 21:14:46 node-4 haproxy[315]: proxy glance-glare has no server available!
<129>Sep 28 21:14:46 node-4 haproxy[315]: 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>Sep 28 21:14:46 node-4 haproxy[315]: Server neutron/node-5 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>Sep 28 21:14:46 node-4 haproxy[315]: proxy neutron has no server available!
<129>Sep 28 21:14:46 node-4 haproxy[315]: 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>Sep 28 21:14:47 node-4 haproxy[315]: Backup Server mysqld/node-5 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>Sep 28 21:14:47 node-4 haproxy[315]: proxy mysqld has no server available!
<129>Sep 28 21:14:47 node-4 haproxy[315]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 28 21:14:47 node-4 haproxy[315]: Server object-storage/node-5 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>Sep 28 21:14:47 node-4 haproxy[315]: proxy object-storage has no server available!
<129>Sep 28 21:14:47 node-4 haproxy[315]: 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>Sep 28 21:14:47 node-4 haproxy[315]: Server heat-api/node-5 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>Sep 28 21:14:47 node-4 haproxy[315]: proxy heat-api has no server available!
<129>Sep 28 21:14:47 node-4 haproxy[315]: 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>Sep 28 21:14:47 node-4 haproxy[315]: Server heat-api-cfn/node-5 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>Sep 28 21:14:47 node-4 haproxy[315]: proxy heat-api-cfn has no server available!
<129>Sep 28 21:14:47 node-4 haproxy[315]: 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>Sep 28 21:14:47 node-4 haproxy[315]: Server heat-api-cloudwatch/node-5 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>Sep 28 21:14:47 node-4 haproxy[315]: proxy heat-api-cloudwatch has no server available!
<27>Sep 28 21:15:21 node-4 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 28 21:15:21 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 28 21:15:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:15:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:15:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:15:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:15:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:15:26 node-4 multipathd: uevent trigger error
<27>Sep 28 21:15:26 node-4 multipathd: uevent trigger error
<27>Sep 28 21:15:26 node-4 multipathd: uevent trigger error
<27>Sep 28 21:15:26 node-4 multipathd: uevent trigger error
<27>Sep 28 21:15:26 node-4 multipathd: uevent trigger error
<43>Sep 28 21:15:27 node-4 apache2_error [Wed Sep 28 21:15:18.827334 2016] [mpm_worker:notice] [pid 8192:tid 140178977306496] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 28 21:15:27 node-4 apache2_error [Wed Sep 28 21:15:18.836243 2016] [mpm_worker:warn] [pid 8192:tid 140178977306496] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 28 21:15:27 node-4 apache2_error [Wed Sep 28 21:15:18.836976 2016] [mpm_worker:notice] [pid 8192:tid 140178977306496] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 28 21:15:27 node-4 apache2_error [Wed Sep 28 21:15:18.836988 2016] [core:notice] [pid 8192:tid 140178977306496] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 21:15:46 node-4 multipathd: uevent trigger error
<27>Sep 28 21:15:54 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 28 21:16:53 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>Sep 28 21:16:55 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 28 21:18:12 node-4 multipathd: uevent trigger error
<27>Sep 28 21:18:12 node-4 multipathd: uevent trigger error
<27>Sep 28 21:18:12 node-4 multipathd: uevent trigger error
<27>Sep 28 21:18:12 node-4 multipathd: uevent trigger error
<27>Sep 28 21:18:12 node-4 multipathd: uevent trigger error
<27>Sep 28 21:18:24 node-4 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 28 21:19:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:19:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:19:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:19:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:19:38 node-4 multipathd: uevent trigger error
<27>Sep 28 21:19:45 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 28 21:19:53 node-4 multipathd: uevent trigger error
<27>Sep 28 21:19:53 node-4 multipathd: uevent trigger error
<27>Sep 28 21:19:53 node-4 multipathd: uevent trigger error
<27>Sep 28 21:19:53 node-4 multipathd: uevent trigger error
<27>Sep 28 21:19:53 node-4 multipathd: uevent trigger error
<11>Sep 28 21:20:48 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<27>Sep 28 21:21:09 node-4 multipathd: uevent trigger error
<27>Sep 28 21:21:09 node-4 multipathd: uevent trigger error
<27>Sep 28 21:21:09 node-4 multipathd: uevent trigger error
<27>Sep 28 21:21:09 node-4 multipathd: uevent trigger error
<27>Sep 28 21:21:09 node-4 multipathd: uevent trigger error
<43>Sep 28 21:22:18 node-4 apache2_error [Wed Sep 28 21:22:18.349127 2016] [mpm_worker:notice] [pid 8192:tid 140178977306496] AH00295: caught SIGTERM, shutting down
<43>Sep 28 21:22:28 node-4 apache2_error [Wed Sep 28 21:22:19.102474 2016] [mpm_worker:notice] [pid 5528:tid 139717768234880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 28 21:22:28 node-4 apache2_error [Wed Sep 28 21:22:19.102515 2016] [core:notice] [pid 5528:tid 139717768234880] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 21:22:56 node-4 multipathd: uevent trigger error
<27>Sep 28 21:22:56 node-4 multipathd: uevent trigger error
<27>Sep 28 21:22:56 node-4 multipathd: uevent trigger error
<27>Sep 28 21:22:56 node-4 multipathd: uevent trigger error
<27>Sep 28 21:22:56 node-4 multipathd: uevent trigger error
<27>Sep 28 21:22:56 node-4 multipathd: uevent trigger error
<43>Sep 28 21:22:58 node-4 apache2_error [Wed Sep 28 21:22:50.921392 2016] [mpm_worker:notice] [pid 5528:tid 139717768234880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 28 21:22:58 node-4 apache2_error [Wed Sep 28 21:22:50.931289 2016] [mpm_worker:warn] [pid 5528:tid 139717768234880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 28 21:22:58 node-4 apache2_error [Wed Sep 28 21:22:50.936960 2016] [mpm_worker:notice] [pid 5528:tid 139717768234880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 28 21:22:58 node-4 apache2_error [Wed Sep 28 21:22:50.936986 2016] [core:notice] [pid 5528:tid 139717768234880] AH00094: Command line: '/usr/sbin/apache2'
<11>Sep 28 21:23:25 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<27>Sep 28 21:23:52 node-4 multipathd: uevent trigger error
<27>Sep 28 21:23:52 node-4 multipathd: uevent trigger error
<27>Sep 28 21:23:52 node-4 multipathd: uevent trigger error
<27>Sep 28 21:23:52 node-4 multipathd: uevent trigger error
<27>Sep 28 21:23:52 node-4 multipathd: uevent trigger error
<27>Sep 28 21:23:52 node-4 multipathd: uevent trigger error
<11>Sep 28 21:24:05 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<11>Sep 28 21:24:34 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<27>Sep 28 21:25:05 node-4 multipathd: uevent trigger error
<27>Sep 28 21:25:05 node-4 multipathd: uevent trigger error
<27>Sep 28 21:25:05 node-4 multipathd: uevent trigger error
<27>Sep 28 21:25:05 node-4 multipathd: uevent trigger error
<27>Sep 28 21:25:05 node-4 multipathd: uevent trigger error
<11>Sep 28 21:25:45 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<11>Sep 28 21:28:36 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<27>Sep 28 21:29:27 node-4 multipathd: uevent trigger error
<27>Sep 28 21:29:27 node-4 multipathd: uevent trigger error
<27>Sep 28 21:29:27 node-4 multipathd: uevent trigger error
<27>Sep 28 21:29:27 node-4 multipathd: uevent trigger error
<27>Sep 28 21:29:27 node-4 multipathd: uevent trigger error
<11>Sep 28 21:29:44 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<11>Sep 28 21:30:53 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<27>Sep 28 21:31:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:31:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:31:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:31:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:31:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:31:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:31:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:32:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:32:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:32:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:32:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:32:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:32:40 node-4 multipathd: uevent trigger error
<11>Sep 28 21:33:07 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<27>Sep 28 21:33:14 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:14 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:14 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:14 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:14 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:14 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:23 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:23 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:23 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:23 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:23 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:23 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:34 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Sep 28 21:33:34 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Sep 28 21:33:34 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Sep 28 21:33:35 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Sep 28 21:33:35 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Sep 28 21:33:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:36 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:52 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:52 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:52 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:52 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:52 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:58 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:58 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:58 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:58 node-4 multipathd: uevent trigger error
<27>Sep 28 21:33:58 node-4 multipathd: uevent trigger error
<43>Sep 28 21:34:49 node-4 apache2_error [Wed Sep 28 21:34:43.508829 2016] [mpm_worker:notice] [pid 5528:tid 139717768234880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 28 21:34:49 node-4 apache2_error [Wed Sep 28 21:34:43.894751 2016] [mpm_worker:warn] [pid 5528:tid 139717768234880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 28 21:34:49 node-4 apache2_error [Wed Sep 28 21:34:43.899378 2016] [mpm_worker:notice] [pid 5528:tid 139717768234880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 28 21:34:49 node-4 apache2_error [Wed Sep 28 21:34:43.899393 2016] [core:notice] [pid 5528:tid 139717768234880] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 21:35:24 node-4 multipathd: uevent trigger error
<27>Sep 28 21:35:24 node-4 multipathd: uevent trigger error
<27>Sep 28 21:35:24 node-4 multipathd: uevent trigger error
<27>Sep 28 21:35:24 node-4 multipathd: uevent trigger error
<27>Sep 28 21:35:24 node-4 multipathd: uevent trigger error
<27>Sep 28 21:35:24 node-4 multipathd: uevent trigger error
<27>Sep 28 21:35:24 node-4 multipathd: uevent trigger error
<43>Sep 28 21:35:29 node-4 apache2_error [Wed Sep 28 21:35:20.560032 2016] [mpm_worker:notice] [pid 5528:tid 139717768234880] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 28 21:35:29 node-4 apache2_error [Wed Sep 28 21:35:20.944440 2016] [mpm_worker:warn] [pid 5528:tid 139717768234880] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 28 21:35:29 node-4 apache2_error [Wed Sep 28 21:35:20.968700 2016] [mpm_worker:notice] [pid 5528:tid 139717768234880] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 28 21:35:29 node-4 apache2_error [Wed Sep 28 21:35:20.968731 2016] [core:notice] [pid 5528:tid 139717768234880] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 28 21:35:57 node-4 multipathd: uevent trigger error
<27>Sep 28 21:35:57 node-4 multipathd: uevent trigger error
<27>Sep 28 21:35:57 node-4 multipathd: uevent trigger error
<27>Sep 28 21:35:57 node-4 multipathd: uevent trigger error
<27>Sep 28 21:35:57 node-4 multipathd: uevent trigger error
<11>Sep 28 21:36:04 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<11>Sep 28 21:36:05 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<27>Sep 28 21:36:06 node-4 multipathd: uevent trigger error
<27>Sep 28 21:36:06 node-4 multipathd: uevent trigger error
<27>Sep 28 21:36:06 node-4 multipathd: uevent trigger error
<27>Sep 28 21:36:06 node-4 multipathd: uevent trigger error
<27>Sep 28 21:36:06 node-4 multipathd: uevent trigger error
<27>Sep 28 21:36:06 node-4 multipathd: uevent trigger error
<11>Sep 28 21:37:27 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<27>Sep 28 21:37:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:37:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:37:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:37:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:37:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:37:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:27 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:27 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:27 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:27 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:27 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:37 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:37 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:37 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:37 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:37 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:37 node-4 multipathd: uevent trigger error
<11>Sep 28 21:38:46 node-4 liberasurecode[29548]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:46 node-4 liberasurecode[29548]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:46 node-4 liberasurecode[29548]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:46 node-4 liberasurecode[29548]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:46 node-4 liberasurecode[29578]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:46 node-4 liberasurecode[29578]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:46 node-4 liberasurecode[29578]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:46 node-4 liberasurecode[29578]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:48 node-4 liberasurecode[30342]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:48 node-4 liberasurecode[30342]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:48 node-4 liberasurecode[30342]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:48 node-4 liberasurecode[30342]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[30999]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[30999]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[30999]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[30999]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[31035]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[31035]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[31035]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[31035]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[31082]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[31082]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[31082]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:52 node-4 liberasurecode[31082]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31141]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31141]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31141]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31141]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31155]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31155]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31155]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31155]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31167]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31167]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31167]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31167]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31179]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31179]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31179]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:38:53 node-4 liberasurecode[31179]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 28 21:38:59 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:59 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:59 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:59 node-4 multipathd: uevent trigger error
<27>Sep 28 21:38:59 node-4 multipathd: uevent trigger error
<27>Sep 28 21:39:04 node-4 multipathd: uevent trigger error
<27>Sep 28 21:39:04 node-4 multipathd: uevent trigger error
<27>Sep 28 21:39:04 node-4 multipathd: uevent trigger error
<27>Sep 28 21:39:04 node-4 multipathd: uevent trigger error
<27>Sep 28 21:39:04 node-4 multipathd: uevent trigger error
<27>Sep 28 21:39:04 node-4 multipathd: uevent trigger error
<11>Sep 28 21:40:01 node-4 liberasurecode[8883]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:40:01 node-4 liberasurecode[8883]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:40:01 node-4 liberasurecode[8883]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:40:01 node-4 liberasurecode[8883]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 28 21:40:02 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<27>Sep 28 21:40:07 node-4 multipathd: uevent trigger error
<27>Sep 28 21:40:07 node-4 multipathd: uevent trigger error
<27>Sep 28 21:40:07 node-4 multipathd: uevent trigger error
<27>Sep 28 21:40:07 node-4 multipathd: uevent trigger error
<27>Sep 28 21:40:07 node-4 multipathd: uevent trigger error
<27>Sep 28 21:40:07 node-4 multipathd: uevent trigger error
<11>Sep 28 21:42:06 node-4 epmd: epmd: node name already occupied rabbitmq-cli-21
<27>Sep 28 21:42:17 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:17 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:17 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:17 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:17 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:22 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:34 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:35 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:35 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:35 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:35 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:35 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:40 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:55 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:55 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:55 node-4 multipathd: uevent trigger error
<27>Sep 28 21:42:55 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:02 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:02 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:02 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:02 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:02 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:06 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:06 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:06 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:06 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:06 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:11 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:11 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:11 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:11 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:16 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:21 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:21 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:21 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:21 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:21 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:25 node-4 multipathd: uevent trigger error
<27>Sep 28 21:43:57 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 28 21:43:57 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Sep 28 21:45:01 node-4 liberasurecode[29663]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:45:01 node-4 liberasurecode[29663]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:45:01 node-4 liberasurecode[29663]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 28 21:45:01 node-4 liberasurecode[29663]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
