Oct  2 06:00:11 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8390" x-info="http://www.rsyslog.com"] start
Oct  2 06:00:11 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct  2 06:00:11 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct  2 06:00:11 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct  2 06:00:11 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct  2 06:00:11 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct  2 06:00:11 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct  2 06:00:11 node-1 kernel: [    0.000000] Linux version 3.13.0-96-generic (buildd@lcy01-09) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #143-Ubuntu SMP Mon Aug 29 20:15:20 UTC 2016 (Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39)
Oct  2 06:00:11 node-1 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=d4b43141-e053-4a21-9abf-2abb95ec3a16 nomdmonddf nomdmonisw
Oct  2 06:00:11 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct  2 06:00:11 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct  2 06:00:11 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct  2 06:00:11 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct  2 06:00:11 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct  2 06:00:11 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct  2 06:00:11 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct  2 06:00:11 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct  2 06:00:11 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Oct  2 06:00:11 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct  2 06:00:11 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct  2 06:00:11 node-1 kernel: [    0.000000] No AGP bridge found
Oct  2 06:00:11 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct  2 06:00:11 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct  2 06:00:11 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct  2 06:00:11 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct  2 06:00:11 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct  2 06:00:11 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct  2 06:00:11 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct  2 06:00:11 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct  2 06:00:11 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct  2 06:00:11 node-1 kernel: [    0.000000]   2 disabled
Oct  2 06:00:11 node-1 kernel: [    0.000000]   3 disabled
Oct  2 06:00:11 node-1 kernel: [    0.000000]   4 disabled
Oct  2 06:00:11 node-1 kernel: [    0.000000]   5 disabled
Oct  2 06:00:11 node-1 kernel: [    0.000000]   6 disabled
Oct  2 06:00:11 node-1 kernel: [    0.000000]   7 disabled
Oct  2 06:00:11 node-1 kernel: [    0.000000]   8 disabled
Oct  2 06:00:11 node-1 kernel: [    0.000000]   9 disabled
Oct  2 06:00:11 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct  2 06:00:11 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct  2 06:00:11 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct  2 06:00:11 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct  2 06:00:11 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct  2 06:00:11 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct  2 06:00:11 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct  2 06:00:11 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct  2 06:00:11 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct  2 06:00:11 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct  2 06:00:11 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct  2 06:00:11 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct  2 06:00:11 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct  2 06:00:11 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct  2 06:00:11 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct  2 06:00:11 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct  2 06:00:11 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct  2 06:00:11 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct  2 06:00:11 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct  2 06:00:11 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct  2 06:00:11 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct  2 06:00:11 node-1 kernel: [    0.000000] Zone ranges:
Oct  2 06:00:11 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] Movable zone start for each node
Oct  2 06:00:11 node-1 kernel: [    0.000000] Early memory node ranges
Oct  2 06:00:11 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct  2 06:00:11 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct  2 06:00:11 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct  2 06:00:11 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct  2 06:00:11 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct  2 06:00:11 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct  2 06:00:11 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct  2 06:00:11 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct  2 06:00:11 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct  2 06:00:11 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct  2 06:00:11 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct  2 06:00:11 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct  2 06:00:11 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct  2 06:00:11 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct  2 06:00:11 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct  2 06:00:11 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct  2 06:00:11 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct  2 06:00:11 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct  2 06:00:11 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct  2 06:00:11 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct  2 06:00:11 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct  2 06:00:11 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct  2 06:00:11 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct  2 06:00:11 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Oct  2 06:00:11 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct  2 06:00:11 node-1 kernel: [    0.000000] Policy zone: Normal
Oct  2 06:00:11 node-1 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=d4b43141-e053-4a21-9abf-2abb95ec3a16 nomdmonddf nomdmonisw
Oct  2 06:00:11 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct  2 06:00:11 node-1 kernel: [    0.000000] Checking aperture...
Oct  2 06:00:11 node-1 kernel: [    0.000000] No AGP bridge found
Oct  2 06:00:11 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct  2 06:00:11 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct  2 06:00:11 node-1 kernel: [    0.000000] Memory: 32653452K/33280636K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Oct  2 06:00:11 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct  2 06:00:11 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct  2 06:00:11 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct  2 06:00:11 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct  2 06:00:11 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct  2 06:00:11 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct  2 06:00:11 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct  2 06:00:11 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct  2 06:00:11 node-1 kernel: [    0.000000] console [tty0] enabled
Oct  2 06:00:11 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct  2 06:00:11 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct  2 06:00:11 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct  2 06:00:11 node-1 kernel: [    0.000000] hpet clockevent registered
Oct  2 06:00:11 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct  2 06:00:11 node-1 kernel: [    0.004000] tsc: Detected 3492.245 MHz processor
Oct  2 06:00:11 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.49 BogoMIPS (lpj=13968980)
Oct  2 06:00:11 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct  2 06:00:11 node-1 kernel: [    0.000052] Security Framework initialized
Oct  2 06:00:11 node-1 kernel: [    0.000070] AppArmor: AppArmor initialized
Oct  2 06:00:11 node-1 kernel: [    0.000071] Yama: becoming mindful.
Oct  2 06:00:11 node-1 kernel: [    0.001458] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.006320] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.008251] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.008279] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.008565] Initializing cgroup subsys memory
Oct  2 06:00:11 node-1 kernel: [    0.008572] Initializing cgroup subsys devices
Oct  2 06:00:11 node-1 kernel: [    0.008574] Initializing cgroup subsys freezer
Oct  2 06:00:11 node-1 kernel: [    0.008576] Initializing cgroup subsys blkio
Oct  2 06:00:11 node-1 kernel: [    0.008577] Initializing cgroup subsys perf_event
Oct  2 06:00:11 node-1 kernel: [    0.008580] Initializing cgroup subsys hugetlb
Oct  2 06:00:11 node-1 kernel: [    0.008599] CPU: Physical Processor ID: 0
Oct  2 06:00:11 node-1 kernel: [    0.008600] CPU: Processor Core ID: 0
Oct  2 06:00:11 node-1 kernel: [    0.008604] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct  2 06:00:11 node-1 kernel: [    0.008604] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct  2 06:00:11 node-1 kernel: [    0.009298] mce: CPU supports 22 MCE banks
Oct  2 06:00:11 node-1 kernel: [    0.009326] CPU0: Thermal monitoring enabled (TM1)
Oct  2 06:00:11 node-1 kernel: [    0.009347] process: using mwait in idle threads
Oct  2 06:00:11 node-1 kernel: [    0.009350] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct  2 06:00:11 node-1 kernel: [    0.009350] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct  2 06:00:11 node-1 kernel: [    0.009350] tlb_flushall_shift: 6
Oct  2 06:00:11 node-1 kernel: [    0.009439] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct  2 06:00:11 node-1 kernel: [    0.010162] ACPI: Core revision 20131115
Oct  2 06:00:11 node-1 kernel: [    0.022840] ACPI: All ACPI Tables successfully acquired
Oct  2 06:00:11 node-1 kernel: [    0.022999] ftrace: allocating 28614 entries in 112 pages
Oct  2 06:00:11 node-1 kernel: [    0.031706] dmar: Host address width 46
Oct  2 06:00:11 node-1 kernel: [    0.031708] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct  2 06:00:11 node-1 kernel: [    0.031714] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  2 06:00:11 node-1 kernel: [    0.031716] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct  2 06:00:11 node-1 kernel: [    0.031720] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  2 06:00:11 node-1 kernel: [    0.031721] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct  2 06:00:11 node-1 kernel: [    0.031723] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct  2 06:00:11 node-1 kernel: [    0.031724] dmar: ATSR flags: 0x0
Oct  2 06:00:11 node-1 kernel: [    0.031725] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct  2 06:00:11 node-1 kernel: [    0.031726] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct  2 06:00:11 node-1 kernel: [    0.031842] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct  2 06:00:11 node-1 kernel: [    0.031843] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct  2 06:00:11 node-1 kernel: [    0.031844] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct  2 06:00:11 node-1 kernel: [    0.031845] HPET id 0 under DRHD base 0xc7ffc000
Oct  2 06:00:11 node-1 kernel: [    0.031846] Your BIOS is broken and requested that x2apic be disabled.
Oct  2 06:00:11 node-1 kernel: [    0.031846] This will slightly decrease performance.
Oct  2 06:00:11 node-1 kernel: [    0.031846] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct  2 06:00:11 node-1 kernel: [    0.032278] Enabled IRQ remapping in xapic mode
Oct  2 06:00:11 node-1 kernel: [    0.032279] x2apic not enabled, IRQ remapping is in xapic mode
Oct  2 06:00:11 node-1 kernel: [    0.032283] Switched APIC routing to physical flat.
Oct  2 06:00:11 node-1 kernel: [    0.032862] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct  2 06:00:11 node-1 kernel: [    0.072515] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct  2 06:00:11 node-1 kernel: [    0.072521] TSC deadline timer enabled
Oct  2 06:00:11 node-1 kernel: [    0.072528] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct  2 06:00:11 node-1 kernel: [    0.072534] ... version:                3
Oct  2 06:00:11 node-1 kernel: [    0.072535] ... bit width:              48
Oct  2 06:00:11 node-1 kernel: [    0.072536] ... generic registers:      4
Oct  2 06:00:11 node-1 kernel: [    0.072537] ... value mask:             0000ffffffffffff
Oct  2 06:00:11 node-1 kernel: [    0.072538] ... max period:             0000ffffffffffff
Oct  2 06:00:11 node-1 kernel: [    0.072539] ... fixed-purpose events:   3
Oct  2 06:00:11 node-1 kernel: [    0.072539] ... event mask:             000000070000000f
Oct  2 06:00:11 node-1 kernel: [    0.073941] x86: Booting SMP configuration:
Oct  2 06:00:11 node-1 kernel: [    0.088048] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct  2 06:00:11 node-1 kernel: [    0.073943] .... node  #0, CPUs:        #1  #2  #3
Oct  2 06:00:11 node-1 kernel: [    0.115960] .... node  #1, CPUs:    #4  #5  #6  #7
Oct  2 06:00:11 node-1 kernel: [    0.270127] .... node  #0, CPUs:    #8  #9 #10 #11
Oct  2 06:00:11 node-1 kernel: [    0.325753] .... node  #1, CPUs:   #12 #13 #14 #15
Oct  2 06:00:11 node-1 kernel: [    0.382816] x86: Booted up 2 nodes, 16 CPUs
Oct  2 06:00:11 node-1 kernel: [    0.382820] smpboot: Total of 16 processors activated (111764.03 BogoMIPS)
Oct  2 06:00:11 node-1 kernel: [    0.407321] devtmpfs: initialized
Oct  2 06:00:11 node-1 kernel: [    0.409807] EVM: security.selinux
Oct  2 06:00:11 node-1 kernel: [    0.409809] EVM: security.SMACK64
Oct  2 06:00:11 node-1 kernel: [    0.409810] EVM: security.ima
Oct  2 06:00:11 node-1 kernel: [    0.409810] EVM: security.capability
Oct  2 06:00:11 node-1 kernel: [    0.409861] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.410516] pinctrl core: initialized pinctrl subsystem
Oct  2 06:00:11 node-1 kernel: [    0.410579] regulator-dummy: no parameters
Oct  2 06:00:11 node-1 kernel: [    0.410610] RTC time:  5:59:35, date: 10/02/16
Oct  2 06:00:11 node-1 kernel: [    0.410645] NET: Registered protocol family 16
Oct  2 06:00:11 node-1 kernel: [    0.410732] cpuidle: using governor ladder
Oct  2 06:00:11 node-1 kernel: [    0.410733] cpuidle: using governor menu
Oct  2 06:00:11 node-1 kernel: [    0.410769] ACPI: bus type PCI registered
Oct  2 06:00:11 node-1 kernel: [    0.410771] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct  2 06:00:11 node-1 kernel: [    0.410817] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct  2 06:00:11 node-1 kernel: [    0.410819] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct  2 06:00:11 node-1 kernel: [    0.424587] PCI: Using configuration type 1 for base access
Oct  2 06:00:11 node-1 kernel: [    0.425591] bio: create slab <bio-0> at 0
Oct  2 06:00:11 node-1 kernel: [    0.425873] ACPI: Added _OSI(Module Device)
Oct  2 06:00:11 node-1 kernel: [    0.425875] ACPI: Added _OSI(Processor Device)
Oct  2 06:00:11 node-1 kernel: [    0.425876] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct  2 06:00:11 node-1 kernel: [    0.425877] ACPI: Added _OSI(Processor Aggregator Device)
Oct  2 06:00:11 node-1 kernel: [    0.438727] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct  2 06:00:11 node-1 kernel: [    0.453281] ACPI: Interpreter enabled
Oct  2 06:00:11 node-1 kernel: [    0.453286] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct  2 06:00:11 node-1 kernel: [    0.453290] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct  2 06:00:11 node-1 kernel: [    0.453293] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct  2 06:00:11 node-1 kernel: [    0.453300] ACPI: (supports S0 S4 S5)
Oct  2 06:00:11 node-1 kernel: [    0.453301] ACPI: Using IOAPIC for interrupt routing
Oct  2 06:00:11 node-1 kernel: [    0.453343] HEST: Table parsing has been initialized.
Oct  2 06:00:11 node-1 kernel: [    0.453346] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct  2 06:00:11 node-1 kernel: [    0.453904] ACPI: No dock devices found.
Oct  2 06:00:11 node-1 kernel: [    0.465659] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct  2 06:00:11 node-1 kernel: [    0.465664] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  2 06:00:11 node-1 kernel: [    0.465667] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  2 06:00:11 node-1 kernel: [    0.465696] PCI host bridge to bus 0000:ff
Oct  2 06:00:11 node-1 kernel: [    0.465698] pci_bus 0000:ff: root bus resource [bus ff]
Oct  2 06:00:11 node-1 kernel: [    0.465706] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.465745] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.465776] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.465811] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.465842] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.465871] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.465901] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.465931] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.465959] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.465987] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466014] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466040] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466069] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466096] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466123] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466152] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466182] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466209] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466236] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.466267] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466293] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.466319] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466345] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466375] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.466410] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466441] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466471] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466502] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466533] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466564] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466595] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466625] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466658] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466691] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466724] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466757] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466790] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466821] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466849] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466881] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466915] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466951] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.466986] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467019] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467049] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467079] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467108] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467137] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467178] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467208] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467239] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467269] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467297] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467328] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467358] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467390] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467422] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467479] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct  2 06:00:11 node-1 kernel: [    0.467482] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  2 06:00:11 node-1 kernel: [    0.467485] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  2 06:00:11 node-1 kernel: [    0.467502] PCI host bridge to bus 0000:7f
Oct  2 06:00:11 node-1 kernel: [    0.467504] pci_bus 0000:7f: root bus resource [bus 7f]
Oct  2 06:00:11 node-1 kernel: [    0.467512] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467540] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.467568] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467597] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467619] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.467643] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.467669] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467695] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467718] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467740] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467762] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467785] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467810] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467832] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467855] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467882] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467903] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467927] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467949] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.467973] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.467995] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.468018] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468040] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468068] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct  2 06:00:11 node-1 kernel: [    0.468105] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468133] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468161] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468189] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468214] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468242] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468270] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468299] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468323] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468351] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468379] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468407] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468435] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468462] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468488] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468516] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468541] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468567] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468595] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468621] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468649] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468674] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468699] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468729] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468756] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468783] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468814] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468840] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468863] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  2 06:00:11 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct  2 06:00:11 node-1 kernel: [    0.468888] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468915] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468946] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.468972] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.470236] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct  2 06:00:11 node-1 kernel: [    0.470240] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  2 06:00:11 node-1 kernel: [    0.471369] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  2 06:00:11 node-1 kernel: [    0.471884] PCI host bridge to bus 0000:00
Oct  2 06:00:11 node-1 kernel: [    0.471886] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct  2 06:00:11 node-1 kernel: [    0.471888] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct  2 06:00:11 node-1 kernel: [    0.471889] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct  2 06:00:11 node-1 kernel: [    0.471890] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct  2 06:00:11 node-1 kernel: [    0.471892] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct  2 06:00:11 node-1 kernel: [    0.471893] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct  2 06:00:11 node-1 kernel: [    0.471894] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct  2 06:00:11 node-1 kernel: [    0.471900] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct  2 06:00:11 node-1 kernel: [    0.471984] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.472015] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.472056] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct  2 06:00:11 node-1 kernel: [    0.472077] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.472106] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.472146] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct  2 06:00:11 node-1 kernel: [    0.472168] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.472197] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.472241] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct  2 06:00:11 node-1 kernel: [    0.472259] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.472330] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.472407] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.472485] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct  2 06:00:11 node-1 kernel: [    0.472490] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct  2 06:00:11 node-1 kernel: [    0.472576] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct  2 06:00:11 node-1 kernel: [    0.472725] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct  2 06:00:11 node-1 kernel: [    0.472743] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct  2 06:00:11 node-1 kernel: [    0.472820] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.472874] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct  2 06:00:11 node-1 kernel: [    0.472896] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.472952] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.472995] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct  2 06:00:11 node-1 kernel: [    0.473024] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.473080] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.473123] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct  2 06:00:11 node-1 kernel: [    0.473148] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct  2 06:00:11 node-1 kernel: [    0.473165] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct  2 06:00:11 node-1 kernel: [    0.473243] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.473293] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct  2 06:00:11 node-1 kernel: [    0.473320] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct  2 06:00:11 node-1 kernel: [    0.473569] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct  2 06:00:11 node-1 kernel: [    0.473575] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct  2 06:00:11 node-1 kernel: [    0.473581] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.473587] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.473594] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct  2 06:00:11 node-1 kernel: [    0.473624] pci 0000:01:00.0: supports D1 D2
Oct  2 06:00:11 node-1 kernel: [    0.479523] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  2 06:00:11 node-1 kernel: [    0.479525] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  2 06:00:11 node-1 kernel: [    0.479527] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  2 06:00:11 node-1 kernel: [    0.479636] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.479670] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct  2 06:00:11 node-1 kernel: [    0.487529] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  2 06:00:11 node-1 kernel: [    0.487535] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.487539] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  2 06:00:11 node-1 kernel: [    0.487624] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.487697] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.487797] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.487843] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  2 06:00:11 node-1 kernel: [    0.487846] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.487848] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  2 06:00:11 node-1 kernel: [    0.487915] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.488038] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.488092] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  2 06:00:11 node-1 kernel: [    0.488095] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.488097] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  2 06:00:11 node-1 kernel: [    0.488146] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.488268] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.488311] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.488430] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.488467] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.488586] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.488622] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct  2 06:00:11 node-1 kernel: [    0.488743] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct  2 06:00:11 node-1 kernel: [    0.488785] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  2 06:00:11 node-1 kernel: [    0.488787] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.488789] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  2 06:00:11 node-1 kernel: [    0.488849] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct  2 06:00:11 node-1 kernel: [    0.488931] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.488985] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.489025] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct  2 06:00:11 node-1 kernel: [    0.489105] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct  2 06:00:11 node-1 kernel: [    0.489214] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  2 06:00:11 node-1 kernel: [    0.489217] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.489219] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  2 06:00:11 node-1 kernel: [    0.489275] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct  2 06:00:11 node-1 kernel: [    0.489329] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.489377] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.489587] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  2 06:00:11 node-1 kernel: [    0.489591] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  2 06:00:11 node-1 kernel: [    0.489654] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct  2 06:00:11 node-1 kernel: [    0.489707] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.489758] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.489988] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  2 06:00:11 node-1 kernel: [    0.489992] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  2 06:00:11 node-1 kernel: [    0.490050] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct  2 06:00:11 node-1 kernel: [    0.490114] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.490166] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct  2 06:00:11 node-1 kernel: [    0.490391] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  2 06:00:11 node-1 kernel: [    0.490395] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  2 06:00:11 node-1 kernel: [    0.490569] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  2 06:00:11 node-1 kernel: [    0.490607] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  2 06:00:11 node-1 kernel: [    0.490681] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct  2 06:00:11 node-1 kernel: [    0.490700] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct  2 06:00:11 node-1 kernel: [    0.490713] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct  2 06:00:11 node-1 kernel: [    0.490726] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct  2 06:00:11 node-1 kernel: [    0.490776] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct  2 06:00:11 node-1 kernel: [    0.495535] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  2 06:00:11 node-1 kernel: [    0.495540] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  2 06:00:11 node-1 kernel: [    0.495572] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct  2 06:00:11 node-1 kernel: [    0.496065] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct  2 06:00:11 node-1 kernel: [    0.496068] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  2 06:00:11 node-1 kernel: [    0.496191] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  2 06:00:11 node-1 kernel: [    0.496297] PCI host bridge to bus 0000:80
Oct  2 06:00:11 node-1 kernel: [    0.496299] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct  2 06:00:11 node-1 kernel: [    0.496301] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct  2 06:00:11 node-1 kernel: [    0.496302] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct  2 06:00:11 node-1 kernel: [    0.496310] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.496373] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.496440] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct  2 06:00:11 node-1 kernel: [    0.496501] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct  2 06:00:11 node-1 kernel: [    0.496506] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct  2 06:00:11 node-1 kernel: [    0.496578] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct  2 06:00:11 node-1 kernel: [    0.496879] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct  2 06:00:11 node-1 kernel: [    0.496911] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct  2 06:00:11 node-1 kernel: [    0.496941] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct  2 06:00:11 node-1 kernel: [    0.496970] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct  2 06:00:11 node-1 kernel: [    0.497000] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  2 06:00:11 node-1 kernel: [    0.497030] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  2 06:00:11 node-1 kernel: [    0.497060] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  2 06:00:11 node-1 kernel: [    0.497090] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  2 06:00:11 node-1 kernel: [    0.497175] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct  2 06:00:11 node-1 kernel: [    0.497179] ACPI: \_SB_.UNC1: notify handler is installed
Oct  2 06:00:11 node-1 kernel: [    0.497180] ACPI: \_SB_.UNC0: notify handler is installed
Oct  2 06:00:11 node-1 kernel: [    0.497196] ACPI: \_SB_.PCI0: notify handler is installed
Oct  2 06:00:11 node-1 kernel: [    0.497248] ACPI: \_SB_.PCI1: notify handler is installed
Oct  2 06:00:11 node-1 kernel: [    0.497328] Found 4 acpi root devices
Oct  2 06:00:11 node-1 kernel: [    0.497435] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct  2 06:00:11 node-1 kernel: [    0.497437] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct  2 06:00:11 node-1 kernel: [    0.497439] vgaarb: loaded
Oct  2 06:00:11 node-1 kernel: [    0.497440] vgaarb: bridge control possible 0000:0c:00.0
Oct  2 06:00:11 node-1 kernel: [    0.497556] SCSI subsystem initialized
Oct  2 06:00:11 node-1 kernel: [    0.497621] libata version 3.00 loaded.
Oct  2 06:00:11 node-1 kernel: [    0.497636] ACPI: bus type USB registered
Oct  2 06:00:11 node-1 kernel: [    0.497645] usbcore: registered new interface driver usbfs
Oct  2 06:00:11 node-1 kernel: [    0.497651] usbcore: registered new interface driver hub
Oct  2 06:00:11 node-1 kernel: [    0.497674] usbcore: registered new device driver usb
Oct  2 06:00:11 node-1 kernel: [    0.497846] PCI: Using ACPI for IRQ routing
Oct  2 06:00:11 node-1 kernel: [    0.501440] PCI: pci_cache_line_size set to 64 bytes
Oct  2 06:00:11 node-1 kernel: [    0.501647] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct  2 06:00:11 node-1 kernel: [    0.501648] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct  2 06:00:11 node-1 kernel: [    0.501649] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct  2 06:00:11 node-1 kernel: [    0.501714] NetLabel: Initializing
Oct  2 06:00:11 node-1 kernel: [    0.501715] NetLabel:  domain hash size = 128
Oct  2 06:00:11 node-1 kernel: [    0.501716] NetLabel:  protocols = UNLABELED CIPSOv4
Oct  2 06:00:11 node-1 kernel: [    0.501725] NetLabel:  unlabeled traffic allowed by default
Oct  2 06:00:11 node-1 kernel: [    0.501785] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct  2 06:00:11 node-1 kernel: [    0.501789] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct  2 06:00:11 node-1 kernel: [    0.503858] Switched to clocksource hpet
Oct  2 06:00:11 node-1 kernel: [    0.508260] AppArmor: AppArmor Filesystem Enabled
Oct  2 06:00:11 node-1 kernel: [    0.508299] pnp: PnP ACPI init
Oct  2 06:00:11 node-1 kernel: [    0.508311] ACPI: bus type PNP registered
Oct  2 06:00:11 node-1 kernel: [    0.508494] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct  2 06:00:11 node-1 kernel: [    0.508505] pnp 00:01: [dma 4]
Oct  2 06:00:11 node-1 kernel: [    0.508523] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct  2 06:00:11 node-1 kernel: [    0.508557] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct  2 06:00:11 node-1 kernel: [    0.508581] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct  2 06:00:11 node-1 kernel: [    0.508602] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct  2 06:00:11 node-1 kernel: [    0.508648] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct  2 06:00:11 node-1 kernel: [    0.508759] system 00:06: [io  0x0500-0x057f] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508762] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct  2 06:00:11 node-1 kernel: [    0.508763] system 00:06: [io  0x0580-0x059f] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508765] system 00:06: [io  0x0600-0x061f] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508766] system 00:06: [io  0x0880-0x0883] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508768] system 00:06: [io  0x0800-0x081f] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508771] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct  2 06:00:11 node-1 kernel: [    0.508773] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508774] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508776] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508777] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508779] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508780] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct  2 06:00:11 node-1 kernel: [    0.508783] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct  2 06:00:11 node-1 kernel: [    0.508885] pnp 00:07: [dma 0 disabled]
Oct  2 06:00:11 node-1 kernel: [    0.508918] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  2 06:00:11 node-1 kernel: [    0.509000] pnp 00:08: [dma 0 disabled]
Oct  2 06:00:11 node-1 kernel: [    0.509036] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  2 06:00:11 node-1 kernel: [    0.509093] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct  2 06:00:11 node-1 kernel: [    0.509542] pnp: PnP ACPI: found 10 devices
Oct  2 06:00:11 node-1 kernel: [    0.509544] ACPI: bus type PNP unregistered
Oct  2 06:00:11 node-1 kernel: [    0.515550] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  2 06:00:11 node-1 kernel: [    0.515554] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  2 06:00:11 node-1 kernel: [    0.515557] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  2 06:00:11 node-1 kernel: [    0.515562] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  2 06:00:11 node-1 kernel: [    0.515564] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.515578] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515608] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  2 06:00:11 node-1 kernel: [    0.515622] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515651] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  2 06:00:11 node-1 kernel: [    0.515666] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  2 06:00:11 node-1 kernel: [    0.515695] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  2 06:00:11 node-1 kernel: [    0.515709] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  2 06:00:11 node-1 kernel: [    0.515738] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  2 06:00:11 node-1 kernel: [    0.515740] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.515755] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515787] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  2 06:00:11 node-1 kernel: [    0.515789] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.515803] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515837] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  2 06:00:11 node-1 kernel: [    0.515839] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.515842] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515846] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  2 06:00:11 node-1 kernel: [    0.515848] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.515851] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515855] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  2 06:00:11 node-1 kernel: [    0.515861] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  2 06:00:11 node-1 kernel: [    0.515870] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  2 06:00:11 node-1 kernel: [    0.515874] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  2 06:00:11 node-1 kernel: [    0.515881] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct  2 06:00:11 node-1 kernel: [    0.515882] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct  2 06:00:11 node-1 kernel: [    0.515883] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct  2 06:00:11 node-1 kernel: [    0.515884] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct  2 06:00:11 node-1 kernel: [    0.515885] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct  2 06:00:11 node-1 kernel: [    0.515886] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct  2 06:00:11 node-1 kernel: [    0.515887] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct  2 06:00:11 node-1 kernel: [    0.515888] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct  2 06:00:11 node-1 kernel: [    0.515889] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.515890] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515891] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.515892] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515893] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.515894] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515895] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.515896] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515897] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct  2 06:00:11 node-1 kernel: [    0.515898] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515899] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct  2 06:00:11 node-1 kernel: [    0.515900] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct  2 06:00:11 node-1 kernel: [    0.515901] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct  2 06:00:11 node-1 kernel: [    0.515903] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct  2 06:00:11 node-1 kernel: [    0.515905] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct  2 06:00:11 node-1 kernel: [    0.515906] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct  2 06:00:11 node-1 kernel: [    0.515948] NET: Registered protocol family 2
Oct  2 06:00:11 node-1 kernel: [    0.516249] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.516628] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.516794] TCP: Hash tables configured (established 262144 bind 65536)
Oct  2 06:00:11 node-1 kernel: [    0.516839] TCP: reno registered
Oct  2 06:00:11 node-1 kernel: [    0.516870] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.516993] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.517150] NET: Registered protocol family 1
Oct  2 06:00:11 node-1 kernel: [    0.551957] pci 0000:0c:00.0: Video device with shadowed ROM
Oct  2 06:00:11 node-1 kernel: [    0.551973] PCI: CLS 64 bytes, default 64
Oct  2 06:00:11 node-1 kernel: [    0.552057] Trying to unpack rootfs image as initramfs...
Oct  2 06:00:11 node-1 kernel: [    0.773311] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Oct  2 06:00:11 node-1 kernel: [    0.773374] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct  2 06:00:11 node-1 kernel: [    0.773384] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct  2 06:00:11 node-1 kernel: [    0.773899] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.773906] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.773913] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.773920] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.773931] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.773944] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.773962] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.773976] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.773988] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.773996] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.774003] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.774010] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.774019] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.774030] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.774043] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.774055] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct  2 06:00:11 node-1 kernel: [    0.774130] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct  2 06:00:11 node-1 kernel: [    0.774134] Scanning for low memory corruption every 60 seconds
Oct  2 06:00:11 node-1 kernel: [    0.774447] Initialise system trusted keyring
Oct  2 06:00:11 node-1 kernel: [    0.774493] audit: initializing netlink socket (disabled)
Oct  2 06:00:11 node-1 kernel: [    0.774504] type=2000 audit(1475387974.724:1): initialized
Oct  2 06:00:11 node-1 kernel: [    0.792141] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct  2 06:00:11 node-1 kernel: [    0.793610] zbud: loaded
Oct  2 06:00:11 node-1 kernel: [    0.793724] VFS: Disk quotas dquot_6.5.2
Oct  2 06:00:11 node-1 kernel: [    0.793758] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct  2 06:00:11 node-1 kernel: [    0.794100] fuse init (API version 7.22)
Oct  2 06:00:11 node-1 kernel: [    0.794169] msgmni has been set to 32768
Oct  2 06:00:11 node-1 kernel: [    0.794214] Key type big_key registered
Oct  2 06:00:11 node-1 kernel: [    0.794684] Key type asymmetric registered
Oct  2 06:00:11 node-1 kernel: [    0.794686] Asymmetric key parser 'x509' registered
Oct  2 06:00:11 node-1 kernel: [    0.794706] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct  2 06:00:11 node-1 kernel: [    0.794763] io scheduler noop registered
Oct  2 06:00:11 node-1 kernel: [    0.794764] io scheduler deadline registered (default)
Oct  2 06:00:11 node-1 kernel: [    0.794782] io scheduler cfq registered
Oct  2 06:00:11 node-1 kernel: [    0.795077] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    0.795173] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    0.795262] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    0.795349] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    0.795446] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    0.795510] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    0.795767] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct  2 06:00:11 node-1 kernel: [    0.795786] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct  2 06:00:11 node-1 kernel: [    0.795805] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct  2 06:00:11 node-1 kernel: [    0.795815] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795817] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795819] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct  2 06:00:11 node-1 kernel: [    0.795823] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795825] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795826] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795827] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795828] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795830] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795831] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795833] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795834] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795836] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795837] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795838] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795840] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct  2 06:00:11 node-1 kernel: [    0.795844] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795847] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct  2 06:00:11 node-1 kernel: [    0.795856] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795859] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct  2 06:00:11 node-1 kernel: [    0.795871] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795873] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct  2 06:00:11 node-1 kernel: [    0.795876] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct  2 06:00:11 node-1 kernel: [    0.795887] ioapic: probe of 0000:00:05.4 failed with error -22
Oct  2 06:00:11 node-1 kernel: [    0.795907] ioapic: probe of 0000:80:05.4 failed with error -22
Oct  2 06:00:11 node-1 kernel: [    0.795912] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct  2 06:00:11 node-1 kernel: [    0.795920] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct  2 06:00:11 node-1 kernel: [    0.795956] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct  2 06:00:11 node-1 kernel: [    0.795957] vesafb: scrolling: redraw
Oct  2 06:00:11 node-1 kernel: [    0.795959] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct  2 06:00:11 node-1 kernel: [    0.815747] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct  2 06:00:11 node-1 kernel: [    0.824255] Console: switching to colour frame buffer device 80x30
Oct  2 06:00:11 node-1 kernel: [    0.832939] fb0: VESA VGA frame buffer device
Oct  2 06:00:11 node-1 kernel: [    0.833135] intel_idle: MWAIT substates: 0x2120
Oct  2 06:00:11 node-1 kernel: [    0.833135] intel_idle: v0.4 model 0x3F
Oct  2 06:00:11 node-1 kernel: [    0.833136] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct  2 06:00:11 node-1 kernel: [    0.833349] ipmi message handler version 39.2
Oct  2 06:00:11 node-1 kernel: [    0.833609] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  2 06:00:11 node-1 kernel: [    0.834039] ACPI: AC Adapter [P111] (on-line)
Oct  2 06:00:11 node-1 kernel: [    0.839262] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct  2 06:00:11 node-1 kernel: [    0.850252] ACPI: Power Button [PWRB]
Oct  2 06:00:11 node-1 kernel: [    0.856002] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct  2 06:00:11 node-1 kernel: [    0.867592] ACPI: Power Button [PWRF]
Oct  2 06:00:11 node-1 kernel: [    0.885384] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct  2 06:00:11 node-1 kernel: [    0.897012] pstore: Registered erst as persistent store backend
Oct  2 06:00:11 node-1 kernel: [    0.903197] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct  2 06:00:11 node-1 kernel: [    0.915141] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct  2 06:00:11 node-1 kernel: [    0.941874] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct  2 06:00:11 node-1 kernel: [    0.975167] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct  2 06:00:11 node-1 kernel: [    0.989356] Linux agpgart interface v0.103
Oct  2 06:00:11 node-1 kernel: [    0.996979] brd: module loaded
Oct  2 06:00:11 node-1 kernel: [    1.004022] loop: module loaded
Oct  2 06:00:11 node-1 kernel: [    1.010769] libphy: Fixed MDIO Bus: probed
Oct  2 06:00:11 node-1 kernel: [    1.017301] tun: Universal TUN/TAP device driver, 1.6
Oct  2 06:00:11 node-1 kernel: [    1.023776] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct  2 06:00:11 node-1 kernel: [    1.030288] PPP generic driver version 2.4.2
Oct  2 06:00:11 node-1 kernel: [    1.036675] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct  2 06:00:11 node-1 kernel: [    1.043104] ehci-pci: EHCI PCI platform driver
Oct  2 06:00:11 node-1 kernel: [    1.049621] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct  2 06:00:11 node-1 kernel: [    1.056033] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct  2 06:00:11 node-1 kernel: [    1.068586] ehci-pci 0000:00:1a.0: debug port 2
Oct  2 06:00:11 node-1 kernel: [    1.078787] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct  2 06:00:11 node-1 kernel: [    1.078812] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct  2 06:00:11 node-1 kernel: [    1.095348] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct  2 06:00:11 node-1 kernel: [    1.101441] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct  2 06:00:11 node-1 kernel: [    1.107620] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  2 06:00:11 node-1 kernel: [    1.119551] usb usb1: Product: EHCI Host Controller
Oct  2 06:00:11 node-1 kernel: [    1.125593] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  2 06:00:11 node-1 kernel: [    1.131672] usb usb1: SerialNumber: 0000:00:1a.0
Oct  2 06:00:11 node-1 kernel: [    1.137639] hub 1-0:1.0: USB hub found
Oct  2 06:00:11 node-1 kernel: [    1.143426] hub 1-0:1.0: 2 ports detected
Oct  2 06:00:11 node-1 kernel: [    1.149225] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct  2 06:00:11 node-1 kernel: [    1.154817] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct  2 06:00:11 node-1 kernel: [    1.165741] ehci-pci 0000:00:1d.0: debug port 2
Oct  2 06:00:11 node-1 kernel: [    1.175049] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct  2 06:00:11 node-1 kernel: [    1.175052] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct  2 06:00:11 node-1 kernel: [    1.191267] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct  2 06:00:11 node-1 kernel: [    1.196478] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct  2 06:00:11 node-1 kernel: [    1.201793] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  2 06:00:11 node-1 kernel: [    1.212424] usb usb2: Product: EHCI Host Controller
Oct  2 06:00:11 node-1 kernel: [    1.217906] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  2 06:00:11 node-1 kernel: [    1.223475] usb usb2: SerialNumber: 0000:00:1d.0
Oct  2 06:00:11 node-1 kernel: [    1.228999] hub 2-0:1.0: USB hub found
Oct  2 06:00:11 node-1 kernel: [    1.234357] hub 2-0:1.0: 2 ports detected
Oct  2 06:00:11 node-1 kernel: [    1.239667] ehci-platform: EHCI generic platform driver
Oct  2 06:00:11 node-1 kernel: [    1.244906] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct  2 06:00:11 node-1 kernel: [    1.250220] ohci-pci: OHCI PCI platform driver
Oct  2 06:00:11 node-1 kernel: [    1.255546] ohci-platform: OHCI generic platform driver
Oct  2 06:00:11 node-1 kernel: [    1.260759] uhci_hcd: USB Universal Host Controller Interface driver
Oct  2 06:00:11 node-1 kernel: [    1.266105] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct  2 06:00:11 node-1 kernel: [    1.459048] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct  2 06:00:11 node-1 kernel: [    1.631223] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct  2 06:00:11 node-1 kernel: [    1.636761] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  2 06:00:11 node-1 kernel: [    1.642490] hub 1-1:1.0: USB hub found
Oct  2 06:00:11 node-1 kernel: [    1.647959] hub 1-1:1.0: 6 ports detected
Oct  2 06:00:11 node-1 kernel: [    1.762780] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct  2 06:00:11 node-1 kernel: [    1.790752] tsc: Refined TSC clocksource calibration: 3491.914 MHz
Oct  2 06:00:11 node-1 kernel: [    2.030883] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct  2 06:00:11 node-1 kernel: [    2.036450] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  2 06:00:11 node-1 kernel: [    2.042273] hub 2-1:1.0: USB hub found
Oct  2 06:00:11 node-1 kernel: [    2.047994] hub 2-1:1.0: 8 ports detected
Oct  2 06:00:11 node-1 kernel: [    2.307804] i8042: No controller found
Oct  2 06:00:11 node-1 kernel: [    2.313221] mousedev: PS/2 mouse device common for all mice
Oct  2 06:00:11 node-1 kernel: [    2.318746] rtc_cmos 00:02: RTC can wake from S4
Oct  2 06:00:11 node-1 kernel: [    2.324335] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct  2 06:00:11 node-1 kernel: [    2.326369] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct  2 06:00:11 node-1 kernel: [    2.335482] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct  2 06:00:11 node-1 kernel: [    2.346674] device-mapper: uevent: version 1.0.3
Oct  2 06:00:11 node-1 kernel: [    2.352385] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct  2 06:00:11 node-1 kernel: [    2.363666] ledtrig-cpu: registered to indicate activity on CPUs
Oct  2 06:00:11 node-1 kernel: [    2.369600] TCP: cubic registered
Oct  2 06:00:11 node-1 kernel: [    2.375488] NET: Registered protocol family 10
Oct  2 06:00:11 node-1 kernel: [    2.381468] NET: Registered protocol family 17
Oct  2 06:00:11 node-1 kernel: [    2.387146] Key type dns_resolver registered
Oct  2 06:00:11 node-1 kernel: [    2.393127] Loading compiled-in X.509 certificates
Oct  2 06:00:11 node-1 kernel: [    2.399298] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct  2 06:00:11 node-1 kernel: [    2.410675] registered taskstats version 1
Oct  2 06:00:11 node-1 kernel: [    2.418599] Key type trusted registered
Oct  2 06:00:11 node-1 kernel: [    2.426179] Key type encrypted registered
Oct  2 06:00:11 node-1 kernel: [    2.431619] AppArmor: AppArmor sha1 policy hashing enabled
Oct  2 06:00:11 node-1 kernel: [    2.437083] IMA: No TPM chip found, activating TPM-bypass!
Oct  2 06:00:11 node-1 kernel: [    2.443222] regulator-dummy: disabling
Oct  2 06:00:11 node-1 kernel: [    2.448756]   Magic number: 4:145:971
Oct  2 06:00:11 node-1 kernel: [    2.454168] pci 0000:7f:14.0: hash matches
Oct  2 06:00:11 node-1 kernel: [    2.459697] rtc_cmos 00:02: setting system clock to 2016-10-02 05:59:37 UTC (1475387977)
Oct  2 06:00:11 node-1 kernel: [    2.470636] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct  2 06:00:11 node-1 kernel: [    2.476360] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  2 06:00:11 node-1 kernel: [    2.487685] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct  2 06:00:11 node-1 kernel: [    2.493499] usb 2-1.4: Manufacturer: Avocent
Oct  2 06:00:11 node-1 kernel: [    2.499271] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct  2 06:00:11 node-1 kernel: [    2.499272] usb 2-1.4: SerialNumber: 20111102-00000001
Oct  2 06:00:11 node-1 kernel: [    2.510820] EDD information not available.
Oct  2 06:00:11 node-1 kernel: [    2.516419] PM: Hibernation image not present or could not be loaded.
Oct  2 06:00:11 node-1 kernel: [    2.517268] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct  2 06:00:11 node-1 kernel: [    2.528628] Write protecting the kernel read-only data: 12288k
Oct  2 06:00:11 node-1 kernel: [    2.534842] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct  2 06:00:11 node-1 kernel: [    2.547332] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct  2 06:00:11 node-1 kernel: [    2.579137] device-mapper: multipath: version 1.6.0 loaded
Oct  2 06:00:11 node-1 kernel: [    2.587201] systemd-udevd[216]: starting version 204
Oct  2 06:00:11 node-1 kernel: [    2.611677] md: linear personality registered for level -1
Oct  2 06:00:11 node-1 kernel: [    2.625544] md: multipath personality registered for level -4
Oct  2 06:00:11 node-1 kernel: [    2.634637] md: raid0 personality registered for level 0
Oct  2 06:00:11 node-1 kernel: [    2.643005] md: raid1 personality registered for level 1
Oct  2 06:00:11 node-1 kernel: [    2.649660] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct  2 06:00:11 node-1 kernel: [    2.656156] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct  2 06:00:11 node-1 kernel: [    2.668395] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct  2 06:00:11 node-1 kernel: [    2.668413] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct  2 06:00:11 node-1 kernel: [    2.668427] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  2 06:00:11 node-1 kernel: [    2.668893] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.668965] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.669013] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.669139] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.669326] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.687928] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct  2 06:00:11 node-1 kernel: [    2.687936] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct  2 06:00:11 node-1 kernel: [    2.687937] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct  2 06:00:11 node-1 kernel: [    2.688054] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.688183] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.688293] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.688385] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.688503] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.688670] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.689072] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.708990] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct  2 06:00:11 node-1 kernel: [    2.708993] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct  2 06:00:11 node-1 kernel: [    2.708997] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  2 06:00:11 node-1 kernel: [    2.709268] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.709365] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.709496] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.709652] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.709825] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.726169] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct  2 06:00:11 node-1 kernel: [    2.726170] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct  2 06:00:11 node-1 kernel: [    2.726171] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  2 06:00:11 node-1 kernel: [    2.726516] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.726643] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.726768] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.726879] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.727101] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.656150] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct  2 06:00:11 node-1 kernel: [    2.866478] Switched to clocksource tsc
Oct  2 06:00:11 node-1 kernel: [    2.867589] megasas: FW now in Ready state
Oct  2 06:00:11 node-1 kernel: [    2.867916] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.868008] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.868138] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.868311] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.868412] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.868530] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.868636] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.868793] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.868941] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.869068] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.869194] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.869275] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.869342] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.869444] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.869625] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.869773] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Oct  2 06:00:11 node-1 kernel: [    2.870384] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct  2 06:00:11 node-1 kernel: [    2.893298] hidraw: raw HID events driver (C) Jiri Kosina
Oct  2 06:00:11 node-1 kernel: [    2.902969] usbcore: registered new interface driver usbhid
Oct  2 06:00:11 node-1 kernel: [    2.909673] usbhid: USB HID core driver
Oct  2 06:00:11 node-1 kernel: [    2.918436] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Oct  2 06:00:11 node-1 kernel: [    2.932856] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Oct  2 06:00:11 node-1 kernel: [    2.933933] raid6: sse2x1    6464 MB/s
Oct  2 06:00:11 node-1 kernel: [    2.952855] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Oct  2 06:00:11 node-1 kernel: [    2.966638] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Oct  2 06:00:11 node-1 kernel: [    2.980530] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Oct  2 06:00:11 node-1 kernel: [    2.994364] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Oct  2 06:00:11 node-1 kernel: [    3.008519] raid6: sse2x2   10083 MB/s
Oct  2 06:00:11 node-1 kernel: [    3.081681] raid6: sse2x4   17270 MB/s
Oct  2 06:00:11 node-1 kernel: [    3.153610] raid6: avx2x1   22914 MB/s
Oct  2 06:00:11 node-1 kernel: [    3.209568] megasas:IOC Init cmd success
Oct  2 06:00:11 node-1 kernel: [    3.225561] raid6: avx2x2   23868 MB/s
Oct  2 06:00:11 node-1 kernel: [    3.297498] raid6: avx2x4   30919 MB/s
Oct  2 06:00:11 node-1 kernel: [    3.303680] raid6: using algorithm avx2x4 (30919 MB/s)
Oct  2 06:00:11 node-1 kernel: [    3.310026] raid6: using avx2x2 recovery algorithm
Oct  2 06:00:11 node-1 kernel: [    3.317158] xor: automatically using best checksumming function:
Oct  2 06:00:11 node-1 kernel: [    3.361414]    avx       : 35592.000 MB/sec
Oct  2 06:00:11 node-1 kernel: [    3.368404] async_tx: api initialized (async)
Oct  2 06:00:11 node-1 kernel: [    3.378592] md: raid6 personality registered for level 6
Oct  2 06:00:11 node-1 kernel: [    3.384935] md: raid5 personality registered for level 5
Oct  2 06:00:11 node-1 kernel: [    3.391103] md: raid4 personality registered for level 4
Oct  2 06:00:11 node-1 kernel: [    3.400374] md: raid10 personality registered for level 10
Oct  2 06:00:11 node-1 kernel: [    3.449282] multipathd (356): /proc/356/oom_adj is deprecated, please use /proc/356/oom_score_adj instead.
Oct  2 06:00:11 node-1 kernel: [    3.717227] megasas: INIT adapter done
Oct  2 06:00:11 node-1 kernel: [    3.817083] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct  2 06:00:11 node-1 kernel: [    3.822707] scsi0 : LSI SAS based MegaRAID driver
Oct  2 06:00:11 node-1 kernel: [    3.830013] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  2 06:00:11 node-1 kernel: [    3.846408] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  2 06:00:11 node-1 kernel: [    3.859014] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct  2 06:00:11 node-1 kernel: [    3.864436] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct  2 06:00:11 node-1 kernel: [    3.875756] sd 0:2:0:0: [sda] Write Protect is off
Oct  2 06:00:11 node-1 kernel: [    3.881450] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct  2 06:00:11 node-1 kernel: [    3.881470] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct  2 06:00:11 node-1 kernel: [    3.925371]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Oct  2 06:00:11 node-1 kernel: [    3.931935] sd 0:2:0:0: [sda] Attached SCSI disk
Oct  2 06:00:11 node-1 kernel: [    4.095541] random: lvm urandom read with 24 bits of entropy available
Oct  2 06:00:11 node-1 kernel: [    4.291480] bio: create slab <bio-1> at 1
Oct  2 06:00:11 node-1 kernel: [    5.091517] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct  2 06:00:11 node-1 kernel: [    5.766179] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct  2 06:00:11 node-1 kernel: [    5.803192] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct  2 06:00:11 node-1 kernel: [    5.827520] random: nonblocking pool is initialized
Oct  2 06:00:11 node-1 kernel: [    5.985005] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct  2 06:00:11 node-1 kernel: [    6.086698] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct  2 06:00:11 node-1 kernel: [    6.149867] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct  2 06:00:11 node-1 kernel: [    6.334489] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct  2 06:00:11 node-1 kernel: [    6.368581] XFS (dm-0): Mounting Filesystem
Oct  2 06:00:11 node-1 kernel: [    6.723004] XFS (dm-0): Ending clean mount
Oct  2 06:00:11 node-1 kernel: [    6.790479] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct  2 06:00:11 node-1 kernel: [    6.817365] XFS (dm-1): Mounting Filesystem
Oct  2 06:00:11 node-1 kernel: [    7.008670] XFS (dm-1): Ending clean mount
Oct  2 06:00:11 node-1 kernel: [    8.657624] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  2 06:00:11 node-1 kernel: [    8.680333] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  2 06:00:11 node-1 kernel: [    8.849204] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  2 06:00:11 node-1 kernel: [    8.849218] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  2 06:00:11 node-1 kernel: [    8.849228] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct  2 06:00:11 node-1 kernel: [    8.849238] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct  2 06:00:11 node-1 kernel: [    8.890919] systemd-udevd[779]: starting version 204
Oct  2 06:00:11 node-1 kernel: [    9.098190] wmi: Mapper loaded
Oct  2 06:00:11 node-1 kernel: [    9.099050] power_meter ACPI000D:00: Found ACPI power meter.
Oct  2 06:00:11 node-1 kernel: [    9.099058] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct  2 06:00:11 node-1 kernel: [    9.126077] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct  2 06:00:11 node-1 kernel: [    9.126084] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  2 06:00:11 node-1 kernel: [    9.126087] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct  2 06:00:11 node-1 kernel: [    9.126090] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  2 06:00:11 node-1 kernel: [    9.126131] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct  2 06:00:11 node-1 kernel: [    9.127189] IPMI System Interface driver.
Oct  2 06:00:11 node-1 kernel: [    9.127237] ipmi_si: probing via ACPI
Oct  2 06:00:11 node-1 kernel: [    9.127259] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct  2 06:00:11 node-1 kernel: [    9.127260] ipmi_si: Adding ACPI-specified kcs state machine
Oct  2 06:00:11 node-1 kernel: [    9.127273] ipmi_si: probing via SMBIOS
Oct  2 06:00:11 node-1 kernel: [    9.127274] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct  2 06:00:11 node-1 kernel: [    9.127275] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct  2 06:00:11 node-1 kernel: [    9.127277] ipmi_si: probing via SPMI
Oct  2 06:00:11 node-1 kernel: [    9.127278] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct  2 06:00:11 node-1 kernel: [    9.127279] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct  2 06:00:11 node-1 kernel: [    9.127281] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct  2 06:00:11 node-1 kernel: [    9.133294] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct  2 06:00:11 node-1 kernel: [    9.188982] systemd-udevd[813]: renamed network interface eth3 to enp9s0
Oct  2 06:00:11 node-1 kernel: [    9.220864] systemd-udevd[805]: renamed network interface eth2 to enp8s0
Oct  2 06:00:11 node-1 kernel: [    9.256847] systemd-udevd[807]: renamed network interface eth0 to enp6s0
Oct  2 06:00:11 node-1 kernel: [    9.280796] systemd-udevd[797]: renamed network interface eth1 to enp7s0
Oct  2 06:00:11 node-1 kernel: [    9.306475] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct  2 06:00:11 node-1 kernel: [    9.306481] ipmi_si 00:09: IPMI kcs interface initialized
Oct  2 06:00:11 node-1 kernel: [    9.546527] type=1400 audit(1475387984.589:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1055 comm="apparmor_parser"
Oct  2 06:00:11 node-1 kernel: [    9.546680] type=1400 audit(1475387984.589:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1055 comm="apparmor_parser"
Oct  2 06:00:11 node-1 kernel: [    9.546806] type=1400 audit(1475387984.589:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1055 comm="apparmor_parser"
Oct  2 06:00:11 node-1 kernel: [    9.549379] type=1400 audit(1475387984.593:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Oct  2 06:00:11 node-1 kernel: [    9.549517] type=1400 audit(1475387984.593:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1053 comm="apparmor_parser"
Oct  2 06:00:11 node-1 kernel: [    9.549636] type=1400 audit(1475387984.593:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1053 comm="apparmor_parser"
Oct  2 06:00:11 node-1 kernel: [    9.557446] type=1400 audit(1475387984.601:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1057 comm="apparmor_parser"
Oct  2 06:00:11 node-1 kernel: [    9.557591] type=1400 audit(1475387984.601:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1057 comm="apparmor_parser"
Oct  2 06:00:11 node-1 kernel: [    9.557714] type=1400 audit(1475387984.601:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1057 comm="apparmor_parser"
Oct  2 06:00:11 node-1 kernel: [    9.559171] type=1400 audit(1475387984.601:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1054 comm="apparmor_parser"
Oct  2 06:00:11 node-1 kernel: [   10.180260] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Oct  2 06:00:11 node-1 kernel: [   10.180978] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Oct  2 06:00:11 node-1 kernel: [   10.360843] enic 0000:06:00.0 enp6s0: Link UP
Oct  2 06:00:11 node-1 kernel: [   10.361965] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct  2 06:00:11 node-1 kernel: [   10.361976] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct  2 06:00:11 node-1 kernel: [   19.684993] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct  2 06:00:12 node-1 failsafe: Failsafe of 120 seconds reached.
Oct  2 06:00:13 node-1 kernel: [   38.543888] init: failsafe main process (8417) killed by TERM signal
Oct  2 06:00:13 node-1 dbus[8463]: [system] AppArmor D-Bus mediation is enabled
Oct  2 06:00:13 node-1 kernel: [   38.789615] audit_printk_skb: 30 callbacks suppressed
Oct  2 06:00:13 node-1 kernel: [   38.789617] type=1400 audit(1475388013.402:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8544 comm="apparmor_parser"
Oct  2 06:00:13 node-1 kernel: [   38.789622] type=1400 audit(1475388013.402:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8544 comm="apparmor_parser"
Oct  2 06:00:13 node-1 kernel: [   38.789625] type=1400 audit(1475388013.402:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Oct  2 06:00:13 node-1 kernel: [   38.789842] type=1400 audit(1475388013.402:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8544 comm="apparmor_parser"
Oct  2 06:00:13 node-1 kernel: [   38.789844] type=1400 audit(1475388013.402:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Oct  2 06:00:13 node-1 kernel: [   38.789957] type=1400 audit(1475388013.402:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Oct  2 06:00:13 node-1 kernel: [   38.791093] type=1400 audit(1475388013.402:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8545 comm="apparmor_parser"
Oct  2 06:00:13 node-1 kernel: [   38.861562] type=1400 audit(1475388013.474:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8547 comm="apparmor_parser"
Oct  2 06:00:13 node-1 anacron[8610]: Anacron 2.3 started on 2016-10-02
Oct  2 06:00:13 node-1 cron[8575]: (CRON) INFO (pidfile fd = 3)
Oct  2 06:00:13 node-1 anacron[8610]: Will run job `cron.daily' in 5 min.
Oct  2 06:00:13 node-1 anacron[8610]: Will run job `cron.weekly' in 10 min.
Oct  2 06:00:13 node-1 anacron[8610]: Will run job `cron.monthly' in 15 min.
Oct  2 06:00:13 node-1 anacron[8610]: Jobs will be executed sequentially
Oct  2 06:00:13 node-1 cron[8625]: (CRON) STARTUP (fork ok)
Oct  2 06:00:13 node-1 multipathd: path checkers start up
Oct  2 06:00:13 node-1 cron[8625]: (CRON) INFO (Running @reboot jobs)
Oct  2 06:00:14 node-1 postfix/master[8755]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct  2 06:00:17 node-1 puppet-agent[8940]: Reopening log files
Oct  2 06:00:17 node-1 puppet-agent[8940]: Could not request certificate: Connection refused - connect(2)
Oct  2 06:00:32 node-1 puppet-user[9019]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct  2 06:00:32 node-1 puppet-user[9019]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct  2 06:00:33 node-1 puppet-user[9019]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct  2 06:00:33 node-1 puppet-user[9019]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct  2 06:00:33 node-1 puppet-user[9019]: Finished catalog run in 1.03 seconds
Oct  2 06:00:34 node-1 multipathd: uevent trigger error
Oct  2 06:00:34 node-1 puppet-user[9459]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  2 06:00:34 node-1 puppet-user[9459]: Compiled catalog for node-1.domain.tld in environment production in 0.12 seconds
Oct  2 06:00:35 node-1 puppet-user[9459]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct  2 06:00:35 node-1 puppet-user[9459]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct  2 06:00:35 node-1 puppet-user[9459]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Oct  2 06:00:35 node-1 puppet-user[9459]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct  2 06:00:35 node-1 puppet-user[9459]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct  2 06:00:35 node-1 puppet-user[9459]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct  2 06:00:35 node-1 puppet-user[9459]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct  2 06:00:35 node-1 puppet-user[9459]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct  2 06:00:35 node-1 puppet-user[9459]: Finished catalog run in 0.06 seconds
Oct  2 06:00:36 node-1 puppet-user[10058]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct  2 06:00:36 node-1 puppet-user[10058]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct  2 06:00:36 node-1 puppet-user[10058]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct  2 06:00:36 node-1 puppet-user[10058]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct  2 06:00:36 node-1 puppet-user[10058]: Finished catalog run in 0.03 seconds
Oct  2 06:00:38 node-1 puppet-user[10525]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct  2 06:00:38 node-1 puppet-user[10525]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct  2 06:00:38 node-1 puppet-user[10525]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct  2 06:00:38 node-1 puppet-user[10525]: Finished catalog run in 0.04 seconds
Oct  2 06:00:39 node-1 puppet-user[10981]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct  2 06:00:39 node-1 puppet-user[10981]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Oct  2 06:00:39 node-1 puppet-user[10981]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct  2 06:00:41 node-1 puppet-user[10981]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Oct  2 06:00:41 node-1 puppet-user[10981]: Finished catalog run in 2.01 seconds
Oct  2 06:00:43 node-1 puppet-user[11519]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct  2 06:00:43 node-1 puppet-user[11519]: Compiled catalog for node-1.domain.tld in environment production in 0.21 seconds
Oct  2 06:00:43 node-1 puppet-user[11519]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct  2 06:00:43 node-1 puppet-user[11519]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Oct  2 06:00:43 node-1 puppet-user[11519]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct  2 06:00:43 node-1 puppet-user[11519]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct  2 06:00:43 node-1 puppet-user[11519]: Finished catalog run in 0.19 seconds
Oct  2 06:00:45 node-1 puppet-user[12002]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct  2 06:00:45 node-1 puppet-user[12002]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Oct  2 06:00:45 node-1 puppet-user[12002]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct  2 06:00:45 node-1 kernel: [   70.913585] nr_pdflush_threads exported in /proc is scheduled for removal
Oct  2 06:00:45 node-1 kernel: [   70.913639] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Oct  2 06:00:45 node-1 puppet-user[12002]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Oct  2 06:00:45 node-1 puppet-user[12002]: Finished catalog run in 0.05 seconds
Oct  2 06:00:47 node-1 puppet-user[12458]: (Scope(Class[main])) MODULAR: sync_time
Oct  2 06:00:47 node-1 puppet-user[12458]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct  2 06:00:47 node-1 ntpdate[12874]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Oct  2 06:00:53 node-1 ntpdate[12874]: adjust time server 10.20.0.2 offset 0.227760 sec
Oct  2 06:00:53 node-1 puppet-user[12458]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct  2 06:00:53 node-1 puppet-user[12458]: Finished catalog run in 6.17 seconds
Oct  2 06:00:59 node-1 puppet-user[13251]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  2 06:00:59 node-1 puppet-user[13251]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct  2 06:00:59 node-1 puppet-user[13251]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct  2 06:00:59 node-1 puppet-user[13251]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Oct  2 06:00:59 node-1 puppet-user[13251]: Finished catalog run in 0.06 seconds
Oct  2 06:01:00 node-1 kernel: [   85.571609] init: plymouth-upstart-bridge main process ended, respawning
Oct  2 06:01:00 node-1 puppet-agent[8940]: Could not run: SIGTERM
Oct  2 06:01:00 node-1 kernel: [   85.844270] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct  2 06:01:00 node-1 ec2: 
Oct  2 06:01:00 node-1 ec2: #############################################################
Oct  2 06:01:00 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct  2 06:01:00 node-1 ec2: 1024 6e:73:f6:6f:b1:31:a2:16:8e:e7:f0:f4:51:76:db:f8  root@node-1.domain.tld (DSA)
Oct  2 06:01:00 node-1 ec2: 256 82:f2:ea:52:ca:b2:31:4b:37:ae:40:0d:37:33:8d:ec  root@node-1.domain.tld (ECDSA)
Oct  2 06:01:00 node-1 ec2: 256 43:51:34:5c:75:61:25:19:b6:49:d7:5b:c4:a4:2b:1f  root@node-1.domain.tld (ED25519)
Oct  2 06:01:00 node-1 ec2: 2048 e8:7b:39:8a:e8:f2:1e:77:f6:8b:89:72:a6:09:7e:c7  root@node-1.domain.tld (RSA)
Oct  2 06:01:00 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct  2 06:01:00 node-1 ec2: #############################################################
Oct  2 06:01:00 node-1 puppet-user[13708]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct  2 06:01:01 node-1 puppet-user[13708]: Compiled catalog for node-1.domain.tld in environment production in 0.51 seconds
Oct  2 06:01:01 node-1 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Oct  2 06:01:01 node-1 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Oct  2 06:01:01 node-1 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Oct  2 06:01:01 node-1 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Oct  2 06:01:01 node-1 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct  2 06:01:01 node-1 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct  2 06:01:01 node-1 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct  2 06:01:01 node-1 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct  2 06:01:01 node-1 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Oct  2 06:01:01 node-1 puppet-user[13708]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct  2 06:01:01 node-1 CRON[14337]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Oct  2 06:01:02 node-1 puppet-user[13708]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct  2 06:01:02 node-1 puppet-user[13708]: Finished catalog run in 0.75 seconds
Oct  2 06:01:03 node-1 puppet-user[14394]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct  2 06:01:03 node-1 puppet-user[14394]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Oct  2 06:01:06 node-1 puppet-user[14394]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct  2 06:01:11 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  2 06:01:11 node-1 nailgun-agent: I, [2016-10-02T06:01:11.868402 #14340]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  2 06:01:24 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  2 06:01:24 node-1 nailgun-agent: I, [2016-10-02T06:01:24.900892 #14340]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct  2 06:01:33 node-1 puppet-user[14394]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct  2 06:01:33 node-1 puppet-user[14394]: Finished catalog run in 29.56 seconds
Oct  2 06:01:35 node-1 puppet-user[17087]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct  2 06:01:35 node-1 puppet-user[17087]: Compiled catalog for node-1.domain.tld in environment production in 0.58 seconds
Oct  2 06:01:35 node-1 puppet-user[17087]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct  2 06:01:35 node-1 puppet-user[17087]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct  2 06:01:35 node-1 puppet-user[17087]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct  2 06:01:35 node-1 puppet-user[17087]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct  2 06:01:35 node-1 puppet-user[17087]: Finished catalog run in 0.08 seconds
Oct  2 06:01:37 node-1 puppet-user[17549]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct  2 06:01:38 node-1 puppet-user[17549]: Compiled catalog for node-1.domain.tld in environment production in 0.97 seconds
Oct  2 06:01:39 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct  2 06:01:39 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct  2 06:01:39 node-1 crontab[17994]: (root) LIST (root)
Oct  2 06:01:39 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct  2 06:01:39 node-1 crontab[17995]: (root) REPLACE (root)
Oct  2 06:01:40 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct  2 06:01:41 node-1 puppet-user[17549]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct  2 06:01:42 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8390" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  2 06:01:42 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct  2 06:01:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:01:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:01:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:01:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:01:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:01:56 node-1 multipathd: uevent trigger error
<27>Oct  2 06:01:56 node-1 multipathd: uevent trigger error
<27>Oct  2 06:01:56 node-1 multipathd: uevent trigger error
<27>Oct  2 06:01:56 node-1 multipathd: uevent trigger error
<27>Oct  2 06:01:56 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:49 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:49 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:49 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:49 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:49 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:02:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:03:31 node-1 ntpdate[1269]: no servers can be used, exiting
<27>Oct  2 06:03:31 node-1 ntpdate[1435]: no servers can be used, exiting
<27>Oct  2 06:04:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:18 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:18 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:18 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:18 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:18 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:18 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:21 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:21 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:21 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:21 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:22 node-1 multipathd: uevent trigger error
<27>Oct  2 06:04:22 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:15 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:15 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:15 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:15 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:15 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:15 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:26 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  2 06:05:26 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  2 06:05:32 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  2 06:05:32 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  2 06:05:38 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  2 06:05:43 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  2 06:05:43 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  2 06:05:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:05:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:04 node-1 multipathd: uevent trigger error
<129>Oct  2 06:06:06 node-1 haproxy[21343]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:06 node-1 haproxy[21343]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:07 node-1 haproxy[21347]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:07 node-1 haproxy[21347]: proxy mysqld has no server available!
<27>Oct  2 06:06:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:13 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:13 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:13 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:13 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:13 node-1 multipathd: uevent trigger error
<129>Oct  2 06:06:15 node-1 haproxy[24125]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:15 node-1 haproxy[24125]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:16 node-1 haproxy[24142]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:16 node-1 haproxy[24142]: proxy mysqld has no server available!
<129>Oct  2 06:06:16 node-1 haproxy[24142]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:16 node-1 haproxy[24142]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:17 node-1 haproxy[24142]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:17 node-1 haproxy[24142]: proxy object-storage has no server available!
<27>Oct  2 06:06:18 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:18 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:18 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:18 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:18 node-1 multipathd: uevent trigger error
<129>Oct  2 06:06:20 node-1 haproxy[25526]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:20 node-1 haproxy[25526]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:21 node-1 haproxy[25530]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:21 node-1 haproxy[25530]: proxy neutron has no server available!
<129>Oct  2 06:06:21 node-1 haproxy[25530]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:21 node-1 haproxy[25530]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:21 node-1 haproxy[25530]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:21 node-1 haproxy[25530]: proxy mysqld has no server available!
<129>Oct  2 06:06:22 node-1 haproxy[25530]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:22 node-1 haproxy[25530]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:22 node-1 haproxy[25530]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:22 node-1 haproxy[25530]: proxy object-storage has no server available!
<27>Oct  2 06:06:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:24 node-1 multipathd: uevent trigger error
<129>Oct  2 06:06:26 node-1 haproxy[26894]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:26 node-1 haproxy[26894]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:26 node-1 haproxy[26894]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:26 node-1 haproxy[26894]: proxy keystone-1 has no server available!
<129>Oct  2 06:06:26 node-1 haproxy[26894]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:27 node-1 haproxy[26905]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:27 node-1 haproxy[26905]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:27 node-1 haproxy[26905]: proxy keystone-2 has no server available!
<129>Oct  2 06:06:27 node-1 haproxy[26905]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:27 node-1 haproxy[26905]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:27 node-1 haproxy[26905]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:27 node-1 haproxy[26905]: proxy neutron has no server available!
<129>Oct  2 06:06:27 node-1 haproxy[26905]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:27 node-1 haproxy[26905]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:28 node-1 haproxy[26905]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:28 node-1 haproxy[26905]: proxy mysqld has no server available!
<129>Oct  2 06:06:28 node-1 haproxy[26905]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:28 node-1 haproxy[26905]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:28 node-1 haproxy[26905]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:28 node-1 haproxy[26905]: proxy object-storage has no server available!
<27>Oct  2 06:06:29 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:29 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:29 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:29 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:29 node-1 multipathd: uevent trigger error
<129>Oct  2 06:06:32 node-1 haproxy[28258]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:32 node-1 haproxy[28258]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:32 node-1 haproxy[28258]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:32 node-1 haproxy[28258]: proxy keystone-1 has no server available!
<129>Oct  2 06:06:32 node-1 haproxy[28258]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:32 node-1 haproxy[28258]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:32 node-1 haproxy[28258]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:32 node-1 haproxy[28258]: proxy keystone-2 has no server available!
<129>Oct  2 06:06:32 node-1 haproxy[28258]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:32 node-1 haproxy[28258]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:32 node-1 haproxy[28258]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:32 node-1 haproxy[28258]: proxy neutron has no server available!
<129>Oct  2 06:06:33 node-1 haproxy[28267]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:33 node-1 haproxy[28267]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:33 node-1 haproxy[28267]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:33 node-1 haproxy[28267]: proxy mysqld has no server available!
<129>Oct  2 06:06:33 node-1 haproxy[28267]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:33 node-1 haproxy[28267]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:33 node-1 haproxy[28267]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:33 node-1 haproxy[28267]: proxy object-storage has no server available!
<129>Oct  2 06:06:33 node-1 haproxy[28267]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:33 node-1 haproxy[28267]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:33 node-1 haproxy[28267]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:33 node-1 haproxy[28267]: proxy aodh has no server available!
<27>Oct  2 06:06:35 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:35 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:35 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:35 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:35 node-1 multipathd: uevent trigger error
<129>Oct  2 06:06:37 node-1 haproxy[29627]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:37 node-1 haproxy[29627]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:37 node-1 haproxy[29627]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:37 node-1 haproxy[29627]: proxy keystone-1 has no server available!
<129>Oct  2 06:06:37 node-1 haproxy[29627]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:37 node-1 haproxy[29627]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:38 node-1 haproxy[29644]: proxy keystone-2 has no server available!
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:38 node-1 haproxy[29644]: proxy neutron has no server available!
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:38 node-1 haproxy[29644]: proxy mysqld has no server available!
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:38 node-1 haproxy[29644]: proxy object-storage has no server available!
<129>Oct  2 06:06:38 node-1 haproxy[29644]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:39 node-1 haproxy[29644]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:39 node-1 haproxy[29644]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:39 node-1 haproxy[29644]: proxy aodh has no server available!
<129>Oct  2 06:06:39 node-1 haproxy[29644]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:39 node-1 haproxy[29644]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:39 node-1 haproxy[29644]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:39 node-1 haproxy[29644]: proxy ceilometer has no server available!
<27>Oct  2 06:06:40 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:40 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:40 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:40 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:40 node-1 multipathd: uevent trigger error
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:43 node-1 haproxy[31023]: proxy keystone-1 has no server available!
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:43 node-1 haproxy[31023]: proxy keystone-2 has no server available!
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:43 node-1 haproxy[31023]: proxy neutron has no server available!
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:43 node-1 haproxy[31023]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:44 node-1 haproxy[31029]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:44 node-1 haproxy[31029]: proxy mysqld has no server available!
<129>Oct  2 06:06:44 node-1 haproxy[31029]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:44 node-1 haproxy[31029]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:44 node-1 haproxy[31029]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:44 node-1 haproxy[31029]: proxy object-storage has no server available!
<129>Oct  2 06:06:44 node-1 haproxy[31029]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:44 node-1 haproxy[31029]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:44 node-1 haproxy[31029]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:44 node-1 haproxy[31029]: proxy aodh has no server available!
<129>Oct  2 06:06:44 node-1 haproxy[31029]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:44 node-1 haproxy[31029]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:44 node-1 haproxy[31029]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:44 node-1 haproxy[31029]: proxy ceilometer has no server available!
<27>Oct  2 06:06:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:46 node-1 multipathd: uevent trigger error
<129>Oct  2 06:06:48 node-1 haproxy[32381]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:48 node-1 haproxy[32381]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:48 node-1 haproxy[32381]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:48 node-1 haproxy[32381]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:48 node-1 haproxy[32381]: proxy keystone-1 has no server available!
<129>Oct  2 06:06:48 node-1 haproxy[32381]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:48 node-1 haproxy[32381]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:48 node-1 haproxy[32381]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:48 node-1 haproxy[32381]: proxy keystone-2 has no server available!
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:49 node-1 haproxy[32385]: proxy neutron has no server available!
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:49 node-1 haproxy[32385]: proxy mysqld has no server available!
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:49 node-1 haproxy[32385]: proxy object-storage has no server available!
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:49 node-1 haproxy[32385]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:49 node-1 haproxy[32385]: proxy aodh has no server available!
<129>Oct  2 06:06:50 node-1 haproxy[32385]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:50 node-1 haproxy[32385]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:50 node-1 haproxy[32385]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:50 node-1 haproxy[32385]: proxy ceilometer has no server available!
<27>Oct  2 06:06:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:51 node-1 multipathd: uevent trigger error
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:54 node-1 haproxy[1353]: proxy keystone-1 has no server available!
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:54 node-1 haproxy[1353]: proxy keystone-2 has no server available!
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:54 node-1 haproxy[1353]: proxy glance-api has no server available!
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:54 node-1 haproxy[1353]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:55 node-1 haproxy[1362]: proxy glance-glare has no server available!
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:55 node-1 haproxy[1362]: proxy neutron has no server available!
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:55 node-1 haproxy[1362]: proxy glance-registry has no server available!
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:55 node-1 haproxy[1362]: proxy mysqld has no server available!
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:55 node-1 haproxy[1362]: proxy object-storage has no server available!
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:55 node-1 haproxy[1362]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:55 node-1 haproxy[1362]: proxy aodh has no server available!
<129>Oct  2 06:06:56 node-1 haproxy[1362]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:56 node-1 haproxy[1362]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:06:56 node-1 haproxy[1362]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:06:56 node-1 haproxy[1362]: proxy ceilometer has no server available!
<27>Oct  2 06:06:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:06:57 node-1 multipathd: uevent trigger error
<129>Oct  2 06:06:59 node-1 haproxy[2732]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:00 node-1 haproxy[2736]: proxy keystone-1 has no server available!
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:00 node-1 haproxy[2736]: proxy keystone-2 has no server available!
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:00 node-1 haproxy[2736]: proxy nova-api has no server available!
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:00 node-1 haproxy[2736]: proxy nova-metadata-api has no server available!
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:00 node-1 haproxy[2736]: proxy glance-api has no server available!
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:00 node-1 haproxy[2736]: proxy glance-glare has no server available!
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:00 node-1 haproxy[2736]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:00 node-1 haproxy[2736]: proxy neutron has no server available!
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:01 node-1 haproxy[2736]: proxy glance-registry has no server available!
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:01 node-1 haproxy[2736]: proxy mysqld has no server available!
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:01 node-1 haproxy[2736]: proxy object-storage has no server available!
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:01 node-1 haproxy[2736]: proxy aodh has no server available!
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:01 node-1 haproxy[2736]: proxy ceilometer has no server available!
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:01 node-1 haproxy[2736]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:01 node-1 haproxy[2736]: proxy nova-novncproxy has no server available!
<27>Oct  2 06:07:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:03 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:03 node-1 multipathd: uevent trigger error
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:05 node-1 haproxy[4078]: proxy keystone-1 has no server available!
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:05 node-1 haproxy[4078]: proxy keystone-2 has no server available!
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:05 node-1 haproxy[4078]: proxy nova-api has no server available!
<129>Oct  2 06:07:05 node-1 haproxy[4078]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:06 node-1 haproxy[4082]: proxy nova-metadata-api has no server available!
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:06 node-1 haproxy[4082]: proxy cinder-api has no server available!
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:06 node-1 haproxy[4082]: proxy glance-api has no server available!
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:06 node-1 haproxy[4082]: proxy glance-glare has no server available!
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:06 node-1 haproxy[4082]: proxy neutron has no server available!
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:06 node-1 haproxy[4082]: proxy glance-registry has no server available!
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:06 node-1 haproxy[4082]: proxy mysqld has no server available!
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:06 node-1 haproxy[4082]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:07 node-1 haproxy[4082]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:07 node-1 haproxy[4082]: proxy object-storage has no server available!
<129>Oct  2 06:07:07 node-1 haproxy[4082]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:07 node-1 haproxy[4082]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:07 node-1 haproxy[4082]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:07 node-1 haproxy[4082]: proxy aodh has no server available!
<129>Oct  2 06:07:07 node-1 haproxy[4082]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:07 node-1 haproxy[4082]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:07 node-1 haproxy[4082]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:07 node-1 haproxy[4082]: proxy ceilometer has no server available!
<129>Oct  2 06:07:07 node-1 haproxy[4082]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:07 node-1 haproxy[4082]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:07 node-1 haproxy[4082]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:07 node-1 haproxy[4082]: proxy nova-novncproxy has no server available!
<27>Oct  2 06:07:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:08 node-1 multipathd: uevent trigger error
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:11 node-1 haproxy[5456]: proxy keystone-1 has no server available!
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:11 node-1 haproxy[5456]: proxy keystone-2 has no server available!
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:11 node-1 haproxy[5456]: proxy nova-api has no server available!
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:11 node-1 haproxy[5456]: proxy nova-metadata-api has no server available!
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:11 node-1 haproxy[5456]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:11 node-1 haproxy[5456]: proxy cinder-api has no server available!
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:12 node-1 haproxy[5460]: proxy glance-api has no server available!
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:12 node-1 haproxy[5460]: proxy glance-glare has no server available!
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:12 node-1 haproxy[5460]: proxy neutron has no server available!
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:12 node-1 haproxy[5460]: proxy glance-registry has no server available!
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:12 node-1 haproxy[5460]: proxy mysqld has no server available!
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:12 node-1 haproxy[5460]: proxy object-storage has no server available!
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:12 node-1 haproxy[5460]: proxy aodh has no server available!
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:12 node-1 haproxy[5460]: proxy ceilometer has no server available!
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:12 node-1 haproxy[5460]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:12 node-1 haproxy[5460]: proxy heat-api has no server available!
<129>Oct  2 06:07:13 node-1 haproxy[5460]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:13 node-1 haproxy[5460]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:13 node-1 haproxy[5460]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:13 node-1 haproxy[5460]: proxy heat-api-cfn has no server available!
<129>Oct  2 06:07:13 node-1 haproxy[5460]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:13 node-1 haproxy[5460]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:13 node-1 haproxy[5460]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:13 node-1 haproxy[5460]: proxy heat-api-cloudwatch has no server available!
<129>Oct  2 06:07:13 node-1 haproxy[5460]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:13 node-1 haproxy[5460]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:07:13 node-1 haproxy[5460]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:07:13 node-1 haproxy[5460]: proxy nova-novncproxy has no server available!
<27>Oct  2 06:07:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:07:25 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  2 06:07:49 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Oct  2 06:07:51 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct  2 06:08:18 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  2 06:08:23 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  2 06:08:42 node-1 multipathd: uevent trigger error
<27>Oct  2 06:08:42 node-1 multipathd: uevent trigger error
<27>Oct  2 06:08:42 node-1 multipathd: uevent trigger error
<27>Oct  2 06:08:42 node-1 multipathd: uevent trigger error
<27>Oct  2 06:08:42 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:01 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:01 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:01 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:01 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:01 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:21 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct  2 06:11:23 node-1 apache2_error [Sun Oct 02 06:11:17.756650 2016] [mpm_event:notice] [pid 14340:tid 140202639464320] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  2 06:11:23 node-1 apache2_error [Sun Oct 02 06:11:17.756800 2016] [core:notice] [pid 14340:tid 140202639464320] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  2 06:11:23 node-1 apache2_error [Sun Oct 02 06:11:20.697362 2016] [mpm_event:notice] [pid 14340:tid 140202639464320] AH00491: caught SIGTERM, shutting down
<43>Oct  2 06:11:23 node-1 apache2_error [Sun Oct 02 06:11:21.784773 2016] [mpm_worker:notice] [pid 15003:tid 140545617037184] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  2 06:11:23 node-1 apache2_error [Sun Oct 02 06:11:21.784852 2016] [core:notice] [pid 15003:tid 140545617037184] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  2 06:11:26 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:26 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:26 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:26 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:26 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:26 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:34 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:34 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:34 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:34 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:34 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:34 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:34 node-1 multipathd: uevent trigger error
<27>Oct  2 06:11:34 node-1 multipathd: uevent trigger error
<43>Oct  2 06:12:43 node-1 apache2_error [Sun Oct 02 06:12:35.955573 2016] [mpm_worker:notice] [pid 15003:tid 140545617037184] AH00295: caught SIGTERM, shutting down
<43>Oct  2 06:12:43 node-1 apache2_error [Sun Oct 02 06:12:36.706474 2016] [mpm_worker:notice] [pid 28179:tid 140163912812416] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  2 06:12:43 node-1 apache2_error [Sun Oct 02 06:12:36.706518 2016] [core:notice] [pid 28179:tid 140163912812416] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  2 06:13:23 node-1 apache2_error [Sun Oct 02 06:13:20.731017 2016] [mpm_worker:notice] [pid 28179:tid 140163912812416] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  2 06:13:23 node-1 apache2_error [Sun Oct 02 06:13:20.930083 2016] [mpm_worker:warn] [pid 28179:tid 140163912812416] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  2 06:13:23 node-1 apache2_error [Sun Oct 02 06:13:20.933127 2016] [mpm_worker:notice] [pid 28179:tid 140163912812416] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  2 06:13:23 node-1 apache2_error [Sun Oct 02 06:13:20.933154 2016] [core:notice] [pid 28179:tid 140163912812416] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  2 06:14:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:24 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:24 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  2 06:14:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:14:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:09 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:15:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:17:07 node-1 multipathd: uevent trigger error
<27>Oct  2 06:17:07 node-1 multipathd: uevent trigger error
<27>Oct  2 06:17:07 node-1 multipathd: uevent trigger error
<27>Oct  2 06:17:07 node-1 multipathd: uevent trigger error
<27>Oct  2 06:17:07 node-1 multipathd: uevent trigger error
<27>Oct  2 06:17:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  2 06:18:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:30 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:30 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:30 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:30 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:30 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:30 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:30 node-1 multipathd: uevent trigger error
<27>Oct  2 06:18:30 node-1 multipathd: uevent trigger error
<27>Oct  2 06:20:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  2 06:20:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:20:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:20:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:20:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:20:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:20:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:06 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:21:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:22:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:22:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:22:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:22:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:22:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:22:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:22:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:12 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Oct  2 06:23:12 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Oct  2 06:23:12 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Oct  2 06:23:13 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Oct  2 06:23:13 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Oct  2 06:23:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:14 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:30 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  2 06:23:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:23:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:28 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:29 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:29 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:31 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  2 06:26:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:26:42 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Oct  2 06:27:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:27:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:27:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:27:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:27:52 node-1 multipathd: uevent trigger error
<27>Oct  2 06:27:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:27:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:27:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:27:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:27:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:42 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:42 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:42 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:42 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:42 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:28:50 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:02 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:08 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:33 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  2 06:29:38 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:38 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:38 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:38 node-1 multipathd: uevent trigger error
<27>Oct  2 06:29:38 node-1 multipathd: uevent trigger error
<27>Oct  2 06:30:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:30:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:30:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:30:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:30:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:30:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:30:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:30:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:30:57 node-1 multipathd: uevent trigger error
<27>Oct  2 06:30:57 node-1 multipathd: uevent trigger error
<11>Oct  2 06:31:11 node-1 liberasurecode[84588]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:11 node-1 liberasurecode[84588]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:11 node-1 liberasurecode[84588]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:11 node-1 liberasurecode[84588]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:11 node-1 liberasurecode[84615]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:11 node-1 liberasurecode[84615]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:11 node-1 liberasurecode[84615]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:11 node-1 liberasurecode[84615]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:12 node-1 liberasurecode[85025]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:12 node-1 liberasurecode[85025]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:12 node-1 liberasurecode[85025]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:12 node-1 liberasurecode[85025]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[86927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[86927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[86927]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[86927]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[86970]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[86970]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[86970]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[86970]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[87014]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[87014]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[87014]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:17 node-1 liberasurecode[87014]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87078]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87078]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87078]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87078]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87099]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87099]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87099]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87099]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87144]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87144]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87144]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87144]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87221]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87221]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87221]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:18 node-1 liberasurecode[87221]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:34 node-1 liberasurecode[88328]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:34 node-1 liberasurecode[88328]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:34 node-1 liberasurecode[88328]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:31:34 node-1 liberasurecode[88328]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  2 06:31:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:31:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:31:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:31:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:31:43 node-1 multipathd: uevent trigger error
<43>Oct  2 06:32:34 node-1 apache2_error [Sun Oct 02 06:32:30.253271 2016] [mpm_worker:notice] [pid 28179:tid 140163912812416] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  2 06:32:34 node-1 apache2_error [Sun Oct 02 06:32:30.637730 2016] [mpm_worker:warn] [pid 28179:tid 140163912812416] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  2 06:32:34 node-1 apache2_error [Sun Oct 02 06:32:30.644280 2016] [mpm_worker:notice] [pid 28179:tid 140163912812416] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  2 06:32:34 node-1 apache2_error [Sun Oct 02 06:32:30.644324 2016] [core:notice] [pid 28179:tid 140163912812416] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  2 06:32:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  2 06:33:11 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:11 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:11 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:11 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:11 node-1 multipathd: uevent trigger error
<43>Oct  2 06:33:14 node-1 apache2_error [Sun Oct 02 06:33:07.551804 2016] [mpm_worker:notice] [pid 28179:tid 140163912812416] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  2 06:33:14 node-1 apache2_error [Sun Oct 02 06:33:07.748567 2016] [mpm_worker:warn] [pid 28179:tid 140163912812416] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  2 06:33:14 node-1 apache2_error [Sun Oct 02 06:33:07.760137 2016] [mpm_worker:notice] [pid 28179:tid 140163912812416] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  2 06:33:14 node-1 apache2_error [Sun Oct 02 06:33:07.760170 2016] [core:notice] [pid 28179:tid 140163912812416] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  2 06:33:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:19 node-1 multipathd: uevent trigger error
<43>Oct  2 06:33:54 node-1 apache2_error [Sun Oct 02 06:33:53.733044 2016] [mpm_worker:notice] [pid 28179:tid 140163912812416] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  2 06:33:54 node-1 apache2_error [Sun Oct 02 06:33:54.122160 2016] [mpm_worker:warn] [pid 28179:tid 140163912812416] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  2 06:33:54 node-1 apache2_error [Sun Oct 02 06:33:54.134696 2016] [mpm_worker:notice] [pid 28179:tid 140163912812416] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  2 06:33:54 node-1 apache2_error [Sun Oct 02 06:33:54.134740 2016] [core:notice] [pid 28179:tid 140163912812416] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  2 06:33:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:33:58 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:04 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:04 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:04 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:04 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:04 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:10 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:10 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:10 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:10 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:10 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:21 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:21 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:21 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:21 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:21 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:35 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:35 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:35 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:35 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:35 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:35 node-1 multipathd: uevent trigger error
<27>Oct  2 06:34:57 node-1 multipathd: uevent trigger error
<11>Oct  2 06:35:01 node-1 liberasurecode[132379]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:35:01 node-1 liberasurecode[132379]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:35:01 node-1 liberasurecode[132379]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:35:01 node-1 liberasurecode[132379]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  2 06:35:03 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct  2 06:35:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:12 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:46 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:35:51 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:04 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:04 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:04 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:04 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:04 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:05 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:08 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  2 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:17 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:22 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:22 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:22 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:22 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:22 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:31 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:36 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:36 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:36 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:36 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:36 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:36:41 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:19 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:27 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:39 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:39 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:39 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:39 node-1 multipathd: uevent trigger error
<27>Oct  2 06:38:39 node-1 multipathd: uevent trigger error
<129>Oct  2 06:38:48 node-1 haproxy[169649]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:38:48 node-1 haproxy[169649]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct  2 06:39:29 node-1 haproxy[169649]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct  2 06:39:29 node-1 haproxy[169649]: proxy neutron has no server available!
<27>Oct  2 06:39:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:33 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:38 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:38 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:38 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:38 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:38 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:43 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:55 node-1 multipathd: uevent trigger error
<27>Oct  2 06:39:55 node-1 multipathd: uevent trigger error
<11>Oct  2 06:40:01 node-1 liberasurecode[190162]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:40:01 node-1 liberasurecode[190162]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:40:01 node-1 liberasurecode[190162]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  2 06:40:01 node-1 liberasurecode[190162]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
