Nov  6 23:25:58 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8390" x-info="http://www.rsyslog.com"] start
Nov  6 23:25:58 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov  6 23:25:58 node-1 rsyslogd: rsyslogd's groupid changed to 104
Nov  6 23:25:58 node-1 rsyslogd: rsyslogd's userid changed to 101
Nov  6 23:25:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov  6 23:25:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov  6 23:25:58 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov  6 23:25:58 node-1 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Nov  6 23:25:58 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=1fc6a47e-fcf7-4368-8e52-4d2cf4b2be67 nomdmonddf nomdmonisw
Nov  6 23:25:58 node-1 kernel: [    0.000000] KERNEL supported cpus:
Nov  6 23:25:58 node-1 kernel: [    0.000000]   Intel GenuineIntel
Nov  6 23:25:58 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Nov  6 23:25:58 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Nov  6 23:25:58 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov  6 23:25:58 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov  6 23:25:58 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov  6 23:25:58 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Nov  6 23:25:58 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
Nov  6 23:25:58 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov  6 23:25:58 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov  6 23:25:58 node-1 kernel: [    0.000000] No AGP bridge found
Nov  6 23:25:58 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov  6 23:25:58 node-1 kernel: [    0.000000] MTRR default type: write-back
Nov  6 23:25:58 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov  6 23:25:58 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Nov  6 23:25:58 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov  6 23:25:58 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov  6 23:25:58 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Nov  6 23:25:58 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov  6 23:25:58 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov  6 23:25:58 node-1 kernel: [    0.000000]   2 disabled
Nov  6 23:25:58 node-1 kernel: [    0.000000]   3 disabled
Nov  6 23:25:58 node-1 kernel: [    0.000000]   4 disabled
Nov  6 23:25:58 node-1 kernel: [    0.000000]   5 disabled
Nov  6 23:25:58 node-1 kernel: [    0.000000]   6 disabled
Nov  6 23:25:58 node-1 kernel: [    0.000000]   7 disabled
Nov  6 23:25:58 node-1 kernel: [    0.000000]   8 disabled
Nov  6 23:25:58 node-1 kernel: [    0.000000]   9 disabled
Nov  6 23:25:58 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov  6 23:25:58 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov  6 23:25:58 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov  6 23:25:58 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov  6 23:25:58 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov  6 23:25:58 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Nov  6 23:25:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov  6 23:25:58 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov  6 23:25:58 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov  6 23:25:58 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov  6 23:25:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov  6 23:25:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov  6 23:25:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov  6 23:25:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Nov  6 23:25:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov  6 23:25:58 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov  6 23:25:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov  6 23:25:58 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov  6 23:25:58 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov  6 23:25:58 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov  6 23:25:58 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov  6 23:25:58 node-1 kernel: [    0.000000] Zone ranges:
Nov  6 23:25:58 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] Movable zone start for each node
Nov  6 23:25:58 node-1 kernel: [    0.000000] Early memory node ranges
Nov  6 23:25:58 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] On node 0 totalpages: 4125855
Nov  6 23:25:58 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov  6 23:25:58 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov  6 23:25:58 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov  6 23:25:58 node-1 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Nov  6 23:25:58 node-1 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Nov  6 23:25:58 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov  6 23:25:58 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov  6 23:25:58 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov  6 23:25:58 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov  6 23:25:58 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov  6 23:25:58 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov  6 23:25:58 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov  6 23:25:58 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov  6 23:25:58 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov  6 23:25:58 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov  6 23:25:58 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov  6 23:25:58 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov  6 23:25:58 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov  6 23:25:58 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov  6 23:25:58 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov  6 23:25:58 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov  6 23:25:58 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov  6 23:25:58 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 
Nov  6 23:25:58 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Nov  6 23:25:58 node-1 kernel: [    0.000000] Policy zone: Normal
Nov  6 23:25:58 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=1fc6a47e-fcf7-4368-8e52-4d2cf4b2be67 nomdmonddf nomdmonisw
Nov  6 23:25:58 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov  6 23:25:58 node-1 kernel: [    0.000000] Checking aperture...
Nov  6 23:25:58 node-1 kernel: [    0.000000] No AGP bridge found
Nov  6 23:25:58 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov  6 23:25:58 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov  6 23:25:58 node-1 kernel: [    0.000000] Memory: 32653460K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627176K reserved)
Nov  6 23:25:58 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov  6 23:25:58 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Nov  6 23:25:58 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov  6 23:25:58 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov  6 23:25:58 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov  6 23:25:58 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov  6 23:25:58 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov  6 23:25:58 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Nov  6 23:25:58 node-1 kernel: [    0.000000] console [tty0] enabled
Nov  6 23:25:58 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov  6 23:25:58 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov  6 23:25:58 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov  6 23:25:58 node-1 kernel: [    0.000000] hpet clockevent registered
Nov  6 23:25:58 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov  6 23:25:58 node-1 kernel: [    0.004000] tsc: Detected 3492.050 MHz processor
Nov  6 23:25:58 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.10 BogoMIPS (lpj=13968200)
Nov  6 23:25:58 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov  6 23:25:58 node-1 kernel: [    0.000042] Security Framework initialized
Nov  6 23:25:58 node-1 kernel: [    0.000060] AppArmor: AppArmor initialized
Nov  6 23:25:58 node-1 kernel: [    0.000061] Yama: becoming mindful.
Nov  6 23:25:58 node-1 kernel: [    0.001467] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.006303] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.008230] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.008259] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.008550] Initializing cgroup subsys memory
Nov  6 23:25:58 node-1 kernel: [    0.008559] Initializing cgroup subsys devices
Nov  6 23:25:58 node-1 kernel: [    0.008561] Initializing cgroup subsys freezer
Nov  6 23:25:58 node-1 kernel: [    0.008562] Initializing cgroup subsys blkio
Nov  6 23:25:58 node-1 kernel: [    0.008564] Initializing cgroup subsys perf_event
Nov  6 23:25:58 node-1 kernel: [    0.008566] Initializing cgroup subsys hugetlb
Nov  6 23:25:58 node-1 kernel: [    0.008586] CPU: Physical Processor ID: 0
Nov  6 23:25:58 node-1 kernel: [    0.008587] CPU: Processor Core ID: 0
Nov  6 23:25:58 node-1 kernel: [    0.008591] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov  6 23:25:58 node-1 kernel: [    0.008591] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov  6 23:25:58 node-1 kernel: [    0.009284] mce: CPU supports 22 MCE banks
Nov  6 23:25:58 node-1 kernel: [    0.009312] CPU0: Thermal monitoring enabled (TM1)
Nov  6 23:25:58 node-1 kernel: [    0.009333] process: using mwait in idle threads
Nov  6 23:25:58 node-1 kernel: [    0.009336] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov  6 23:25:58 node-1 kernel: [    0.009336] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov  6 23:25:58 node-1 kernel: [    0.009336] tlb_flushall_shift: 6
Nov  6 23:25:58 node-1 kernel: [    0.009423] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov  6 23:25:58 node-1 kernel: [    0.010149] ACPI: Core revision 20131115
Nov  6 23:25:58 node-1 kernel: [    0.022951] ACPI: All ACPI Tables successfully acquired
Nov  6 23:25:58 node-1 kernel: [    0.023115] ftrace: allocating 28622 entries in 112 pages
Nov  6 23:25:58 node-1 kernel: [    0.031870] dmar: Host address width 46
Nov  6 23:25:58 node-1 kernel: [    0.031872] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov  6 23:25:58 node-1 kernel: [    0.031879] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  6 23:25:58 node-1 kernel: [    0.031880] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov  6 23:25:58 node-1 kernel: [    0.031884] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  6 23:25:58 node-1 kernel: [    0.031886] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov  6 23:25:58 node-1 kernel: [    0.031887] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov  6 23:25:58 node-1 kernel: [    0.031888] dmar: ATSR flags: 0x0
Nov  6 23:25:58 node-1 kernel: [    0.031889] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov  6 23:25:58 node-1 kernel: [    0.031891] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov  6 23:25:58 node-1 kernel: [    0.032006] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov  6 23:25:58 node-1 kernel: [    0.032007] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov  6 23:25:58 node-1 kernel: [    0.032008] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov  6 23:25:58 node-1 kernel: [    0.032009] HPET id 0 under DRHD base 0xc7ffc000
Nov  6 23:25:58 node-1 kernel: [    0.032010] Your BIOS is broken and requested that x2apic be disabled.
Nov  6 23:25:58 node-1 kernel: [    0.032010] This will slightly decrease performance.
Nov  6 23:25:58 node-1 kernel: [    0.032010] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov  6 23:25:58 node-1 kernel: [    0.032442] Enabled IRQ remapping in xapic mode
Nov  6 23:25:58 node-1 kernel: [    0.032443] x2apic not enabled, IRQ remapping is in xapic mode
Nov  6 23:25:58 node-1 kernel: [    0.032447] Switched APIC routing to physical flat.
Nov  6 23:25:58 node-1 kernel: [    0.033038] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov  6 23:25:58 node-1 kernel: [    0.072689] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov  6 23:25:58 node-1 kernel: [    0.072695] TSC deadline timer enabled
Nov  6 23:25:58 node-1 kernel: [    0.072703] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov  6 23:25:58 node-1 kernel: [    0.072709] ... version:                3
Nov  6 23:25:58 node-1 kernel: [    0.072710] ... bit width:              48
Nov  6 23:25:58 node-1 kernel: [    0.072710] ... generic registers:      4
Nov  6 23:25:58 node-1 kernel: [    0.072711] ... value mask:             0000ffffffffffff
Nov  6 23:25:58 node-1 kernel: [    0.072712] ... max period:             0000ffffffffffff
Nov  6 23:25:58 node-1 kernel: [    0.072713] ... fixed-purpose events:   3
Nov  6 23:25:58 node-1 kernel: [    0.072714] ... event mask:             000000070000000f
Nov  6 23:25:58 node-1 kernel: [    0.074145] x86: Booting SMP configuration:
Nov  6 23:25:58 node-1 kernel: [    0.088349] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov  6 23:25:58 node-1 kernel: [    0.074147] .... node  #0, CPUs:        #1  #2  #3
Nov  6 23:25:58 node-1 kernel: [    0.116262] .... node  #1, CPUs:    #4  #5  #6  #7
Nov  6 23:25:58 node-1 kernel: [    0.270111] .... node  #0, CPUs:    #8  #9 #10 #11
Nov  6 23:25:58 node-1 kernel: [    0.325718] .... node  #1, CPUs:   #12 #13 #14 #15
Nov  6 23:25:58 node-1 kernel: [    0.381973] x86: Booted up 2 nodes, 16 CPUs
Nov  6 23:25:58 node-1 kernel: [    0.381977] smpboot: Total of 16 processors activated (111758.12 BogoMIPS)
Nov  6 23:25:58 node-1 kernel: [    0.403997] devtmpfs: initialized
Nov  6 23:25:58 node-1 kernel: [    0.406480] EVM: security.selinux
Nov  6 23:25:58 node-1 kernel: [    0.406481] EVM: security.SMACK64
Nov  6 23:25:58 node-1 kernel: [    0.406482] EVM: security.ima
Nov  6 23:25:58 node-1 kernel: [    0.406483] EVM: security.capability
Nov  6 23:25:58 node-1 kernel: [    0.406532] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.407196] pinctrl core: initialized pinctrl subsystem
Nov  6 23:25:58 node-1 kernel: [    0.407258] regulator-dummy: no parameters
Nov  6 23:25:58 node-1 kernel: [    0.407289] RTC time: 23:25:22, date: 11/06/16
Nov  6 23:25:58 node-1 kernel: [    0.407322] NET: Registered protocol family 16
Nov  6 23:25:58 node-1 kernel: [    0.407407] cpuidle: using governor ladder
Nov  6 23:25:58 node-1 kernel: [    0.407408] cpuidle: using governor menu
Nov  6 23:25:58 node-1 kernel: [    0.407442] ACPI: bus type PCI registered
Nov  6 23:25:58 node-1 kernel: [    0.407443] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov  6 23:25:58 node-1 kernel: [    0.407488] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov  6 23:25:58 node-1 kernel: [    0.407491] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov  6 23:25:58 node-1 kernel: [    0.421230] PCI: Using configuration type 1 for base access
Nov  6 23:25:58 node-1 kernel: [    0.422231] bio: create slab <bio-0> at 0
Nov  6 23:25:58 node-1 kernel: [    0.422502] ACPI: Added _OSI(Module Device)
Nov  6 23:25:58 node-1 kernel: [    0.422504] ACPI: Added _OSI(Processor Device)
Nov  6 23:25:58 node-1 kernel: [    0.422505] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov  6 23:25:58 node-1 kernel: [    0.422506] ACPI: Added _OSI(Processor Aggregator Device)
Nov  6 23:25:58 node-1 kernel: [    0.435185] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov  6 23:25:58 node-1 kernel: [    0.446664] ACPI: Interpreter enabled
Nov  6 23:25:58 node-1 kernel: [    0.446670] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov  6 23:25:58 node-1 kernel: [    0.446674] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov  6 23:25:58 node-1 kernel: [    0.446676] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov  6 23:25:58 node-1 kernel: [    0.446683] ACPI: (supports S0 S4 S5)
Nov  6 23:25:58 node-1 kernel: [    0.446684] ACPI: Using IOAPIC for interrupt routing
Nov  6 23:25:58 node-1 kernel: [    0.446726] HEST: Table parsing has been initialized.
Nov  6 23:25:58 node-1 kernel: [    0.446729] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov  6 23:25:58 node-1 kernel: [    0.447280] ACPI: No dock devices found.
Nov  6 23:25:58 node-1 kernel: [    0.458728] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov  6 23:25:58 node-1 kernel: [    0.458733] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  6 23:25:58 node-1 kernel: [    0.458736] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  6 23:25:58 node-1 kernel: [    0.458766] PCI host bridge to bus 0000:ff
Nov  6 23:25:58 node-1 kernel: [    0.458768] pci_bus 0000:ff: root bus resource [bus ff]
Nov  6 23:25:58 node-1 kernel: [    0.458776] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.458813] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.458843] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.458877] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.458906] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.458934] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.458964] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.458992] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459022] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459048] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459075] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459100] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459127] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459153] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459178] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459204] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459231] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459257] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459283] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.459310] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459335] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.459360] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459385] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459413] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.459446] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459476] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459505] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459535] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459564] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459594] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459623] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459652] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459682] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459713] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459743] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459772] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459803] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459832] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459858] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459888] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459920] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459956] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.459989] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460021] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460048] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460076] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460105] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460133] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460163] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460192] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460223] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460251] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460279] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460306] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460335] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460365] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460395] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460452] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov  6 23:25:58 node-1 kernel: [    0.460455] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  6 23:25:58 node-1 kernel: [    0.460458] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  6 23:25:58 node-1 kernel: [    0.460477] PCI host bridge to bus 0000:7f
Nov  6 23:25:58 node-1 kernel: [    0.460479] pci_bus 0000:7f: root bus resource [bus 7f]
Nov  6 23:25:58 node-1 kernel: [    0.460484] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460512] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.460540] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460570] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460591] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.460616] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.460642] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460668] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460691] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460713] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460736] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460758] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460781] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460803] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460827] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460853] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460874] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460897] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460920] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.460944] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.460966] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.460988] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461017] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461045] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov  6 23:25:58 node-1 kernel: [    0.461082] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461110] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461138] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461167] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461192] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461220] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461246] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461275] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461299] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461329] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461358] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461386] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461415] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461441] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461466] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461494] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461519] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461545] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461574] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461600] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461624] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461651] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461676] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461703] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461728] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461754] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461783] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461809] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461831] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461857] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461883] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461912] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.461938] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.463189] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov  6 23:25:58 node-1 kernel: [    0.463193] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  6 23:25:58 node-1 kernel: [    0.464311] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  6 23:25:58 node-1 kernel: [    0.464820] PCI host bridge to bus 0000:00
Nov  6 23:25:58 node-1 kernel: [    0.464823] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov  6 23:25:58 node-1 kernel: [    0.464824] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov  6 23:25:58 node-1 kernel: [    0.464826] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov  6 23:25:58 node-1 kernel: [    0.464827] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov  6 23:25:58 node-1 kernel: [    0.464828] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov  6 23:25:58 node-1 kernel: [    0.464830] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov  6 23:25:58 node-1 kernel: [    0.464831] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov  6 23:25:58 node-1 kernel: [    0.464837] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov  6 23:25:58 node-1 kernel: [    0.464919] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.464950] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.464991] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov  6 23:25:58 node-1 kernel: [    0.465018] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.465047] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.465088] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov  6 23:25:58 node-1 kernel: [    0.465107] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.465137] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.465177] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov  6 23:25:58 node-1 kernel: [    0.465194] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.465265] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.465342] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.465419] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov  6 23:25:58 node-1 kernel: [    0.465424] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov  6 23:25:58 node-1 kernel: [    0.465510] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov  6 23:25:58 node-1 kernel: [    0.465657] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov  6 23:25:58 node-1 kernel: [    0.465674] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov  6 23:25:58 node-1 kernel: [    0.465752] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.465807] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov  6 23:25:58 node-1 kernel: [    0.465829] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.465885] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.465928] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov  6 23:25:58 node-1 kernel: [    0.465956] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.466012] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.466055] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov  6 23:25:58 node-1 kernel: [    0.466079] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov  6 23:25:58 node-1 kernel: [    0.466096] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov  6 23:25:58 node-1 kernel: [    0.466174] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.466224] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov  6 23:25:58 node-1 kernel: [    0.466250] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov  6 23:25:58 node-1 kernel: [    0.466496] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov  6 23:25:58 node-1 kernel: [    0.466502] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov  6 23:25:58 node-1 kernel: [    0.466508] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.466513] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.466521] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov  6 23:25:58 node-1 kernel: [    0.466551] pci 0000:01:00.0: supports D1 D2
Nov  6 23:25:58 node-1 kernel: [    0.473011] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  6 23:25:58 node-1 kernel: [    0.473017] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  6 23:25:58 node-1 kernel: [    0.473022] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  6 23:25:58 node-1 kernel: [    0.473282] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.473342] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov  6 23:25:58 node-1 kernel: [    0.481008] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  6 23:25:58 node-1 kernel: [    0.481014] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.481018] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  6 23:25:58 node-1 kernel: [    0.481102] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.481184] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.481260] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.481305] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  6 23:25:58 node-1 kernel: [    0.481308] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.481310] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  6 23:25:58 node-1 kernel: [    0.481362] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.481484] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.481537] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  6 23:25:58 node-1 kernel: [    0.481539] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.481541] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  6 23:25:58 node-1 kernel: [    0.481591] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.481713] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.481754] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.481889] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.481927] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.482048] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.482085] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov  6 23:25:58 node-1 kernel: [    0.482204] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov  6 23:25:58 node-1 kernel: [    0.482246] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  6 23:25:58 node-1 kernel: [    0.482249] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.482251] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  6 23:25:58 node-1 kernel: [    0.482309] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov  6 23:25:58 node-1 kernel: [    0.482372] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.482424] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.482465] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov  6 23:25:58 node-1 kernel: [    0.482547] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov  6 23:25:58 node-1 kernel: [    0.482652] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  6 23:25:58 node-1 kernel: [    0.482655] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.482657] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  6 23:25:58 node-1 kernel: [    0.482713] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov  6 23:25:58 node-1 kernel: [    0.482766] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.482815] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.483052] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  6 23:25:58 node-1 kernel: [    0.483056] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  6 23:25:58 node-1 kernel: [    0.483119] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov  6 23:25:58 node-1 kernel: [    0.483175] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.483223] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.483432] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  6 23:25:58 node-1 kernel: [    0.483436] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  6 23:25:58 node-1 kernel: [    0.483494] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov  6 23:25:58 node-1 kernel: [    0.483554] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.483606] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov  6 23:25:58 node-1 kernel: [    0.483829] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  6 23:25:58 node-1 kernel: [    0.483833] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  6 23:25:58 node-1 kernel: [    0.484028] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  6 23:25:58 node-1 kernel: [    0.484071] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  6 23:25:58 node-1 kernel: [    0.484149] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov  6 23:25:58 node-1 kernel: [    0.484168] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov  6 23:25:58 node-1 kernel: [    0.484181] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov  6 23:25:58 node-1 kernel: [    0.484195] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov  6 23:25:58 node-1 kernel: [    0.484245] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov  6 23:25:58 node-1 kernel: [    0.489025] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  6 23:25:58 node-1 kernel: [    0.489030] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  6 23:25:58 node-1 kernel: [    0.489062] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov  6 23:25:58 node-1 kernel: [    0.489550] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov  6 23:25:58 node-1 kernel: [    0.489553] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  6 23:25:58 node-1 kernel: [    0.489673] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  6 23:25:58 node-1 kernel: [    0.489778] PCI host bridge to bus 0000:80
Nov  6 23:25:58 node-1 kernel: [    0.489780] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov  6 23:25:58 node-1 kernel: [    0.489782] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov  6 23:25:58 node-1 kernel: [    0.489783] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov  6 23:25:58 node-1 kernel: [    0.489791] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.489852] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.489918] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov  6 23:25:58 node-1 kernel: [    0.489978] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov  6 23:25:58 node-1 kernel: [    0.489983] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov  6 23:25:58 node-1 kernel: [    0.490054] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov  6 23:25:58 node-1 kernel: [    0.490349] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov  6 23:25:58 node-1 kernel: [    0.490381] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov  6 23:25:58 node-1 kernel: [    0.490410] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov  6 23:25:58 node-1 kernel: [    0.490439] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov  6 23:25:58 node-1 kernel: [    0.490469] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  6 23:25:58 node-1 kernel: [    0.490498] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  6 23:25:58 node-1 kernel: [    0.490528] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  6 23:25:58 node-1 kernel: [    0.490558] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  6 23:25:58 node-1 kernel: [    0.490642] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov  6 23:25:58 node-1 kernel: [    0.490646] ACPI: \_SB_.UNC1: notify handler is installed
Nov  6 23:25:58 node-1 kernel: [    0.490648] ACPI: \_SB_.UNC0: notify handler is installed
Nov  6 23:25:58 node-1 kernel: [    0.490662] ACPI: \_SB_.PCI0: notify handler is installed
Nov  6 23:25:58 node-1 kernel: [    0.490715] ACPI: \_SB_.PCI1: notify handler is installed
Nov  6 23:25:58 node-1 kernel: [    0.490794] Found 4 acpi root devices
Nov  6 23:25:58 node-1 kernel: [    0.490898] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov  6 23:25:58 node-1 kernel: [    0.490900] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov  6 23:25:58 node-1 kernel: [    0.490902] vgaarb: loaded
Nov  6 23:25:58 node-1 kernel: [    0.490903] vgaarb: bridge control possible 0000:0c:00.0
Nov  6 23:25:58 node-1 kernel: [    0.491016] SCSI subsystem initialized
Nov  6 23:25:58 node-1 kernel: [    0.491078] libata version 3.00 loaded.
Nov  6 23:25:58 node-1 kernel: [    0.491093] ACPI: bus type USB registered
Nov  6 23:25:58 node-1 kernel: [    0.491103] usbcore: registered new interface driver usbfs
Nov  6 23:25:58 node-1 kernel: [    0.491108] usbcore: registered new interface driver hub
Nov  6 23:25:58 node-1 kernel: [    0.491131] usbcore: registered new device driver usb
Nov  6 23:25:58 node-1 kernel: [    0.491287] PCI: Using ACPI for IRQ routing
Nov  6 23:25:58 node-1 kernel: [    0.494873] PCI: pci_cache_line_size set to 64 bytes
Nov  6 23:25:58 node-1 kernel: [    0.495076] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov  6 23:25:58 node-1 kernel: [    0.495077] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Nov  6 23:25:58 node-1 kernel: [    0.495078] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov  6 23:25:58 node-1 kernel: [    0.495140] NetLabel: Initializing
Nov  6 23:25:58 node-1 kernel: [    0.495142] NetLabel:  domain hash size = 128
Nov  6 23:25:58 node-1 kernel: [    0.495143] NetLabel:  protocols = UNLABELED CIPSOv4
Nov  6 23:25:58 node-1 kernel: [    0.495152] NetLabel:  unlabeled traffic allowed by default
Nov  6 23:25:58 node-1 kernel: [    0.495206] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov  6 23:25:58 node-1 kernel: [    0.495210] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov  6 23:25:58 node-1 kernel: [    0.497279] Switched to clocksource hpet
Nov  6 23:25:58 node-1 kernel: [    0.501535] AppArmor: AppArmor Filesystem Enabled
Nov  6 23:25:58 node-1 kernel: [    0.501572] pnp: PnP ACPI init
Nov  6 23:25:58 node-1 kernel: [    0.501584] ACPI: bus type PNP registered
Nov  6 23:25:58 node-1 kernel: [    0.501758] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov  6 23:25:58 node-1 kernel: [    0.501770] pnp 00:01: [dma 4]
Nov  6 23:25:58 node-1 kernel: [    0.501787] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov  6 23:25:58 node-1 kernel: [    0.501820] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov  6 23:25:58 node-1 kernel: [    0.501844] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov  6 23:25:58 node-1 kernel: [    0.501864] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov  6 23:25:58 node-1 kernel: [    0.501909] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov  6 23:25:58 node-1 kernel: [    0.502016] system 00:06: [io  0x0500-0x057f] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502019] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov  6 23:25:58 node-1 kernel: [    0.502020] system 00:06: [io  0x0580-0x059f] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502022] system 00:06: [io  0x0600-0x061f] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502023] system 00:06: [io  0x0880-0x0883] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502025] system 00:06: [io  0x0800-0x081f] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502028] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov  6 23:25:58 node-1 kernel: [    0.502030] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502031] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502033] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502034] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502036] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502037] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov  6 23:25:58 node-1 kernel: [    0.502040] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov  6 23:25:58 node-1 kernel: [    0.502139] pnp 00:07: [dma 0 disabled]
Nov  6 23:25:58 node-1 kernel: [    0.502170] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  6 23:25:58 node-1 kernel: [    0.502250] pnp 00:08: [dma 0 disabled]
Nov  6 23:25:58 node-1 kernel: [    0.502285] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  6 23:25:58 node-1 kernel: [    0.502342] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov  6 23:25:58 node-1 kernel: [    0.502776] pnp: PnP ACPI: found 10 devices
Nov  6 23:25:58 node-1 kernel: [    0.502778] ACPI: bus type PNP unregistered
Nov  6 23:25:58 node-1 kernel: [    0.508668] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  6 23:25:58 node-1 kernel: [    0.508672] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  6 23:25:58 node-1 kernel: [    0.508675] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  6 23:25:58 node-1 kernel: [    0.508680] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  6 23:25:58 node-1 kernel: [    0.508682] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.508696] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  6 23:25:58 node-1 kernel: [    0.508726] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  6 23:25:58 node-1 kernel: [    0.508740] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  6 23:25:58 node-1 kernel: [    0.508769] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  6 23:25:58 node-1 kernel: [    0.508784] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  6 23:25:58 node-1 kernel: [    0.508812] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  6 23:25:58 node-1 kernel: [    0.508827] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  6 23:25:58 node-1 kernel: [    0.508874] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  6 23:25:58 node-1 kernel: [    0.508876] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.508891] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  6 23:25:58 node-1 kernel: [    0.508920] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  6 23:25:58 node-1 kernel: [    0.508922] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.508937] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  6 23:25:58 node-1 kernel: [    0.508966] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  6 23:25:58 node-1 kernel: [    0.508967] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.508970] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  6 23:25:58 node-1 kernel: [    0.508975] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  6 23:25:58 node-1 kernel: [    0.508977] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.508979] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  6 23:25:58 node-1 kernel: [    0.508984] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  6 23:25:58 node-1 kernel: [    0.508989] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  6 23:25:58 node-1 kernel: [    0.508998] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  6 23:25:58 node-1 kernel: [    0.509002] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  6 23:25:58 node-1 kernel: [    0.509009] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov  6 23:25:58 node-1 kernel: [    0.509010] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov  6 23:25:58 node-1 kernel: [    0.509011] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov  6 23:25:58 node-1 kernel: [    0.509012] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov  6 23:25:58 node-1 kernel: [    0.509013] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov  6 23:25:58 node-1 kernel: [    0.509014] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov  6 23:25:58 node-1 kernel: [    0.509015] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov  6 23:25:58 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov  6 23:25:58 node-1 kernel: [    0.509016] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov  6 23:25:58 node-1 kernel: [    0.509017] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.509018] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  6 23:25:58 node-1 kernel: [    0.509019] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.509020] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  6 23:25:58 node-1 kernel: [    0.509021] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.509022] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  6 23:25:58 node-1 kernel: [    0.509023] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.509024] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  6 23:25:58 node-1 kernel: [    0.509025] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov  6 23:25:58 node-1 kernel: [    0.509026] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov  6 23:25:58 node-1 kernel: [    0.509027] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov  6 23:25:58 node-1 kernel: [    0.509028] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov  6 23:25:58 node-1 kernel: [    0.509030] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov  6 23:25:58 node-1 kernel: [    0.509031] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov  6 23:25:58 node-1 kernel: [    0.509033] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov  6 23:25:58 node-1 kernel: [    0.509034] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov  6 23:25:58 node-1 kernel: [    0.509072] NET: Registered protocol family 2
Nov  6 23:25:58 node-1 kernel: [    0.509364] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.509709] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.509861] TCP: Hash tables configured (established 262144 bind 65536)
Nov  6 23:25:58 node-1 kernel: [    0.509901] TCP: reno registered
Nov  6 23:25:58 node-1 kernel: [    0.509931] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.510029] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.510179] NET: Registered protocol family 1
Nov  6 23:25:58 node-1 kernel: [    0.545370] pci 0000:0c:00.0: Video device with shadowed ROM
Nov  6 23:25:58 node-1 kernel: [    0.545384] PCI: CLS 64 bytes, default 64
Nov  6 23:25:58 node-1 kernel: [    0.545443] Trying to unpack rootfs image as initramfs...
Nov  6 23:25:58 node-1 kernel: [    0.766815] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Nov  6 23:25:58 node-1 kernel: [    0.766875] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov  6 23:25:58 node-1 kernel: [    0.766885] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Nov  6 23:25:58 node-1 kernel: [    0.767286] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767293] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767300] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767307] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767317] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767325] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767337] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767345] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767352] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767359] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767366] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767373] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767382] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767402] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767409] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767415] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov  6 23:25:58 node-1 kernel: [    0.767513] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov  6 23:25:58 node-1 kernel: [    0.767516] Scanning for low memory corruption every 60 seconds
Nov  6 23:25:58 node-1 kernel: [    0.767897] Initialise system trusted keyring
Nov  6 23:25:58 node-1 kernel: [    0.767948] audit: initializing netlink socket (disabled)
Nov  6 23:25:58 node-1 kernel: [    0.767965] type=2000 audit(1478474721.712:1): initialized
Nov  6 23:25:58 node-1 kernel: [    0.785669] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov  6 23:25:58 node-1 kernel: [    0.787143] zbud: loaded
Nov  6 23:25:58 node-1 kernel: [    0.787261] VFS: Disk quotas dquot_6.5.2
Nov  6 23:25:58 node-1 kernel: [    0.787295] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov  6 23:25:58 node-1 kernel: [    0.787651] fuse init (API version 7.22)
Nov  6 23:25:58 node-1 kernel: [    0.787710] msgmni has been set to 32768
Nov  6 23:25:58 node-1 kernel: [    0.787760] Key type big_key registered
Nov  6 23:25:58 node-1 kernel: [    0.788238] Key type asymmetric registered
Nov  6 23:25:58 node-1 kernel: [    0.788240] Asymmetric key parser 'x509' registered
Nov  6 23:25:58 node-1 kernel: [    0.788259] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov  6 23:25:58 node-1 kernel: [    0.788323] io scheduler noop registered
Nov  6 23:25:58 node-1 kernel: [    0.788324] io scheduler deadline registered (default)
Nov  6 23:25:58 node-1 kernel: [    0.788342] io scheduler cfq registered
Nov  6 23:25:58 node-1 kernel: [    0.788661] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    0.788781] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    0.788907] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    0.789028] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    0.789159] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    0.789253] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    0.789628] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov  6 23:25:58 node-1 kernel: [    0.789653] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov  6 23:25:58 node-1 kernel: [    0.789675] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov  6 23:25:58 node-1 kernel: [    0.789684] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789687] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789689] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov  6 23:25:58 node-1 kernel: [    0.789694] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789696] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789697] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789699] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789700] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789701] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789703] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789704] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789706] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789707] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789709] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789710] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789712] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov  6 23:25:58 node-1 kernel: [    0.789717] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789719] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov  6 23:25:58 node-1 kernel: [    0.789731] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789734] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov  6 23:25:58 node-1 kernel: [    0.789744] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789746] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov  6 23:25:58 node-1 kernel: [    0.789749] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov  6 23:25:58 node-1 kernel: [    0.789783] ioapic: probe of 0000:00:05.4 failed with error -22
Nov  6 23:25:58 node-1 kernel: [    0.789789] ioapic: probe of 0000:80:05.4 failed with error -22
Nov  6 23:25:58 node-1 kernel: [    0.789793] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov  6 23:25:58 node-1 kernel: [    0.789802] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov  6 23:25:58 node-1 kernel: [    0.789839] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov  6 23:25:58 node-1 kernel: [    0.789841] vesafb: scrolling: redraw
Nov  6 23:25:58 node-1 kernel: [    0.789842] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov  6 23:25:58 node-1 kernel: [    0.809967] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov  6 23:25:58 node-1 kernel: [    0.818440] Console: switching to colour frame buffer device 80x30
Nov  6 23:25:58 node-1 kernel: [    0.827104] fb0: VESA VGA frame buffer device
Nov  6 23:25:58 node-1 kernel: [    0.827299] intel_idle: MWAIT substates: 0x2120
Nov  6 23:25:58 node-1 kernel: [    0.827300] intel_idle: v0.4 model 0x3F
Nov  6 23:25:58 node-1 kernel: [    0.827301] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov  6 23:25:58 node-1 kernel: [    0.827529] ipmi message handler version 39.2
Nov  6 23:25:58 node-1 kernel: [    0.827806] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov  6 23:25:58 node-1 kernel: [    0.828238] ACPI: AC Adapter [P111] (on-line)
Nov  6 23:25:58 node-1 kernel: [    0.833456] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov  6 23:25:58 node-1 kernel: [    0.844466] ACPI: Power Button [PWRB]
Nov  6 23:25:58 node-1 kernel: [    0.850217] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov  6 23:25:58 node-1 kernel: [    0.861841] ACPI: Power Button [PWRF]
Nov  6 23:25:58 node-1 kernel: [    0.882819] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov  6 23:25:58 node-1 kernel: [    0.894523] pstore: Registered erst as persistent store backend
Nov  6 23:25:58 node-1 kernel: [    0.900752] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov  6 23:25:58 node-1 kernel: [    0.912759] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov  6 23:25:58 node-1 kernel: [    0.939553] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov  6 23:25:58 node-1 kernel: [    0.973054] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov  6 23:25:58 node-1 kernel: [    0.987218] Linux agpgart interface v0.103
Nov  6 23:25:58 node-1 kernel: [    0.994863] brd: module loaded
Nov  6 23:25:58 node-1 kernel: [    1.001884] loop: module loaded
Nov  6 23:25:58 node-1 kernel: [    1.008611] libphy: Fixed MDIO Bus: probed
Nov  6 23:25:58 node-1 kernel: [    1.015098] tun: Universal TUN/TAP device driver, 1.6
Nov  6 23:25:58 node-1 kernel: [    1.021581] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov  6 23:25:58 node-1 kernel: [    1.028099] PPP generic driver version 2.4.2
Nov  6 23:25:58 node-1 kernel: [    1.034490] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov  6 23:25:58 node-1 kernel: [    1.040935] ehci-pci: EHCI PCI platform driver
Nov  6 23:25:58 node-1 kernel: [    1.047463] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov  6 23:25:58 node-1 kernel: [    1.053883] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov  6 23:25:58 node-1 kernel: [    1.066417] ehci-pci 0000:00:1a.0: debug port 2
Nov  6 23:25:58 node-1 kernel: [    1.076622] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov  6 23:25:58 node-1 kernel: [    1.076640] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov  6 23:25:58 node-1 kernel: [    1.092766] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov  6 23:25:58 node-1 kernel: [    1.098843] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov  6 23:25:58 node-1 kernel: [    1.105015] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  6 23:25:58 node-1 kernel: [    1.116930] usb usb1: Product: EHCI Host Controller
Nov  6 23:25:58 node-1 kernel: [    1.122968] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  6 23:25:58 node-1 kernel: [    1.129028] usb usb1: SerialNumber: 0000:00:1a.0
Nov  6 23:25:58 node-1 kernel: [    1.135010] hub 1-0:1.0: USB hub found
Nov  6 23:25:58 node-1 kernel: [    1.140789] hub 1-0:1.0: 2 ports detected
Nov  6 23:25:58 node-1 kernel: [    1.146578] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov  6 23:25:58 node-1 kernel: [    1.152157] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov  6 23:25:58 node-1 kernel: [    1.163058] ehci-pci 0000:00:1d.0: debug port 2
Nov  6 23:25:58 node-1 kernel: [    1.172363] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov  6 23:25:58 node-1 kernel: [    1.172366] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov  6 23:25:58 node-1 kernel: [    1.188685] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov  6 23:25:58 node-1 kernel: [    1.193886] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov  6 23:25:58 node-1 kernel: [    1.199263] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  6 23:25:58 node-1 kernel: [    1.209893] usb usb2: Product: EHCI Host Controller
Nov  6 23:25:58 node-1 kernel: [    1.215366] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  6 23:25:58 node-1 kernel: [    1.220914] usb usb2: SerialNumber: 0000:00:1d.0
Nov  6 23:25:58 node-1 kernel: [    1.226464] hub 2-0:1.0: USB hub found
Nov  6 23:25:58 node-1 kernel: [    1.231813] hub 2-0:1.0: 2 ports detected
Nov  6 23:25:58 node-1 kernel: [    1.237128] ehci-platform: EHCI generic platform driver
Nov  6 23:25:58 node-1 kernel: [    1.242362] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov  6 23:25:58 node-1 kernel: [    1.247686] ohci-pci: OHCI PCI platform driver
Nov  6 23:25:58 node-1 kernel: [    1.253002] ohci-platform: OHCI generic platform driver
Nov  6 23:25:58 node-1 kernel: [    1.258238] uhci_hcd: USB Universal Host Controller Interface driver
Nov  6 23:25:58 node-1 kernel: [    1.263614] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov  6 23:25:58 node-1 kernel: [    1.456463] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov  6 23:25:58 node-1 kernel: [    1.784178] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov  6 23:25:58 node-1 kernel: [    1.796534] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov  6 23:25:58 node-1 kernel: [    1.802158] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  6 23:25:58 node-1 kernel: [    1.807930] hub 1-1:1.0: USB hub found
Nov  6 23:25:58 node-1 kernel: [    1.813521] hub 1-1:1.0: 6 ports detected
Nov  6 23:25:58 node-1 kernel: [    1.928085] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov  6 23:25:58 node-1 kernel: [    2.302454] i8042: No controller found
Nov  6 23:25:58 node-1 kernel: [    2.308016] mousedev: PS/2 mouse device common for all mice
Nov  6 23:25:58 node-1 kernel: [    2.313763] rtc_cmos 00:02: RTC can wake from S4
Nov  6 23:25:58 node-1 kernel: [    2.316526] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov  6 23:25:58 node-1 kernel: [    2.316527] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  6 23:25:58 node-1 kernel: [    2.316919] hub 2-1:1.0: USB hub found
Nov  6 23:25:58 node-1 kernel: [    2.317156] hub 2-1:1.0: 8 ports detected
Nov  6 23:25:58 node-1 kernel: [    2.342126] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov  6 23:25:58 node-1 kernel: [    2.347897] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov  6 23:25:58 node-1 kernel: [    2.359248] device-mapper: uevent: version 1.0.3
Nov  6 23:25:58 node-1 kernel: [    2.364981] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov  6 23:25:58 node-1 kernel: [    2.376404] ledtrig-cpu: registered to indicate activity on CPUs
Nov  6 23:25:58 node-1 kernel: [    2.382424] TCP: cubic registered
Nov  6 23:25:58 node-1 kernel: [    2.388330] NET: Registered protocol family 10
Nov  6 23:25:58 node-1 kernel: [    2.394432] NET: Registered protocol family 17
Nov  6 23:25:58 node-1 kernel: [    2.400224] Key type dns_resolver registered
Nov  6 23:25:58 node-1 kernel: [    2.406304] Loading compiled-in X.509 certificates
Nov  6 23:25:58 node-1 kernel: [    2.412547] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov  6 23:25:58 node-1 kernel: [    2.424210] registered taskstats version 1
Nov  6 23:25:58 node-1 kernel: [    2.432316] Key type trusted registered
Nov  6 23:25:58 node-1 kernel: [    2.440135] Key type encrypted registered
Nov  6 23:25:58 node-1 kernel: [    2.445648] AppArmor: AppArmor sha1 policy hashing enabled
Nov  6 23:25:58 node-1 kernel: [    2.451171] IMA: No TPM chip found, activating TPM-bypass!
Nov  6 23:25:58 node-1 kernel: [    2.457255] regulator-dummy: disabling
Nov  6 23:25:58 node-1 kernel: [    2.462755]   Magic number: 8:297:453
Nov  6 23:25:58 node-1 kernel: [    2.468538] rtc_cmos 00:02: setting system clock to 2016-11-06 23:25:24 UTC (1478474724)
Nov  6 23:25:58 node-1 kernel: [    2.480932] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov  6 23:25:58 node-1 kernel: [    2.486595] EDD information not available.
Nov  6 23:25:58 node-1 kernel: [    2.492228] PM: Hibernation image not present or could not be loaded.
Nov  6 23:25:58 node-1 kernel: [    2.493037] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov  6 23:25:58 node-1 kernel: [    2.504347] Write protecting the kernel read-only data: 12288k
Nov  6 23:25:58 node-1 kernel: [    2.510586] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov  6 23:25:58 node-1 kernel: [    2.523486] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov  6 23:25:58 node-1 kernel: [    2.555239] device-mapper: multipath: version 1.6.0 loaded
Nov  6 23:25:58 node-1 kernel: [    2.563116] systemd-udevd[215]: starting version 204
Nov  6 23:25:58 node-1 kernel: [    2.582609] md: linear personality registered for level -1
Nov  6 23:25:58 node-1 kernel: [    2.596878] md: multipath personality registered for level -4
Nov  6 23:25:58 node-1 kernel: [    2.599628] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov  6 23:25:58 node-1 kernel: [    2.611094] md: raid0 personality registered for level 0
Nov  6 23:25:58 node-1 kernel: [    2.619420] md: raid1 personality registered for level 1
Nov  6 23:25:58 node-1 kernel: [    2.628996] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov  6 23:25:58 node-1 kernel: [    2.635722] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov  6 23:25:58 node-1 kernel: [    2.635515] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov  6 23:25:58 node-1 kernel: [    2.636280] megasas: FW now in Ready state
Nov  6 23:25:58 node-1 kernel: [    2.636339] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636374] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636409] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636447] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636487] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636523] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636559] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636590] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636627] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636664] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636697] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636734] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636766] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636804] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636841] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.636874] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.637036] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov  6 23:25:58 node-1 kernel: [    2.675230] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Nov  6 23:25:58 node-1 kernel: [    2.694874] 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
Nov  6 23:25:58 node-1 kernel: [    2.695526] raid6: sse2x1    7306 MB/s
Nov  6 23:25:58 node-1 kernel: [    2.715234] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  6 23:25:58 node-1 kernel: [    2.722215] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.722219] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.722223] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.722227] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.722286] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  6 23:25:58 node-1 kernel: [    2.743819] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Nov  6 23:25:58 node-1 kernel: [    2.757026] 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
Nov  6 23:25:58 node-1 kernel: [    2.763671] raid6: sse2x2    2489 MB/s
Nov  6 23:25:58 node-1 kernel: [    2.776898] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov  6 23:25:58 node-1 kernel: [    2.831308] raid6: sse2x4    7835 MB/s
Nov  6 23:25:58 node-1 kernel: [    2.903236] raid6: avx2x1   14937 MB/s
Nov  6 23:25:58 node-1 kernel: [    2.975176] raid6: avx2x2   18859 MB/s
Nov  6 23:25:58 node-1 kernel: [    3.047124] raid6: avx2x4   21273 MB/s
Nov  6 23:25:58 node-1 kernel: [    3.053240] raid6: using algorithm avx2x4 (21273 MB/s)
Nov  6 23:25:58 node-1 kernel: [    3.059336] raid6: using avx2x2 recovery algorithm
Nov  6 23:25:58 node-1 kernel: [    3.065319] Switched to clocksource tsc
Nov  6 23:25:58 node-1 kernel: [    3.065321] megasas:IOC Init cmd success
Nov  6 23:25:58 node-1 kernel: [    3.065331] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.065370] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.065410] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.065447] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.065478] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.065507] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.065661] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.067021] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov  6 23:25:58 node-1 kernel: [    3.067022] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  6 23:25:58 node-1 kernel: [    3.067023] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov  6 23:25:58 node-1 kernel: [    3.067024] usb 2-1.4: Manufacturer: Avocent
Nov  6 23:25:58 node-1 kernel: [    3.067024] usb 2-1.4: SerialNumber: 20111102-00000001
Nov  6 23:25:58 node-1 kernel: [    3.078951] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Nov  6 23:25:58 node-1 kernel: [    3.078952] 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
Nov  6 23:25:58 node-1 kernel: [    3.078953] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  6 23:25:58 node-1 kernel: [    3.079008] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.079047] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.079106] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.079143] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.079273] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.087119] megasas: INIT adapter done
Nov  6 23:25:58 node-1 kernel: [    3.090514] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Nov  6 23:25:58 node-1 kernel: [    3.090515] 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
Nov  6 23:25:58 node-1 kernel: [    3.090516] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  6 23:25:58 node-1 kernel: [    3.090572] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.090612] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.090650] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.090684] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.090754] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  6 23:25:58 node-1 kernel: [    3.125022] xor: automatically using best checksumming function:
Nov  6 23:25:58 node-1 kernel: [    3.159028] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov  6 23:25:58 node-1 kernel: [    3.159372] scsi0 : LSI SAS based MegaRAID driver
Nov  6 23:25:58 node-1 kernel: [    3.163014]    avx       : 36457.000 MB/sec
Nov  6 23:25:58 node-1 kernel: [    3.166389] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  6 23:25:58 node-1 kernel: [    3.172055] hidraw: raw HID events driver (C) Jiri Kosina
Nov  6 23:25:58 node-1 kernel: [    3.177185] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  6 23:25:58 node-1 kernel: [    3.181008] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov  6 23:25:58 node-1 kernel: [    3.181151] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov  6 23:25:58 node-1 kernel: [    3.181490] sd 0:2:0:0: [sda] Write Protect is off
Nov  6 23:25:58 node-1 kernel: [    3.181491] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov  6 23:25:58 node-1 kernel: [    3.181562] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov  6 23:25:58 node-1 kernel: [    3.211469]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Nov  6 23:25:58 node-1 kernel: [    3.212035] sd 0:2:0:0: [sda] Attached SCSI disk
Nov  6 23:25:58 node-1 kernel: [    3.256393] async_tx: api initialized (async)
Nov  6 23:25:58 node-1 kernel: [    3.271761] usbcore: registered new interface driver usbhid
Nov  6 23:25:58 node-1 kernel: [    3.271762] usbhid: USB HID core driver
Nov  6 23:25:58 node-1 kernel: [    3.339040] 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
Nov  6 23:25:58 node-1 kernel: [    3.351987] 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
Nov  6 23:25:58 node-1 kernel: [    3.365232] 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
Nov  6 23:25:58 node-1 kernel: [    3.378429] 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
Nov  6 23:25:58 node-1 kernel: [    3.378697] md: raid6 personality registered for level 6
Nov  6 23:25:58 node-1 kernel: [    3.378698] md: raid5 personality registered for level 5
Nov  6 23:25:58 node-1 kernel: [    3.378698] md: raid4 personality registered for level 4
Nov  6 23:25:58 node-1 kernel: [    3.411848] 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
Nov  6 23:25:58 node-1 kernel: [    3.425077] 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
Nov  6 23:25:58 node-1 kernel: [    3.438743] md: raid10 personality registered for level 10
Nov  6 23:25:58 node-1 kernel: [    3.489826] random: lvm urandom read with 38 bits of entropy available
Nov  6 23:25:58 node-1 kernel: [    3.501835] multipathd (366): /proc/366/oom_adj is deprecated, please use /proc/366/oom_score_adj instead.
Nov  6 23:25:58 node-1 kernel: [    3.743016] bio: create slab <bio-1> at 1
Nov  6 23:25:58 node-1 kernel: [    4.534245] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov  6 23:25:58 node-1 kernel: [    5.049298] init: plymouth-upstart-bridge main process (552) terminated with status 1
Nov  6 23:25:58 node-1 kernel: [    5.062289] init: plymouth-upstart-bridge main process ended, respawning
Nov  6 23:25:58 node-1 kernel: [    5.066575] random: nonblocking pool is initialized
Nov  6 23:25:58 node-1 kernel: [    5.079734] init: plymouth-upstart-bridge main process (565) terminated with status 1
Nov  6 23:25:58 node-1 kernel: [    5.093528] init: plymouth-upstart-bridge main process ended, respawning
Nov  6 23:25:58 node-1 kernel: [    5.226922] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Nov  6 23:25:58 node-1 kernel: [    5.257836] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov  6 23:25:58 node-1 kernel: [    5.373957] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov  6 23:25:58 node-1 kernel: [    5.427810] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov  6 23:25:58 node-1 kernel: [    5.490981] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov  6 23:25:58 node-1 kernel: [    5.646777] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov  6 23:25:58 node-1 kernel: [    5.702545] XFS (dm-0): Mounting Filesystem
Nov  6 23:25:58 node-1 kernel: [    6.022339] XFS (dm-0): Ending clean mount
Nov  6 23:25:58 node-1 kernel: [    6.143576] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Nov  6 23:25:58 node-1 kernel: [    6.181246] XFS (dm-1): Mounting Filesystem
Nov  6 23:25:58 node-1 kernel: [    6.251347] XFS (dm-1): Ending clean mount
Nov  6 23:25:58 node-1 kernel: [    8.201205] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  6 23:25:58 node-1 kernel: [    8.224892] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  6 23:25:58 node-1 kernel: [    8.459766] systemd-udevd[778]: starting version 204
Nov  6 23:25:58 node-1 kernel: [    8.673116] power_meter ACPI000D:00: Found ACPI power meter.
Nov  6 23:25:58 node-1 kernel: [    8.673130] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov  6 23:25:58 node-1 kernel: [    8.695401] IPMI System Interface driver.
Nov  6 23:25:58 node-1 kernel: [    8.695449] ipmi_si: probing via ACPI
Nov  6 23:25:58 node-1 kernel: [    8.695464] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov  6 23:25:58 node-1 kernel: [    8.695465] ipmi_si: Adding ACPI-specified kcs state machine
Nov  6 23:25:58 node-1 kernel: [    8.695475] ipmi_si: probing via SMBIOS
Nov  6 23:25:58 node-1 kernel: [    8.695476] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov  6 23:25:58 node-1 kernel: [    8.695477] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov  6 23:25:58 node-1 kernel: [    8.695480] ipmi_si: probing via SPMI
Nov  6 23:25:58 node-1 kernel: [    8.695481] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov  6 23:25:58 node-1 kernel: [    8.695482] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov  6 23:25:58 node-1 kernel: [    8.695484] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov  6 23:25:58 node-1 kernel: [    8.697310] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov  6 23:25:58 node-1 kernel: [    8.697315] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  6 23:25:58 node-1 kernel: [    8.697318] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov  6 23:25:58 node-1 kernel: [    8.697320] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  6 23:25:58 node-1 kernel: [    8.697333] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov  6 23:25:58 node-1 kernel: [    8.704845] wmi: Mapper loaded
Nov  6 23:25:58 node-1 kernel: [    8.724379] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov  6 23:25:58 node-1 kernel: [    8.778773] systemd-udevd[796]: renamed network interface eth0 to enp6s0
Nov  6 23:25:58 node-1 kernel: [    8.814648] systemd-udevd[806]: renamed network interface eth1 to enp7s0
Nov  6 23:25:58 node-1 kernel: [    8.830595] systemd-udevd[795]: renamed network interface eth2 to enp8s0
Nov  6 23:25:58 node-1 kernel: [    8.846614] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov  6 23:25:58 node-1 kernel: [    8.846618] ipmi_si 00:09: IPMI kcs interface initialized
Nov  6 23:25:58 node-1 kernel: [    8.865826] systemd-udevd[797]: renamed network interface eth3 to enp9s0
Nov  6 23:25:58 node-1 kernel: [    9.164320] type=1400 audit(1478474731.197:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1058 comm="apparmor_parser"
Nov  6 23:25:58 node-1 kernel: [    9.164474] type=1400 audit(1478474731.197:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1058 comm="apparmor_parser"
Nov  6 23:25:58 node-1 kernel: [    9.164596] type=1400 audit(1478474731.197:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1058 comm="apparmor_parser"
Nov  6 23:25:58 node-1 kernel: [    9.173755] type=1400 audit(1478474731.205:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1055 comm="apparmor_parser"
Nov  6 23:25:58 node-1 kernel: [    9.173923] type=1400 audit(1478474731.209:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1055 comm="apparmor_parser"
Nov  6 23:25:58 node-1 kernel: [    9.174053] type=1400 audit(1478474731.209:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1055 comm="apparmor_parser"
Nov  6 23:25:58 node-1 kernel: [    9.192463] type=1400 audit(1478474731.225:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1059 comm="apparmor_parser"
Nov  6 23:25:58 node-1 kernel: [    9.192607] type=1400 audit(1478474731.225:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1059 comm="apparmor_parser"
Nov  6 23:25:58 node-1 kernel: [    9.192730] type=1400 audit(1478474731.225:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1059 comm="apparmor_parser"
Nov  6 23:25:58 node-1 kernel: [    9.195194] type=1400 audit(1478474731.229:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1057 comm="apparmor_parser"
Nov  6 23:25:58 node-1 kernel: [    9.880345] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  6 23:25:58 node-1 kernel: [    9.881085] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  6 23:25:58 node-1 kernel: [   10.075650] enic 0000:06:00.0 enp6s0: Link UP
Nov  6 23:25:58 node-1 kernel: [   10.076081] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov  6 23:25:58 node-1 kernel: [   10.076093] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov  6 23:25:58 node-1 kernel: [   19.711677] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov  6 23:25:59 node-1 failsafe: Failsafe of 120 seconds reached.
Nov  6 23:25:59 node-1 kernel: [   38.157371] init: failsafe main process (8418) killed by TERM signal
Nov  6 23:25:59 node-1 dbus[8460]: [system] AppArmor D-Bus mediation is enabled
Nov  6 23:25:59 node-1 kernel: [   38.330825] audit_printk_skb: 30 callbacks suppressed
Nov  6 23:25:59 node-1 kernel: [   38.330827] type=1400 audit(1478474759.989:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8544 comm="apparmor_parser"
Nov  6 23:25:59 node-1 kernel: [   38.330934] type=1400 audit(1478474759.989:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8543 comm="apparmor_parser"
Nov  6 23:25:59 node-1 kernel: [   38.330939] type=1400 audit(1478474759.989:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8543 comm="apparmor_parser"
Nov  6 23:25:59 node-1 kernel: [   38.330942] type=1400 audit(1478474759.989:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Nov  6 23:25:59 node-1 kernel: [   38.331173] type=1400 audit(1478474759.989:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8543 comm="apparmor_parser"
Nov  6 23:25:59 node-1 kernel: [   38.331175] type=1400 audit(1478474759.989:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Nov  6 23:25:59 node-1 kernel: [   38.331292] type=1400 audit(1478474759.989:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Nov  6 23:26:00 node-1 kernel: [   38.419394] type=1400 audit(1478474760.077:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8546 comm="apparmor_parser"
Nov  6 23:26:00 node-1 anacron[8610]: Anacron 2.3 started on 2016-11-06
Nov  6 23:26:00 node-1 cron[8576]: (CRON) INFO (pidfile fd = 3)
Nov  6 23:26:00 node-1 cron[8618]: (CRON) STARTUP (fork ok)
Nov  6 23:26:00 node-1 anacron[8610]: Will run job `cron.daily' in 5 min.
Nov  6 23:26:00 node-1 anacron[8610]: Will run job `cron.weekly' in 10 min.
Nov  6 23:26:00 node-1 anacron[8610]: Will run job `cron.monthly' in 15 min.
Nov  6 23:26:00 node-1 anacron[8610]: Jobs will be executed sequentially
Nov  6 23:26:00 node-1 multipathd: path checkers start up
Nov  6 23:26:00 node-1 cron[8618]: (CRON) INFO (Running @reboot jobs)
Nov  6 23:26:00 node-1 postfix/master[8755]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov  6 23:26:03 node-1 puppet-agent[8939]: Reopening log files
Nov  6 23:26:04 node-1 puppet-agent[8939]: Could not request certificate: Connection refused - connect(2)
Nov  6 23:26:17 node-1 puppet-user[9147]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov  6 23:26:17 node-1 puppet-user[9147]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov  6 23:26:19 node-1 puppet-user[9147]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov  6 23:26:19 node-1 puppet-user[9147]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov  6 23:26:19 node-1 puppet-user[9147]: Finished catalog run in 1.55 seconds
Nov  6 23:26:20 node-1 multipathd: uevent trigger error
Nov  6 23:26:20 node-1 puppet-user[9602]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  6 23:26:20 node-1 puppet-user[9602]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Nov  6 23:26:20 node-1 puppet-user[9602]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov  6 23:26:20 node-1 puppet-user[9602]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov  6 23:26:20 node-1 puppet-user[9602]: (/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"]'
Nov  6 23:26:20 node-1 puppet-user[9602]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov  6 23:26:20 node-1 puppet-user[9602]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov  6 23:26:20 node-1 puppet-user[9602]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov  6 23:26:20 node-1 puppet-user[9602]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov  6 23:26:20 node-1 puppet-user[9602]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov  6 23:26:20 node-1 puppet-user[9602]: Finished catalog run in 0.05 seconds
Nov  6 23:26:22 node-1 puppet-user[10077]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov  6 23:26:22 node-1 puppet-user[10077]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Nov  6 23:26:22 node-1 puppet-user[10077]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov  6 23:26:22 node-1 puppet-user[10077]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov  6 23:26:22 node-1 puppet-user[10077]: Finished catalog run in 0.04 seconds
Nov  6 23:26:23 node-1 puppet-user[10549]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov  6 23:26:23 node-1 puppet-user[10549]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov  6 23:26:24 node-1 puppet-user[10549]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov  6 23:26:24 node-1 puppet-user[10549]: Finished catalog run in 0.03 seconds
Nov  6 23:26:25 node-1 puppet-user[11194]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov  6 23:26:25 node-1 puppet-user[11194]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Nov  6 23:26:25 node-1 puppet-user[11194]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov  6 23:26:26 node-1 puppet-user[11194]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Nov  6 23:26:26 node-1 puppet-user[11194]: Finished catalog run in 0.45 seconds
Nov  6 23:26:27 node-1 puppet-user[11687]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov  6 23:26:27 node-1 puppet-user[11687]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Nov  6 23:26:27 node-1 puppet-user[11687]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Nov  6 23:26:27 node-1 puppet-user[11687]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov  6 23:26:27 node-1 puppet-user[11687]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov  6 23:26:27 node-1 puppet-user[11687]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov  6 23:26:27 node-1 puppet-user[11687]: Finished catalog run in 0.22 seconds
Nov  6 23:26:29 node-1 puppet-user[12168]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov  6 23:26:29 node-1 puppet-user[12168]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Nov  6 23:26:29 node-1 puppet-user[12168]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov  6 23:26:29 node-1 kernel: [   67.442430] nr_pdflush_threads exported in /proc is scheduled for removal
Nov  6 23:26:29 node-1 kernel: [   67.442479] 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.
Nov  6 23:26:29 node-1 puppet-user[12168]: (/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'
Nov  6 23:26:29 node-1 puppet-user[12168]: Finished catalog run in 0.05 seconds
Nov  6 23:26:31 node-1 puppet-user[12644]: (Scope(Class[main])) MODULAR: sync_time
Nov  6 23:26:31 node-1 puppet-user[12644]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov  6 23:26:31 node-1 ntpdate[13059]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov  6 23:26:35 node-1 kernel: [   74.001747] init: plymouth-upstart-bridge main process ended, respawning
Nov  6 23:26:36 node-1 puppet-agent[8939]: Could not run: SIGTERM
Nov  6 23:26:36 node-1 kernel: [   74.308815] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov  6 23:26:36 node-1 ec2: 
Nov  6 23:26:36 node-1 ec2: #############################################################
Nov  6 23:26:36 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov  6 23:26:36 node-1 ec2: 1024 d4:1e:69:e0:78:f7:74:7c:c7:f6:2c:04:d3:25:37:b5  root@node-1.domain.tld (DSA)
Nov  6 23:26:36 node-1 ec2: 256 74:b2:54:59:72:6d:b5:63:2e:5a:54:f3:7b:e1:74:2d  root@node-1.domain.tld (ECDSA)
Nov  6 23:26:36 node-1 ec2: 256 47:d4:9f:da:25:bd:49:2c:95:5a:cd:82:d9:a5:48:7b  root@node-1.domain.tld (ED25519)
Nov  6 23:26:36 node-1 ec2: 2048 0e:d5:dc:af:f3:b1:36:d3:45:04:a7:e1:11:94:30:5d  root@node-1.domain.tld (RSA)
Nov  6 23:26:36 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov  6 23:26:36 node-1 ec2: #############################################################
Nov  6 23:26:37 node-1 ntpdate[13059]: adjust time server 10.20.0.2 offset 0.000154 sec
Nov  6 23:26:37 node-1 puppet-user[12644]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov  6 23:26:37 node-1 puppet-user[12644]: Finished catalog run in 6.17 seconds
Nov  6 23:26:43 node-1 puppet-user[13447]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  6 23:26:43 node-1 puppet-user[13447]: Compiled catalog for node-1.domain.tld in environment production in 0.10 seconds
Nov  6 23:26:43 node-1 puppet-user[13447]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov  6 23:26:43 node-1 puppet-user[13447]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs"]'
Nov  6 23:26:43 node-1 puppet-user[13447]: Finished catalog run in 0.07 seconds
Nov  6 23:26:45 node-1 puppet-user[13909]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov  6 23:26:45 node-1 puppet-user[13909]: Compiled catalog for node-1.domain.tld in environment production in 0.48 seconds
Nov  6 23:26:45 node-1 puppet-user[13909]: (/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
Nov  6 23:26:45 node-1 puppet-user[13909]: (/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
Nov  6 23:26:45 node-1 puppet-user[13909]: (/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
Nov  6 23:26:45 node-1 puppet-user[13909]: (/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
Nov  6 23:26:45 node-1 puppet-user[13909]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov  6 23:26:45 node-1 puppet-user[13909]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Nov  6 23:26:45 node-1 puppet-user[13909]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov  6 23:26:45 node-1 puppet-user[13909]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Nov  6 23:26:45 node-1 puppet-user[13909]: (/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
Nov  6 23:26:45 node-1 puppet-user[13909]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Nov  6 23:26:46 node-1 puppet-user[13909]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov  6 23:26:46 node-1 puppet-user[13909]: Finished catalog run in 0.83 seconds
Nov  6 23:26:48 node-1 puppet-user[14423]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov  6 23:26:48 node-1 puppet-user[14423]: Compiled catalog for node-1.domain.tld in environment production in 0.13 seconds
Nov  6 23:26:51 node-1 puppet-user[14423]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov  6 23:27:01 node-1 CRON[15942]: (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")
Nov  6 23:27:18 node-1 puppet-user[14423]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov  6 23:27:18 node-1 puppet-user[14423]: Finished catalog run in 29.95 seconds
Nov  6 23:27:20 node-1 puppet-user[16897]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov  6 23:27:21 node-1 puppet-user[16897]: Compiled catalog for node-1.domain.tld in environment production in 0.62 seconds
Nov  6 23:27:21 node-1 puppet-user[16897]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov  6 23:27:21 node-1 puppet-user[16897]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov  6 23:27:21 node-1 puppet-user[16897]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov  6 23:27:21 node-1 puppet-user[16897]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov  6 23:27:21 node-1 puppet-user[16897]: Finished catalog run in 0.09 seconds
Nov  6 23:27:22 node-1 puppet-user[17364]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov  6 23:27:23 node-1 puppet-user[17364]: Compiled catalog for node-1.domain.tld in environment production in 0.87 seconds
Nov  6 23:27:24 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov  6 23:27:24 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov  6 23:27:24 node-1 crontab[17813]: (root) LIST (root)
Nov  6 23:27:24 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov  6 23:27:24 node-1 crontab[17814]: (root) REPLACE (root)
Nov  6 23:27:25 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/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
Nov  6 23:27:26 node-1 puppet-user[17364]: (/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
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/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
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/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
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/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
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/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
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov  6 23:27:26 node-1 puppet-user[17364]: (/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
Nov  6 23:27:26 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov  6 23:27:27 node-1 puppet-user[17364]: (/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
Nov  6 23:27:27 node-1 puppet-user[17364]: (/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
Nov  6 23:27:27 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov  6 23:27:27 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov  6 23:27:27 node-1 puppet-user[17364]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Nov  6 23:27:27 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8390" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  6 23:27:27 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov  6 23:27:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:41 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:41 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:41 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:41 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:41 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:41 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:27:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:28:33 node-1 ntpdate[28620]: no servers can be used, exiting
<27>Nov  6 23:28:33 node-1 ntpdate[28781]: no servers can be used, exiting
<27>Nov  6 23:28:33 node-1 ntpdate[28989]: no servers can be used, exiting
<27>Nov  6 23:29:05 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:05 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:05 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:05 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:05 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:05 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:08 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:08 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:08 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:08 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:08 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:21 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:21 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:21 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:21 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:21 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:24 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:24 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:24 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:24 node-1 multipathd: uevent trigger error
<27>Nov  6 23:29:24 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:18 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:18 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:18 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:18 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:18 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:18 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:19 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:29 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  6 23:30:29 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  6 23:30:35 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  6 23:30:35 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  6 23:30:41 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  6 23:30:46 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  6 23:30:46 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  6 23:30:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:54 node-1 multipathd: uevent trigger error
<27>Nov  6 23:30:54 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:03 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:03 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:03 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:03 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:03 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:17 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:17 node-1 multipathd: uevent trigger error
<129>Nov  6 23:31:18 node-1 haproxy[18884]: 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>Nov  6 23:31:19 node-1 haproxy[18888]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:20 node-1 haproxy[18888]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:20 node-1 haproxy[18888]: proxy mysqld has no server available!
<27>Nov  6 23:31:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:25 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:25 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:25 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:25 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:25 node-1 multipathd: uevent trigger error
<129>Nov  6 23:31:28 node-1 haproxy[21786]: 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>Nov  6 23:31:28 node-1 haproxy[21786]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:28 node-1 haproxy[21786]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:28 node-1 haproxy[21786]: proxy mysqld has no server available!
<129>Nov  6 23:31:29 node-1 haproxy[21790]: 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>Nov  6 23:31:29 node-1 haproxy[21790]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:29 node-1 haproxy[21790]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:29 node-1 haproxy[21790]: proxy object-storage has no server available!
<27>Nov  6 23:31:31 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:31 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:31 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:31 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:31 node-1 multipathd: uevent trigger error
<129>Nov  6 23:31:33 node-1 haproxy[23170]: 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>Nov  6 23:31:33 node-1 haproxy[23170]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:34 node-1 haproxy[23174]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:34 node-1 haproxy[23174]: proxy neutron has no server available!
<129>Nov  6 23:31:34 node-1 haproxy[23174]: 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>Nov  6 23:31:34 node-1 haproxy[23174]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:34 node-1 haproxy[23174]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:34 node-1 haproxy[23174]: proxy mysqld has no server available!
<129>Nov  6 23:31:34 node-1 haproxy[23174]: 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>Nov  6 23:31:35 node-1 haproxy[23174]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:35 node-1 haproxy[23174]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:35 node-1 haproxy[23174]: proxy object-storage has no server available!
<27>Nov  6 23:31:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:36 node-1 multipathd: uevent trigger error
<129>Nov  6 23:31:39 node-1 haproxy[24630]: 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>Nov  6 23:31:39 node-1 haproxy[24630]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:39 node-1 haproxy[24630]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:39 node-1 haproxy[24630]: proxy keystone-1 has no server available!
<129>Nov  6 23:31:39 node-1 haproxy[24630]: 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>Nov  6 23:31:39 node-1 haproxy[24630]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:40 node-1 haproxy[24634]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:40 node-1 haproxy[24634]: proxy keystone-2 has no server available!
<129>Nov  6 23:31:40 node-1 haproxy[24634]: 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>Nov  6 23:31:40 node-1 haproxy[24634]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:40 node-1 haproxy[24634]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:40 node-1 haproxy[24634]: proxy neutron has no server available!
<129>Nov  6 23:31:40 node-1 haproxy[24634]: 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>Nov  6 23:31:40 node-1 haproxy[24634]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:40 node-1 haproxy[24634]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:40 node-1 haproxy[24634]: proxy mysqld has no server available!
<129>Nov  6 23:31:40 node-1 haproxy[24634]: 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>Nov  6 23:31:41 node-1 haproxy[24634]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:41 node-1 haproxy[24634]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:41 node-1 haproxy[24634]: proxy object-storage has no server available!
<27>Nov  6 23:31:42 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:42 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:42 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:42 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:42 node-1 multipathd: uevent trigger error
<129>Nov  6 23:31:44 node-1 haproxy[26100]: 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>Nov  6 23:31:44 node-1 haproxy[26100]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:45 node-1 haproxy[26106]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:45 node-1 haproxy[26106]: proxy keystone-1 has no server available!
<129>Nov  6 23:31:45 node-1 haproxy[26106]: 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>Nov  6 23:31:45 node-1 haproxy[26106]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:45 node-1 haproxy[26106]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:45 node-1 haproxy[26106]: proxy keystone-2 has no server available!
<129>Nov  6 23:31:45 node-1 haproxy[26106]: 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>Nov  6 23:31:45 node-1 haproxy[26106]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:45 node-1 haproxy[26106]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:45 node-1 haproxy[26106]: proxy neutron has no server available!
<129>Nov  6 23:31:45 node-1 haproxy[26106]: 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>Nov  6 23:31:45 node-1 haproxy[26106]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:46 node-1 haproxy[26106]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:46 node-1 haproxy[26106]: proxy mysqld has no server available!
<129>Nov  6 23:31:46 node-1 haproxy[26106]: 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>Nov  6 23:31:46 node-1 haproxy[26106]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:46 node-1 haproxy[26106]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:46 node-1 haproxy[26106]: proxy object-storage has no server available!
<129>Nov  6 23:31:46 node-1 haproxy[26106]: 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>Nov  6 23:31:46 node-1 haproxy[26106]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:46 node-1 haproxy[26106]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:46 node-1 haproxy[26106]: proxy aodh has no server available!
<27>Nov  6 23:31:48 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:48 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:48 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:48 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:48 node-1 multipathd: uevent trigger error
<129>Nov  6 23:31:50 node-1 haproxy[27499]: 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>Nov  6 23:31:50 node-1 haproxy[27499]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:50 node-1 haproxy[27499]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:50 node-1 haproxy[27499]: proxy keystone-1 has no server available!
<129>Nov  6 23:31:50 node-1 haproxy[27499]: 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>Nov  6 23:31:50 node-1 haproxy[27499]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:50 node-1 haproxy[27499]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:50 node-1 haproxy[27499]: proxy keystone-2 has no server available!
<129>Nov  6 23:31:51 node-1 haproxy[27503]: 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>Nov  6 23:31:51 node-1 haproxy[27503]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:51 node-1 haproxy[27503]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:51 node-1 haproxy[27503]: proxy neutron has no server available!
<129>Nov  6 23:31:51 node-1 haproxy[27503]: 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>Nov  6 23:31:51 node-1 haproxy[27503]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:51 node-1 haproxy[27503]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:51 node-1 haproxy[27503]: proxy mysqld has no server available!
<129>Nov  6 23:31:51 node-1 haproxy[27503]: 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>Nov  6 23:31:51 node-1 haproxy[27503]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:51 node-1 haproxy[27503]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:51 node-1 haproxy[27503]: proxy object-storage has no server available!
<129>Nov  6 23:31:51 node-1 haproxy[27503]: 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>Nov  6 23:31:52 node-1 haproxy[27503]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:52 node-1 haproxy[27503]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:52 node-1 haproxy[27503]: proxy aodh has no server available!
<129>Nov  6 23:31:52 node-1 haproxy[27503]: 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>Nov  6 23:31:52 node-1 haproxy[27503]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:52 node-1 haproxy[27503]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:52 node-1 haproxy[27503]: proxy ceilometer has no server available!
<27>Nov  6 23:31:54 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:54 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:54 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:54 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:54 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:54 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:54 node-1 multipathd: uevent trigger error
<129>Nov  6 23:31:56 node-1 haproxy[28908]: 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>Nov  6 23:31:56 node-1 haproxy[28908]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:56 node-1 haproxy[28908]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:56 node-1 haproxy[28908]: proxy keystone-1 has no server available!
<129>Nov  6 23:31:56 node-1 haproxy[28908]: 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>Nov  6 23:31:56 node-1 haproxy[28908]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:56 node-1 haproxy[28908]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:56 node-1 haproxy[28908]: proxy keystone-2 has no server available!
<129>Nov  6 23:31:56 node-1 haproxy[28908]: 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>Nov  6 23:31:56 node-1 haproxy[28908]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:56 node-1 haproxy[28908]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:56 node-1 haproxy[28908]: proxy neutron has no server available!
<129>Nov  6 23:31:56 node-1 haproxy[28908]: 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>Nov  6 23:31:57 node-1 haproxy[28912]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:57 node-1 haproxy[28912]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:57 node-1 haproxy[28912]: proxy mysqld has no server available!
<129>Nov  6 23:31:57 node-1 haproxy[28912]: 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>Nov  6 23:31:57 node-1 haproxy[28912]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:57 node-1 haproxy[28912]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:57 node-1 haproxy[28912]: proxy object-storage has no server available!
<129>Nov  6 23:31:57 node-1 haproxy[28912]: 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>Nov  6 23:31:57 node-1 haproxy[28912]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:57 node-1 haproxy[28912]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:57 node-1 haproxy[28912]: proxy aodh has no server available!
<129>Nov  6 23:31:57 node-1 haproxy[28912]: 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>Nov  6 23:31:57 node-1 haproxy[28912]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:31:58 node-1 haproxy[28912]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:31:58 node-1 haproxy[28912]: proxy ceilometer has no server available!
<27>Nov  6 23:31:59 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:59 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:59 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:59 node-1 multipathd: uevent trigger error
<27>Nov  6 23:31:59 node-1 multipathd: uevent trigger error
<129>Nov  6 23:32:01 node-1 haproxy[30374]: 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>Nov  6 23:32:01 node-1 haproxy[30374]: 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>Nov  6 23:32:01 node-1 haproxy[30374]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:01 node-1 haproxy[30374]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:01 node-1 haproxy[30374]: proxy keystone-1 has no server available!
<129>Nov  6 23:32:02 node-1 haproxy[30405]: 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>Nov  6 23:32:02 node-1 haproxy[30405]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:02 node-1 haproxy[30405]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:02 node-1 haproxy[30405]: proxy keystone-2 has no server available!
<129>Nov  6 23:32:02 node-1 haproxy[30405]: 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>Nov  6 23:32:02 node-1 haproxy[30405]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:02 node-1 haproxy[30405]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:02 node-1 haproxy[30405]: proxy neutron has no server available!
<129>Nov  6 23:32:02 node-1 haproxy[30405]: 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>Nov  6 23:32:02 node-1 haproxy[30405]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:02 node-1 haproxy[30405]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:02 node-1 haproxy[30405]: proxy mysqld has no server available!
<129>Nov  6 23:32:02 node-1 haproxy[30405]: 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>Nov  6 23:32:02 node-1 haproxy[30405]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:02 node-1 haproxy[30405]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:02 node-1 haproxy[30405]: proxy object-storage has no server available!
<129>Nov  6 23:32:03 node-1 haproxy[30405]: 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>Nov  6 23:32:03 node-1 haproxy[30405]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:03 node-1 haproxy[30405]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:03 node-1 haproxy[30405]: proxy aodh has no server available!
<129>Nov  6 23:32:03 node-1 haproxy[30405]: 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>Nov  6 23:32:03 node-1 haproxy[30405]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:03 node-1 haproxy[30405]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:03 node-1 haproxy[30405]: proxy ceilometer has no server available!
<27>Nov  6 23:32:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:04 node-1 multipathd: uevent trigger error
<129>Nov  6 23:32:07 node-1 haproxy[31904]: 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>Nov  6 23:32:07 node-1 haproxy[31904]: 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>Nov  6 23:32:07 node-1 haproxy[31904]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:07 node-1 haproxy[31904]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:07 node-1 haproxy[31904]: proxy keystone-1 has no server available!
<129>Nov  6 23:32:07 node-1 haproxy[31904]: 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>Nov  6 23:32:07 node-1 haproxy[31904]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:07 node-1 haproxy[31904]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:07 node-1 haproxy[31904]: proxy keystone-2 has no server available!
<129>Nov  6 23:32:07 node-1 haproxy[31904]: 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>Nov  6 23:32:07 node-1 haproxy[31904]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:08 node-1 haproxy[31908]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:08 node-1 haproxy[31908]: proxy glance-api has no server available!
<129>Nov  6 23:32:08 node-1 haproxy[31908]: 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>Nov  6 23:32:08 node-1 haproxy[31908]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:08 node-1 haproxy[31908]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:08 node-1 haproxy[31908]: proxy glance-glare has no server available!
<129>Nov  6 23:32:08 node-1 haproxy[31908]: 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>Nov  6 23:32:08 node-1 haproxy[31908]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:08 node-1 haproxy[31908]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:08 node-1 haproxy[31908]: proxy neutron has no server available!
<129>Nov  6 23:32:08 node-1 haproxy[31908]: 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>Nov  6 23:32:08 node-1 haproxy[31908]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:08 node-1 haproxy[31908]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:08 node-1 haproxy[31908]: proxy glance-registry has no server available!
<129>Nov  6 23:32:08 node-1 haproxy[31908]: 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>Nov  6 23:32:08 node-1 haproxy[31908]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:08 node-1 haproxy[31908]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:08 node-1 haproxy[31908]: proxy mysqld has no server available!
<129>Nov  6 23:32:08 node-1 haproxy[31908]: 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>Nov  6 23:32:08 node-1 haproxy[31908]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:08 node-1 haproxy[31908]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:08 node-1 haproxy[31908]: proxy object-storage has no server available!
<129>Nov  6 23:32:09 node-1 haproxy[31908]: 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>Nov  6 23:32:09 node-1 haproxy[31908]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:09 node-1 haproxy[31908]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:09 node-1 haproxy[31908]: proxy aodh has no server available!
<129>Nov  6 23:32:09 node-1 haproxy[31908]: 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>Nov  6 23:32:09 node-1 haproxy[31908]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:09 node-1 haproxy[31908]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:09 node-1 haproxy[31908]: proxy ceilometer has no server available!
<27>Nov  6 23:32:10 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:10 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:10 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:10 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:10 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:10 node-1 multipathd: uevent trigger error
<129>Nov  6 23:32:13 node-1 haproxy[946]: 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>Nov  6 23:32:13 node-1 haproxy[946]: 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>Nov  6 23:32:13 node-1 haproxy[946]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:13 node-1 haproxy[946]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:13 node-1 haproxy[946]: proxy keystone-1 has no server available!
<129>Nov  6 23:32:13 node-1 haproxy[946]: 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>Nov  6 23:32:13 node-1 haproxy[946]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:13 node-1 haproxy[946]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:13 node-1 haproxy[946]: proxy keystone-2 has no server available!
<129>Nov  6 23:32:13 node-1 haproxy[946]: 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>Nov  6 23:32:13 node-1 haproxy[946]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:13 node-1 haproxy[946]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:13 node-1 haproxy[946]: proxy nova-api has no server available!
<129>Nov  6 23:32:13 node-1 haproxy[946]: 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>Nov  6 23:32:13 node-1 haproxy[946]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:14 node-1 haproxy[953]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:14 node-1 haproxy[953]: proxy nova-metadata-api has no server available!
<129>Nov  6 23:32:14 node-1 haproxy[953]: 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>Nov  6 23:32:14 node-1 haproxy[953]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:14 node-1 haproxy[953]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:14 node-1 haproxy[953]: proxy glance-api has no server available!
<129>Nov  6 23:32:14 node-1 haproxy[953]: 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>Nov  6 23:32:14 node-1 haproxy[953]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:14 node-1 haproxy[953]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:14 node-1 haproxy[953]: proxy glance-glare has no server available!
<129>Nov  6 23:32:14 node-1 haproxy[953]: 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>Nov  6 23:32:14 node-1 haproxy[953]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:14 node-1 haproxy[953]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:14 node-1 haproxy[953]: proxy neutron has no server available!
<129>Nov  6 23:32:14 node-1 haproxy[953]: 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>Nov  6 23:32:14 node-1 haproxy[953]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:14 node-1 haproxy[953]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:14 node-1 haproxy[953]: proxy glance-registry has no server available!
<129>Nov  6 23:32:14 node-1 haproxy[953]: 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>Nov  6 23:32:14 node-1 haproxy[953]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:14 node-1 haproxy[953]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:14 node-1 haproxy[953]: proxy mysqld has no server available!
<129>Nov  6 23:32:14 node-1 haproxy[953]: 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>Nov  6 23:32:14 node-1 haproxy[953]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:14 node-1 haproxy[953]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:14 node-1 haproxy[953]: proxy object-storage has no server available!
<129>Nov  6 23:32:14 node-1 haproxy[953]: 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>Nov  6 23:32:14 node-1 haproxy[953]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:15 node-1 haproxy[953]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:15 node-1 haproxy[953]: proxy aodh has no server available!
<129>Nov  6 23:32:15 node-1 haproxy[953]: 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>Nov  6 23:32:15 node-1 haproxy[953]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:15 node-1 haproxy[953]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:15 node-1 haproxy[953]: proxy ceilometer has no server available!
<129>Nov  6 23:32:15 node-1 haproxy[953]: 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>Nov  6 23:32:15 node-1 haproxy[953]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:15 node-1 haproxy[953]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:15 node-1 haproxy[953]: proxy nova-novncproxy has no server available!
<27>Nov  6 23:32:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:16 node-1 multipathd: uevent trigger error
<129>Nov  6 23:32:18 node-1 haproxy[2527]: 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>Nov  6 23:32:19 node-1 haproxy[2531]: 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>Nov  6 23:32:19 node-1 haproxy[2531]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:19 node-1 haproxy[2531]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:19 node-1 haproxy[2531]: proxy keystone-1 has no server available!
<129>Nov  6 23:32:19 node-1 haproxy[2531]: 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>Nov  6 23:32:19 node-1 haproxy[2531]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:19 node-1 haproxy[2531]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:19 node-1 haproxy[2531]: proxy keystone-2 has no server available!
<129>Nov  6 23:32:19 node-1 haproxy[2531]: 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>Nov  6 23:32:19 node-1 haproxy[2531]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:19 node-1 haproxy[2531]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:19 node-1 haproxy[2531]: proxy nova-api has no server available!
<129>Nov  6 23:32:19 node-1 haproxy[2531]: 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>Nov  6 23:32:19 node-1 haproxy[2531]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:19 node-1 haproxy[2531]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:19 node-1 haproxy[2531]: proxy nova-metadata-api has no server available!
<129>Nov  6 23:32:19 node-1 haproxy[2531]: 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>Nov  6 23:32:19 node-1 haproxy[2531]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:19 node-1 haproxy[2531]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:19 node-1 haproxy[2531]: proxy cinder-api has no server available!
<129>Nov  6 23:32:19 node-1 haproxy[2531]: 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>Nov  6 23:32:19 node-1 haproxy[2531]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:19 node-1 haproxy[2531]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:19 node-1 haproxy[2531]: proxy glance-api has no server available!
<129>Nov  6 23:32:19 node-1 haproxy[2531]: 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>Nov  6 23:32:19 node-1 haproxy[2531]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:19 node-1 haproxy[2531]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:19 node-1 haproxy[2531]: proxy glance-glare has no server available!
<129>Nov  6 23:32:20 node-1 haproxy[2531]: 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>Nov  6 23:32:20 node-1 haproxy[2531]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:20 node-1 haproxy[2531]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:20 node-1 haproxy[2531]: proxy neutron has no server available!
<129>Nov  6 23:32:20 node-1 haproxy[2531]: 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>Nov  6 23:32:20 node-1 haproxy[2531]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:20 node-1 haproxy[2531]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:20 node-1 haproxy[2531]: proxy glance-registry has no server available!
<129>Nov  6 23:32:20 node-1 haproxy[2531]: 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>Nov  6 23:32:20 node-1 haproxy[2531]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:20 node-1 haproxy[2531]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:20 node-1 haproxy[2531]: proxy mysqld has no server available!
<129>Nov  6 23:32:20 node-1 haproxy[2531]: 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>Nov  6 23:32:20 node-1 haproxy[2531]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:20 node-1 haproxy[2531]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:20 node-1 haproxy[2531]: proxy object-storage has no server available!
<129>Nov  6 23:32:20 node-1 haproxy[2531]: 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>Nov  6 23:32:20 node-1 haproxy[2531]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:20 node-1 haproxy[2531]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:20 node-1 haproxy[2531]: proxy aodh has no server available!
<129>Nov  6 23:32:20 node-1 haproxy[2531]: 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>Nov  6 23:32:20 node-1 haproxy[2531]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:20 node-1 haproxy[2531]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:20 node-1 haproxy[2531]: proxy ceilometer has no server available!
<129>Nov  6 23:32:20 node-1 haproxy[2531]: 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>Nov  6 23:32:20 node-1 haproxy[2531]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:20 node-1 haproxy[2531]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:20 node-1 haproxy[2531]: proxy nova-novncproxy has no server available!
<27>Nov  6 23:32:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:22 node-1 multipathd: uevent trigger error
<129>Nov  6 23:32:24 node-1 haproxy[3977]: 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>Nov  6 23:32:25 node-1 haproxy[3986]: 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>Nov  6 23:32:25 node-1 haproxy[3986]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:25 node-1 haproxy[3986]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:25 node-1 haproxy[3986]: proxy keystone-1 has no server available!
<129>Nov  6 23:32:25 node-1 haproxy[3986]: 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>Nov  6 23:32:25 node-1 haproxy[3986]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:25 node-1 haproxy[3986]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:25 node-1 haproxy[3986]: proxy keystone-2 has no server available!
<129>Nov  6 23:32:25 node-1 haproxy[3986]: 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>Nov  6 23:32:25 node-1 haproxy[3986]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:25 node-1 haproxy[3986]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:25 node-1 haproxy[3986]: proxy nova-api has no server available!
<129>Nov  6 23:32:25 node-1 haproxy[3986]: 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>Nov  6 23:32:25 node-1 haproxy[3986]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:25 node-1 haproxy[3986]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:25 node-1 haproxy[3986]: proxy nova-metadata-api has no server available!
<129>Nov  6 23:32:25 node-1 haproxy[3986]: 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>Nov  6 23:32:25 node-1 haproxy[3986]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:25 node-1 haproxy[3986]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:25 node-1 haproxy[3986]: proxy cinder-api has no server available!
<129>Nov  6 23:32:25 node-1 haproxy[3986]: 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>Nov  6 23:32:25 node-1 haproxy[3986]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:25 node-1 haproxy[3986]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:25 node-1 haproxy[3986]: proxy glance-api has no server available!
<129>Nov  6 23:32:25 node-1 haproxy[3986]: 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>Nov  6 23:32:25 node-1 haproxy[3986]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:25 node-1 haproxy[3986]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:25 node-1 haproxy[3986]: proxy glance-glare has no server available!
<129>Nov  6 23:32:25 node-1 haproxy[3986]: 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>Nov  6 23:32:25 node-1 haproxy[3986]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:25 node-1 haproxy[3986]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:25 node-1 haproxy[3986]: proxy neutron has no server available!
<129>Nov  6 23:32:25 node-1 haproxy[3986]: 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>Nov  6 23:32:26 node-1 haproxy[3986]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:26 node-1 haproxy[3986]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:26 node-1 haproxy[3986]: proxy glance-registry has no server available!
<129>Nov  6 23:32:26 node-1 haproxy[3986]: 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>Nov  6 23:32:26 node-1 haproxy[3986]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:26 node-1 haproxy[3986]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:26 node-1 haproxy[3986]: proxy mysqld has no server available!
<129>Nov  6 23:32:26 node-1 haproxy[3986]: 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>Nov  6 23:32:26 node-1 haproxy[3986]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:26 node-1 haproxy[3986]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:26 node-1 haproxy[3986]: proxy object-storage has no server available!
<129>Nov  6 23:32:26 node-1 haproxy[3986]: 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>Nov  6 23:32:26 node-1 haproxy[3986]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:26 node-1 haproxy[3986]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:26 node-1 haproxy[3986]: proxy aodh has no server available!
<129>Nov  6 23:32:26 node-1 haproxy[3986]: 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>Nov  6 23:32:26 node-1 haproxy[3986]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:26 node-1 haproxy[3986]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:26 node-1 haproxy[3986]: proxy ceilometer has no server available!
<129>Nov  6 23:32:26 node-1 haproxy[3986]: 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>Nov  6 23:32:26 node-1 haproxy[3986]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:26 node-1 haproxy[3986]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:26 node-1 haproxy[3986]: proxy heat-api has no server available!
<129>Nov  6 23:32:26 node-1 haproxy[3986]: 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>Nov  6 23:32:26 node-1 haproxy[3986]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:26 node-1 haproxy[3986]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:26 node-1 haproxy[3986]: proxy heat-api-cfn has no server available!
<129>Nov  6 23:32:26 node-1 haproxy[3986]: 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>Nov  6 23:32:26 node-1 haproxy[3986]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:26 node-1 haproxy[3986]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:26 node-1 haproxy[3986]: proxy heat-api-cloudwatch has no server available!
<129>Nov  6 23:32:26 node-1 haproxy[3986]: 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>Nov  6 23:32:26 node-1 haproxy[3986]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  6 23:32:26 node-1 haproxy[3986]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  6 23:32:26 node-1 haproxy[3986]: proxy nova-novncproxy has no server available!
<27>Nov  6 23:32:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:31 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:31 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:31 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:31 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:31 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:31 node-1 multipathd: uevent trigger error
<27>Nov  6 23:32:39 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov  6 23:32:58 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  6 23:33:03 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>Nov  6 23:33:05 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov  6 23:33:28 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  6 23:33:51 node-1 multipathd: uevent trigger error
<27>Nov  6 23:33:51 node-1 multipathd: uevent trigger error
<27>Nov  6 23:33:51 node-1 multipathd: uevent trigger error
<27>Nov  6 23:33:51 node-1 multipathd: uevent trigger error
<27>Nov  6 23:33:51 node-1 multipathd: uevent trigger error
<27>Nov  6 23:35:39 node-1 multipathd: uevent trigger error
<27>Nov  6 23:35:39 node-1 multipathd: uevent trigger error
<27>Nov  6 23:35:39 node-1 multipathd: uevent trigger error
<27>Nov  6 23:35:39 node-1 multipathd: uevent trigger error
<27>Nov  6 23:35:39 node-1 multipathd: uevent trigger error
<27>Nov  6 23:35:45 node-1 multipathd: uevent trigger error
<27>Nov  6 23:35:45 node-1 multipathd: uevent trigger error
<27>Nov  6 23:35:45 node-1 multipathd: uevent trigger error
<27>Nov  6 23:35:45 node-1 multipathd: uevent trigger error
<43>Nov  6 23:35:57 node-1 apache2_error [Sun Nov 06 23:35:55.804853 2016] [mpm_event:notice] [pid 9148:tid 140336052737920] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  6 23:35:57 node-1 apache2_error [Sun Nov 06 23:35:55.804994 2016] [core:notice] [pid 9148:tid 140336052737920] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  6 23:36:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  6 23:36:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:04 node-1 multipathd: uevent trigger error
<43>Nov  6 23:36:07 node-1 apache2_error [Sun Nov 06 23:35:58.784707 2016] [mpm_event:notice] [pid 9148:tid 140336052737920] AH00491: caught SIGTERM, shutting down
<43>Nov  6 23:36:07 node-1 apache2_error [Sun Nov 06 23:35:59.863147 2016] [mpm_worker:notice] [pid 9516:tid 140552706574208] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  6 23:36:07 node-1 apache2_error [Sun Nov 06 23:35:59.863189 2016] [core:notice] [pid 9516:tid 140552706574208] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  6 23:36:08 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:08 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:08 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:08 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:08 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:53 node-1 multipathd: uevent trigger error
<43>Nov  6 23:36:58 node-1 apache2_error [Sun Nov 06 23:36:49.615737 2016] [mpm_worker:notice] [pid 9516:tid 140552706574208] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  6 23:36:58 node-1 apache2_error [Sun Nov 06 23:36:49.618837 2016] [mpm_worker:warn] [pid 9516:tid 140552706574208] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  6 23:36:58 node-1 apache2_error [Sun Nov 06 23:36:49.619250 2016] [mpm_worker:notice] [pid 9516:tid 140552706574208] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  6 23:36:58 node-1 apache2_error [Sun Nov 06 23:36:49.619258 2016] [core:notice] [pid 9516:tid 140552706574208] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  6 23:36:58 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:58 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:58 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:58 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:58 node-1 multipathd: uevent trigger error
<27>Nov  6 23:36:58 node-1 multipathd: uevent trigger error
<43>Nov  6 23:38:08 node-1 apache2_error [Sun Nov 06 23:38:01.237855 2016] [mpm_worker:notice] [pid 9516:tid 140552706574208] AH00295: caught SIGTERM, shutting down
<43>Nov  6 23:38:08 node-1 apache2_error [Sun Nov 06 23:38:01.982802 2016] [mpm_worker:notice] [pid 30458:tid 139760952317824] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  6 23:38:08 node-1 apache2_error [Sun Nov 06 23:38:01.982842 2016] [core:notice] [pid 30458:tid 139760952317824] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  6 23:38:48 node-1 apache2_error [Sun Nov 06 23:38:46.346817 2016] [mpm_worker:notice] [pid 30458:tid 139760952317824] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  6 23:38:48 node-1 apache2_error [Sun Nov 06 23:38:46.356583 2016] [mpm_worker:warn] [pid 30458:tid 139760952317824] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  6 23:38:48 node-1 apache2_error [Sun Nov 06 23:38:46.362765 2016] [mpm_worker:notice] [pid 30458:tid 139760952317824] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  6 23:38:48 node-1 apache2_error [Sun Nov 06 23:38:46.362806 2016] [core:notice] [pid 30458:tid 139760952317824] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  6 23:39:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  6 23:40:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:28 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:57 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:57 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:57 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:57 node-1 multipathd: uevent trigger error
<27>Nov  6 23:40:57 node-1 multipathd: uevent trigger error
<27>Nov  6 23:41:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:41:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:41:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:41:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:41:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:42:00 node-1 multipathd: uevent trigger error
<27>Nov  6 23:42:00 node-1 multipathd: uevent trigger error
<27>Nov  6 23:42:00 node-1 multipathd: uevent trigger error
<27>Nov  6 23:42:00 node-1 multipathd: uevent trigger error
<27>Nov  6 23:42:00 node-1 multipathd: uevent trigger error
<27>Nov  6 23:42:03 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  6 23:43:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:43:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:43:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:43:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:43:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:03 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:03 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:03 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:03 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:03 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:29 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:35 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:35 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:35 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:35 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:35 node-1 multipathd: uevent trigger error
<27>Nov  6 23:44:35 node-1 multipathd: uevent trigger error
<27>Nov  6 23:45:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  6 23:46:55 node-1 multipathd: uevent trigger error
<27>Nov  6 23:46:55 node-1 multipathd: uevent trigger error
<27>Nov  6 23:46:55 node-1 multipathd: uevent trigger error
<27>Nov  6 23:46:55 node-1 multipathd: uevent trigger error
<27>Nov  6 23:46:55 node-1 multipathd: uevent trigger error
<27>Nov  6 23:46:55 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:14 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:14 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:14 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:14 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:14 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:14 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:19 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:19 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:19 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:19 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:19 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:19 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:19 node-1 multipathd: uevent trigger error
<27>Nov  6 23:47:19 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:00 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:00 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:00 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:00 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:00 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  6 23:48:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:48:27 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:13 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:13 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:13 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:13 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:13 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:13 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:13 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:20 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Interface
<27>Nov  6 23:49:20 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-prv" in table Port
<27>Nov  6 23:49:20 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-prv" in table Port
<27>Nov  6 23:49:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Nov  6 23:49:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Nov  6 23:49:21 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Nov  6 23:49:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:22 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:36 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:50 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:50 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:50 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:50 node-1 multipathd: uevent trigger error
<27>Nov  6 23:49:50 node-1 multipathd: uevent trigger error
<27>Nov  6 23:50:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:50:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:50:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:50:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:50:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:50:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:50:07 node-1 multipathd: uevent trigger error
<27>Nov  6 23:51:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  6 23:52:25 node-1 multipathd: uevent trigger error
<27>Nov  6 23:52:25 node-1 multipathd: uevent trigger error
<27>Nov  6 23:52:25 node-1 multipathd: uevent trigger error
<27>Nov  6 23:52:25 node-1 multipathd: uevent trigger error
<27>Nov  6 23:52:25 node-1 multipathd: uevent trigger error
<27>Nov  6 23:52:37 node-1 multipathd: uevent trigger error
<27>Nov  6 23:52:38 node-1 multipathd: uevent trigger error
<27>Nov  6 23:52:38 node-1 multipathd: uevent trigger error
<27>Nov  6 23:53:01 node-1 multipathd: uevent trigger error
<27>Nov  6 23:53:01 node-1 multipathd: uevent trigger error
<27>Nov  6 23:53:01 node-1 multipathd: uevent trigger error
<27>Nov  6 23:53:01 node-1 multipathd: uevent trigger error
<27>Nov  6 23:53:01 node-1 multipathd: uevent trigger error
<27>Nov  6 23:53:01 node-1 multipathd: uevent trigger error
<27>Nov  6 23:53:02 node-1 multipathd: sda: spurious uevent, path already in pathvec
<27>Nov  6 23:54:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:06 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  6 23:54:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:12 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:49 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:49 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:49 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:49 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:49 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:49 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:53 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:57 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:57 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:57 node-1 multipathd: uevent trigger error
<27>Nov  6 23:54:57 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:09 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:09 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:09 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:09 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:09 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:15 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:15 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:15 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:16 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:40 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:40 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:40 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:40 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:40 node-1 multipathd: uevent trigger error
<27>Nov  6 23:55:40 node-1 multipathd: uevent trigger error
<27>Nov  6 23:56:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:56:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:56:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:56:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:56:44 node-1 multipathd: uevent trigger error
<27>Nov  6 23:56:59 node-1 multipathd: uevent trigger error
<27>Nov  6 23:56:59 node-1 multipathd: uevent trigger error
<27>Nov  6 23:56:59 node-1 multipathd: uevent trigger error
<27>Nov  6 23:56:59 node-1 multipathd: uevent trigger error
<11>Nov  6 23:57:11 node-1 liberasurecode[87379]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:11 node-1 liberasurecode[87379]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:11 node-1 liberasurecode[87379]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:11 node-1 liberasurecode[87379]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:11 node-1 liberasurecode[87422]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:11 node-1 liberasurecode[87422]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:11 node-1 liberasurecode[87422]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:11 node-1 liberasurecode[87422]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  6 23:57:12 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Nov  6 23:57:13 node-1 liberasurecode[87899]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:13 node-1 liberasurecode[87899]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:13 node-1 liberasurecode[87899]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:13 node-1 liberasurecode[87899]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:17 node-1 liberasurecode[88484]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:17 node-1 liberasurecode[88484]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:17 node-1 liberasurecode[88484]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:17 node-1 liberasurecode[88484]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88525]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88525]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88525]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88525]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88591]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88591]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88591]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88591]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88673]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88673]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88673]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88673]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88685]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88685]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88685]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88685]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88697]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88697]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88697]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88697]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88739]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88739]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88739]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:18 node-1 liberasurecode[88739]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:27 node-1 liberasurecode[89365]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:27 node-1 liberasurecode[89365]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:27 node-1 liberasurecode[89365]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  6 23:57:27 node-1 liberasurecode[89365]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  6 23:57:35 node-1 multipathd: uevent trigger error
<27>Nov  6 23:57:35 node-1 multipathd: uevent trigger error
<27>Nov  6 23:57:35 node-1 multipathd: uevent trigger error
<27>Nov  6 23:57:35 node-1 multipathd: uevent trigger error
<27>Nov  6 23:57:35 node-1 multipathd: uevent trigger error
<43>Nov  6 23:58:29 node-1 apache2_error [Sun Nov 06 23:58:23.111670 2016] [mpm_worker:notice] [pid 30458:tid 139760952317824] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  6 23:58:29 node-1 apache2_error [Sun Nov 06 23:58:23.493771 2016] [mpm_worker:warn] [pid 30458:tid 139760952317824] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  6 23:58:29 node-1 apache2_error [Sun Nov 06 23:58:23.497609 2016] [mpm_worker:notice] [pid 30458:tid 139760952317824] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  6 23:58:29 node-1 apache2_error [Sun Nov 06 23:58:23.497630 2016] [core:notice] [pid 30458:tid 139760952317824] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  6 23:58:59 node-1 apache2_error [Sun Nov 06 23:58:59.870431 2016] [mpm_worker:notice] [pid 30458:tid 139760952317824] AH00297: SIGUSR1 received.  Doing graceful restart
<27>Nov  6 23:59:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:04 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:04 node-1 multipathd: uevent trigger error
<43>Nov  6 23:59:09 node-1 apache2_error [Sun Nov 06 23:59:00.066593 2016] [mpm_worker:warn] [pid 30458:tid 139760952317824] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  6 23:59:09 node-1 apache2_error [Sun Nov 06 23:59:00.072432 2016] [mpm_worker:notice] [pid 30458:tid 139760952317824] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  6 23:59:09 node-1 apache2_error [Sun Nov 06 23:59:00.072468 2016] [core:notice] [pid 30458:tid 139760952317824] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  6 23:59:10 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:10 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:10 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:10 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:15 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:15 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:15 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:15 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:15 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:32 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:32 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:32 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:32 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:32 node-1 multipathd: uevent trigger error
<27>Nov  6 23:59:54 node-1 multipathd: uevent trigger error
<11>Nov  7 00:00:01 node-1 liberasurecode[121077]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 00:00:01 node-1 liberasurecode[121077]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 00:00:01 node-1 liberasurecode[121077]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  7 00:00:01 node-1 liberasurecode[121077]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  7 00:00:02 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:02 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:02 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:02 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:02 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:08 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov  7 00:00:17 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:17 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:22 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:22 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:22 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:22 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:22 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:32 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:32 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:32 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:32 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:32 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:32 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:37 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:37 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:37 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:37 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:37 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:51 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:51 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:51 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:51 node-1 multipathd: uevent trigger error
<27>Nov  7 00:00:51 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:23 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:23 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:23 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:23 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:23 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:36 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:36 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:36 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:36 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:36 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:41 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:41 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:41 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:41 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:41 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:41 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:54 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:54 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:54 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:54 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:54 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:59 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:59 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:59 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:59 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:59 node-1 multipathd: uevent trigger error
<27>Nov  7 00:01:59 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:04 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:04 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:04 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:04 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:04 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:09 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:09 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:09 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:09 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:09 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:13 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:13 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:13 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:13 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:13 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:18 node-1 multipathd: uevent trigger error
<27>Nov  7 00:02:18 node-1 multipathd: uevent trigger error
