Oct 30 04:06:01 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8403" x-info="http://www.rsyslog.com"] start
Oct 30 04:06:01 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 30 04:06:01 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 30 04:06:01 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 30 04:06:01 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 30 04:06:01 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 30 04:06:01 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 30 04:06:01 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)
Oct 30 04:06:01 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=f8609434-0b1f-439a-b0e5-ed6379fb0598 nomdmonddf nomdmonisw
Oct 30 04:06:01 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 30 04:06:01 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 30 04:06:01 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 30 04:06:01 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 30 04:06:01 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 30 04:06:01 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 30 04:06:01 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 30 04:06:01 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 30 04:06:01 node-1 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Oct 30 04:06:01 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 30 04:06:01 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 30 04:06:01 node-1 kernel: [    0.000000] No AGP bridge found
Oct 30 04:06:01 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 30 04:06:01 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 30 04:06:01 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 30 04:06:01 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 30 04:06:01 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 30 04:06:01 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 30 04:06:01 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 30 04:06:01 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 30 04:06:01 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 30 04:06:01 node-1 kernel: [    0.000000]   2 disabled
Oct 30 04:06:01 node-1 kernel: [    0.000000]   3 disabled
Oct 30 04:06:01 node-1 kernel: [    0.000000]   4 disabled
Oct 30 04:06:01 node-1 kernel: [    0.000000]   5 disabled
Oct 30 04:06:01 node-1 kernel: [    0.000000]   6 disabled
Oct 30 04:06:01 node-1 kernel: [    0.000000]   7 disabled
Oct 30 04:06:01 node-1 kernel: [    0.000000]   8 disabled
Oct 30 04:06:01 node-1 kernel: [    0.000000]   9 disabled
Oct 30 04:06:01 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 30 04:06:01 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 30 04:06:01 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 30 04:06:01 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 30 04:06:01 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 30 04:06:01 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 30 04:06:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 30 04:06:01 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 30 04:06:01 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 30 04:06:01 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 30 04:06:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 30 04:06:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 30 04:06:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 30 04:06:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 30 04:06:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 30 04:06:01 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 30 04:06:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 30 04:06:01 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 30 04:06:01 node-1 kernel: [    0.000000] RAMDISK: [mem 0x3581e000-0x36c06fff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 30 04:06:01 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 30 04:06:01 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 30 04:06:01 node-1 kernel: [    0.000000] Zone ranges:
Oct 30 04:06:01 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 30 04:06:01 node-1 kernel: [    0.000000] Early memory node ranges
Oct 30 04:06:01 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 30 04:06:01 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 30 04:06:01 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 30 04:06:01 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 30 04:06:01 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 30 04:06:01 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 30 04:06:01 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 30 04:06:01 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 30 04:06:01 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 30 04:06:01 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 30 04:06:01 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 30 04:06:01 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 30 04:06:01 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 30 04:06:01 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 30 04:06:01 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 30 04:06:01 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 30 04:06:01 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 30 04:06:01 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 30 04:06:01 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 30 04:06:01 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 30 04:06:01 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 30 04:06:01 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 30 04:06:01 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 30 04:06:01 node-1 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Oct 30 04:06:01 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 30 04:06:01 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 30 04:06:01 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=f8609434-0b1f-439a-b0e5-ed6379fb0598 nomdmonddf nomdmonisw
Oct 30 04:06:01 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 30 04:06:01 node-1 kernel: [    0.000000] Checking aperture...
Oct 30 04:06:01 node-1 kernel: [    0.000000] No AGP bridge found
Oct 30 04:06:01 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 30 04:06:01 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 30 04:06:01 node-1 kernel: [    0.000000] Memory: 32653308K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627188K reserved)
Oct 30 04:06:01 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 30 04:06:01 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 30 04:06:01 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 30 04:06:01 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 30 04:06:01 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 30 04:06:01 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 30 04:06:01 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 30 04:06:01 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 30 04:06:01 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 30 04:06:01 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 30 04:06:01 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 30 04:06:01 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 30 04:06:01 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 30 04:06:01 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 30 04:06:01 node-1 kernel: [    0.004000] tsc: Detected 3492.144 MHz processor
Oct 30 04:06:01 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.28 BogoMIPS (lpj=13968576)
Oct 30 04:06:01 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct 30 04:06:01 node-1 kernel: [    0.000043] Security Framework initialized
Oct 30 04:06:01 node-1 kernel: [    0.000061] AppArmor: AppArmor initialized
Oct 30 04:06:01 node-1 kernel: [    0.000062] Yama: becoming mindful.
Oct 30 04:06:01 node-1 kernel: [    0.001460] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.006322] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.008259] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.008287] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.008575] Initializing cgroup subsys memory
Oct 30 04:06:01 node-1 kernel: [    0.008583] Initializing cgroup subsys devices
Oct 30 04:06:01 node-1 kernel: [    0.008585] Initializing cgroup subsys freezer
Oct 30 04:06:01 node-1 kernel: [    0.008587] Initializing cgroup subsys blkio
Oct 30 04:06:01 node-1 kernel: [    0.008588] Initializing cgroup subsys perf_event
Oct 30 04:06:01 node-1 kernel: [    0.008591] Initializing cgroup subsys hugetlb
Oct 30 04:06:01 node-1 kernel: [    0.008610] CPU: Physical Processor ID: 0
Oct 30 04:06:01 node-1 kernel: [    0.008611] CPU: Processor Core ID: 0
Oct 30 04:06:01 node-1 kernel: [    0.008615] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 30 04:06:01 node-1 kernel: [    0.008615] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 30 04:06:01 node-1 kernel: [    0.009309] mce: CPU supports 22 MCE banks
Oct 30 04:06:01 node-1 kernel: [    0.009337] CPU0: Thermal monitoring enabled (TM1)
Oct 30 04:06:01 node-1 kernel: [    0.009358] process: using mwait in idle threads
Oct 30 04:06:01 node-1 kernel: [    0.009361] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 30 04:06:01 node-1 kernel: [    0.009361] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 30 04:06:01 node-1 kernel: [    0.009361] tlb_flushall_shift: 6
Oct 30 04:06:01 node-1 kernel: [    0.009449] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 30 04:06:01 node-1 kernel: [    0.010172] ACPI: Core revision 20131115
Oct 30 04:06:01 node-1 kernel: [    0.022969] ACPI: All ACPI Tables successfully acquired
Oct 30 04:06:01 node-1 kernel: [    0.023133] ftrace: allocating 28622 entries in 112 pages
Oct 30 04:06:01 node-1 kernel: [    0.031889] dmar: Host address width 46
Oct 30 04:06:01 node-1 kernel: [    0.031891] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 30 04:06:01 node-1 kernel: [    0.031897] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 30 04:06:01 node-1 kernel: [    0.031899] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 30 04:06:01 node-1 kernel: [    0.031903] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 30 04:06:01 node-1 kernel: [    0.031905] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 30 04:06:01 node-1 kernel: [    0.031906] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 30 04:06:01 node-1 kernel: [    0.031907] dmar: ATSR flags: 0x0
Oct 30 04:06:01 node-1 kernel: [    0.031908] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 30 04:06:01 node-1 kernel: [    0.031909] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 30 04:06:01 node-1 kernel: [    0.032025] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 30 04:06:01 node-1 kernel: [    0.032026] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 30 04:06:01 node-1 kernel: [    0.032027] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 30 04:06:01 node-1 kernel: [    0.032028] HPET id 0 under DRHD base 0xc7ffc000
Oct 30 04:06:01 node-1 kernel: [    0.032029] Your BIOS is broken and requested that x2apic be disabled.
Oct 30 04:06:01 node-1 kernel: [    0.032029] This will slightly decrease performance.
Oct 30 04:06:01 node-1 kernel: [    0.032029] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 30 04:06:01 node-1 kernel: [    0.032462] Enabled IRQ remapping in xapic mode
Oct 30 04:06:01 node-1 kernel: [    0.032463] x2apic not enabled, IRQ remapping is in xapic mode
Oct 30 04:06:01 node-1 kernel: [    0.032467] Switched APIC routing to physical flat.
Oct 30 04:06:01 node-1 kernel: [    0.033094] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 30 04:06:01 node-1 kernel: [    0.072746] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 30 04:06:01 node-1 kernel: [    0.072752] TSC deadline timer enabled
Oct 30 04:06:01 node-1 kernel: [    0.072759] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 30 04:06:01 node-1 kernel: [    0.072765] ... version:                3
Oct 30 04:06:01 node-1 kernel: [    0.072766] ... bit width:              48
Oct 30 04:06:01 node-1 kernel: [    0.072767] ... generic registers:      4
Oct 30 04:06:01 node-1 kernel: [    0.072768] ... value mask:             0000ffffffffffff
Oct 30 04:06:01 node-1 kernel: [    0.072769] ... max period:             0000ffffffffffff
Oct 30 04:06:01 node-1 kernel: [    0.072770] ... fixed-purpose events:   3
Oct 30 04:06:01 node-1 kernel: [    0.072771] ... event mask:             000000070000000f
Oct 30 04:06:01 node-1 kernel: [    0.074205] x86: Booting SMP configuration:
Oct 30 04:06:01 node-1 kernel: [    0.088410] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 30 04:06:01 node-1 kernel: [    0.074207] .... node  #0, CPUs:        #1  #2  #3
Oct 30 04:06:01 node-1 kernel: [    0.116325] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 30 04:06:01 node-1 kernel: [    0.270472] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 30 04:06:01 node-1 kernel: [    0.326094] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 30 04:06:01 node-1 kernel: [    0.382952] x86: Booted up 2 nodes, 16 CPUs
Oct 30 04:06:01 node-1 kernel: [    0.382956] smpboot: Total of 16 processors activated (111760.59 BogoMIPS)
Oct 30 04:06:01 node-1 kernel: [    0.407361] devtmpfs: initialized
Oct 30 04:06:01 node-1 kernel: [    0.409905] EVM: security.selinux
Oct 30 04:06:01 node-1 kernel: [    0.409906] EVM: security.SMACK64
Oct 30 04:06:01 node-1 kernel: [    0.409907] EVM: security.ima
Oct 30 04:06:01 node-1 kernel: [    0.409908] EVM: security.capability
Oct 30 04:06:01 node-1 kernel: [    0.409958] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.410627] pinctrl core: initialized pinctrl subsystem
Oct 30 04:06:01 node-1 kernel: [    0.410689] regulator-dummy: no parameters
Oct 30 04:06:01 node-1 kernel: [    0.410720] RTC time:  4:05:24, date: 10/30/16
Oct 30 04:06:01 node-1 kernel: [    0.410754] NET: Registered protocol family 16
Oct 30 04:06:01 node-1 kernel: [    0.410840] cpuidle: using governor ladder
Oct 30 04:06:01 node-1 kernel: [    0.410841] cpuidle: using governor menu
Oct 30 04:06:01 node-1 kernel: [    0.410888] ACPI: bus type PCI registered
Oct 30 04:06:01 node-1 kernel: [    0.410890] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 30 04:06:01 node-1 kernel: [    0.410937] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 30 04:06:01 node-1 kernel: [    0.410939] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 30 04:06:01 node-1 kernel: [    0.424679] PCI: Using configuration type 1 for base access
Oct 30 04:06:01 node-1 kernel: [    0.425678] bio: create slab <bio-0> at 0
Oct 30 04:06:01 node-1 kernel: [    0.425994] ACPI: Added _OSI(Module Device)
Oct 30 04:06:01 node-1 kernel: [    0.425995] ACPI: Added _OSI(Processor Device)
Oct 30 04:06:01 node-1 kernel: [    0.425997] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 30 04:06:01 node-1 kernel: [    0.425998] ACPI: Added _OSI(Processor Aggregator Device)
Oct 30 04:06:01 node-1 kernel: [    0.438690] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 30 04:06:01 node-1 kernel: [    0.449347] ACPI: Interpreter enabled
Oct 30 04:06:01 node-1 kernel: [    0.449353] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 30 04:06:01 node-1 kernel: [    0.449357] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 30 04:06:01 node-1 kernel: [    0.449359] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 30 04:06:01 node-1 kernel: [    0.449366] ACPI: (supports S0 S4 S5)
Oct 30 04:06:01 node-1 kernel: [    0.449367] ACPI: Using IOAPIC for interrupt routing
Oct 30 04:06:01 node-1 kernel: [    0.449409] HEST: Table parsing has been initialized.
Oct 30 04:06:01 node-1 kernel: [    0.449412] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 30 04:06:01 node-1 kernel: [    0.449966] ACPI: No dock devices found.
Oct 30 04:06:01 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 30 04:06:01 node-1 kernel: [    0.461519] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 30 04:06:01 node-1 kernel: [    0.461524] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 04:06:01 node-1 kernel: [    0.461527] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 30 04:06:01 node-1 kernel: [    0.461554] PCI host bridge to bus 0000:ff
Oct 30 04:06:01 node-1 kernel: [    0.461556] pci_bus 0000:ff: root bus resource [bus ff]
Oct 30 04:06:01 node-1 kernel: [    0.461564] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461602] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.461633] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461667] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461696] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.461725] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.461755] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461784] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461813] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461840] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461866] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461892] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461920] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461946] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461972] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.461999] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462027] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462054] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462081] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.462108] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462134] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.462159] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462185] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462214] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.462249] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462280] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462309] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462340] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462371] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462402] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462433] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462464] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462495] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462528] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462562] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462593] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462624] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462653] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462680] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462713] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462746] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462783] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462818] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462850] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462881] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462911] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462940] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.462969] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463001] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463031] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463062] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463090] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463119] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463148] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463176] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463207] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463238] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463294] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 30 04:06:01 node-1 kernel: [    0.463297] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 04:06:01 node-1 kernel: [    0.463300] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 30 04:06:01 node-1 kernel: [    0.463317] PCI host bridge to bus 0000:7f
Oct 30 04:06:01 node-1 kernel: [    0.463319] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 30 04:06:01 node-1 kernel: [    0.463324] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463351] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.463379] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463406] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463428] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.463452] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.463482] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463508] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463530] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463554] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463578] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463602] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463627] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463651] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463676] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463704] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463726] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463748] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463771] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.463794] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463817] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.463839] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463861] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463887] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 30 04:06:01 node-1 kernel: [    0.463919] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463945] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463971] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.463997] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464022] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464049] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464076] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464105] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464131] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464158] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464186] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464213] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464242] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464266] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464290] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464318] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464343] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464369] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464397] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464424] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464450] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464474] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464499] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464525] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464550] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464574] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464603] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464627] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464649] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464674] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464700] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464729] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.464754] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.465997] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 30 04:06:01 node-1 kernel: [    0.466000] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 04:06:01 node-1 kernel: [    0.467126] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 30 04:06:01 node-1 kernel: [    0.467638] PCI host bridge to bus 0000:00
Oct 30 04:06:01 node-1 kernel: [    0.467641] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 30 04:06:01 node-1 kernel: [    0.467642] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 30 04:06:01 node-1 kernel: [    0.467644] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 30 04:06:01 node-1 kernel: [    0.467645] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 30 04:06:01 node-1 kernel: [    0.467646] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 30 04:06:01 node-1 kernel: [    0.467648] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 30 04:06:01 node-1 kernel: [    0.467649] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 30 04:06:01 node-1 kernel: [    0.467655] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 30 04:06:01 node-1 kernel: [    0.467737] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.467768] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.467809] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 30 04:06:01 node-1 kernel: [    0.467828] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.467857] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.467897] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 30 04:06:01 node-1 kernel: [    0.467916] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.467945] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.467985] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 30 04:06:01 node-1 kernel: [    0.468002] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.468072] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.468149] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.468223] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 30 04:06:01 node-1 kernel: [    0.468228] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 30 04:06:01 node-1 kernel: [    0.468314] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 30 04:06:01 node-1 kernel: [    0.468462] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 30 04:06:01 node-1 kernel: [    0.468480] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 30 04:06:01 node-1 kernel: [    0.468558] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.468613] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 30 04:06:01 node-1 kernel: [    0.468636] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.468691] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.468734] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 30 04:06:01 node-1 kernel: [    0.468763] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.468818] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.468861] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 30 04:06:01 node-1 kernel: [    0.468886] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 30 04:06:01 node-1 kernel: [    0.468904] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 30 04:06:01 node-1 kernel: [    0.468982] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.469031] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 30 04:06:01 node-1 kernel: [    0.469060] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 30 04:06:01 node-1 kernel: [    0.469309] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 30 04:06:01 node-1 kernel: [    0.469315] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 30 04:06:01 node-1 kernel: [    0.469321] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.469327] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.469334] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 30 04:06:01 node-1 kernel: [    0.469364] pci 0000:01:00.0: supports D1 D2
Oct 30 04:06:01 node-1 kernel: [    0.479480] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 30 04:06:01 node-1 kernel: [    0.479486] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 30 04:06:01 node-1 kernel: [    0.479490] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 30 04:06:01 node-1 kernel: [    0.479635] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.479669] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 30 04:06:01 node-1 kernel: [    0.487477] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 30 04:06:01 node-1 kernel: [    0.487483] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.487487] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 04:06:01 node-1 kernel: [    0.487571] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.487655] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.487731] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.487777] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 30 04:06:01 node-1 kernel: [    0.487780] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.487782] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 04:06:01 node-1 kernel: [    0.487835] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.487978] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.488032] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 30 04:06:01 node-1 kernel: [    0.488035] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.488037] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 04:06:01 node-1 kernel: [    0.488086] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.488205] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.488245] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.488367] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.488403] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.488522] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.488560] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 30 04:06:01 node-1 kernel: [    0.488679] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 30 04:06:01 node-1 kernel: [    0.488723] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 30 04:06:01 node-1 kernel: [    0.488725] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.488727] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 04:06:01 node-1 kernel: [    0.488786] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 30 04:06:01 node-1 kernel: [    0.488848] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.488925] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.488966] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 30 04:06:01 node-1 kernel: [    0.489045] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 30 04:06:01 node-1 kernel: [    0.489153] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 30 04:06:01 node-1 kernel: [    0.489155] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.489157] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 30 04:06:01 node-1 kernel: [    0.489213] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 30 04:06:01 node-1 kernel: [    0.489267] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.489316] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.489531] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 30 04:06:01 node-1 kernel: [    0.489535] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 30 04:06:01 node-1 kernel: [    0.489599] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 30 04:06:01 node-1 kernel: [    0.489652] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.489700] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.489931] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 30 04:06:01 node-1 kernel: [    0.489934] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 30 04:06:01 node-1 kernel: [    0.489994] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 30 04:06:01 node-1 kernel: [    0.490057] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.490109] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 30 04:06:01 node-1 kernel: [    0.490330] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 30 04:06:01 node-1 kernel: [    0.490333] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 30 04:06:01 node-1 kernel: [    0.490510] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 30 04:06:01 node-1 kernel: [    0.490549] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 30 04:06:01 node-1 kernel: [    0.490627] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 30 04:06:01 node-1 kernel: [    0.490645] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 30 04:06:01 node-1 kernel: [    0.490659] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 30 04:06:01 node-1 kernel: [    0.490672] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 30 04:06:01 node-1 kernel: [    0.490722] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 30 04:06:01 node-1 kernel: [    0.495483] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 30 04:06:01 node-1 kernel: [    0.495492] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 30 04:06:01 node-1 kernel: [    0.495544] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 30 04:06:01 node-1 kernel: [    0.496087] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 30 04:06:01 node-1 kernel: [    0.496090] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 30 04:06:01 node-1 kernel: [    0.496210] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 30 04:06:01 node-1 kernel: [    0.496318] PCI host bridge to bus 0000:80
Oct 30 04:06:01 node-1 kernel: [    0.496320] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 30 04:06:01 node-1 kernel: [    0.496321] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 30 04:06:01 node-1 kernel: [    0.496323] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 30 04:06:01 node-1 kernel: [    0.496331] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.496396] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.496465] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 30 04:06:01 node-1 kernel: [    0.496527] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 30 04:06:01 node-1 kernel: [    0.496533] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 30 04:06:01 node-1 kernel: [    0.496605] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 30 04:06:01 node-1 kernel: [    0.496902] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 30 04:06:01 node-1 kernel: [    0.496933] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 30 04:06:01 node-1 kernel: [    0.496962] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 30 04:06:01 node-1 kernel: [    0.496991] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 30 04:06:01 node-1 kernel: [    0.497021] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 04:06:01 node-1 kernel: [    0.497050] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 04:06:01 node-1 kernel: [    0.497080] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 04:06:01 node-1 kernel: [    0.497110] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 30 04:06:01 node-1 kernel: [    0.497195] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 30 04:06:01 node-1 kernel: [    0.497200] ACPI: \_SB_.UNC1: notify handler is installed
Oct 30 04:06:01 node-1 kernel: [    0.497201] ACPI: \_SB_.UNC0: notify handler is installed
Oct 30 04:06:01 node-1 kernel: [    0.497216] ACPI: \_SB_.PCI0: notify handler is installed
Oct 30 04:06:01 node-1 kernel: [    0.497268] ACPI: \_SB_.PCI1: notify handler is installed
Oct 30 04:06:01 node-1 kernel: [    0.497347] Found 4 acpi root devices
Oct 30 04:06:01 node-1 kernel: [    0.497455] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 30 04:06:01 node-1 kernel: [    0.497457] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 30 04:06:01 node-1 kernel: [    0.497459] vgaarb: loaded
Oct 30 04:06:01 node-1 kernel: [    0.497460] vgaarb: bridge control possible 0000:0c:00.0
Oct 30 04:06:01 node-1 kernel: [    0.497578] SCSI subsystem initialized
Oct 30 04:06:01 node-1 kernel: [    0.497642] libata version 3.00 loaded.
Oct 30 04:06:01 node-1 kernel: [    0.497657] ACPI: bus type USB registered
Oct 30 04:06:01 node-1 kernel: [    0.497667] usbcore: registered new interface driver usbfs
Oct 30 04:06:01 node-1 kernel: [    0.497672] usbcore: registered new interface driver hub
Oct 30 04:06:01 node-1 kernel: [    0.497697] usbcore: registered new device driver usb
Oct 30 04:06:01 node-1 kernel: [    0.497862] PCI: Using ACPI for IRQ routing
Oct 30 04:06:01 node-1 kernel: [    0.501450] PCI: pci_cache_line_size set to 64 bytes
Oct 30 04:06:01 node-1 kernel: [    0.501651] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 30 04:06:01 node-1 kernel: [    0.501652] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 30 04:06:01 node-1 kernel: [    0.501653] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 30 04:06:01 node-1 kernel: [    0.501718] NetLabel: Initializing
Oct 30 04:06:01 node-1 kernel: [    0.501719] NetLabel:  domain hash size = 128
Oct 30 04:06:01 node-1 kernel: [    0.501720] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 30 04:06:01 node-1 kernel: [    0.501730] NetLabel:  unlabeled traffic allowed by default
Oct 30 04:06:01 node-1 kernel: [    0.501786] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 30 04:06:01 node-1 kernel: [    0.501790] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 30 04:06:01 node-1 kernel: [    0.503845] Switched to clocksource hpet
Oct 30 04:06:01 node-1 kernel: [    0.507687] AppArmor: AppArmor Filesystem Enabled
Oct 30 04:06:01 node-1 kernel: [    0.507700] pnp: PnP ACPI init
Oct 30 04:06:01 node-1 kernel: [    0.507707] ACPI: bus type PNP registered
Oct 30 04:06:01 node-1 kernel: [    0.507824] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 30 04:06:01 node-1 kernel: [    0.507832] pnp 00:01: [dma 4]
Oct 30 04:06:01 node-1 kernel: [    0.507849] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 30 04:06:01 node-1 kernel: [    0.507877] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 30 04:06:01 node-1 kernel: [    0.507896] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 30 04:06:01 node-1 kernel: [    0.507917] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 30 04:06:01 node-1 kernel: [    0.507950] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 30 04:06:01 node-1 kernel: [    0.508003] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508005] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 30 04:06:01 node-1 kernel: [    0.508007] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508009] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508010] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508015] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508018] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 30 04:06:01 node-1 kernel: [    0.508019] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508021] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508022] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508024] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508025] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508027] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 30 04:06:01 node-1 kernel: [    0.508028] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 30 04:06:01 node-1 kernel: [    0.508112] pnp 00:07: [dma 0 disabled]
Oct 30 04:06:01 node-1 kernel: [    0.508140] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 30 04:06:01 node-1 kernel: [    0.508215] pnp 00:08: [dma 0 disabled]
Oct 30 04:06:01 node-1 kernel: [    0.508247] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 30 04:06:01 node-1 kernel: [    0.508297] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 30 04:06:01 node-1 kernel: [    0.508643] pnp: PnP ACPI: found 10 devices
Oct 30 04:06:01 node-1 kernel: [    0.508644] ACPI: bus type PNP unregistered
Oct 30 04:06:01 node-1 kernel: [    0.514928] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 30 04:06:01 node-1 kernel: [    0.514931] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 30 04:06:01 node-1 kernel: [    0.514934] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 30 04:06:01 node-1 kernel: [    0.514938] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 30 04:06:01 node-1 kernel: [    0.514940] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.514955] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 30 04:06:01 node-1 kernel: [    0.514984] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 30 04:06:01 node-1 kernel: [    0.514998] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515027] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 30 04:06:01 node-1 kernel: [    0.515041] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 30 04:06:01 node-1 kernel: [    0.515070] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 30 04:06:01 node-1 kernel: [    0.515084] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 30 04:06:01 node-1 kernel: [    0.515113] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 30 04:06:01 node-1 kernel: [    0.515115] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.515129] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515158] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 30 04:06:01 node-1 kernel: [    0.515160] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.515174] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515203] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 30 04:06:01 node-1 kernel: [    0.515205] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.515208] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515212] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 30 04:06:01 node-1 kernel: [    0.515213] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.515216] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515220] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 30 04:06:01 node-1 kernel: [    0.515224] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 30 04:06:01 node-1 kernel: [    0.515232] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 30 04:06:01 node-1 kernel: [    0.515236] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 30 04:06:01 node-1 kernel: [    0.515242] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 30 04:06:01 node-1 kernel: [    0.515243] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 30 04:06:01 node-1 kernel: [    0.515244] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 30 04:06:01 node-1 kernel: [    0.515245] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 30 04:06:01 node-1 kernel: [    0.515246] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 30 04:06:01 node-1 kernel: [    0.515247] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 30 04:06:01 node-1 kernel: [    0.515248] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 30 04:06:01 node-1 kernel: [    0.515248] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 30 04:06:01 node-1 kernel: [    0.515249] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.515250] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515251] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.515252] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515253] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.515254] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515255] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.515255] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515256] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 30 04:06:01 node-1 kernel: [    0.515257] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515258] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 30 04:06:01 node-1 kernel: [    0.515259] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 30 04:06:01 node-1 kernel: [    0.515260] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 30 04:06:01 node-1 kernel: [    0.515261] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 30 04:06:01 node-1 kernel: [    0.515263] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 30 04:06:01 node-1 kernel: [    0.515264] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 30 04:06:01 node-1 kernel: [    0.515303] NET: Registered protocol family 2
Oct 30 04:06:01 node-1 kernel: [    0.515557] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.515890] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.516035] TCP: Hash tables configured (established 262144 bind 65536)
Oct 30 04:06:01 node-1 kernel: [    0.516078] TCP: reno registered
Oct 30 04:06:01 node-1 kernel: [    0.516107] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.516203] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.516351] NET: Registered protocol family 1
Oct 30 04:06:01 node-1 kernel: [    0.555876] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 30 04:06:01 node-1 kernel: [    0.555882] PCI: CLS 64 bytes, default 64
Oct 30 04:06:01 node-1 kernel: [    0.555926] Trying to unpack rootfs image as initramfs...
Oct 30 04:06:01 node-1 kernel: [    0.775326] Freeing initrd memory: 20388K (ffff88003581e000 - ffff880036c07000)
Oct 30 04:06:01 node-1 kernel: [    0.775358] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 30 04:06:01 node-1 kernel: [    0.775361] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 30 04:06:01 node-1 kernel: [    0.775797] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775803] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775808] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775813] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775825] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775842] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775857] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775872] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775884] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775894] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775901] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775907] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775917] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775929] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775942] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.775955] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 30 04:06:01 node-1 kernel: [    0.776061] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 30 04:06:01 node-1 kernel: [    0.776068] Scanning for low memory corruption every 60 seconds
Oct 30 04:06:01 node-1 kernel: [    0.776497] Initialise system trusted keyring
Oct 30 04:06:01 node-1 kernel: [    0.776551] audit: initializing netlink socket (disabled)
Oct 30 04:06:01 node-1 kernel: [    0.776567] type=2000 audit(1477800324.728:1): initialized
Oct 30 04:06:01 node-1 kernel: [    0.794372] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 30 04:06:01 node-1 kernel: [    0.795912] zbud: loaded
Oct 30 04:06:01 node-1 kernel: [    0.796038] VFS: Disk quotas dquot_6.5.2
Oct 30 04:06:01 node-1 kernel: [    0.796077] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 30 04:06:01 node-1 kernel: [    0.796447] fuse init (API version 7.22)
Oct 30 04:06:01 node-1 kernel: [    0.796511] msgmni has been set to 32768
Oct 30 04:06:01 node-1 kernel: [    0.796561] Key type big_key registered
Oct 30 04:06:01 node-1 kernel: [    0.797083] Key type asymmetric registered
Oct 30 04:06:01 node-1 kernel: [    0.797085] Asymmetric key parser 'x509' registered
Oct 30 04:06:01 node-1 kernel: [    0.797108] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 30 04:06:01 node-1 kernel: [    0.797189] io scheduler noop registered
Oct 30 04:06:01 node-1 kernel: [    0.797190] io scheduler deadline registered (default)
Oct 30 04:06:01 node-1 kernel: [    0.797212] io scheduler cfq registered
Oct 30 04:06:01 node-1 kernel: [    0.797611] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    0.797742] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    0.797859] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    0.797969] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    0.798083] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    0.798220] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    0.798579] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 30 04:06:01 node-1 kernel: [    0.798605] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 30 04:06:01 node-1 kernel: [    0.798621] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 30 04:06:01 node-1 kernel: [    0.798630] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798632] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798635] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 30 04:06:01 node-1 kernel: [    0.798640] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798642] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798643] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798645] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798647] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798648] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798649] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798651] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798652] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798654] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798655] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798656] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798659] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 30 04:06:01 node-1 kernel: [    0.798664] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798666] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 30 04:06:01 node-1 kernel: [    0.798681] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798684] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 30 04:06:01 node-1 kernel: [    0.798695] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798697] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 30 04:06:01 node-1 kernel: [    0.798700] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 30 04:06:01 node-1 kernel: [    0.798747] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 30 04:06:01 node-1 kernel: [    0.798753] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 30 04:06:01 node-1 kernel: [    0.798757] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 30 04:06:01 node-1 kernel: [    0.798766] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 30 04:06:01 node-1 kernel: [    0.798807] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 30 04:06:01 node-1 kernel: [    0.798808] vesafb: scrolling: redraw
Oct 30 04:06:01 node-1 kernel: [    0.798810] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 30 04:06:01 node-1 kernel: [    0.819364] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 30 04:06:01 node-1 kernel: [    0.827981] Console: switching to colour frame buffer device 80x30
Oct 30 04:06:01 node-1 kernel: [    0.836658] fb0: VESA VGA frame buffer device
Oct 30 04:06:01 node-1 kernel: [    0.836856] intel_idle: MWAIT substates: 0x2120
Oct 30 04:06:01 node-1 kernel: [    0.836857] intel_idle: v0.4 model 0x3F
Oct 30 04:06:01 node-1 kernel: [    0.836858] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 30 04:06:01 node-1 kernel: [    0.837099] ipmi message handler version 39.2
Oct 30 04:06:01 node-1 kernel: [    0.837372] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 30 04:06:01 node-1 kernel: [    0.837808] ACPI: AC Adapter [P111] (on-line)
Oct 30 04:06:01 node-1 kernel: [    0.843039] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 30 04:06:01 node-1 kernel: [    0.854083] ACPI: Power Button [PWRB]
Oct 30 04:06:01 node-1 kernel: [    0.859858] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 30 04:06:01 node-1 kernel: [    0.871494] ACPI: Power Button [PWRF]
Oct 30 04:06:01 node-1 kernel: [    0.897381] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 30 04:06:01 node-1 kernel: [    0.909049] pstore: Registered erst as persistent store backend
Oct 30 04:06:01 node-1 kernel: [    0.915257] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 30 04:06:01 node-1 kernel: [    0.927217] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 30 04:06:01 node-1 kernel: [    0.953974] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 30 04:06:01 node-1 kernel: [    0.987272] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 30 04:06:01 node-1 kernel: [    1.001318] Linux agpgart interface v0.103
Oct 30 04:06:01 node-1 kernel: [    1.008948] brd: module loaded
Oct 30 04:06:01 node-1 kernel: [    1.015985] loop: module loaded
Oct 30 04:06:01 node-1 kernel: [    1.022697] libphy: Fixed MDIO Bus: probed
Oct 30 04:06:01 node-1 kernel: [    1.029161] tun: Universal TUN/TAP device driver, 1.6
Oct 30 04:06:01 node-1 kernel: [    1.035630] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 30 04:06:01 node-1 kernel: [    1.042149] PPP generic driver version 2.4.2
Oct 30 04:06:01 node-1 kernel: [    1.048521] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 30 04:06:01 node-1 kernel: [    1.054948] ehci-pci: EHCI PCI platform driver
Oct 30 04:06:01 node-1 kernel: [    1.061465] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 30 04:06:01 node-1 kernel: [    1.067865] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 30 04:06:01 node-1 kernel: [    1.080370] ehci-pci 0000:00:1a.0: debug port 2
Oct 30 04:06:01 node-1 kernel: [    1.090554] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 30 04:06:01 node-1 kernel: [    1.090573] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 30 04:06:01 node-1 kernel: [    1.107339] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 30 04:06:01 node-1 kernel: [    1.113402] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 30 04:06:01 node-1 kernel: [    1.119559] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 30 04:06:01 node-1 kernel: [    1.131443] usb usb1: Product: EHCI Host Controller
Oct 30 04:06:01 node-1 kernel: [    1.137460] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 30 04:06:01 node-1 kernel: [    1.143493] usb usb1: SerialNumber: 0000:00:1a.0
Oct 30 04:06:01 node-1 kernel: [    1.149437] hub 1-0:1.0: USB hub found
Oct 30 04:06:01 node-1 kernel: [    1.155195] hub 1-0:1.0: 2 ports detected
Oct 30 04:06:01 node-1 kernel: [    1.160984] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 30 04:06:01 node-1 kernel: [    1.166545] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 30 04:06:01 node-1 kernel: [    1.177416] ehci-pci 0000:00:1d.0: debug port 2
Oct 30 04:06:01 node-1 kernel: [    1.186691] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 30 04:06:01 node-1 kernel: [    1.186695] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 30 04:06:01 node-1 kernel: [    1.203257] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 30 04:06:01 node-1 kernel: [    1.208449] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 30 04:06:01 node-1 kernel: [    1.213742] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 30 04:06:01 node-1 kernel: [    1.224326] usb usb2: Product: EHCI Host Controller
Oct 30 04:06:01 node-1 kernel: [    1.229798] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Oct 30 04:06:01 node-1 kernel: [    1.235349] usb usb2: SerialNumber: 0000:00:1d.0
Oct 30 04:06:01 node-1 kernel: [    1.240872] hub 2-0:1.0: USB hub found
Oct 30 04:06:01 node-1 kernel: [    1.246236] hub 2-0:1.0: 2 ports detected
Oct 30 04:06:01 node-1 kernel: [    1.251543] ehci-platform: EHCI generic platform driver
Oct 30 04:06:01 node-1 kernel: [    1.256788] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 30 04:06:01 node-1 kernel: [    1.262099] ohci-pci: OHCI PCI platform driver
Oct 30 04:06:01 node-1 kernel: [    1.267418] ohci-platform: OHCI generic platform driver
Oct 30 04:06:01 node-1 kernel: [    1.272626] uhci_hcd: USB Universal Host Controller Interface driver
Oct 30 04:06:01 node-1 kernel: [    1.277984] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 30 04:06:01 node-1 kernel: [    1.471036] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 30 04:06:01 node-1 kernel: [    1.770831] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 30 04:06:01 node-1 kernel: [    1.787075] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 30 04:06:01 node-1 kernel: [    1.792689] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 30 04:06:01 node-1 kernel: [    1.798471] hub 1-1:1.0: USB hub found
Oct 30 04:06:01 node-1 kernel: [    1.804062] hub 1-1:1.0: 6 ports detected
Oct 30 04:06:01 node-1 kernel: [    1.918676] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 30 04:06:01 node-1 kernel: [    2.316716] i8042: No controller found
Oct 30 04:06:01 node-1 kernel: [    2.322255] mousedev: PS/2 mouse device common for all mice
Oct 30 04:06:01 node-1 kernel: [    2.327983] rtc_cmos 00:02: RTC can wake from S4
Oct 30 04:06:01 node-1 kernel: [    2.331184] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 30 04:06:01 node-1 kernel: [    2.331185] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 30 04:06:01 node-1 kernel: [    2.331944] hub 2-1:1.0: USB hub found
Oct 30 04:06:01 node-1 kernel: [    2.332184] hub 2-1:1.0: 8 ports detected
Oct 30 04:06:01 node-1 kernel: [    2.356407] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 30 04:06:01 node-1 kernel: [    2.362173] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 30 04:06:01 node-1 kernel: [    2.373511] device-mapper: uevent: version 1.0.3
Oct 30 04:06:01 node-1 kernel: [    2.379235] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 30 04:06:01 node-1 kernel: [    2.390716] ledtrig-cpu: registered to indicate activity on CPUs
Oct 30 04:06:01 node-1 kernel: [    2.396793] TCP: cubic registered
Oct 30 04:06:01 node-1 kernel: [    2.402665] NET: Registered protocol family 10
Oct 30 04:06:01 node-1 kernel: [    2.408719] NET: Registered protocol family 17
Oct 30 04:06:01 node-1 kernel: [    2.414492] Key type dns_resolver registered
Oct 30 04:06:01 node-1 kernel: [    2.420540] Loading compiled-in X.509 certificates
Oct 30 04:06:01 node-1 kernel: [    2.426757] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Oct 30 04:06:01 node-1 kernel: [    2.438401] registered taskstats version 1
Oct 30 04:06:01 node-1 kernel: [    2.446482] Key type trusted registered
Oct 30 04:06:01 node-1 kernel: [    2.454125] Key type encrypted registered
Oct 30 04:06:01 node-1 kernel: [    2.459630] AppArmor: AppArmor sha1 policy hashing enabled
Oct 30 04:06:01 node-1 kernel: [    2.465155] IMA: No TPM chip found, activating TPM-bypass!
Oct 30 04:06:01 node-1 kernel: [    2.471274] regulator-dummy: disabling
Oct 30 04:06:01 node-1 kernel: [    2.476788]   Magic number: 4:215:61
Oct 30 04:06:01 node-1 kernel: [    2.482430] memory memory222: hash matches
Oct 30 04:06:01 node-1 kernel: [    2.487928] rtc_cmos 00:02: setting system clock to 2016-10-30 04:05:26 UTC (1477800326)
Oct 30 04:06:01 node-1 kernel: [    2.500275] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 30 04:06:01 node-1 kernel: [    2.505905] EDD information not available.
Oct 30 04:06:01 node-1 kernel: [    2.511463] PM: Hibernation image not present or could not be loaded.
Oct 30 04:06:01 node-1 kernel: [    2.512315] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 30 04:06:01 node-1 kernel: [    2.523613] Write protecting the kernel read-only data: 12288k
Oct 30 04:06:01 node-1 kernel: [    2.530006] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 30 04:06:01 node-1 kernel: [    2.542834] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 30 04:06:01 node-1 kernel: [    2.574655] device-mapper: multipath: version 1.6.0 loaded
Oct 30 04:06:01 node-1 kernel: [    2.582447] systemd-udevd[216]: starting version 204
Oct 30 04:06:01 node-1 kernel: [    2.606893] md: linear personality registered for level -1
Oct 30 04:06:01 node-1 kernel: [    2.610265] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 30 04:06:01 node-1 kernel: [    2.627705] md: multipath personality registered for level -4
Oct 30 04:06:01 node-1 kernel: [    2.635798] md: raid0 personality registered for level 0
Oct 30 04:06:01 node-1 kernel: [    2.644248] md: raid1 personality registered for level 1
Oct 30 04:06:01 node-1 kernel: [    2.650574] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 30 04:06:01 node-1 kernel: [    2.656764] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 30 04:06:01 node-1 kernel: [    2.657740] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 30 04:06:01 node-1 kernel: [    2.658393] megasas: FW now in Ready state
Oct 30 04:06:01 node-1 kernel: [    2.658486] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658527] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658568] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658615] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658658] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658694] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658732] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658777] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658824] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658859] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658914] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658956] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.658996] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.659065] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.659116] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.659162] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.659338] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 30 04:06:01 node-1 kernel: [    2.695761] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Oct 30 04:06:01 node-1 kernel: [    2.709109] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 30 04:06:01 node-1 kernel: [    2.722968] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 30 04:06:01 node-1 kernel: [    2.729987] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.729992] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.729996] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.730001] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.730050] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 30 04:06:01 node-1 kernel: [    2.749818] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Oct 30 04:06:01 node-1 kernel: [    2.757987] raid6: sse2x1    9688 MB/s
Oct 30 04:06:01 node-1 kernel: [    2.769980] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct 30 04:06:01 node-1 kernel: [    2.783440] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 30 04:06:01 node-1 kernel: [    2.825895] raid6: sse2x2   10288 MB/s
Oct 30 04:06:01 node-1 kernel: [    2.897835] raid6: sse2x4   10143 MB/s
Oct 30 04:06:01 node-1 kernel: [    2.969766] raid6: avx2x1   14954 MB/s
Oct 30 04:06:01 node-1 kernel: [    3.041710] raid6: avx2x2   18889 MB/s
Oct 30 04:06:01 node-1 kernel: [    3.113643] raid6: avx2x4   21339 MB/s
Oct 30 04:06:01 node-1 kernel: [    3.119656] raid6: using algorithm avx2x4 (21339 MB/s)
Oct 30 04:06:01 node-1 kernel: [    3.125599] raid6: using avx2x2 recovery algorithm
Oct 30 04:06:01 node-1 kernel: [    3.131422] megasas:IOC Init cmd success
Oct 30 04:06:01 node-1 kernel: [    3.131424] Switched to clocksource tsc
Oct 30 04:06:01 node-1 kernel: [    3.131579] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.131605] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.131642] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.131681] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.131717] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.131751] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.131859] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.143691] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Oct 30 04:06:01 node-1 kernel: [    3.143693] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 30 04:06:01 node-1 kernel: [    3.143694] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 30 04:06:01 node-1 kernel: [    3.143758] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.143796] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.143827] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.143861] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.144010] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.146335] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 30 04:06:01 node-1 kernel: [    3.146336] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 30 04:06:01 node-1 kernel: [    3.146337] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 30 04:06:01 node-1 kernel: [    3.146338] usb 2-1.4: Manufacturer: Avocent
Oct 30 04:06:01 node-1 kernel: [    3.146338] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 30 04:06:01 node-1 kernel: [    3.154932] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Oct 30 04:06:01 node-1 kernel: [    3.154933] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 30 04:06:01 node-1 kernel: [    3.154934] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 30 04:06:01 node-1 kernel: [    3.155005] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.155041] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.155075] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.155079] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.155165] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 30 04:06:01 node-1 kernel: [    3.157613] megasas: INIT adapter done
Oct 30 04:06:01 node-1 kernel: [    3.229552] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 30 04:06:01 node-1 kernel: [    3.229910] scsi0 : LSI SAS based MegaRAID driver
Oct 30 04:06:01 node-1 kernel: [    3.231259] xor: automatically using best checksumming function:
Oct 30 04:06:01 node-1 kernel: [    3.231272] hidraw: raw HID events driver (C) Jiri Kosina
Oct 30 04:06:01 node-1 kernel: [    3.236944] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 30 04:06:01 node-1 kernel: [    3.247792] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 30 04:06:01 node-1 kernel: [    3.251948] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 30 04:06:01 node-1 kernel: [    3.251953] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 30 04:06:01 node-1 kernel: [    3.252343] sd 0:2:0:0: [sda] Write Protect is off
Oct 30 04:06:01 node-1 kernel: [    3.252344] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 30 04:06:01 node-1 kernel: [    3.252424] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 30 04:06:01 node-1 kernel: [    3.269525]    avx       : 35909.000 MB/sec
Oct 30 04:06:01 node-1 kernel: [    3.274765]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct 30 04:06:01 node-1 kernel: [    3.276432] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 30 04:06:01 node-1 kernel: [    3.349333] usbcore: registered new interface driver usbhid
Oct 30 04:06:01 node-1 kernel: [    3.349333] usbhid: USB HID core driver
Oct 30 04:06:01 node-1 kernel: [    3.352935] async_tx: api initialized (async)
Oct 30 04:06:01 node-1 kernel: [    3.389758] random: lvm urandom read with 26 bits of entropy available
Oct 30 04:06:01 node-1 kernel: [    3.408676] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Oct 30 04:06:01 node-1 kernel: [    3.421354] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Oct 30 04:06:01 node-1 kernel: [    3.434112] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Oct 30 04:06:01 node-1 kernel: [    3.447269] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Oct 30 04:06:01 node-1 kernel: [    3.460720] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Oct 30 04:06:01 node-1 kernel: [    3.460904] md: raid6 personality registered for level 6
Oct 30 04:06:01 node-1 kernel: [    3.460904] md: raid5 personality registered for level 5
Oct 30 04:06:01 node-1 kernel: [    3.460904] md: raid4 personality registered for level 4
Oct 30 04:06:01 node-1 kernel: [    3.494681] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Oct 30 04:06:01 node-1 kernel: [    3.510040] md: raid10 personality registered for level 10
Oct 30 04:06:01 node-1 kernel: [    3.564957] multipathd (372): /proc/372/oom_adj is deprecated, please use /proc/372/oom_score_adj instead.
Oct 30 04:06:01 node-1 kernel: [    3.655766] bio: create slab <bio-1> at 1
Oct 30 04:06:01 node-1 kernel: [    4.420304] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 30 04:06:01 node-1 kernel: [    5.003454] init: plymouth-upstart-bridge main process (553) terminated with status 1
Oct 30 04:06:01 node-1 kernel: [    5.016283] init: plymouth-upstart-bridge main process ended, respawning
Oct 30 04:06:01 node-1 kernel: [    5.025646] init: plymouth-upstart-bridge main process (565) terminated with status 1
Oct 30 04:06:01 node-1 kernel: [    5.038106] init: plymouth-upstart-bridge main process ended, respawning
Oct 30 04:06:01 node-1 kernel: [    5.183355] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 30 04:06:01 node-1 kernel: [    5.224715] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 30 04:06:01 node-1 kernel: [    5.254080] random: nonblocking pool is initialized
Oct 30 04:06:01 node-1 kernel: [    5.343024] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 30 04:06:01 node-1 kernel: [    5.373019] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 30 04:06:01 node-1 kernel: [    5.443241] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 30 04:06:01 node-1 kernel: [    5.630808] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 30 04:06:01 node-1 kernel: [    5.665755] XFS (dm-0): Mounting Filesystem
Oct 30 04:06:01 node-1 kernel: [    5.882658] XFS (dm-0): Ending clean mount
Oct 30 04:06:01 node-1 kernel: [    5.932155] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 30 04:06:01 node-1 kernel: [    5.961961] XFS (dm-1): Mounting Filesystem
Oct 30 04:06:01 node-1 kernel: [    6.085415] XFS (dm-1): Ending clean mount
Oct 30 04:06:01 node-1 kernel: [    7.948894] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 30 04:06:01 node-1 kernel: [    7.976743] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 30 04:06:01 node-1 kernel: [    8.165536] systemd-udevd[783]: starting version 204
Oct 30 04:06:01 node-1 kernel: [    8.356784] power_meter ACPI000D:00: Found ACPI power meter.
Oct 30 04:06:01 node-1 kernel: [    8.356810] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 30 04:06:01 node-1 kernel: [    8.406403] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 30 04:06:01 node-1 kernel: [    8.406410] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 30 04:06:01 node-1 kernel: [    8.406413] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 30 04:06:01 node-1 kernel: [    8.406416] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 30 04:06:01 node-1 kernel: [    8.406441] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 30 04:06:01 node-1 kernel: [    8.410895] IPMI System Interface driver.
Oct 30 04:06:01 node-1 kernel: [    8.410935] ipmi_si: probing via ACPI
Oct 30 04:06:01 node-1 kernel: [    8.410958] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 30 04:06:01 node-1 kernel: [    8.410959] ipmi_si: Adding ACPI-specified kcs state machine
Oct 30 04:06:01 node-1 kernel: [    8.410969] ipmi_si: probing via SMBIOS
Oct 30 04:06:01 node-1 kernel: [    8.410970] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 30 04:06:01 node-1 kernel: [    8.410970] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 30 04:06:01 node-1 kernel: [    8.410972] ipmi_si: probing via SPMI
Oct 30 04:06:01 node-1 kernel: [    8.410973] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 30 04:06:01 node-1 kernel: [    8.410974] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 30 04:06:01 node-1 kernel: [    8.410975] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 30 04:06:01 node-1 kernel: [    8.417315] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 30 04:06:01 node-1 kernel: [    8.433346] wmi: Mapper loaded
Oct 30 04:06:01 node-1 kernel: [    8.481568] systemd-udevd[802]: renamed network interface eth0 to enp6s0
Oct 30 04:06:01 node-1 kernel: [    8.513450] systemd-udevd[806]: renamed network interface eth1 to enp7s0
Oct 30 04:06:01 node-1 kernel: [    8.545410] systemd-udevd[812]: renamed network interface eth2 to enp8s0
Oct 30 04:06:01 node-1 kernel: [    8.552084] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 30 04:06:01 node-1 kernel: [    8.552091] ipmi_si 00:09: IPMI kcs interface initialized
Oct 30 04:06:01 node-1 kernel: [    8.569394] systemd-udevd[801]: renamed network interface eth3 to enp9s0
Oct 30 04:06:01 node-1 kernel: [    8.896756] type=1400 audit(1477800332.911:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=982 comm="apparmor_parser"
Oct 30 04:06:01 node-1 kernel: [    8.896927] type=1400 audit(1477800332.911:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=982 comm="apparmor_parser"
Oct 30 04:06:01 node-1 kernel: [    8.897060] type=1400 audit(1477800332.911:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=982 comm="apparmor_parser"
Oct 30 04:06:01 node-1 kernel: [    8.910697] type=1400 audit(1477800332.923:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1064 comm="apparmor_parser"
Oct 30 04:06:01 node-1 kernel: [    8.910939] type=1400 audit(1477800332.923:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1064 comm="apparmor_parser"
Oct 30 04:06:01 node-1 kernel: [    8.911147] type=1400 audit(1477800332.923:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1064 comm="apparmor_parser"
Oct 30 04:06:01 node-1 kernel: [    8.927296] type=1400 audit(1477800332.939:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=983 comm="apparmor_parser"
Oct 30 04:06:01 node-1 kernel: [    8.927436] type=1400 audit(1477800332.939:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=983 comm="apparmor_parser"
Oct 30 04:06:01 node-1 kernel: [    8.927557] type=1400 audit(1477800332.939:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=983 comm="apparmor_parser"
Oct 30 04:06:01 node-1 kernel: [    8.934569] type=1400 audit(1477800332.947:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=995 comm="apparmor_parser"
Oct 30 04:06:01 node-1 kernel: [    9.535159] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 30 04:06:01 node-1 kernel: [    9.538285] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 30 04:06:01 node-1 kernel: [    9.721815] enic 0000:06:00.0 enp6s0: Link UP
Oct 30 04:06:01 node-1 kernel: [    9.722937] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 30 04:06:01 node-1 kernel: [    9.722943] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 30 04:06:01 node-1 kernel: [   18.930649] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 30 04:06:02 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 30 04:06:02 node-1 kernel: [   37.732454] init: failsafe main process (8430) killed by TERM signal
Oct 30 04:06:02 node-1 dbus[8463]: [system] AppArmor D-Bus mediation is enabled
Oct 30 04:06:03 node-1 kernel: [   37.972424] audit_printk_skb: 30 callbacks suppressed
Oct 30 04:06:03 node-1 kernel: [   37.972425] type=1400 audit(1477800362.999:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8556 comm="apparmor_parser"
Oct 30 04:06:03 node-1 kernel: [   37.972696] type=1400 audit(1477800362.999:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8555 comm="apparmor_parser"
Oct 30 04:06:03 node-1 kernel: [   37.972700] type=1400 audit(1477800362.999:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8555 comm="apparmor_parser"
Oct 30 04:06:03 node-1 kernel: [   37.972702] type=1400 audit(1477800362.999:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8555 comm="apparmor_parser"
Oct 30 04:06:03 node-1 kernel: [   37.972938] type=1400 audit(1477800362.999:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8555 comm="apparmor_parser"
Oct 30 04:06:03 node-1 kernel: [   37.972939] type=1400 audit(1477800362.999:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8555 comm="apparmor_parser"
Oct 30 04:06:03 node-1 kernel: [   37.973052] type=1400 audit(1477800362.999:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8555 comm="apparmor_parser"
Oct 30 04:06:03 node-1 kernel: [   38.043563] type=1400 audit(1477800363.071:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8558 comm="apparmor_parser"
Oct 30 04:06:03 node-1 cron[8588]: (CRON) INFO (pidfile fd = 3)
Oct 30 04:06:03 node-1 anacron[8604]: Anacron 2.3 started on 2016-10-30
Oct 30 04:06:03 node-1 cron[8612]: (CRON) STARTUP (fork ok)
Oct 30 04:06:03 node-1 anacron[8604]: Will run job `cron.daily' in 5 min.
Oct 30 04:06:03 node-1 anacron[8604]: Will run job `cron.weekly' in 10 min.
Oct 30 04:06:03 node-1 anacron[8604]: Will run job `cron.monthly' in 15 min.
Oct 30 04:06:03 node-1 anacron[8604]: Jobs will be executed sequentially
Oct 30 04:06:03 node-1 cron[8612]: (CRON) INFO (Running @reboot jobs)
Oct 30 04:06:03 node-1 multipathd: path checkers start up
Oct 30 04:06:03 node-1 postfix/master[8767]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 30 04:06:06 node-1 puppet-agent[8951]: Reopening log files
Oct 30 04:06:07 node-1 puppet-agent[8951]: Could not request certificate: Connection refused - connect(2)
Oct 30 04:06:21 node-1 puppet-user[9031]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 30 04:06:21 node-1 puppet-user[9031]: Compiled catalog for node-1.domain.tld in environment production in 0.03 seconds
Oct 30 04:06:22 node-1 puppet-user[9031]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 30 04:06:22 node-1 puppet-user[9031]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 30 04:06:22 node-1 puppet-user[9031]: Finished catalog run in 0.98 seconds
Oct 30 04:06:24 node-1 multipathd: uevent trigger error
Oct 30 04:06:24 node-1 puppet-user[9471]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 30 04:06:24 node-1 puppet-user[9471]: Compiled catalog for node-1.domain.tld in environment production in 0.09 seconds
Oct 30 04:06:24 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 30 04:06:24 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 30 04:06:24 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Oct 30 04:06:24 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 30 04:06:24 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 30 04:06:24 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 30 04:06:24 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 30 04:06:24 node-1 puppet-user[9471]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 30 04:06:24 node-1 puppet-user[9471]: Finished catalog run in 0.06 seconds
Oct 30 04:06:26 node-1 puppet-user[10057]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 30 04:06:26 node-1 puppet-user[10057]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 30 04:06:26 node-1 puppet-user[10057]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 30 04:06:26 node-1 puppet-user[10057]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 30 04:06:26 node-1 puppet-user[10057]: Finished catalog run in 0.03 seconds
Oct 30 04:06:28 node-1 puppet-user[10520]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 30 04:06:28 node-1 puppet-user[10520]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 30 04:06:28 node-1 puppet-user[10520]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 30 04:06:28 node-1 puppet-user[10520]: Finished catalog run in 0.04 seconds
Oct 30 04:06:29 node-1 puppet-user[10972]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 30 04:06:29 node-1 puppet-user[10972]: Compiled catalog for node-1.domain.tld in environment production in 0.16 seconds
Oct 30 04:06:29 node-1 puppet-user[10972]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 30 04:06:30 node-1 puppet-user[10972]: (/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
Oct 30 04:06:30 node-1 puppet-user[10972]: (/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
Oct 30 04:06:30 node-1 puppet-user[10972]: Finished catalog run in 0.80 seconds
Oct 30 04:06:31 node-1 puppet-user[11473]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 30 04:06:31 node-1 puppet-user[11473]: Compiled catalog for node-1.domain.tld in environment production in 0.23 seconds
Oct 30 04:06:32 node-1 puppet-user[11473]: (/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
Oct 30 04:06:32 node-1 puppet-user[11473]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 30 04:06:32 node-1 puppet-user[11473]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 30 04:06:32 node-1 puppet-user[11473]: (/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
Oct 30 04:06:32 node-1 puppet-user[11473]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 30 04:06:32 node-1 puppet-user[11473]: Finished catalog run in 0.29 seconds
Oct 30 04:06:33 node-1 puppet-user[11945]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 30 04:06:33 node-1 puppet-user[11945]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Oct 30 04:06:33 node-1 puppet-user[11945]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 30 04:06:33 node-1 kernel: [   68.918719] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 30 04:06:33 node-1 kernel: [   68.918769] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Oct 30 04:06:33 node-1 puppet-user[11945]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Oct 30 04:06:34 node-1 puppet-user[11945]: Finished catalog run in 0.05 seconds
Oct 30 04:06:35 node-1 puppet-user[12398]: (Scope(Class[main])) MODULAR: sync_time
Oct 30 04:06:35 node-1 puppet-user[12398]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 30 04:06:35 node-1 ntpdate[12814]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 30 04:06:41 node-1 ntpdate[12814]: adjust time server 10.20.0.2 offset -0.493364 sec
Oct 30 04:06:41 node-1 puppet-user[12398]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 30 04:06:41 node-1 puppet-user[12398]: Finished catalog run in 6.17 seconds
Oct 30 04:06:47 node-1 puppet-user[13196]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 30 04:06:47 node-1 puppet-user[13196]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 30 04:06:47 node-1 puppet-user[13196]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 30 04:06:47 node-1 puppet-user[13196]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Oct 30 04:06:47 node-1 puppet-user[13196]: Finished catalog run in 0.06 seconds
Oct 30 04:06:48 node-1 puppet-user[13649]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 30 04:06:49 node-1 kernel: [   83.958021] init: plymouth-upstart-bridge main process ended, respawning
Oct 30 04:06:49 node-1 puppet-user[13649]: Compiled catalog for node-1.domain.tld in environment production in 0.52 seconds
Oct 30 04:06:49 node-1 puppet-agent[8951]: Could not run: SIGTERM
Oct 30 04:06:49 node-1 puppet-user[13649]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Oct 30 04:06:49 node-1 kernel: [   84.260823] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 30 04:06:49 node-1 puppet-user[13649]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Oct 30 04:06:49 node-1 puppet-user[13649]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Oct 30 04:06:49 node-1 puppet-user[13649]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Oct 30 04:06:49 node-1 puppet-user[13649]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 30 04:06:49 node-1 puppet-user[13649]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct 30 04:06:49 node-1 puppet-user[13649]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 30 04:06:49 node-1 ec2: 
Oct 30 04:06:49 node-1 ec2: #############################################################
Oct 30 04:06:49 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 30 04:06:49 node-1 ec2: 1024 ea:4e:0a:23:ad:5e:de:71:d1:a2:81:1e:6b:1c:12:60  root@node-1.domain.tld (DSA)
Oct 30 04:06:49 node-1 puppet-user[13649]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct 30 04:06:49 node-1 ec2: 256 e2:cc:88:64:57:17:a6:08:32:e4:15:55:36:93:42:af  root@node-1.domain.tld (ECDSA)
Oct 30 04:06:49 node-1 ec2: 256 b7:4f:54:e2:8c:06:30:e5:75:a1:d9:e2:dd:b2:23:2f  root@node-1.domain.tld (ED25519)
Oct 30 04:06:49 node-1 ec2: 2048 ec:7a:a1:19:ea:b6:42:e9:c8:89:d1:01:84:22:69:13  root@node-1.domain.tld (RSA)
Oct 30 04:06:49 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 30 04:06:49 node-1 ec2: #############################################################
Oct 30 04:06:49 node-1 puppet-user[13649]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Oct 30 04:06:49 node-1 puppet-user[13649]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct 30 04:06:50 node-1 puppet-user[13649]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 30 04:06:50 node-1 puppet-user[13649]: Finished catalog run in 0.84 seconds
Oct 30 04:06:51 node-1 puppet-user[14324]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 30 04:06:51 node-1 puppet-user[14324]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Oct 30 04:06:54 node-1 puppet-user[14324]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 30 04:07:01 node-1 CRON[15646]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Oct 30 04:07:20 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 30 04:07:20 node-1 nailgun-agent: I, [2016-10-30T04:07:20.508936 #15649]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 30 04:07:21 node-1 puppet-user[14324]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 30 04:07:21 node-1 puppet-user[14324]: Finished catalog run in 29.91 seconds
Oct 30 04:07:23 node-1 puppet-user[16877]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 30 04:07:24 node-1 puppet-user[16877]: Compiled catalog for node-1.domain.tld in environment production in 0.57 seconds
Oct 30 04:07:24 node-1 puppet-user[16877]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 30 04:07:24 node-1 puppet-user[16877]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 30 04:07:24 node-1 puppet-user[16877]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 30 04:07:24 node-1 puppet-user[16877]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 30 04:07:24 node-1 puppet-user[16877]: Finished catalog run in 0.10 seconds
Oct 30 04:07:26 node-1 puppet-user[17339]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 30 04:07:26 node-1 puppet-user[17339]: Compiled catalog for node-1.domain.tld in environment production in 0.85 seconds
Oct 30 04:07:27 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 30 04:07:27 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 30 04:07:27 node-1 crontab[17775]: (root) LIST (root)
Oct 30 04:07:27 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 30 04:07:27 node-1 crontab[17776]: (root) REPLACE (root)
Oct 30 04:07:28 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 30 04:07:29 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 30 04:07:30 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Oct 30 04:07:30 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 30 04:07:30 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Oct 30 04:07:30 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Oct 30 04:07:30 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 30 04:07:30 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 30 04:07:30 node-1 puppet-user[17339]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct 30 04:07:30 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8403" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 30 04:07:30 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 30 04:07:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:44 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:44 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:44 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:44 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:49 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:49 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:49 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:49 node-1 multipathd: uevent trigger error
<27>Oct 30 04:07:49 node-1 multipathd: uevent trigger error
<27>Oct 30 04:08:44 node-1 ntpdate[28869]: no servers can be used, exiting
<27>Oct 30 04:09:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:29 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:29 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:29 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:29 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:29 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:09:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:10:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:10:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:10:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:10:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:10:35 node-1 multipathd: uevent trigger error
<27>Oct 30 04:10:35 node-1 multipathd: uevent trigger error
<27>Oct 30 04:10:35 node-1 multipathd: uevent trigger error
<27>Oct 30 04:10:35 node-1 multipathd: uevent trigger error
<27>Oct 30 04:10:37 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 04:10:37 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 04:10:43 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 04:10:43 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 04:10:49 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 04:10:55 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 04:10:55 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 30 04:11:02 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:02 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:02 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:02 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:02 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:12 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:12 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:12 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:12 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:12 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:12 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:59 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:59 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:59 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:59 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:59 node-1 multipathd: uevent trigger error
<27>Oct 30 04:11:59 node-1 multipathd: uevent trigger error
<129>Oct 30 04:12:01 node-1 haproxy[24849]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 63ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:01 node-1 haproxy[24849]: proxy odl-neutron-endpoint has no server available!
<129>Oct 30 04:12:02 node-1 haproxy[24856]: 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>Oct 30 04:12:02 node-1 haproxy[24856]: proxy odl-jetty has no server available!
<27>Oct 30 04:12:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:25 node-1 multipathd: uevent trigger error
<129>Oct 30 04:12:27 node-1 haproxy[27480]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:27 node-1 haproxy[27480]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:28 node-1 haproxy[27484]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:28 node-1 haproxy[27484]: proxy mysqld has no server available!
<27>Oct 30 04:12:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:34 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:34 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:34 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:34 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:34 node-1 multipathd: uevent trigger error
<129>Oct 30 04:12:36 node-1 haproxy[30116]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:37 node-1 haproxy[30120]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:37 node-1 haproxy[30120]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:37 node-1 haproxy[30120]: proxy mysqld has no server available!
<129>Oct 30 04:12:37 node-1 haproxy[30120]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:37 node-1 haproxy[30120]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:38 node-1 haproxy[30120]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:38 node-1 haproxy[30120]: proxy object-storage has no server available!
<27>Oct 30 04:12:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:40 node-1 multipathd: uevent trigger error
<129>Oct 30 04:12:42 node-1 haproxy[31450]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:42 node-1 haproxy[31450]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:42 node-1 haproxy[31450]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:42 node-1 haproxy[31450]: proxy neutron has no server available!
<129>Oct 30 04:12:43 node-1 haproxy[31454]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:43 node-1 haproxy[31454]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:43 node-1 haproxy[31454]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:43 node-1 haproxy[31454]: proxy mysqld has no server available!
<129>Oct 30 04:12:43 node-1 haproxy[31454]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:43 node-1 haproxy[31454]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:43 node-1 haproxy[31454]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:43 node-1 haproxy[31454]: proxy object-storage has no server available!
<27>Oct 30 04:12:45 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:45 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:45 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:45 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:45 node-1 multipathd: uevent trigger error
<129>Oct 30 04:12:48 node-1 haproxy[352]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:48 node-1 haproxy[352]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:48 node-1 haproxy[352]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:48 node-1 haproxy[352]: proxy keystone-1 has no server available!
<129>Oct 30 04:12:48 node-1 haproxy[352]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:48 node-1 haproxy[352]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:48 node-1 haproxy[352]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:48 node-1 haproxy[352]: proxy keystone-2 has no server available!
<129>Oct 30 04:12:48 node-1 haproxy[352]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:48 node-1 haproxy[352]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:49 node-1 haproxy[356]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:49 node-1 haproxy[356]: proxy neutron has no server available!
<129>Oct 30 04:12:49 node-1 haproxy[356]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:49 node-1 haproxy[356]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:49 node-1 haproxy[356]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:49 node-1 haproxy[356]: proxy mysqld has no server available!
<129>Oct 30 04:12:49 node-1 haproxy[356]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:49 node-1 haproxy[356]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:49 node-1 haproxy[356]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:49 node-1 haproxy[356]: proxy object-storage has no server available!
<27>Oct 30 04:12:51 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:51 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:51 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:51 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:51 node-1 multipathd: uevent trigger error
<129>Oct 30 04:12:53 node-1 haproxy[1716]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:53 node-1 haproxy[1716]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:53 node-1 haproxy[1716]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:53 node-1 haproxy[1716]: proxy keystone-1 has no server available!
<129>Oct 30 04:12:53 node-1 haproxy[1716]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:53 node-1 haproxy[1716]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:53 node-1 haproxy[1716]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:53 node-1 haproxy[1716]: proxy keystone-2 has no server available!
<129>Oct 30 04:12:54 node-1 haproxy[1720]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:54 node-1 haproxy[1720]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:54 node-1 haproxy[1720]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:54 node-1 haproxy[1720]: proxy neutron has no server available!
<129>Oct 30 04:12:54 node-1 haproxy[1720]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:54 node-1 haproxy[1720]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:54 node-1 haproxy[1720]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:54 node-1 haproxy[1720]: proxy mysqld has no server available!
<129>Oct 30 04:12:54 node-1 haproxy[1720]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:54 node-1 haproxy[1720]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:54 node-1 haproxy[1720]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:54 node-1 haproxy[1720]: proxy object-storage has no server available!
<129>Oct 30 04:12:54 node-1 haproxy[1720]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:55 node-1 haproxy[1720]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:55 node-1 haproxy[1720]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:55 node-1 haproxy[1720]: proxy aodh has no server available!
<27>Oct 30 04:12:56 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:56 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:57 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:57 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:57 node-1 multipathd: uevent trigger error
<27>Oct 30 04:12:57 node-1 multipathd: uevent trigger error
<129>Oct 30 04:12:59 node-1 haproxy[3156]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:59 node-1 haproxy[3156]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:59 node-1 haproxy[3156]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:59 node-1 haproxy[3156]: proxy keystone-1 has no server available!
<129>Oct 30 04:12:59 node-1 haproxy[3156]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:59 node-1 haproxy[3156]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:59 node-1 haproxy[3156]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:59 node-1 haproxy[3156]: proxy keystone-2 has no server available!
<129>Oct 30 04:12:59 node-1 haproxy[3156]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:59 node-1 haproxy[3156]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:12:59 node-1 haproxy[3156]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:12:59 node-1 haproxy[3156]: proxy neutron has no server available!
<129>Oct 30 04:12:59 node-1 haproxy[3156]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:00 node-1 haproxy[3160]: proxy mysqld has no server available!
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:00 node-1 haproxy[3160]: proxy object-storage has no server available!
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:00 node-1 haproxy[3160]: proxy aodh has no server available!
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:00 node-1 haproxy[3160]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:00 node-1 haproxy[3160]: proxy ceilometer has no server available!
<27>Oct 30 04:13:02 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:02 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:02 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:02 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:02 node-1 multipathd: uevent trigger error
<129>Oct 30 04:13:04 node-1 haproxy[4576]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:04 node-1 haproxy[4576]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:04 node-1 haproxy[4576]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:04 node-1 haproxy[4576]: proxy keystone-1 has no server available!
<129>Oct 30 04:13:04 node-1 haproxy[4576]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:05 node-1 haproxy[4580]: proxy keystone-2 has no server available!
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:05 node-1 haproxy[4580]: proxy neutron has no server available!
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:05 node-1 haproxy[4580]: proxy mysqld has no server available!
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:05 node-1 haproxy[4580]: proxy object-storage has no server available!
<129>Oct 30 04:13:05 node-1 haproxy[4580]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:06 node-1 haproxy[4580]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:06 node-1 haproxy[4580]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:06 node-1 haproxy[4580]: proxy aodh has no server available!
<129>Oct 30 04:13:06 node-1 haproxy[4580]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:06 node-1 haproxy[4580]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:06 node-1 haproxy[4580]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:06 node-1 haproxy[4580]: proxy ceilometer has no server available!
<27>Oct 30 04:13:07 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:07 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:07 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:07 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:07 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:07 node-1 multipathd: uevent trigger error
<129>Oct 30 04:13:10 node-1 haproxy[6028]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:10 node-1 haproxy[6028]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:10 node-1 haproxy[6028]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:10 node-1 haproxy[6028]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:10 node-1 haproxy[6028]: proxy keystone-1 has no server available!
<129>Oct 30 04:13:10 node-1 haproxy[6028]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:10 node-1 haproxy[6028]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:10 node-1 haproxy[6028]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:10 node-1 haproxy[6028]: proxy keystone-2 has no server available!
<129>Oct 30 04:13:10 node-1 haproxy[6028]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:10 node-1 haproxy[6028]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:10 node-1 haproxy[6028]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:10 node-1 haproxy[6028]: proxy neutron has no server available!
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:11 node-1 haproxy[6032]: proxy mysqld has no server available!
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:11 node-1 haproxy[6032]: proxy object-storage has no server available!
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:11 node-1 haproxy[6032]: proxy aodh has no server available!
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:11 node-1 haproxy[6032]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:11 node-1 haproxy[6032]: proxy ceilometer has no server available!
<27>Oct 30 04:13:13 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:13 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:13 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:13 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:13 node-1 multipathd: uevent trigger error
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:16 node-1 haproxy[7528]: proxy keystone-1 has no server available!
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:16 node-1 haproxy[7528]: proxy keystone-2 has no server available!
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:16 node-1 haproxy[7528]: proxy glance-api has no server available!
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:16 node-1 haproxy[7528]: proxy glance-glare has no server available!
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:16 node-1 haproxy[7528]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:16 node-1 haproxy[7528]: proxy neutron has no server available!
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:17 node-1 haproxy[7532]: proxy glance-registry has no server available!
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:17 node-1 haproxy[7532]: proxy mysqld has no server available!
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:17 node-1 haproxy[7532]: proxy object-storage has no server available!
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:17 node-1 haproxy[7532]: proxy aodh has no server available!
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:17 node-1 haproxy[7532]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:17 node-1 haproxy[7532]: proxy ceilometer has no server available!
<27>Oct 30 04:13:19 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:19 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:19 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:19 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:19 node-1 multipathd: uevent trigger error
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:22 node-1 haproxy[9065]: proxy keystone-1 has no server available!
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:22 node-1 haproxy[9065]: proxy keystone-2 has no server available!
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:22 node-1 haproxy[9065]: proxy nova-api has no server available!
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:22 node-1 haproxy[9065]: proxy nova-metadata-api has no server available!
<27>Oct 30 04:13:22 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:22 node-1 haproxy[9065]: proxy glance-api has no server available!
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:22 node-1 haproxy[9065]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:23 node-1 haproxy[9073]: proxy glance-glare has no server available!
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:23 node-1 haproxy[9073]: proxy neutron has no server available!
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:23 node-1 haproxy[9073]: proxy glance-registry has no server available!
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:23 node-1 haproxy[9073]: proxy mysqld has no server available!
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:23 node-1 haproxy[9073]: proxy object-storage has no server available!
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:23 node-1 haproxy[9073]: proxy aodh has no server available!
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:23 node-1 haproxy[9073]: proxy ceilometer has no server available!
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:23 node-1 haproxy[9073]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:23 node-1 haproxy[9073]: proxy nova-novncproxy has no server available!
<27>Oct 30 04:13:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:25 node-1 multipathd: uevent trigger error
<129>Oct 30 04:13:27 node-1 haproxy[10497]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:27 node-1 haproxy[10497]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:27 node-1 haproxy[10497]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:27 node-1 haproxy[10497]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:27 node-1 haproxy[10497]: proxy keystone-1 has no server available!
<129>Oct 30 04:13:27 node-1 haproxy[10497]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:27 node-1 haproxy[10497]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:27 node-1 haproxy[10497]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:27 node-1 haproxy[10497]: proxy keystone-2 has no server available!
<129>Oct 30 04:13:27 node-1 haproxy[10497]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:27 node-1 haproxy[10497]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:28 node-1 haproxy[10501]: proxy nova-api has no server available!
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:28 node-1 haproxy[10501]: proxy nova-metadata-api has no server available!
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:28 node-1 haproxy[10501]: proxy cinder-api has no server available!
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:28 node-1 haproxy[10501]: proxy glance-api has no server available!
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:28 node-1 haproxy[10501]: proxy glance-glare has no server available!
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:28 node-1 haproxy[10501]: proxy neutron has no server available!
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:28 node-1 haproxy[10501]: proxy glance-registry has no server available!
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:28 node-1 haproxy[10501]: proxy mysqld has no server available!
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:28 node-1 haproxy[10501]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:29 node-1 haproxy[10501]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:29 node-1 haproxy[10501]: proxy object-storage has no server available!
<129>Oct 30 04:13:29 node-1 haproxy[10501]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:29 node-1 haproxy[10501]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:29 node-1 haproxy[10501]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:29 node-1 haproxy[10501]: proxy aodh has no server available!
<129>Oct 30 04:13:29 node-1 haproxy[10501]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:29 node-1 haproxy[10501]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:29 node-1 haproxy[10501]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:29 node-1 haproxy[10501]: proxy ceilometer has no server available!
<129>Oct 30 04:13:29 node-1 haproxy[10501]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:29 node-1 haproxy[10501]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:29 node-1 haproxy[10501]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:29 node-1 haproxy[10501]: proxy nova-novncproxy has no server available!
<27>Oct 30 04:13:30 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 30 04:13:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:31 node-1 multipathd: uevent trigger error
<129>Oct 30 04:13:33 node-1 haproxy[12263]: Server horizon/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:33 node-1 haproxy[12263]: Server keystone-1/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:33 node-1 haproxy[12263]: Server keystone-1/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:33 node-1 haproxy[12263]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:33 node-1 haproxy[12263]: proxy keystone-1 has no server available!
<129>Oct 30 04:13:33 node-1 haproxy[12263]: Server keystone-2/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:33 node-1 haproxy[12263]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:33 node-1 haproxy[12263]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:33 node-1 haproxy[12263]: proxy keystone-2 has no server available!
<129>Oct 30 04:13:33 node-1 haproxy[12263]: Server nova-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:33 node-1 haproxy[12263]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:33 node-1 haproxy[12263]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:33 node-1 haproxy[12263]: proxy nova-api has no server available!
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:34 node-1 haproxy[12269]: proxy nova-metadata-api has no server available!
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server cinder-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:34 node-1 haproxy[12269]: proxy cinder-api has no server available!
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server glance-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:34 node-1 haproxy[12269]: proxy glance-api has no server available!
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server glance-glare/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:34 node-1 haproxy[12269]: proxy glance-glare has no server available!
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server neutron/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:34 node-1 haproxy[12269]: proxy neutron has no server available!
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server glance-registry/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:34 node-1 haproxy[12269]: proxy glance-registry has no server available!
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server mysqld/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:34 node-1 haproxy[12269]: proxy mysqld has no server available!
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server object-storage/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:34 node-1 haproxy[12269]: proxy object-storage has no server available!
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server aodh/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:34 node-1 haproxy[12269]: proxy aodh has no server available!
<129>Oct 30 04:13:34 node-1 haproxy[12269]: Server ceilometer/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:35 node-1 haproxy[12269]: proxy ceilometer has no server available!
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server heat-api/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:35 node-1 haproxy[12269]: proxy heat-api has no server available!
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:35 node-1 haproxy[12269]: proxy heat-api-cfn has no server available!
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:35 node-1 haproxy[12269]: proxy heat-api-cloudwatch has no server available!
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 30 04:13:35 node-1 haproxy[12269]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 30 04:13:35 node-1 haproxy[12269]: proxy nova-novncproxy has no server available!
<27>Oct 30 04:13:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:13:47 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 30 04:14:11 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Oct 30 04:14:13 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 30 04:15:09 node-1 multipathd: uevent trigger error
<27>Oct 30 04:15:09 node-1 multipathd: uevent trigger error
<27>Oct 30 04:15:09 node-1 multipathd: uevent trigger error
<27>Oct 30 04:15:09 node-1 multipathd: uevent trigger error
<27>Oct 30 04:16:47 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 04:17:23 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:23 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:23 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:23 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:23 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:28 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:29 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:29 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:29 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:29 node-1 multipathd: uevent trigger error
<43>Oct 30 04:17:40 node-1 apache2_error [Sun Oct 30 04:17:39.479827 2016] [mpm_event:notice] [pid 22588:tid 139638954903424] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 30 04:17:40 node-1 apache2_error [Sun Oct 30 04:17:39.479971 2016] [core:notice] [pid 22588:tid 139638954903424] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 04:17:48 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:48 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:48 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:48 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:48 node-1 multipathd: uevent trigger error
<43>Oct 30 04:17:50 node-1 apache2_error [Sun Oct 30 04:17:42.462973 2016] [mpm_event:notice] [pid 22588:tid 139638954903424] AH00491: caught SIGTERM, shutting down
<43>Oct 30 04:17:50 node-1 apache2_error [Sun Oct 30 04:17:43.549125 2016] [mpm_worker:notice] [pid 23628:tid 139676630378368] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 30 04:17:50 node-1 apache2_error [Sun Oct 30 04:17:43.549155 2016] [core:notice] [pid 23628:tid 139676630378368] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 04:17:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:56 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:56 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:56 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:56 node-1 multipathd: uevent trigger error
<27>Oct 30 04:17:56 node-1 multipathd: uevent trigger error
<43>Oct 30 04:19:00 node-1 apache2_error [Sun Oct 30 04:18:57.704595 2016] [mpm_worker:notice] [pid 23628:tid 139676630378368] AH00295: caught SIGTERM, shutting down
<43>Oct 30 04:19:00 node-1 apache2_error [Sun Oct 30 04:18:58.444320 2016] [mpm_worker:notice] [pid 5175:tid 140581080225664] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 04:19:00 node-1 apache2_error [Sun Oct 30 04:18:58.444354 2016] [core:notice] [pid 5175:tid 140581080225664] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 04:19:48 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 30 04:19:50 node-1 apache2_error [Sun Oct 30 04:19:42.309755 2016] [mpm_worker:notice] [pid 5175:tid 140581080225664] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 04:19:50 node-1 apache2_error [Sun Oct 30 04:19:42.504878 2016] [mpm_worker:warn] [pid 5175:tid 140581080225664] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 04:19:50 node-1 apache2_error [Sun Oct 30 04:19:42.507746 2016] [mpm_worker:notice] [pid 5175:tid 140581080225664] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 04:19:50 node-1 apache2_error [Sun Oct 30 04:19:42.507760 2016] [core:notice] [pid 5175:tid 140581080225664] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 04:20:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:27 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:27 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:20:47 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:06 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:06 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:06 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:06 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:06 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:10 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:10 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:10 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:10 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:10 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:21:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:22:13 node-1 multipathd: uevent trigger error
<27>Oct 30 04:22:13 node-1 multipathd: uevent trigger error
<27>Oct 30 04:22:13 node-1 multipathd: uevent trigger error
<27>Oct 30 04:22:13 node-1 multipathd: uevent trigger error
<27>Oct 30 04:22:13 node-1 multipathd: uevent trigger error
<27>Oct 30 04:22:49 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 04:23:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:23:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:23:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:23:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:23:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:23:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:15 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:44 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:44 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:44 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:44 node-1 multipathd: uevent trigger error
<27>Oct 30 04:24:44 node-1 multipathd: uevent trigger error
<27>Oct 30 04:26:04 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 04:27:04 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:04 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:04 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:04 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:04 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:04 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:20 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:27:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:28:35 node-1 multipathd: uevent trigger error
<27>Oct 30 04:28:35 node-1 multipathd: uevent trigger error
<27>Oct 30 04:28:35 node-1 multipathd: uevent trigger error
<27>Oct 30 04:28:35 node-1 multipathd: uevent trigger error
<27>Oct 30 04:28:35 node-1 multipathd: uevent trigger error
<27>Oct 30 04:29:06 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 04:29:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:29:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:29:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:29:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:29:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:29:34 node-1 multipathd: uevent trigger error
<27>Oct 30 04:29:34 node-1 multipathd: uevent trigger error
<27>Oct 30 04:29:34 node-1 multipathd: uevent trigger error
<27>Oct 30 04:29:34 node-1 multipathd: uevent trigger error
<27>Oct 30 04:31:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:31:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:31:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:31:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:31:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:31:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:32:07 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 04:32:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:32:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:32:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:32:25 node-1 multipathd: uevent trigger error
<27>Oct 30 04:32:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:32:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:32:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:32:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:32:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:21 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:21 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:21 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:21 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:30 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:41 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:41 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:41 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:41 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:41 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:48 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:48 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:48 node-1 multipathd: uevent trigger error
<27>Oct 30 04:33:48 node-1 multipathd: uevent trigger error
<27>Oct 30 04:34:21 node-1 multipathd: uevent trigger error
<27>Oct 30 04:34:21 node-1 multipathd: uevent trigger error
<27>Oct 30 04:34:21 node-1 multipathd: uevent trigger error
<27>Oct 30 04:34:21 node-1 multipathd: uevent trigger error
<27>Oct 30 04:35:09 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 04:35:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:35:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:35:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:35:24 node-1 multipathd: uevent trigger error
<27>Oct 30 04:35:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:35:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:35:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:35:40 node-1 multipathd: uevent trigger error
<27>Oct 30 04:35:40 node-1 multipathd: uevent trigger error
<11>Oct 30 04:35:53 node-1 liberasurecode[6916]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:53 node-1 liberasurecode[6916]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:53 node-1 liberasurecode[6916]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:53 node-1 liberasurecode[6916]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:53 node-1 liberasurecode[6946]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:53 node-1 liberasurecode[6946]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:53 node-1 liberasurecode[6946]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:53 node-1 liberasurecode[6946]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:55 node-1 liberasurecode[7358]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:55 node-1 liberasurecode[7358]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:55 node-1 liberasurecode[7358]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:55 node-1 liberasurecode[7358]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:59 node-1 liberasurecode[7894]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:59 node-1 liberasurecode[7894]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:59 node-1 liberasurecode[7894]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:59 node-1 liberasurecode[7894]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:59 node-1 liberasurecode[7935]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:59 node-1 liberasurecode[7935]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:59 node-1 liberasurecode[7935]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:35:59 node-1 liberasurecode[7935]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[7979]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[7979]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[7979]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[7979]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8061]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8061]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8061]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8061]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8077]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8077]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8077]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8077]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8092]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8092]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8092]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8092]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8108]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8108]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8108]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:00 node-1 liberasurecode[8108]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:09 node-1 liberasurecode[9875]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:09 node-1 liberasurecode[9875]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:09 node-1 liberasurecode[9875]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:36:09 node-1 liberasurecode[9875]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 30 04:36:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:36:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:36:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:36:18 node-1 multipathd: uevent trigger error
<27>Oct 30 04:36:18 node-1 multipathd: uevent trigger error
<43>Oct 30 04:37:12 node-1 apache2_error [Sun Oct 30 04:37:04.783783 2016] [mpm_worker:notice] [pid 5175:tid 140581080225664] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 04:37:12 node-1 apache2_error [Sun Oct 30 04:37:05.167380 2016] [mpm_worker:warn] [pid 5175:tid 140581080225664] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 04:37:12 node-1 apache2_error [Sun Oct 30 04:37:05.173362 2016] [mpm_worker:notice] [pid 5175:tid 140581080225664] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 04:37:12 node-1 apache2_error [Sun Oct 30 04:37:05.173400 2016] [core:notice] [pid 5175:tid 140581080225664] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 30 04:37:42 node-1 apache2_error [Sun Oct 30 04:37:42.142606 2016] [mpm_worker:notice] [pid 5175:tid 140581080225664] AH00297: SIGUSR1 received.  Doing graceful restart
<27>Oct 30 04:37:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:37:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:37:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:37:46 node-1 multipathd: uevent trigger error
<43>Oct 30 04:37:52 node-1 apache2_error [Sun Oct 30 04:37:42.338673 2016] [mpm_worker:warn] [pid 5175:tid 140581080225664] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 04:37:52 node-1 apache2_error [Sun Oct 30 04:37:42.343145 2016] [mpm_worker:notice] [pid 5175:tid 140581080225664] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 04:37:52 node-1 apache2_error [Sun Oct 30 04:37:42.343165 2016] [core:notice] [pid 5175:tid 140581080225664] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 04:37:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:37:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:37:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:37:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:10 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 30 04:38:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:31 node-1 multipathd: uevent trigger error
<43>Oct 30 04:38:32 node-1 apache2_error [Sun Oct 30 04:38:27.641777 2016] [mpm_worker:notice] [pid 5175:tid 140581080225664] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 30 04:38:32 node-1 apache2_error [Sun Oct 30 04:38:27.836529 2016] [mpm_worker:warn] [pid 5175:tid 140581080225664] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 30 04:38:32 node-1 apache2_error [Sun Oct 30 04:38:27.841505 2016] [mpm_worker:notice] [pid 5175:tid 140581080225664] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 30 04:38:32 node-1 apache2_error [Sun Oct 30 04:38:27.841527 2016] [core:notice] [pid 5175:tid 140581080225664] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 30 04:38:38 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:38 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:38 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:38 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:38 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:38 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:43 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:43 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:43 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:43 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:43 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:38:53 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:06 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:06 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:06 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:06 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:26 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:33 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 30 04:39:42 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:42 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:42 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:42 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:42 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:52 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:52 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:52 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:52 node-1 multipathd: uevent trigger error
<27>Oct 30 04:39:52 node-1 multipathd: uevent trigger error
<11>Oct 30 04:40:02 node-1 liberasurecode[27153]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:40:02 node-1 liberasurecode[27153]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:40:02 node-1 liberasurecode[27153]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 30 04:40:02 node-1 liberasurecode[27153]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 30 04:40:05 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:05 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:05 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:05 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:05 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:32 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:50 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:50 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:50 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:50 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:50 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:55 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:55 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:55 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:55 node-1 multipathd: uevent trigger error
<27>Oct 30 04:40:55 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:08 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:08 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:08 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:08 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:22 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:27 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:27 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:27 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:27 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:27 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:31 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:36 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:41 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:41 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:41 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:41 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:41 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:46 node-1 multipathd: uevent trigger error
<27>Oct 30 04:41:46 node-1 multipathd: uevent trigger error
