Nov  5 04:09:21 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8395" x-info="http://www.rsyslog.com"] start
Nov  5 04:09:21 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov  5 04:09:21 node-1 rsyslogd: rsyslogd's groupid changed to 104
Nov  5 04:09:21 node-1 rsyslogd: rsyslogd's userid changed to 101
Nov  5 04:09:21 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov  5 04:09:21 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov  5 04:09:21 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov  5 04:09:21 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  5 04:09:21 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=5be8bcbe-3230-4ac3-8946-1216b263369e nomdmonddf nomdmonisw
Nov  5 04:09:21 node-1 kernel: [    0.000000] KERNEL supported cpus:
Nov  5 04:09:21 node-1 kernel: [    0.000000]   Intel GenuineIntel
Nov  5 04:09:21 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Nov  5 04:09:21 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Nov  5 04:09:21 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov  5 04:09:21 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov  5 04:09:21 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov  5 04:09:21 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Nov  5 04:09:21 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  5 04:09:21 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov  5 04:09:21 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov  5 04:09:21 node-1 kernel: [    0.000000] No AGP bridge found
Nov  5 04:09:21 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov  5 04:09:21 node-1 kernel: [    0.000000] MTRR default type: write-back
Nov  5 04:09:21 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov  5 04:09:21 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Nov  5 04:09:21 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov  5 04:09:21 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov  5 04:09:21 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Nov  5 04:09:21 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov  5 04:09:21 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov  5 04:09:21 node-1 kernel: [    0.000000]   2 disabled
Nov  5 04:09:21 node-1 kernel: [    0.000000]   3 disabled
Nov  5 04:09:21 node-1 kernel: [    0.000000]   4 disabled
Nov  5 04:09:21 node-1 kernel: [    0.000000]   5 disabled
Nov  5 04:09:21 node-1 kernel: [    0.000000]   6 disabled
Nov  5 04:09:21 node-1 kernel: [    0.000000]   7 disabled
Nov  5 04:09:21 node-1 kernel: [    0.000000]   8 disabled
Nov  5 04:09:21 node-1 kernel: [    0.000000]   9 disabled
Nov  5 04:09:21 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov  5 04:09:21 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov  5 04:09:21 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov  5 04:09:21 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov  5 04:09:21 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov  5 04:09:21 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Nov  5 04:09:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov  5 04:09:21 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov  5 04:09:21 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov  5 04:09:21 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov  5 04:09:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov  5 04:09:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov  5 04:09:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov  5 04:09:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Nov  5 04:09:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov  5 04:09:21 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov  5 04:09:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov  5 04:09:21 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov  5 04:09:21 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov  5 04:09:21 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov  5 04:09:21 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov  5 04:09:21 node-1 kernel: [    0.000000] Zone ranges:
Nov  5 04:09:21 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] Movable zone start for each node
Nov  5 04:09:21 node-1 kernel: [    0.000000] Early memory node ranges
Nov  5 04:09:21 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Nov  5 04:09:21 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov  5 04:09:21 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov  5 04:09:21 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov  5 04:09:21 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Nov  5 04:09:21 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Nov  5 04:09:21 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov  5 04:09:21 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov  5 04:09:21 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov  5 04:09:21 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov  5 04:09:21 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov  5 04:09:21 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov  5 04:09:21 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov  5 04:09:21 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov  5 04:09:21 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov  5 04:09:21 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov  5 04:09:21 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov  5 04:09:21 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov  5 04:09:21 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov  5 04:09:21 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov  5 04:09:21 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov  5 04:09:21 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov  5 04:09:21 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov  5 04:09:21 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  5 04:09:21 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Nov  5 04:09:21 node-1 kernel: [    0.000000] Policy zone: Normal
Nov  5 04:09:21 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=5be8bcbe-3230-4ac3-8946-1216b263369e nomdmonddf nomdmonisw
Nov  5 04:09:21 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov  5 04:09:21 node-1 kernel: [    0.000000] Checking aperture...
Nov  5 04:09:21 node-1 kernel: [    0.000000] No AGP bridge found
Nov  5 04:09:21 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov  5 04:09:21 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov  5 04:09:21 node-1 kernel: [    0.000000] Memory: 32653312K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627184K reserved)
Nov  5 04:09:21 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov  5 04:09:21 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Nov  5 04:09:21 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov  5 04:09:21 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov  5 04:09:21 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov  5 04:09:21 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov  5 04:09:21 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov  5 04:09:21 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Nov  5 04:09:21 node-1 kernel: [    0.000000] console [tty0] enabled
Nov  5 04:09:21 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov  5 04:09:21 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov  5 04:09:21 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov  5 04:09:21 node-1 kernel: [    0.000000] hpet clockevent registered
Nov  5 04:09:21 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov  5 04:09:21 node-1 kernel: [    0.004000] tsc: Detected 3492.303 MHz processor
Nov  5 04:09:21 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.60 BogoMIPS (lpj=13969212)
Nov  5 04:09:21 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov  5 04:09:21 node-1 kernel: [    0.000043] Security Framework initialized
Nov  5 04:09:21 node-1 kernel: [    0.000060] AppArmor: AppArmor initialized
Nov  5 04:09:21 node-1 kernel: [    0.000062] Yama: becoming mindful.
Nov  5 04:09:21 node-1 kernel: [    0.001463] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.006385] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.008309] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.008337] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.008624] Initializing cgroup subsys memory
Nov  5 04:09:21 node-1 kernel: [    0.008632] Initializing cgroup subsys devices
Nov  5 04:09:21 node-1 kernel: [    0.008634] Initializing cgroup subsys freezer
Nov  5 04:09:21 node-1 kernel: [    0.008635] Initializing cgroup subsys blkio
Nov  5 04:09:21 node-1 kernel: [    0.008637] Initializing cgroup subsys perf_event
Nov  5 04:09:21 node-1 kernel: [    0.008639] Initializing cgroup subsys hugetlb
Nov  5 04:09:21 node-1 kernel: [    0.008659] CPU: Physical Processor ID: 0
Nov  5 04:09:21 node-1 kernel: [    0.008660] CPU: Processor Core ID: 0
Nov  5 04:09:21 node-1 kernel: [    0.008664] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov  5 04:09:21 node-1 kernel: [    0.008664] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov  5 04:09:21 node-1 kernel: [    0.009358] mce: CPU supports 22 MCE banks
Nov  5 04:09:21 node-1 kernel: [    0.009385] CPU0: Thermal monitoring enabled (TM1)
Nov  5 04:09:21 node-1 kernel: [    0.009406] process: using mwait in idle threads
Nov  5 04:09:21 node-1 kernel: [    0.009409] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov  5 04:09:21 node-1 kernel: [    0.009409] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov  5 04:09:21 node-1 kernel: [    0.009409] tlb_flushall_shift: 6
Nov  5 04:09:21 node-1 kernel: [    0.009498] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov  5 04:09:21 node-1 kernel: [    0.010220] ACPI: Core revision 20131115
Nov  5 04:09:21 node-1 kernel: [    0.023012] ACPI: All ACPI Tables successfully acquired
Nov  5 04:09:21 node-1 kernel: [    0.023172] ftrace: allocating 28622 entries in 112 pages
Nov  5 04:09:21 node-1 kernel: [    0.031929] dmar: Host address width 46
Nov  5 04:09:21 node-1 kernel: [    0.031931] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov  5 04:09:21 node-1 kernel: [    0.031937] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  5 04:09:21 node-1 kernel: [    0.031939] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov  5 04:09:21 node-1 kernel: [    0.031943] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  5 04:09:21 node-1 kernel: [    0.031945] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov  5 04:09:21 node-1 kernel: [    0.031946] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov  5 04:09:21 node-1 kernel: [    0.031947] dmar: ATSR flags: 0x0
Nov  5 04:09:21 node-1 kernel: [    0.031948] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov  5 04:09:21 node-1 kernel: [    0.031950] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov  5 04:09:21 node-1 kernel: [    0.032065] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov  5 04:09:21 node-1 kernel: [    0.032066] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov  5 04:09:21 node-1 kernel: [    0.032067] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov  5 04:09:21 node-1 kernel: [    0.032069] HPET id 0 under DRHD base 0xc7ffc000
Nov  5 04:09:21 node-1 kernel: [    0.032070] Your BIOS is broken and requested that x2apic be disabled.
Nov  5 04:09:21 node-1 kernel: [    0.032070] This will slightly decrease performance.
Nov  5 04:09:21 node-1 kernel: [    0.032070] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov  5 04:09:21 node-1 kernel: [    0.032503] Enabled IRQ remapping in xapic mode
Nov  5 04:09:21 node-1 kernel: [    0.032504] x2apic not enabled, IRQ remapping is in xapic mode
Nov  5 04:09:21 node-1 kernel: [    0.032508] Switched APIC routing to physical flat.
Nov  5 04:09:21 node-1 kernel: [    0.033126] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov  5 04:09:21 node-1 kernel: [    0.072780] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov  5 04:09:21 node-1 kernel: [    0.072786] TSC deadline timer enabled
Nov  5 04:09:21 node-1 kernel: [    0.072793] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov  5 04:09:21 node-1 kernel: [    0.072799] ... version:                3
Nov  5 04:09:21 node-1 kernel: [    0.072800] ... bit width:              48
Nov  5 04:09:21 node-1 kernel: [    0.072801] ... generic registers:      4
Nov  5 04:09:21 node-1 kernel: [    0.072802] ... value mask:             0000ffffffffffff
Nov  5 04:09:21 node-1 kernel: [    0.072803] ... max period:             0000ffffffffffff
Nov  5 04:09:21 node-1 kernel: [    0.072804] ... fixed-purpose events:   3
Nov  5 04:09:21 node-1 kernel: [    0.072805] ... event mask:             000000070000000f
Nov  5 04:09:21 node-1 kernel: [    0.074235] x86: Booting SMP configuration:
Nov  5 04:09:21 node-1 kernel: [    0.088342] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov  5 04:09:21 node-1 kernel: [    0.074237] .... node  #0, CPUs:        #1  #2  #3
Nov  5 04:09:21 node-1 kernel: [    0.116260] .... node  #1, CPUs:    #4  #5  #6  #7
Nov  5 04:09:21 node-1 kernel: [    0.270416] .... node  #0, CPUs:    #8  #9 #10 #11
Nov  5 04:09:21 node-1 kernel: [    0.326039] .... node  #1, CPUs:   #12 #13 #14 #15
Nov  5 04:09:21 node-1 kernel: [    0.382894] x86: Booted up 2 nodes, 16 CPUs
Nov  5 04:09:21 node-1 kernel: [    0.382898] smpboot: Total of 16 processors activated (111765.70 BogoMIPS)
Nov  5 04:09:21 node-1 kernel: [    0.407702] devtmpfs: initialized
Nov  5 04:09:21 node-1 kernel: [    0.410465] EVM: security.selinux
Nov  5 04:09:21 node-1 kernel: [    0.410467] EVM: security.SMACK64
Nov  5 04:09:21 node-1 kernel: [    0.410468] EVM: security.ima
Nov  5 04:09:21 node-1 kernel: [    0.410469] EVM: security.capability
Nov  5 04:09:21 node-1 kernel: [    0.410518] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.411165] pinctrl core: initialized pinctrl subsystem
Nov  5 04:09:21 node-1 kernel: [    0.411239] regulator-dummy: no parameters
Nov  5 04:09:21 node-1 kernel: [    0.411271] RTC time:  4:08:44, date: 11/05/16
Nov  5 04:09:21 node-1 kernel: [    0.411305] NET: Registered protocol family 16
Nov  5 04:09:21 node-1 kernel: [    0.411387] cpuidle: using governor ladder
Nov  5 04:09:21 node-1 kernel: [    0.411388] cpuidle: using governor menu
Nov  5 04:09:21 node-1 kernel: [    0.411423] ACPI: bus type PCI registered
Nov  5 04:09:21 node-1 kernel: [    0.411425] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov  5 04:09:21 node-1 kernel: [    0.411470] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov  5 04:09:21 node-1 kernel: [    0.411473] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov  5 04:09:21 node-1 kernel: [    0.425202] PCI: Using configuration type 1 for base access
Nov  5 04:09:21 node-1 kernel: [    0.426201] bio: create slab <bio-0> at 0
Nov  5 04:09:21 node-1 kernel: [    0.426467] ACPI: Added _OSI(Module Device)
Nov  5 04:09:21 node-1 kernel: [    0.426469] ACPI: Added _OSI(Processor Device)
Nov  5 04:09:21 node-1 kernel: [    0.426470] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov  5 04:09:21 node-1 kernel: [    0.426471] ACPI: Added _OSI(Processor Aggregator Device)
Nov  5 04:09:21 node-1 kernel: [    0.439168] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov  5 04:09:21 node-1 kernel: [    0.449675] ACPI: Interpreter enabled
Nov  5 04:09:21 node-1 kernel: [    0.449681] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov  5 04:09:21 node-1 kernel: [    0.449685] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov  5 04:09:21 node-1 kernel: [    0.449688] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov  5 04:09:21 node-1 kernel: [    0.449694] ACPI: (supports S0 S4 S5)
Nov  5 04:09:21 node-1 kernel: [    0.449696] ACPI: Using IOAPIC for interrupt routing
Nov  5 04:09:21 node-1 kernel: [    0.449738] HEST: Table parsing has been initialized.
Nov  5 04:09:21 node-1 kernel: [    0.449741] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov  5 04:09:21 node-1 kernel: [    0.450294] ACPI: No dock devices found.
Nov  5 04:09:21 node-1 kernel: [    0.461922] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov  5 04:09:21 node-1 kernel: [    0.461927] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 04:09:21 node-1 kernel: [    0.461930] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  5 04:09:21 node-1 kernel: [    0.461960] PCI host bridge to bus 0000:ff
Nov  5 04:09:21 node-1 kernel: [    0.461962] pci_bus 0000:ff: root bus resource [bus ff]
Nov  5 04:09:21 node-1 kernel: [    0.461970] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462009] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.462039] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462075] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462105] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.462134] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.462165] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462195] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462226] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462256] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462282] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462309] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462337] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462363] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462390] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462417] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462446] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462473] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462500] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.462528] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462554] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.462579] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462605] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462636] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.462671] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462702] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462732] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462762] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462793] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462824] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462858] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462890] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462922] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462955] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.462987] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463020] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463053] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463083] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463111] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463144] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463176] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463212] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463245] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463278] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463308] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463337] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463367] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463397] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463429] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463459] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463490] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463519] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463547] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463575] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463606] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463637] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463669] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463725] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov  5 04:09:21 node-1 kernel: [    0.463728] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 04:09:21 node-1 kernel: [    0.463731] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  5 04:09:21 node-1 kernel: [    0.463749] PCI host bridge to bus 0000:7f
Nov  5 04:09:21 node-1 kernel: [    0.463750] pci_bus 0000:7f: root bus resource [bus 7f]
Nov  5 04:09:21 node-1 kernel: [    0.463755] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463782] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.463810] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463839] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463861] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.463885] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.463911] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463936] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463964] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.463988] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464012] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464036] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464062] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464085] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464109] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464134] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464155] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464178] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464200] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.464224] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464246] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.464267] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464290] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464318] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov  5 04:09:21 node-1 kernel: [    0.464351] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464377] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464404] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464431] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464456] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464482] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464508] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464536] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464563] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464592] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464620] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464648] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464678] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464704] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464731] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464761] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464787] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464814] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464844] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464872] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464896] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464921] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464948] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.464976] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.465002] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.465029] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.465058] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.465083] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.465106] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.465131] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.465157] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.465185] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.465211] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.466465] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov  5 04:09:21 node-1 kernel: [    0.466468] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 04:09:21 node-1 kernel: [    0.467587] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  5 04:09:21 node-1 kernel: [    0.468101] PCI host bridge to bus 0000:00
Nov  5 04:09:21 node-1 kernel: [    0.468103] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov  5 04:09:21 node-1 kernel: [    0.468105] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov  5 04:09:21 node-1 kernel: [    0.468106] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov  5 04:09:21 node-1 kernel: [    0.468108] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov  5 04:09:21 node-1 kernel: [    0.468109] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov  5 04:09:21 node-1 kernel: [    0.468110] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov  5 04:09:21 node-1 kernel: [    0.468112] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov  5 04:09:21 node-1 kernel: [    0.468117] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov  5 04:09:21 node-1 kernel: [    0.468200] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.468231] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.468273] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov  5 04:09:21 node-1 kernel: [    0.468293] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.468322] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.468362] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov  5 04:09:21 node-1 kernel: [    0.468381] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.468410] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.468453] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov  5 04:09:21 node-1 kernel: [    0.468471] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.468542] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.468620] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.468699] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov  5 04:09:21 node-1 kernel: [    0.468704] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov  5 04:09:21 node-1 kernel: [    0.468789] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov  5 04:09:21 node-1 kernel: [    0.468938] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov  5 04:09:21 node-1 kernel: [    0.468956] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov  5 04:09:21 node-1 kernel: [    0.469034] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.469089] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov  5 04:09:21 node-1 kernel: [    0.469112] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.469167] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.469210] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov  5 04:09:21 node-1 kernel: [    0.469239] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.469294] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.469337] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov  5 04:09:21 node-1 kernel: [    0.469365] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov  5 04:09:21 node-1 kernel: [    0.469382] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov  5 04:09:21 node-1 kernel: [    0.469460] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.469510] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov  5 04:09:21 node-1 kernel: [    0.469537] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov  5 04:09:21 node-1 kernel: [    0.469785] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov  5 04:09:21 node-1 kernel: [    0.469791] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov  5 04:09:21 node-1 kernel: [    0.469797] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.469803] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.469810] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov  5 04:09:21 node-1 kernel: [    0.469840] pci 0000:01:00.0: supports D1 D2
Nov  5 04:09:21 node-1 kernel: [    0.479969] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  5 04:09:21 node-1 kernel: [    0.479975] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  5 04:09:21 node-1 kernel: [    0.479979] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  5 04:09:21 node-1 kernel: [    0.480102] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.480136] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov  5 04:09:21 node-1 kernel: [    0.491965] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  5 04:09:21 node-1 kernel: [    0.491967] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.491969] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 04:09:21 node-1 kernel: [    0.492023] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.492091] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.492167] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.492213] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  5 04:09:21 node-1 kernel: [    0.492217] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.492218] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 04:09:21 node-1 kernel: [    0.492271] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.492393] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.492451] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  5 04:09:21 node-1 kernel: [    0.492454] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.492456] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 04:09:21 node-1 kernel: [    0.492505] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.492624] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.492666] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.492813] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.492851] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.492975] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.493013] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov  5 04:09:21 node-1 kernel: [    0.493136] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov  5 04:09:21 node-1 kernel: [    0.493178] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  5 04:09:21 node-1 kernel: [    0.493181] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.493183] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 04:09:21 node-1 kernel: [    0.493250] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov  5 04:09:21 node-1 kernel: [    0.493315] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.493366] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.493406] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov  5 04:09:21 node-1 kernel: [    0.493489] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov  5 04:09:21 node-1 kernel: [    0.493607] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  5 04:09:21 node-1 kernel: [    0.493610] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.493612] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  5 04:09:21 node-1 kernel: [    0.493668] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov  5 04:09:21 node-1 kernel: [    0.493742] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.493789] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.494001] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  5 04:09:21 node-1 kernel: [    0.494004] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  5 04:09:21 node-1 kernel: [    0.494069] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov  5 04:09:21 node-1 kernel: [    0.494123] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.494171] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.494381] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  5 04:09:21 node-1 kernel: [    0.494385] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  5 04:09:21 node-1 kernel: [    0.494444] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov  5 04:09:21 node-1 kernel: [    0.494504] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.494558] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov  5 04:09:21 node-1 kernel: [    0.494807] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  5 04:09:21 node-1 kernel: [    0.494811] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  5 04:09:21 node-1 kernel: [    0.494986] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  5 04:09:21 node-1 kernel: [    0.495024] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  5 04:09:21 node-1 kernel: [    0.495100] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov  5 04:09:21 node-1 kernel: [    0.495118] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov  5 04:09:21 node-1 kernel: [    0.495131] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov  5 04:09:21 node-1 kernel: [    0.495144] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov  5 04:09:21 node-1 kernel: [    0.495194] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov  5 04:09:21 node-1 kernel: [    0.499981] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  5 04:09:21 node-1 kernel: [    0.499990] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  5 04:09:21 node-1 kernel: [    0.500042] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov  5 04:09:21 node-1 kernel: [    0.500552] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov  5 04:09:21 node-1 kernel: [    0.500555] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 04:09:21 node-1 kernel: [    0.500681] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  5 04:09:21 node-1 kernel: [    0.500788] PCI host bridge to bus 0000:80
Nov  5 04:09:21 node-1 kernel: [    0.500790] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov  5 04:09:21 node-1 kernel: [    0.500791] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov  5 04:09:21 node-1 kernel: [    0.500793] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov  5 04:09:21 node-1 kernel: [    0.500801] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.500867] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.500936] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov  5 04:09:21 node-1 kernel: [    0.500998] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov  5 04:09:21 node-1 kernel: [    0.501003] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov  5 04:09:21 node-1 kernel: [    0.501077] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov  5 04:09:21 node-1 kernel: [    0.501377] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov  5 04:09:21 node-1 kernel: [    0.501408] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov  5 04:09:21 node-1 kernel: [    0.501438] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov  5 04:09:21 node-1 kernel: [    0.501467] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov  5 04:09:21 node-1 kernel: [    0.501497] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 04:09:21 node-1 kernel: [    0.501526] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 04:09:21 node-1 kernel: [    0.501556] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 04:09:21 node-1 kernel: [    0.501586] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 04:09:21 node-1 kernel: [    0.501672] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov  5 04:09:21 node-1 kernel: [    0.501676] ACPI: \_SB_.UNC1: notify handler is installed
Nov  5 04:09:21 node-1 kernel: [    0.501677] ACPI: \_SB_.UNC0: notify handler is installed
Nov  5 04:09:21 node-1 kernel: [    0.501692] ACPI: \_SB_.PCI0: notify handler is installed
Nov  5 04:09:21 node-1 kernel: [    0.501745] ACPI: \_SB_.PCI1: notify handler is installed
Nov  5 04:09:21 node-1 kernel: [    0.501825] Found 4 acpi root devices
Nov  5 04:09:21 node-1 kernel: [    0.501944] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov  5 04:09:21 node-1 kernel: [    0.501946] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov  5 04:09:21 node-1 kernel: [    0.501947] vgaarb: loaded
Nov  5 04:09:21 node-1 kernel: [    0.501949] vgaarb: bridge control possible 0000:0c:00.0
Nov  5 04:09:21 node-1 kernel: [    0.502072] SCSI subsystem initialized
Nov  5 04:09:21 node-1 kernel: [    0.502135] libata version 3.00 loaded.
Nov  5 04:09:21 node-1 kernel: [    0.502151] ACPI: bus type USB registered
Nov  5 04:09:21 node-1 kernel: [    0.502161] usbcore: registered new interface driver usbfs
Nov  5 04:09:21 node-1 kernel: [    0.502166] usbcore: registered new interface driver hub
Nov  5 04:09:21 node-1 kernel: [    0.502187] usbcore: registered new device driver usb
Nov  5 04:09:21 node-1 kernel: [    0.502363] PCI: Using ACPI for IRQ routing
Nov  5 04:09:21 node-1 kernel: [    0.505970] PCI: pci_cache_line_size set to 64 bytes
Nov  5 04:09:21 node-1 kernel: [    0.506180] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov  5 04:09:21 node-1 kernel: [    0.506181] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Nov  5 04:09:21 node-1 kernel: [    0.506182] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov  5 04:09:21 node-1 kernel: [    0.506247] NetLabel: Initializing
Nov  5 04:09:21 node-1 kernel: [    0.506249] NetLabel:  domain hash size = 128
Nov  5 04:09:21 node-1 kernel: [    0.506250] NetLabel:  protocols = UNLABELED CIPSOv4
Nov  5 04:09:21 node-1 kernel: [    0.506259] NetLabel:  unlabeled traffic allowed by default
Nov  5 04:09:21 node-1 kernel: [    0.506316] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov  5 04:09:21 node-1 kernel: [    0.506320] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov  5 04:09:21 node-1 kernel: [    0.508376] Switched to clocksource hpet
Nov  5 04:09:21 node-1 kernel: [    0.512260] AppArmor: AppArmor Filesystem Enabled
Nov  5 04:09:21 node-1 kernel: [    0.512274] pnp: PnP ACPI init
Nov  5 04:09:21 node-1 kernel: [    0.512281] ACPI: bus type PNP registered
Nov  5 04:09:21 node-1 kernel: [    0.512407] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov  5 04:09:21 node-1 kernel: [    0.512416] pnp 00:01: [dma 4]
Nov  5 04:09:21 node-1 kernel: [    0.512428] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov  5 04:09:21 node-1 kernel: [    0.512454] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov  5 04:09:21 node-1 kernel: [    0.512473] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov  5 04:09:21 node-1 kernel: [    0.512491] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov  5 04:09:21 node-1 kernel: [    0.512524] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov  5 04:09:21 node-1 kernel: [    0.512577] system 00:06: [io  0x0500-0x057f] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512579] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov  5 04:09:21 node-1 kernel: [    0.512581] system 00:06: [io  0x0580-0x059f] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512583] system 00:06: [io  0x0600-0x061f] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512584] system 00:06: [io  0x0880-0x0883] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512588] system 00:06: [io  0x0800-0x081f] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512591] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov  5 04:09:21 node-1 kernel: [    0.512592] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512594] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512595] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512597] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512598] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512600] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov  5 04:09:21 node-1 kernel: [    0.512602] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov  5 04:09:21 node-1 kernel: [    0.512685] pnp 00:07: [dma 0 disabled]
Nov  5 04:09:21 node-1 kernel: [    0.512714] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  5 04:09:21 node-1 kernel: [    0.512788] pnp 00:08: [dma 0 disabled]
Nov  5 04:09:21 node-1 kernel: [    0.512820] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  5 04:09:21 node-1 kernel: [    0.512871] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov  5 04:09:21 node-1 kernel: [    0.513217] pnp: PnP ACPI: found 10 devices
Nov  5 04:09:21 node-1 kernel: [    0.513218] ACPI: bus type PNP unregistered
Nov  5 04:09:21 node-1 kernel: [    0.519618] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  5 04:09:21 node-1 kernel: [    0.519620] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  5 04:09:21 node-1 kernel: [    0.519623] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  5 04:09:21 node-1 kernel: [    0.519627] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  5 04:09:21 node-1 kernel: [    0.519629] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.519644] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519687] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  5 04:09:21 node-1 kernel: [    0.519701] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519730] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  5 04:09:21 node-1 kernel: [    0.519744] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  5 04:09:21 node-1 kernel: [    0.519776] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  5 04:09:21 node-1 kernel: [    0.519790] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  5 04:09:21 node-1 kernel: [    0.519819] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  5 04:09:21 node-1 kernel: [    0.519821] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.519836] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519864] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  5 04:09:21 node-1 kernel: [    0.519866] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.519881] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519909] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  5 04:09:21 node-1 kernel: [    0.519911] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.519914] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519918] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  5 04:09:21 node-1 kernel: [    0.519920] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.519922] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519926] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  5 04:09:21 node-1 kernel: [    0.519931] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  5 04:09:21 node-1 kernel: [    0.519938] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  5 04:09:21 node-1 kernel: [    0.519942] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  5 04:09:21 node-1 kernel: [    0.519948] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov  5 04:09:21 node-1 kernel: [    0.519949] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov  5 04:09:21 node-1 kernel: [    0.519950] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov  5 04:09:21 node-1 kernel: [    0.519951] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov  5 04:09:21 node-1 kernel: [    0.519952] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov  5 04:09:21 node-1 kernel: [    0.519953] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov  5 04:09:21 node-1 kernel: [    0.519954] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov  5 04:09:21 node-1 kernel: [    0.519954] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov  5 04:09:21 node-1 kernel: [    0.519955] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.519956] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519957] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.519958] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519959] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.519960] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519961] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.519961] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519962] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov  5 04:09:21 node-1 kernel: [    0.519963] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519964] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov  5 04:09:21 node-1 kernel: [    0.519965] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov  5 04:09:21 node-1 kernel: [    0.519966] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov  5 04:09:21 node-1 kernel: [    0.519967] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov  5 04:09:21 node-1 kernel: [    0.519969] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov  5 04:09:21 node-1 kernel: [    0.519970] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov  5 04:09:21 node-1 kernel: [    0.520005] NET: Registered protocol family 2
Nov  5 04:09:21 node-1 kernel: [    0.520264] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.520609] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.520755] TCP: Hash tables configured (established 262144 bind 65536)
Nov  5 04:09:21 node-1 kernel: [    0.520792] TCP: reno registered
Nov  5 04:09:21 node-1 kernel: [    0.520820] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.520917] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.521065] NET: Registered protocol family 1
Nov  5 04:09:21 node-1 kernel: [    0.560473] pci 0000:0c:00.0: Video device with shadowed ROM
Nov  5 04:09:21 node-1 kernel: [    0.560487] PCI: CLS 64 bytes, default 64
Nov  5 04:09:21 node-1 kernel: [    0.560564] Trying to unpack rootfs image as initramfs...
Nov  5 04:09:21 node-1 kernel: [    0.780365] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Nov  5 04:09:21 node-1 kernel: [    0.780426] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov  5 04:09:21 node-1 kernel: [    0.780429] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Nov  5 04:09:21 node-1 kernel: [    0.780858] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780864] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780869] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780875] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780884] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780895] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780904] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780913] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780921] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780930] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780937] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780943] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780949] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780957] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780965] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.780973] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 04:09:21 node-1 kernel: [    0.781013] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov  5 04:09:21 node-1 kernel: [    0.781017] Scanning for low memory corruption every 60 seconds
Nov  5 04:09:21 node-1 kernel: [    0.781331] Initialise system trusted keyring
Nov  5 04:09:21 node-1 kernel: [    0.781375] audit: initializing netlink socket (disabled)
Nov  5 04:09:21 node-1 kernel: [    0.781385] type=2000 audit(1478318924.736:1): initialized
Nov  5 04:09:21 node-1 kernel: [    0.799089] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov  5 04:09:21 node-1 kernel: [    0.800545] zbud: loaded
Nov  5 04:09:21 node-1 kernel: [    0.800657] VFS: Disk quotas dquot_6.5.2
Nov  5 04:09:21 node-1 kernel: [    0.800699] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov  5 04:09:21 node-1 kernel: [    0.801077] fuse init (API version 7.22)
Nov  5 04:09:21 node-1 kernel: [    0.801134] msgmni has been set to 32768
Nov  5 04:09:21 node-1 kernel: [    0.801181] Key type big_key registered
Nov  5 04:09:21 node-1 kernel: [    0.801735] Key type asymmetric registered
Nov  5 04:09:21 node-1 kernel: [    0.801737] Asymmetric key parser 'x509' registered
Nov  5 04:09:21 node-1 kernel: [    0.801760] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov  5 04:09:21 node-1 kernel: [    0.801821] io scheduler noop registered
Nov  5 04:09:21 node-1 kernel: [    0.801823] io scheduler deadline registered (default)
Nov  5 04:09:21 node-1 kernel: [    0.801843] io scheduler cfq registered
Nov  5 04:09:21 node-1 kernel: [    0.802164] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    0.802256] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    0.802344] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    0.802431] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    0.802527] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    0.802595] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    0.802864] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov  5 04:09:21 node-1 kernel: [    0.802883] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov  5 04:09:21 node-1 kernel: [    0.802895] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov  5 04:09:21 node-1 kernel: [    0.802905] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802907] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802909] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov  5 04:09:21 node-1 kernel: [    0.802913] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802915] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802916] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802917] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802919] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802920] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802922] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802923] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802924] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802926] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802927] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802929] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802931] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov  5 04:09:21 node-1 kernel: [    0.802935] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802937] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov  5 04:09:21 node-1 kernel: [    0.802945] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802948] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov  5 04:09:21 node-1 kernel: [    0.802958] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802960] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov  5 04:09:21 node-1 kernel: [    0.802963] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov  5 04:09:21 node-1 kernel: [    0.802975] ioapic: probe of 0000:00:05.4 failed with error -22
Nov  5 04:09:21 node-1 kernel: [    0.803089] ioapic: probe of 0000:80:05.4 failed with error -22
Nov  5 04:09:21 node-1 kernel: [    0.803093] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov  5 04:09:21 node-1 kernel: [    0.803101] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov  5 04:09:21 node-1 kernel: [    0.803138] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov  5 04:09:21 node-1 kernel: [    0.803139] vesafb: scrolling: redraw
Nov  5 04:09:21 node-1 kernel: [    0.803141] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov  5 04:09:21 node-1 kernel: [    0.824117] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov  5 04:09:21 node-1 kernel: [    0.832641] Console: switching to colour frame buffer device 80x30
Nov  5 04:09:21 node-1 kernel: [    0.841317] fb0: VESA VGA frame buffer device
Nov  5 04:09:21 node-1 kernel: [    0.841515] intel_idle: MWAIT substates: 0x2120
Nov  5 04:09:21 node-1 kernel: [    0.841516] intel_idle: v0.4 model 0x3F
Nov  5 04:09:21 node-1 kernel: [    0.841517] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov  5 04:09:21 node-1 kernel: [    0.841742] ipmi message handler version 39.2
Nov  5 04:09:21 node-1 kernel: [    0.842021] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov  5 04:09:21 node-1 kernel: [    0.842459] ACPI: AC Adapter [P111] (on-line)
Nov  5 04:09:21 node-1 kernel: [    0.847740] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov  5 04:09:21 node-1 kernel: [    0.858838] ACPI: Power Button [PWRB]
Nov  5 04:09:21 node-1 kernel: [    0.864641] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov  5 04:09:21 node-1 kernel: [    0.876355] ACPI: Power Button [PWRF]
Nov  5 04:09:21 node-1 kernel: [    0.893887] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov  5 04:09:21 node-1 kernel: [    0.905655] pstore: Registered erst as persistent store backend
Nov  5 04:09:21 node-1 kernel: [    0.911918] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov  5 04:09:21 node-1 kernel: [    0.924031] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov  5 04:09:21 node-1 kernel: [    0.950878] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov  5 04:09:21 node-1 kernel: [    0.984293] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov  5 04:09:21 node-1 kernel: [    0.998550] Linux agpgart interface v0.103
Nov  5 04:09:21 node-1 kernel: [    1.006274] brd: module loaded
Nov  5 04:09:21 node-1 kernel: [    1.013358] loop: module loaded
Nov  5 04:09:21 node-1 kernel: [    1.020135] libphy: Fixed MDIO Bus: probed
Nov  5 04:09:21 node-1 kernel: [    1.026655] tun: Universal TUN/TAP device driver, 1.6
Nov  5 04:09:21 node-1 kernel: [    1.033161] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov  5 04:09:21 node-1 kernel: [    1.039679] PPP generic driver version 2.4.2
Nov  5 04:09:21 node-1 kernel: [    1.046066] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov  5 04:09:21 node-1 kernel: [    1.052517] ehci-pci: EHCI PCI platform driver
Nov  5 04:09:21 node-1 kernel: [    1.059124] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov  5 04:09:21 node-1 kernel: [    1.065550] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov  5 04:09:21 node-1 kernel: [    1.078105] ehci-pci 0000:00:1a.0: debug port 2
Nov  5 04:09:21 node-1 kernel: [    1.088311] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov  5 04:09:21 node-1 kernel: [    1.088331] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov  5 04:09:21 node-1 kernel: [    1.103876] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov  5 04:09:21 node-1 kernel: [    1.109966] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov  5 04:09:21 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov  5 04:09:21 node-1 kernel: [    1.116132] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  5 04:09:21 node-1 kernel: [    1.128042] usb usb1: Product: EHCI Host Controller
Nov  5 04:09:21 node-1 kernel: [    1.134160] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  5 04:09:21 node-1 kernel: [    1.140215] usb usb1: SerialNumber: 0000:00:1a.0
Nov  5 04:09:21 node-1 kernel: [    1.146181] hub 1-0:1.0: USB hub found
Nov  5 04:09:21 node-1 kernel: [    1.151971] hub 1-0:1.0: 2 ports detected
Nov  5 04:09:21 node-1 kernel: [    1.157775] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov  5 04:09:21 node-1 kernel: [    1.163366] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov  5 04:09:21 node-1 kernel: [    1.174288] ehci-pci 0000:00:1d.0: debug port 2
Nov  5 04:09:21 node-1 kernel: [    1.183595] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov  5 04:09:21 node-1 kernel: [    1.183598] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov  5 04:09:21 node-1 kernel: [    1.199795] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov  5 04:09:21 node-1 kernel: [    1.205002] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov  5 04:09:21 node-1 kernel: [    1.210315] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  5 04:09:21 node-1 kernel: [    1.220888] usb usb2: Product: EHCI Host Controller
Nov  5 04:09:21 node-1 kernel: [    1.226352] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  5 04:09:21 node-1 kernel: [    1.231927] usb usb2: SerialNumber: 0000:00:1d.0
Nov  5 04:09:21 node-1 kernel: [    1.237460] hub 2-0:1.0: USB hub found
Nov  5 04:09:21 node-1 kernel: [    1.242818] hub 2-0:1.0: 2 ports detected
Nov  5 04:09:21 node-1 kernel: [    1.248124] ehci-platform: EHCI generic platform driver
Nov  5 04:09:21 node-1 kernel: [    1.253364] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov  5 04:09:21 node-1 kernel: [    1.258689] ohci-pci: OHCI PCI platform driver
Nov  5 04:09:21 node-1 kernel: [    1.263994] ohci-platform: OHCI generic platform driver
Nov  5 04:09:21 node-1 kernel: [    1.269193] uhci_hcd: USB Universal Host Controller Interface driver
Nov  5 04:09:21 node-1 kernel: [    1.274544] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov  5 04:09:21 node-1 kernel: [    1.467576] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov  5 04:09:21 node-1 kernel: [    1.639729] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov  5 04:09:21 node-1 kernel: [    1.645255] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  5 04:09:21 node-1 kernel: [    1.650992] hub 1-1:1.0: USB hub found
Nov  5 04:09:21 node-1 kernel: [    1.656466] hub 1-1:1.0: 6 ports detected
Nov  5 04:09:21 node-1 kernel: [    1.771309] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov  5 04:09:21 node-1 kernel: [    1.779352] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov  5 04:09:21 node-1 kernel: [    2.039391] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov  5 04:09:21 node-1 kernel: [    2.044931] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  5 04:09:21 node-1 kernel: [    2.050784] hub 2-1:1.0: USB hub found
Nov  5 04:09:21 node-1 kernel: [    2.056504] hub 2-1:1.0: 8 ports detected
Nov  5 04:09:21 node-1 kernel: [    2.315988] i8042: No controller found
Nov  5 04:09:21 node-1 kernel: [    2.321372] mousedev: PS/2 mouse device common for all mice
Nov  5 04:09:21 node-1 kernel: [    2.326908] rtc_cmos 00:02: RTC can wake from S4
Nov  5 04:09:21 node-1 kernel: [    2.332475] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov  5 04:09:21 node-1 kernel: [    2.334909] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov  5 04:09:21 node-1 kernel: [    2.343644] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov  5 04:09:21 node-1 kernel: [    2.354773] device-mapper: uevent: version 1.0.3
Nov  5 04:09:21 node-1 kernel: [    2.360411] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov  5 04:09:21 node-1 kernel: [    2.371638] ledtrig-cpu: registered to indicate activity on CPUs
Nov  5 04:09:21 node-1 kernel: [    2.377570] TCP: cubic registered
Nov  5 04:09:21 node-1 kernel: [    2.383468] NET: Registered protocol family 10
Nov  5 04:09:21 node-1 kernel: [    2.389439] NET: Registered protocol family 17
Nov  5 04:09:21 node-1 kernel: [    2.395133] Key type dns_resolver registered
Nov  5 04:09:21 node-1 kernel: [    2.401113] Loading compiled-in X.509 certificates
Nov  5 04:09:21 node-1 kernel: [    2.407292] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov  5 04:09:21 node-1 kernel: [    2.418690] registered taskstats version 1
Nov  5 04:09:21 node-1 kernel: [    2.426639] Key type trusted registered
Nov  5 04:09:21 node-1 kernel: [    2.434201] Key type encrypted registered
Nov  5 04:09:21 node-1 kernel: [    2.439659] AppArmor: AppArmor sha1 policy hashing enabled
Nov  5 04:09:21 node-1 kernel: [    2.445149] IMA: No TPM chip found, activating TPM-bypass!
Nov  5 04:09:21 node-1 kernel: [    2.451290] regulator-dummy: disabling
Nov  5 04:09:21 node-1 kernel: [    2.456878]   Magic number: 8:890:109
Nov  5 04:09:21 node-1 kernel: [    2.462443] memory memory258: hash matches
Nov  5 04:09:21 node-1 kernel: [    2.467854] rtc_cmos 00:02: setting system clock to 2016-11-05 04:08:46 UTC (1478318926)
Nov  5 04:09:21 node-1 kernel: [    2.471353] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov  5 04:09:21 node-1 kernel: [    2.471356] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  5 04:09:21 node-1 kernel: [    2.471357] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov  5 04:09:21 node-1 kernel: [    2.471359] usb 2-1.4: Manufacturer: Avocent
Nov  5 04:09:21 node-1 kernel: [    2.471360] usb 2-1.4: SerialNumber: 20111102-00000001
Nov  5 04:09:21 node-1 kernel: [    2.514778] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov  5 04:09:21 node-1 kernel: [    2.520465] EDD information not available.
Nov  5 04:09:21 node-1 kernel: [    2.526032] PM: Hibernation image not present or could not be loaded.
Nov  5 04:09:21 node-1 kernel: [    2.526918] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov  5 04:09:21 node-1 kernel: [    2.538165] Write protecting the kernel read-only data: 12288k
Nov  5 04:09:21 node-1 kernel: [    2.544320] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov  5 04:09:21 node-1 kernel: [    2.556674] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov  5 04:09:21 node-1 kernel: [    2.589515] device-mapper: multipath: version 1.6.0 loaded
Nov  5 04:09:21 node-1 kernel: [    2.597679] systemd-udevd[216]: starting version 204
Nov  5 04:09:21 node-1 kernel: [    2.618402] md: linear personality registered for level -1
Nov  5 04:09:21 node-1 kernel: [    2.632377] md: multipath personality registered for level -4
Nov  5 04:09:21 node-1 kernel: [    2.640407] md: raid0 personality registered for level 0
Nov  5 04:09:21 node-1 kernel: [    2.648561] md: raid1 personality registered for level 1
Nov  5 04:09:21 node-1 kernel: [    2.657098] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov  5 04:09:21 node-1 kernel: [    2.663470] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov  5 04:09:21 node-1 kernel: [    2.663725] hidraw: raw HID events driver (C) Jiri Kosina
Nov  5 04:09:21 node-1 kernel: [    2.675620] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Nov  5 04:09:21 node-1 kernel: [    2.675621] 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  5 04:09:21 node-1 kernel: [    2.675642] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  5 04:09:21 node-1 kernel: [    2.676161] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.676347] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.676459] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.676538] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.676813] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.695499] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Nov  5 04:09:21 node-1 kernel: [    2.695540] 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  5 04:09:21 node-1 kernel: [    2.695577] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov  5 04:09:21 node-1 kernel: [    2.695856] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.695976] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.696053] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.696209] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.696355] enic 0000:07:00.0: irq 104 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.696488] enic 0000:07:00.0: irq 105 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.696723] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.718161] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Nov  5 04:09:21 node-1 kernel: [    2.718181] 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  5 04:09:21 node-1 kernel: [    2.718203] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  5 04:09:21 node-1 kernel: [    2.718457] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.718665] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.718801] enic 0000:08:00.0: irq 108 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.718915] enic 0000:08:00.0: irq 109 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.719049] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.730662] raid6: sse2x1    5499 MB/s
Nov  5 04:09:21 node-1 kernel: [    2.734718] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Nov  5 04:09:21 node-1 kernel: [    2.734742] 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  5 04:09:21 node-1 kernel: [    2.734743] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  5 04:09:21 node-1 kernel: [    2.735114] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.735252] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.735335] enic 0000:09:00.0: irq 112 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.735477] enic 0000:09:00.0: irq 113 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.735717] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  5 04:09:21 node-1 kernel: [    2.798689] raid6: sse2x2   12445 MB/s
Nov  5 04:09:21 node-1 kernel: [    2.866662] raid6: sse2x4    9587 MB/s
Nov  5 04:09:21 node-1 kernel: [    2.934338] raid6: avx2x1   14745 MB/s
Nov  5 04:09:21 node-1 kernel: [    3.006275] raid6: avx2x2   18853 MB/s
Nov  5 04:09:21 node-1 kernel: [    3.078210] raid6: avx2x4   21345 MB/s
Nov  5 04:09:21 node-1 kernel: [    3.084148] raid6: using algorithm avx2x4 (21345 MB/s)
Nov  5 04:09:21 node-1 kernel: [    3.090267] raid6: using avx2x2 recovery algorithm
Nov  5 04:09:21 node-1 kernel: [    3.096253] Switched to clocksource tsc
Nov  5 04:09:21 node-1 kernel: [    3.097094] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov  5 04:09:21 node-1 kernel: [    3.098911] megasas: FW now in Ready state
Nov  5 04:09:21 node-1 kernel: [    3.098966] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099002] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099032] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099066] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099099] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099136] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099173] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099212] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099251] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099288] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099316] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099349] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099387] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099423] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099467] megaraid_sas 0000:01:00.0: irq 128 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099498] megaraid_sas 0000:01:00.0: irq 129 for MSI/MSI-X
Nov  5 04:09:21 node-1 kernel: [    3.099673] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov  5 04:09:21 node-1 kernel: [    3.125746] xor: automatically using best checksumming function:
Nov  5 04:09:21 node-1 kernel: [    3.128044] usbcore: registered new interface driver usbhid
Nov  5 04:09:21 node-1 kernel: [    3.128044] usbhid: USB HID core driver
Nov  5 04:09:21 node-1 kernel: [    3.144060] 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  5 04:09:21 node-1 kernel: [    3.155606] 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  5 04:09:21 node-1 kernel: [    3.167278] 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  5 04:09:21 node-1 kernel: [    3.179400] 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  5 04:09:21 node-1 kernel: [    3.182159]    avx       : 35280.000 MB/sec
Nov  5 04:09:21 node-1 kernel: [    3.198085] 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  5 04:09:21 node-1 kernel: [    3.210526] async_tx: api initialized (async)
Nov  5 04:09:21 node-1 kernel: [    3.210687] 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  5 04:09:21 node-1 kernel: [    3.233229] md: raid6 personality registered for level 6
Nov  5 04:09:21 node-1 kernel: [    3.239691] md: raid5 personality registered for level 5
Nov  5 04:09:21 node-1 kernel: [    3.246152] md: raid4 personality registered for level 4
Nov  5 04:09:21 node-1 kernel: [    3.255602] md: raid10 personality registered for level 10
Nov  5 04:09:21 node-1 kernel: [    3.311273] multipathd (354): /proc/354/oom_adj is deprecated, please use /proc/354/oom_score_adj instead.
Nov  5 04:09:21 node-1 kernel: [    3.437943] megasas:IOC Init cmd success
Nov  5 04:09:21 node-1 kernel: [    3.465950] megasas: INIT adapter done
Nov  5 04:09:21 node-1 kernel: [    3.565839] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov  5 04:09:21 node-1 kernel: [    3.572721] scsi0 : LSI SAS based MegaRAID driver
Nov  5 04:09:21 node-1 kernel: [    3.580337] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  5 04:09:21 node-1 kernel: [    3.599116] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  5 04:09:21 node-1 kernel: [    3.614747] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov  5 04:09:21 node-1 kernel: [    3.621228] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov  5 04:09:21 node-1 kernel: [    3.633989] sd 0:2:0:0: [sda] Write Protect is off
Nov  5 04:09:21 node-1 kernel: [    3.640193] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov  5 04:09:21 node-1 kernel: [    3.640212] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov  5 04:09:21 node-1 kernel: [    3.686874]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Nov  5 04:09:21 node-1 kernel: [    3.693473] sd 0:2:0:0: [sda] Attached SCSI disk
Nov  5 04:09:21 node-1 kernel: [    3.826565] random: lvm urandom read with 31 bits of entropy available
Nov  5 04:09:21 node-1 kernel: [    3.949725] bio: create slab <bio-1> at 1
Nov  5 04:09:21 node-1 kernel: [    4.747878] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov  5 04:09:21 node-1 kernel: [    5.312686] init: plymouth-upstart-bridge main process (551) terminated with status 1
Nov  5 04:09:21 node-1 kernel: [    5.325110] init: plymouth-upstart-bridge main process ended, respawning
Nov  5 04:09:21 node-1 kernel: [    5.442259] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Nov  5 04:09:21 node-1 kernel: [    5.478954] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov  5 04:09:21 node-1 kernel: [    5.534176] random: nonblocking pool is initialized
Nov  5 04:09:21 node-1 kernel: [    5.607964] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov  5 04:09:21 node-1 kernel: [    5.661836] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov  5 04:09:21 node-1 kernel: [    5.780014] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov  5 04:09:21 node-1 kernel: [    5.955626] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov  5 04:09:21 node-1 kernel: [    5.994082] XFS (dm-0): Mounting Filesystem
Nov  5 04:09:21 node-1 kernel: [    6.243380] XFS (dm-0): Ending clean mount
Nov  5 04:09:21 node-1 kernel: [    6.298613] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Nov  5 04:09:21 node-1 kernel: [    6.326178] XFS (dm-1): Mounting Filesystem
Nov  5 04:09:21 node-1 kernel: [    6.452220] XFS (dm-1): Ending clean mount
Nov  5 04:09:21 node-1 kernel: [    8.343751] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Nov  5 04:09:21 node-1 kernel: [    8.367303] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Nov  5 04:09:21 node-1 kernel: [    8.548019] systemd-udevd[776]: starting version 204
Nov  5 04:09:21 node-1 kernel: [    8.775200] IPMI System Interface driver.
Nov  5 04:09:21 node-1 kernel: [    8.775264] ipmi_si: probing via ACPI
Nov  5 04:09:21 node-1 kernel: [    8.775279] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov  5 04:09:21 node-1 kernel: [    8.775280] ipmi_si: Adding ACPI-specified kcs state machine
Nov  5 04:09:21 node-1 kernel: [    8.775303] ipmi_si: probing via SMBIOS
Nov  5 04:09:21 node-1 kernel: [    8.775304] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov  5 04:09:21 node-1 kernel: [    8.775305] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov  5 04:09:21 node-1 kernel: [    8.775307] ipmi_si: probing via SPMI
Nov  5 04:09:21 node-1 kernel: [    8.775308] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov  5 04:09:21 node-1 kernel: [    8.775309] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov  5 04:09:21 node-1 kernel: [    8.775311] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov  5 04:09:21 node-1 kernel: [    8.819364] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov  5 04:09:21 node-1 kernel: [    8.819369] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  5 04:09:21 node-1 kernel: [    8.819372] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov  5 04:09:21 node-1 kernel: [    8.819373] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  5 04:09:21 node-1 kernel: [    8.819388] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov  5 04:09:21 node-1 kernel: [    8.825245] wmi: Mapper loaded
Nov  5 04:09:21 node-1 kernel: [    8.827892] power_meter ACPI000D:00: Found ACPI power meter.
Nov  5 04:09:21 node-1 kernel: [    8.827921] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov  5 04:09:21 node-1 kernel: [    8.834834] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov  5 04:09:21 node-1 kernel: [    8.897754] systemd-udevd[798]: renamed network interface eth1 to enp7s0
Nov  5 04:09:21 node-1 kernel: [    8.917025] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov  5 04:09:21 node-1 kernel: [    8.917031] ipmi_si 00:09: IPMI kcs interface initialized
Nov  5 04:09:21 node-1 kernel: [    8.921671] systemd-udevd[805]: renamed network interface eth3 to enp9s0
Nov  5 04:09:21 node-1 kernel: [    8.949617] systemd-udevd[796]: renamed network interface eth0 to enp6s0
Nov  5 04:09:21 node-1 kernel: [    8.977632] systemd-udevd[800]: renamed network interface eth2 to enp8s0
Nov  5 04:09:21 node-1 kernel: [    9.282072] type=1400 audit(1478318933.316:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=977 comm="apparmor_parser"
Nov  5 04:09:21 node-1 kernel: [    9.282225] type=1400 audit(1478318933.316:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=977 comm="apparmor_parser"
Nov  5 04:09:21 node-1 kernel: [    9.282355] type=1400 audit(1478318933.316:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=977 comm="apparmor_parser"
Nov  5 04:09:21 node-1 kernel: [    9.324283] type=1400 audit(1478318933.356:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=980 comm="apparmor_parser"
Nov  5 04:09:21 node-1 kernel: [    9.324520] type=1400 audit(1478318933.356:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=980 comm="apparmor_parser"
Nov  5 04:09:21 node-1 kernel: [    9.324728] type=1400 audit(1478318933.356:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=980 comm="apparmor_parser"
Nov  5 04:09:21 node-1 kernel: [    9.328750] type=1400 audit(1478318933.360:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1011 comm="apparmor_parser"
Nov  5 04:09:21 node-1 kernel: [    9.328900] type=1400 audit(1478318933.364:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1011 comm="apparmor_parser"
Nov  5 04:09:21 node-1 kernel: [    9.329022] type=1400 audit(1478318933.364:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1011 comm="apparmor_parser"
Nov  5 04:09:21 node-1 kernel: [    9.337652] type=1400 audit(1478318933.372:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=982 comm="apparmor_parser"
Nov  5 04:09:21 node-1 kernel: [    9.857258] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Nov  5 04:09:21 node-1 kernel: [    9.857988] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Nov  5 04:09:21 node-1 kernel: [   10.008132] enic 0000:06:00.0 enp6s0: Link UP
Nov  5 04:09:21 node-1 kernel: [   10.008554] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov  5 04:09:21 node-1 kernel: [   10.008559] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov  5 04:09:21 node-1 kernel: [   19.499171] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov  5 04:09:22 node-1 failsafe: Failsafe of 120 seconds reached.
Nov  5 04:09:23 node-1 kernel: [   38.230455] init: failsafe main process (8422) killed by TERM signal
Nov  5 04:09:23 node-1 dbus[8461]: [system] AppArmor D-Bus mediation is enabled
Nov  5 04:09:23 node-1 kernel: [   38.459503] audit_printk_skb: 30 callbacks suppressed
Nov  5 04:09:23 node-1 kernel: [   38.459504] type=1400 audit(1478318963.227:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8544 comm="apparmor_parser"
Nov  5 04:09:23 node-1 kernel: [   38.460084] type=1400 audit(1478318963.231:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8543 comm="apparmor_parser"
Nov  5 04:09:23 node-1 kernel: [   38.460143] type=1400 audit(1478318963.231:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8543 comm="apparmor_parser"
Nov  5 04:09:23 node-1 kernel: [   38.460151] type=1400 audit(1478318963.231:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Nov  5 04:09:23 node-1 kernel: [   38.461188] type=1400 audit(1478318963.231:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8543 comm="apparmor_parser"
Nov  5 04:09:23 node-1 kernel: [   38.461192] type=1400 audit(1478318963.231:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Nov  5 04:09:23 node-1 kernel: [   38.461537] type=1400 audit(1478318963.231:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8543 comm="apparmor_parser"
Nov  5 04:09:23 node-1 kernel: [   38.531873] type=1400 audit(1478318963.303:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8546 comm="apparmor_parser"
Nov  5 04:09:23 node-1 anacron[8614]: Anacron 2.3 started on 2016-11-05
Nov  5 04:09:23 node-1 cron[8580]: (CRON) INFO (pidfile fd = 3)
Nov  5 04:09:23 node-1 cron[8621]: (CRON) STARTUP (fork ok)
Nov  5 04:09:23 node-1 anacron[8614]: Will run job `cron.daily' in 5 min.
Nov  5 04:09:23 node-1 anacron[8614]: Will run job `cron.weekly' in 10 min.
Nov  5 04:09:23 node-1 anacron[8614]: Will run job `cron.monthly' in 15 min.
Nov  5 04:09:23 node-1 anacron[8614]: Jobs will be executed sequentially
Nov  5 04:09:23 node-1 multipathd: path checkers start up
Nov  5 04:09:23 node-1 cron[8621]: (CRON) INFO (Running @reboot jobs)
Nov  5 04:09:23 node-1 postfix/master[8759]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov  5 04:09:26 node-1 puppet-agent[8944]: Reopening log files
Nov  5 04:09:27 node-1 puppet-agent[8944]: Could not request certificate: Connection refused - connect(2)
Nov  5 04:09:41 node-1 puppet-user[9152]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov  5 04:09:41 node-1 puppet-user[9152]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Nov  5 04:09:43 node-1 puppet-user[9152]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov  5 04:09:43 node-1 puppet-user[9152]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov  5 04:09:43 node-1 puppet-user[9152]: Finished catalog run in 2.04 seconds
Nov  5 04:09:45 node-1 multipathd: uevent trigger error
Nov  5 04:09:45 node-1 puppet-user[9622]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  5 04:09:45 node-1 puppet-user[9622]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Nov  5 04:09:45 node-1 puppet-user[9622]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov  5 04:09:45 node-1 puppet-user[9622]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov  5 04:09:45 node-1 puppet-user[9622]: (/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  5 04:09:45 node-1 puppet-user[9622]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov  5 04:09:45 node-1 puppet-user[9622]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov  5 04:09:45 node-1 puppet-user[9622]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov  5 04:09:45 node-1 puppet-user[9622]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov  5 04:09:45 node-1 puppet-user[9622]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov  5 04:09:45 node-1 puppet-user[9622]: Finished catalog run in 0.04 seconds
Nov  5 04:09:46 node-1 puppet-user[10074]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov  5 04:09:46 node-1 puppet-user[10074]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Nov  5 04:09:47 node-1 puppet-user[10074]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov  5 04:09:47 node-1 puppet-user[10074]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov  5 04:09:47 node-1 puppet-user[10074]: Finished catalog run in 0.03 seconds
Nov  5 04:09:48 node-1 puppet-user[10537]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov  5 04:09:48 node-1 puppet-user[10537]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Nov  5 04:09:48 node-1 puppet-user[10537]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov  5 04:09:48 node-1 puppet-user[10537]: Finished catalog run in 0.03 seconds
Nov  5 04:09:50 node-1 puppet-user[11173]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov  5 04:09:50 node-1 puppet-user[11173]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Nov  5 04:09:50 node-1 puppet-user[11173]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov  5 04:09:50 node-1 puppet-user[11173]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Nov  5 04:09:51 node-1 puppet-user[11173]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Nov  5 04:09:51 node-1 puppet-user[11173]: Finished catalog run in 0.80 seconds
Nov  5 04:09:52 node-1 puppet-user[11676]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov  5 04:09:52 node-1 puppet-user[11676]: Compiled catalog for node-1.domain.tld in environment production in 0.22 seconds
Nov  5 04:09:52 node-1 puppet-user[11676]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Nov  5 04:09:52 node-1 puppet-user[11676]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov  5 04:09:52 node-1 puppet-user[11676]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov  5 04:09:52 node-1 puppet-user[11676]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Nov  5 04:09:53 node-1 puppet-user[11676]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov  5 04:09:53 node-1 puppet-user[11676]: Finished catalog run in 0.32 seconds
Nov  5 04:09:54 node-1 puppet-user[12154]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov  5 04:09:54 node-1 puppet-user[12154]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Nov  5 04:09:54 node-1 puppet-user[12154]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov  5 04:09:54 node-1 kernel: [   70.152256] nr_pdflush_threads exported in /proc is scheduled for removal
Nov  5 04:09:54 node-1 kernel: [   70.152306] 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  5 04:09:54 node-1 puppet-user[12154]: (/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  5 04:09:54 node-1 puppet-user[12154]: Finished catalog run in 0.05 seconds
Nov  5 04:09:56 node-1 puppet-user[12611]: (Scope(Class[main])) MODULAR: sync_time
Nov  5 04:09:56 node-1 puppet-user[12611]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Nov  5 04:09:56 node-1 ntpdate[13027]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov  5 04:10:01 node-1 kernel: [   76.279247] init: plymouth-upstart-bridge main process ended, respawning
Nov  5 04:10:01 node-1 puppet-agent[8944]: Could not run: SIGTERM
Nov  5 04:10:01 node-1 kernel: [   76.535971] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov  5 04:10:01 node-1 ec2: 
Nov  5 04:10:01 node-1 ec2: #############################################################
Nov  5 04:10:01 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov  5 04:10:01 node-1 ec2: 1024 d1:21:45:75:e3:d3:b2:a6:d4:39:f7:6c:85:10:bf:d3  root@node-1.domain.tld (DSA)
Nov  5 04:10:01 node-1 ec2: 256 65:14:52:f7:df:88:50:c8:60:99:7f:03:4c:64:98:ed  root@node-1.domain.tld (ECDSA)
Nov  5 04:10:01 node-1 ec2: 256 25:c1:40:31:a9:25:1c:ca:b2:9e:bc:4b:ba:49:c7:58  root@node-1.domain.tld (ED25519)
Nov  5 04:10:01 node-1 ec2: 2048 29:67:cb:69:90:6d:21:25:9f:d2:50:6b:d2:ca:a2:8a  root@node-1.domain.tld (RSA)
Nov  5 04:10:01 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov  5 04:10:01 node-1 ec2: #############################################################
Nov  5 04:10:01 node-1 CRON[13304]: (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  5 04:10:02 node-1 ntpdate[13027]: adjust time server 10.20.0.2 offset -0.354060 sec
Nov  5 04:10:02 node-1 puppet-user[12611]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov  5 04:10:02 node-1 puppet-user[12611]: Finished catalog run in 6.16 seconds
Nov  5 04:10:08 node-1 puppet-user[13406]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  5 04:10:08 node-1 puppet-user[13406]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Nov  5 04:10:08 node-1 puppet-user[13406]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov  5 04:10:08 node-1 puppet-user[13406]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Nov  5 04:10:08 node-1 puppet-user[13406]: Finished catalog run in 0.07 seconds
Nov  5 04:10:09 node-1 puppet-user[13869]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov  5 04:10:10 node-1 puppet-user[13869]: Compiled catalog for node-1.domain.tld in environment production in 0.47 seconds
Nov  5 04:10:10 node-1 puppet-user[13869]: (/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  5 04:10:10 node-1 puppet-user[13869]: (/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  5 04:10:10 node-1 puppet-user[13869]: (/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  5 04:10:10 node-1 puppet-user[13869]: (/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  5 04:10:10 node-1 puppet-user[13869]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov  5 04:10:10 node-1 puppet-user[13869]: (/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  5 04:10:10 node-1 puppet-user[13869]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov  5 04:10:10 node-1 puppet-user[13869]: (/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  5 04:10:10 node-1 puppet-user[13869]: (/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  5 04:10:10 node-1 puppet-user[13869]: (/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  5 04:10:11 node-1 puppet-user[13869]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov  5 04:10:11 node-1 puppet-user[13869]: Finished catalog run in 0.93 seconds
Nov  5 04:10:12 node-1 puppet-user[14384]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov  5 04:10:12 node-1 puppet-user[14384]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Nov  5 04:10:15 node-1 puppet-user[14384]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov  5 04:10:30 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  5 04:10:30 node-1 nailgun-agent: I, [2016-11-05T04:10:30.695119 #13307]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  5 04:10:42 node-1 puppet-user[14384]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov  5 04:10:42 node-1 puppet-user[14384]: Finished catalog run in 29.67 seconds
Nov  5 04:10:43 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  5 04:10:43 node-1 nailgun-agent: I, [2016-11-05T04:10:43.785521 #13307]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Nov  5 04:10:44 node-1 puppet-user[16957]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov  5 04:10:45 node-1 puppet-user[16957]: Compiled catalog for node-1.domain.tld in environment production in 0.66 seconds
Nov  5 04:10:45 node-1 puppet-user[16957]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov  5 04:10:45 node-1 puppet-user[16957]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov  5 04:10:45 node-1 puppet-user[16957]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov  5 04:10:45 node-1 puppet-user[16957]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov  5 04:10:45 node-1 puppet-user[16957]: Finished catalog run in 0.08 seconds
Nov  5 04:10:47 node-1 puppet-user[17579]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov  5 04:10:48 node-1 puppet-user[17579]: Compiled catalog for node-1.domain.tld in environment production in 0.89 seconds
Nov  5 04:10:48 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov  5 04:10:48 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov  5 04:10:48 node-1 crontab[18015]: (root) LIST (root)
Nov  5 04:10:48 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov  5 04:10:48 node-1 crontab[18016]: (root) REPLACE (root)
Nov  5 04:10:49 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/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  5 04:10:50 node-1 puppet-user[17579]: (/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  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/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  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov  5 04:10:50 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/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  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/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  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/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  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/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  5 04:10:51 node-1 puppet-user[17579]: (/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  5 04:10:51 node-1 puppet-user[17579]: (/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  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/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  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/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  5 04:10:51 node-1 puppet-user[17579]: (/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  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov  5 04:10:51 node-1 puppet-user[17579]: (/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  5 04:10:51 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8395" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 04:10:51 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov  5 04:10:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:10:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:10:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:10:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:10:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:08 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:08 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:08 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:08 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:11:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:05 node-1 ntpdate[29041]: no servers can be used, exiting
<27>Nov  5 04:12:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:50 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:50 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:50 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:50 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:12:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:13:48 node-1 multipathd: uevent trigger error
<27>Nov  5 04:13:48 node-1 multipathd: uevent trigger error
<27>Nov  5 04:13:48 node-1 multipathd: uevent trigger error
<27>Nov  5 04:13:48 node-1 multipathd: uevent trigger error
<27>Nov  5 04:13:48 node-1 multipathd: uevent trigger error
<27>Nov  5 04:13:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:13:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:13:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:13:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:13:59 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 04:13:59 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 04:14:05 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 04:14:05 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 04:14:10 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 04:14:16 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 04:14:16 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 04:14:23 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:23 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:23 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:23 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:23 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:14:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:20 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:20 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:20 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:20 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:20 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:20 node-1 multipathd: uevent trigger error
<129>Nov  5 04:15:23 node-1 haproxy[25184]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 55ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:15:23 node-1 haproxy[25184]: proxy odl-neutron-endpoint has no server available!
<129>Nov  5 04:15:24 node-1 haproxy[25189]: Server odl-jetty/node-1 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  5 04:15:24 node-1 haproxy[25189]: proxy odl-jetty has no server available!
<27>Nov  5 04:15:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:46 node-1 multipathd: uevent trigger error
<129>Nov  5 04:15:49 node-1 haproxy[27651]: 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  5 04:15:49 node-1 haproxy[27651]: 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  5 04:15:49 node-1 haproxy[27651]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:15:49 node-1 haproxy[27651]: proxy mysqld has no server available!
<27>Nov  5 04:15:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:55 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:55 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:55 node-1 multipathd: uevent trigger error
<27>Nov  5 04:15:55 node-1 multipathd: uevent trigger error
<129>Nov  5 04:15:58 node-1 haproxy[30281]: 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  5 04:15:58 node-1 haproxy[30281]: 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  5 04:15:58 node-1 haproxy[30281]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:15:58 node-1 haproxy[30281]: proxy mysqld has no server available!
<129>Nov  5 04:15:59 node-1 haproxy[30285]: 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  5 04:15:59 node-1 haproxy[30285]: 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  5 04:15:59 node-1 haproxy[30285]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:15:59 node-1 haproxy[30285]: proxy object-storage has no server available!
<27>Nov  5 04:16:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:01 node-1 multipathd: uevent trigger error
<129>Nov  5 04:16:03 node-1 haproxy[31622]: 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  5 04:16:03 node-1 haproxy[31622]: 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  5 04:16:04 node-1 haproxy[31628]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:04 node-1 haproxy[31628]: proxy neutron has no server available!
<129>Nov  5 04:16:04 node-1 haproxy[31628]: 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  5 04:16:04 node-1 haproxy[31628]: 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  5 04:16:04 node-1 haproxy[31628]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:04 node-1 haproxy[31628]: proxy mysqld has no server available!
<129>Nov  5 04:16:04 node-1 haproxy[31628]: 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  5 04:16:05 node-1 haproxy[31628]: 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  5 04:16:05 node-1 haproxy[31628]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:05 node-1 haproxy[31628]: proxy object-storage has no server available!
<27>Nov  5 04:16:07 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:07 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:07 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:07 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:07 node-1 multipathd: uevent trigger error
<129>Nov  5 04:16:09 node-1 haproxy[563]: 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  5 04:16:09 node-1 haproxy[563]: 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  5 04:16:09 node-1 haproxy[563]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:09 node-1 haproxy[563]: proxy keystone-1 has no server available!
<129>Nov  5 04:16:09 node-1 haproxy[563]: 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  5 04:16:10 node-1 haproxy[567]: 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  5 04:16:10 node-1 haproxy[567]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:10 node-1 haproxy[567]: proxy keystone-2 has no server available!
<129>Nov  5 04:16:10 node-1 haproxy[567]: 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  5 04:16:10 node-1 haproxy[567]: 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  5 04:16:10 node-1 haproxy[567]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:10 node-1 haproxy[567]: proxy neutron has no server available!
<129>Nov  5 04:16:10 node-1 haproxy[567]: 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  5 04:16:10 node-1 haproxy[567]: 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  5 04:16:10 node-1 haproxy[567]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:10 node-1 haproxy[567]: proxy mysqld has no server available!
<129>Nov  5 04:16:11 node-1 haproxy[567]: 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  5 04:16:11 node-1 haproxy[567]: 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  5 04:16:11 node-1 haproxy[567]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:11 node-1 haproxy[567]: proxy object-storage has no server available!
<27>Nov  5 04:16:12 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:12 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:12 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:12 node-1 multipathd: uevent trigger error
<129>Nov  5 04:16:14 node-1 haproxy[1899]: 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  5 04:16:15 node-1 haproxy[1903]: 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  5 04:16:15 node-1 haproxy[1903]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:15 node-1 haproxy[1903]: proxy keystone-1 has no server available!
<129>Nov  5 04:16:15 node-1 haproxy[1903]: 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  5 04:16:15 node-1 haproxy[1903]: 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  5 04:16:15 node-1 haproxy[1903]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:15 node-1 haproxy[1903]: proxy keystone-2 has no server available!
<129>Nov  5 04:16:15 node-1 haproxy[1903]: 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  5 04:16:15 node-1 haproxy[1903]: 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  5 04:16:15 node-1 haproxy[1903]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:15 node-1 haproxy[1903]: proxy neutron has no server available!
<129>Nov  5 04:16:15 node-1 haproxy[1903]: 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  5 04:16:15 node-1 haproxy[1903]: 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  5 04:16:16 node-1 haproxy[1903]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:16 node-1 haproxy[1903]: proxy mysqld has no server available!
<129>Nov  5 04:16:16 node-1 haproxy[1903]: 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  5 04:16:16 node-1 haproxy[1903]: 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  5 04:16:16 node-1 haproxy[1903]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:16 node-1 haproxy[1903]: proxy object-storage has no server available!
<129>Nov  5 04:16:16 node-1 haproxy[1903]: 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  5 04:16:16 node-1 haproxy[1903]: 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  5 04:16:16 node-1 haproxy[1903]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:16 node-1 haproxy[1903]: proxy aodh has no server available!
<27>Nov  5 04:16:18 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:18 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:18 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:18 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:18 node-1 multipathd: uevent trigger error
<129>Nov  5 04:16:20 node-1 haproxy[3505]: 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  5 04:16:20 node-1 haproxy[3505]: 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  5 04:16:20 node-1 haproxy[3505]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:20 node-1 haproxy[3505]: proxy keystone-1 has no server available!
<129>Nov  5 04:16:20 node-1 haproxy[3505]: 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  5 04:16:20 node-1 haproxy[3505]: 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  5 04:16:21 node-1 haproxy[3511]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:21 node-1 haproxy[3511]: proxy keystone-2 has no server available!
<129>Nov  5 04:16:21 node-1 haproxy[3511]: 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  5 04:16:21 node-1 haproxy[3511]: 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  5 04:16:21 node-1 haproxy[3511]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:21 node-1 haproxy[3511]: proxy neutron has no server available!
<129>Nov  5 04:16:21 node-1 haproxy[3511]: 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  5 04:16:21 node-1 haproxy[3511]: 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  5 04:16:21 node-1 haproxy[3511]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:21 node-1 haproxy[3511]: proxy mysqld has no server available!
<129>Nov  5 04:16:21 node-1 haproxy[3511]: 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  5 04:16:21 node-1 haproxy[3511]: 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  5 04:16:21 node-1 haproxy[3511]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:21 node-1 haproxy[3511]: proxy object-storage has no server available!
<129>Nov  5 04:16:21 node-1 haproxy[3511]: 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  5 04:16:22 node-1 haproxy[3511]: 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  5 04:16:22 node-1 haproxy[3511]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:22 node-1 haproxy[3511]: proxy aodh has no server available!
<129>Nov  5 04:16:22 node-1 haproxy[3511]: 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  5 04:16:22 node-1 haproxy[3511]: 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  5 04:16:22 node-1 haproxy[3511]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:22 node-1 haproxy[3511]: proxy ceilometer has no server available!
<27>Nov  5 04:16:23 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:23 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:23 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:23 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:23 node-1 multipathd: uevent trigger error
<129>Nov  5 04:16:25 node-1 haproxy[4898]: 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  5 04:16:26 node-1 haproxy[4905]: 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  5 04:16:26 node-1 haproxy[4905]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:26 node-1 haproxy[4905]: proxy keystone-1 has no server available!
<129>Nov  5 04:16:26 node-1 haproxy[4905]: 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  5 04:16:26 node-1 haproxy[4905]: 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  5 04:16:26 node-1 haproxy[4905]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:26 node-1 haproxy[4905]: proxy keystone-2 has no server available!
<129>Nov  5 04:16:26 node-1 haproxy[4905]: 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  5 04:16:26 node-1 haproxy[4905]: 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  5 04:16:26 node-1 haproxy[4905]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:26 node-1 haproxy[4905]: proxy neutron has no server available!
<129>Nov  5 04:16:26 node-1 haproxy[4905]: 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  5 04:16:26 node-1 haproxy[4905]: 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  5 04:16:26 node-1 haproxy[4905]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:26 node-1 haproxy[4905]: proxy mysqld has no server available!
<129>Nov  5 04:16:26 node-1 haproxy[4905]: 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  5 04:16:27 node-1 haproxy[4905]: 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  5 04:16:27 node-1 haproxy[4905]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:27 node-1 haproxy[4905]: proxy object-storage has no server available!
<129>Nov  5 04:16:27 node-1 haproxy[4905]: 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  5 04:16:27 node-1 haproxy[4905]: 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  5 04:16:27 node-1 haproxy[4905]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:27 node-1 haproxy[4905]: proxy aodh has no server available!
<129>Nov  5 04:16:27 node-1 haproxy[4905]: 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  5 04:16:27 node-1 haproxy[4905]: 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  5 04:16:27 node-1 haproxy[4905]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:27 node-1 haproxy[4905]: proxy ceilometer has no server available!
<27>Nov  5 04:16:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:29 node-1 multipathd: uevent trigger error
<129>Nov  5 04:16:31 node-1 haproxy[6505]: 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  5 04:16:31 node-1 haproxy[6505]: 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  5 04:16:31 node-1 haproxy[6505]: 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  5 04:16:31 node-1 haproxy[6505]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:31 node-1 haproxy[6505]: proxy keystone-1 has no server available!
<129>Nov  5 04:16:31 node-1 haproxy[6505]: 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  5 04:16:31 node-1 haproxy[6505]: 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  5 04:16:31 node-1 haproxy[6505]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:31 node-1 haproxy[6505]: proxy keystone-2 has no server available!
<129>Nov  5 04:16:31 node-1 haproxy[6505]: 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  5 04:16:32 node-1 haproxy[6511]: 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  5 04:16:32 node-1 haproxy[6511]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:32 node-1 haproxy[6511]: proxy neutron has no server available!
<129>Nov  5 04:16:32 node-1 haproxy[6511]: 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  5 04:16:32 node-1 haproxy[6511]: 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  5 04:16:32 node-1 haproxy[6511]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:32 node-1 haproxy[6511]: proxy mysqld has no server available!
<129>Nov  5 04:16:32 node-1 haproxy[6511]: 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  5 04:16:32 node-1 haproxy[6511]: 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  5 04:16:32 node-1 haproxy[6511]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:32 node-1 haproxy[6511]: proxy object-storage has no server available!
<129>Nov  5 04:16:32 node-1 haproxy[6511]: 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  5 04:16:32 node-1 haproxy[6511]: 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  5 04:16:32 node-1 haproxy[6511]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:32 node-1 haproxy[6511]: proxy aodh has no server available!
<129>Nov  5 04:16:32 node-1 haproxy[6511]: 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  5 04:16:32 node-1 haproxy[6511]: 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  5 04:16:33 node-1 haproxy[6511]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:33 node-1 haproxy[6511]: proxy ceilometer has no server available!
<27>Nov  5 04:16:34 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:34 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:34 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:34 node-1 multipathd: uevent trigger error
<129>Nov  5 04:16:37 node-1 haproxy[8015]: 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  5 04:16:37 node-1 haproxy[8015]: 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  5 04:16:37 node-1 haproxy[8015]: 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  5 04:16:37 node-1 haproxy[8015]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:37 node-1 haproxy[8015]: proxy keystone-1 has no server available!
<129>Nov  5 04:16:37 node-1 haproxy[8015]: 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  5 04:16:37 node-1 haproxy[8015]: 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  5 04:16:37 node-1 haproxy[8015]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:37 node-1 haproxy[8015]: proxy keystone-2 has no server available!
<129>Nov  5 04:16:37 node-1 haproxy[8015]: 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  5 04:16:37 node-1 haproxy[8015]: 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  5 04:16:37 node-1 haproxy[8015]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:37 node-1 haproxy[8015]: proxy glance-api has no server available!
<129>Nov  5 04:16:37 node-1 haproxy[8015]: 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  5 04:16:37 node-1 haproxy[8015]: 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  5 04:16:37 node-1 haproxy[8015]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:37 node-1 haproxy[8015]: proxy glance-glare has no server available!
<129>Nov  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:38 node-1 haproxy[8020]: proxy neutron has no server available!
<129>Nov  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:38 node-1 haproxy[8020]: proxy glance-registry has no server available!
<129>Nov  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:38 node-1 haproxy[8020]: proxy mysqld has no server available!
<129>Nov  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:38 node-1 haproxy[8020]: proxy object-storage has no server available!
<129>Nov  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:38 node-1 haproxy[8020]: proxy aodh has no server available!
<129>Nov  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:38 node-1 haproxy[8020]: 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  5 04:16:39 node-1 haproxy[8020]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:39 node-1 haproxy[8020]: proxy ceilometer has no server available!
<27>Nov  5 04:16:40 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:40 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:40 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:40 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:40 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Nov  5 04:16:43 node-1 haproxy[9585]: 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  5 04:16:43 node-1 haproxy[9585]: 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  5 04:16:43 node-1 haproxy[9585]: 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  5 04:16:43 node-1 haproxy[9585]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:43 node-1 haproxy[9585]: proxy keystone-1 has no server available!
<129>Nov  5 04:16:43 node-1 haproxy[9585]: 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  5 04:16:43 node-1 haproxy[9585]: 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  5 04:16:43 node-1 haproxy[9585]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:43 node-1 haproxy[9585]: proxy keystone-2 has no server available!
<129>Nov  5 04:16:43 node-1 haproxy[9585]: 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  5 04:16:43 node-1 haproxy[9585]: 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  5 04:16:43 node-1 haproxy[9585]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:43 node-1 haproxy[9585]: proxy nova-api has no server available!
<129>Nov  5 04:16:43 node-1 haproxy[9585]: 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  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:44 node-1 haproxy[9589]: proxy nova-metadata-api has no server available!
<129>Nov  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:44 node-1 haproxy[9589]: proxy glance-api has no server available!
<129>Nov  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:44 node-1 haproxy[9589]: proxy glance-glare has no server available!
<129>Nov  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:44 node-1 haproxy[9589]: proxy neutron has no server available!
<129>Nov  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:44 node-1 haproxy[9589]: proxy glance-registry has no server available!
<129>Nov  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:44 node-1 haproxy[9589]: proxy mysqld has no server available!
<129>Nov  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:44 node-1 haproxy[9589]: proxy object-storage has no server available!
<129>Nov  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:44 node-1 haproxy[9589]: 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  5 04:16:45 node-1 haproxy[9589]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:45 node-1 haproxy[9589]: proxy aodh has no server available!
<129>Nov  5 04:16:45 node-1 haproxy[9589]: 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  5 04:16:45 node-1 haproxy[9589]: 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  5 04:16:45 node-1 haproxy[9589]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:45 node-1 haproxy[9589]: proxy ceilometer has no server available!
<129>Nov  5 04:16:45 node-1 haproxy[9589]: 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  5 04:16:45 node-1 haproxy[9589]: 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  5 04:16:45 node-1 haproxy[9589]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:45 node-1 haproxy[9589]: proxy nova-novncproxy has no server available!
<27>Nov  5 04:16:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:48 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<129>Nov  5 04:16:48 node-1 haproxy[11049]: 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  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:49 node-1 haproxy[11053]: proxy keystone-1 has no server available!
<129>Nov  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:49 node-1 haproxy[11053]: proxy keystone-2 has no server available!
<129>Nov  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:49 node-1 haproxy[11053]: proxy nova-api has no server available!
<129>Nov  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:49 node-1 haproxy[11053]: proxy nova-metadata-api has no server available!
<129>Nov  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:49 node-1 haproxy[11053]: proxy cinder-api has no server available!
<129>Nov  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:49 node-1 haproxy[11053]: proxy glance-api has no server available!
<129>Nov  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:49 node-1 haproxy[11053]: proxy glance-glare has no server available!
<129>Nov  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:49 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:50 node-1 haproxy[11053]: proxy neutron has no server available!
<129>Nov  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:50 node-1 haproxy[11053]: proxy glance-registry has no server available!
<129>Nov  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:50 node-1 haproxy[11053]: proxy mysqld has no server available!
<129>Nov  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:50 node-1 haproxy[11053]: proxy object-storage has no server available!
<129>Nov  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:50 node-1 haproxy[11053]: proxy aodh has no server available!
<129>Nov  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:50 node-1 haproxy[11053]: proxy ceilometer has no server available!
<129>Nov  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: 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  5 04:16:50 node-1 haproxy[11053]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:50 node-1 haproxy[11053]: proxy nova-novncproxy has no server available!
<27>Nov  5 04:16:51 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:51 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:51 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:51 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:52 node-1 multipathd: uevent trigger error
<129>Nov  5 04:16:54 node-1 haproxy[12436]: 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  5 04:16:54 node-1 haproxy[12436]: 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  5 04:16:54 node-1 haproxy[12436]: 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  5 04:16:54 node-1 haproxy[12436]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:54 node-1 haproxy[12436]: proxy keystone-1 has no server available!
<129>Nov  5 04:16:54 node-1 haproxy[12436]: 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  5 04:16:54 node-1 haproxy[12436]: 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  5 04:16:55 node-1 haproxy[12440]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:55 node-1 haproxy[12440]: proxy keystone-2 has no server available!
<129>Nov  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:55 node-1 haproxy[12440]: proxy nova-api has no server available!
<129>Nov  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:55 node-1 haproxy[12440]: proxy nova-metadata-api has no server available!
<129>Nov  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:55 node-1 haproxy[12440]: proxy cinder-api has no server available!
<129>Nov  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:55 node-1 haproxy[12440]: proxy glance-api has no server available!
<129>Nov  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:55 node-1 haproxy[12440]: proxy glance-glare has no server available!
<129>Nov  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:55 node-1 haproxy[12440]: proxy neutron has no server available!
<129>Nov  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:55 node-1 haproxy[12440]: proxy glance-registry has no server available!
<129>Nov  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:55 node-1 haproxy[12440]: proxy mysqld has no server available!
<129>Nov  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: 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  5 04:16:55 node-1 haproxy[12440]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:55 node-1 haproxy[12440]: proxy object-storage has no server available!
<129>Nov  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:56 node-1 haproxy[12440]: proxy aodh has no server available!
<129>Nov  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:56 node-1 haproxy[12440]: proxy ceilometer has no server available!
<129>Nov  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:56 node-1 haproxy[12440]: proxy heat-api has no server available!
<129>Nov  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:56 node-1 haproxy[12440]: proxy heat-api-cfn has no server available!
<129>Nov  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:56 node-1 haproxy[12440]: proxy heat-api-cloudwatch has no server available!
<129>Nov  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: 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  5 04:16:56 node-1 haproxy[12440]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 04:16:56 node-1 haproxy[12440]: proxy nova-novncproxy has no server available!
<27>Nov  5 04:16:57 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:57 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:57 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:57 node-1 multipathd: uevent trigger error
<27>Nov  5 04:16:57 node-1 multipathd: uevent trigger error
<27>Nov  5 04:17:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:17:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:17:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:17:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:17:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:17:08 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov  5 04:17:33 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  5 04:17:35 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov  5 04:18:26 node-1 multipathd: uevent trigger error
<27>Nov  5 04:18:26 node-1 multipathd: uevent trigger error
<27>Nov  5 04:18:26 node-1 multipathd: uevent trigger error
<27>Nov  5 04:18:26 node-1 multipathd: uevent trigger error
<27>Nov  5 04:18:26 node-1 multipathd: uevent trigger error
<27>Nov  5 04:18:26 node-1 multipathd: uevent trigger error
<27>Nov  5 04:19:59 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 04:20:35 node-1 multipathd: uevent trigger error
<27>Nov  5 04:20:35 node-1 multipathd: uevent trigger error
<27>Nov  5 04:20:35 node-1 multipathd: uevent trigger error
<27>Nov  5 04:20:35 node-1 multipathd: uevent trigger error
<27>Nov  5 04:20:35 node-1 multipathd: uevent trigger error
<27>Nov  5 04:20:42 node-1 multipathd: uevent trigger error
<27>Nov  5 04:20:42 node-1 multipathd: uevent trigger error
<27>Nov  5 04:20:42 node-1 multipathd: uevent trigger error
<27>Nov  5 04:20:42 node-1 multipathd: uevent trigger error
<27>Nov  5 04:20:42 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:02 node-1 multipathd: uevent trigger error
<43>Nov  5 04:21:02 node-1 apache2_error [Sat Nov 05 04:20:53.255122 2016] [mpm_event:notice] [pid 22667:tid 140364091123584] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  5 04:21:02 node-1 apache2_error [Sat Nov 05 04:20:53.255281 2016] [core:notice] [pid 22667:tid 140364091123584] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  5 04:21:02 node-1 apache2_error [Sat Nov 05 04:20:56.200350 2016] [mpm_event:notice] [pid 22667:tid 140364091123584] AH00491: caught SIGTERM, shutting down
<43>Nov  5 04:21:02 node-1 apache2_error [Sat Nov 05 04:20:57.283914 2016] [mpm_worker:notice] [pid 24366:tid 139650392536960] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  5 04:21:02 node-1 apache2_error [Sat Nov 05 04:20:57.283945 2016] [core:notice] [pid 24366:tid 139650392536960] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 04:21:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:07 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:21:10 node-1 multipathd: uevent trigger error
<43>Nov  5 04:22:12 node-1 apache2_error [Sat Nov 05 04:22:11.914129 2016] [mpm_worker:notice] [pid 24366:tid 139650392536960] AH00295: caught SIGTERM, shutting down
<43>Nov  5 04:22:22 node-1 apache2_error [Sat Nov 05 04:22:12.669049 2016] [mpm_worker:notice] [pid 5051:tid 139700967692160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 04:22:22 node-1 apache2_error [Sat Nov 05 04:22:12.669093 2016] [core:notice] [pid 5051:tid 139700967692160] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 04:23:00 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  5 04:23:02 node-1 apache2_error [Sat Nov 05 04:22:56.605366 2016] [mpm_worker:notice] [pid 5051:tid 139700967692160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 04:23:02 node-1 apache2_error [Sat Nov 05 04:22:56.801845 2016] [mpm_worker:warn] [pid 5051:tid 139700967692160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 04:23:02 node-1 apache2_error [Sat Nov 05 04:22:56.806834 2016] [mpm_worker:notice] [pid 5051:tid 139700967692160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 04:23:02 node-1 apache2_error [Sat Nov 05 04:22:56.806867 2016] [core:notice] [pid 5051:tid 139700967692160] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 04:23:41 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:41 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:41 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:41 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:41 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:50 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:50 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:50 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:50 node-1 multipathd: uevent trigger error
<27>Nov  5 04:23:50 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:27 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:27 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:32 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:47 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:47 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:47 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:47 node-1 multipathd: uevent trigger error
<27>Nov  5 04:24:47 node-1 multipathd: uevent trigger error
<27>Nov  5 04:25:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:25:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:25:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:25:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:25:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:25:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:26:02 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 04:26:43 node-1 multipathd: uevent trigger error
<27>Nov  5 04:26:43 node-1 multipathd: uevent trigger error
<27>Nov  5 04:26:43 node-1 multipathd: uevent trigger error
<27>Nov  5 04:26:43 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:39 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:45 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:45 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:45 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:45 node-1 multipathd: uevent trigger error
<27>Nov  5 04:27:45 node-1 multipathd: uevent trigger error
<27>Nov  5 04:28:11 node-1 multipathd: uevent trigger error
<27>Nov  5 04:28:11 node-1 multipathd: uevent trigger error
<27>Nov  5 04:28:11 node-1 multipathd: uevent trigger error
<27>Nov  5 04:28:11 node-1 multipathd: uevent trigger error
<27>Nov  5 04:28:11 node-1 multipathd: uevent trigger error
<27>Nov  5 04:29:04 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 04:30:30 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:30 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:30 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:30 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:57 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:57 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:57 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:57 node-1 multipathd: uevent trigger error
<27>Nov  5 04:30:57 node-1 multipathd: uevent trigger error
<27>Nov  5 04:31:19 node-1 multipathd: uevent trigger error
<27>Nov  5 04:31:19 node-1 multipathd: uevent trigger error
<27>Nov  5 04:31:19 node-1 multipathd: uevent trigger error
<27>Nov  5 04:31:19 node-1 multipathd: uevent trigger error
<27>Nov  5 04:31:19 node-1 multipathd: uevent trigger error
<27>Nov  5 04:32:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:32:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:32:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:32:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:32:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:32:05 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 04:32:45 node-1 multipathd: uevent trigger error
<27>Nov  5 04:32:45 node-1 multipathd: uevent trigger error
<27>Nov  5 04:32:45 node-1 multipathd: uevent trigger error
<27>Nov  5 04:32:45 node-1 multipathd: uevent trigger error
<27>Nov  5 04:32:45 node-1 multipathd: uevent trigger error
<27>Nov  5 04:33:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:33:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:33:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:33:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:33:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 04:35:18 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:19 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:19 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:19 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:19 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:51 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:51 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:51 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:51 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:51 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:35:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:37 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:37 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:37 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:37 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:42 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:42 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:42 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:42 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:46 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:58 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:58 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:58 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:58 node-1 multipathd: uevent trigger error
<27>Nov  5 04:36:58 node-1 multipathd: uevent trigger error
<27>Nov  5 04:37:04 node-1 multipathd: uevent trigger error
<27>Nov  5 04:37:04 node-1 multipathd: uevent trigger error
<27>Nov  5 04:37:04 node-1 multipathd: uevent trigger error
<27>Nov  5 04:37:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:37:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:37:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:37:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:37:36 node-1 multipathd: uevent trigger error
<27>Nov  5 04:38:08 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 04:38:40 node-1 multipathd: uevent trigger error
<27>Nov  5 04:38:40 node-1 multipathd: uevent trigger error
<27>Nov  5 04:38:40 node-1 multipathd: uevent trigger error
<27>Nov  5 04:38:40 node-1 multipathd: uevent trigger error
<27>Nov  5 04:38:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:38:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:38:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:38:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:38:56 node-1 multipathd: uevent trigger error
<11>Nov  5 04:39:09 node-1 liberasurecode[8520]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:09 node-1 liberasurecode[8520]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:09 node-1 liberasurecode[8520]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:09 node-1 liberasurecode[8520]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:09 node-1 liberasurecode[8558]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:09 node-1 liberasurecode[8558]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:09 node-1 liberasurecode[8558]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:09 node-1 liberasurecode[8558]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:11 node-1 liberasurecode[8978]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:11 node-1 liberasurecode[8978]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:11 node-1 liberasurecode[8978]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:11 node-1 liberasurecode[8978]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10323]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10323]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10323]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10323]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10364]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10364]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10364]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10364]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10541]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10541]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10541]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:15 node-1 liberasurecode[10541]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10731]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10731]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10731]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10731]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10775]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10775]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10775]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10775]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10804]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10804]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10804]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10804]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10818]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10818]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10818]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:16 node-1 liberasurecode[10818]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:32 node-1 liberasurecode[12158]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:32 node-1 liberasurecode[12158]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:32 node-1 liberasurecode[12158]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:39:32 node-1 liberasurecode[12158]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  5 04:39:41 node-1 multipathd: uevent trigger error
<27>Nov  5 04:39:41 node-1 multipathd: uevent trigger error
<27>Nov  5 04:39:41 node-1 multipathd: uevent trigger error
<27>Nov  5 04:39:41 node-1 multipathd: uevent trigger error
<27>Nov  5 04:39:41 node-1 multipathd: uevent trigger error
<11>Nov  5 04:40:01 node-1 liberasurecode[16624]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:40:01 node-1 liberasurecode[16624]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:40:01 node-1 liberasurecode[16624]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:40:01 node-1 liberasurecode[16624]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Nov  5 04:40:33 node-1 apache2_error [Sat Nov 05 04:40:26.846037 2016] [mpm_worker:notice] [pid 5051:tid 139700967692160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 04:40:33 node-1 apache2_error [Sat Nov 05 04:40:27.227686 2016] [mpm_worker:warn] [pid 5051:tid 139700967692160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 04:40:33 node-1 apache2_error [Sat Nov 05 04:40:27.230889 2016] [mpm_worker:notice] [pid 5051:tid 139700967692160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 04:40:33 node-1 apache2_error [Sat Nov 05 04:40:27.230910 2016] [core:notice] [pid 5051:tid 139700967692160] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 04:41:08 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:08 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:08 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:08 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:08 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  5 04:41:13 node-1 apache2_error [Sat Nov 05 04:41:04.271967 2016] [mpm_worker:notice] [pid 5051:tid 139700967692160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 04:41:13 node-1 apache2_error [Sat Nov 05 04:41:04.465600 2016] [mpm_worker:warn] [pid 5051:tid 139700967692160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 04:41:13 node-1 apache2_error [Sat Nov 05 04:41:04.472865 2016] [mpm_worker:notice] [pid 5051:tid 139700967692160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 04:41:13 node-1 apache2_error [Sat Nov 05 04:41:04.472915 2016] [core:notice] [pid 5051:tid 139700967692160] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 04:41:15 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:15 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:15 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:15 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:15 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:53 node-1 multipathd: uevent trigger error
<27>Nov  5 04:41:53 node-1 multipathd: uevent trigger error
<43>Nov  5 04:41:53 node-1 apache2_error [Sat Nov 05 04:41:49.733248 2016] [mpm_worker:notice] [pid 5051:tid 139700967692160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 04:41:53 node-1 apache2_error [Sat Nov 05 04:41:50.115104 2016] [mpm_worker:warn] [pid 5051:tid 139700967692160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 04:41:53 node-1 apache2_error [Sat Nov 05 04:41:50.120290 2016] [mpm_worker:notice] [pid 5051:tid 139700967692160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 04:41:53 node-1 apache2_error [Sat Nov 05 04:41:50.120322 2016] [core:notice] [pid 5051:tid 139700967692160] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 04:42:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:12 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:12 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:12 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:12 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:29 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:29 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:29 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:29 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:29 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:50 node-1 multipathd: uevent trigger error
<27>Nov  5 04:42:56 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov  5 04:43:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:15 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:15 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:15 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:15 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:15 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:28 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:33 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:33 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:33 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:33 node-1 multipathd: uevent trigger error
<27>Nov  5 04:43:33 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:00 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:13 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:13 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:13 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:13 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:13 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:18 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:18 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:18 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:18 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:18 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:30 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:30 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:30 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:30 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:30 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:47 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:47 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:47 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:47 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:47 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:52 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:44:56 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:01 node-1 multipathd: uevent trigger error
<11>Nov  5 04:45:01 node-1 liberasurecode[24005]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:45:01 node-1 liberasurecode[24005]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:45:01 node-1 liberasurecode[24005]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 04:45:01 node-1 liberasurecode[24005]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  5 04:45:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:01 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:05 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:06 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:10 node-1 multipathd: uevent trigger error
<27>Nov  5 04:45:10 node-1 multipathd: uevent trigger error
