Nov  9 05:56:18 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8379" x-info="http://www.rsyslog.com"] start
Nov  9 05:56:18 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov  9 05:56:18 node-1 rsyslogd: rsyslogd's groupid changed to 104
Nov  9 05:56:18 node-1 rsyslogd: rsyslogd's userid changed to 101
Nov  9 05:56:18 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov  9 05:56:18 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov  9 05:56:18 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov  9 05:56:18 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  9 05:56:18 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=a6a17c46-4294-4f15-ab19-8e64ee935db0 nomdmonddf nomdmonisw
Nov  9 05:56:18 node-1 kernel: [    0.000000] KERNEL supported cpus:
Nov  9 05:56:18 node-1 kernel: [    0.000000]   Intel GenuineIntel
Nov  9 05:56:18 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Nov  9 05:56:18 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Nov  9 05:56:18 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov  9 05:56:18 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov  9 05:56:18 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov  9 05:56:18 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Nov  9 05:56:18 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  9 05:56:18 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov  9 05:56:18 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov  9 05:56:18 node-1 kernel: [    0.000000] No AGP bridge found
Nov  9 05:56:18 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov  9 05:56:18 node-1 kernel: [    0.000000] MTRR default type: write-back
Nov  9 05:56:18 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov  9 05:56:18 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Nov  9 05:56:18 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov  9 05:56:18 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov  9 05:56:18 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Nov  9 05:56:18 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov  9 05:56:18 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov  9 05:56:18 node-1 kernel: [    0.000000]   2 disabled
Nov  9 05:56:18 node-1 kernel: [    0.000000]   3 disabled
Nov  9 05:56:18 node-1 kernel: [    0.000000]   4 disabled
Nov  9 05:56:18 node-1 kernel: [    0.000000]   5 disabled
Nov  9 05:56:18 node-1 kernel: [    0.000000]   6 disabled
Nov  9 05:56:18 node-1 kernel: [    0.000000]   7 disabled
Nov  9 05:56:18 node-1 kernel: [    0.000000]   8 disabled
Nov  9 05:56:18 node-1 kernel: [    0.000000]   9 disabled
Nov  9 05:56:18 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov  9 05:56:18 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov  9 05:56:18 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov  9 05:56:18 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov  9 05:56:18 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov  9 05:56:18 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Nov  9 05:56:18 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov  9 05:56:18 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov  9 05:56:18 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov  9 05:56:18 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov  9 05:56:18 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov  9 05:56:18 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov  9 05:56:18 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov  9 05:56:18 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Nov  9 05:56:18 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov  9 05:56:18 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov  9 05:56:18 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov  9 05:56:18 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov  9 05:56:18 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov  9 05:56:18 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov  9 05:56:18 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov  9 05:56:18 node-1 kernel: [    0.000000] Zone ranges:
Nov  9 05:56:18 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] Movable zone start for each node
Nov  9 05:56:18 node-1 kernel: [    0.000000] Early memory node ranges
Nov  9 05:56:18 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Nov  9 05:56:18 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov  9 05:56:18 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov  9 05:56:18 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov  9 05:56:18 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Nov  9 05:56:18 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Nov  9 05:56:18 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov  9 05:56:18 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov  9 05:56:18 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov  9 05:56:18 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov  9 05:56:18 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov  9 05:56:18 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov  9 05:56:18 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov  9 05:56:18 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov  9 05:56:18 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov  9 05:56:18 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov  9 05:56:18 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov  9 05:56:18 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov  9 05:56:18 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov  9 05:56:18 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov  9 05:56:18 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov  9 05:56:18 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov  9 05:56:18 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov  9 05:56:18 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  9 05:56:18 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Nov  9 05:56:18 node-1 kernel: [    0.000000] Policy zone: Normal
Nov  9 05:56:18 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=a6a17c46-4294-4f15-ab19-8e64ee935db0 nomdmonddf nomdmonisw
Nov  9 05:56:18 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov  9 05:56:18 node-1 kernel: [    0.000000] Checking aperture...
Nov  9 05:56:18 node-1 kernel: [    0.000000] No AGP bridge found
Nov  9 05:56:18 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov  9 05:56:18 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov  9 05:56:18 node-1 kernel: [    0.000000] Memory: 32653312K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627184K reserved)
Nov  9 05:56:18 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov  9 05:56:18 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Nov  9 05:56:18 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov  9 05:56:18 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov  9 05:56:18 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov  9 05:56:18 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov  9 05:56:18 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov  9 05:56:18 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Nov  9 05:56:18 node-1 kernel: [    0.000000] console [tty0] enabled
Nov  9 05:56:18 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov  9 05:56:18 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov  9 05:56:18 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov  9 05:56:18 node-1 kernel: [    0.000000] hpet clockevent registered
Nov  9 05:56:18 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov  9 05:56:18 node-1 kernel: [    0.004000] tsc: Detected 3492.045 MHz processor
Nov  9 05:56:18 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.09 BogoMIPS (lpj=13968180)
Nov  9 05:56:18 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov  9 05:56:18 node-1 kernel: [    0.000043] Security Framework initialized
Nov  9 05:56:18 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Nov  9 05:56:18 node-1 kernel: [    0.000062] Yama: becoming mindful.
Nov  9 05:56:18 node-1 kernel: [    0.001459] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.006382] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.008307] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.008335] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.008615] Initializing cgroup subsys memory
Nov  9 05:56:18 node-1 kernel: [    0.008623] Initializing cgroup subsys devices
Nov  9 05:56:18 node-1 kernel: [    0.008625] Initializing cgroup subsys freezer
Nov  9 05:56:18 node-1 kernel: [    0.008626] Initializing cgroup subsys blkio
Nov  9 05:56:18 node-1 kernel: [    0.008628] Initializing cgroup subsys perf_event
Nov  9 05:56:18 node-1 kernel: [    0.008630] Initializing cgroup subsys hugetlb
Nov  9 05:56:18 node-1 kernel: [    0.008649] CPU: Physical Processor ID: 0
Nov  9 05:56:18 node-1 kernel: [    0.008650] CPU: Processor Core ID: 0
Nov  9 05:56:18 node-1 kernel: [    0.008654] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov  9 05:56:18 node-1 kernel: [    0.008654] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov  9 05:56:18 node-1 kernel: [    0.009348] mce: CPU supports 22 MCE banks
Nov  9 05:56:18 node-1 kernel: [    0.009376] CPU0: Thermal monitoring enabled (TM1)
Nov  9 05:56:18 node-1 kernel: [    0.009396] process: using mwait in idle threads
Nov  9 05:56:18 node-1 kernel: [    0.009400] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov  9 05:56:18 node-1 kernel: [    0.009400] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov  9 05:56:18 node-1 kernel: [    0.009400] tlb_flushall_shift: 6
Nov  9 05:56:18 node-1 kernel: [    0.009488] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov  9 05:56:18 node-1 kernel: [    0.010212] ACPI: Core revision 20131115
Nov  9 05:56:18 node-1 kernel: [    0.023041] ACPI: All ACPI Tables successfully acquired
Nov  9 05:56:18 node-1 kernel: [    0.023203] ftrace: allocating 28622 entries in 112 pages
Nov  9 05:56:18 node-1 kernel: [    0.031967] dmar: Host address width 46
Nov  9 05:56:18 node-1 kernel: [    0.031969] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov  9 05:56:18 node-1 kernel: [    0.031975] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  9 05:56:18 node-1 kernel: [    0.031977] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov  9 05:56:18 node-1 kernel: [    0.031981] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  9 05:56:18 node-1 kernel: [    0.031983] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov  9 05:56:18 node-1 kernel: [    0.031984] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov  9 05:56:18 node-1 kernel: [    0.031985] dmar: ATSR flags: 0x0
Nov  9 05:56:18 node-1 kernel: [    0.031986] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov  9 05:56:18 node-1 kernel: [    0.031987] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov  9 05:56:18 node-1 kernel: [    0.032103] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov  9 05:56:18 node-1 kernel: [    0.032104] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov  9 05:56:18 node-1 kernel: [    0.032105] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov  9 05:56:18 node-1 kernel: [    0.032106] HPET id 0 under DRHD base 0xc7ffc000
Nov  9 05:56:18 node-1 kernel: [    0.032108] Your BIOS is broken and requested that x2apic be disabled.
Nov  9 05:56:18 node-1 kernel: [    0.032108] This will slightly decrease performance.
Nov  9 05:56:18 node-1 kernel: [    0.032108] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov  9 05:56:18 node-1 kernel: [    0.032539] Enabled IRQ remapping in xapic mode
Nov  9 05:56:18 node-1 kernel: [    0.032540] x2apic not enabled, IRQ remapping is in xapic mode
Nov  9 05:56:18 node-1 kernel: [    0.032544] Switched APIC routing to physical flat.
Nov  9 05:56:18 node-1 kernel: [    0.033163] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov  9 05:56:18 node-1 kernel: [    0.072814] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov  9 05:56:18 node-1 kernel: [    0.072820] TSC deadline timer enabled
Nov  9 05:56:18 node-1 kernel: [    0.072827] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov  9 05:56:18 node-1 kernel: [    0.072833] ... version:                3
Nov  9 05:56:18 node-1 kernel: [    0.072834] ... bit width:              48
Nov  9 05:56:18 node-1 kernel: [    0.072835] ... generic registers:      4
Nov  9 05:56:18 node-1 kernel: [    0.072836] ... value mask:             0000ffffffffffff
Nov  9 05:56:18 node-1 kernel: [    0.072837] ... max period:             0000ffffffffffff
Nov  9 05:56:18 node-1 kernel: [    0.072838] ... fixed-purpose events:   3
Nov  9 05:56:18 node-1 kernel: [    0.072839] ... event mask:             000000070000000f
Nov  9 05:56:18 node-1 kernel: [    0.074245] x86: Booting SMP configuration:
Nov  9 05:56:18 node-1 kernel: [    0.088450] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov  9 05:56:18 node-1 kernel: [    0.074247] .... node  #0, CPUs:        #1  #2  #3
Nov  9 05:56:18 node-1 kernel: [    0.116360] .... node  #1, CPUs:    #4  #5  #6  #7
Nov  9 05:56:18 node-1 kernel: [    0.270525] .... node  #0, CPUs:    #8  #9 #10 #11
Nov  9 05:56:18 node-1 kernel: [    0.326148] .... node  #1, CPUs:   #12 #13 #14 #15
Nov  9 05:56:18 node-1 kernel: [    0.383004] x86: Booted up 2 nodes, 16 CPUs
Nov  9 05:56:18 node-1 kernel: [    0.383007] smpboot: Total of 16 processors activated (111757.68 BogoMIPS)
Nov  9 05:56:18 node-1 kernel: [    0.407680] devtmpfs: initialized
Nov  9 05:56:18 node-1 kernel: [    0.410187] EVM: security.selinux
Nov  9 05:56:18 node-1 kernel: [    0.410189] EVM: security.SMACK64
Nov  9 05:56:18 node-1 kernel: [    0.410190] EVM: security.ima
Nov  9 05:56:18 node-1 kernel: [    0.410191] EVM: security.capability
Nov  9 05:56:18 node-1 kernel: [    0.410240] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.410898] pinctrl core: initialized pinctrl subsystem
Nov  9 05:56:18 node-1 kernel: [    0.410960] regulator-dummy: no parameters
Nov  9 05:56:18 node-1 kernel: [    0.410992] RTC time:  5:55:42, date: 11/09/16
Nov  9 05:56:18 node-1 kernel: [    0.411024] NET: Registered protocol family 16
Nov  9 05:56:18 node-1 kernel: [    0.411107] cpuidle: using governor ladder
Nov  9 05:56:18 node-1 kernel: [    0.411108] cpuidle: using governor menu
Nov  9 05:56:18 node-1 kernel: [    0.411141] ACPI: bus type PCI registered
Nov  9 05:56:18 node-1 kernel: [    0.411143] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov  9 05:56:18 node-1 kernel: [    0.411209] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov  9 05:56:18 node-1 kernel: [    0.411212] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov  9 05:56:18 node-1 kernel: [    0.424943] PCI: Using configuration type 1 for base access
Nov  9 05:56:18 node-1 kernel: [    0.425946] bio: create slab <bio-0> at 0
Nov  9 05:56:18 node-1 kernel: [    0.426229] ACPI: Added _OSI(Module Device)
Nov  9 05:56:18 node-1 kernel: [    0.426230] ACPI: Added _OSI(Processor Device)
Nov  9 05:56:18 node-1 kernel: [    0.426232] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov  9 05:56:18 node-1 kernel: [    0.426233] ACPI: Added _OSI(Processor Aggregator Device)
Nov  9 05:56:18 node-1 kernel: [    0.438954] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov  9 05:56:18 node-1 kernel: [    0.450459] ACPI: Interpreter enabled
Nov  9 05:56:18 node-1 kernel: [    0.450464] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov  9 05:56:18 node-1 kernel: [    0.450468] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov  9 05:56:18 node-1 kernel: [    0.450471] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov  9 05:56:18 node-1 kernel: [    0.450478] ACPI: (supports S0 S4 S5)
Nov  9 05:56:18 node-1 kernel: [    0.450479] ACPI: Using IOAPIC for interrupt routing
Nov  9 05:56:18 node-1 kernel: [    0.450521] HEST: Table parsing has been initialized.
Nov  9 05:56:18 node-1 kernel: [    0.450523] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov  9 05:56:18 node-1 kernel: [    0.451077] ACPI: No dock devices found.
Nov  9 05:56:18 node-1 kernel: [    0.462626] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov  9 05:56:18 node-1 kernel: [    0.462631] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 05:56:18 node-1 kernel: [    0.462634] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  9 05:56:18 node-1 kernel: [    0.462660] PCI host bridge to bus 0000:ff
Nov  9 05:56:18 node-1 kernel: [    0.462662] pci_bus 0000:ff: root bus resource [bus ff]
Nov  9 05:56:18 node-1 kernel: [    0.462670] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.462707] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.462737] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.462770] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.462801] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.462829] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.462859] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.462887] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.462914] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.462942] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.462967] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.462993] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463021] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463046] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463072] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463098] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463126] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463152] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463178] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.463206] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463231] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.463256] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463282] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463311] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.463345] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463375] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463404] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463434] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463466] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463498] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463529] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463559] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463588] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463620] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463652] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463683] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463718] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463747] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463774] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463807] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463841] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463881] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463917] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463950] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.463978] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464007] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464036] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464067] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464100] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464131] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464163] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464192] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464222] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464251] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464281] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464312] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464346] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464404] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov  9 05:56:18 node-1 kernel: [    0.464406] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 05:56:18 node-1 kernel: [    0.464409] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  9 05:56:18 node-1 kernel: [    0.464428] PCI host bridge to bus 0000:7f
Nov  9 05:56:18 node-1 kernel: [    0.464429] pci_bus 0000:7f: root bus resource [bus 7f]
Nov  9 05:56:18 node-1 kernel: [    0.464434] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464462] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.464489] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464518] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464540] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.464565] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.464592] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464618] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464643] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464666] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464688] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464710] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464734] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464757] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464786] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464817] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464839] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464862] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464886] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.464912] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464937] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.464961] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.464986] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465015] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov  9 05:56:18 node-1 kernel: [    0.465049] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465075] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465102] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465128] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465153] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465181] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465209] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465242] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465268] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465296] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465324] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465353] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465381] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465405] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465429] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465458] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465483] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465510] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465540] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465568] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465594] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465619] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465647] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465674] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465701] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465727] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465757] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465782] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465805] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465830] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465855] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465884] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.465910] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.467151] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov  9 05:56:18 node-1 kernel: [    0.467154] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 05:56:18 node-1 kernel: [    0.468272] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  9 05:56:18 node-1 kernel: [    0.468784] PCI host bridge to bus 0000:00
Nov  9 05:56:18 node-1 kernel: [    0.468786] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov  9 05:56:18 node-1 kernel: [    0.468788] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov  9 05:56:18 node-1 kernel: [    0.468789] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov  9 05:56:18 node-1 kernel: [    0.468791] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov  9 05:56:18 node-1 kernel: [    0.468792] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov  9 05:56:18 node-1 kernel: [    0.468794] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov  9 05:56:18 node-1 kernel: [    0.468795] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov  9 05:56:18 node-1 kernel: [    0.468801] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov  9 05:56:18 node-1 kernel: [    0.468883] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.468914] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.468955] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov  9 05:56:18 node-1 kernel: [    0.468974] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.469003] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.469043] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov  9 05:56:18 node-1 kernel: [    0.469060] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.469089] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.469130] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov  9 05:56:18 node-1 kernel: [    0.469146] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.469218] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.469293] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.469368] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov  9 05:56:18 node-1 kernel: [    0.469373] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov  9 05:56:18 node-1 kernel: [    0.469458] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov  9 05:56:18 node-1 kernel: [    0.469604] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov  9 05:56:18 node-1 kernel: [    0.469621] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov  9 05:56:18 node-1 kernel: [    0.469699] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.469754] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov  9 05:56:18 node-1 kernel: [    0.469775] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.469831] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.469874] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov  9 05:56:18 node-1 kernel: [    0.469901] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.469956] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.469999] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov  9 05:56:18 node-1 kernel: [    0.470023] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov  9 05:56:18 node-1 kernel: [    0.470041] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov  9 05:56:18 node-1 kernel: [    0.470119] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.470169] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov  9 05:56:18 node-1 kernel: [    0.470194] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov  9 05:56:18 node-1 kernel: [    0.470439] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov  9 05:56:18 node-1 kernel: [    0.470445] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov  9 05:56:18 node-1 kernel: [    0.470451] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.470457] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.470464] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov  9 05:56:18 node-1 kernel: [    0.470494] pci 0000:01:00.0: supports D1 D2
Nov  9 05:56:18 node-1 kernel: [    0.476783] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  9 05:56:18 node-1 kernel: [    0.476789] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  9 05:56:18 node-1 kernel: [    0.476794] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  9 05:56:18 node-1 kernel: [    0.476949] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.476982] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov  9 05:56:18 node-1 kernel: [    0.484779] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  9 05:56:18 node-1 kernel: [    0.484782] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.484783] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  9 05:56:18 node-1 kernel: [    0.484838] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.484906] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.484982] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.485026] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  9 05:56:18 node-1 kernel: [    0.485030] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.485032] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  9 05:56:18 node-1 kernel: [    0.485088] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.485211] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.485264] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  9 05:56:18 node-1 kernel: [    0.485266] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.485269] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  9 05:56:18 node-1 kernel: [    0.485327] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.485447] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.485485] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.485607] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.485642] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.485762] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.485797] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov  9 05:56:18 node-1 kernel: [    0.485917] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov  9 05:56:18 node-1 kernel: [    0.485958] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  9 05:56:18 node-1 kernel: [    0.485961] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.485963] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  9 05:56:18 node-1 kernel: [    0.486022] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov  9 05:56:18 node-1 kernel: [    0.486085] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.486137] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.486179] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov  9 05:56:18 node-1 kernel: [    0.486260] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov  9 05:56:18 node-1 kernel: [    0.486397] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  9 05:56:18 node-1 kernel: [    0.486400] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.486402] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  9 05:56:18 node-1 kernel: [    0.486460] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov  9 05:56:18 node-1 kernel: [    0.486519] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.486570] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.486782] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  9 05:56:18 node-1 kernel: [    0.486786] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  9 05:56:18 node-1 kernel: [    0.486854] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov  9 05:56:18 node-1 kernel: [    0.486912] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.486959] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.487175] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  9 05:56:18 node-1 kernel: [    0.487179] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  9 05:56:18 node-1 kernel: [    0.487249] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov  9 05:56:18 node-1 kernel: [    0.487311] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.487391] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov  9 05:56:18 node-1 kernel: [    0.487613] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  9 05:56:18 node-1 kernel: [    0.487617] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  9 05:56:18 node-1 kernel: [    0.487790] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  9 05:56:18 node-1 kernel: [    0.487829] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  9 05:56:18 node-1 kernel: [    0.487905] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov  9 05:56:18 node-1 kernel: [    0.487924] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov  9 05:56:18 node-1 kernel: [    0.487937] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov  9 05:56:18 node-1 kernel: [    0.487950] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov  9 05:56:18 node-1 kernel: [    0.488001] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov  9 05:56:18 node-1 kernel: [    0.492792] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  9 05:56:18 node-1 kernel: [    0.492801] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  9 05:56:18 node-1 kernel: [    0.492859] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov  9 05:56:18 node-1 kernel: [    0.493347] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov  9 05:56:18 node-1 kernel: [    0.493350] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  9 05:56:18 node-1 kernel: [    0.493471] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  9 05:56:18 node-1 kernel: [    0.493577] PCI host bridge to bus 0000:80
Nov  9 05:56:18 node-1 kernel: [    0.493579] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov  9 05:56:18 node-1 kernel: [    0.493580] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov  9 05:56:18 node-1 kernel: [    0.493582] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov  9 05:56:18 node-1 kernel: [    0.493590] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.493653] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.493720] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov  9 05:56:18 node-1 kernel: [    0.493781] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov  9 05:56:18 node-1 kernel: [    0.493786] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov  9 05:56:18 node-1 kernel: [    0.493856] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov  9 05:56:18 node-1 kernel: [    0.494153] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov  9 05:56:18 node-1 kernel: [    0.494184] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov  9 05:56:18 node-1 kernel: [    0.494214] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov  9 05:56:18 node-1 kernel: [    0.494243] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov  9 05:56:18 node-1 kernel: [    0.494272] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  9 05:56:18 node-1 kernel: [    0.494302] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  9 05:56:18 node-1 kernel: [    0.494332] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  9 05:56:18 node-1 kernel: [    0.494362] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  9 05:56:18 node-1 kernel: [    0.494447] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov  9 05:56:18 node-1 kernel: [    0.494451] ACPI: \_SB_.UNC1: notify handler is installed
Nov  9 05:56:18 node-1 kernel: [    0.494452] ACPI: \_SB_.UNC0: notify handler is installed
Nov  9 05:56:18 node-1 kernel: [    0.494467] ACPI: \_SB_.PCI0: notify handler is installed
Nov  9 05:56:18 node-1 kernel: [    0.494520] ACPI: \_SB_.PCI1: notify handler is installed
Nov  9 05:56:18 node-1 kernel: [    0.494599] Found 4 acpi root devices
Nov  9 05:56:18 node-1 kernel: [    0.494705] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov  9 05:56:18 node-1 kernel: [    0.494707] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov  9 05:56:18 node-1 kernel: [    0.494708] vgaarb: loaded
Nov  9 05:56:18 node-1 kernel: [    0.494710] vgaarb: bridge control possible 0000:0c:00.0
Nov  9 05:56:18 node-1 kernel: [    0.494822] SCSI subsystem initialized
Nov  9 05:56:18 node-1 kernel: [    0.494886] libata version 3.00 loaded.
Nov  9 05:56:18 node-1 kernel: [    0.494900] ACPI: bus type USB registered
Nov  9 05:56:18 node-1 kernel: [    0.494910] usbcore: registered new interface driver usbfs
Nov  9 05:56:18 node-1 kernel: [    0.494915] usbcore: registered new interface driver hub
Nov  9 05:56:18 node-1 kernel: [    0.494938] usbcore: registered new device driver usb
Nov  9 05:56:18 node-1 kernel: [    0.495112] PCI: Using ACPI for IRQ routing
Nov  9 05:56:18 node-1 kernel: [    0.498700] PCI: pci_cache_line_size set to 64 bytes
Nov  9 05:56:18 node-1 kernel: [    0.498907] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov  9 05:56:18 node-1 kernel: [    0.498908] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Nov  9 05:56:18 node-1 kernel: [    0.498908] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov  9 05:56:18 node-1 kernel: [    0.498971] NetLabel: Initializing
Nov  9 05:56:18 node-1 kernel: [    0.498972] NetLabel:  domain hash size = 128
Nov  9 05:56:18 node-1 kernel: [    0.498973] NetLabel:  protocols = UNLABELED CIPSOv4
Nov  9 05:56:18 node-1 kernel: [    0.498983] NetLabel:  unlabeled traffic allowed by default
Nov  9 05:56:18 node-1 kernel: [    0.499037] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov  9 05:56:18 node-1 kernel: [    0.499041] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov  9 05:56:18 node-1 kernel: [    0.501097] Switched to clocksource hpet
Nov  9 05:56:18 node-1 kernel: [    0.505279] AppArmor: AppArmor Filesystem Enabled
Nov  9 05:56:18 node-1 kernel: [    0.505293] pnp: PnP ACPI init
Nov  9 05:56:18 node-1 kernel: [    0.505300] ACPI: bus type PNP registered
Nov  9 05:56:18 node-1 kernel: [    0.505413] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov  9 05:56:18 node-1 kernel: [    0.505422] pnp 00:01: [dma 4]
Nov  9 05:56:18 node-1 kernel: [    0.505434] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov  9 05:56:18 node-1 kernel: [    0.505460] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov  9 05:56:18 node-1 kernel: [    0.505480] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov  9 05:56:18 node-1 kernel: [    0.505498] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov  9 05:56:18 node-1 kernel: [    0.505531] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov  9 05:56:18 node-1 kernel: [    0.505585] system 00:06: [io  0x0500-0x057f] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505587] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov  9 05:56:18 node-1 kernel: [    0.505589] system 00:06: [io  0x0580-0x059f] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505590] system 00:06: [io  0x0600-0x061f] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505591] system 00:06: [io  0x0880-0x0883] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505596] system 00:06: [io  0x0800-0x081f] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505598] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov  9 05:56:18 node-1 kernel: [    0.505600] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505601] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505603] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505604] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505606] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505607] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov  9 05:56:18 node-1 kernel: [    0.505609] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov  9 05:56:18 node-1 kernel: [    0.505693] pnp 00:07: [dma 0 disabled]
Nov  9 05:56:18 node-1 kernel: [    0.505721] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  9 05:56:18 node-1 kernel: [    0.505796] pnp 00:08: [dma 0 disabled]
Nov  9 05:56:18 node-1 kernel: [    0.505827] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  9 05:56:18 node-1 kernel: [    0.505878] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov  9 05:56:18 node-1 kernel: [    0.506224] pnp: PnP ACPI: found 10 devices
Nov  9 05:56:18 node-1 kernel: [    0.506226] ACPI: bus type PNP unregistered
Nov  9 05:56:18 node-1 kernel: [    0.512433] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  9 05:56:18 node-1 kernel: [    0.512436] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  9 05:56:18 node-1 kernel: [    0.512438] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  9 05:56:18 node-1 kernel: [    0.512443] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  9 05:56:18 node-1 kernel: [    0.512444] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.512459] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512488] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  9 05:56:18 node-1 kernel: [    0.512503] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512532] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  9 05:56:18 node-1 kernel: [    0.512546] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  9 05:56:18 node-1 kernel: [    0.512575] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  9 05:56:18 node-1 kernel: [    0.512590] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  9 05:56:18 node-1 kernel: [    0.512618] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  9 05:56:18 node-1 kernel: [    0.512620] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.512635] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512664] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  9 05:56:18 node-1 kernel: [    0.512665] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.512680] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512709] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  9 05:56:18 node-1 kernel: [    0.512710] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.512713] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512717] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  9 05:56:18 node-1 kernel: [    0.512719] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.512721] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512725] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  9 05:56:18 node-1 kernel: [    0.512730] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  9 05:56:18 node-1 kernel: [    0.512738] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  9 05:56:18 node-1 kernel: [    0.512741] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  9 05:56:18 node-1 kernel: [    0.512747] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov  9 05:56:18 node-1 kernel: [    0.512748] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov  9 05:56:18 node-1 kernel: [    0.512749] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov  9 05:56:18 node-1 kernel: [    0.512750] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov  9 05:56:18 node-1 kernel: [    0.512751] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov  9 05:56:18 node-1 kernel: [    0.512752] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov  9 05:56:18 node-1 kernel: [    0.512753] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov  9 05:56:18 node-1 kernel: [    0.512754] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov  9 05:56:18 node-1 kernel: [    0.512755] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.512755] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512756] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.512757] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512758] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.512759] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512760] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.512761] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512762] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov  9 05:56:18 node-1 kernel: [    0.512763] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512764] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov  9 05:56:18 node-1 kernel: [    0.512765] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov  9 05:56:18 node-1 kernel: [    0.512766] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov  9 05:56:18 node-1 kernel: [    0.512767] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov  9 05:56:18 node-1 kernel: [    0.512769] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov  9 05:56:18 node-1 kernel: [    0.512770] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov  9 05:56:18 node-1 kernel: [    0.512805] NET: Registered protocol family 2
Nov  9 05:56:18 node-1 kernel: [    0.513062] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.513396] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.513540] TCP: Hash tables configured (established 262144 bind 65536)
Nov  9 05:56:18 node-1 kernel: [    0.513575] TCP: reno registered
Nov  9 05:56:18 node-1 kernel: [    0.513603] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.513699] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.513845] NET: Registered protocol family 1
Nov  9 05:56:18 node-1 kernel: [    0.553194] pci 0000:0c:00.0: Video device with shadowed ROM
Nov  9 05:56:18 node-1 kernel: [    0.553208] PCI: CLS 64 bytes, default 64
Nov  9 05:56:18 node-1 kernel: [    0.553285] Trying to unpack rootfs image as initramfs...
Nov  9 05:56:18 node-1 kernel: [    0.772773] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Nov  9 05:56:18 node-1 kernel: [    0.772810] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov  9 05:56:18 node-1 kernel: [    0.772812] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Nov  9 05:56:18 node-1 kernel: [    0.773245] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773251] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773256] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773261] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773270] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773281] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773290] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773299] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773307] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773316] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773328] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773335] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773344] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773366] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773374] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773381] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov  9 05:56:18 node-1 kernel: [    0.773459] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov  9 05:56:18 node-1 kernel: [    0.773462] Scanning for low memory corruption every 60 seconds
Nov  9 05:56:18 node-1 kernel: [    0.773837] Initialise system trusted keyring
Nov  9 05:56:18 node-1 kernel: [    0.773893] audit: initializing netlink socket (disabled)
Nov  9 05:56:18 node-1 kernel: [    0.773909] type=2000 audit(1478670941.724:1): initialized
Nov  9 05:56:18 node-1 kernel: [    0.791652] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov  9 05:56:18 node-1 kernel: [    0.793164] zbud: loaded
Nov  9 05:56:18 node-1 kernel: [    0.793288] VFS: Disk quotas dquot_6.5.2
Nov  9 05:56:18 node-1 kernel: [    0.793327] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov  9 05:56:18 node-1 kernel: [    0.793695] fuse init (API version 7.22)
Nov  9 05:56:18 node-1 kernel: [    0.793757] msgmni has been set to 32768
Nov  9 05:56:18 node-1 kernel: [    0.793804] Key type big_key registered
Nov  9 05:56:18 node-1 kernel: [    0.794329] Key type asymmetric registered
Nov  9 05:56:18 node-1 kernel: [    0.794331] Asymmetric key parser 'x509' registered
Nov  9 05:56:18 node-1 kernel: [    0.794354] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov  9 05:56:18 node-1 kernel: [    0.794425] io scheduler noop registered
Nov  9 05:56:18 node-1 kernel: [    0.794426] io scheduler deadline registered (default)
Nov  9 05:56:18 node-1 kernel: [    0.794445] io scheduler cfq registered
Nov  9 05:56:18 node-1 kernel: [    0.794935] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    0.795058] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    0.795175] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    0.795286] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    0.795400] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    0.795507] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    0.795891] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov  9 05:56:18 node-1 kernel: [    0.795916] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov  9 05:56:18 node-1 kernel: [    0.795933] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov  9 05:56:18 node-1 kernel: [    0.795951] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795953] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795956] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov  9 05:56:18 node-1 kernel: [    0.795961] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795962] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795964] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795965] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795967] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795968] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795970] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795971] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795972] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795974] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795975] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795977] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795979] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov  9 05:56:18 node-1 kernel: [    0.795985] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.795987] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov  9 05:56:18 node-1 kernel: [    0.796001] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.796005] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov  9 05:56:18 node-1 kernel: [    0.796015] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.796017] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov  9 05:56:18 node-1 kernel: [    0.796020] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov  9 05:56:18 node-1 kernel: [    0.796058] ioapic: probe of 0000:00:05.4 failed with error -22
Nov  9 05:56:18 node-1 kernel: [    0.796065] ioapic: probe of 0000:80:05.4 failed with error -22
Nov  9 05:56:18 node-1 kernel: [    0.796069] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov  9 05:56:18 node-1 kernel: [    0.796078] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov  9 05:56:18 node-1 kernel: [    0.796119] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov  9 05:56:18 node-1 kernel: [    0.796120] vesafb: scrolling: redraw
Nov  9 05:56:18 node-1 kernel: [    0.796121] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov  9 05:56:18 node-1 kernel: [    0.816851] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov  9 05:56:18 node-1 kernel: [    0.825352] Console: switching to colour frame buffer device 80x30
Nov  9 05:56:18 node-1 kernel: [    0.834030] fb0: VESA VGA frame buffer device
Nov  9 05:56:18 node-1 kernel: [    0.834225] intel_idle: MWAIT substates: 0x2120
Nov  9 05:56:18 node-1 kernel: [    0.834225] intel_idle: v0.4 model 0x3F
Nov  9 05:56:18 node-1 kernel: [    0.834226] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov  9 05:56:18 node-1 kernel: [    0.834472] ipmi message handler version 39.2
Nov  9 05:56:18 node-1 kernel: [    0.834743] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov  9 05:56:18 node-1 kernel: [    0.835173] ACPI: AC Adapter [P111] (on-line)
Nov  9 05:56:18 node-1 kernel: [    0.840387] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov  9 05:56:18 node-1 kernel: [    0.851445] ACPI: Power Button [PWRB]
Nov  9 05:56:18 node-1 kernel: [    0.857229] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov  9 05:56:18 node-1 kernel: [    0.868906] ACPI: Power Button [PWRF]
Nov  9 05:56:18 node-1 kernel: [    0.894664] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov  9 05:56:18 node-1 kernel: [    0.906474] pstore: Registered erst as persistent store backend
Nov  9 05:56:18 node-1 kernel: [    0.912764] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov  9 05:56:18 node-1 kernel: [    0.924839] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov  9 05:56:18 node-1 kernel: [    0.951603] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov  9 05:56:18 node-1 kernel: [    0.984863] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov  9 05:56:18 node-1 kernel: [    0.998898] Linux agpgart interface v0.103
Nov  9 05:56:18 node-1 kernel: [    1.006489] brd: module loaded
Nov  9 05:56:18 node-1 kernel: [    1.013506] loop: module loaded
Nov  9 05:56:18 node-1 kernel: [    1.020226] libphy: Fixed MDIO Bus: probed
Nov  9 05:56:18 node-1 kernel: [    1.026680] tun: Universal TUN/TAP device driver, 1.6
Nov  9 05:56:18 node-1 kernel: [    1.033145] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov  9 05:56:18 node-1 kernel: [    1.039658] PPP generic driver version 2.4.2
Nov  9 05:56:18 node-1 kernel: [    1.046038] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov  9 05:56:18 node-1 kernel: [    1.052480] ehci-pci: EHCI PCI platform driver
Nov  9 05:56:18 node-1 kernel: [    1.059003] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov  9 05:56:18 node-1 kernel: [    1.065405] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov  9 05:56:18 node-1 kernel: [    1.078003] ehci-pci 0000:00:1a.0: debug port 2
Nov  9 05:56:18 node-1 kernel: [    1.088199] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov  9 05:56:18 node-1 kernel: [    1.088218] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov  9 05:56:18 node-1 kernel: [    1.104591] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov  9 05:56:18 node-1 kernel: [    1.110664] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov  9 05:56:18 node-1 kernel: [    1.116829] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  9 05:56:18 node-1 kernel: [    1.128724] usb usb1: Product: EHCI Host Controller
Nov  9 05:56:18 node-1 kernel: [    1.134744] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  9 05:56:18 node-1 kernel: [    1.140781] usb usb1: SerialNumber: 0000:00:1a.0
Nov  9 05:56:18 node-1 kernel: [    1.146727] hub 1-0:1.0: USB hub found
Nov  9 05:56:18 node-1 kernel: [    1.152493] hub 1-0:1.0: 2 ports detected
Nov  9 05:56:18 node-1 kernel: [    1.158285] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov  9 05:56:18 node-1 kernel: [    1.163859] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov  9 05:56:18 node-1 kernel: [    1.174761] ehci-pci 0000:00:1d.0: debug port 2
Nov  9 05:56:18 node-1 kernel: [    1.184062] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov  9 05:56:18 node-1 kernel: [    1.184068] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov  9 05:56:18 node-1 kernel: [    1.200510] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov  9 05:56:18 node-1 kernel: [    1.205713] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov  9 05:56:18 node-1 kernel: [    1.211018] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  9 05:56:18 node-1 kernel: [    1.221582] usb usb2: Product: EHCI Host Controller
Nov  9 05:56:18 node-1 kernel: [    1.227041] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  9 05:56:18 node-1 kernel: [    1.232581] usb usb2: SerialNumber: 0000:00:1d.0
Nov  9 05:56:18 node-1 kernel: [    1.238093] hub 2-0:1.0: USB hub found
Nov  9 05:56:18 node-1 kernel: [    1.243444] hub 2-0:1.0: 2 ports detected
Nov  9 05:56:18 node-1 kernel: [    1.248749] ehci-platform: EHCI generic platform driver
Nov  9 05:56:18 node-1 kernel: [    1.253987] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov  9 05:56:18 node-1 kernel: [    1.259308] ohci-pci: OHCI PCI platform driver
Nov  9 05:56:18 node-1 kernel: [    1.264610] ohci-platform: OHCI generic platform driver
Nov  9 05:56:18 node-1 kernel: [    1.269807] uhci_hcd: USB Universal Host Controller Interface driver
Nov  9 05:56:18 node-1 kernel: [    1.275146] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov  9 05:56:18 node-1 kernel: [    1.468288] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov  9 05:56:18 node-1 kernel: [    1.772068] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov  9 05:56:18 node-1 kernel: [    1.788350] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov  9 05:56:18 node-1 kernel: [    1.793950] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  9 05:56:18 node-1 kernel: [    1.799618] hub 1-1:1.0: USB hub found
Nov  9 05:56:18 node-1 kernel: [    1.805087] hub 1-1:1.0: 6 ports detected
Nov  9 05:56:18 node-1 kernel: [    1.919925] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov  9 05:56:18 node-1 kernel: [    2.314045] i8042: No controller found
Nov  9 05:56:18 node-1 kernel: [    2.319605] mousedev: PS/2 mouse device common for all mice
Nov  9 05:56:18 node-1 kernel: [    2.325297] rtc_cmos 00:02: RTC can wake from S4
Nov  9 05:56:18 node-1 kernel: [    2.328331] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov  9 05:56:18 node-1 kernel: [    2.328332] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  9 05:56:18 node-1 kernel: [    2.328726] hub 2-1:1.0: USB hub found
Nov  9 05:56:18 node-1 kernel: [    2.328962] hub 2-1:1.0: 8 ports detected
Nov  9 05:56:18 node-1 kernel: [    2.353501] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov  9 05:56:18 node-1 kernel: [    2.359241] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov  9 05:56:18 node-1 kernel: [    2.370514] device-mapper: uevent: version 1.0.3
Nov  9 05:56:18 node-1 kernel: [    2.376207] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov  9 05:56:18 node-1 kernel: [    2.387560] ledtrig-cpu: registered to indicate activity on CPUs
Nov  9 05:56:18 node-1 kernel: [    2.393514] TCP: cubic registered
Nov  9 05:56:18 node-1 kernel: [    2.399372] NET: Registered protocol family 10
Nov  9 05:56:18 node-1 kernel: [    2.405437] NET: Registered protocol family 17
Nov  9 05:56:18 node-1 kernel: [    2.411193] Key type dns_resolver registered
Nov  9 05:56:18 node-1 kernel: [    2.417219] Loading compiled-in X.509 certificates
Nov  9 05:56:18 node-1 kernel: [    2.423437] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov  9 05:56:18 node-1 kernel: [    2.435038] registered taskstats version 1
Nov  9 05:56:18 node-1 kernel: [    2.443065] Key type trusted registered
Nov  9 05:56:18 node-1 kernel: [    2.450639] Key type encrypted registered
Nov  9 05:56:18 node-1 kernel: [    2.456138] AppArmor: AppArmor sha1 policy hashing enabled
Nov  9 05:56:18 node-1 kernel: [    2.461638] IMA: No TPM chip found, activating TPM-bypass!
Nov  9 05:56:18 node-1 kernel: [    2.467743] regulator-dummy: disabling
Nov  9 05:56:18 node-1 kernel: [    2.473204]   Magic number: 8:126:921
Nov  9 05:56:18 node-1 kernel: [    2.478665] clockevents clockevent14: hash matches
Nov  9 05:56:18 node-1 kernel: [    2.484154] acpi device:ef: hash matches
Nov  9 05:56:18 node-1 kernel: [    2.489696] rtc_cmos 00:02: setting system clock to 2016-11-09 05:55:44 UTC (1478670944)
Nov  9 05:56:18 node-1 kernel: [    2.502033] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov  9 05:56:18 node-1 kernel: [    2.507603] EDD information not available.
Nov  9 05:56:18 node-1 kernel: [    2.513147] PM: Hibernation image not present or could not be loaded.
Nov  9 05:56:18 node-1 kernel: [    2.514008] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov  9 05:56:18 node-1 kernel: [    2.525296] Write protecting the kernel read-only data: 12288k
Nov  9 05:56:18 node-1 kernel: [    2.531629] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov  9 05:56:18 node-1 kernel: [    2.544377] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov  9 05:56:18 node-1 kernel: [    2.576378] device-mapper: multipath: version 1.6.0 loaded
Nov  9 05:56:18 node-1 kernel: [    2.584132] systemd-udevd[215]: starting version 204
Nov  9 05:56:18 node-1 kernel: [    2.603346] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov  9 05:56:18 node-1 kernel: [    2.614796] md: linear personality registered for level -1
Nov  9 05:56:18 node-1 kernel: [    2.629166] md: multipath personality registered for level -4
Nov  9 05:56:18 node-1 kernel: [    2.637189] md: raid0 personality registered for level 0
Nov  9 05:56:18 node-1 kernel: [    2.643653] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov  9 05:56:18 node-1 kernel: [    2.643655] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov  9 05:56:18 node-1 kernel: [    2.644275] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov  9 05:56:18 node-1 kernel: [    2.644536] megasas: FW now in Ready state
Nov  9 05:56:18 node-1 kernel: [    2.644594] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644629] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644653] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644666] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644689] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644725] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644766] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644802] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644840] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644879] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644912] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644953] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.644992] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.645026] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.645061] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.645099] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.645266] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov  9 05:56:18 node-1 kernel: [    2.682079] md: raid1 personality registered for level 1
Nov  9 05:56:18 node-1 kernel: [    2.691490] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Nov  9 05:56:18 node-1 kernel: [    2.704983] 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  9 05:56:18 node-1 kernel: [    2.718953] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  9 05:56:18 node-1 kernel: [    2.726003] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.726007] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.726011] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.726016] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.726055] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  9 05:56:18 node-1 kernel: [    2.746470] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Nov  9 05:56:18 node-1 kernel: [    2.755318] raid6: sse2x1    1759 MB/s
Nov  9 05:56:18 node-1 kernel: [    2.766786] 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  9 05:56:18 node-1 kernel: [    2.780336] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov  9 05:56:18 node-1 kernel: [    2.823146] raid6: sse2x2    5817 MB/s
Nov  9 05:56:18 node-1 kernel: [    2.895087] raid6: sse2x4   10141 MB/s
Nov  9 05:56:18 node-1 kernel: [    2.967029] raid6: avx2x1   14951 MB/s
Nov  9 05:56:18 node-1 kernel: [    3.038959] raid6: avx2x2   18874 MB/s
Nov  9 05:56:18 node-1 kernel: [    3.110891] raid6: avx2x4   21333 MB/s
Nov  9 05:56:18 node-1 kernel: [    3.117032] raid6: using algorithm avx2x4 (21333 MB/s)
Nov  9 05:56:18 node-1 kernel: [    3.123114] raid6: using avx2x2 recovery algorithm
Nov  9 05:56:18 node-1 kernel: [    3.129102] megasas:IOC Init cmd success
Nov  9 05:56:18 node-1 kernel: [    3.129250] Switched to clocksource tsc
Nov  9 05:56:18 node-1 kernel: [    3.140750] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.140756] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.140760] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.140763] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.140767] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.140770] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.140829] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.152583] xor: automatically using best checksumming function:
Nov  9 05:56:18 node-1 kernel: [    3.156875] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov  9 05:56:18 node-1 kernel: [    3.156876] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  9 05:56:18 node-1 kernel: [    3.156876] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov  9 05:56:18 node-1 kernel: [    3.156883] usb 2-1.4: Manufacturer: Avocent
Nov  9 05:56:18 node-1 kernel: [    3.156885] usb 2-1.4: SerialNumber: 20111102-00000001
Nov  9 05:56:18 node-1 kernel: [    3.169357] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Nov  9 05:56:18 node-1 kernel: [    3.169358] 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  9 05:56:18 node-1 kernel: [    3.169359] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  9 05:56:18 node-1 kernel: [    3.169622] megasas: INIT adapter done
Nov  9 05:56:18 node-1 kernel: [    3.169943] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.170047] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.170136] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.170303] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.170790] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.184192] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Nov  9 05:56:18 node-1 kernel: [    3.184203] 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  9 05:56:18 node-1 kernel: [    3.184204] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  9 05:56:18 node-1 kernel: [    3.184461] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.184574] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.184653] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.184813] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.185178] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  9 05:56:18 node-1 kernel: [    3.239283] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov  9 05:56:18 node-1 kernel: [    3.241356] scsi0 : LSI SAS based MegaRAID driver
Nov  9 05:56:18 node-1 kernel: [    3.249323] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  9 05:56:18 node-1 kernel: [    3.308001] hidraw: raw HID events driver (C) Jiri Kosina
Nov  9 05:56:18 node-1 kernel: [    3.311083] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  9 05:56:18 node-1 kernel: [    3.315284] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov  9 05:56:18 node-1 kernel: [    3.315421] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov  9 05:56:18 node-1 kernel: [    3.315751] sd 0:2:0:0: [sda] Write Protect is off
Nov  9 05:56:18 node-1 kernel: [    3.315752] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov  9 05:56:18 node-1 kernel: [    3.315823] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov  9 05:56:18 node-1 kernel: [    3.346682]    avx       : 35713.000 MB/sec
Nov  9 05:56:18 node-1 kernel: [    3.346815]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Nov  9 05:56:18 node-1 kernel: [    3.348219] sd 0:2:0:0: [sda] Attached SCSI disk
Nov  9 05:56:18 node-1 kernel: [    3.388983] async_tx: api initialized (async)
Nov  9 05:56:18 node-1 kernel: [    3.397410] usbcore: registered new interface driver usbhid
Nov  9 05:56:18 node-1 kernel: [    3.403862] usbhid: USB HID core driver
Nov  9 05:56:18 node-1 kernel: [    3.411273] 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  9 05:56:18 node-1 kernel: [    3.424285] 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  9 05:56:18 node-1 kernel: [    3.437423] md: raid6 personality registered for level 6
Nov  9 05:56:18 node-1 kernel: [    3.437635] 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  9 05:56:18 node-1 kernel: [    3.438761] 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  9 05:56:18 node-1 kernel: [    3.439947] 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  9 05:56:18 node-1 kernel: [    3.440813] 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  9 05:56:18 node-1 kernel: [    3.497977] md: raid5 personality registered for level 5
Nov  9 05:56:18 node-1 kernel: [    3.505039] md: raid4 personality registered for level 4
Nov  9 05:56:18 node-1 kernel: [    3.515154] md: raid10 personality registered for level 10
Nov  9 05:56:18 node-1 kernel: [    3.550501] random: lvm urandom read with 33 bits of entropy available
Nov  9 05:56:18 node-1 kernel: [    3.578558] multipathd (368): /proc/368/oom_adj is deprecated, please use /proc/368/oom_score_adj instead.
Nov  9 05:56:18 node-1 kernel: [    3.679951] bio: create slab <bio-1> at 1
Nov  9 05:56:18 node-1 kernel: [    4.425778] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov  9 05:56:18 node-1 kernel: [    5.114226] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Nov  9 05:56:18 node-1 kernel: [    5.151474] random: nonblocking pool is initialized
Nov  9 05:56:18 node-1 kernel: [    5.161930] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov  9 05:56:18 node-1 kernel: [    5.291822] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov  9 05:56:18 node-1 kernel: [    5.339795] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov  9 05:56:18 node-1 kernel: [    5.499920] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov  9 05:56:18 node-1 kernel: [    5.729782] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov  9 05:56:18 node-1 kernel: [    5.767710] XFS (dm-0): Mounting Filesystem
Nov  9 05:56:18 node-1 kernel: [    6.124668] XFS (dm-0): Ending clean mount
Nov  9 05:56:18 node-1 kernel: [    6.191928] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Nov  9 05:56:18 node-1 kernel: [    6.231399] XFS (dm-1): Mounting Filesystem
Nov  9 05:56:18 node-1 kernel: [    6.306221] XFS (dm-1): Ending clean mount
Nov  9 05:56:18 node-1 kernel: [    8.060692] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Nov  9 05:56:18 node-1 kernel: [    8.074170] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Nov  9 05:56:18 node-1 kernel: [    8.261260] systemd-udevd[777]: starting version 204
Nov  9 05:56:18 node-1 kernel: [    8.486102] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov  9 05:56:18 node-1 kernel: [    8.504236] wmi: Mapper loaded
Nov  9 05:56:18 node-1 kernel: [    8.505546] power_meter ACPI000D:00: Found ACPI power meter.
Nov  9 05:56:18 node-1 kernel: [    8.505574] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov  9 05:56:18 node-1 kernel: [    8.516782] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov  9 05:56:18 node-1 kernel: [    8.516789] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  9 05:56:18 node-1 kernel: [    8.516792] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov  9 05:56:18 node-1 kernel: [    8.516795] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  9 05:56:18 node-1 kernel: [    8.517042] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov  9 05:56:18 node-1 kernel: [    8.518794] IPMI System Interface driver.
Nov  9 05:56:18 node-1 kernel: [    8.518834] ipmi_si: probing via ACPI
Nov  9 05:56:18 node-1 kernel: [    8.518847] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov  9 05:56:18 node-1 kernel: [    8.518848] ipmi_si: Adding ACPI-specified kcs state machine
Nov  9 05:56:18 node-1 kernel: [    8.518859] ipmi_si: probing via SMBIOS
Nov  9 05:56:18 node-1 kernel: [    8.518860] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov  9 05:56:18 node-1 kernel: [    8.518861] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov  9 05:56:18 node-1 kernel: [    8.518864] ipmi_si: probing via SPMI
Nov  9 05:56:18 node-1 kernel: [    8.518865] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov  9 05:56:18 node-1 kernel: [    8.518866] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov  9 05:56:18 node-1 kernel: [    8.518868] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov  9 05:56:18 node-1 kernel: [    8.566748] systemd-udevd[794]: renamed network interface eth1 to enp7s0
Nov  9 05:56:18 node-1 kernel: [    8.594637] systemd-udevd[812]: renamed network interface eth0 to enp6s0
Nov  9 05:56:18 node-1 kernel: [    8.614610] systemd-udevd[815]: renamed network interface eth3 to enp9s0
Nov  9 05:56:18 node-1 kernel: [    8.638603] systemd-udevd[813]: renamed network interface eth2 to enp8s0
Nov  9 05:56:18 node-1 kernel: [    8.675291] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov  9 05:56:18 node-1 kernel: [    8.675297] ipmi_si 00:09: IPMI kcs interface initialized
Nov  9 05:56:18 node-1 kernel: [    9.019911] type=1400 audit(1478670951.033:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1045 comm="apparmor_parser"
Nov  9 05:56:18 node-1 kernel: [    9.020056] type=1400 audit(1478670951.033:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1045 comm="apparmor_parser"
Nov  9 05:56:18 node-1 kernel: [    9.020181] type=1400 audit(1478670951.033:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1045 comm="apparmor_parser"
Nov  9 05:56:18 node-1 kernel: [    9.031911] type=1400 audit(1478670951.045:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Nov  9 05:56:18 node-1 kernel: [    9.032061] type=1400 audit(1478670951.045:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1049 comm="apparmor_parser"
Nov  9 05:56:18 node-1 kernel: [    9.032186] type=1400 audit(1478670951.045:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1049 comm="apparmor_parser"
Nov  9 05:56:18 node-1 kernel: [    9.034908] type=1400 audit(1478670951.049:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1044 comm="apparmor_parser"
Nov  9 05:56:18 node-1 kernel: [    9.035045] type=1400 audit(1478670951.049:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1044 comm="apparmor_parser"
Nov  9 05:56:18 node-1 kernel: [    9.035163] type=1400 audit(1478670951.049:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1044 comm="apparmor_parser"
Nov  9 05:56:18 node-1 kernel: [    9.036159] type=1400 audit(1478670951.049:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1046 comm="apparmor_parser"
Nov  9 05:56:18 node-1 kernel: [    9.546323] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Nov  9 05:56:18 node-1 kernel: [    9.558856] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Nov  9 05:56:18 node-1 kernel: [    9.752092] enic 0000:06:00.0 enp6s0: Link UP
Nov  9 05:56:18 node-1 kernel: [    9.753210] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov  9 05:56:18 node-1 kernel: [    9.753220] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov  9 05:56:18 node-1 kernel: [   19.193371] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov  9 05:56:18 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov  9 05:56:19 node-1 failsafe: Failsafe of 120 seconds reached.
Nov  9 05:56:20 node-1 kernel: [   38.683366] init: failsafe main process (8406) killed by TERM signal
Nov  9 05:56:20 node-1 dbus[8514]: [system] AppArmor D-Bus mediation is enabled
Nov  9 05:56:20 node-1 kernel: [   38.918624] audit_printk_skb: 30 callbacks suppressed
Nov  9 05:56:20 node-1 kernel: [   38.918624] type=1400 audit(1478670980.257:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8523 comm="apparmor_parser"
Nov  9 05:56:20 node-1 kernel: [   38.922810] type=1400 audit(1478670980.261:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8522 comm="apparmor_parser"
Nov  9 05:56:20 node-1 kernel: [   38.922815] type=1400 audit(1478670980.261:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8522 comm="apparmor_parser"
Nov  9 05:56:20 node-1 kernel: [   38.922818] type=1400 audit(1478670980.261:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Nov  9 05:56:20 node-1 kernel: [   38.923036] type=1400 audit(1478670980.261:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8522 comm="apparmor_parser"
Nov  9 05:56:20 node-1 kernel: [   38.923038] type=1400 audit(1478670980.261:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Nov  9 05:56:20 node-1 kernel: [   38.923152] type=1400 audit(1478670980.261:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Nov  9 05:56:20 node-1 kernel: [   38.997586] type=1400 audit(1478670980.337:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8525 comm="apparmor_parser"
Nov  9 05:56:20 node-1 anacron[8593]: Anacron 2.3 started on 2016-11-09
Nov  9 05:56:20 node-1 cron[8565]: (CRON) INFO (pidfile fd = 3)
Nov  9 05:56:20 node-1 anacron[8593]: Will run job `cron.daily' in 5 min.
Nov  9 05:56:20 node-1 anacron[8593]: Will run job `cron.weekly' in 10 min.
Nov  9 05:56:20 node-1 anacron[8593]: Will run job `cron.monthly' in 15 min.
Nov  9 05:56:20 node-1 anacron[8593]: Jobs will be executed sequentially
Nov  9 05:56:20 node-1 cron[8607]: (CRON) STARTUP (fork ok)
Nov  9 05:56:20 node-1 multipathd: path checkers start up
Nov  9 05:56:20 node-1 cron[8607]: (CRON) INFO (Running @reboot jobs)
Nov  9 05:56:21 node-1 postfix/master[8744]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov  9 05:56:24 node-1 puppet-agent[8928]: Reopening log files
Nov  9 05:56:24 node-1 puppet-agent[8928]: Could not request certificate: Connection refused - connect(2)
Nov  9 05:56:39 node-1 puppet-user[9136]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov  9 05:56:39 node-1 puppet-user[9136]: Compiled catalog for node-1.domain.tld in environment production in 0.04 seconds
Nov  9 05:56:41 node-1 puppet-user[9136]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov  9 05:56:41 node-1 puppet-user[9136]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov  9 05:56:41 node-1 puppet-user[9136]: Finished catalog run in 1.99 seconds
Nov  9 05:56:42 node-1 multipathd: uevent trigger error
Nov  9 05:56:42 node-1 puppet-user[9616]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  9 05:56:42 node-1 puppet-user[9616]: Compiled catalog for node-1.domain.tld in environment production in 0.18 seconds
Nov  9 05:56:43 node-1 puppet-user[9616]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov  9 05:56:43 node-1 puppet-user[9616]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov  9 05:56:43 node-1 puppet-user[9616]: (/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  9 05:56:43 node-1 puppet-user[9616]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov  9 05:56:43 node-1 puppet-user[9616]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov  9 05:56:43 node-1 puppet-user[9616]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov  9 05:56:43 node-1 puppet-user[9616]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov  9 05:56:43 node-1 puppet-user[9616]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov  9 05:56:43 node-1 puppet-user[9616]: Finished catalog run in 0.06 seconds
Nov  9 05:56:44 node-1 puppet-user[10078]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov  9 05:56:44 node-1 puppet-user[10078]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Nov  9 05:56:44 node-1 puppet-user[10078]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov  9 05:56:44 node-1 puppet-user[10078]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov  9 05:56:44 node-1 puppet-user[10078]: Finished catalog run in 0.03 seconds
Nov  9 05:56:46 node-1 puppet-user[10541]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov  9 05:56:46 node-1 puppet-user[10541]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov  9 05:56:46 node-1 puppet-user[10541]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov  9 05:56:46 node-1 puppet-user[10541]: Finished catalog run in 0.04 seconds
Nov  9 05:56:47 node-1 puppet-user[10998]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov  9 05:56:47 node-1 puppet-user[10998]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Nov  9 05:56:48 node-1 puppet-user[10998]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov  9 05:56:50 node-1 puppet-user[10998]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Nov  9 05:56:50 node-1 puppet-user[10998]: Finished catalog run in 1.94 seconds
Nov  9 05:56:51 node-1 puppet-user[11722]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov  9 05:56:51 node-1 puppet-user[11722]: Compiled catalog for node-1.domain.tld in environment production in 0.19 seconds
Nov  9 05:56:51 node-1 puppet-user[11722]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov  9 05:56:51 node-1 puppet-user[11722]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Nov  9 05:56:51 node-1 puppet-user[11722]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov  9 05:56:51 node-1 puppet-user[11722]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov  9 05:56:51 node-1 puppet-user[11722]: Finished catalog run in 0.23 seconds
Nov  9 05:56:53 node-1 puppet-user[12211]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov  9 05:56:53 node-1 puppet-user[12211]: Compiled catalog for node-1.domain.tld in environment production in 0.14 seconds
Nov  9 05:56:53 node-1 puppet-user[12211]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov  9 05:56:53 node-1 kernel: [   71.672004] nr_pdflush_threads exported in /proc is scheduled for removal
Nov  9 05:56:53 node-1 kernel: [   71.672054] 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  9 05:56:53 node-1 puppet-user[12211]: (/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  9 05:56:53 node-1 puppet-user[12211]: Finished catalog run in 0.05 seconds
Nov  9 05:56:54 node-1 puppet-user[12668]: (Scope(Class[main])) MODULAR: sync_time
Nov  9 05:56:54 node-1 puppet-user[12668]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov  9 05:56:55 node-1 ntpdate[13084]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov  9 05:56:59 node-1 kernel: [   77.712112] init: plymouth-upstart-bridge main process ended, respawning
Nov  9 05:56:59 node-1 puppet-agent[8928]: Could not run: SIGTERM
Nov  9 05:56:59 node-1 kernel: [   77.989947] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov  9 05:56:59 node-1 ec2: 
Nov  9 05:56:59 node-1 ec2: #############################################################
Nov  9 05:56:59 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov  9 05:56:59 node-1 ec2: 1024 b7:57:d0:6a:09:d8:d7:da:4a:52:cd:92:3a:58:27:36  root@node-1.domain.tld (DSA)
Nov  9 05:56:59 node-1 ec2: 256 d3:77:3f:a1:ad:20:1e:50:c0:47:23:58:16:32:4d:45  root@node-1.domain.tld (ECDSA)
Nov  9 05:56:59 node-1 ec2: 256 32:e5:b0:6d:ee:de:1b:6d:40:a5:76:cd:97:25:ad:5f  root@node-1.domain.tld (ED25519)
Nov  9 05:56:59 node-1 ec2: 2048 24:dd:ee:d8:3e:c6:8e:a1:32:65:3a:4c:db:03:9c:2e  root@node-1.domain.tld (RSA)
Nov  9 05:56:59 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov  9 05:56:59 node-1 ec2: #############################################################
Nov  9 05:57:01 node-1 ntpdate[13084]: adjust time server 10.20.0.2 offset 0.000591 sec
Nov  9 05:57:01 node-1 puppet-user[12668]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov  9 05:57:01 node-1 puppet-user[12668]: Finished catalog run in 6.17 seconds
Nov  9 05:57:01 node-1 CRON[13432]: (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  9 05:57:07 node-1 puppet-user[13468]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  9 05:57:07 node-1 puppet-user[13468]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Nov  9 05:57:07 node-1 puppet-user[13468]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov  9 05:57:07 node-1 puppet-user[13468]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Nov  9 05:57:07 node-1 puppet-user[13468]: Finished catalog run in 0.07 seconds
Nov  9 05:57:08 node-1 puppet-user[13926]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov  9 05:57:09 node-1 puppet-user[13926]: Compiled catalog for node-1.domain.tld in environment production in 0.46 seconds
Nov  9 05:57:09 node-1 puppet-user[13926]: (/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  9 05:57:09 node-1 puppet-user[13926]: (/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  9 05:57:09 node-1 puppet-user[13926]: (/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  9 05:57:09 node-1 puppet-user[13926]: (/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  9 05:57:09 node-1 puppet-user[13926]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov  9 05:57:09 node-1 puppet-user[13926]: (/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  9 05:57:09 node-1 puppet-user[13926]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov  9 05:57:09 node-1 puppet-user[13926]: (/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  9 05:57:09 node-1 puppet-user[13926]: (/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  9 05:57:09 node-1 puppet-user[13926]: (/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  9 05:57:09 node-1 puppet-user[13926]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov  9 05:57:09 node-1 puppet-user[13926]: Finished catalog run in 0.81 seconds
Nov  9 05:57:11 node-1 puppet-user[14436]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov  9 05:57:11 node-1 puppet-user[14436]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Nov  9 05:57:15 node-1 puppet-user[14436]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov  9 05:57:17 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 05:57:17 node-1 nailgun-agent: I, [2016-11-09T05:57:17.092240 #13435]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  9 05:57:29 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  9 05:57:30 node-1 nailgun-agent: I, [2016-11-09T05:57:30.037228 #13435]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Nov  9 05:57:42 node-1 puppet-user[14436]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov  9 05:57:42 node-1 puppet-user[14436]: Finished catalog run in 30.88 seconds
Nov  9 05:57:44 node-1 puppet-user[17177]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov  9 05:57:45 node-1 puppet-user[17177]: Compiled catalog for node-1.domain.tld in environment production in 0.58 seconds
Nov  9 05:57:45 node-1 puppet-user[17177]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov  9 05:57:45 node-1 puppet-user[17177]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov  9 05:57:45 node-1 puppet-user[17177]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov  9 05:57:45 node-1 puppet-user[17177]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov  9 05:57:45 node-1 puppet-user[17177]: Finished catalog run in 0.09 seconds
Nov  9 05:57:47 node-1 puppet-user[17640]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov  9 05:57:48 node-1 puppet-user[17640]: Compiled catalog for node-1.domain.tld in environment production in 0.85 seconds
Nov  9 05:57:48 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov  9 05:57:48 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov  9 05:57:48 node-1 crontab[18081]: (root) LIST (root)
Nov  9 05:57:48 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov  9 05:57:48 node-1 crontab[18082]: (root) REPLACE (root)
Nov  9 05:57:49 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/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  9 05:57:50 node-1 puppet-user[17640]: (/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  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/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  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/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  9 05:57:50 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov  9 05:57:50 node-1 puppet-user[17640]: (/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  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov  9 05:57:51 node-1 puppet-user[17640]: (/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  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov  9 05:57:51 node-1 puppet-user[17640]: (/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  9 05:57:51 node-1 puppet-user[17640]: (/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  9 05:57:51 node-1 puppet-user[17640]: (/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  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov  9 05:57:51 node-1 puppet-user[17640]: (/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  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov  9 05:57:51 node-1 puppet-user[17640]: (/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  9 05:57:51 node-1 puppet-user[17640]: (/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  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov  9 05:57:51 node-1 puppet-user[17640]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov  9 05:57:51 node-1 puppet-user[17640]: (/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  9 05:57:51 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8379" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  9 05:57:51 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov  9 05:57:53 node-1 multipathd: uevent trigger error
<27>Nov  9 05:57:53 node-1 multipathd: uevent trigger error
<27>Nov  9 05:57:53 node-1 multipathd: uevent trigger error
<27>Nov  9 05:57:53 node-1 multipathd: uevent trigger error
<27>Nov  9 05:57:53 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:06 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:06 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:06 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:06 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:06 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:56 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:56 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:56 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:56 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:58 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:58 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:58 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:58 node-1 multipathd: uevent trigger error
<27>Nov  9 05:58:58 node-1 multipathd: uevent trigger error
<27>Nov  9 05:59:38 node-1 ntpdate[1511]: no servers can be used, exiting
<27>Nov  9 06:00:10 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:10 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:10 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:10 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:10 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:24 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:24 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:24 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:24 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:24 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:27 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:27 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:28 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:28 node-1 multipathd: uevent trigger error
<27>Nov  9 06:00:28 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:22 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:22 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:22 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:22 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:33 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 06:01:33 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 06:01:39 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 06:01:39 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 06:01:45 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 06:01:50 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 06:01:50 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  9 06:01:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:01:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:20 node-1 multipathd: uevent trigger error
<129>Nov  9 06:02:22 node-1 haproxy[23672]: 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  9 06:02:23 node-1 haproxy[23681]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:23 node-1 haproxy[23681]: Backup Server mysqld/node-4 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  9 06:02:23 node-1 haproxy[23681]: proxy mysqld has no server available!
<27>Nov  9 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:25 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:28 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:28 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:28 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:28 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:28 node-1 multipathd: uevent trigger error
<129>Nov  9 06:02:31 node-1 haproxy[26456]: 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  9 06:02:31 node-1 haproxy[26456]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:31 node-1 haproxy[26456]: Backup Server mysqld/node-4 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  9 06:02:31 node-1 haproxy[26456]: proxy mysqld has no server available!
<129>Nov  9 06:02:32 node-1 haproxy[26461]: 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  9 06:02:32 node-1 haproxy[26461]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:32 node-1 haproxy[26461]: Server object-storage/node-4 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  9 06:02:32 node-1 haproxy[26461]: proxy object-storage has no server available!
<27>Nov  9 06:02:34 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:34 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:34 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:34 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:34 node-1 multipathd: uevent trigger error
<129>Nov  9 06:02:36 node-1 haproxy[27786]: 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  9 06:02:36 node-1 haproxy[27786]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:36 node-1 haproxy[27786]: Server neutron/node-4 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  9 06:02:36 node-1 haproxy[27786]: proxy neutron has no server available!
<129>Nov  9 06:02:36 node-1 haproxy[27786]: 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  9 06:02:37 node-1 haproxy[27790]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:37 node-1 haproxy[27790]: Backup Server mysqld/node-4 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  9 06:02:37 node-1 haproxy[27790]: proxy mysqld has no server available!
<129>Nov  9 06:02:37 node-1 haproxy[27790]: 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  9 06:02:37 node-1 haproxy[27790]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:38 node-1 haproxy[27790]: Server object-storage/node-4 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  9 06:02:38 node-1 haproxy[27790]: proxy object-storage has no server available!
<27>Nov  9 06:02:39 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:39 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:39 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:39 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:39 node-1 multipathd: uevent trigger error
<129>Nov  9 06:02:41 node-1 haproxy[29197]: 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  9 06:02:42 node-1 haproxy[29201]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:42 node-1 haproxy[29201]: Server keystone-1/node-4 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  9 06:02:42 node-1 haproxy[29201]: proxy keystone-1 has no server available!
<129>Nov  9 06:02:42 node-1 haproxy[29201]: 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  9 06:02:42 node-1 haproxy[29201]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:42 node-1 haproxy[29201]: Server keystone-2/node-4 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  9 06:02:42 node-1 haproxy[29201]: proxy keystone-2 has no server available!
<129>Nov  9 06:02:42 node-1 haproxy[29201]: 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  9 06:02:42 node-1 haproxy[29201]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:42 node-1 haproxy[29201]: Server neutron/node-4 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  9 06:02:42 node-1 haproxy[29201]: proxy neutron has no server available!
<129>Nov  9 06:02:43 node-1 haproxy[29201]: 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  9 06:02:43 node-1 haproxy[29201]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:43 node-1 haproxy[29201]: Backup Server mysqld/node-4 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  9 06:02:43 node-1 haproxy[29201]: proxy mysqld has no server available!
<129>Nov  9 06:02:43 node-1 haproxy[29201]: 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  9 06:02:43 node-1 haproxy[29201]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:43 node-1 haproxy[29201]: Server object-storage/node-4 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  9 06:02:43 node-1 haproxy[29201]: proxy object-storage has no server available!
<27>Nov  9 06:02:45 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:45 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:45 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:45 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:45 node-1 multipathd: uevent trigger error
<129>Nov  9 06:02:47 node-1 haproxy[30590]: 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  9 06:02:47 node-1 haproxy[30590]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:47 node-1 haproxy[30590]: Server keystone-1/node-4 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  9 06:02:47 node-1 haproxy[30590]: proxy keystone-1 has no server available!
<129>Nov  9 06:02:47 node-1 haproxy[30590]: 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  9 06:02:47 node-1 haproxy[30590]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:47 node-1 haproxy[30590]: Server keystone-2/node-4 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  9 06:02:47 node-1 haproxy[30590]: proxy keystone-2 has no server available!
<129>Nov  9 06:02:47 node-1 haproxy[30590]: 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  9 06:02:48 node-1 haproxy[30594]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:48 node-1 haproxy[30594]: Server neutron/node-4 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  9 06:02:48 node-1 haproxy[30594]: proxy neutron has no server available!
<129>Nov  9 06:02:48 node-1 haproxy[30594]: 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  9 06:02:48 node-1 haproxy[30594]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:48 node-1 haproxy[30594]: Backup Server mysqld/node-4 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  9 06:02:48 node-1 haproxy[30594]: proxy mysqld has no server available!
<129>Nov  9 06:02:48 node-1 haproxy[30594]: 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  9 06:02:48 node-1 haproxy[30594]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:48 node-1 haproxy[30594]: Server object-storage/node-4 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  9 06:02:48 node-1 haproxy[30594]: proxy object-storage has no server available!
<129>Nov  9 06:02:48 node-1 haproxy[30594]: 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  9 06:02:49 node-1 haproxy[30594]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:49 node-1 haproxy[30594]: Server aodh/node-4 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  9 06:02:49 node-1 haproxy[30594]: proxy aodh has no server available!
<27>Nov  9 06:02:50 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:50 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:50 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:50 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:50 node-1 multipathd: uevent trigger error
<129>Nov  9 06:02:52 node-1 haproxy[31955]: 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  9 06:02:52 node-1 haproxy[31955]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:52 node-1 haproxy[31955]: Server keystone-1/node-4 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  9 06:02:52 node-1 haproxy[31955]: proxy keystone-1 has no server available!
<129>Nov  9 06:02:52 node-1 haproxy[31955]: 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  9 06:02:53 node-1 haproxy[31959]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:53 node-1 haproxy[31959]: Server keystone-2/node-4 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  9 06:02:53 node-1 haproxy[31959]: proxy keystone-2 has no server available!
<129>Nov  9 06:02:53 node-1 haproxy[31959]: 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  9 06:02:53 node-1 haproxy[31959]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:53 node-1 haproxy[31959]: Server neutron/node-4 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  9 06:02:53 node-1 haproxy[31959]: proxy neutron has no server available!
<129>Nov  9 06:02:53 node-1 haproxy[31959]: 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  9 06:02:53 node-1 haproxy[31959]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:53 node-1 haproxy[31959]: Backup Server mysqld/node-4 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  9 06:02:53 node-1 haproxy[31959]: proxy mysqld has no server available!
<129>Nov  9 06:02:53 node-1 haproxy[31959]: 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  9 06:02:53 node-1 haproxy[31959]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:54 node-1 haproxy[31959]: Server object-storage/node-4 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  9 06:02:54 node-1 haproxy[31959]: proxy object-storage has no server available!
<129>Nov  9 06:02:54 node-1 haproxy[31959]: 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  9 06:02:54 node-1 haproxy[31959]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:54 node-1 haproxy[31959]: Server aodh/node-4 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  9 06:02:54 node-1 haproxy[31959]: proxy aodh has no server available!
<129>Nov  9 06:02:54 node-1 haproxy[31959]: 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  9 06:02:54 node-1 haproxy[31959]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:54 node-1 haproxy[31959]: Server ceilometer/node-4 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  9 06:02:54 node-1 haproxy[31959]: proxy ceilometer has no server available!
<27>Nov  9 06:02:56 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:56 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:56 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:56 node-1 multipathd: uevent trigger error
<27>Nov  9 06:02:56 node-1 multipathd: uevent trigger error
<129>Nov  9 06:02:58 node-1 haproxy[899]: 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  9 06:02:58 node-1 haproxy[899]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:58 node-1 haproxy[899]: Server keystone-1/node-4 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  9 06:02:58 node-1 haproxy[899]: proxy keystone-1 has no server available!
<129>Nov  9 06:02:58 node-1 haproxy[899]: 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  9 06:02:58 node-1 haproxy[899]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:58 node-1 haproxy[899]: Server keystone-2/node-4 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  9 06:02:58 node-1 haproxy[899]: proxy keystone-2 has no server available!
<129>Nov  9 06:02:58 node-1 haproxy[899]: 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  9 06:02:58 node-1 haproxy[899]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:58 node-1 haproxy[899]: Server neutron/node-4 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  9 06:02:58 node-1 haproxy[899]: proxy neutron has no server available!
<129>Nov  9 06:02:58 node-1 haproxy[899]: 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  9 06:02:59 node-1 haproxy[903]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:59 node-1 haproxy[903]: Backup Server mysqld/node-4 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  9 06:02:59 node-1 haproxy[903]: proxy mysqld has no server available!
<129>Nov  9 06:02:59 node-1 haproxy[903]: 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  9 06:02:59 node-1 haproxy[903]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:59 node-1 haproxy[903]: Server object-storage/node-4 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  9 06:02:59 node-1 haproxy[903]: proxy object-storage has no server available!
<129>Nov  9 06:02:59 node-1 haproxy[903]: 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  9 06:02:59 node-1 haproxy[903]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:02:59 node-1 haproxy[903]: Server aodh/node-4 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  9 06:02:59 node-1 haproxy[903]: proxy aodh has no server available!
<129>Nov  9 06:02:59 node-1 haproxy[903]: 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  9 06:02:59 node-1 haproxy[903]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:00 node-1 haproxy[903]: Server ceilometer/node-4 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  9 06:03:00 node-1 haproxy[903]: proxy ceilometer has no server available!
<27>Nov  9 06:03:01 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:01 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:01 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:01 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:01 node-1 multipathd: uevent trigger error
<129>Nov  9 06:03:03 node-1 haproxy[2236]: 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  9 06:03:03 node-1 haproxy[2236]: 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  9 06:03:03 node-1 haproxy[2236]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:03 node-1 haproxy[2236]: Server keystone-1/node-4 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  9 06:03:03 node-1 haproxy[2236]: proxy keystone-1 has no server available!
<129>Nov  9 06:03:03 node-1 haproxy[2236]: 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  9 06:03:04 node-1 haproxy[2243]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:04 node-1 haproxy[2243]: Server keystone-2/node-4 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  9 06:03:04 node-1 haproxy[2243]: proxy keystone-2 has no server available!
<129>Nov  9 06:03:04 node-1 haproxy[2243]: 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  9 06:03:04 node-1 haproxy[2243]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:04 node-1 haproxy[2243]: Server neutron/node-4 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  9 06:03:04 node-1 haproxy[2243]: proxy neutron has no server available!
<129>Nov  9 06:03:04 node-1 haproxy[2243]: 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  9 06:03:04 node-1 haproxy[2243]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:04 node-1 haproxy[2243]: Backup Server mysqld/node-4 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  9 06:03:04 node-1 haproxy[2243]: proxy mysqld has no server available!
<129>Nov  9 06:03:04 node-1 haproxy[2243]: 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  9 06:03:04 node-1 haproxy[2243]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:04 node-1 haproxy[2243]: Server object-storage/node-4 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  9 06:03:04 node-1 haproxy[2243]: proxy object-storage has no server available!
<129>Nov  9 06:03:04 node-1 haproxy[2243]: 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  9 06:03:05 node-1 haproxy[2243]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:05 node-1 haproxy[2243]: Server aodh/node-4 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  9 06:03:05 node-1 haproxy[2243]: proxy aodh has no server available!
<129>Nov  9 06:03:05 node-1 haproxy[2243]: 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  9 06:03:05 node-1 haproxy[2243]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:05 node-1 haproxy[2243]: Server ceilometer/node-4 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  9 06:03:05 node-1 haproxy[2243]: proxy ceilometer has no server available!
<27>Nov  9 06:03:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:07 node-1 multipathd: uevent trigger error
<129>Nov  9 06:03:09 node-1 haproxy[3638]: 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  9 06:03:10 node-1 haproxy[3642]: 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  9 06:03:10 node-1 haproxy[3642]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:10 node-1 haproxy[3642]: Server keystone-1/node-4 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  9 06:03:10 node-1 haproxy[3642]: proxy keystone-1 has no server available!
<129>Nov  9 06:03:10 node-1 haproxy[3642]: 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  9 06:03:10 node-1 haproxy[3642]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:10 node-1 haproxy[3642]: Server keystone-2/node-4 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  9 06:03:10 node-1 haproxy[3642]: proxy keystone-2 has no server available!
<129>Nov  9 06:03:10 node-1 haproxy[3642]: 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  9 06:03:10 node-1 haproxy[3642]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:10 node-1 haproxy[3642]: Server glance-api/node-4 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  9 06:03:10 node-1 haproxy[3642]: proxy glance-api has no server available!
<129>Nov  9 06:03:10 node-1 haproxy[3642]: 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  9 06:03:10 node-1 haproxy[3642]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:10 node-1 haproxy[3642]: Server glance-glare/node-4 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  9 06:03:10 node-1 haproxy[3642]: proxy glance-glare has no server available!
<129>Nov  9 06:03:10 node-1 haproxy[3642]: 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  9 06:03:10 node-1 haproxy[3642]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:10 node-1 haproxy[3642]: Server neutron/node-4 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  9 06:03:10 node-1 haproxy[3642]: proxy neutron has no server available!
<129>Nov  9 06:03:10 node-1 haproxy[3642]: 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  9 06:03:11 node-1 haproxy[3642]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:11 node-1 haproxy[3642]: Server glance-registry/node-4 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  9 06:03:11 node-1 haproxy[3642]: proxy glance-registry has no server available!
<129>Nov  9 06:03:11 node-1 haproxy[3642]: 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  9 06:03:11 node-1 haproxy[3642]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:11 node-1 haproxy[3642]: Backup Server mysqld/node-4 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  9 06:03:11 node-1 haproxy[3642]: proxy mysqld has no server available!
<129>Nov  9 06:03:11 node-1 haproxy[3642]: 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  9 06:03:11 node-1 haproxy[3642]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:11 node-1 haproxy[3642]: Server object-storage/node-4 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  9 06:03:11 node-1 haproxy[3642]: proxy object-storage has no server available!
<129>Nov  9 06:03:11 node-1 haproxy[3642]: 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  9 06:03:11 node-1 haproxy[3642]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:11 node-1 haproxy[3642]: Server aodh/node-4 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  9 06:03:11 node-1 haproxy[3642]: proxy aodh has no server available!
<129>Nov  9 06:03:11 node-1 haproxy[3642]: 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  9 06:03:11 node-1 haproxy[3642]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:11 node-1 haproxy[3642]: Server ceilometer/node-4 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  9 06:03:11 node-1 haproxy[3642]: proxy ceilometer has no server available!
<27>Nov  9 06:03:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:13 node-1 multipathd: uevent trigger error
<129>Nov  9 06:03:15 node-1 haproxy[5050]: 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  9 06:03:16 node-1 haproxy[5054]: 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  9 06:03:16 node-1 haproxy[5054]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:16 node-1 haproxy[5054]: Server keystone-1/node-4 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  9 06:03:16 node-1 haproxy[5054]: proxy keystone-1 has no server available!
<129>Nov  9 06:03:16 node-1 haproxy[5054]: 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  9 06:03:16 node-1 haproxy[5054]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:16 node-1 haproxy[5054]: Server keystone-2/node-4 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  9 06:03:16 node-1 haproxy[5054]: proxy keystone-2 has no server available!
<129>Nov  9 06:03:16 node-1 haproxy[5054]: 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  9 06:03:16 node-1 haproxy[5054]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:16 node-1 haproxy[5054]: Server nova-api/node-4 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  9 06:03:16 node-1 haproxy[5054]: proxy nova-api has no server available!
<129>Nov  9 06:03:16 node-1 haproxy[5054]: 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  9 06:03:16 node-1 haproxy[5054]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:16 node-1 haproxy[5054]: Server nova-metadata-api/node-4 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  9 06:03:16 node-1 haproxy[5054]: proxy nova-metadata-api has no server available!
<129>Nov  9 06:03:16 node-1 haproxy[5054]: 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  9 06:03:16 node-1 haproxy[5054]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:16 node-1 haproxy[5054]: Server glance-api/node-4 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  9 06:03:16 node-1 haproxy[5054]: proxy glance-api has no server available!
<129>Nov  9 06:03:16 node-1 haproxy[5054]: 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  9 06:03:16 node-1 haproxy[5054]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:16 node-1 haproxy[5054]: Server glance-glare/node-4 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  9 06:03:16 node-1 haproxy[5054]: proxy glance-glare has no server available!
<129>Nov  9 06:03:16 node-1 haproxy[5054]: 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  9 06:03:16 node-1 haproxy[5054]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:17 node-1 haproxy[5054]: Server neutron/node-4 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  9 06:03:17 node-1 haproxy[5054]: proxy neutron has no server available!
<129>Nov  9 06:03:17 node-1 haproxy[5054]: 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  9 06:03:17 node-1 haproxy[5054]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:17 node-1 haproxy[5054]: Server glance-registry/node-4 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  9 06:03:17 node-1 haproxy[5054]: proxy glance-registry has no server available!
<129>Nov  9 06:03:17 node-1 haproxy[5054]: 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  9 06:03:17 node-1 haproxy[5054]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:17 node-1 haproxy[5054]: Backup Server mysqld/node-4 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  9 06:03:17 node-1 haproxy[5054]: proxy mysqld has no server available!
<129>Nov  9 06:03:17 node-1 haproxy[5054]: 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  9 06:03:17 node-1 haproxy[5054]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:17 node-1 haproxy[5054]: Server object-storage/node-4 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  9 06:03:17 node-1 haproxy[5054]: proxy object-storage has no server available!
<129>Nov  9 06:03:17 node-1 haproxy[5054]: 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  9 06:03:17 node-1 haproxy[5054]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:17 node-1 haproxy[5054]: Server aodh/node-4 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  9 06:03:17 node-1 haproxy[5054]: proxy aodh has no server available!
<129>Nov  9 06:03:17 node-1 haproxy[5054]: 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  9 06:03:17 node-1 haproxy[5054]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:17 node-1 haproxy[5054]: Server ceilometer/node-4 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  9 06:03:17 node-1 haproxy[5054]: proxy ceilometer has no server available!
<129>Nov  9 06:03:17 node-1 haproxy[5054]: 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  9 06:03:17 node-1 haproxy[5054]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:17 node-1 haproxy[5054]: Server nova-novncproxy/node-4 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  9 06:03:17 node-1 haproxy[5054]: proxy nova-novncproxy has no server available!
<27>Nov  9 06:03:19 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:19 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:19 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:19 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:19 node-1 multipathd: uevent trigger error
<129>Nov  9 06:03:21 node-1 haproxy[6391]: 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  9 06:03:21 node-1 haproxy[6391]: 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  9 06:03:21 node-1 haproxy[6391]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:21 node-1 haproxy[6391]: Server keystone-1/node-4 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  9 06:03:21 node-1 haproxy[6391]: proxy keystone-1 has no server available!
<129>Nov  9 06:03:21 node-1 haproxy[6391]: 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  9 06:03:21 node-1 haproxy[6391]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:21 node-1 haproxy[6391]: Server keystone-2/node-4 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  9 06:03:21 node-1 haproxy[6391]: proxy keystone-2 has no server available!
<129>Nov  9 06:03:21 node-1 haproxy[6391]: 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  9 06:03:21 node-1 haproxy[6391]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:21 node-1 haproxy[6391]: Server nova-api/node-4 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  9 06:03:21 node-1 haproxy[6391]: proxy nova-api has no server available!
<129>Nov  9 06:03:21 node-1 haproxy[6391]: 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  9 06:03:22 node-1 haproxy[6396]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:22 node-1 haproxy[6396]: Server nova-metadata-api/node-4 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  9 06:03:22 node-1 haproxy[6396]: proxy nova-metadata-api has no server available!
<129>Nov  9 06:03:22 node-1 haproxy[6396]: 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  9 06:03:22 node-1 haproxy[6396]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:22 node-1 haproxy[6396]: Backup Server cinder-api/node-4 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  9 06:03:22 node-1 haproxy[6396]: proxy cinder-api has no server available!
<129>Nov  9 06:03:22 node-1 haproxy[6396]: 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  9 06:03:22 node-1 haproxy[6396]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:22 node-1 haproxy[6396]: Server glance-api/node-4 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  9 06:03:22 node-1 haproxy[6396]: proxy glance-api has no server available!
<129>Nov  9 06:03:22 node-1 haproxy[6396]: 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  9 06:03:22 node-1 haproxy[6396]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:22 node-1 haproxy[6396]: Server glance-glare/node-4 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  9 06:03:22 node-1 haproxy[6396]: proxy glance-glare has no server available!
<129>Nov  9 06:03:22 node-1 haproxy[6396]: 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  9 06:03:22 node-1 haproxy[6396]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:22 node-1 haproxy[6396]: Server neutron/node-4 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  9 06:03:22 node-1 haproxy[6396]: proxy neutron has no server available!
<129>Nov  9 06:03:22 node-1 haproxy[6396]: 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  9 06:03:22 node-1 haproxy[6396]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:22 node-1 haproxy[6396]: Server glance-registry/node-4 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  9 06:03:22 node-1 haproxy[6396]: proxy glance-registry has no server available!
<129>Nov  9 06:03:22 node-1 haproxy[6396]: 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  9 06:03:22 node-1 haproxy[6396]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:22 node-1 haproxy[6396]: Backup Server mysqld/node-4 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  9 06:03:22 node-1 haproxy[6396]: proxy mysqld has no server available!
<129>Nov  9 06:03:22 node-1 haproxy[6396]: 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  9 06:03:22 node-1 haproxy[6396]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:23 node-1 haproxy[6396]: Server object-storage/node-4 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  9 06:03:23 node-1 haproxy[6396]: proxy object-storage has no server available!
<129>Nov  9 06:03:23 node-1 haproxy[6396]: 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  9 06:03:23 node-1 haproxy[6396]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:23 node-1 haproxy[6396]: Server aodh/node-4 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  9 06:03:23 node-1 haproxy[6396]: proxy aodh has no server available!
<129>Nov  9 06:03:23 node-1 haproxy[6396]: 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  9 06:03:23 node-1 haproxy[6396]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:23 node-1 haproxy[6396]: Server ceilometer/node-4 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  9 06:03:23 node-1 haproxy[6396]: proxy ceilometer has no server available!
<129>Nov  9 06:03:23 node-1 haproxy[6396]: 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  9 06:03:23 node-1 haproxy[6396]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:23 node-1 haproxy[6396]: Server nova-novncproxy/node-4 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  9 06:03:23 node-1 haproxy[6396]: proxy nova-novncproxy has no server available!
<27>Nov  9 06:03:24 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:24 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:24 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:24 node-1 multipathd: uevent trigger error
<129>Nov  9 06:03:27 node-1 haproxy[7832]: 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  9 06:03:27 node-1 haproxy[7832]: 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  9 06:03:27 node-1 haproxy[7832]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:27 node-1 haproxy[7832]: Server keystone-1/node-4 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  9 06:03:27 node-1 haproxy[7832]: proxy keystone-1 has no server available!
<129>Nov  9 06:03:27 node-1 haproxy[7832]: 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  9 06:03:27 node-1 haproxy[7832]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:27 node-1 haproxy[7832]: Server keystone-2/node-4 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  9 06:03:27 node-1 haproxy[7832]: proxy keystone-2 has no server available!
<129>Nov  9 06:03:27 node-1 haproxy[7832]: 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  9 06:03:27 node-1 haproxy[7832]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:27 node-1 haproxy[7832]: Server nova-api/node-4 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  9 06:03:27 node-1 haproxy[7832]: proxy nova-api has no server available!
<129>Nov  9 06:03:27 node-1 haproxy[7832]: 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  9 06:03:27 node-1 haproxy[7832]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:27 node-1 haproxy[7832]: Server nova-metadata-api/node-4 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  9 06:03:27 node-1 haproxy[7832]: proxy nova-metadata-api has no server available!
<129>Nov  9 06:03:27 node-1 haproxy[7832]: 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  9 06:03:27 node-1 haproxy[7832]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:27 node-1 haproxy[7832]: Backup Server cinder-api/node-4 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  9 06:03:27 node-1 haproxy[7832]: proxy cinder-api has no server available!
<129>Nov  9 06:03:27 node-1 haproxy[7832]: 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  9 06:03:27 node-1 haproxy[7832]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:28 node-1 haproxy[7836]: Server glance-api/node-4 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  9 06:03:28 node-1 haproxy[7836]: proxy glance-api has no server available!
<129>Nov  9 06:03:28 node-1 haproxy[7836]: 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  9 06:03:28 node-1 haproxy[7836]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:28 node-1 haproxy[7836]: Server glance-glare/node-4 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  9 06:03:28 node-1 haproxy[7836]: proxy glance-glare has no server available!
<129>Nov  9 06:03:28 node-1 haproxy[7836]: 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  9 06:03:28 node-1 haproxy[7836]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:28 node-1 haproxy[7836]: Server neutron/node-4 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  9 06:03:28 node-1 haproxy[7836]: proxy neutron has no server available!
<129>Nov  9 06:03:28 node-1 haproxy[7836]: 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  9 06:03:28 node-1 haproxy[7836]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:28 node-1 haproxy[7836]: Server glance-registry/node-4 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  9 06:03:28 node-1 haproxy[7836]: proxy glance-registry has no server available!
<129>Nov  9 06:03:28 node-1 haproxy[7836]: 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  9 06:03:28 node-1 haproxy[7836]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:28 node-1 haproxy[7836]: Backup Server mysqld/node-4 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  9 06:03:28 node-1 haproxy[7836]: proxy mysqld has no server available!
<129>Nov  9 06:03:28 node-1 haproxy[7836]: 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  9 06:03:28 node-1 haproxy[7836]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:28 node-1 haproxy[7836]: Server object-storage/node-4 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  9 06:03:28 node-1 haproxy[7836]: proxy object-storage has no server available!
<129>Nov  9 06:03:28 node-1 haproxy[7836]: 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  9 06:03:28 node-1 haproxy[7836]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:28 node-1 haproxy[7836]: Server aodh/node-4 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  9 06:03:28 node-1 haproxy[7836]: proxy aodh has no server available!
<129>Nov  9 06:03:28 node-1 haproxy[7836]: 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  9 06:03:28 node-1 haproxy[7836]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:28 node-1 haproxy[7836]: Server ceilometer/node-4 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  9 06:03:28 node-1 haproxy[7836]: proxy ceilometer has no server available!
<129>Nov  9 06:03:28 node-1 haproxy[7836]: 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  9 06:03:28 node-1 haproxy[7836]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:28 node-1 haproxy[7836]: Server heat-api/node-4 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  9 06:03:28 node-1 haproxy[7836]: proxy heat-api has no server available!
<129>Nov  9 06:03:28 node-1 haproxy[7836]: 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  9 06:03:28 node-1 haproxy[7836]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:29 node-1 haproxy[7836]: Server heat-api-cfn/node-4 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  9 06:03:29 node-1 haproxy[7836]: proxy heat-api-cfn has no server available!
<129>Nov  9 06:03:29 node-1 haproxy[7836]: 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  9 06:03:29 node-1 haproxy[7836]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:29 node-1 haproxy[7836]: Server heat-api-cloudwatch/node-4 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  9 06:03:29 node-1 haproxy[7836]: proxy heat-api-cloudwatch has no server available!
<129>Nov  9 06:03:29 node-1 haproxy[7836]: 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  9 06:03:29 node-1 haproxy[7836]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:03:29 node-1 haproxy[7836]: Server nova-novncproxy/node-4 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  9 06:03:29 node-1 haproxy[7836]: proxy nova-novncproxy has no server available!
<27>Nov  9 06:03:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:34 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:34 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:34 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:34 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:34 node-1 multipathd: uevent trigger error
<27>Nov  9 06:03:40 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov  9 06:04:04 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  9 06:04:07 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov  9 06:04:28 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 06:04:31 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  9 06:04:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:04:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:04:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:04:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:04:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:04:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:35 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:35 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:35 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:35 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:35 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:06:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:00 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:00 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:00 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:00 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:00 node-1 multipathd: uevent trigger error
<43>Nov  9 06:07:02 node-1 apache2_error [Wed Nov 09 06:06:52.258704 2016] [mpm_event:notice] [pid 13869:tid 140540781799296] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  9 06:07:02 node-1 apache2_error [Wed Nov 09 06:06:52.258849 2016] [core:notice] [pid 13869:tid 140540781799296] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  9 06:07:02 node-1 apache2_error [Wed Nov 09 06:06:55.292810 2016] [mpm_event:notice] [pid 13869:tid 140540781799296] AH00491: caught SIGTERM, shutting down
<43>Nov  9 06:07:02 node-1 apache2_error [Wed Nov 09 06:06:56.378098 2016] [mpm_worker:notice] [pid 14663:tid 140459005097856] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  9 06:07:02 node-1 apache2_error [Wed Nov 09 06:06:56.378135 2016] [core:notice] [pid 14663:tid 140459005097856] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 06:07:04 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:04 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:04 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:04 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:04 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:04 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:13 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:44 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 06:07:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:07:58 node-1 multipathd: uevent trigger error
<43>Nov  9 06:08:02 node-1 apache2_error [Wed Nov 09 06:07:54.769995 2016] [mpm_worker:notice] [pid 14663:tid 140459005097856] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 06:08:02 node-1 apache2_error [Wed Nov 09 06:07:54.776900 2016] [mpm_worker:warn] [pid 14663:tid 140459005097856] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  9 06:08:02 node-1 apache2_error [Wed Nov 09 06:07:54.777659 2016] [mpm_worker:notice] [pid 14663:tid 140459005097856] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  9 06:08:02 node-1 apache2_error [Wed Nov 09 06:07:54.777672 2016] [core:notice] [pid 14663:tid 140459005097856] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov  9 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov  9 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov  9 06:08:03 node-1 multipathd: uevent trigger error
<27>Nov  9 06:08:03 node-1 multipathd: uevent trigger error
<43>Nov  9 06:09:12 node-1 apache2_error [Wed Nov 09 06:09:06.217050 2016] [mpm_worker:notice] [pid 14663:tid 140459005097856] AH00295: caught SIGTERM, shutting down
<43>Nov  9 06:09:12 node-1 apache2_error [Wed Nov 09 06:09:06.964167 2016] [mpm_worker:notice] [pid 4360:tid 139860491179904] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 06:09:12 node-1 apache2_error [Wed Nov 09 06:09:06.964209 2016] [core:notice] [pid 4360:tid 139860491179904] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  9 06:09:52 node-1 apache2_error [Wed Nov 09 06:09:51.010550 2016] [mpm_worker:notice] [pid 4360:tid 139860491179904] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 06:09:52 node-1 apache2_error [Wed Nov 09 06:09:51.015453 2016] [mpm_worker:warn] [pid 4360:tid 139860491179904] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  9 06:09:52 node-1 apache2_error [Wed Nov 09 06:09:51.019141 2016] [mpm_worker:notice] [pid 4360:tid 139860491179904] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 06:09:52 node-1 apache2_error [Wed Nov 09 06:09:51.019160 2016] [core:notice] [pid 4360:tid 139860491179904] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 06:10:48 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 06:11:11 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:11 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:11 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:11 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:11 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:11 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:32 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:32 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:32 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:32 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:32 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:32 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:11:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:12:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:12:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:12:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:12:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:12:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:13:06 node-1 multipathd: uevent trigger error
<27>Nov  9 06:13:06 node-1 multipathd: uevent trigger error
<27>Nov  9 06:13:06 node-1 multipathd: uevent trigger error
<27>Nov  9 06:13:06 node-1 multipathd: uevent trigger error
<27>Nov  9 06:13:06 node-1 multipathd: uevent trigger error
<27>Nov  9 06:13:06 node-1 multipathd: uevent trigger error
<27>Nov  9 06:13:49 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 06:14:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:14:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:14:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:14:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:14:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:08 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:08 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:08 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:08 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:09 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:36 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:36 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:36 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:36 node-1 multipathd: uevent trigger error
<27>Nov  9 06:15:36 node-1 multipathd: uevent trigger error
<27>Nov  9 06:16:51 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 06:17:56 node-1 multipathd: uevent trigger error
<27>Nov  9 06:17:56 node-1 multipathd: uevent trigger error
<27>Nov  9 06:17:56 node-1 multipathd: uevent trigger error
<27>Nov  9 06:17:56 node-1 multipathd: uevent trigger error
<27>Nov  9 06:17:56 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:12 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:12 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:12 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:12 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:12 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:17 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:17 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:17 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:17 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:17 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:17 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:18:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:02 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:02 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:02 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:02 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:02 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:23 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:23 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:23 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:23 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:23 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:23 node-1 multipathd: uevent trigger error
<27>Nov  9 06:19:53 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 06:20:09 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:09 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:09 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:09 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:09 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:16 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Nov  9 06:20:16 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Nov  9 06:20:16 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Nov  9 06:20:17 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Nov  9 06:20:17 node-1 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Nov  9 06:20:18 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:18 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:18 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:18 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:18 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:31 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:31 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:31 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:31 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:31 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:46 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:46 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:46 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:46 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:46 node-1 multipathd: uevent trigger error
<27>Nov  9 06:20:46 node-1 multipathd: uevent trigger error
<27>Nov  9 06:21:03 node-1 multipathd: uevent trigger error
<27>Nov  9 06:21:03 node-1 multipathd: uevent trigger error
<27>Nov  9 06:21:03 node-1 multipathd: uevent trigger error
<27>Nov  9 06:21:03 node-1 multipathd: uevent trigger error
<27>Nov  9 06:21:03 node-1 multipathd: uevent trigger error
<27>Nov  9 06:21:03 node-1 multipathd: uevent trigger error
<27>Nov  9 06:22:54 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 06:23:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:23:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:17 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:17 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:17 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:17 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:22 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:26 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:26 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:26 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:26 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:26 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:37 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:37 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:38 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:38 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:24:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:25:36 node-1 multipathd: uevent trigger error
<27>Nov  9 06:25:36 node-1 multipathd: uevent trigger error
<27>Nov  9 06:25:36 node-1 multipathd: uevent trigger error
<27>Nov  9 06:25:36 node-1 multipathd: uevent trigger error
<27>Nov  9 06:25:55 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  9 06:26:40 node-1 multipathd: uevent trigger error
<27>Nov  9 06:26:40 node-1 multipathd: uevent trigger error
<27>Nov  9 06:26:40 node-1 multipathd: uevent trigger error
<27>Nov  9 06:26:40 node-1 multipathd: uevent trigger error
<27>Nov  9 06:26:40 node-1 multipathd: uevent trigger error
<27>Nov  9 06:26:55 node-1 multipathd: uevent trigger error
<27>Nov  9 06:26:55 node-1 multipathd: uevent trigger error
<27>Nov  9 06:26:55 node-1 multipathd: uevent trigger error
<27>Nov  9 06:26:55 node-1 multipathd: uevent trigger error
<27>Nov  9 06:26:55 node-1 multipathd: uevent trigger error
<11>Nov  9 06:27:08 node-1 liberasurecode[23001]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:08 node-1 liberasurecode[23001]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:08 node-1 liberasurecode[23001]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:08 node-1 liberasurecode[23001]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:08 node-1 liberasurecode[23066]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:08 node-1 liberasurecode[23066]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:08 node-1 liberasurecode[23066]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:08 node-1 liberasurecode[23066]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:10 node-1 liberasurecode[24024]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:10 node-1 liberasurecode[24024]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:10 node-1 liberasurecode[24024]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:10 node-1 liberasurecode[24024]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24637]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24637]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24637]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24637]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24681]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24681]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24681]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24681]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24722]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24722]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24722]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:14 node-1 liberasurecode[24722]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24790]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24790]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24790]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24790]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24804]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24804]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24804]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24804]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24826]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24826]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24826]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24826]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24840]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24840]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24840]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:15 node-1 liberasurecode[24840]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:32 node-1 liberasurecode[26039]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:32 node-1 liberasurecode[26039]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:32 node-1 liberasurecode[26039]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:27:32 node-1 liberasurecode[26039]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  9 06:27:40 node-1 multipathd: uevent trigger error
<27>Nov  9 06:27:40 node-1 multipathd: uevent trigger error
<27>Nov  9 06:27:40 node-1 multipathd: uevent trigger error
<27>Nov  9 06:27:40 node-1 multipathd: uevent trigger error
<27>Nov  9 06:27:40 node-1 multipathd: uevent trigger error
<43>Nov  9 06:28:34 node-1 apache2_error [Wed Nov 09 06:28:26.436651 2016] [mpm_worker:notice] [pid 4360:tid 139860491179904] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 06:28:34 node-1 apache2_error [Wed Nov 09 06:28:26.817467 2016] [mpm_worker:warn] [pid 4360:tid 139860491179904] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  9 06:28:34 node-1 apache2_error [Wed Nov 09 06:28:26.820829 2016] [mpm_worker:notice] [pid 4360:tid 139860491179904] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 06:28:34 node-1 apache2_error [Wed Nov 09 06:28:26.820871 2016] [core:notice] [pid 4360:tid 139860491179904] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 06:28:57 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  9 06:29:04 node-1 apache2_error [Wed Nov 09 06:29:03.576908 2016] [mpm_worker:notice] [pid 4360:tid 139860491179904] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  9 06:29:04 node-1 apache2_error [Wed Nov 09 06:29:03.773515 2016] [mpm_worker:warn] [pid 4360:tid 139860491179904] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  9 06:29:04 node-1 apache2_error [Wed Nov 09 06:29:03.784822 2016] [mpm_worker:notice] [pid 4360:tid 139860491179904] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  9 06:29:04 node-1 apache2_error [Wed Nov 09 06:29:03.784855 2016] [core:notice] [pid 4360:tid 139860491179904] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  9 06:29:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:07 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:14 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:30 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:45 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:45 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:45 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:45 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:45 node-1 multipathd: uevent trigger error
<27>Nov  9 06:29:45 node-1 multipathd: uevent trigger error
<11>Nov  9 06:30:01 node-1 liberasurecode[24605]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:30:01 node-1 liberasurecode[24605]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:30:01 node-1 liberasurecode[24605]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:30:01 node-1 liberasurecode[24605]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  9 06:30:05 node-1 multipathd: uevent trigger error
<27>Nov  9 06:30:11 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov  9 06:30:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:30:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:30:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:30:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:30:20 node-1 multipathd: uevent trigger error
<27>Nov  9 06:30:25 node-1 multipathd: uevent trigger error
<27>Nov  9 06:30:25 node-1 multipathd: uevent trigger error
<27>Nov  9 06:30:25 node-1 multipathd: uevent trigger error
<27>Nov  9 06:30:25 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:15 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:15 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:15 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:15 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:15 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:29 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:29 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:29 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:29 node-1 multipathd: uevent trigger error
<129>Nov  9 06:33:39 node-1 haproxy[31661]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  9 06:33:40 node-1 haproxy[31661]: Server neutron/node-4 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.
<27>Nov  9 06:33:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:41 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:33:57 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:02 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:02 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:02 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:02 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:02 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:16 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:21 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:33 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:33 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:33 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:33 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:33 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:34:44 node-1 multipathd: uevent trigger error
<129>Nov  9 06:34:50 node-1 haproxy[31661]: 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.
<11>Nov  9 06:35:01 node-1 liberasurecode[26034]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:35:01 node-1 liberasurecode[26034]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:35:01 node-1 liberasurecode[26034]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  9 06:35:01 node-1 liberasurecode[26034]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  9 06:35:35 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:35 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:35 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:35 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:39 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:39 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:39 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:39 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:39 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:44 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:49 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:49 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:49 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:49 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:49 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:53 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:58 node-1 multipathd: uevent trigger error
<27>Nov  9 06:35:58 node-1 multipathd: uevent trigger error
