Oct  1 18:11:13 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8388" x-info="http://www.rsyslog.com"] start
Oct  1 18:11:13 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct  1 18:11:13 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct  1 18:11:13 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct  1 18:11:13 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct  1 18:11:13 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct  1 18:11:13 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct  1 18:11:13 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  1 18:11:13 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=c34ccf65-6645-4c14-989c-6c2e2b0928f0 nomdmonddf nomdmonisw
Oct  1 18:11:13 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct  1 18:11:13 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct  1 18:11:13 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct  1 18:11:13 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct  1 18:11:13 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct  1 18:11:13 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct  1 18:11:13 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct  1 18:11:13 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct  1 18:11:13 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  1 18:11:13 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct  1 18:11:13 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct  1 18:11:13 node-1 kernel: [    0.000000] No AGP bridge found
Oct  1 18:11:13 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct  1 18:11:13 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct  1 18:11:13 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct  1 18:11:13 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct  1 18:11:13 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct  1 18:11:13 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct  1 18:11:13 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct  1 18:11:13 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct  1 18:11:13 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct  1 18:11:13 node-1 kernel: [    0.000000]   2 disabled
Oct  1 18:11:13 node-1 kernel: [    0.000000]   3 disabled
Oct  1 18:11:13 node-1 kernel: [    0.000000]   4 disabled
Oct  1 18:11:13 node-1 kernel: [    0.000000]   5 disabled
Oct  1 18:11:13 node-1 kernel: [    0.000000]   6 disabled
Oct  1 18:11:13 node-1 kernel: [    0.000000]   7 disabled
Oct  1 18:11:13 node-1 kernel: [    0.000000]   8 disabled
Oct  1 18:11:13 node-1 kernel: [    0.000000]   9 disabled
Oct  1 18:11:13 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct  1 18:11:13 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct  1 18:11:13 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct  1 18:11:13 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct  1 18:11:13 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct  1 18:11:13 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct  1 18:11:13 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct  1 18:11:13 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct  1 18:11:13 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct  1 18:11:13 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct  1 18:11:13 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct  1 18:11:13 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct  1 18:11:13 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct  1 18:11:13 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Oct  1 18:11:13 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct  1 18:11:13 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct  1 18:11:13 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct  1 18:11:13 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct  1 18:11:13 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct  1 18:11:13 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct  1 18:11:13 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct  1 18:11:13 node-1 kernel: [    0.000000] Zone ranges:
Oct  1 18:11:13 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] Movable zone start for each node
Oct  1 18:11:13 node-1 kernel: [    0.000000] Early memory node ranges
Oct  1 18:11:13 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Oct  1 18:11:13 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct  1 18:11:13 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct  1 18:11:13 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct  1 18:11:13 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Oct  1 18:11:13 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Oct  1 18:11:13 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct  1 18:11:13 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct  1 18:11:13 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct  1 18:11:13 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct  1 18:11:13 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct  1 18:11:13 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct  1 18:11:13 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct  1 18:11:13 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct  1 18:11:13 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct  1 18:11:13 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct  1 18:11:13 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct  1 18:11:13 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct  1 18:11:13 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct  1 18:11:13 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct  1 18:11:13 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct  1 18:11:13 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct  1 18:11:13 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct  1 18:11:13 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  1 18:11:13 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Oct  1 18:11:13 node-1 kernel: [    0.000000] Policy zone: Normal
Oct  1 18:11:13 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=c34ccf65-6645-4c14-989c-6c2e2b0928f0 nomdmonddf nomdmonisw
Oct  1 18:11:13 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct  1 18:11:13 node-1 kernel: [    0.000000] Checking aperture...
Oct  1 18:11:13 node-1 kernel: [    0.000000] No AGP bridge found
Oct  1 18:11:13 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct  1 18:11:13 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct  1 18:11:13 node-1 kernel: [    0.000000] Memory: 32653460K/33280636K available (7420K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Oct  1 18:11:13 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct  1 18:11:13 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct  1 18:11:13 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct  1 18:11:13 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct  1 18:11:13 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct  1 18:11:13 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct  1 18:11:13 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct  1 18:11:13 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct  1 18:11:13 node-1 kernel: [    0.000000] console [tty0] enabled
Oct  1 18:11:13 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct  1 18:11:13 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct  1 18:11:13 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct  1 18:11:13 node-1 kernel: [    0.000000] hpet clockevent registered
Oct  1 18:11:13 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct  1 18:11:13 node-1 kernel: [    0.004000] tsc: Detected 3491.613 MHz processor
Oct  1 18:11:13 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.22 BogoMIPS (lpj=13966452)
Oct  1 18:11:13 node-1 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct  1 18:11:13 node-1 kernel: [    0.000044] Security Framework initialized
Oct  1 18:11:13 node-1 kernel: [    0.000062] AppArmor: AppArmor initialized
Oct  1 18:11:13 node-1 kernel: [    0.000064] Yama: becoming mindful.
Oct  1 18:11:13 node-1 kernel: [    0.001440] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.006328] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.008249] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.008276] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.008556] Initializing cgroup subsys memory
Oct  1 18:11:13 node-1 kernel: [    0.008564] Initializing cgroup subsys devices
Oct  1 18:11:13 node-1 kernel: [    0.008566] Initializing cgroup subsys freezer
Oct  1 18:11:13 node-1 kernel: [    0.008568] Initializing cgroup subsys blkio
Oct  1 18:11:13 node-1 kernel: [    0.008570] Initializing cgroup subsys perf_event
Oct  1 18:11:13 node-1 kernel: [    0.008572] Initializing cgroup subsys hugetlb
Oct  1 18:11:13 node-1 kernel: [    0.008592] CPU: Physical Processor ID: 0
Oct  1 18:11:13 node-1 kernel: [    0.008593] CPU: Processor Core ID: 0
Oct  1 18:11:13 node-1 kernel: [    0.008597] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct  1 18:11:13 node-1 kernel: [    0.008597] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct  1 18:11:13 node-1 kernel: [    0.009291] mce: CPU supports 22 MCE banks
Oct  1 18:11:13 node-1 kernel: [    0.009318] CPU0: Thermal monitoring enabled (TM1)
Oct  1 18:11:13 node-1 kernel: [    0.009339] process: using mwait in idle threads
Oct  1 18:11:13 node-1 kernel: [    0.009342] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct  1 18:11:13 node-1 kernel: [    0.009342] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct  1 18:11:13 node-1 kernel: [    0.009342] tlb_flushall_shift: 6
Oct  1 18:11:13 node-1 kernel: [    0.009431] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct  1 18:11:13 node-1 kernel: [    0.010155] ACPI: Core revision 20131115
Oct  1 18:11:13 node-1 kernel: [    0.022825] ACPI: All ACPI Tables successfully acquired
Oct  1 18:11:13 node-1 kernel: [    0.022990] ftrace: allocating 28614 entries in 112 pages
Oct  1 18:11:13 node-1 kernel: [    0.031688] dmar: Host address width 46
Oct  1 18:11:13 node-1 kernel: [    0.031691] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct  1 18:11:13 node-1 kernel: [    0.031697] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  1 18:11:13 node-1 kernel: [    0.031698] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct  1 18:11:13 node-1 kernel: [    0.031702] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct  1 18:11:13 node-1 kernel: [    0.031704] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct  1 18:11:13 node-1 kernel: [    0.031705] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct  1 18:11:13 node-1 kernel: [    0.031706] dmar: ATSR flags: 0x0
Oct  1 18:11:13 node-1 kernel: [    0.031707] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct  1 18:11:13 node-1 kernel: [    0.031708] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct  1 18:11:13 node-1 kernel: [    0.031824] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct  1 18:11:13 node-1 kernel: [    0.031825] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct  1 18:11:13 node-1 kernel: [    0.031826] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct  1 18:11:13 node-1 kernel: [    0.031827] HPET id 0 under DRHD base 0xc7ffc000
Oct  1 18:11:13 node-1 kernel: [    0.031828] Your BIOS is broken and requested that x2apic be disabled.
Oct  1 18:11:13 node-1 kernel: [    0.031828] This will slightly decrease performance.
Oct  1 18:11:13 node-1 kernel: [    0.031828] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct  1 18:11:13 node-1 kernel: [    0.032259] Enabled IRQ remapping in xapic mode
Oct  1 18:11:13 node-1 kernel: [    0.032260] x2apic not enabled, IRQ remapping is in xapic mode
Oct  1 18:11:13 node-1 kernel: [    0.032264] Switched APIC routing to physical flat.
Oct  1 18:11:13 node-1 kernel: [    0.032833] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct  1 18:11:13 node-1 kernel: [    0.072479] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct  1 18:11:13 node-1 kernel: [    0.072485] TSC deadline timer enabled
Oct  1 18:11:13 node-1 kernel: [    0.072492] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct  1 18:11:13 node-1 kernel: [    0.072498] ... version:                3
Oct  1 18:11:13 node-1 kernel: [    0.072499] ... bit width:              48
Oct  1 18:11:13 node-1 kernel: [    0.072500] ... generic registers:      4
Oct  1 18:11:13 node-1 kernel: [    0.072501] ... value mask:             0000ffffffffffff
Oct  1 18:11:13 node-1 kernel: [    0.072502] ... max period:             0000ffffffffffff
Oct  1 18:11:13 node-1 kernel: [    0.072503] ... fixed-purpose events:   3
Oct  1 18:11:13 node-1 kernel: [    0.072504] ... event mask:             000000070000000f
Oct  1 18:11:13 node-1 kernel: [    0.073876] x86: Booting SMP configuration:
Oct  1 18:11:13 node-1 kernel: [    0.087978] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct  1 18:11:13 node-1 kernel: [    0.073877] .... node  #0, CPUs:        #1  #2  #3
Oct  1 18:11:13 node-1 kernel: [    0.115880] .... node  #1, CPUs:    #4  #5  #6  #7
Oct  1 18:11:13 node-1 kernel: [    0.270007] .... node  #0, CPUs:    #8  #9 #10 #11
Oct  1 18:11:13 node-1 kernel: [    0.325629] .... node  #1, CPUs:   #12 #13 #14 #15
Oct  1 18:11:13 node-1 kernel: [    0.382673] x86: Booted up 2 nodes, 16 CPUs
Oct  1 18:11:13 node-1 kernel: [    0.382677] smpboot: Total of 16 processors activated (111744.10 BogoMIPS)
Oct  1 18:11:13 node-1 kernel: [    0.407637] devtmpfs: initialized
Oct  1 18:11:13 node-1 kernel: [    0.409970] EVM: security.selinux
Oct  1 18:11:13 node-1 kernel: [    0.409972] EVM: security.SMACK64
Oct  1 18:11:13 node-1 kernel: [    0.409973] EVM: security.ima
Oct  1 18:11:13 node-1 kernel: [    0.409973] EVM: security.capability
Oct  1 18:11:13 node-1 kernel: [    0.410027] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.410694] pinctrl core: initialized pinctrl subsystem
Oct  1 18:11:13 node-1 kernel: [    0.410751] regulator-dummy: no parameters
Oct  1 18:11:13 node-1 kernel: [    0.410782] RTC time: 18:10:37, date: 10/01/16
Oct  1 18:11:13 node-1 kernel: [    0.410816] NET: Registered protocol family 16
Oct  1 18:11:13 node-1 kernel: [    0.410900] cpuidle: using governor ladder
Oct  1 18:11:13 node-1 kernel: [    0.410901] cpuidle: using governor menu
Oct  1 18:11:13 node-1 kernel: [    0.410936] ACPI: bus type PCI registered
Oct  1 18:11:13 node-1 kernel: [    0.410938] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct  1 18:11:13 node-1 kernel: [    0.410983] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct  1 18:11:13 node-1 kernel: [    0.410986] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct  1 18:11:13 node-1 kernel: [    0.424734] PCI: Using configuration type 1 for base access
Oct  1 18:11:13 node-1 kernel: [    0.425751] bio: create slab <bio-0> at 0
Oct  1 18:11:13 node-1 kernel: [    0.426037] ACPI: Added _OSI(Module Device)
Oct  1 18:11:13 node-1 kernel: [    0.426039] ACPI: Added _OSI(Processor Device)
Oct  1 18:11:13 node-1 kernel: [    0.426040] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct  1 18:11:13 node-1 kernel: [    0.426041] ACPI: Added _OSI(Processor Aggregator Device)
Oct  1 18:11:13 node-1 kernel: [    0.438857] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct  1 18:11:13 node-1 kernel: [    0.449597] ACPI: Interpreter enabled
Oct  1 18:11:13 node-1 kernel: [    0.449603] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct  1 18:11:13 node-1 kernel: [    0.449607] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct  1 18:11:13 node-1 kernel: [    0.449609] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct  1 18:11:13 node-1 kernel: [    0.449616] ACPI: (supports S0 S4 S5)
Oct  1 18:11:13 node-1 kernel: [    0.449618] ACPI: Using IOAPIC for interrupt routing
Oct  1 18:11:13 node-1 kernel: [    0.449661] HEST: Table parsing has been initialized.
Oct  1 18:11:13 node-1 kernel: [    0.449664] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct  1 18:11:13 node-1 kernel: [    0.450223] ACPI: No dock devices found.
Oct  1 18:11:13 node-1 kernel: [    0.461880] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct  1 18:11:13 node-1 kernel: [    0.461885] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  1 18:11:13 node-1 kernel: [    0.461888] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  1 18:11:13 node-1 kernel: [    0.461916] PCI host bridge to bus 0000:ff
Oct  1 18:11:13 node-1 kernel: [    0.461918] pci_bus 0000:ff: root bus resource [bus ff]
Oct  1 18:11:13 node-1 kernel: [    0.461927] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.461965] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.461997] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462032] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462062] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.462092] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.462124] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462154] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462185] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462213] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462240] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462267] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462296] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462322] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462349] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462376] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462406] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462433] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462461] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.462489] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462516] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.462542] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462570] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462600] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.462636] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462668] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462698] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462730] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462761] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462792] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462826] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462859] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462890] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462922] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462953] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.462984] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463016] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463047] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463075] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463108] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463143] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463179] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463213] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463246] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463276] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463305] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463335] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463364] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463396] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463426] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463457] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463486] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463516] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463543] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463572] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463603] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463634] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463696] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct  1 18:11:13 node-1 kernel: [    0.463699] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  1 18:11:13 node-1 kernel: [    0.463702] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct  1 18:11:13 node-1 kernel: [    0.463720] PCI host bridge to bus 0000:7f
Oct  1 18:11:13 node-1 kernel: [    0.463722] pci_bus 0000:7f: root bus resource [bus 7f]
Oct  1 18:11:13 node-1 kernel: [    0.463727] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463754] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.463783] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463812] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463834] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.463858] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.463884] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463911] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463933] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463956] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.463978] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464001] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464025] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464047] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464070] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464095] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464117] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464140] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464162] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.464186] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464208] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.464230] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464253] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464279] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct  1 18:11:13 node-1 kernel: [    0.464312] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464338] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464364] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464390] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464415] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464443] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464470] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464499] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464524] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464552] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464580] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464607] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464636] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464661] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464687] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464718] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464743] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464770] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464798] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464824] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464849] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464874] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464899] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464925] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464952] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.464978] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.465008] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.465033] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.465055] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.465080] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.465104] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.465133] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.465159] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.466404] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct  1 18:11:13 node-1 kernel: [    0.466408] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  1 18:11:13 node-1 kernel: [    0.467549] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  1 18:11:13 node-1 kernel: [    0.468061] PCI host bridge to bus 0000:00
Oct  1 18:11:13 node-1 kernel: [    0.468063] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct  1 18:11:13 node-1 kernel: [    0.468065] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct  1 18:11:13 node-1 kernel: [    0.468066] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct  1 18:11:13 node-1 kernel: [    0.468067] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct  1 18:11:13 node-1 kernel: [    0.468069] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct  1 18:11:13 node-1 kernel: [    0.468070] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct  1 18:11:13 node-1 kernel: [    0.468072] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct  1 18:11:13 node-1 kernel: [    0.468077] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct  1 18:11:13 node-1 kernel: [    0.468160] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.468191] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.468233] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct  1 18:11:13 node-1 kernel: [    0.468252] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.468281] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.468322] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct  1 18:11:13 node-1 kernel: [    0.468340] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.468370] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.468410] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct  1 18:11:13 node-1 kernel: [    0.468427] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.468497] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.468575] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.468650] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct  1 18:11:13 node-1 kernel: [    0.468655] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct  1 18:11:13 node-1 kernel: [    0.468741] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct  1 18:11:13 node-1 kernel: [    0.468889] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct  1 18:11:13 node-1 kernel: [    0.468907] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct  1 18:11:13 node-1 kernel: [    0.468985] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.469040] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct  1 18:11:13 node-1 kernel: [    0.469061] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.469117] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.469160] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct  1 18:11:13 node-1 kernel: [    0.469187] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.469243] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.469286] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct  1 18:11:13 node-1 kernel: [    0.469310] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct  1 18:11:13 node-1 kernel: [    0.469328] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct  1 18:11:13 node-1 kernel: [    0.469406] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.469456] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct  1 18:11:13 node-1 kernel: [    0.469479] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct  1 18:11:13 node-1 kernel: [    0.469726] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct  1 18:11:13 node-1 kernel: [    0.469732] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct  1 18:11:13 node-1 kernel: [    0.469738] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.469744] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.469751] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct  1 18:11:13 node-1 kernel: [    0.469790] pci 0000:01:00.0: supports D1 D2
Oct  1 18:11:13 node-1 kernel: [    0.479649] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  1 18:11:13 node-1 kernel: [    0.479657] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  1 18:11:13 node-1 kernel: [    0.479661] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  1 18:11:13 node-1 kernel: [    0.479810] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.479843] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct  1 18:11:13 node-1 kernel: [    0.491652] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  1 18:11:13 node-1 kernel: [    0.491659] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.491663] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  1 18:11:13 node-1 kernel: [    0.491731] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.491800] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.491876] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.491922] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  1 18:11:13 node-1 kernel: [    0.491925] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.491927] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  1 18:11:13 node-1 kernel: [    0.491980] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.492107] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.492161] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  1 18:11:13 node-1 kernel: [    0.492163] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.492165] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  1 18:11:13 node-1 kernel: [    0.492214] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.492334] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.492372] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.492494] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.492532] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.492671] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.492709] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct  1 18:11:13 node-1 kernel: [    0.492828] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct  1 18:11:13 node-1 kernel: [    0.492871] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  1 18:11:13 node-1 kernel: [    0.492873] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.492875] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  1 18:11:13 node-1 kernel: [    0.492935] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct  1 18:11:13 node-1 kernel: [    0.493002] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.493054] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.493095] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct  1 18:11:13 node-1 kernel: [    0.493177] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct  1 18:11:13 node-1 kernel: [    0.493283] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  1 18:11:13 node-1 kernel: [    0.493285] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.493287] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  1 18:11:13 node-1 kernel: [    0.493343] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct  1 18:11:13 node-1 kernel: [    0.493397] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.493445] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.493678] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  1 18:11:13 node-1 kernel: [    0.493682] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  1 18:11:13 node-1 kernel: [    0.493745] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct  1 18:11:13 node-1 kernel: [    0.493801] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.493849] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.494059] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  1 18:11:13 node-1 kernel: [    0.494063] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  1 18:11:13 node-1 kernel: [    0.494121] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct  1 18:11:13 node-1 kernel: [    0.494181] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.494234] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct  1 18:11:13 node-1 kernel: [    0.494455] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  1 18:11:13 node-1 kernel: [    0.494459] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  1 18:11:13 node-1 kernel: [    0.494636] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  1 18:11:13 node-1 kernel: [    0.494674] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  1 18:11:13 node-1 kernel: [    0.494751] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct  1 18:11:13 node-1 kernel: [    0.494770] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct  1 18:11:13 node-1 kernel: [    0.494783] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct  1 18:11:13 node-1 kernel: [    0.494796] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct  1 18:11:13 node-1 kernel: [    0.494847] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct  1 18:11:13 node-1 kernel: [    0.503656] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  1 18:11:13 node-1 kernel: [    0.503665] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  1 18:11:13 node-1 kernel: [    0.503718] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct  1 18:11:13 node-1 kernel: [    0.504263] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct  1 18:11:13 node-1 kernel: [    0.504266] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct  1 18:11:13 node-1 kernel: [    0.504386] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct  1 18:11:13 node-1 kernel: [    0.504494] PCI host bridge to bus 0000:80
Oct  1 18:11:13 node-1 kernel: [    0.504496] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct  1 18:11:13 node-1 kernel: [    0.504498] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct  1 18:11:13 node-1 kernel: [    0.504499] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct  1 18:11:13 node-1 kernel: [    0.504507] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.504571] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.504638] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct  1 18:11:13 node-1 kernel: [    0.504702] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct  1 18:11:13 node-1 kernel: [    0.504708] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct  1 18:11:13 node-1 kernel: [    0.504781] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct  1 18:11:13 node-1 kernel: [    0.505080] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct  1 18:11:13 node-1 kernel: [    0.505112] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct  1 18:11:13 node-1 kernel: [    0.505142] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct  1 18:11:13 node-1 kernel: [    0.505171] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct  1 18:11:13 node-1 kernel: [    0.505200] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  1 18:11:13 node-1 kernel: [    0.505230] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  1 18:11:13 node-1 kernel: [    0.505260] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  1 18:11:13 node-1 kernel: [    0.505290] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct  1 18:11:13 node-1 kernel: [    0.505376] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct  1 18:11:13 node-1 kernel: [    0.505380] ACPI: \_SB_.UNC1: notify handler is installed
Oct  1 18:11:13 node-1 kernel: [    0.505381] ACPI: \_SB_.UNC0: notify handler is installed
Oct  1 18:11:13 node-1 kernel: [    0.505397] ACPI: \_SB_.PCI0: notify handler is installed
Oct  1 18:11:13 node-1 kernel: [    0.505450] ACPI: \_SB_.PCI1: notify handler is installed
Oct  1 18:11:13 node-1 kernel: [    0.505530] Found 4 acpi root devices
Oct  1 18:11:13 node-1 kernel: [    0.505639] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct  1 18:11:13 node-1 kernel: [    0.505641] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct  1 18:11:13 node-1 kernel: [    0.505643] vgaarb: loaded
Oct  1 18:11:13 node-1 kernel: [    0.505644] vgaarb: bridge control possible 0000:0c:00.0
Oct  1 18:11:13 node-1 kernel: [    0.505768] SCSI subsystem initialized
Oct  1 18:11:13 node-1 kernel: [    0.505832] libata version 3.00 loaded.
Oct  1 18:11:13 node-1 kernel: [    0.505848] ACPI: bus type USB registered
Oct  1 18:11:13 node-1 kernel: [    0.505858] usbcore: registered new interface driver usbfs
Oct  1 18:11:13 node-1 kernel: [    0.505863] usbcore: registered new interface driver hub
Oct  1 18:11:13 node-1 kernel: [    0.505888] usbcore: registered new device driver usb
Oct  1 18:11:13 node-1 kernel: [    0.506062] PCI: Using ACPI for IRQ routing
Oct  1 18:11:13 node-1 kernel: [    0.509679] PCI: pci_cache_line_size set to 64 bytes
Oct  1 18:11:13 node-1 kernel: [    0.509883] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct  1 18:11:13 node-1 kernel: [    0.509884] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Oct  1 18:11:13 node-1 kernel: [    0.509885] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct  1 18:11:13 node-1 kernel: [    0.509954] NetLabel: Initializing
Oct  1 18:11:13 node-1 kernel: [    0.509955] NetLabel:  domain hash size = 128
Oct  1 18:11:13 node-1 kernel: [    0.509956] NetLabel:  protocols = UNLABELED CIPSOv4
Oct  1 18:11:13 node-1 kernel: [    0.509966] NetLabel:  unlabeled traffic allowed by default
Oct  1 18:11:13 node-1 kernel: [    0.510024] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct  1 18:11:13 node-1 kernel: [    0.510028] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct  1 18:11:13 node-1 kernel: [    0.512098] Switched to clocksource hpet
Oct  1 18:11:13 node-1 kernel: [    0.516562] AppArmor: AppArmor Filesystem Enabled
Oct  1 18:11:13 node-1 kernel: [    0.516600] pnp: PnP ACPI init
Oct  1 18:11:13 node-1 kernel: [    0.516613] ACPI: bus type PNP registered
Oct  1 18:11:13 node-1 kernel: [    0.516797] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct  1 18:11:13 node-1 kernel: [    0.516809] pnp 00:01: [dma 4]
Oct  1 18:11:13 node-1 kernel: [    0.516827] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct  1 18:11:13 node-1 kernel: [    0.516862] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct  1 18:11:13 node-1 kernel: [    0.516886] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct  1 18:11:13 node-1 kernel: [    0.516912] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct  1 18:11:13 node-1 kernel: [    0.516958] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct  1 18:11:13 node-1 kernel: [    0.517072] system 00:06: [io  0x0500-0x057f] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517074] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct  1 18:11:13 node-1 kernel: [    0.517076] system 00:06: [io  0x0580-0x059f] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517077] system 00:06: [io  0x0600-0x061f] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517079] system 00:06: [io  0x0880-0x0883] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517080] system 00:06: [io  0x0800-0x081f] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517084] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct  1 18:11:13 node-1 kernel: [    0.517085] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517087] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517088] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517090] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517091] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517093] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct  1 18:11:13 node-1 kernel: [    0.517095] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct  1 18:11:13 node-1 kernel: [    0.517196] pnp 00:07: [dma 0 disabled]
Oct  1 18:11:13 node-1 kernel: [    0.517230] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  1 18:11:13 node-1 kernel: [    0.517313] pnp 00:08: [dma 0 disabled]
Oct  1 18:11:13 node-1 kernel: [    0.517349] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct  1 18:11:13 node-1 kernel: [    0.517407] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct  1 18:11:13 node-1 kernel: [    0.517858] pnp: PnP ACPI: found 10 devices
Oct  1 18:11:13 node-1 kernel: [    0.517860] ACPI: bus type PNP unregistered
Oct  1 18:11:13 node-1 kernel: [    0.523854] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct  1 18:11:13 node-1 kernel: [    0.523858] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct  1 18:11:13 node-1 kernel: [    0.523861] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct  1 18:11:13 node-1 kernel: [    0.523866] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct  1 18:11:13 node-1 kernel: [    0.523868] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.523883] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct  1 18:11:13 node-1 kernel: [    0.523912] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct  1 18:11:13 node-1 kernel: [    0.523926] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct  1 18:11:13 node-1 kernel: [    0.523955] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct  1 18:11:13 node-1 kernel: [    0.523970] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct  1 18:11:13 node-1 kernel: [    0.523999] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct  1 18:11:13 node-1 kernel: [    0.524013] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct  1 18:11:13 node-1 kernel: [    0.524042] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct  1 18:11:13 node-1 kernel: [    0.524044] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.524059] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  1 18:11:13 node-1 kernel: [    0.524092] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct  1 18:11:13 node-1 kernel: [    0.524094] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.524108] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct  1 18:11:13 node-1 kernel: [    0.524137] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct  1 18:11:13 node-1 kernel: [    0.524139] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.524142] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  1 18:11:13 node-1 kernel: [    0.524147] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct  1 18:11:13 node-1 kernel: [    0.524149] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.524151] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct  1 18:11:13 node-1 kernel: [    0.524156] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct  1 18:11:13 node-1 kernel: [    0.524162] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct  1 18:11:13 node-1 kernel: [    0.524171] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct  1 18:11:13 node-1 kernel: [    0.524175] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct  1 18:11:13 node-1 kernel: [    0.524182] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct  1 18:11:13 node-1 kernel: [    0.524183] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct  1 18:11:13 node-1 kernel: [    0.524184] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct  1 18:11:13 node-1 kernel: [    0.524184] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct  1 18:11:13 node-1 kernel: [    0.524185] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct  1 18:11:13 node-1 kernel: [    0.524186] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct  1 18:11:13 node-1 kernel: [    0.524187] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct  1 18:11:13 node-1 kernel: [    0.524188] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct  1 18:11:13 node-1 kernel: [    0.524189] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.524190] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  1 18:11:13 node-1 kernel: [    0.524191] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.524192] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct  1 18:11:13 node-1 kernel: [    0.524193] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.524194] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  1 18:11:13 node-1 kernel: [    0.524195] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.524196] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct  1 18:11:13 node-1 kernel: [    0.524197] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct  1 18:11:13 node-1 kernel: [    0.524198] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct  1 18:11:13 node-1 kernel: [    0.524200] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct  1 18:11:13 node-1 kernel: [    0.524201] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct  1 18:11:13 node-1 kernel: [    0.524202] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct  1 18:11:13 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct  1 18:11:13 node-1 kernel: [    0.524203] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct  1 18:11:13 node-1 kernel: [    0.524206] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct  1 18:11:13 node-1 kernel: [    0.524207] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct  1 18:11:13 node-1 kernel: [    0.524250] NET: Registered protocol family 2
Oct  1 18:11:13 node-1 kernel: [    0.524551] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.524921] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.525087] TCP: Hash tables configured (established 262144 bind 65536)
Oct  1 18:11:13 node-1 kernel: [    0.525133] TCP: reno registered
Oct  1 18:11:13 node-1 kernel: [    0.525165] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.525274] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.525434] NET: Registered protocol family 1
Oct  1 18:11:13 node-1 kernel: [    0.560193] pci 0000:0c:00.0: Video device with shadowed ROM
Oct  1 18:11:13 node-1 kernel: [    0.560208] PCI: CLS 64 bytes, default 64
Oct  1 18:11:13 node-1 kernel: [    0.560302] Trying to unpack rootfs image as initramfs...
Oct  1 18:11:13 node-1 kernel: [    0.781884] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Oct  1 18:11:13 node-1 kernel: [    0.781942] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct  1 18:11:13 node-1 kernel: [    0.781952] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Oct  1 18:11:13 node-1 kernel: [    0.782497] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782503] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782510] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782516] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782527] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782542] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782559] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782572] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782582] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782589] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782596] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782602] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782610] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782623] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782634] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782646] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct  1 18:11:13 node-1 kernel: [    0.782707] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct  1 18:11:13 node-1 kernel: [    0.782712] Scanning for low memory corruption every 60 seconds
Oct  1 18:11:13 node-1 kernel: [    0.782974] Initialise system trusted keyring
Oct  1 18:11:13 node-1 kernel: [    0.783014] audit: initializing netlink socket (disabled)
Oct  1 18:11:13 node-1 kernel: [    0.783021] type=2000 audit(1475345436.732:1): initialized
Oct  1 18:11:13 node-1 kernel: [    0.800696] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct  1 18:11:13 node-1 kernel: [    0.802149] zbud: loaded
Oct  1 18:11:13 node-1 kernel: [    0.802262] VFS: Disk quotas dquot_6.5.2
Oct  1 18:11:13 node-1 kernel: [    0.802301] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct  1 18:11:13 node-1 kernel: [    0.802669] fuse init (API version 7.22)
Oct  1 18:11:13 node-1 kernel: [    0.802727] msgmni has been set to 32768
Oct  1 18:11:13 node-1 kernel: [    0.802773] Key type big_key registered
Oct  1 18:11:13 node-1 kernel: [    0.803259] Key type asymmetric registered
Oct  1 18:11:13 node-1 kernel: [    0.803261] Asymmetric key parser 'x509' registered
Oct  1 18:11:13 node-1 kernel: [    0.803281] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct  1 18:11:13 node-1 kernel: [    0.803340] io scheduler noop registered
Oct  1 18:11:13 node-1 kernel: [    0.803342] io scheduler deadline registered (default)
Oct  1 18:11:13 node-1 kernel: [    0.803360] io scheduler cfq registered
Oct  1 18:11:13 node-1 kernel: [    0.803646] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    0.803743] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    0.803840] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    0.803933] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    0.804033] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    0.804116] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    0.804363] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct  1 18:11:13 node-1 kernel: [    0.804381] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct  1 18:11:13 node-1 kernel: [    0.804393] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct  1 18:11:13 node-1 kernel: [    0.804400] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804402] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804404] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct  1 18:11:13 node-1 kernel: [    0.804408] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804410] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804411] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804412] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804413] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804415] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804416] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804418] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804419] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804420] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804422] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804423] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804425] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct  1 18:11:13 node-1 kernel: [    0.804429] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804431] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct  1 18:11:13 node-1 kernel: [    0.804444] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804447] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct  1 18:11:13 node-1 kernel: [    0.804456] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804458] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct  1 18:11:13 node-1 kernel: [    0.804461] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct  1 18:11:13 node-1 kernel: [    0.804473] ioapic: probe of 0000:00:05.4 failed with error -22
Oct  1 18:11:13 node-1 kernel: [    0.804554] ioapic: probe of 0000:80:05.4 failed with error -22
Oct  1 18:11:13 node-1 kernel: [    0.804558] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct  1 18:11:13 node-1 kernel: [    0.804567] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct  1 18:11:13 node-1 kernel: [    0.804601] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct  1 18:11:13 node-1 kernel: [    0.804602] vesafb: scrolling: redraw
Oct  1 18:11:13 node-1 kernel: [    0.804603] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct  1 18:11:13 node-1 kernel: [    0.824219] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct  1 18:11:13 node-1 kernel: [    0.832743] Console: switching to colour frame buffer device 80x30
Oct  1 18:11:13 node-1 kernel: [    0.841515] fb0: VESA VGA frame buffer device
Oct  1 18:11:13 node-1 kernel: [    0.841709] intel_idle: MWAIT substates: 0x2120
Oct  1 18:11:13 node-1 kernel: [    0.841710] intel_idle: v0.4 model 0x3F
Oct  1 18:11:13 node-1 kernel: [    0.841711] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct  1 18:11:13 node-1 kernel: [    0.841931] ipmi message handler version 39.2
Oct  1 18:11:13 node-1 kernel: [    0.842195] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct  1 18:11:13 node-1 kernel: [    0.842624] ACPI: AC Adapter [P111] (on-line)
Oct  1 18:11:13 node-1 kernel: [    0.847878] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct  1 18:11:13 node-1 kernel: [    0.858874] ACPI: Power Button [PWRB]
Oct  1 18:11:13 node-1 kernel: [    0.864633] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct  1 18:11:13 node-1 kernel: [    0.876370] ACPI: Power Button [PWRF]
Oct  1 18:11:13 node-1 kernel: [    0.897660] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct  1 18:11:13 node-1 kernel: [    0.909314] pstore: Registered erst as persistent store backend
Oct  1 18:11:13 node-1 kernel: [    0.915495] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct  1 18:11:13 node-1 kernel: [    0.927457] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct  1 18:11:13 node-1 kernel: [    0.954217] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct  1 18:11:13 node-1 kernel: [    0.987498] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct  1 18:11:13 node-1 kernel: [    1.001564] Linux agpgart interface v0.103
Oct  1 18:11:13 node-1 kernel: [    1.009199] brd: module loaded
Oct  1 18:11:13 node-1 kernel: [    1.016245] loop: module loaded
Oct  1 18:11:13 node-1 kernel: [    1.022953] libphy: Fixed MDIO Bus: probed
Oct  1 18:11:13 node-1 kernel: [    1.029412] tun: Universal TUN/TAP device driver, 1.6
Oct  1 18:11:13 node-1 kernel: [    1.035865] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct  1 18:11:13 node-1 kernel: [    1.042371] PPP generic driver version 2.4.2
Oct  1 18:11:13 node-1 kernel: [    1.048746] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct  1 18:11:13 node-1 kernel: [    1.055205] ehci-pci: EHCI PCI platform driver
Oct  1 18:11:13 node-1 kernel: [    1.061723] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct  1 18:11:13 node-1 kernel: [    1.068133] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct  1 18:11:13 node-1 kernel: [    1.080663] ehci-pci 0000:00:1a.0: debug port 2
Oct  1 18:11:13 node-1 kernel: [    1.090853] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct  1 18:11:13 node-1 kernel: [    1.090871] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct  1 18:11:13 node-1 kernel: [    1.107584] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct  1 18:11:13 node-1 kernel: [    1.113641] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct  1 18:11:13 node-1 kernel: [    1.119800] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  1 18:11:13 node-1 kernel: [    1.131679] usb usb1: Product: EHCI Host Controller
Oct  1 18:11:13 node-1 kernel: [    1.137763] usb usb1: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  1 18:11:13 node-1 kernel: [    1.143899] usb usb1: SerialNumber: 0000:00:1a.0
Oct  1 18:11:13 node-1 kernel: [    1.149941] hub 1-0:1.0: USB hub found
Oct  1 18:11:13 node-1 kernel: [    1.155778] hub 1-0:1.0: 2 ports detected
Oct  1 18:11:13 node-1 kernel: [    1.161638] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct  1 18:11:13 node-1 kernel: [    1.167262] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct  1 18:11:13 node-1 kernel: [    1.178326] ehci-pci 0000:00:1d.0: debug port 2
Oct  1 18:11:13 node-1 kernel: [    1.187692] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct  1 18:11:13 node-1 kernel: [    1.187695] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct  1 18:11:13 node-1 kernel: [    1.203502] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct  1 18:11:13 node-1 kernel: [    1.208751] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct  1 18:11:13 node-1 kernel: [    1.214054] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct  1 18:11:13 node-1 kernel: [    1.224631] usb usb2: Product: EHCI Host Controller
Oct  1 18:11:13 node-1 kernel: [    1.230107] usb usb2: Manufacturer: Linux 3.13.0-96-generic ehci_hcd
Oct  1 18:11:13 node-1 kernel: [    1.235658] usb usb2: SerialNumber: 0000:00:1d.0
Oct  1 18:11:13 node-1 kernel: [    1.241180] hub 2-0:1.0: USB hub found
Oct  1 18:11:13 node-1 kernel: [    1.246532] hub 2-0:1.0: 2 ports detected
Oct  1 18:11:13 node-1 kernel: [    1.251829] ehci-platform: EHCI generic platform driver
Oct  1 18:11:13 node-1 kernel: [    1.257069] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct  1 18:11:13 node-1 kernel: [    1.262388] ohci-pci: OHCI PCI platform driver
Oct  1 18:11:13 node-1 kernel: [    1.267695] ohci-platform: OHCI generic platform driver
Oct  1 18:11:13 node-1 kernel: [    1.272894] uhci_hcd: USB Universal Host Controller Interface driver
Oct  1 18:11:13 node-1 kernel: [    1.278234] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct  1 18:11:13 node-1 kernel: [    1.471282] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct  1 18:11:13 node-1 kernel: [    1.647497] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct  1 18:11:13 node-1 kernel: [    1.653002] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  1 18:11:13 node-1 kernel: [    1.658765] hub 1-1:1.0: USB hub found
Oct  1 18:11:13 node-1 kernel: [    1.664234] hub 1-1:1.0: 6 ports detected
Oct  1 18:11:13 node-1 kernel: [    1.779016] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct  1 18:11:13 node-1 kernel: [    1.779018] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct  1 18:11:13 node-1 kernel: [    2.047158] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct  1 18:11:13 node-1 kernel: [    2.052646] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct  1 18:11:13 node-1 kernel: [    2.058421] hub 2-1:1.0: USB hub found
Oct  1 18:11:13 node-1 kernel: [    2.064019] hub 2-1:1.0: 8 ports detected
Oct  1 18:11:13 node-1 kernel: [    2.319662] i8042: No controller found
Oct  1 18:11:13 node-1 kernel: [    2.325016] mousedev: PS/2 mouse device common for all mice
Oct  1 18:11:13 node-1 kernel: [    2.330464] rtc_cmos 00:02: RTC can wake from S4
Oct  1 18:11:13 node-1 kernel: [    2.335986] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct  1 18:11:13 node-1 kernel: [    2.341512] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct  1 18:11:13 node-1 kernel: [    2.346596] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct  1 18:11:13 node-1 kernel: [    2.357974] device-mapper: uevent: version 1.0.3
Oct  1 18:11:13 node-1 kernel: [    2.363569] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct  1 18:11:13 node-1 kernel: [    2.374731] ledtrig-cpu: registered to indicate activity on CPUs
Oct  1 18:11:13 node-1 kernel: [    2.380712] TCP: cubic registered
Oct  1 18:11:13 node-1 kernel: [    2.386596] NET: Registered protocol family 10
Oct  1 18:11:13 node-1 kernel: [    2.392592] NET: Registered protocol family 17
Oct  1 18:11:13 node-1 kernel: [    2.398327] Key type dns_resolver registered
Oct  1 18:11:13 node-1 kernel: [    2.404311] Loading compiled-in X.509 certificates
Oct  1 18:11:13 node-1 kernel: [    2.410449] Loaded X.509 cert 'Magrathea: Glacier signing key: 5ce91a5f5a603a312b28b6e022cb5618e5dc44ed'
Oct  1 18:11:13 node-1 kernel: [    2.421780] registered taskstats version 1
Oct  1 18:11:13 node-1 kernel: [    2.429694] Key type trusted registered
Oct  1 18:11:13 node-1 kernel: [    2.437210] Key type encrypted registered
Oct  1 18:11:13 node-1 kernel: [    2.442643] AppArmor: AppArmor sha1 policy hashing enabled
Oct  1 18:11:13 node-1 kernel: [    2.448110] IMA: No TPM chip found, activating TPM-bypass!
Oct  1 18:11:13 node-1 kernel: [    2.454249] regulator-dummy: disabling
Oct  1 18:11:13 node-1 kernel: [    2.459797]   Magic number: 4:624:189
Oct  1 18:11:13 node-1 kernel: [    2.465299] acpi device:48: hash matches
Oct  1 18:11:13 node-1 kernel: [    2.470633] acpi device:1b: hash matches
Oct  1 18:11:13 node-1 kernel: [    2.475971] rtc_cmos 00:02: setting system clock to 2016-10-01 18:10:39 UTC (1475345439)
Oct  1 18:11:13 node-1 kernel: [    2.483370] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct  1 18:11:13 node-1 kernel: [    2.483371] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  1 18:11:13 node-1 kernel: [    2.483372] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct  1 18:11:13 node-1 kernel: [    2.483373] usb 2-1.4: Manufacturer: Avocent
Oct  1 18:11:13 node-1 kernel: [    2.483374] usb 2-1.4: SerialNumber: 20111102-00000001
Oct  1 18:11:13 node-1 kernel: [    2.521420] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct  1 18:11:13 node-1 kernel: [    2.526893] EDD information not available.
Oct  1 18:11:13 node-1 kernel: [    2.532284] PM: Hibernation image not present or could not be loaded.
Oct  1 18:11:13 node-1 kernel: [    2.533151] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct  1 18:11:13 node-1 kernel: [    2.543949] Write protecting the kernel read-only data: 12288k
Oct  1 18:11:13 node-1 kernel: [    2.549894] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct  1 18:11:13 node-1 kernel: [    2.561962] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Oct  1 18:11:13 node-1 kernel: [    2.593600] device-mapper: multipath: version 1.6.0 loaded
Oct  1 18:11:13 node-1 kernel: [    2.601369] systemd-udevd[217]: starting version 204
Oct  1 18:11:13 node-1 kernel: [    2.627208] md: linear personality registered for level -1
Oct  1 18:11:13 node-1 kernel: [    2.640891] md: multipath personality registered for level -4
Oct  1 18:11:13 node-1 kernel: [    2.648831] md: raid0 personality registered for level 0
Oct  1 18:11:13 node-1 kernel: [    2.656865] md: raid1 personality registered for level 1
Oct  1 18:11:13 node-1 kernel: [    2.667337] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct  1 18:11:13 node-1 kernel: [    2.673504] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct  1 18:11:13 node-1 kernel: [    2.679843] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct  1 18:11:13 node-1 kernel: [    2.680832] megasas: FW now in Ready state
Oct  1 18:11:13 node-1 kernel: [    2.681287] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.681405] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.681520] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.681667] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.681794] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.681911] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.682036] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.682137] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.682663] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.682776] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.682839] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.682998] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.683153] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.683326] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.683457] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.683603] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.684310] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct  1 18:11:13 node-1 kernel: [    2.705502] hidraw: raw HID events driver (C) Jiri Kosina
Oct  1 18:11:13 node-1 kernel: [    2.713912] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Oct  1 18:11:13 node-1 kernel: [    2.721572] usbcore: registered new interface driver usbhid
Oct  1 18:11:13 node-1 kernel: [    2.721601] usbhid: USB HID core driver
Oct  1 18:11:13 node-1 kernel: [    2.730376] raid6: sse2x1    1698 MB/s
Oct  1 18:11:13 node-1 kernel: [    2.746394] 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  1 18:11:13 node-1 kernel: [    2.759737] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  1 18:11:13 node-1 kernel: [    2.766584] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.766590] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.766596] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.766600] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.766647] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  1 18:11:13 node-1 kernel: [    2.798163] raid6: sse2x2    3431 MB/s
Oct  1 18:11:13 node-1 kernel: [    2.870110] raid6: sse2x4   10133 MB/s
Oct  1 18:11:13 node-1 kernel: [    2.942040] raid6: avx2x1   14952 MB/s
Oct  1 18:11:13 node-1 kernel: [    3.013979] raid6: avx2x2   18865 MB/s
Oct  1 18:11:13 node-1 kernel: [    3.085920] raid6: avx2x4   21354 MB/s
Oct  1 18:11:13 node-1 kernel: [    3.091528] raid6: using algorithm avx2x4 (21354 MB/s)
Oct  1 18:11:13 node-1 kernel: [    3.097139] raid6: using avx2x2 recovery algorithm
Oct  1 18:11:13 node-1 kernel: [    3.102654] Switched to clocksource tsc
Oct  1 18:11:13 node-1 kernel: [    3.102656] megasas:IOC Init cmd success
Oct  1 18:11:13 node-1 kernel: [    3.114230] xor: automatically using best checksumming function:
Oct  1 18:11:13 node-1 kernel: [    3.118080] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Oct  1 18:11:13 node-1 kernel: [    3.118081] 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  1 18:11:13 node-1 kernel: [    3.118083] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct  1 18:11:13 node-1 kernel: [    3.118271] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.118362] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.118430] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.118531] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.118641] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.118750] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.119020] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.126213] megasas: INIT adapter done
Oct  1 18:11:13 node-1 kernel: [    3.136640] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Oct  1 18:11:13 node-1 kernel: [    3.136654] 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  1 18:11:13 node-1 kernel: [    3.136668] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  1 18:11:13 node-1 kernel: [    3.137068] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.137210] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.137308] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.137419] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.137643] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.155073] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Oct  1 18:11:13 node-1 kernel: [    3.155081] 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  1 18:11:13 node-1 kernel: [    3.155093] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct  1 18:11:13 node-1 kernel: [    3.155401] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.155502] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.155603] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.155787] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.156083] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct  1 18:11:13 node-1 kernel: [    3.198057] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct  1 18:11:13 node-1 kernel: [    3.199708] scsi0 : LSI SAS based MegaRAID driver
Oct  1 18:11:13 node-1 kernel: [    3.207270] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  1 18:11:13 node-1 kernel: [    3.268305] 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  1 18:11:13 node-1 kernel: [    3.272451] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct  1 18:11:13 node-1 kernel: [    3.276785] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct  1 18:11:13 node-1 kernel: [    3.276812] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct  1 18:11:13 node-1 kernel: [    3.277106] sd 0:2:0:0: [sda] Write Protect is off
Oct  1 18:11:13 node-1 kernel: [    3.277107] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct  1 18:11:13 node-1 kernel: [    3.277173] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct  1 18:11:13 node-1 kernel: [    3.301082]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct  1 18:11:13 node-1 kernel: [    3.302651] sd 0:2:0:0: [sda] Attached SCSI disk
Oct  1 18:11:13 node-1 kernel: [    3.305723]    avx       : 36839.000 MB/sec
Oct  1 18:11:13 node-1 kernel: [    3.356689] 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  1 18:11:13 node-1 kernel: [    3.370230] async_tx: api initialized (async)
Oct  1 18:11:13 node-1 kernel: [    3.370266] 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  1 18:11:13 node-1 kernel: [    3.370322] 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  1 18:11:13 node-1 kernel: [    3.370375] 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  1 18:11:13 node-1 kernel: [    3.370421] 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  1 18:11:13 node-1 kernel: [    3.436943] md: raid6 personality registered for level 6
Oct  1 18:11:13 node-1 kernel: [    3.444301] md: raid5 personality registered for level 5
Oct  1 18:11:13 node-1 kernel: [    3.451410] md: raid4 personality registered for level 4
Oct  1 18:11:13 node-1 kernel: [    3.461404] md: raid10 personality registered for level 10
Oct  1 18:11:13 node-1 kernel: [    3.486084] random: lvm urandom read with 30 bits of entropy available
Oct  1 18:11:13 node-1 kernel: [    3.522698] multipathd (368): /proc/368/oom_adj is deprecated, please use /proc/368/oom_score_adj instead.
Oct  1 18:11:13 node-1 kernel: [    3.630645] bio: create slab <bio-1> at 1
Oct  1 18:11:13 node-1 kernel: [    4.446642] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct  1 18:11:13 node-1 kernel: [    4.950476] init: plymouth-upstart-bridge main process (552) terminated with status 1
Oct  1 18:11:13 node-1 kernel: [    4.963283] init: plymouth-upstart-bridge main process ended, respawning
Oct  1 18:11:13 node-1 kernel: [    4.972349] init: plymouth-upstart-bridge main process (564) terminated with status 1
Oct  1 18:11:13 node-1 kernel: [    4.984717] init: plymouth-upstart-bridge main process ended, respawning
Oct  1 18:11:13 node-1 kernel: [    5.111567] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct  1 18:11:13 node-1 kernel: [    5.149845] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct  1 18:11:13 node-1 kernel: [    5.322281] random: nonblocking pool is initialized
Oct  1 18:11:13 node-1 kernel: [    5.330328] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct  1 18:11:13 node-1 kernel: [    5.372297] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct  1 18:11:13 node-1 kernel: [    5.465421] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct  1 18:11:13 node-1 kernel: [    5.650080] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct  1 18:11:13 node-1 kernel: [    5.704701] XFS (dm-0): Mounting Filesystem
Oct  1 18:11:13 node-1 kernel: [    5.842139] XFS (dm-0): Ending clean mount
Oct  1 18:11:13 node-1 kernel: [    5.926443] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct  1 18:11:13 node-1 kernel: [    5.995684] XFS (dm-1): Mounting Filesystem
Oct  1 18:11:13 node-1 kernel: [    6.132784] XFS (dm-1): Ending clean mount
Oct  1 18:11:13 node-1 kernel: [    8.231587] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct  1 18:11:13 node-1 kernel: [    8.259840] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct  1 18:11:13 node-1 kernel: [    8.417802] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct  1 18:11:13 node-1 kernel: [    8.417809] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Oct  1 18:11:13 node-1 kernel: [    8.417813] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Oct  1 18:11:13 node-1 kernel: [    8.417818] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Oct  1 18:11:13 node-1 kernel: [    8.446432] systemd-udevd[781]: starting version 204
Oct  1 18:11:13 node-1 kernel: [    8.645506] wmi: Mapper loaded
Oct  1 18:11:13 node-1 kernel: [    8.666462] power_meter ACPI000D:00: Found ACPI power meter.
Oct  1 18:11:13 node-1 kernel: [    8.666484] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct  1 18:11:13 node-1 kernel: [    8.679547] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct  1 18:11:13 node-1 kernel: [    8.686639] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct  1 18:11:13 node-1 kernel: [    8.686644] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  1 18:11:13 node-1 kernel: [    8.686647] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct  1 18:11:13 node-1 kernel: [    8.686649] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct  1 18:11:13 node-1 kernel: [    8.686662] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct  1 18:11:13 node-1 kernel: [    8.701294] IPMI System Interface driver.
Oct  1 18:11:13 node-1 kernel: [    8.701325] ipmi_si: probing via ACPI
Oct  1 18:11:13 node-1 kernel: [    8.701342] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct  1 18:11:13 node-1 kernel: [    8.701343] ipmi_si: Adding ACPI-specified kcs state machine
Oct  1 18:11:13 node-1 kernel: [    8.701350] ipmi_si: probing via SMBIOS
Oct  1 18:11:13 node-1 kernel: [    8.701351] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct  1 18:11:13 node-1 kernel: [    8.701351] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct  1 18:11:13 node-1 kernel: [    8.701353] ipmi_si: probing via SPMI
Oct  1 18:11:13 node-1 kernel: [    8.701353] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct  1 18:11:13 node-1 kernel: [    8.701354] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct  1 18:11:13 node-1 kernel: [    8.701355] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct  1 18:11:13 node-1 kernel: [    8.761589] systemd-udevd[827]: renamed network interface eth1 to enp7s0
Oct  1 18:11:13 node-1 kernel: [    8.797447] systemd-udevd[800]: renamed network interface eth0 to enp6s0
Oct  1 18:11:13 node-1 kernel: [    8.837404] systemd-udevd[798]: renamed network interface eth2 to enp8s0
Oct  1 18:11:13 node-1 kernel: [    8.849208] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct  1 18:11:13 node-1 kernel: [    8.849214] ipmi_si 00:09: IPMI kcs interface initialized
Oct  1 18:11:13 node-1 kernel: [    8.861404] systemd-udevd[802]: renamed network interface eth3 to enp9s0
Oct  1 18:11:13 node-1 kernel: [    9.146418] type=1400 audit(1475345446.170:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1051 comm="apparmor_parser"
Oct  1 18:11:13 node-1 kernel: [    9.146584] type=1400 audit(1475345446.170:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1051 comm="apparmor_parser"
Oct  1 18:11:13 node-1 kernel: [    9.146719] type=1400 audit(1475345446.170:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1051 comm="apparmor_parser"
Oct  1 18:11:13 node-1 kernel: [    9.157523] type=1400 audit(1475345446.182:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1059 comm="apparmor_parser"
Oct  1 18:11:13 node-1 kernel: [    9.157699] type=1400 audit(1475345446.182:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1059 comm="apparmor_parser"
Oct  1 18:11:13 node-1 kernel: [    9.157833] type=1400 audit(1475345446.182:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1059 comm="apparmor_parser"
Oct  1 18:11:13 node-1 kernel: [    9.169085] type=1400 audit(1475345446.194:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1063 comm="apparmor_parser"
Oct  1 18:11:13 node-1 kernel: [    9.169231] type=1400 audit(1475345446.194:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1063 comm="apparmor_parser"
Oct  1 18:11:13 node-1 kernel: [    9.169353] type=1400 audit(1475345446.194:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1063 comm="apparmor_parser"
Oct  1 18:11:13 node-1 kernel: [    9.180201] type=1400 audit(1475345446.202:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Oct  1 18:11:13 node-1 kernel: [    9.664038] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct  1 18:11:13 node-1 kernel: [    9.671794] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct  1 18:11:13 node-1 kernel: [    9.914591] enic 0000:06:00.0 enp6s0: Link UP
Oct  1 18:11:13 node-1 kernel: [    9.915811] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct  1 18:11:13 node-1 kernel: [    9.915821] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct  1 18:11:13 node-1 kernel: [   19.186664] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct  1 18:11:14 node-1 failsafe: Failsafe of 120 seconds reached.
Oct  1 18:11:14 node-1 kernel: [   38.470225] init: failsafe main process (8415) killed by TERM signal
Oct  1 18:11:14 node-1 dbus[8436]: [system] AppArmor D-Bus mediation is enabled
Oct  1 18:11:14 node-1 kernel: [   38.682302] audit_printk_skb: 30 callbacks suppressed
Oct  1 18:11:14 node-1 kernel: [   38.682304] type=1400 audit(1475345474.979:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8541 comm="apparmor_parser"
Oct  1 18:11:14 node-1 kernel: [   38.682586] type=1400 audit(1475345474.979:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8540 comm="apparmor_parser"
Oct  1 18:11:14 node-1 kernel: [   38.682591] type=1400 audit(1475345474.979:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8540 comm="apparmor_parser"
Oct  1 18:11:14 node-1 kernel: [   38.682593] type=1400 audit(1475345474.979:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8540 comm="apparmor_parser"
Oct  1 18:11:14 node-1 kernel: [   38.682825] type=1400 audit(1475345474.979:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8540 comm="apparmor_parser"
Oct  1 18:11:14 node-1 kernel: [   38.682827] type=1400 audit(1475345474.979:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8540 comm="apparmor_parser"
Oct  1 18:11:14 node-1 kernel: [   38.682939] type=1400 audit(1475345474.979:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8540 comm="apparmor_parser"
Oct  1 18:11:15 node-1 kernel: [   38.785117] type=1400 audit(1475345475.083:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8543 comm="apparmor_parser"
Oct  1 18:11:15 node-1 cron[8573]: (CRON) INFO (pidfile fd = 3)
Oct  1 18:11:15 node-1 anacron[8590]: Anacron 2.3 started on 2016-10-01
Oct  1 18:11:15 node-1 cron[8597]: (CRON) STARTUP (fork ok)
Oct  1 18:11:15 node-1 anacron[8590]: Will run job `cron.daily' in 5 min.
Oct  1 18:11:15 node-1 anacron[8590]: Will run job `cron.weekly' in 10 min.
Oct  1 18:11:15 node-1 anacron[8590]: Will run job `cron.monthly' in 15 min.
Oct  1 18:11:15 node-1 anacron[8590]: Jobs will be executed sequentially
Oct  1 18:11:15 node-1 multipathd: path checkers start up
Oct  1 18:11:15 node-1 cron[8597]: (CRON) INFO (Running @reboot jobs)
Oct  1 18:11:15 node-1 postfix/master[8753]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct  1 18:11:18 node-1 puppet-agent[8938]: Reopening log files
Oct  1 18:11:20 node-1 puppet-agent[8938]: Could not request certificate: Connection refused - connect(2)
Oct  1 18:11:33 node-1 puppet-user[9146]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct  1 18:11:33 node-1 puppet-user[9146]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct  1 18:11:34 node-1 puppet-user[9146]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct  1 18:11:34 node-1 puppet-user[9146]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct  1 18:11:35 node-1 puppet-user[9146]: Finished catalog run in 0.96 seconds
Oct  1 18:11:36 node-1 multipathd: uevent trigger error
Oct  1 18:11:36 node-1 puppet-user[9566]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  1 18:11:36 node-1 puppet-user[9566]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct  1 18:11:36 node-1 puppet-user[9566]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct  1 18:11:36 node-1 puppet-user[9566]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct  1 18:11:36 node-1 puppet-user[9566]: (/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  1 18:11:36 node-1 puppet-user[9566]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct  1 18:11:36 node-1 puppet-user[9566]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct  1 18:11:36 node-1 puppet-user[9566]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct  1 18:11:36 node-1 puppet-user[9566]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct  1 18:11:36 node-1 puppet-user[9566]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct  1 18:11:36 node-1 puppet-user[9566]: Finished catalog run in 0.07 seconds
Oct  1 18:11:38 node-1 puppet-user[10023]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct  1 18:11:38 node-1 puppet-user[10023]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct  1 18:11:38 node-1 puppet-user[10023]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct  1 18:11:38 node-1 puppet-user[10023]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct  1 18:11:38 node-1 puppet-user[10023]: Finished catalog run in 0.04 seconds
Oct  1 18:11:39 node-1 puppet-user[10481]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct  1 18:11:39 node-1 puppet-user[10481]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct  1 18:11:40 node-1 puppet-user[10481]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct  1 18:11:40 node-1 puppet-user[10481]: Finished catalog run in 0.05 seconds
Oct  1 18:11:41 node-1 puppet-user[10928]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct  1 18:11:41 node-1 puppet-user[10928]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Oct  1 18:11:41 node-1 puppet-user[10928]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct  1 18:11:42 node-1 puppet-user[10928]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Oct  1 18:11:42 node-1 puppet-user[10928]: Finished catalog run in 0.44 seconds
Oct  1 18:11:43 node-1 puppet-user[11582]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct  1 18:11:43 node-1 puppet-user[11582]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Oct  1 18:11:43 node-1 puppet-user[11582]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct  1 18:11:43 node-1 puppet-user[11582]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct  1 18:11:43 node-1 puppet-user[11582]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Oct  1 18:11:43 node-1 puppet-user[11582]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct  1 18:11:43 node-1 puppet-user[11582]: Finished catalog run in 0.19 seconds
Oct  1 18:11:45 node-1 puppet-user[12060]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct  1 18:11:45 node-1 puppet-user[12060]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Oct  1 18:11:45 node-1 puppet-user[12060]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct  1 18:11:45 node-1 kernel: [   69.181593] nr_pdflush_threads exported in /proc is scheduled for removal
Oct  1 18:11:45 node-1 kernel: [   69.181643] 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  1 18:11:45 node-1 puppet-user[12060]: (/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  1 18:11:45 node-1 puppet-user[12060]: Finished catalog run in 0.06 seconds
Oct  1 18:11:47 node-1 puppet-user[12517]: (Scope(Class[main])) MODULAR: sync_time
Oct  1 18:11:47 node-1 puppet-user[12517]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct  1 18:11:47 node-1 ntpdate[12924]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Oct  1 18:11:53 node-1 ntpdate[12924]: adjust time server 10.20.0.2 offset 0.384450 sec
Oct  1 18:11:53 node-1 puppet-user[12517]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct  1 18:11:53 node-1 puppet-user[12517]: Finished catalog run in 6.17 seconds
Oct  1 18:11:53 node-1 kernel: [   77.653989] init: plymouth-upstart-bridge main process ended, respawning
Oct  1 18:11:54 node-1 puppet-agent[8938]: Could not run: SIGTERM
Oct  1 18:11:54 node-1 kernel: [   77.971322] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct  1 18:11:54 node-1 ec2: 
Oct  1 18:11:54 node-1 ec2: #############################################################
Oct  1 18:11:54 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct  1 18:11:54 node-1 ec2: 1024 b9:02:70:16:2c:96:58:e5:ff:e9:6b:c9:4c:29:d7:a9  root@node-1.domain.tld (DSA)
Oct  1 18:11:54 node-1 ec2: 256 24:8e:9f:04:e1:24:a4:84:4b:75:a9:d9:25:9b:9b:5b  root@node-1.domain.tld (ECDSA)
Oct  1 18:11:54 node-1 ec2: 256 f5:13:a0:1e:b9:5f:fe:e6:ca:ff:4b:63:30:93:51:98  root@node-1.domain.tld (ED25519)
Oct  1 18:11:54 node-1 ec2: 2048 5c:02:fe:28:ae:b4:1b:52:2e:90:28:d2:a4:4b:21:aa  root@node-1.domain.tld (RSA)
Oct  1 18:11:54 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct  1 18:11:54 node-1 ec2: #############################################################
Oct  1 18:11:58 node-1 puppet-user[13292]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct  1 18:11:58 node-1 puppet-user[13292]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct  1 18:11:59 node-1 puppet-user[13292]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct  1 18:11:59 node-1 puppet-user[13292]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Oct  1 18:11:59 node-1 puppet-user[13292]: Finished catalog run in 0.07 seconds
Oct  1 18:12:00 node-1 puppet-user[13754]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct  1 18:12:00 node-1 puppet-user[13754]: Compiled catalog for node-1.domain.tld in environment production in 0.49 seconds
Oct  1 18:12:01 node-1 puppet-user[13754]: (/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  1 18:12:01 node-1 puppet-user[13754]: (/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  1 18:12:01 node-1 puppet-user[13754]: (/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  1 18:12:01 node-1 puppet-user[13754]: (/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  1 18:12:01 node-1 puppet-user[13754]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct  1 18:12:01 node-1 puppet-user[13754]: (/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  1 18:12:01 node-1 puppet-user[13754]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct  1 18:12:01 node-1 puppet-user[13754]: (/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  1 18:12:01 node-1 puppet-user[13754]: (/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  1 18:12:01 node-1 puppet-user[13754]: (/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  1 18:12:01 node-1 CRON[14208]: (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  1 18:12:01 node-1 puppet-user[13754]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct  1 18:12:01 node-1 puppet-user[13754]: Finished catalog run in 0.85 seconds
Oct  1 18:12:03 node-1 puppet-user[14270]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct  1 18:12:03 node-1 puppet-user[14270]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Oct  1 18:12:06 node-1 puppet-user[14270]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct  1 18:12:16 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  1 18:12:16 node-1 nailgun-agent: I, [2016-10-01T18:12:16.514178 #14211]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct  1 18:12:29 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct  1 18:12:29 node-1 nailgun-agent: I, [2016-10-01T18:12:29.852979 #14211]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct  1 18:12:33 node-1 puppet-user[14270]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct  1 18:12:33 node-1 puppet-user[14270]: Finished catalog run in 29.95 seconds
Oct  1 18:12:35 node-1 puppet-user[16981]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct  1 18:12:36 node-1 puppet-user[16981]: Compiled catalog for node-1.domain.tld in environment production in 0.71 seconds
Oct  1 18:12:36 node-1 puppet-user[16981]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct  1 18:12:36 node-1 puppet-user[16981]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct  1 18:12:36 node-1 puppet-user[16981]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct  1 18:12:36 node-1 puppet-user[16981]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct  1 18:12:36 node-1 puppet-user[16981]: Finished catalog run in 0.09 seconds
Oct  1 18:12:38 node-1 puppet-user[17444]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct  1 18:12:39 node-1 puppet-user[17444]: Compiled catalog for node-1.domain.tld in environment production in 0.94 seconds
Oct  1 18:12:39 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct  1 18:12:39 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct  1 18:12:39 node-1 crontab[17885]: (root) LIST (root)
Oct  1 18:12:39 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct  1 18:12:39 node-1 crontab[17886]: (root) REPLACE (root)
Oct  1 18:12:40 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct  1 18:12:41 node-1 puppet-user[17444]: (/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  1 18:12:41 node-1 puppet-user[17444]: (/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  1 18:12:41 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct  1 18:12:42 node-1 puppet-user[17444]: (/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  1 18:12:42 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8388" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct  1 18:12:42 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct  1 18:12:44 node-1 multipathd: uevent trigger error
<27>Oct  1 18:12:44 node-1 multipathd: uevent trigger error
<27>Oct  1 18:12:44 node-1 multipathd: uevent trigger error
<27>Oct  1 18:12:44 node-1 multipathd: uevent trigger error
<27>Oct  1 18:12:44 node-1 multipathd: uevent trigger error
<27>Oct  1 18:12:57 node-1 multipathd: uevent trigger error
<27>Oct  1 18:12:57 node-1 multipathd: uevent trigger error
<27>Oct  1 18:12:57 node-1 multipathd: uevent trigger error
<27>Oct  1 18:12:57 node-1 multipathd: uevent trigger error
<27>Oct  1 18:13:00 node-1 multipathd: uevent trigger error
<27>Oct  1 18:13:00 node-1 multipathd: uevent trigger error
<27>Oct  1 18:13:00 node-1 multipathd: uevent trigger error
<27>Oct  1 18:13:00 node-1 multipathd: uevent trigger error
<27>Oct  1 18:13:00 node-1 multipathd: uevent trigger error
<27>Oct  1 18:13:55 node-1 ntpdate[28769]: no servers can be used, exiting
<27>Oct  1 18:14:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:30 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:30 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:30 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:30 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:44 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:44 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:44 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:44 node-1 multipathd: uevent trigger error
<27>Oct  1 18:14:44 node-1 multipathd: uevent trigger error
<27>Oct  1 18:15:38 node-1 multipathd: uevent trigger error
<27>Oct  1 18:15:38 node-1 multipathd: uevent trigger error
<27>Oct  1 18:15:38 node-1 multipathd: uevent trigger error
<27>Oct  1 18:15:38 node-1 multipathd: uevent trigger error
<27>Oct  1 18:15:47 node-1 multipathd: uevent trigger error
<27>Oct  1 18:15:47 node-1 multipathd: uevent trigger error
<27>Oct  1 18:15:47 node-1 multipathd: uevent trigger error
<27>Oct  1 18:15:47 node-1 multipathd: uevent trigger error
<27>Oct  1 18:15:50 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  1 18:15:50 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  1 18:15:56 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  1 18:15:56 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  1 18:16:01 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  1 18:16:07 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  1 18:16:07 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct  1 18:16:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:15 node-1 ntpdate[13988]: the NTP socket is in use, exiting
<27>Oct  1 18:16:15 node-1 ntpdate[14093]: the NTP socket is in use, exiting
<27>Oct  1 18:16:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:27 node-1 multipathd: uevent trigger error
<129>Oct  1 18:16:29 node-1 haproxy[16553]: 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  1 18:16:30 node-1 haproxy[16557]: Backup Server mysqld/node-3 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  1 18:16:30 node-1 haproxy[16557]: Backup Server mysqld/node-5 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  1 18:16:30 node-1 haproxy[16557]: proxy mysqld has no server available!
<27>Oct  1 18:16:32 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:33 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:33 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:33 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:33 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:36 node-1 multipathd: uevent trigger error
<129>Oct  1 18:16:38 node-1 haproxy[19162]: 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  1 18:16:39 node-1 haproxy[19166]: Backup Server mysqld/node-3 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  1 18:16:39 node-1 haproxy[19166]: Backup Server mysqld/node-5 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  1 18:16:39 node-1 haproxy[19166]: proxy mysqld has no server available!
<129>Oct  1 18:16:39 node-1 haproxy[19166]: 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  1 18:16:40 node-1 haproxy[19166]: Server object-storage/node-3 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  1 18:16:40 node-1 haproxy[19166]: Server object-storage/node-5 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  1 18:16:40 node-1 haproxy[19166]: proxy object-storage has no server available!
<27>Oct  1 18:16:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:41 node-1 multipathd: uevent trigger error
<129>Oct  1 18:16:44 node-1 haproxy[20525]: 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  1 18:16:44 node-1 haproxy[20525]: Server neutron/node-3 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  1 18:16:44 node-1 haproxy[20525]: Server neutron/node-5 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  1 18:16:44 node-1 haproxy[20525]: proxy neutron has no server available!
<129>Oct  1 18:16:44 node-1 haproxy[20525]: 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  1 18:16:45 node-1 haproxy[20529]: Backup Server mysqld/node-3 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  1 18:16:45 node-1 haproxy[20529]: Backup Server mysqld/node-5 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  1 18:16:45 node-1 haproxy[20529]: proxy mysqld has no server available!
<129>Oct  1 18:16:45 node-1 haproxy[20529]: 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  1 18:16:45 node-1 haproxy[20529]: Server object-storage/node-3 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  1 18:16:45 node-1 haproxy[20529]: Server object-storage/node-5 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  1 18:16:45 node-1 haproxy[20529]: proxy object-storage has no server available!
<27>Oct  1 18:16:47 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:47 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:47 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:47 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:47 node-1 multipathd: uevent trigger error
<129>Oct  1 18:16:49 node-1 haproxy[21903]: 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  1 18:16:49 node-1 haproxy[21903]: Server keystone-1/node-3 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  1 18:16:50 node-1 haproxy[21907]: Server keystone-1/node-5 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  1 18:16:50 node-1 haproxy[21907]: proxy keystone-1 has no server available!
<129>Oct  1 18:16:50 node-1 haproxy[21907]: 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  1 18:16:50 node-1 haproxy[21907]: Server keystone-2/node-3 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  1 18:16:50 node-1 haproxy[21907]: Server keystone-2/node-5 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  1 18:16:50 node-1 haproxy[21907]: proxy keystone-2 has no server available!
<129>Oct  1 18:16:50 node-1 haproxy[21907]: 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  1 18:16:50 node-1 haproxy[21907]: Server neutron/node-3 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  1 18:16:50 node-1 haproxy[21907]: Server neutron/node-5 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  1 18:16:50 node-1 haproxy[21907]: proxy neutron has no server available!
<129>Oct  1 18:16:50 node-1 haproxy[21907]: 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  1 18:16:51 node-1 haproxy[21907]: Backup Server mysqld/node-3 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  1 18:16:51 node-1 haproxy[21907]: Backup Server mysqld/node-5 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  1 18:16:51 node-1 haproxy[21907]: proxy mysqld has no server available!
<129>Oct  1 18:16:51 node-1 haproxy[21907]: 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  1 18:16:51 node-1 haproxy[21907]: Server object-storage/node-3 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  1 18:16:51 node-1 haproxy[21907]: Server object-storage/node-5 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  1 18:16:51 node-1 haproxy[21907]: proxy object-storage has no server available!
<27>Oct  1 18:16:52 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:52 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:52 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:53 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:53 node-1 multipathd: uevent trigger error
<129>Oct  1 18:16:55 node-1 haproxy[23245]: 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  1 18:16:55 node-1 haproxy[23245]: Server keystone-1/node-3 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  1 18:16:55 node-1 haproxy[23245]: Server keystone-1/node-5 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  1 18:16:55 node-1 haproxy[23245]: proxy keystone-1 has no server available!
<129>Oct  1 18:16:55 node-1 haproxy[23245]: 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  1 18:16:55 node-1 haproxy[23245]: Server keystone-2/node-3 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  1 18:16:55 node-1 haproxy[23245]: Server keystone-2/node-5 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  1 18:16:55 node-1 haproxy[23245]: proxy keystone-2 has no server available!
<129>Oct  1 18:16:55 node-1 haproxy[23245]: 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  1 18:16:55 node-1 haproxy[23245]: Server neutron/node-3 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  1 18:16:56 node-1 haproxy[23249]: Server neutron/node-5 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  1 18:16:56 node-1 haproxy[23249]: proxy neutron has no server available!
<129>Oct  1 18:16:56 node-1 haproxy[23249]: 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  1 18:16:56 node-1 haproxy[23249]: Backup Server mysqld/node-3 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  1 18:16:56 node-1 haproxy[23249]: Backup Server mysqld/node-5 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  1 18:16:56 node-1 haproxy[23249]: proxy mysqld has no server available!
<129>Oct  1 18:16:56 node-1 haproxy[23249]: 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  1 18:16:56 node-1 haproxy[23249]: Server object-storage/node-3 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  1 18:16:56 node-1 haproxy[23249]: Server object-storage/node-5 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  1 18:16:56 node-1 haproxy[23249]: proxy object-storage has no server available!
<129>Oct  1 18:16:56 node-1 haproxy[23249]: 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  1 18:16:56 node-1 haproxy[23249]: Server aodh/node-3 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  1 18:16:57 node-1 haproxy[23249]: Server aodh/node-5 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  1 18:16:57 node-1 haproxy[23249]: proxy aodh has no server available!
<27>Oct  1 18:16:58 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:58 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:58 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:58 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:58 node-1 multipathd: uevent trigger error
<27>Oct  1 18:16:58 node-1 multipathd: uevent trigger error
<129>Oct  1 18:17:00 node-1 haproxy[24603]: 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  1 18:17:00 node-1 haproxy[24603]: Server keystone-1/node-3 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  1 18:17:00 node-1 haproxy[24603]: Server keystone-1/node-5 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  1 18:17:00 node-1 haproxy[24603]: proxy keystone-1 has no server available!
<129>Oct  1 18:17:01 node-1 haproxy[24609]: 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  1 18:17:01 node-1 haproxy[24609]: Server keystone-2/node-3 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  1 18:17:01 node-1 haproxy[24609]: Server keystone-2/node-5 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  1 18:17:01 node-1 haproxy[24609]: proxy keystone-2 has no server available!
<129>Oct  1 18:17:01 node-1 haproxy[24609]: 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  1 18:17:01 node-1 haproxy[24609]: Server neutron/node-3 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  1 18:17:01 node-1 haproxy[24609]: Server neutron/node-5 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  1 18:17:01 node-1 haproxy[24609]: proxy neutron has no server available!
<129>Oct  1 18:17:01 node-1 haproxy[24609]: 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  1 18:17:01 node-1 haproxy[24609]: Backup Server mysqld/node-3 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  1 18:17:01 node-1 haproxy[24609]: Backup Server mysqld/node-5 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  1 18:17:01 node-1 haproxy[24609]: proxy mysqld has no server available!
<129>Oct  1 18:17:01 node-1 haproxy[24609]: 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  1 18:17:01 node-1 haproxy[24609]: Server object-storage/node-3 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  1 18:17:02 node-1 haproxy[24609]: Server object-storage/node-5 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  1 18:17:02 node-1 haproxy[24609]: proxy object-storage has no server available!
<129>Oct  1 18:17:02 node-1 haproxy[24609]: 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  1 18:17:02 node-1 haproxy[24609]: Server aodh/node-3 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  1 18:17:02 node-1 haproxy[24609]: Server aodh/node-5 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  1 18:17:02 node-1 haproxy[24609]: proxy aodh has no server available!
<129>Oct  1 18:17:02 node-1 haproxy[24609]: 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  1 18:17:02 node-1 haproxy[24609]: Server ceilometer/node-3 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  1 18:17:02 node-1 haproxy[24609]: Server ceilometer/node-5 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  1 18:17:02 node-1 haproxy[24609]: proxy ceilometer has no server available!
<27>Oct  1 18:17:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:04 node-1 multipathd: uevent trigger error
<129>Oct  1 18:17:06 node-1 haproxy[26126]: 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  1 18:17:06 node-1 haproxy[26126]: Server keystone-1/node-3 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  1 18:17:06 node-1 haproxy[26126]: Server keystone-1/node-5 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  1 18:17:06 node-1 haproxy[26126]: proxy keystone-1 has no server available!
<129>Oct  1 18:17:06 node-1 haproxy[26126]: 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  1 18:17:06 node-1 haproxy[26126]: Server keystone-2/node-3 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  1 18:17:06 node-1 haproxy[26126]: Server keystone-2/node-5 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  1 18:17:06 node-1 haproxy[26126]: proxy keystone-2 has no server available!
<129>Oct  1 18:17:06 node-1 haproxy[26126]: 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  1 18:17:06 node-1 haproxy[26126]: Server neutron/node-3 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  1 18:17:07 node-1 haproxy[26130]: Server neutron/node-5 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  1 18:17:07 node-1 haproxy[26130]: proxy neutron has no server available!
<129>Oct  1 18:17:07 node-1 haproxy[26130]: 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  1 18:17:07 node-1 haproxy[26130]: Backup Server mysqld/node-3 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  1 18:17:07 node-1 haproxy[26130]: Backup Server mysqld/node-5 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  1 18:17:07 node-1 haproxy[26130]: proxy mysqld has no server available!
<129>Oct  1 18:17:07 node-1 haproxy[26130]: 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  1 18:17:07 node-1 haproxy[26130]: Server object-storage/node-3 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  1 18:17:07 node-1 haproxy[26130]: Server object-storage/node-5 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  1 18:17:07 node-1 haproxy[26130]: proxy object-storage has no server available!
<129>Oct  1 18:17:07 node-1 haproxy[26130]: 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  1 18:17:07 node-1 haproxy[26130]: Server aodh/node-3 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  1 18:17:07 node-1 haproxy[26130]: Server aodh/node-5 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  1 18:17:07 node-1 haproxy[26130]: proxy aodh has no server available!
<129>Oct  1 18:17:07 node-1 haproxy[26130]: 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  1 18:17:08 node-1 haproxy[26130]: Server ceilometer/node-3 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  1 18:17:08 node-1 haproxy[26130]: Server ceilometer/node-5 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  1 18:17:08 node-1 haproxy[26130]: proxy ceilometer has no server available!
<27>Oct  1 18:17:09 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:09 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:09 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:09 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:09 node-1 multipathd: uevent trigger error
<129>Oct  1 18:17:11 node-1 haproxy[27490]: 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  1 18:17:11 node-1 haproxy[27490]: 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  1 18:17:11 node-1 haproxy[27490]: Server keystone-1/node-3 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  1 18:17:11 node-1 haproxy[27490]: Server keystone-1/node-5 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  1 18:17:11 node-1 haproxy[27490]: proxy keystone-1 has no server available!
<129>Oct  1 18:17:11 node-1 haproxy[27490]: 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  1 18:17:12 node-1 haproxy[27494]: Server keystone-2/node-3 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  1 18:17:12 node-1 haproxy[27494]: Server keystone-2/node-5 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  1 18:17:12 node-1 haproxy[27494]: proxy keystone-2 has no server available!
<129>Oct  1 18:17:12 node-1 haproxy[27494]: 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  1 18:17:12 node-1 haproxy[27494]: Server neutron/node-3 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  1 18:17:12 node-1 haproxy[27494]: Server neutron/node-5 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  1 18:17:12 node-1 haproxy[27494]: proxy neutron has no server available!
<129>Oct  1 18:17:12 node-1 haproxy[27494]: 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  1 18:17:12 node-1 haproxy[27494]: Backup Server mysqld/node-3 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  1 18:17:12 node-1 haproxy[27494]: Backup Server mysqld/node-5 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  1 18:17:12 node-1 haproxy[27494]: proxy mysqld has no server available!
<129>Oct  1 18:17:12 node-1 haproxy[27494]: 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  1 18:17:12 node-1 haproxy[27494]: Server object-storage/node-3 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  1 18:17:12 node-1 haproxy[27494]: Server object-storage/node-5 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  1 18:17:12 node-1 haproxy[27494]: proxy object-storage has no server available!
<129>Oct  1 18:17:12 node-1 haproxy[27494]: 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  1 18:17:13 node-1 haproxy[27494]: Server aodh/node-3 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  1 18:17:13 node-1 haproxy[27494]: Server aodh/node-5 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  1 18:17:13 node-1 haproxy[27494]: proxy aodh has no server available!
<129>Oct  1 18:17:13 node-1 haproxy[27494]: 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  1 18:17:13 node-1 haproxy[27494]: Server ceilometer/node-3 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  1 18:17:13 node-1 haproxy[27494]: Server ceilometer/node-5 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  1 18:17:13 node-1 haproxy[27494]: proxy ceilometer has no server available!
<27>Oct  1 18:17:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:14 node-1 multipathd: uevent trigger error
<129>Oct  1 18:17:17 node-1 haproxy[29025]: 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  1 18:17:17 node-1 haproxy[29025]: 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  1 18:17:17 node-1 haproxy[29025]: Server keystone-1/node-3 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  1 18:17:17 node-1 haproxy[29025]: Server keystone-1/node-5 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  1 18:17:17 node-1 haproxy[29025]: proxy keystone-1 has no server available!
<129>Oct  1 18:17:17 node-1 haproxy[29025]: 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  1 18:17:17 node-1 haproxy[29025]: Server keystone-2/node-3 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  1 18:17:17 node-1 haproxy[29025]: Server keystone-2/node-5 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  1 18:17:17 node-1 haproxy[29025]: proxy keystone-2 has no server available!
<129>Oct  1 18:17:17 node-1 haproxy[29025]: 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  1 18:17:17 node-1 haproxy[29025]: Server glance-api/node-3 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  1 18:17:17 node-1 haproxy[29025]: Server glance-api/node-5 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  1 18:17:17 node-1 haproxy[29025]: proxy glance-api has no server available!
<129>Oct  1 18:17:17 node-1 haproxy[29025]: 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  1 18:17:17 node-1 haproxy[29025]: Server glance-glare/node-3 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  1 18:17:17 node-1 haproxy[29025]: Server glance-glare/node-5 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  1 18:17:17 node-1 haproxy[29025]: proxy glance-glare has no server available!
<129>Oct  1 18:17:18 node-1 haproxy[29031]: 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  1 18:17:18 node-1 haproxy[29031]: Server neutron/node-3 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  1 18:17:18 node-1 haproxy[29031]: Server neutron/node-5 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  1 18:17:18 node-1 haproxy[29031]: proxy neutron has no server available!
<129>Oct  1 18:17:18 node-1 haproxy[29031]: 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  1 18:17:18 node-1 haproxy[29031]: Server glance-registry/node-3 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  1 18:17:18 node-1 haproxy[29031]: Server glance-registry/node-5 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  1 18:17:18 node-1 haproxy[29031]: proxy glance-registry has no server available!
<129>Oct  1 18:17:18 node-1 haproxy[29031]: 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  1 18:17:18 node-1 haproxy[29031]: Backup Server mysqld/node-3 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  1 18:17:18 node-1 haproxy[29031]: Backup Server mysqld/node-5 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  1 18:17:18 node-1 haproxy[29031]: proxy mysqld has no server available!
<129>Oct  1 18:17:18 node-1 haproxy[29031]: 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  1 18:17:18 node-1 haproxy[29031]: Server object-storage/node-3 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  1 18:17:18 node-1 haproxy[29031]: Server object-storage/node-5 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  1 18:17:18 node-1 haproxy[29031]: proxy object-storage has no server available!
<129>Oct  1 18:17:18 node-1 haproxy[29031]: 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  1 18:17:18 node-1 haproxy[29031]: Server aodh/node-3 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  1 18:17:18 node-1 haproxy[29031]: Server aodh/node-5 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  1 18:17:18 node-1 haproxy[29031]: proxy aodh has no server available!
<129>Oct  1 18:17:18 node-1 haproxy[29031]: 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  1 18:17:18 node-1 haproxy[29031]: Server ceilometer/node-3 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  1 18:17:19 node-1 haproxy[29031]: Server ceilometer/node-5 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  1 18:17:19 node-1 haproxy[29031]: proxy ceilometer has no server available!
<27>Oct  1 18:17:20 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:20 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:20 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:20 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:20 node-1 multipathd: uevent trigger error
<129>Oct  1 18:17:22 node-1 haproxy[30426]: 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  1 18:17:23 node-1 haproxy[30430]: 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  1 18:17:23 node-1 haproxy[30430]: Server keystone-1/node-3 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  1 18:17:23 node-1 haproxy[30430]: Server keystone-1/node-5 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  1 18:17:23 node-1 haproxy[30430]: proxy keystone-1 has no server available!
<129>Oct  1 18:17:23 node-1 haproxy[30430]: 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  1 18:17:23 node-1 haproxy[30430]: Server keystone-2/node-3 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  1 18:17:23 node-1 haproxy[30430]: Server keystone-2/node-5 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  1 18:17:23 node-1 haproxy[30430]: proxy keystone-2 has no server available!
<129>Oct  1 18:17:23 node-1 haproxy[30430]: 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  1 18:17:23 node-1 haproxy[30430]: Server nova-api/node-3 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  1 18:17:23 node-1 haproxy[30430]: Server nova-api/node-5 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  1 18:17:23 node-1 haproxy[30430]: proxy nova-api has no server available!
<129>Oct  1 18:17:23 node-1 haproxy[30430]: 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  1 18:17:23 node-1 haproxy[30430]: Server nova-metadata-api/node-3 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  1 18:17:23 node-1 haproxy[30430]: Server nova-metadata-api/node-5 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  1 18:17:23 node-1 haproxy[30430]: proxy nova-metadata-api has no server available!
<129>Oct  1 18:17:23 node-1 haproxy[30430]: 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  1 18:17:23 node-1 haproxy[30430]: Server glance-api/node-3 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  1 18:17:23 node-1 haproxy[30430]: Server glance-api/node-5 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  1 18:17:23 node-1 haproxy[30430]: proxy glance-api has no server available!
<129>Oct  1 18:17:23 node-1 haproxy[30430]: 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  1 18:17:23 node-1 haproxy[30430]: Server glance-glare/node-3 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  1 18:17:23 node-1 haproxy[30430]: Server glance-glare/node-5 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  1 18:17:23 node-1 haproxy[30430]: proxy glance-glare has no server available!
<129>Oct  1 18:17:23 node-1 haproxy[30430]: 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  1 18:17:23 node-1 haproxy[30430]: Server neutron/node-3 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  1 18:17:23 node-1 haproxy[30430]: Server neutron/node-5 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  1 18:17:23 node-1 haproxy[30430]: proxy neutron has no server available!
<129>Oct  1 18:17:24 node-1 haproxy[30430]: 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  1 18:17:24 node-1 haproxy[30430]: Server glance-registry/node-3 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  1 18:17:24 node-1 haproxy[30430]: Server glance-registry/node-5 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  1 18:17:24 node-1 haproxy[30430]: proxy glance-registry has no server available!
<129>Oct  1 18:17:24 node-1 haproxy[30430]: 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  1 18:17:24 node-1 haproxy[30430]: Backup Server mysqld/node-3 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  1 18:17:24 node-1 haproxy[30430]: Backup Server mysqld/node-5 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  1 18:17:24 node-1 haproxy[30430]: proxy mysqld has no server available!
<129>Oct  1 18:17:24 node-1 haproxy[30430]: 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  1 18:17:24 node-1 haproxy[30430]: Server object-storage/node-3 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  1 18:17:24 node-1 haproxy[30430]: Server object-storage/node-5 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  1 18:17:24 node-1 haproxy[30430]: proxy object-storage has no server available!
<129>Oct  1 18:17:24 node-1 haproxy[30430]: 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  1 18:17:24 node-1 haproxy[30430]: Server aodh/node-3 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  1 18:17:24 node-1 haproxy[30430]: Server aodh/node-5 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  1 18:17:24 node-1 haproxy[30430]: proxy aodh has no server available!
<129>Oct  1 18:17:24 node-1 haproxy[30430]: 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  1 18:17:24 node-1 haproxy[30430]: Server ceilometer/node-3 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  1 18:17:24 node-1 haproxy[30430]: Server ceilometer/node-5 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  1 18:17:24 node-1 haproxy[30430]: proxy ceilometer has no server available!
<129>Oct  1 18:17:24 node-1 haproxy[30430]: 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  1 18:17:24 node-1 haproxy[30430]: Server nova-novncproxy/node-3 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  1 18:17:24 node-1 haproxy[30430]: Server nova-novncproxy/node-5 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  1 18:17:24 node-1 haproxy[30430]: proxy nova-novncproxy has no server available!
<27>Oct  1 18:17:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:26 node-1 multipathd: uevent trigger error
<129>Oct  1 18:17:28 node-1 haproxy[31763]: 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  1 18:17:28 node-1 haproxy[31763]: 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  1 18:17:28 node-1 haproxy[31763]: Server keystone-1/node-3 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  1 18:17:28 node-1 haproxy[31763]: Server keystone-1/node-5 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  1 18:17:28 node-1 haproxy[31763]: proxy keystone-1 has no server available!
<129>Oct  1 18:17:28 node-1 haproxy[31763]: 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  1 18:17:28 node-1 haproxy[31763]: Server keystone-2/node-3 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  1 18:17:28 node-1 haproxy[31763]: Server keystone-2/node-5 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  1 18:17:28 node-1 haproxy[31763]: proxy keystone-2 has no server available!
<129>Oct  1 18:17:28 node-1 haproxy[31763]: 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  1 18:17:28 node-1 haproxy[31763]: Server nova-api/node-3 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  1 18:17:28 node-1 haproxy[31763]: Server nova-api/node-5 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  1 18:17:28 node-1 haproxy[31763]: proxy nova-api has no server available!
<129>Oct  1 18:17:28 node-1 haproxy[31763]: 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  1 18:17:28 node-1 haproxy[31763]: Server nova-metadata-api/node-3 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  1 18:17:28 node-1 haproxy[31763]: Server nova-metadata-api/node-5 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  1 18:17:28 node-1 haproxy[31763]: proxy nova-metadata-api has no server available!
<129>Oct  1 18:17:29 node-1 haproxy[31769]: 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  1 18:17:29 node-1 haproxy[31769]: Backup Server cinder-api/node-3 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  1 18:17:29 node-1 haproxy[31769]: Backup Server cinder-api/node-5 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  1 18:17:29 node-1 haproxy[31769]: proxy cinder-api has no server available!
<129>Oct  1 18:17:29 node-1 haproxy[31769]: 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  1 18:17:29 node-1 haproxy[31769]: Server glance-api/node-3 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  1 18:17:29 node-1 haproxy[31769]: Server glance-api/node-5 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  1 18:17:29 node-1 haproxy[31769]: proxy glance-api has no server available!
<129>Oct  1 18:17:29 node-1 haproxy[31769]: 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  1 18:17:29 node-1 haproxy[31769]: Server glance-glare/node-3 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  1 18:17:29 node-1 haproxy[31769]: Server glance-glare/node-5 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  1 18:17:29 node-1 haproxy[31769]: proxy glance-glare has no server available!
<129>Oct  1 18:17:29 node-1 haproxy[31769]: 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  1 18:17:29 node-1 haproxy[31769]: Server neutron/node-3 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  1 18:17:29 node-1 haproxy[31769]: Server neutron/node-5 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  1 18:17:29 node-1 haproxy[31769]: proxy neutron has no server available!
<129>Oct  1 18:17:29 node-1 haproxy[31769]: 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  1 18:17:29 node-1 haproxy[31769]: Server glance-registry/node-3 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  1 18:17:29 node-1 haproxy[31769]: Server glance-registry/node-5 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  1 18:17:29 node-1 haproxy[31769]: proxy glance-registry has no server available!
<129>Oct  1 18:17:29 node-1 haproxy[31769]: 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  1 18:17:29 node-1 haproxy[31769]: Backup Server mysqld/node-3 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  1 18:17:29 node-1 haproxy[31769]: Backup Server mysqld/node-5 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  1 18:17:29 node-1 haproxy[31769]: proxy mysqld has no server available!
<129>Oct  1 18:17:29 node-1 haproxy[31769]: 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  1 18:17:29 node-1 haproxy[31769]: Server object-storage/node-3 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  1 18:17:29 node-1 haproxy[31769]: Server object-storage/node-5 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  1 18:17:29 node-1 haproxy[31769]: proxy object-storage has no server available!
<129>Oct  1 18:17:29 node-1 haproxy[31769]: 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  1 18:17:29 node-1 haproxy[31769]: Server aodh/node-3 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  1 18:17:30 node-1 haproxy[31769]: Server aodh/node-5 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  1 18:17:30 node-1 haproxy[31769]: proxy aodh has no server available!
<129>Oct  1 18:17:30 node-1 haproxy[31769]: 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  1 18:17:30 node-1 haproxy[31769]: Server ceilometer/node-3 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  1 18:17:30 node-1 haproxy[31769]: Server ceilometer/node-5 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  1 18:17:30 node-1 haproxy[31769]: proxy ceilometer has no server available!
<129>Oct  1 18:17:30 node-1 haproxy[31769]: 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  1 18:17:30 node-1 haproxy[31769]: Server nova-novncproxy/node-3 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  1 18:17:30 node-1 haproxy[31769]: Server nova-novncproxy/node-5 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  1 18:17:30 node-1 haproxy[31769]: proxy nova-novncproxy has no server available!
<27>Oct  1 18:17:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:31 node-1 multipathd: uevent trigger error
<129>Oct  1 18:17:34 node-1 haproxy[730]: 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  1 18:17:34 node-1 haproxy[730]: 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  1 18:17:34 node-1 haproxy[730]: Server keystone-1/node-3 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  1 18:17:34 node-1 haproxy[730]: Server keystone-1/node-5 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  1 18:17:34 node-1 haproxy[730]: proxy keystone-1 has no server available!
<129>Oct  1 18:17:34 node-1 haproxy[730]: 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  1 18:17:34 node-1 haproxy[730]: Server keystone-2/node-3 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  1 18:17:34 node-1 haproxy[730]: Server keystone-2/node-5 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  1 18:17:34 node-1 haproxy[730]: proxy keystone-2 has no server available!
<129>Oct  1 18:17:34 node-1 haproxy[730]: 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  1 18:17:34 node-1 haproxy[730]: Server nova-api/node-3 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  1 18:17:34 node-1 haproxy[730]: Server nova-api/node-5 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  1 18:17:34 node-1 haproxy[730]: proxy nova-api has no server available!
<129>Oct  1 18:17:34 node-1 haproxy[730]: 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  1 18:17:34 node-1 haproxy[730]: Server nova-metadata-api/node-3 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  1 18:17:34 node-1 haproxy[730]: Server nova-metadata-api/node-5 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  1 18:17:34 node-1 haproxy[730]: proxy nova-metadata-api has no server available!
<129>Oct  1 18:17:34 node-1 haproxy[730]: 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  1 18:17:34 node-1 haproxy[730]: Backup Server cinder-api/node-3 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  1 18:17:34 node-1 haproxy[730]: Backup Server cinder-api/node-5 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  1 18:17:34 node-1 haproxy[730]: proxy cinder-api has no server available!
<129>Oct  1 18:17:34 node-1 haproxy[730]: 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  1 18:17:34 node-1 haproxy[730]: Server glance-api/node-3 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  1 18:17:34 node-1 haproxy[730]: Server glance-api/node-5 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  1 18:17:34 node-1 haproxy[730]: proxy glance-api has no server available!
<129>Oct  1 18:17:35 node-1 haproxy[734]: 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  1 18:17:35 node-1 haproxy[734]: Server glance-glare/node-3 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  1 18:17:35 node-1 haproxy[734]: Server glance-glare/node-5 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  1 18:17:35 node-1 haproxy[734]: proxy glance-glare has no server available!
<129>Oct  1 18:17:35 node-1 haproxy[734]: 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  1 18:17:35 node-1 haproxy[734]: Server neutron/node-3 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  1 18:17:35 node-1 haproxy[734]: Server neutron/node-5 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  1 18:17:35 node-1 haproxy[734]: proxy neutron has no server available!
<129>Oct  1 18:17:35 node-1 haproxy[734]: 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  1 18:17:35 node-1 haproxy[734]: Server glance-registry/node-3 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  1 18:17:35 node-1 haproxy[734]: Server glance-registry/node-5 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  1 18:17:35 node-1 haproxy[734]: proxy glance-registry has no server available!
<129>Oct  1 18:17:35 node-1 haproxy[734]: 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  1 18:17:35 node-1 haproxy[734]: Backup Server mysqld/node-3 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  1 18:17:35 node-1 haproxy[734]: Backup Server mysqld/node-5 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  1 18:17:35 node-1 haproxy[734]: proxy mysqld has no server available!
<129>Oct  1 18:17:35 node-1 haproxy[734]: 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  1 18:17:35 node-1 haproxy[734]: Server object-storage/node-3 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  1 18:17:35 node-1 haproxy[734]: Server object-storage/node-5 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  1 18:17:35 node-1 haproxy[734]: proxy object-storage has no server available!
<129>Oct  1 18:17:35 node-1 haproxy[734]: 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  1 18:17:35 node-1 haproxy[734]: Server aodh/node-3 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  1 18:17:35 node-1 haproxy[734]: Server aodh/node-5 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  1 18:17:35 node-1 haproxy[734]: proxy aodh has no server available!
<129>Oct  1 18:17:35 node-1 haproxy[734]: 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  1 18:17:35 node-1 haproxy[734]: Server ceilometer/node-3 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  1 18:17:35 node-1 haproxy[734]: Server ceilometer/node-5 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  1 18:17:35 node-1 haproxy[734]: proxy ceilometer has no server available!
<129>Oct  1 18:17:35 node-1 haproxy[734]: 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  1 18:17:35 node-1 haproxy[734]: Server heat-api/node-3 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  1 18:17:35 node-1 haproxy[734]: Server heat-api/node-5 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  1 18:17:35 node-1 haproxy[734]: proxy heat-api has no server available!
<129>Oct  1 18:17:35 node-1 haproxy[734]: 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  1 18:17:35 node-1 haproxy[734]: Server heat-api-cfn/node-3 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  1 18:17:35 node-1 haproxy[734]: Server heat-api-cfn/node-5 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  1 18:17:35 node-1 haproxy[734]: proxy heat-api-cfn has no server available!
<129>Oct  1 18:17:36 node-1 haproxy[734]: 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  1 18:17:36 node-1 haproxy[734]: Server heat-api-cloudwatch/node-3 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  1 18:17:36 node-1 haproxy[734]: Server heat-api-cloudwatch/node-5 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  1 18:17:36 node-1 haproxy[734]: proxy heat-api-cloudwatch has no server available!
<129>Oct  1 18:17:36 node-1 haproxy[734]: 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  1 18:17:36 node-1 haproxy[734]: Server nova-novncproxy/node-3 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  1 18:17:36 node-1 haproxy[734]: Server nova-novncproxy/node-5 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  1 18:17:36 node-1 haproxy[734]: proxy nova-novncproxy has no server available!
<27>Oct  1 18:17:38 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:38 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:38 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:38 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:38 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:17:48 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct  1 18:18:13 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  1 18:18:15 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct  1 18:18:43 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  1 18:18:45 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  1 18:19:11 node-1 multipathd: uevent trigger error
<27>Oct  1 18:19:11 node-1 multipathd: uevent trigger error
<27>Oct  1 18:19:11 node-1 multipathd: uevent trigger error
<27>Oct  1 18:19:11 node-1 multipathd: uevent trigger error
<27>Oct  1 18:19:11 node-1 multipathd: uevent trigger error
<27>Oct  1 18:20:59 node-1 multipathd: uevent trigger error
<27>Oct  1 18:20:59 node-1 multipathd: uevent trigger error
<27>Oct  1 18:20:59 node-1 multipathd: uevent trigger error
<27>Oct  1 18:20:59 node-1 multipathd: uevent trigger error
<27>Oct  1 18:20:59 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:05 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:05 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:05 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:05 node-1 multipathd: uevent trigger error
<43>Oct  1 18:21:23 node-1 apache2_error [Sat Oct 01 18:21:16.599926 2016] [mpm_event:notice] [pid 6712:tid 140201822640000] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  1 18:21:23 node-1 apache2_error [Sat Oct 01 18:21:16.600008 2016] [core:notice] [pid 6712:tid 140201822640000] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  1 18:21:23 node-1 apache2_error [Sat Oct 01 18:21:19.469696 2016] [mpm_event:notice] [pid 6712:tid 140201822640000] AH00491: caught SIGTERM, shutting down
<43>Oct  1 18:21:23 node-1 apache2_error [Sat Oct 01 18:21:20.557504 2016] [mpm_worker:notice] [pid 7094:tid 140319070902144] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  1 18:21:23 node-1 apache2_error [Sat Oct 01 18:21:20.557573 2016] [core:notice] [pid 7094:tid 140319070902144] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  1 18:21:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:28 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:28 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:28 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:28 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:28 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:21:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:22:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  1 18:22:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:22:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:22:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:22:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:22:13 node-1 multipathd: uevent trigger error
<43>Oct  1 18:22:13 node-1 apache2_error [Sat Oct 01 18:22:09.762934 2016] [mpm_worker:notice] [pid 7094:tid 140319070902144] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  1 18:22:13 node-1 apache2_error [Sat Oct 01 18:22:09.766819 2016] [mpm_worker:warn] [pid 7094:tid 140319070902144] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  1 18:22:13 node-1 apache2_error [Sat Oct 01 18:22:09.767646 2016] [mpm_worker:notice] [pid 7094:tid 140319070902144] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct  1 18:22:13 node-1 apache2_error [Sat Oct 01 18:22:09.767652 2016] [core:notice] [pid 7094:tid 140319070902144] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  1 18:22:17 node-1 multipathd: uevent trigger error
<27>Oct  1 18:22:17 node-1 multipathd: uevent trigger error
<27>Oct  1 18:22:17 node-1 multipathd: uevent trigger error
<27>Oct  1 18:22:17 node-1 multipathd: uevent trigger error
<27>Oct  1 18:22:17 node-1 multipathd: uevent trigger error
<27>Oct  1 18:22:17 node-1 multipathd: uevent trigger error
<43>Oct  1 18:23:23 node-1 apache2_error [Sat Oct 01 18:23:20.823027 2016] [mpm_worker:notice] [pid 7094:tid 140319070902144] AH00295: caught SIGTERM, shutting down
<43>Oct  1 18:23:23 node-1 apache2_error [Sat Oct 01 18:23:21.584892 2016] [mpm_worker:notice] [pid 28130:tid 140120172251008] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  1 18:23:23 node-1 apache2_error [Sat Oct 01 18:23:21.584928 2016] [core:notice] [pid 28130:tid 140120172251008] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct  1 18:24:13 node-1 apache2_error [Sat Oct 01 18:24:05.869626 2016] [mpm_worker:notice] [pid 28130:tid 140120172251008] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  1 18:24:13 node-1 apache2_error [Sat Oct 01 18:24:05.878902 2016] [mpm_worker:warn] [pid 28130:tid 140120172251008] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  1 18:24:13 node-1 apache2_error [Sat Oct 01 18:24:05.885846 2016] [mpm_worker:notice] [pid 28130:tid 140120172251008] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  1 18:24:13 node-1 apache2_error [Sat Oct 01 18:24:05.885872 2016] [core:notice] [pid 28130:tid 140120172251008] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  1 18:25:03 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  1 18:25:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:46 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:46 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:46 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:46 node-1 multipathd: uevent trigger error
<27>Oct  1 18:25:46 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:05 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:05 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:05 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:05 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:05 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:09 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:10 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:10 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:10 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:10 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:26:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:27:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:27:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:27:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:27:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:28:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  1 18:28:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:28:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:28:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:28:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:28:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:28:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:19 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:19 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:19 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:19 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:19 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:25 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:25 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:25 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:25 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:25 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:29:51 node-1 multipathd: uevent trigger error
<27>Oct  1 18:31:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  1 18:32:10 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:11 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:11 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:11 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:11 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:11 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:26 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:32:31 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:12 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:12 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:12 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:12 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:12 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:17 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:17 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:17 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:17 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:18 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:42 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:42 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:42 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:42 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:42 node-1 multipathd: uevent trigger error
<27>Oct  1 18:33:42 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  1 18:34:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:34 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct  1 18:34:34 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct  1 18:34:34 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct  1 18:34:35 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Oct  1 18:34:35 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Oct  1 18:34:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:49 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:49 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:49 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:49 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:49 node-1 multipathd: uevent trigger error
<27>Oct  1 18:34:49 node-1 multipathd: uevent trigger error
<27>Oct  1 18:35:03 node-1 multipathd: uevent trigger error
<27>Oct  1 18:35:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:35:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:35:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:35:20 node-1 multipathd: uevent trigger error
<27>Oct  1 18:35:20 node-1 multipathd: uevent trigger error
<27>Oct  1 18:35:20 node-1 multipathd: uevent trigger error
<27>Oct  1 18:35:20 node-1 multipathd: uevent trigger error
<27>Oct  1 18:35:20 node-1 multipathd: uevent trigger error
<27>Oct  1 18:37:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  1 18:37:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:37:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:37:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:37:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:37:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:37:41 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:13 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:18 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:18 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:18 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:18 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:18 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:37 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:37 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:37 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:37 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:49 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:49 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:49 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:49 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:54 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:54 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:54 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:54 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:58 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:58 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:58 node-1 multipathd: uevent trigger error
<27>Oct  1 18:38:58 node-1 multipathd: uevent trigger error
<27>Oct  1 18:39:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:39:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:39:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:39:04 node-1 multipathd: uevent trigger error
<27>Oct  1 18:39:43 node-1 multipathd: uevent trigger error
<27>Oct  1 18:39:43 node-1 multipathd: uevent trigger error
<27>Oct  1 18:39:43 node-1 multipathd: uevent trigger error
<27>Oct  1 18:39:43 node-1 multipathd: uevent trigger error
<27>Oct  1 18:40:12 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  1 18:40:54 node-1 multipathd: uevent trigger error
<27>Oct  1 18:40:54 node-1 multipathd: uevent trigger error
<27>Oct  1 18:40:54 node-1 multipathd: uevent trigger error
<27>Oct  1 18:40:54 node-1 multipathd: uevent trigger error
<27>Oct  1 18:40:54 node-1 multipathd: uevent trigger error
<27>Oct  1 18:41:08 node-1 multipathd: uevent trigger error
<27>Oct  1 18:41:08 node-1 multipathd: uevent trigger error
<27>Oct  1 18:41:08 node-1 multipathd: uevent trigger error
<27>Oct  1 18:41:08 node-1 multipathd: uevent trigger error
<27>Oct  1 18:41:08 node-1 multipathd: uevent trigger error
<11>Oct  1 18:41:21 node-1 liberasurecode[17057]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:21 node-1 liberasurecode[17057]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:21 node-1 liberasurecode[17057]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:21 node-1 liberasurecode[17057]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:21 node-1 liberasurecode[17081]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:21 node-1 liberasurecode[17081]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:21 node-1 liberasurecode[17081]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:21 node-1 liberasurecode[17081]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:23 node-1 liberasurecode[17736]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:23 node-1 liberasurecode[17736]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:23 node-1 liberasurecode[17736]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:23 node-1 liberasurecode[17736]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:27 node-1 liberasurecode[18805]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:27 node-1 liberasurecode[18805]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:27 node-1 liberasurecode[18805]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:27 node-1 liberasurecode[18805]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[18927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[18927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[18927]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[18927]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19014]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19014]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19014]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19014]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19308]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19308]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19308]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19308]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19321]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19321]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19321]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19321]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19343]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19343]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19343]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19343]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19364]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19364]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19364]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:28 node-1 liberasurecode[19364]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:37 node-1 liberasurecode[20755]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:37 node-1 liberasurecode[20755]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:37 node-1 liberasurecode[20755]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:41:37 node-1 liberasurecode[20755]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  1 18:41:46 node-1 multipathd: uevent trigger error
<27>Oct  1 18:41:46 node-1 multipathd: uevent trigger error
<27>Oct  1 18:41:46 node-1 multipathd: uevent trigger error
<27>Oct  1 18:41:46 node-1 multipathd: uevent trigger error
<27>Oct  1 18:41:46 node-1 multipathd: uevent trigger error
<43>Oct  1 18:42:35 node-1 apache2_error [Sat Oct 01 18:42:33.549095 2016] [mpm_worker:notice] [pid 28130:tid 140120172251008] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  1 18:42:35 node-1 apache2_error [Sat Oct 01 18:42:33.936853 2016] [mpm_worker:warn] [pid 28130:tid 140120172251008] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  1 18:42:35 node-1 apache2_error [Sat Oct 01 18:42:33.939988 2016] [mpm_worker:notice] [pid 28130:tid 140120172251008] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  1 18:42:35 node-1 apache2_error [Sat Oct 01 18:42:33.939999 2016] [core:notice] [pid 28130:tid 140120172251008] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  1 18:43:13 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct  1 18:43:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:14 node-1 multipathd: uevent trigger error
<43>Oct  1 18:43:15 node-1 apache2_error [Sat Oct 01 18:43:10.859643 2016] [mpm_worker:notice] [pid 28130:tid 140120172251008] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct  1 18:43:15 node-1 apache2_error [Sat Oct 01 18:43:11.053079 2016] [mpm_worker:warn] [pid 28130:tid 140120172251008] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct  1 18:43:15 node-1 apache2_error [Sat Oct 01 18:43:11.065372 2016] [mpm_worker:notice] [pid 28130:tid 140120172251008] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct  1 18:43:15 node-1 apache2_error [Sat Oct 01 18:43:11.065392 2016] [core:notice] [pid 28130:tid 140120172251008] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct  1 18:43:21 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:21 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:21 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:21 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:21 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:21 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:27 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:35 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:35 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:35 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:36 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:53 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:53 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:53 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:53 node-1 multipathd: uevent trigger error
<27>Oct  1 18:43:53 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:14 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:20 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct  1 18:44:29 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:29 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:29 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:29 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:29 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:33 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:33 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:33 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:33 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:39 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:39 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:39 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:39 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:52 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:52 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:52 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:52 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:52 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:55 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct  1 18:44:57 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:57 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:57 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:57 node-1 multipathd: uevent trigger error
<27>Oct  1 18:44:57 node-1 multipathd: uevent trigger error
<11>Oct  1 18:45:01 node-1 liberasurecode[2835]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:45:01 node-1 liberasurecode[2835]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:45:01 node-1 liberasurecode[2835]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct  1 18:45:01 node-1 liberasurecode[2835]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct  1 18:45:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:24 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:37 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:37 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:37 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:37 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:38 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:45 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:45 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:45 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:45 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:45 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:45:50 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:02 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:02 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:02 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:02 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:02 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:07 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:07 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:07 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:07 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:07 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:12 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:12 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:12 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:12 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:12 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:16 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:16 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:16 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:16 node-1 multipathd: uevent trigger error
<27>Oct  1 18:46:16 node-1 multipathd: uevent trigger error
