Oct 21 17:59:08 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8386" x-info="http://www.rsyslog.com"] start
Oct 21 17:59:08 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 21 17:59:08 node-1 rsyslogd: rsyslogd's groupid changed to 104
Oct 21 17:59:08 node-1 rsyslogd: rsyslogd's userid changed to 101
Oct 21 17:59:08 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 21 17:59:08 node-1 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 21 17:59:08 node-1 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 21 17:59:08 node-1 kernel: [    0.000000] Linux version 3.13.0-98-generic (buildd@lgw01-45) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #145-Ubuntu SMP Sat Oct 8 20:13:07 UTC 2016 (Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39)
Oct 21 17:59:08 node-1 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-98-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=58f22ea5-f075-45e2-83c3-8e266ac595a2 nomdmonddf nomdmonisw
Oct 21 17:59:08 node-1 kernel: [    0.000000] KERNEL supported cpus:
Oct 21 17:59:08 node-1 kernel: [    0.000000]   Intel GenuineIntel
Oct 21 17:59:08 node-1 kernel: [    0.000000]   AMD AuthenticAMD
Oct 21 17:59:08 node-1 kernel: [    0.000000]   Centaur CentaurHauls
Oct 21 17:59:08 node-1 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 21 17:59:08 node-1 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 21 17:59:08 node-1 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 21 17:59:08 node-1 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 21 17:59:08 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 21 17:59:08 node-1 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 21 17:59:08 node-1 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 21 17:59:08 node-1 kernel: [    0.000000] No AGP bridge found
Oct 21 17:59:08 node-1 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 21 17:59:08 node-1 kernel: [    0.000000] MTRR default type: write-back
Oct 21 17:59:08 node-1 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 21 17:59:08 node-1 kernel: [    0.000000]   00000-9FFFF write-back
Oct 21 17:59:08 node-1 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 21 17:59:08 node-1 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 21 17:59:08 node-1 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 21 17:59:08 node-1 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 21 17:59:08 node-1 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 21 17:59:08 node-1 kernel: [    0.000000]   2 disabled
Oct 21 17:59:08 node-1 kernel: [    0.000000]   3 disabled
Oct 21 17:59:08 node-1 kernel: [    0.000000]   4 disabled
Oct 21 17:59:08 node-1 kernel: [    0.000000]   5 disabled
Oct 21 17:59:08 node-1 kernel: [    0.000000]   6 disabled
Oct 21 17:59:08 node-1 kernel: [    0.000000]   7 disabled
Oct 21 17:59:08 node-1 kernel: [    0.000000]   8 disabled
Oct 21 17:59:08 node-1 kernel: [    0.000000]   9 disabled
Oct 21 17:59:08 node-1 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 21 17:59:08 node-1 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 21 17:59:08 node-1 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 21 17:59:08 node-1 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 21 17:59:08 node-1 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 21 17:59:08 node-1 kernel: [    0.000000] Using GB pages for direct mapping
Oct 21 17:59:08 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 21 17:59:08 node-1 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 21 17:59:08 node-1 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 21 17:59:08 node-1 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 21 17:59:08 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 21 17:59:08 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 21 17:59:08 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 21 17:59:08 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 21 17:59:08 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 21 17:59:08 node-1 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 21 17:59:08 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 21 17:59:08 node-1 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 21 17:59:08 node-1 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 21 17:59:08 node-1 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 21 17:59:08 node-1 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 21 17:59:08 node-1 kernel: [    0.000000] Zone ranges:
Oct 21 17:59:08 node-1 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] Movable zone start for each node
Oct 21 17:59:08 node-1 kernel: [    0.000000] Early memory node ranges
Oct 21 17:59:08 node-1 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 21 17:59:08 node-1 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 21 17:59:08 node-1 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 21 17:59:08 node-1 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 21 17:59:08 node-1 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 21 17:59:08 node-1 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 21 17:59:08 node-1 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 21 17:59:08 node-1 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 21 17:59:08 node-1 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 21 17:59:08 node-1 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 21 17:59:08 node-1 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 21 17:59:08 node-1 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 21 17:59:08 node-1 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 21 17:59:08 node-1 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 21 17:59:08 node-1 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 21 17:59:08 node-1 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 21 17:59:08 node-1 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 21 17:59:08 node-1 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 21 17:59:08 node-1 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 21 17:59:08 node-1 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 21 17:59:08 node-1 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 21 17:59:08 node-1 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 21 17:59:08 node-1 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 21 17:59:08 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 21 17:59:08 node-1 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 21 17:59:08 node-1 kernel: [    0.000000] Policy zone: Normal
Oct 21 17:59:08 node-1 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-98-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=58f22ea5-f075-45e2-83c3-8e266ac595a2 nomdmonddf nomdmonisw
Oct 21 17:59:08 node-1 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 21 17:59:08 node-1 kernel: [    0.000000] Checking aperture...
Oct 21 17:59:08 node-1 kernel: [    0.000000] No AGP bridge found
Oct 21 17:59:08 node-1 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 21 17:59:08 node-1 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 21 17:59:08 node-1 kernel: [    0.000000] Memory: 32653316K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627180K reserved)
Oct 21 17:59:08 node-1 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 21 17:59:08 node-1 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 21 17:59:08 node-1 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 21 17:59:08 node-1 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 21 17:59:08 node-1 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 21 17:59:08 node-1 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 21 17:59:08 node-1 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 21 17:59:08 node-1 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 21 17:59:08 node-1 kernel: [    0.000000] console [tty0] enabled
Oct 21 17:59:08 node-1 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 21 17:59:08 node-1 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 21 17:59:08 node-1 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 21 17:59:08 node-1 kernel: [    0.000000] hpet clockevent registered
Oct 21 17:59:08 node-1 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 21 17:59:08 node-1 kernel: [    0.004000] tsc: Detected 3492.155 MHz processor
Oct 21 17:59:08 node-1 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.31 BogoMIPS (lpj=13968620)
Oct 21 17:59:08 node-1 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Oct 21 17:59:08 node-1 kernel: [    0.000051] Security Framework initialized
Oct 21 17:59:08 node-1 kernel: [    0.000068] AppArmor: AppArmor initialized
Oct 21 17:59:08 node-1 kernel: [    0.000070] Yama: becoming mindful.
Oct 21 17:59:08 node-1 kernel: [    0.001472] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.006346] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.008275] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.008303] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.008596] Initializing cgroup subsys memory
Oct 21 17:59:08 node-1 kernel: [    0.008604] Initializing cgroup subsys devices
Oct 21 17:59:08 node-1 kernel: [    0.008606] Initializing cgroup subsys freezer
Oct 21 17:59:08 node-1 kernel: [    0.008607] Initializing cgroup subsys blkio
Oct 21 17:59:08 node-1 kernel: [    0.008609] Initializing cgroup subsys perf_event
Oct 21 17:59:08 node-1 kernel: [    0.008611] Initializing cgroup subsys hugetlb
Oct 21 17:59:08 node-1 kernel: [    0.008631] CPU: Physical Processor ID: 0
Oct 21 17:59:08 node-1 kernel: [    0.008632] CPU: Processor Core ID: 0
Oct 21 17:59:08 node-1 kernel: [    0.008636] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 21 17:59:08 node-1 kernel: [    0.008636] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 21 17:59:08 node-1 kernel: [    0.009330] mce: CPU supports 22 MCE banks
Oct 21 17:59:08 node-1 kernel: [    0.009357] CPU0: Thermal monitoring enabled (TM1)
Oct 21 17:59:08 node-1 kernel: [    0.009378] process: using mwait in idle threads
Oct 21 17:59:08 node-1 kernel: [    0.009381] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 21 17:59:08 node-1 kernel: [    0.009381] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 21 17:59:08 node-1 kernel: [    0.009381] tlb_flushall_shift: 6
Oct 21 17:59:08 node-1 kernel: [    0.009469] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 21 17:59:08 node-1 kernel: [    0.010188] ACPI: Core revision 20131115
Oct 21 17:59:08 node-1 kernel: [    0.023009] ACPI: All ACPI Tables successfully acquired
Oct 21 17:59:08 node-1 kernel: [    0.023168] ftrace: allocating 28622 entries in 112 pages
Oct 21 17:59:08 node-1 kernel: [    0.031930] dmar: Host address width 46
Oct 21 17:59:08 node-1 kernel: [    0.031932] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 21 17:59:08 node-1 kernel: [    0.031938] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 21 17:59:08 node-1 kernel: [    0.031940] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 21 17:59:08 node-1 kernel: [    0.031944] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 21 17:59:08 node-1 kernel: [    0.031946] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 21 17:59:08 node-1 kernel: [    0.031947] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 21 17:59:08 node-1 kernel: [    0.031948] dmar: ATSR flags: 0x0
Oct 21 17:59:08 node-1 kernel: [    0.031949] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 21 17:59:08 node-1 kernel: [    0.031950] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 21 17:59:08 node-1 kernel: [    0.032066] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 21 17:59:08 node-1 kernel: [    0.032067] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 21 17:59:08 node-1 kernel: [    0.032068] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 21 17:59:08 node-1 kernel: [    0.032069] HPET id 0 under DRHD base 0xc7ffc000
Oct 21 17:59:08 node-1 kernel: [    0.032070] Your BIOS is broken and requested that x2apic be disabled.
Oct 21 17:59:08 node-1 kernel: [    0.032070] This will slightly decrease performance.
Oct 21 17:59:08 node-1 kernel: [    0.032070] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 21 17:59:08 node-1 kernel: [    0.032502] Enabled IRQ remapping in xapic mode
Oct 21 17:59:08 node-1 kernel: [    0.032503] x2apic not enabled, IRQ remapping is in xapic mode
Oct 21 17:59:08 node-1 kernel: [    0.032507] Switched APIC routing to physical flat.
Oct 21 17:59:08 node-1 kernel: [    0.033129] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 21 17:59:08 node-1 kernel: [    0.072781] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 21 17:59:08 node-1 kernel: [    0.072787] TSC deadline timer enabled
Oct 21 17:59:08 node-1 kernel: [    0.072795] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 21 17:59:08 node-1 kernel: [    0.072801] ... version:                3
Oct 21 17:59:08 node-1 kernel: [    0.072802] ... bit width:              48
Oct 21 17:59:08 node-1 kernel: [    0.072802] ... generic registers:      4
Oct 21 17:59:08 node-1 kernel: [    0.072803] ... value mask:             0000ffffffffffff
Oct 21 17:59:08 node-1 kernel: [    0.072805] ... max period:             0000ffffffffffff
Oct 21 17:59:08 node-1 kernel: [    0.072805] ... fixed-purpose events:   3
Oct 21 17:59:08 node-1 kernel: [    0.072806] ... event mask:             000000070000000f
Oct 21 17:59:08 node-1 kernel: [    0.074226] x86: Booting SMP configuration:
Oct 21 17:59:08 node-1 kernel: [    0.088433] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 21 17:59:08 node-1 kernel: [    0.074228] .... node  #0, CPUs:        #1  #2  #3
Oct 21 17:59:08 node-1 kernel: [    0.116344] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 21 17:59:08 node-1 kernel: [    0.270518] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 21 17:59:08 node-1 kernel: [    0.326149] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 21 17:59:08 node-1 kernel: [    0.383206] x86: Booted up 2 nodes, 16 CPUs
Oct 21 17:59:08 node-1 kernel: [    0.383210] smpboot: Total of 16 processors activated (111761.00 BogoMIPS)
Oct 21 17:59:08 node-1 kernel: [    0.406820] devtmpfs: initialized
Oct 21 17:59:08 node-1 kernel: [    0.409538] EVM: security.selinux
Oct 21 17:59:08 node-1 kernel: [    0.409540] EVM: security.SMACK64
Oct 21 17:59:08 node-1 kernel: [    0.409541] EVM: security.ima
Oct 21 17:59:08 node-1 kernel: [    0.409542] EVM: security.capability
Oct 21 17:59:08 node-1 kernel: [    0.409592] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.410253] pinctrl core: initialized pinctrl subsystem
Oct 21 17:59:08 node-1 kernel: [    0.410326] regulator-dummy: no parameters
Oct 21 17:59:08 node-1 kernel: [    0.410357] RTC time: 17:58:29, date: 10/21/16
Oct 21 17:59:08 node-1 kernel: [    0.410391] NET: Registered protocol family 16
Oct 21 17:59:08 node-1 kernel: [    0.410474] cpuidle: using governor ladder
Oct 21 17:59:08 node-1 kernel: [    0.410475] cpuidle: using governor menu
Oct 21 17:59:08 node-1 kernel: [    0.410510] ACPI: bus type PCI registered
Oct 21 17:59:08 node-1 kernel: [    0.410511] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 21 17:59:08 node-1 kernel: [    0.410556] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 21 17:59:08 node-1 kernel: [    0.410558] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 21 17:59:08 node-1 kernel: [    0.424304] PCI: Using configuration type 1 for base access
Oct 21 17:59:08 node-1 kernel: [    0.425303] bio: create slab <bio-0> at 0
Oct 21 17:59:08 node-1 kernel: [    0.425578] ACPI: Added _OSI(Module Device)
Oct 21 17:59:08 node-1 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 21 17:59:08 node-1 kernel: [    0.425580] ACPI: Added _OSI(Processor Device)
Oct 21 17:59:08 node-1 kernel: [    0.425581] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 21 17:59:08 node-1 kernel: [    0.425582] ACPI: Added _OSI(Processor Aggregator Device)
Oct 21 17:59:08 node-1 kernel: [    0.438332] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 21 17:59:08 node-1 kernel: [    0.449057] ACPI: Interpreter enabled
Oct 21 17:59:08 node-1 kernel: [    0.449062] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 21 17:59:08 node-1 kernel: [    0.449066] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 21 17:59:08 node-1 kernel: [    0.449069] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 21 17:59:08 node-1 kernel: [    0.449076] ACPI: (supports S0 S4 S5)
Oct 21 17:59:08 node-1 kernel: [    0.449077] ACPI: Using IOAPIC for interrupt routing
Oct 21 17:59:08 node-1 kernel: [    0.449117] HEST: Table parsing has been initialized.
Oct 21 17:59:08 node-1 kernel: [    0.449120] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 21 17:59:08 node-1 kernel: [    0.449676] ACPI: No dock devices found.
Oct 21 17:59:08 node-1 kernel: [    0.461280] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 21 17:59:08 node-1 kernel: [    0.461285] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 21 17:59:08 node-1 kernel: [    0.461288] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 21 17:59:08 node-1 kernel: [    0.461317] PCI host bridge to bus 0000:ff
Oct 21 17:59:08 node-1 kernel: [    0.461319] pci_bus 0000:ff: root bus resource [bus ff]
Oct 21 17:59:08 node-1 kernel: [    0.461327] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461365] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.461396] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461431] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461461] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.461491] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.461522] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461551] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461582] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461614] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461643] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461670] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461698] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461724] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461751] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461778] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461807] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461834] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461861] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.461889] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461915] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.461941] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461967] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.461997] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.462032] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462063] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462093] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462123] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462154] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462185] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462216] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462246] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462277] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462308] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462341] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462374] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462408] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462439] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462466] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462500] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462535] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462575] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462611] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462644] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462678] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462707] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462737] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462768] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462799] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462830] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462862] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462891] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462920] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462950] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.462979] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463011] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463044] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463101] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 21 17:59:08 node-1 kernel: [    0.463104] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 21 17:59:08 node-1 kernel: [    0.463107] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 21 17:59:08 node-1 kernel: [    0.463129] PCI host bridge to bus 0000:7f
Oct 21 17:59:08 node-1 kernel: [    0.463131] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 21 17:59:08 node-1 kernel: [    0.463136] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463164] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.463193] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463223] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463245] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.463270] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.463297] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463323] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463345] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463368] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463390] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463413] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463437] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463459] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463482] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463507] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463529] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463552] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463574] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.463597] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463619] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.463641] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463663] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463689] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 21 17:59:08 node-1 kernel: [    0.463722] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463748] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463774] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463801] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463826] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463853] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463880] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463909] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463934] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463961] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.463989] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464016] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464045] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464070] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464096] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464125] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464150] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464176] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464206] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464235] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464261] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464288] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464314] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464341] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464365] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464392] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464422] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464446] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464468] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464493] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464518] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464546] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.464572] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.465812] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 21 17:59:08 node-1 kernel: [    0.465815] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 21 17:59:08 node-1 kernel: [    0.466938] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 21 17:59:08 node-1 kernel: [    0.467449] PCI host bridge to bus 0000:00
Oct 21 17:59:08 node-1 kernel: [    0.467451] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 21 17:59:08 node-1 kernel: [    0.467453] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 21 17:59:08 node-1 kernel: [    0.467454] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 21 17:59:08 node-1 kernel: [    0.467456] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 21 17:59:08 node-1 kernel: [    0.467457] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 21 17:59:08 node-1 kernel: [    0.467458] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 21 17:59:08 node-1 kernel: [    0.467460] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 21 17:59:08 node-1 kernel: [    0.467465] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 21 17:59:08 node-1 kernel: [    0.467548] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.467578] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.467620] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 21 17:59:08 node-1 kernel: [    0.467638] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.467668] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.467708] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 21 17:59:08 node-1 kernel: [    0.467725] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.467754] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.467797] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 21 17:59:08 node-1 kernel: [    0.467812] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.467883] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.467960] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.468035] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 21 17:59:08 node-1 kernel: [    0.468040] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 21 17:59:08 node-1 kernel: [    0.468124] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 21 17:59:08 node-1 kernel: [    0.468271] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 21 17:59:08 node-1 kernel: [    0.468288] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 21 17:59:08 node-1 kernel: [    0.468366] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.468420] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 21 17:59:08 node-1 kernel: [    0.468441] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.468497] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.468540] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 21 17:59:08 node-1 kernel: [    0.468567] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.468622] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.468665] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 21 17:59:08 node-1 kernel: [    0.468689] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 21 17:59:08 node-1 kernel: [    0.468707] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 21 17:59:08 node-1 kernel: [    0.468784] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.468834] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 21 17:59:08 node-1 kernel: [    0.468860] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 21 17:59:08 node-1 kernel: [    0.469105] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 21 17:59:08 node-1 kernel: [    0.469111] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 21 17:59:08 node-1 kernel: [    0.469117] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.469123] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.469130] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 21 17:59:08 node-1 kernel: [    0.469161] pci 0000:01:00.0: supports D1 D2
Oct 21 17:59:08 node-1 kernel: [    0.479125] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 21 17:59:08 node-1 kernel: [    0.479131] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 21 17:59:08 node-1 kernel: [    0.479135] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 21 17:59:08 node-1 kernel: [    0.479346] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.479380] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 21 17:59:08 node-1 kernel: [    0.487123] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 21 17:59:08 node-1 kernel: [    0.487125] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.487127] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 21 17:59:08 node-1 kernel: [    0.487181] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.487249] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.487326] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.487370] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 21 17:59:08 node-1 kernel: [    0.487374] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.487375] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 21 17:59:08 node-1 kernel: [    0.487427] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.487549] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.487607] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 21 17:59:08 node-1 kernel: [    0.487609] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.487611] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 21 17:59:08 node-1 kernel: [    0.487661] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.487779] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.487818] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.487938] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.487975] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.488096] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.488144] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 21 17:59:08 node-1 kernel: [    0.488264] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 21 17:59:08 node-1 kernel: [    0.488306] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 21 17:59:08 node-1 kernel: [    0.488309] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.488311] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 21 17:59:08 node-1 kernel: [    0.488371] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 21 17:59:08 node-1 kernel: [    0.488434] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.488486] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.488527] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 21 17:59:08 node-1 kernel: [    0.488612] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 21 17:59:08 node-1 kernel: [    0.488717] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 21 17:59:08 node-1 kernel: [    0.488720] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.488722] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 21 17:59:08 node-1 kernel: [    0.488777] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 21 17:59:08 node-1 kernel: [    0.488831] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.488879] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.489090] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 21 17:59:08 node-1 kernel: [    0.489094] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 21 17:59:08 node-1 kernel: [    0.489176] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 21 17:59:08 node-1 kernel: [    0.489233] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.489281] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.489490] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 21 17:59:08 node-1 kernel: [    0.489494] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 21 17:59:08 node-1 kernel: [    0.489554] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 21 17:59:08 node-1 kernel: [    0.489616] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.489668] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 21 17:59:08 node-1 kernel: [    0.489889] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 21 17:59:08 node-1 kernel: [    0.489893] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 21 17:59:08 node-1 kernel: [    0.490067] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 21 17:59:08 node-1 kernel: [    0.490106] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 21 17:59:08 node-1 kernel: [    0.490179] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 21 17:59:08 node-1 kernel: [    0.490198] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 21 17:59:08 node-1 kernel: [    0.490211] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 21 17:59:08 node-1 kernel: [    0.490224] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 21 17:59:08 node-1 kernel: [    0.490274] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 21 17:59:08 node-1 kernel: [    0.495144] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 21 17:59:08 node-1 kernel: [    0.495149] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 21 17:59:08 node-1 kernel: [    0.495181] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 21 17:59:08 node-1 kernel: [    0.495668] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 21 17:59:08 node-1 kernel: [    0.495671] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 21 17:59:08 node-1 kernel: [    0.495796] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 21 17:59:08 node-1 kernel: [    0.495902] PCI host bridge to bus 0000:80
Oct 21 17:59:08 node-1 kernel: [    0.495904] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 21 17:59:08 node-1 kernel: [    0.495905] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 21 17:59:08 node-1 kernel: [    0.495907] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 21 17:59:08 node-1 kernel: [    0.495915] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.495978] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.496045] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 21 17:59:08 node-1 kernel: [    0.496106] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 21 17:59:08 node-1 kernel: [    0.496112] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 21 17:59:08 node-1 kernel: [    0.496185] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 21 17:59:08 node-1 kernel: [    0.496485] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 21 17:59:08 node-1 kernel: [    0.496516] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 21 17:59:08 node-1 kernel: [    0.496546] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 21 17:59:08 node-1 kernel: [    0.496575] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 21 17:59:08 node-1 kernel: [    0.496604] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 21 17:59:08 node-1 kernel: [    0.496634] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 21 17:59:08 node-1 kernel: [    0.496663] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 21 17:59:08 node-1 kernel: [    0.496693] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 21 17:59:08 node-1 kernel: [    0.496778] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 21 17:59:08 node-1 kernel: [    0.496783] ACPI: \_SB_.UNC1: notify handler is installed
Oct 21 17:59:08 node-1 kernel: [    0.496784] ACPI: \_SB_.UNC0: notify handler is installed
Oct 21 17:59:08 node-1 kernel: [    0.496799] ACPI: \_SB_.PCI0: notify handler is installed
Oct 21 17:59:08 node-1 kernel: [    0.496852] ACPI: \_SB_.PCI1: notify handler is installed
Oct 21 17:59:08 node-1 kernel: [    0.496931] Found 4 acpi root devices
Oct 21 17:59:08 node-1 kernel: [    0.497040] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 21 17:59:08 node-1 kernel: [    0.497042] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 21 17:59:08 node-1 kernel: [    0.497044] vgaarb: loaded
Oct 21 17:59:08 node-1 kernel: [    0.497045] vgaarb: bridge control possible 0000:0c:00.0
Oct 21 17:59:08 node-1 kernel: [    0.497166] SCSI subsystem initialized
Oct 21 17:59:08 node-1 kernel: [    0.497230] libata version 3.00 loaded.
Oct 21 17:59:08 node-1 kernel: [    0.497245] ACPI: bus type USB registered
Oct 21 17:59:08 node-1 kernel: [    0.497255] usbcore: registered new interface driver usbfs
Oct 21 17:59:08 node-1 kernel: [    0.497260] usbcore: registered new interface driver hub
Oct 21 17:59:08 node-1 kernel: [    0.497285] usbcore: registered new device driver usb
Oct 21 17:59:08 node-1 kernel: [    0.497455] PCI: Using ACPI for IRQ routing
Oct 21 17:59:08 node-1 kernel: [    0.501038] PCI: pci_cache_line_size set to 64 bytes
Oct 21 17:59:08 node-1 kernel: [    0.501265] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 21 17:59:08 node-1 kernel: [    0.501266] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 21 17:59:08 node-1 kernel: [    0.501266] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 21 17:59:08 node-1 kernel: [    0.501332] NetLabel: Initializing
Oct 21 17:59:08 node-1 kernel: [    0.501333] NetLabel:  domain hash size = 128
Oct 21 17:59:08 node-1 kernel: [    0.501334] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 21 17:59:08 node-1 kernel: [    0.501344] NetLabel:  unlabeled traffic allowed by default
Oct 21 17:59:08 node-1 kernel: [    0.501443] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 21 17:59:08 node-1 kernel: [    0.501447] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 21 17:59:08 node-1 kernel: [    0.503502] Switched to clocksource hpet
Oct 21 17:59:08 node-1 kernel: [    0.507507] AppArmor: AppArmor Filesystem Enabled
Oct 21 17:59:08 node-1 kernel: [    0.507521] pnp: PnP ACPI init
Oct 21 17:59:08 node-1 kernel: [    0.507528] ACPI: bus type PNP registered
Oct 21 17:59:08 node-1 kernel: [    0.507640] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 21 17:59:08 node-1 kernel: [    0.507648] pnp 00:01: [dma 4]
Oct 21 17:59:08 node-1 kernel: [    0.507660] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 21 17:59:08 node-1 kernel: [    0.507687] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 21 17:59:08 node-1 kernel: [    0.507707] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 21 17:59:08 node-1 kernel: [    0.507726] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 21 17:59:08 node-1 kernel: [    0.507759] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 21 17:59:08 node-1 kernel: [    0.507813] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507815] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 21 17:59:08 node-1 kernel: [    0.507817] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507818] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507820] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507824] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507826] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 21 17:59:08 node-1 kernel: [    0.507828] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507829] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507831] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507832] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507834] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507835] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 21 17:59:08 node-1 kernel: [    0.507837] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 21 17:59:08 node-1 kernel: [    0.507921] pnp 00:07: [dma 0 disabled]
Oct 21 17:59:08 node-1 kernel: [    0.507949] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 21 17:59:08 node-1 kernel: [    0.508025] pnp 00:08: [dma 0 disabled]
Oct 21 17:59:08 node-1 kernel: [    0.508058] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 21 17:59:08 node-1 kernel: [    0.508109] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 21 17:59:08 node-1 kernel: [    0.508454] pnp: PnP ACPI: found 10 devices
Oct 21 17:59:08 node-1 kernel: [    0.508456] ACPI: bus type PNP unregistered
Oct 21 17:59:08 node-1 kernel: [    0.514722] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 21 17:59:08 node-1 kernel: [    0.514725] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 21 17:59:08 node-1 kernel: [    0.514728] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 21 17:59:08 node-1 kernel: [    0.514732] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 21 17:59:08 node-1 kernel: [    0.514734] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.514748] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 21 17:59:08 node-1 kernel: [    0.514777] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 21 17:59:08 node-1 kernel: [    0.514792] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 21 17:59:08 node-1 kernel: [    0.514820] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 21 17:59:08 node-1 kernel: [    0.514835] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 21 17:59:08 node-1 kernel: [    0.514866] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 21 17:59:08 node-1 kernel: [    0.514881] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 21 17:59:08 node-1 kernel: [    0.514909] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 21 17:59:08 node-1 kernel: [    0.514911] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.514926] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 21 17:59:08 node-1 kernel: [    0.514955] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 21 17:59:08 node-1 kernel: [    0.514957] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.514971] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 21 17:59:08 node-1 kernel: [    0.515000] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 21 17:59:08 node-1 kernel: [    0.515002] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.515004] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 21 17:59:08 node-1 kernel: [    0.515008] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 21 17:59:08 node-1 kernel: [    0.515010] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.515013] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 21 17:59:08 node-1 kernel: [    0.515016] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 21 17:59:08 node-1 kernel: [    0.515021] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 21 17:59:08 node-1 kernel: [    0.515029] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 21 17:59:08 node-1 kernel: [    0.515032] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 21 17:59:08 node-1 kernel: [    0.515039] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 21 17:59:08 node-1 kernel: [    0.515040] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 21 17:59:08 node-1 kernel: [    0.515040] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 21 17:59:08 node-1 kernel: [    0.515041] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 21 17:59:08 node-1 kernel: [    0.515042] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 21 17:59:08 node-1 kernel: [    0.515043] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 21 17:59:08 node-1 kernel: [    0.515044] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 21 17:59:08 node-1 kernel: [    0.515045] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 21 17:59:08 node-1 kernel: [    0.515046] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.515047] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 21 17:59:08 node-1 kernel: [    0.515047] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.515048] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 21 17:59:08 node-1 kernel: [    0.515049] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.515050] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 21 17:59:08 node-1 kernel: [    0.515051] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.515052] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 21 17:59:08 node-1 kernel: [    0.515053] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 21 17:59:08 node-1 kernel: [    0.515054] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 21 17:59:08 node-1 kernel: [    0.515055] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 21 17:59:08 node-1 kernel: [    0.515056] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 21 17:59:08 node-1 kernel: [    0.515057] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 21 17:59:08 node-1 kernel: [    0.515058] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 21 17:59:08 node-1 kernel: [    0.515060] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 21 17:59:08 node-1 kernel: [    0.515061] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 21 17:59:08 node-1 kernel: [    0.515101] NET: Registered protocol family 2
Oct 21 17:59:08 node-1 kernel: [    0.515364] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.515699] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.515846] TCP: Hash tables configured (established 262144 bind 65536)
Oct 21 17:59:08 node-1 kernel: [    0.515881] TCP: reno registered
Oct 21 17:59:08 node-1 kernel: [    0.515910] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.516007] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.516157] NET: Registered protocol family 1
Oct 21 17:59:08 node-1 kernel: [    0.555600] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 21 17:59:08 node-1 kernel: [    0.555614] PCI: CLS 64 bytes, default 64
Oct 21 17:59:08 node-1 kernel: [    0.555692] Trying to unpack rootfs image as initramfs...
Oct 21 17:59:08 node-1 kernel: [    0.775313] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Oct 21 17:59:08 node-1 kernel: [    0.775359] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 21 17:59:08 node-1 kernel: [    0.775361] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 21 17:59:08 node-1 kernel: [    0.775776] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775782] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775786] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775792] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775804] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775820] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775835] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775850] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775861] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775872] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775878] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775884] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775893] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775906] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775918] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.775931] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 21 17:59:08 node-1 kernel: [    0.776034] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 21 17:59:08 node-1 kernel: [    0.776040] Scanning for low memory corruption every 60 seconds
Oct 21 17:59:08 node-1 kernel: [    0.776478] Initialise system trusted keyring
Oct 21 17:59:08 node-1 kernel: [    0.776531] audit: initializing netlink socket (disabled)
Oct 21 17:59:08 node-1 kernel: [    0.776546] type=2000 audit(1477072708.732:1): initialized
Oct 21 17:59:08 node-1 kernel: [    0.794314] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 21 17:59:08 node-1 kernel: [    0.795839] zbud: loaded
Oct 21 17:59:08 node-1 kernel: [    0.795965] VFS: Disk quotas dquot_6.5.2
Oct 21 17:59:08 node-1 kernel: [    0.796004] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 21 17:59:08 node-1 kernel: [    0.796383] fuse init (API version 7.22)
Oct 21 17:59:08 node-1 kernel: [    0.796446] msgmni has been set to 32768
Oct 21 17:59:08 node-1 kernel: [    0.796497] Key type big_key registered
Oct 21 17:59:08 node-1 kernel: [    0.797060] Key type asymmetric registered
Oct 21 17:59:08 node-1 kernel: [    0.797062] Asymmetric key parser 'x509' registered
Oct 21 17:59:08 node-1 kernel: [    0.797084] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 21 17:59:08 node-1 kernel: [    0.797157] io scheduler noop registered
Oct 21 17:59:08 node-1 kernel: [    0.797159] io scheduler deadline registered (default)
Oct 21 17:59:08 node-1 kernel: [    0.797180] io scheduler cfq registered
Oct 21 17:59:08 node-1 kernel: [    0.797583] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    0.797710] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    0.797826] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    0.797938] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    0.798052] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    0.798150] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    0.798564] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 21 17:59:08 node-1 kernel: [    0.798603] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 21 17:59:08 node-1 kernel: [    0.798630] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 21 17:59:08 node-1 kernel: [    0.798649] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798654] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798660] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 21 17:59:08 node-1 kernel: [    0.798681] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798682] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798683] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798685] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798686] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798687] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798689] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798690] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798692] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798693] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798694] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798696] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798698] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 21 17:59:08 node-1 kernel: [    0.798704] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798706] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 21 17:59:08 node-1 kernel: [    0.798721] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798725] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 21 17:59:08 node-1 kernel: [    0.798735] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798737] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 21 17:59:08 node-1 kernel: [    0.798740] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 21 17:59:08 node-1 kernel: [    0.798779] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 21 17:59:08 node-1 kernel: [    0.798785] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 21 17:59:08 node-1 kernel: [    0.798789] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 21 17:59:08 node-1 kernel: [    0.798799] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 21 17:59:08 node-1 kernel: [    0.798839] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 21 17:59:08 node-1 kernel: [    0.798841] vesafb: scrolling: redraw
Oct 21 17:59:08 node-1 kernel: [    0.798842] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 21 17:59:08 node-1 kernel: [    0.819499] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 21 17:59:08 node-1 kernel: [    0.827999] Console: switching to colour frame buffer device 80x30
Oct 21 17:59:08 node-1 kernel: [    0.836664] fb0: VESA VGA frame buffer device
Oct 21 17:59:08 node-1 kernel: [    0.836860] intel_idle: MWAIT substates: 0x2120
Oct 21 17:59:08 node-1 kernel: [    0.836861] intel_idle: v0.4 model 0x3F
Oct 21 17:59:08 node-1 kernel: [    0.836862] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 21 17:59:08 node-1 kernel: [    0.837103] ipmi message handler version 39.2
Oct 21 17:59:08 node-1 kernel: [    0.837377] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 21 17:59:08 node-1 kernel: [    0.837810] ACPI: AC Adapter [P111] (on-line)
Oct 21 17:59:08 node-1 kernel: [    0.843043] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 21 17:59:08 node-1 kernel: [    0.854069] ACPI: Power Button [PWRB]
Oct 21 17:59:08 node-1 kernel: [    0.859834] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 21 17:59:08 node-1 kernel: [    0.871458] ACPI: Power Button [PWRF]
Oct 21 17:59:08 node-1 kernel: [    0.897033] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 21 17:59:08 node-1 kernel: [    0.908708] pstore: Registered erst as persistent store backend
Oct 21 17:59:08 node-1 kernel: [    0.914901] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 21 17:59:08 node-1 kernel: [    0.926843] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 21 17:59:08 node-1 kernel: [    0.953601] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 21 17:59:08 node-1 kernel: [    0.986875] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 21 17:59:08 node-1 kernel: [    1.000902] Linux agpgart interface v0.103
Oct 21 17:59:08 node-1 kernel: [    1.008533] brd: module loaded
Oct 21 17:59:08 node-1 kernel: [    1.015574] loop: module loaded
Oct 21 17:59:08 node-1 kernel: [    1.022292] libphy: Fixed MDIO Bus: probed
Oct 21 17:59:08 node-1 kernel: [    1.028765] tun: Universal TUN/TAP device driver, 1.6
Oct 21 17:59:08 node-1 kernel: [    1.035233] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 21 17:59:08 node-1 kernel: [    1.041754] PPP generic driver version 2.4.2
Oct 21 17:59:08 node-1 kernel: [    1.048143] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 21 17:59:08 node-1 kernel: [    1.054597] ehci-pci: EHCI PCI platform driver
Oct 21 17:59:08 node-1 kernel: [    1.061151] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 21 17:59:08 node-1 kernel: [    1.067553] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 21 17:59:08 node-1 kernel: [    1.080110] ehci-pci 0000:00:1a.0: debug port 2
Oct 21 17:59:08 node-1 kernel: [    1.090311] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 21 17:59:08 node-1 kernel: [    1.090329] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 21 17:59:08 node-1 kernel: [    1.106996] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 21 17:59:08 node-1 kernel: [    1.113071] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 21 17:59:08 node-1 kernel: [    1.119235] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 21 17:59:08 node-1 kernel: [    1.131112] usb usb1: Product: EHCI Host Controller
Oct 21 17:59:08 node-1 kernel: [    1.137129] usb usb1: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 21 17:59:08 node-1 kernel: [    1.143166] usb usb1: SerialNumber: 0000:00:1a.0
Oct 21 17:59:08 node-1 kernel: [    1.149251] hub 1-0:1.0: USB hub found
Oct 21 17:59:08 node-1 kernel: [    1.155073] hub 1-0:1.0: 2 ports detected
Oct 21 17:59:08 node-1 kernel: [    1.160924] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 21 17:59:08 node-1 kernel: [    1.166603] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 21 17:59:08 node-1 kernel: [    1.177629] ehci-pci 0000:00:1d.0: debug port 2
Oct 21 17:59:08 node-1 kernel: [    1.186995] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 21 17:59:08 node-1 kernel: [    1.186998] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 21 17:59:08 node-1 kernel: [    1.202914] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 21 17:59:08 node-1 kernel: [    1.208178] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 21 17:59:08 node-1 kernel: [    1.213548] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 21 17:59:08 node-1 kernel: [    1.224273] usb usb2: Product: EHCI Host Controller
Oct 21 17:59:08 node-1 kernel: [    1.229759] usb usb2: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 21 17:59:08 node-1 kernel: [    1.235306] usb usb2: SerialNumber: 0000:00:1d.0
Oct 21 17:59:08 node-1 kernel: [    1.240822] hub 2-0:1.0: USB hub found
Oct 21 17:59:08 node-1 kernel: [    1.246175] hub 2-0:1.0: 2 ports detected
Oct 21 17:59:08 node-1 kernel: [    1.251476] ehci-platform: EHCI generic platform driver
Oct 21 17:59:08 node-1 kernel: [    1.256708] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 21 17:59:08 node-1 kernel: [    1.262017] ohci-pci: OHCI PCI platform driver
Oct 21 17:59:08 node-1 kernel: [    1.267322] ohci-platform: OHCI generic platform driver
Oct 21 17:59:08 node-1 kernel: [    1.272537] uhci_hcd: USB Universal Host Controller Interface driver
Oct 21 17:59:08 node-1 kernel: [    1.277908] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 21 17:59:08 node-1 kernel: [    1.470693] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 21 17:59:08 node-1 kernel: [    1.774482] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Oct 21 17:59:08 node-1 kernel: [    1.790736] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 21 17:59:08 node-1 kernel: [    1.796424] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 21 17:59:08 node-1 kernel: [    1.802254] hub 1-1:1.0: USB hub found
Oct 21 17:59:08 node-1 kernel: [    1.807848] hub 1-1:1.0: 6 ports detected
Oct 21 17:59:08 node-1 kernel: [    1.922331] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 21 17:59:08 node-1 kernel: [    2.316765] i8042: No controller found
Oct 21 17:59:08 node-1 kernel: [    2.322313] mousedev: PS/2 mouse device common for all mice
Oct 21 17:59:08 node-1 kernel: [    2.328041] rtc_cmos 00:02: RTC can wake from S4
Oct 21 17:59:08 node-1 kernel: [    2.333765] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 21 17:59:08 node-1 kernel: [    2.334714] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 21 17:59:08 node-1 kernel: [    2.334715] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 21 17:59:08 node-1 kernel: [    2.335356] hub 2-1:1.0: USB hub found
Oct 21 17:59:08 node-1 kernel: [    2.335593] hub 2-1:1.0: 8 ports detected
Oct 21 17:59:08 node-1 kernel: [    2.361874] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 21 17:59:08 node-1 kernel: [    2.373193] device-mapper: uevent: version 1.0.3
Oct 21 17:59:08 node-1 kernel: [    2.378938] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 21 17:59:08 node-1 kernel: [    2.390331] ledtrig-cpu: registered to indicate activity on CPUs
Oct 21 17:59:08 node-1 kernel: [    2.396333] TCP: cubic registered
Oct 21 17:59:08 node-1 kernel: [    2.402198] NET: Registered protocol family 10
Oct 21 17:59:08 node-1 kernel: [    2.408282] NET: Registered protocol family 17
Oct 21 17:59:08 node-1 kernel: [    2.414066] Key type dns_resolver registered
Oct 21 17:59:08 node-1 kernel: [    2.420132] Loading compiled-in X.509 certificates
Oct 21 17:59:08 node-1 kernel: [    2.426367] Loaded X.509 cert 'Magrathea: Glacier signing key: c29c39823a6b07000b1e1e4c1cabc3708bc09796'
Oct 21 17:59:08 node-1 kernel: [    2.438048] registered taskstats version 1
Oct 21 17:59:08 node-1 kernel: [    2.446153] Key type trusted registered
Oct 21 17:59:08 node-1 kernel: [    2.453853] Key type encrypted registered
Oct 21 17:59:08 node-1 kernel: [    2.459395] AppArmor: AppArmor sha1 policy hashing enabled
Oct 21 17:59:08 node-1 kernel: [    2.464961] IMA: No TPM chip found, activating TPM-bypass!
Oct 21 17:59:08 node-1 kernel: [    2.471092] regulator-dummy: disabling
Oct 21 17:59:08 node-1 kernel: [    2.476628]   Magic number: 4:848:997
Oct 21 17:59:08 node-1 kernel: [    2.482376] rtc_cmos 00:02: setting system clock to 2016-10-21 17:58:31 UTC (1477072711)
Oct 21 17:59:08 node-1 kernel: [    2.494931] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 21 17:59:08 node-1 kernel: [    2.500648] EDD information not available.
Oct 21 17:59:08 node-1 kernel: [    2.506351] PM: Hibernation image not present or could not be loaded.
Oct 21 17:59:08 node-1 kernel: [    2.507220] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 21 17:59:08 node-1 kernel: [    2.518809] Write protecting the kernel read-only data: 12288k
Oct 21 17:59:08 node-1 kernel: [    2.525211] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 21 17:59:08 node-1 kernel: [    2.538161] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 21 17:59:08 node-1 kernel: [    2.570575] device-mapper: multipath: version 1.6.0 loaded
Oct 21 17:59:08 node-1 kernel: [    2.578682] systemd-udevd[216]: starting version 204
Oct 21 17:59:08 node-1 kernel: [    2.601048] md: linear personality registered for level -1
Oct 21 17:59:08 node-1 kernel: [    2.613728] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 21 17:59:08 node-1 kernel: [    2.620950] md: multipath personality registered for level -4
Oct 21 17:59:08 node-1 kernel: [    2.629134] md: raid0 personality registered for level 0
Oct 21 17:59:08 node-1 kernel: [    2.637732] md: raid1 personality registered for level 1
Oct 21 17:59:08 node-1 kernel: [    2.646291] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 21 17:59:08 node-1 kernel: [    2.652670] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 21 17:59:08 node-1 kernel: [    2.658975] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 21 17:59:08 node-1 kernel: [    2.660721] megasas: FW now in Ready state
Oct 21 17:59:08 node-1 kernel: [    2.661129] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.661240] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.661388] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.661518] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.661667] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.662075] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.662160] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.662239] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.662373] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.662445] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.662558] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.662649] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.662818] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.662948] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.663048] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.663112] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.663845] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 21 17:59:08 node-1 kernel: [    2.691565] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Oct 21 17:59:08 node-1 kernel: [    2.704804] 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 21 17:59:08 node-1 kernel: [    2.713726] raid6: sse2x1   11265 MB/s
Oct 21 17:59:08 node-1 kernel: [    2.725455] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 21 17:59:08 node-1 kernel: [    2.732421] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.732426] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.732432] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.732437] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.732477] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.750815] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 21 17:59:08 node-1 kernel: [    2.757564] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 21 17:59:08 node-1 kernel: [    2.762265] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Oct 21 17:59:08 node-1 kernel: [    2.762295] 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 21 17:59:08 node-1 kernel: [    2.762321] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 21 17:59:08 node-1 kernel: [    2.762818] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.763012] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.763134] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.763225] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.763320] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.763447] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.763630] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 21 17:59:08 node-1 kernel: [    2.781821] raid6: sse2x2   12863 MB/s
Oct 21 17:59:08 node-1 kernel: [    2.824093] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 21 17:59:08 node-1 kernel: [    2.830614] usb 2-1.4: Manufacturer: Avocent
Oct 21 17:59:08 node-1 kernel: [    2.836995] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 21 17:59:08 node-1 kernel: [    2.849533] raid6: sse2x4    9613 MB/s
Oct 21 17:59:08 node-1 kernel: [    2.921471] raid6: avx2x1   14956 MB/s
Oct 21 17:59:08 node-1 kernel: [    2.993406] raid6: avx2x2   18871 MB/s
Oct 21 17:59:08 node-1 kernel: [    3.065342] raid6: avx2x4   21273 MB/s
Oct 21 17:59:08 node-1 kernel: [    3.071347] raid6: using algorithm avx2x4 (21273 MB/s)
Oct 21 17:59:08 node-1 kernel: [    3.077371] raid6: using avx2x2 recovery algorithm
Oct 21 17:59:08 node-1 kernel: [    3.083259] megasas:IOC Init cmd success
Oct 21 17:59:08 node-1 kernel: [    3.083264] Switched to clocksource tsc
Oct 21 17:59:08 node-1 kernel: [    3.092481] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Oct 21 17:59:08 node-1 kernel: [    3.092482] 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 21 17:59:08 node-1 kernel: [    3.092484] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 21 17:59:08 node-1 kernel: [    3.092561] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    3.092598] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    3.092625] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    3.092654] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    3.092731] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 21 17:59:08 node-1 kernel: [    3.100218] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Oct 21 17:59:08 node-1 kernel: [    3.100220] 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 21 17:59:08 node-1 kernel: [    3.100220] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 21 17:59:08 node-1 kernel: [    3.100292] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    3.100331] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    3.100349] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    3.100388] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 21 17:59:08 node-1 kernel: [    3.100465] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 21 17:59:08 node-1 kernel: [    3.105322] megasas: INIT adapter done
Oct 21 17:59:08 node-1 kernel: [    3.177234] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 21 17:59:08 node-1 kernel: [    3.177565] scsi0 : LSI SAS based MegaRAID driver
Oct 21 17:59:08 node-1 kernel: [    3.184937] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 21 17:59:08 node-1 kernel: [    3.185126] xor: automatically using best checksumming function:
Oct 21 17:59:08 node-1 kernel: [    3.185139] hidraw: raw HID events driver (C) Jiri Kosina
Oct 21 17:59:08 node-1 kernel: [    3.195942] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 21 17:59:08 node-1 kernel: [    3.200087] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 21 17:59:08 node-1 kernel: [    3.200214] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 21 17:59:08 node-1 kernel: [    3.200397] sd 0:2:0:0: [sda] Write Protect is off
Oct 21 17:59:08 node-1 kernel: [    3.200398] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 21 17:59:08 node-1 kernel: [    3.200469] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 21 17:59:08 node-1 kernel: [    3.229172]    avx       : 52273.000 MB/sec
Oct 21 17:59:08 node-1 kernel: [    3.229362]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct 21 17:59:08 node-1 kernel: [    3.230708] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 21 17:59:08 node-1 kernel: [    3.272190] usbcore: registered new interface driver usbhid
Oct 21 17:59:08 node-1 kernel: [    3.272190] usbhid: USB HID core driver
Oct 21 17:59:08 node-1 kernel: [    3.294768] async_tx: api initialized (async)
Oct 21 17:59:08 node-1 kernel: [    3.301142] 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 21 17:59:08 node-1 kernel: [    3.313822] 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 21 17:59:08 node-1 kernel: [    3.326598] 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 21 17:59:08 node-1 kernel: [    3.339346] 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 21 17:59:08 node-1 kernel: [    3.352680] 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 21 17:59:08 node-1 kernel: [    3.366367] 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 21 17:59:08 node-1 kernel: [    3.366390] md: raid6 personality registered for level 6
Oct 21 17:59:08 node-1 kernel: [    3.366390] md: raid5 personality registered for level 5
Oct 21 17:59:08 node-1 kernel: [    3.366390] md: raid4 personality registered for level 4
Oct 21 17:59:08 node-1 kernel: [    3.404027] md: raid10 personality registered for level 10
Oct 21 17:59:08 node-1 kernel: [    3.437686] random: lvm urandom read with 32 bits of entropy available
Oct 21 17:59:08 node-1 kernel: [    3.465328] multipathd (370): /proc/370/oom_adj is deprecated, please use /proc/370/oom_score_adj instead.
Oct 21 17:59:08 node-1 kernel: [    3.584513] bio: create slab <bio-1> at 1
Oct 21 17:59:08 node-1 kernel: [    4.324890] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 21 17:59:08 node-1 kernel: [    5.062332] random: nonblocking pool is initialized
Oct 21 17:59:08 node-1 kernel: [    5.068812] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 21 17:59:08 node-1 kernel: [    5.121109] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 21 17:59:08 node-1 kernel: [    5.288252] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 21 17:59:08 node-1 kernel: [    5.378003] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 21 17:59:08 node-1 kernel: [    5.477654] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 21 17:59:08 node-1 kernel: [    5.714556] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 21 17:59:08 node-1 kernel: [    5.747658] XFS (dm-0): Mounting Filesystem
Oct 21 17:59:08 node-1 kernel: [    6.011791] XFS (dm-0): Ending clean mount
Oct 21 17:59:08 node-1 kernel: [    6.064458] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 21 17:59:08 node-1 kernel: [    6.109123] XFS (dm-1): Mounting Filesystem
Oct 21 17:59:08 node-1 kernel: [    6.264981] XFS (dm-1): Ending clean mount
Oct 21 17:59:08 node-1 kernel: [    7.633262] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 21 17:59:08 node-1 kernel: [    7.658770] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 21 17:59:08 node-1 kernel: [    7.840936] systemd-udevd[774]: starting version 204
Oct 21 17:59:08 node-1 kernel: [    8.024699] power_meter ACPI000D:00: Found ACPI power meter.
Oct 21 17:59:08 node-1 kernel: [    8.024718] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 21 17:59:08 node-1 kernel: [    8.040494] IPMI System Interface driver.
Oct 21 17:59:08 node-1 kernel: [    8.040542] ipmi_si: probing via ACPI
Oct 21 17:59:08 node-1 kernel: [    8.040561] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 21 17:59:08 node-1 kernel: [    8.040563] ipmi_si: Adding ACPI-specified kcs state machine
Oct 21 17:59:08 node-1 kernel: [    8.040573] ipmi_si: probing via SMBIOS
Oct 21 17:59:08 node-1 kernel: [    8.040574] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 21 17:59:08 node-1 kernel: [    8.040575] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 21 17:59:08 node-1 kernel: [    8.040576] ipmi_si: probing via SPMI
Oct 21 17:59:08 node-1 kernel: [    8.040577] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 21 17:59:08 node-1 kernel: [    8.040577] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 21 17:59:08 node-1 kernel: [    8.040579] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 21 17:59:08 node-1 kernel: [    8.074766] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 21 17:59:08 node-1 kernel: [    8.074771] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 21 17:59:08 node-1 kernel: [    8.074774] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 21 17:59:08 node-1 kernel: [    8.074775] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 21 17:59:08 node-1 kernel: [    8.074843] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 21 17:59:08 node-1 kernel: [    8.087591] wmi: Mapper loaded
Oct 21 17:59:08 node-1 kernel: [    8.105818] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 21 17:59:08 node-1 kernel: [    8.175168] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 21 17:59:08 node-1 kernel: [    8.175175] ipmi_si 00:09: IPMI kcs interface initialized
Oct 21 17:59:08 node-1 kernel: [    8.181555] systemd-udevd[792]: renamed network interface eth0 to enp6s0
Oct 21 17:59:08 node-1 kernel: [    8.209434] systemd-udevd[793]: renamed network interface eth1 to enp7s0
Oct 21 17:59:08 node-1 kernel: [    8.229326] systemd-udevd[823]: renamed network interface eth2 to enp8s0
Oct 21 17:59:08 node-1 kernel: [    8.265344] systemd-udevd[802]: renamed network interface eth3 to enp9s0
Oct 21 17:59:08 node-1 kernel: [    8.563077] type=1400 audit(1477072717.581:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1063 comm="apparmor_parser"
Oct 21 17:59:08 node-1 kernel: [    8.563229] type=1400 audit(1477072717.581:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1063 comm="apparmor_parser"
Oct 21 17:59:08 node-1 kernel: [    8.563359] type=1400 audit(1477072717.581:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1063 comm="apparmor_parser"
Oct 21 17:59:08 node-1 kernel: [    8.569381] type=1400 audit(1477072717.589:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1059 comm="apparmor_parser"
Oct 21 17:59:08 node-1 kernel: [    8.569528] type=1400 audit(1477072717.589:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1059 comm="apparmor_parser"
Oct 21 17:59:08 node-1 kernel: [    8.569651] type=1400 audit(1477072717.589:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1059 comm="apparmor_parser"
Oct 21 17:59:08 node-1 kernel: [    8.571975] type=1400 audit(1477072717.589:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Oct 21 17:59:08 node-1 kernel: [    8.572117] type=1400 audit(1477072717.589:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1060 comm="apparmor_parser"
Oct 21 17:59:08 node-1 kernel: [    8.572238] type=1400 audit(1477072717.589:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1060 comm="apparmor_parser"
Oct 21 17:59:08 node-1 kernel: [    8.572684] type=1400 audit(1477072717.593:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Oct 21 17:59:08 node-1 kernel: [    9.104899] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 21 17:59:08 node-1 kernel: [    9.106579] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 21 17:59:08 node-1 kernel: [    9.270932] enic 0000:06:00.0 enp6s0: Link UP
Oct 21 17:59:08 node-1 kernel: [    9.272051] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 21 17:59:08 node-1 kernel: [    9.272061] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 21 17:59:08 node-1 kernel: [   17.810821] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 21 17:59:10 node-1 failsafe: Failsafe of 120 seconds reached.
Oct 21 17:59:10 node-1 kernel: [   41.475320] init: failsafe main process (8413) killed by TERM signal
Oct 21 17:59:10 node-1 dbus[8519]: [system] AppArmor D-Bus mediation is enabled
Oct 21 17:59:10 node-1 kernel: [   41.644587] audit_printk_skb: 30 callbacks suppressed
Oct 21 17:59:10 node-1 kernel: [   41.644601] type=1400 audit(1477072750.223:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8530 comm="apparmor_parser"
Oct 21 17:59:10 node-1 kernel: [   41.645194] type=1400 audit(1477072750.223:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8529 comm="apparmor_parser"
Oct 21 17:59:10 node-1 kernel: [   41.645199] type=1400 audit(1477072750.223:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8529 comm="apparmor_parser"
Oct 21 17:59:10 node-1 kernel: [   41.645202] type=1400 audit(1477072750.223:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8529 comm="apparmor_parser"
Oct 21 17:59:10 node-1 kernel: [   41.645431] type=1400 audit(1477072750.223:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8529 comm="apparmor_parser"
Oct 21 17:59:10 node-1 kernel: [   41.645433] type=1400 audit(1477072750.223:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8529 comm="apparmor_parser"
Oct 21 17:59:10 node-1 kernel: [   41.645549] type=1400 audit(1477072750.223:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8529 comm="apparmor_parser"
Oct 21 17:59:10 node-1 kernel: [   41.714985] type=1400 audit(1477072750.291:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8532 comm="apparmor_parser"
Oct 21 17:59:10 node-1 cron[8570]: (CRON) INFO (pidfile fd = 3)
Oct 21 17:59:10 node-1 anacron[8595]: Anacron 2.3 started on 2016-10-21
Oct 21 17:59:10 node-1 cron[8607]: (CRON) STARTUP (fork ok)
Oct 21 17:59:10 node-1 anacron[8595]: Will run job `cron.daily' in 5 min.
Oct 21 17:59:10 node-1 anacron[8595]: Will run job `cron.weekly' in 10 min.
Oct 21 17:59:10 node-1 anacron[8595]: Will run job `cron.monthly' in 15 min.
Oct 21 17:59:10 node-1 anacron[8595]: Jobs will be executed sequentially
Oct 21 17:59:10 node-1 cron[8607]: (CRON) INFO (Running @reboot jobs)
Oct 21 17:59:10 node-1 multipathd: path checkers start up
Oct 21 17:59:10 node-1 postfix/master[8751]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 21 17:59:14 node-1 puppet-agent[8935]: Reopening log files
Oct 21 17:59:15 node-1 puppet-agent[8935]: Could not request certificate: Connection refused - connect(2)
Oct 21 17:59:25 node-1 puppet-user[9143]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 21 17:59:25 node-1 puppet-user[9143]: Compiled catalog for node-1.domain.tld in environment production in 0.04 seconds
Oct 21 17:59:26 node-1 puppet-user[9143]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 21 17:59:26 node-1 puppet-user[9143]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 21 17:59:26 node-1 puppet-user[9143]: Finished catalog run in 1.02 seconds
Oct 21 17:59:28 node-1 multipathd: uevent trigger error
Oct 21 17:59:28 node-1 puppet-user[9568]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 21 17:59:28 node-1 puppet-user[9568]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 21 17:59:28 node-1 puppet-user[9568]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 21 17:59:28 node-1 puppet-user[9568]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 21 17:59:28 node-1 puppet-user[9568]: (/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 21 17:59:28 node-1 puppet-user[9568]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 21 17:59:28 node-1 puppet-user[9568]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 21 17:59:28 node-1 puppet-user[9568]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 21 17:59:28 node-1 puppet-user[9568]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 21 17:59:28 node-1 puppet-user[9568]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 21 17:59:28 node-1 puppet-user[9568]: Finished catalog run in 0.05 seconds
Oct 21 17:59:29 node-1 puppet-user[10025]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 21 17:59:29 node-1 puppet-user[10025]: Compiled catalog for node-1.domain.tld in environment production in 0.07 seconds
Oct 21 17:59:30 node-1 puppet-user[10025]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 21 17:59:30 node-1 puppet-user[10025]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 21 17:59:30 node-1 puppet-user[10025]: Finished catalog run in 0.02 seconds
Oct 21 17:59:31 node-1 puppet-user[10483]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 21 17:59:31 node-1 puppet-user[10483]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 21 17:59:31 node-1 puppet-user[10483]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 21 17:59:31 node-1 puppet-user[10483]: Finished catalog run in 0.03 seconds
Oct 21 17:59:32 node-1 puppet-user[10946]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 21 17:59:33 node-1 puppet-user[10946]: Compiled catalog for node-1.domain.tld in environment production in 0.17 seconds
Oct 21 17:59:33 node-1 puppet-user[10946]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 21 17:59:33 node-1 puppet-user[10946]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-kvm-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-kvm-0.9/]/returns) executed successfully
Oct 21 17:59:33 node-1 puppet-user[10946]: Finished catalog run in 0.42 seconds
Oct 21 17:59:34 node-1 puppet-user[11600]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 21 17:59:35 node-1 puppet-user[11600]: Compiled catalog for node-1.domain.tld in environment production in 0.20 seconds
Oct 21 17:59:35 node-1 puppet-user[11600]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 21 17:59:35 node-1 puppet-user[11600]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 21 17:59:35 node-1 puppet-user[11600]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-kvm-0.9.0]/Apt::Setting[list-fuel-plugin-kvm-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-kvm-0.9.0.list]/ensure) created
Oct 21 17:59:35 node-1 puppet-user[11600]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 21 17:59:35 node-1 puppet-user[11600]: Finished catalog run in 0.23 seconds
Oct 21 17:59:36 node-1 puppet-user[12078]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 21 17:59:37 node-1 puppet-user[12078]: Compiled catalog for node-1.domain.tld in environment production in 0.15 seconds
Oct 21 17:59:37 node-1 puppet-user[12078]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 21 17:59:37 node-1 kernel: [   68.307682] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 21 17:59:37 node-1 kernel: [   68.307729] 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 21 17:59:37 node-1 puppet-user[12078]: (/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 21 17:59:37 node-1 puppet-user[12078]: Finished catalog run in 0.05 seconds
Oct 21 17:59:39 node-1 puppet-user[12536]: (Scope(Class[main])) MODULAR: sync_time
Oct 21 17:59:39 node-1 puppet-user[12536]: Compiled catalog for node-1.domain.tld in environment production in 0.02 seconds
Oct 21 17:59:39 node-1 ntpdate[12952]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 21 17:59:45 node-1 kernel: [   76.402316] init: plymouth-upstart-bridge main process ended, respawning
Oct 21 17:59:45 node-1 ntpdate[12952]: adjust time server 10.20.0.2 offset 0.001164 sec
Oct 21 17:59:45 node-1 puppet-user[12536]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 21 17:59:45 node-1 puppet-user[12536]: Finished catalog run in 6.16 seconds
Oct 21 17:59:45 node-1 puppet-agent[8935]: Could not run: SIGTERM
Oct 21 17:59:45 node-1 kernel: [   76.703062] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 21 17:59:45 node-1 ec2: 
Oct 21 17:59:45 node-1 ec2: #############################################################
Oct 21 17:59:45 node-1 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 21 17:59:45 node-1 ec2: 1024 37:dd:31:ed:44:8c:c5:e9:9d:0b:a2:69:95:5e:cd:a2  root@node-1.domain.tld (DSA)
Oct 21 17:59:45 node-1 ec2: 256 c3:ce:02:59:37:8d:56:8f:51:5b:04:2d:7c:a6:e4:5b  root@node-1.domain.tld (ECDSA)
Oct 21 17:59:45 node-1 ec2: 256 3c:4d:63:43:4b:98:43:21:01:30:4e:31:56:78:e2:f7  root@node-1.domain.tld (ED25519)
Oct 21 17:59:45 node-1 ec2: 2048 2d:c5:83:08:00:43:18:6b:52:3e:b2:9b:4b:7a:99:42  root@node-1.domain.tld (RSA)
Oct 21 17:59:45 node-1 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 21 17:59:45 node-1 ec2: #############################################################
Oct 21 17:59:50 node-1 puppet-user[13320]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 21 17:59:51 node-1 puppet-user[13320]: Compiled catalog for node-1.domain.tld in environment production in 0.08 seconds
Oct 21 17:59:51 node-1 puppet-user[13320]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 21 17:59:51 node-1 puppet-user[13320]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-kvm"]'
Oct 21 17:59:51 node-1 puppet-user[13320]: Finished catalog run in 0.06 seconds
Oct 21 17:59:52 node-1 puppet-user[13778]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 21 17:59:53 node-1 puppet-user[13778]: Compiled catalog for node-1.domain.tld in environment production in 0.51 seconds
Oct 21 17:59:53 node-1 puppet-user[13778]: (/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 21 17:59:53 node-1 puppet-user[13778]: (/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 21 17:59:53 node-1 puppet-user[13778]: (/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 21 17:59:53 node-1 puppet-user[13778]: (/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 21 17:59:53 node-1 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 21 17:59:53 node-1 puppet-user[13778]: (/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 21 17:59:53 node-1 puppet-user[13778]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 21 17:59:53 node-1 puppet-user[13778]: (/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 21 17:59:53 node-1 puppet-user[13778]: (/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 21 17:59:53 node-1 puppet-user[13778]: (/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 21 17:59:53 node-1 puppet-user[13778]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 21 17:59:54 node-1 puppet-user[13778]: Finished catalog run in 0.79 seconds
Oct 21 17:59:55 node-1 puppet-user[14283]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 21 17:59:55 node-1 puppet-user[14283]: Compiled catalog for node-1.domain.tld in environment production in 0.11 seconds
Oct 21 17:59:58 node-1 puppet-user[14283]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 21 18:00:01 node-1 CRON[15400]: (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 21 18:00:18 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 21 18:00:18 node-1 nailgun-agent: I, [2016-10-21T18:00:18.975927 #15403]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 21 18:00:25 node-1 puppet-user[14283]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 21 18:00:25 node-1 puppet-user[14283]: Finished catalog run in 29.48 seconds
Oct 21 18:00:27 node-1 puppet-user[16838]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 21 18:00:27 node-1 puppet-user[16838]: Compiled catalog for node-1.domain.tld in environment production in 0.48 seconds
Oct 21 18:00:27 node-1 puppet-user[16838]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 21 18:00:27 node-1 puppet-user[16838]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 21 18:00:27 node-1 puppet-user[16838]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 21 18:00:27 node-1 puppet-user[16838]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 21 18:00:27 node-1 puppet-user[16838]: Finished catalog run in 0.08 seconds
Oct 21 18:00:29 node-1 puppet-user[17296]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 21 18:00:30 node-1 puppet-user[17296]: Compiled catalog for node-1.domain.tld in environment production in 0.80 seconds
Oct 21 18:00:30 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 21 18:00:30 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 21 18:00:30 node-1 crontab[17730]: (root) LIST (root)
Oct 21 18:00:30 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 21 18:00:30 node-1 crontab[17731]: (root) REPLACE (root)
Oct 21 18:00:31 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 21 18:00:31 node-1 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 21 18:00:32 node-1 nailgun-agent: I, [2016-10-21T18:00:32.036365 #15403]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 1
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/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 21 18:00:32 node-1 puppet-user[17296]: (/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 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/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 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 21 18:00:32 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/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 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/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 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/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 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/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 21 18:00:33 node-1 puppet-user[17296]: (/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 21 18:00:33 node-1 puppet-user[17296]: (/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 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/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 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/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 21 18:00:33 node-1 puppet-user[17296]: (/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 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 21 18:00:33 node-1 puppet-user[17296]: (/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 21 18:00:33 node-1 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8386" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 21 18:00:33 node-1 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 21 18:00:35 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:35 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:35 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:35 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:35 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:48 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:48 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:48 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:48 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:48 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:50 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:50 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:50 node-1 multipathd: uevent trigger error
<27>Oct 21 18:00:50 node-1 multipathd: uevent trigger error
<27>Oct 21 18:01:46 node-1 ntpdate[28832]: no servers can be used, exiting
<27>Oct 21 18:01:46 node-1 ntpdate[28959]: no servers can be used, exiting
<27>Oct 21 18:02:18 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:18 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:18 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:18 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:18 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:21 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:31 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:35 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:35 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:35 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:35 node-1 multipathd: uevent trigger error
<27>Oct 21 18:02:35 node-1 multipathd: uevent trigger error
<27>Oct 21 18:03:29 node-1 multipathd: uevent trigger error
<27>Oct 21 18:03:29 node-1 multipathd: uevent trigger error
<27>Oct 21 18:03:29 node-1 multipathd: uevent trigger error
<27>Oct 21 18:03:29 node-1 multipathd: uevent trigger error
<27>Oct 21 18:03:38 node-1 multipathd: uevent trigger error
<27>Oct 21 18:03:38 node-1 multipathd: uevent trigger error
<27>Oct 21 18:03:38 node-1 multipathd: uevent trigger error
<27>Oct 21 18:03:38 node-1 multipathd: uevent trigger error
<27>Oct 21 18:03:38 node-1 multipathd: uevent trigger error
<27>Oct 21 18:03:40 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 21 18:03:41 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 21 18:03:47 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 21 18:03:47 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 21 18:03:52 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 21 18:03:58 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 21 18:03:58 node-1 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 21 18:04:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:06 node-1 ntpdate[13804]: the NTP socket is in use, exiting
<27>Oct 21 18:04:18 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:18 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:18 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:18 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:18 node-1 multipathd: uevent trigger error
<129>Oct 21 18:04:20 node-1 haproxy[16533]: 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 21 18:04:20 node-1 haproxy[16533]: 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 21 18:04:21 node-1 haproxy[16537]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:21 node-1 haproxy[16537]: proxy mysqld has no server available!
<27>Oct 21 18:04:23 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:23 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:23 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:23 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:23 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:26 node-1 multipathd: uevent trigger error
<129>Oct 21 18:04:29 node-1 haproxy[19313]: 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 21 18:04:29 node-1 haproxy[19313]: 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 21 18:04:29 node-1 haproxy[19313]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:29 node-1 haproxy[19313]: proxy mysqld has no server available!
<129>Oct 21 18:04:30 node-1 haproxy[19322]: 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 21 18:04:30 node-1 haproxy[19322]: 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 21 18:04:30 node-1 haproxy[19322]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:30 node-1 haproxy[19322]: proxy object-storage has no server available!
<27>Oct 21 18:04:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:32 node-1 multipathd: uevent trigger error
<129>Oct 21 18:04:34 node-1 haproxy[20684]: 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 21 18:04:34 node-1 haproxy[20684]: 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 21 18:04:35 node-1 haproxy[20688]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:35 node-1 haproxy[20688]: proxy neutron has no server available!
<129>Oct 21 18:04:35 node-1 haproxy[20688]: 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 21 18:04:35 node-1 haproxy[20688]: 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 21 18:04:35 node-1 haproxy[20688]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:35 node-1 haproxy[20688]: proxy mysqld has no server available!
<129>Oct 21 18:04:35 node-1 haproxy[20688]: 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 21 18:04:36 node-1 haproxy[20688]: 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 21 18:04:36 node-1 haproxy[20688]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:36 node-1 haproxy[20688]: proxy object-storage has no server available!
<27>Oct 21 18:04:37 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:37 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:37 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:37 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:37 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:37 node-1 multipathd: uevent trigger error
<129>Oct 21 18:04:40 node-1 haproxy[22041]: 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 21 18:04:40 node-1 haproxy[22041]: 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 21 18:04:40 node-1 haproxy[22041]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:40 node-1 haproxy[22041]: proxy keystone-1 has no server available!
<129>Oct 21 18:04:40 node-1 haproxy[22041]: 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 21 18:04:40 node-1 haproxy[22041]: Server keystone-2/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 21 18:04:40 node-1 haproxy[22041]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:40 node-1 haproxy[22041]: proxy keystone-2 has no server available!
<129>Oct 21 18:04:41 node-1 haproxy[22047]: 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 21 18:04:41 node-1 haproxy[22047]: 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 21 18:04:41 node-1 haproxy[22047]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:41 node-1 haproxy[22047]: proxy neutron has no server available!
<129>Oct 21 18:04:41 node-1 haproxy[22047]: 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 21 18:04:41 node-1 haproxy[22047]: 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 21 18:04:41 node-1 haproxy[22047]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:41 node-1 haproxy[22047]: proxy mysqld has no server available!
<129>Oct 21 18:04:41 node-1 haproxy[22047]: 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 21 18:04:41 node-1 haproxy[22047]: 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 21 18:04:42 node-1 haproxy[22047]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:42 node-1 haproxy[22047]: proxy object-storage has no server available!
<27>Oct 21 18:04:43 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:43 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:43 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:43 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:43 node-1 multipathd: uevent trigger error
<129>Oct 21 18:04:45 node-1 haproxy[23380]: 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 21 18:04:45 node-1 haproxy[23380]: 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 21 18:04:45 node-1 haproxy[23380]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:45 node-1 haproxy[23380]: proxy keystone-1 has no server available!
<129>Oct 21 18:04:45 node-1 haproxy[23380]: 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 21 18:04:45 node-1 haproxy[23380]: 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 21 18:04:46 node-1 haproxy[23384]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:46 node-1 haproxy[23384]: proxy keystone-2 has no server available!
<129>Oct 21 18:04:46 node-1 haproxy[23384]: 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 21 18:04:46 node-1 haproxy[23384]: 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 21 18:04:46 node-1 haproxy[23384]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:46 node-1 haproxy[23384]: proxy neutron has no server available!
<129>Oct 21 18:04:46 node-1 haproxy[23384]: 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 21 18:04:46 node-1 haproxy[23384]: 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 21 18:04:46 node-1 haproxy[23384]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:46 node-1 haproxy[23384]: proxy mysqld has no server available!
<129>Oct 21 18:04:46 node-1 haproxy[23384]: 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 21 18:04:46 node-1 haproxy[23384]: 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 21 18:04:47 node-1 haproxy[23384]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:47 node-1 haproxy[23384]: proxy object-storage has no server available!
<129>Oct 21 18:04:47 node-1 haproxy[23384]: 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 21 18:04:47 node-1 haproxy[23384]: 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 21 18:04:47 node-1 haproxy[23384]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:47 node-1 haproxy[23384]: proxy aodh has no server available!
<27>Oct 21 18:04:48 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:48 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:48 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:48 node-1 multipathd: uevent trigger error
<129>Oct 21 18:04:51 node-1 haproxy[24760]: 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 21 18:04:51 node-1 haproxy[24760]: 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 21 18:04:51 node-1 haproxy[24760]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:51 node-1 haproxy[24760]: proxy keystone-1 has no server available!
<129>Oct 21 18:04:51 node-1 haproxy[24760]: 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 21 18:04:51 node-1 haproxy[24760]: 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 21 18:04:51 node-1 haproxy[24760]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:51 node-1 haproxy[24760]: proxy keystone-2 has no server available!
<129>Oct 21 18:04:51 node-1 haproxy[24760]: 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 21 18:04:51 node-1 haproxy[24760]: 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 21 18:04:51 node-1 haproxy[24760]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:51 node-1 haproxy[24760]: proxy neutron has no server available!
<129>Oct 21 18:04:51 node-1 haproxy[24760]: 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 21 18:04:52 node-1 haproxy[24764]: 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 21 18:04:52 node-1 haproxy[24764]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:52 node-1 haproxy[24764]: proxy mysqld has no server available!
<129>Oct 21 18:04:52 node-1 haproxy[24764]: 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 21 18:04:52 node-1 haproxy[24764]: 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 21 18:04:52 node-1 haproxy[24764]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:52 node-1 haproxy[24764]: proxy object-storage has no server available!
<129>Oct 21 18:04:52 node-1 haproxy[24764]: 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 21 18:04:52 node-1 haproxy[24764]: 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 21 18:04:52 node-1 haproxy[24764]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:52 node-1 haproxy[24764]: proxy aodh has no server available!
<129>Oct 21 18:04:52 node-1 haproxy[24764]: 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 21 18:04:52 node-1 haproxy[24764]: 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 21 18:04:53 node-1 haproxy[24764]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:53 node-1 haproxy[24764]: proxy ceilometer has no server available!
<27>Oct 21 18:04:54 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:54 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:54 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:54 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:54 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:54 node-1 multipathd: uevent trigger error
<129>Oct 21 18:04:56 node-1 haproxy[26133]: 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 21 18:04:56 node-1 haproxy[26133]: 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 21 18:04:56 node-1 haproxy[26133]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:56 node-1 haproxy[26133]: proxy keystone-1 has no server available!
<129>Oct 21 18:04:56 node-1 haproxy[26133]: 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 21 18:04:56 node-1 haproxy[26133]: 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 21 18:04:57 node-1 haproxy[26139]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:57 node-1 haproxy[26139]: proxy keystone-2 has no server available!
<129>Oct 21 18:04:57 node-1 haproxy[26139]: 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 21 18:04:57 node-1 haproxy[26139]: 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 21 18:04:57 node-1 haproxy[26139]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:57 node-1 haproxy[26139]: proxy neutron has no server available!
<129>Oct 21 18:04:57 node-1 haproxy[26139]: 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 21 18:04:57 node-1 haproxy[26139]: 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 21 18:04:57 node-1 haproxy[26139]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:57 node-1 haproxy[26139]: proxy mysqld has no server available!
<129>Oct 21 18:04:57 node-1 haproxy[26139]: 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 21 18:04:57 node-1 haproxy[26139]: 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 21 18:04:57 node-1 haproxy[26139]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:57 node-1 haproxy[26139]: proxy object-storage has no server available!
<129>Oct 21 18:04:57 node-1 haproxy[26139]: 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 21 18:04:58 node-1 haproxy[26139]: 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 21 18:04:58 node-1 haproxy[26139]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:58 node-1 haproxy[26139]: proxy aodh has no server available!
<129>Oct 21 18:04:58 node-1 haproxy[26139]: 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 21 18:04:58 node-1 haproxy[26139]: 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 21 18:04:58 node-1 haproxy[26139]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:04:58 node-1 haproxy[26139]: proxy ceilometer has no server available!
<27>Oct 21 18:04:59 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:59 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:59 node-1 multipathd: uevent trigger error
<27>Oct 21 18:04:59 node-1 multipathd: uevent trigger error
<129>Oct 21 18:05:01 node-1 haproxy[27484]: 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 21 18:05:02 node-1 haproxy[27493]: 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 21 18:05:02 node-1 haproxy[27493]: 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 21 18:05:02 node-1 haproxy[27493]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:02 node-1 haproxy[27493]: proxy keystone-1 has no server available!
<129>Oct 21 18:05:02 node-1 haproxy[27493]: 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 21 18:05:02 node-1 haproxy[27493]: 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 21 18:05:02 node-1 haproxy[27493]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:02 node-1 haproxy[27493]: proxy keystone-2 has no server available!
<129>Oct 21 18:05:02 node-1 haproxy[27493]: 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 21 18:05:02 node-1 haproxy[27493]: 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 21 18:05:02 node-1 haproxy[27493]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:02 node-1 haproxy[27493]: proxy neutron has no server available!
<129>Oct 21 18:05:02 node-1 haproxy[27493]: 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 21 18:05:02 node-1 haproxy[27493]: 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 21 18:05:03 node-1 haproxy[27493]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:03 node-1 haproxy[27493]: proxy mysqld has no server available!
<129>Oct 21 18:05:03 node-1 haproxy[27493]: 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 21 18:05:03 node-1 haproxy[27493]: 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 21 18:05:03 node-1 haproxy[27493]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:03 node-1 haproxy[27493]: proxy object-storage has no server available!
<129>Oct 21 18:05:03 node-1 haproxy[27493]: 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 21 18:05:03 node-1 haproxy[27493]: 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 21 18:05:03 node-1 haproxy[27493]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:03 node-1 haproxy[27493]: proxy aodh has no server available!
<129>Oct 21 18:05:03 node-1 haproxy[27493]: 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 21 18:05:03 node-1 haproxy[27493]: 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 21 18:05:03 node-1 haproxy[27493]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:03 node-1 haproxy[27493]: proxy ceilometer has no server available!
<27>Oct 21 18:05:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:05 node-1 multipathd: uevent trigger error
<129>Oct 21 18:05:07 node-1 haproxy[29002]: 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 21 18:05:07 node-1 haproxy[29002]: 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 21 18:05:07 node-1 haproxy[29002]: 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 21 18:05:07 node-1 haproxy[29002]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:07 node-1 haproxy[29002]: proxy keystone-1 has no server available!
<129>Oct 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:08 node-1 haproxy[29006]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:08 node-1 haproxy[29006]: proxy keystone-2 has no server available!
<129>Oct 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:08 node-1 haproxy[29006]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:08 node-1 haproxy[29006]: proxy glance-api has no server available!
<129>Oct 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:08 node-1 haproxy[29006]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:08 node-1 haproxy[29006]: proxy glance-glare has no server available!
<129>Oct 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:08 node-1 haproxy[29006]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:08 node-1 haproxy[29006]: proxy neutron has no server available!
<129>Oct 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:08 node-1 haproxy[29006]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:08 node-1 haproxy[29006]: proxy glance-registry has no server available!
<129>Oct 21 18:05:08 node-1 haproxy[29006]: 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 21 18:05:09 node-1 haproxy[29006]: 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 21 18:05:09 node-1 haproxy[29006]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:09 node-1 haproxy[29006]: proxy mysqld has no server available!
<129>Oct 21 18:05:09 node-1 haproxy[29006]: 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 21 18:05:09 node-1 haproxy[29006]: 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 21 18:05:09 node-1 haproxy[29006]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:09 node-1 haproxy[29006]: proxy object-storage has no server available!
<129>Oct 21 18:05:09 node-1 haproxy[29006]: 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 21 18:05:09 node-1 haproxy[29006]: 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 21 18:05:09 node-1 haproxy[29006]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:09 node-1 haproxy[29006]: proxy aodh has no server available!
<129>Oct 21 18:05:09 node-1 haproxy[29006]: 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 21 18:05:09 node-1 haproxy[29006]: 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 21 18:05:09 node-1 haproxy[29006]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:09 node-1 haproxy[29006]: proxy ceilometer has no server available!
<27>Oct 21 18:05:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:10 node-1 multipathd: uevent trigger error
<129>Oct 21 18:05:13 node-1 haproxy[30404]: 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 21 18:05:13 node-1 haproxy[30404]: 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 21 18:05:13 node-1 haproxy[30404]: 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 21 18:05:13 node-1 haproxy[30404]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:13 node-1 haproxy[30404]: proxy keystone-1 has no server available!
<129>Oct 21 18:05:13 node-1 haproxy[30404]: 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 21 18:05:13 node-1 haproxy[30404]: 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 21 18:05:13 node-1 haproxy[30404]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:13 node-1 haproxy[30404]: proxy keystone-2 has no server available!
<129>Oct 21 18:05:13 node-1 haproxy[30404]: 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 21 18:05:13 node-1 haproxy[30404]: 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 21 18:05:13 node-1 haproxy[30404]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:13 node-1 haproxy[30404]: proxy nova-api has no server available!
<129>Oct 21 18:05:13 node-1 haproxy[30404]: 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 21 18:05:13 node-1 haproxy[30404]: 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 21 18:05:14 node-1 haproxy[30408]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:14 node-1 haproxy[30408]: proxy nova-metadata-api has no server available!
<129>Oct 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:14 node-1 haproxy[30408]: proxy glance-api has no server available!
<129>Oct 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:14 node-1 haproxy[30408]: proxy glance-glare has no server available!
<129>Oct 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:14 node-1 haproxy[30408]: proxy neutron has no server available!
<129>Oct 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:14 node-1 haproxy[30408]: proxy glance-registry has no server available!
<129>Oct 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:14 node-1 haproxy[30408]: proxy mysqld has no server available!
<129>Oct 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:14 node-1 haproxy[30408]: proxy object-storage has no server available!
<129>Oct 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:14 node-1 haproxy[30408]: 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 21 18:05:15 node-1 haproxy[30408]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:15 node-1 haproxy[30408]: proxy aodh has no server available!
<129>Oct 21 18:05:15 node-1 haproxy[30408]: 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 21 18:05:15 node-1 haproxy[30408]: 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 21 18:05:15 node-1 haproxy[30408]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:15 node-1 haproxy[30408]: proxy ceilometer has no server available!
<129>Oct 21 18:05:15 node-1 haproxy[30408]: 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 21 18:05:15 node-1 haproxy[30408]: 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 21 18:05:15 node-1 haproxy[30408]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:15 node-1 haproxy[30408]: proxy nova-novncproxy has no server available!
<27>Oct 21 18:05:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:16 node-1 multipathd: uevent trigger error
<129>Oct 21 18:05:18 node-1 haproxy[31913]: 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 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:19 node-1 haproxy[31917]: proxy keystone-1 has no server available!
<129>Oct 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:19 node-1 haproxy[31917]: proxy keystone-2 has no server available!
<129>Oct 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:19 node-1 haproxy[31917]: proxy nova-api has no server available!
<129>Oct 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:19 node-1 haproxy[31917]: proxy nova-metadata-api has no server available!
<129>Oct 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:19 node-1 haproxy[31917]: proxy cinder-api has no server available!
<129>Oct 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:19 node-1 haproxy[31917]: proxy glance-api has no server available!
<129>Oct 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:19 node-1 haproxy[31917]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:19 node-1 haproxy[31917]: proxy glance-glare has no server available!
<129>Oct 21 18:05:19 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:20 node-1 haproxy[31917]: proxy neutron has no server available!
<129>Oct 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:20 node-1 haproxy[31917]: proxy glance-registry has no server available!
<129>Oct 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:20 node-1 haproxy[31917]: proxy mysqld has no server available!
<129>Oct 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:20 node-1 haproxy[31917]: proxy object-storage has no server available!
<129>Oct 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:20 node-1 haproxy[31917]: proxy aodh has no server available!
<129>Oct 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:20 node-1 haproxy[31917]: proxy ceilometer has no server available!
<129>Oct 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: 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 21 18:05:20 node-1 haproxy[31917]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:20 node-1 haproxy[31917]: proxy nova-novncproxy has no server available!
<27>Oct 21 18:05:21 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:21 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:21 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:21 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:21 node-1 multipathd: uevent trigger error
<129>Oct 21 18:05:24 node-1 haproxy[856]: 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 21 18:05:24 node-1 haproxy[856]: 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 21 18:05:24 node-1 haproxy[856]: 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 21 18:05:24 node-1 haproxy[856]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:24 node-1 haproxy[856]: proxy keystone-1 has no server available!
<129>Oct 21 18:05:24 node-1 haproxy[856]: 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 21 18:05:24 node-1 haproxy[856]: 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 21 18:05:24 node-1 haproxy[856]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:24 node-1 haproxy[856]: proxy keystone-2 has no server available!
<129>Oct 21 18:05:24 node-1 haproxy[856]: 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 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:25 node-1 haproxy[860]: proxy nova-api has no server available!
<129>Oct 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:25 node-1 haproxy[860]: proxy nova-metadata-api has no server available!
<129>Oct 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:25 node-1 haproxy[860]: proxy cinder-api has no server available!
<129>Oct 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:25 node-1 haproxy[860]: proxy glance-api has no server available!
<129>Oct 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:25 node-1 haproxy[860]: proxy glance-glare has no server available!
<129>Oct 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:25 node-1 haproxy[860]: proxy neutron has no server available!
<129>Oct 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:25 node-1 haproxy[860]: proxy glance-registry has no server available!
<129>Oct 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:25 node-1 haproxy[860]: proxy mysqld has no server available!
<129>Oct 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:25 node-1 haproxy[860]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:25 node-1 haproxy[860]: proxy object-storage has no server available!
<129>Oct 21 18:05:25 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:26 node-1 haproxy[860]: proxy aodh has no server available!
<129>Oct 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:26 node-1 haproxy[860]: proxy ceilometer has no server available!
<129>Oct 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:26 node-1 haproxy[860]: proxy heat-api has no server available!
<129>Oct 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:26 node-1 haproxy[860]: proxy heat-api-cfn has no server available!
<129>Oct 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:26 node-1 haproxy[860]: proxy heat-api-cloudwatch has no server available!
<129>Oct 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: 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 21 18:05:26 node-1 haproxy[860]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 21 18:05:26 node-1 haproxy[860]: proxy nova-novncproxy has no server available!
<27>Oct 21 18:05:27 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:27 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:27 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:27 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:31 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:31 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:31 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:31 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:31 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:31 node-1 multipathd: uevent trigger error
<27>Oct 21 18:05:38 node-1 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 21 18:06:02 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 21 18:06:04 node-1 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 21 18:06:26 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 21 18:06:32 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 21 18:06:50 node-1 multipathd: uevent trigger error
<27>Oct 21 18:06:50 node-1 multipathd: uevent trigger error
<27>Oct 21 18:06:50 node-1 multipathd: uevent trigger error
<27>Oct 21 18:06:50 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:09 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:09 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:09 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:09 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:09 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:29 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 21 18:09:34 node-1 apache2_error [Fri Oct 21 18:09:30.738194 2016] [mpm_event:notice] [pid 10525:tid 139697086687104] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 21 18:09:34 node-1 apache2_error [Fri Oct 21 18:09:30.738344 2016] [core:notice] [pid 10525:tid 139697086687104] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 21 18:09:34 node-1 apache2_error [Fri Oct 21 18:09:33.704201 2016] [mpm_event:notice] [pid 10525:tid 139697086687104] AH00491: caught SIGTERM, shutting down
<27>Oct 21 18:09:39 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:39 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:39 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:39 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:39 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:09:42 node-1 multipathd: uevent trigger error
<43>Oct 21 18:09:44 node-1 apache2_error [Fri Oct 21 18:09:34.795480 2016] [mpm_worker:notice] [pid 10897:tid 140520299341696] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 21 18:09:44 node-1 apache2_error [Fri Oct 21 18:09:34.795502 2016] [core:notice] [pid 10897:tid 140520299341696] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 21 18:10:54 node-1 apache2_error [Fri Oct 21 18:10:45.387477 2016] [mpm_worker:notice] [pid 10897:tid 140520299341696] AH00295: caught SIGTERM, shutting down
<43>Oct 21 18:10:54 node-1 apache2_error [Fri Oct 21 18:10:46.137757 2016] [mpm_worker:notice] [pid 22775:tid 139825308358528] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 21 18:10:54 node-1 apache2_error [Fri Oct 21 18:10:46.137795 2016] [core:notice] [pid 22775:tid 139825308358528] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 21 18:11:34 node-1 apache2_error [Fri Oct 21 18:11:30.060571 2016] [mpm_worker:notice] [pid 22775:tid 139825308358528] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 21 18:11:34 node-1 apache2_error [Fri Oct 21 18:11:30.256279 2016] [mpm_worker:warn] [pid 22775:tid 139825308358528] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 21 18:11:34 node-1 apache2_error [Fri Oct 21 18:11:30.260175 2016] [mpm_worker:notice] [pid 22775:tid 139825308358528] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 21 18:11:34 node-1 apache2_error [Fri Oct 21 18:11:30.260193 2016] [core:notice] [pid 22775:tid 139825308358528] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 21 18:12:14 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:14 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:14 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:14 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:14 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:30 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 21 18:12:34 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:34 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:34 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:34 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:34 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:34 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:56 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:56 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:56 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:56 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:56 node-1 multipathd: uevent trigger error
<27>Oct 21 18:12:56 node-1 multipathd: uevent trigger error
<27>Oct 21 18:13:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:13:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:13:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:13:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:13:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:13:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:13:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:13:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:13:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:13:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:14:08 node-1 multipathd: uevent trigger error
<27>Oct 21 18:14:08 node-1 multipathd: uevent trigger error
<27>Oct 21 18:14:08 node-1 multipathd: uevent trigger error
<27>Oct 21 18:14:08 node-1 multipathd: uevent trigger error
<27>Oct 21 18:15:21 node-1 multipathd: uevent trigger error
<27>Oct 21 18:15:21 node-1 multipathd: uevent trigger error
<27>Oct 21 18:15:21 node-1 multipathd: uevent trigger error
<27>Oct 21 18:15:21 node-1 multipathd: uevent trigger error
<27>Oct 21 18:15:21 node-1 multipathd: uevent trigger error
<27>Oct 21 18:15:32 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 21 18:16:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:22 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:22 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:22 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:22 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:49 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:49 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:49 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:49 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:49 node-1 multipathd: uevent trigger error
<27>Oct 21 18:16:49 node-1 multipathd: uevent trigger error
<27>Oct 21 18:18:33 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 21 18:19:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:27 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:28 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:28 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:28 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:28 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:19:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:41 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:41 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:41 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:41 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:41 node-1 multipathd: uevent trigger error
<27>Oct 21 18:20:41 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:24 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:24 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:24 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:24 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:31 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Oct 21 18:21:31 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Oct 21 18:21:31 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Oct 21 18:21:32 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Oct 21 18:21:32 node-1 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Oct 21 18:21:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:33 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:35 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 21 18:21:46 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:46 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:46 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:46 node-1 multipathd: uevent trigger error
<27>Oct 21 18:21:46 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:17 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:17 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:17 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:17 node-1 multipathd: uevent trigger error
<27>Oct 21 18:22:18 node-1 multipathd: uevent trigger error
<27>Oct 21 18:24:36 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 21 18:24:37 node-1 multipathd: uevent trigger error
<27>Oct 21 18:24:37 node-1 multipathd: uevent trigger error
<27>Oct 21 18:24:37 node-1 multipathd: uevent trigger error
<27>Oct 21 18:24:37 node-1 multipathd: uevent trigger error
<27>Oct 21 18:24:37 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:11 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:11 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:11 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:11 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:49 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:49 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:49 node-1 multipathd: uevent trigger error
<27>Oct 21 18:25:49 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:01 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:26:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:27:02 node-1 multipathd: uevent trigger error
<27>Oct 21 18:27:02 node-1 multipathd: uevent trigger error
<27>Oct 21 18:27:02 node-1 multipathd: uevent trigger error
<27>Oct 21 18:27:02 node-1 multipathd: uevent trigger error
<27>Oct 21 18:27:02 node-1 multipathd: uevent trigger error
<27>Oct 21 18:27:38 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 21 18:28:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:28:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:28:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:28:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:28:05 node-1 multipathd: uevent trigger error
<27>Oct 21 18:28:22 node-1 multipathd: uevent trigger error
<27>Oct 21 18:28:22 node-1 multipathd: uevent trigger error
<27>Oct 21 18:28:22 node-1 multipathd: uevent trigger error
<27>Oct 21 18:28:22 node-1 multipathd: uevent trigger error
<27>Oct 21 18:28:22 node-1 multipathd: uevent trigger error
<11>Oct 21 18:28:34 node-1 liberasurecode[5199]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:34 node-1 liberasurecode[5199]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:34 node-1 liberasurecode[5199]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:34 node-1 liberasurecode[5199]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:34 node-1 liberasurecode[5238]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:34 node-1 liberasurecode[5238]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:34 node-1 liberasurecode[5238]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:34 node-1 liberasurecode[5238]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:35 node-1 liberasurecode[5990]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:35 node-1 liberasurecode[5990]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:35 node-1 liberasurecode[5990]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:35 node-1 liberasurecode[5990]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6685]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6685]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6685]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6685]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6726]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6726]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6726]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6726]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6794]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6794]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6794]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6794]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6868]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6868]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6868]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6868]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6880]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6880]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6880]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6880]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6895]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6895]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6895]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:40 node-1 liberasurecode[6895]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:41 node-1 liberasurecode[6911]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:41 node-1 liberasurecode[6911]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:41 node-1 liberasurecode[6911]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:41 node-1 liberasurecode[6911]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:57 node-1 liberasurecode[9313]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:57 node-1 liberasurecode[9313]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:57 node-1 liberasurecode[9313]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:28:57 node-1 liberasurecode[9313]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 21 18:29:06 node-1 multipathd: uevent trigger error
<27>Oct 21 18:29:06 node-1 multipathd: uevent trigger error
<27>Oct 21 18:29:06 node-1 multipathd: uevent trigger error
<27>Oct 21 18:29:06 node-1 multipathd: uevent trigger error
<27>Oct 21 18:29:06 node-1 multipathd: uevent trigger error
<43>Oct 21 18:29:56 node-1 apache2_error [Fri Oct 21 18:29:52.876297 2016] [mpm_worker:notice] [pid 22775:tid 139825308358528] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 21 18:29:56 node-1 apache2_error [Fri Oct 21 18:29:53.265503 2016] [mpm_worker:warn] [pid 22775:tid 139825308358528] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 21 18:29:56 node-1 apache2_error [Fri Oct 21 18:29:53.270767 2016] [mpm_worker:notice] [pid 22775:tid 139825308358528] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 21 18:29:56 node-1 apache2_error [Fri Oct 21 18:29:53.270796 2016] [core:notice] [pid 22775:tid 139825308358528] AH00094: Command line: '/usr/sbin/apache2'
<11>Oct 21 18:30:01 node-1 liberasurecode[18624]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:30:01 node-1 liberasurecode[18624]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:30:01 node-1 liberasurecode[18624]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:30:01 node-1 liberasurecode[18624]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 21 18:30:34 node-1 multipathd: uevent trigger error
<27>Oct 21 18:30:34 node-1 multipathd: uevent trigger error
<27>Oct 21 18:30:34 node-1 multipathd: uevent trigger error
<27>Oct 21 18:30:34 node-1 multipathd: uevent trigger error
<43>Oct 21 18:30:36 node-1 apache2_error [Fri Oct 21 18:30:30.353827 2016] [mpm_worker:notice] [pid 22775:tid 139825308358528] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 21 18:30:36 node-1 apache2_error [Fri Oct 21 18:30:30.551561 2016] [mpm_worker:warn] [pid 22775:tid 139825308358528] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 21 18:30:36 node-1 apache2_error [Fri Oct 21 18:30:30.559091 2016] [mpm_worker:notice] [pid 22775:tid 139825308358528] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 21 18:30:36 node-1 apache2_error [Fri Oct 21 18:30:30.559111 2016] [core:notice] [pid 22775:tid 139825308358528] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 21 18:30:40 node-1 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 21 18:30:41 node-1 multipathd: uevent trigger error
<27>Oct 21 18:30:41 node-1 multipathd: uevent trigger error
<27>Oct 21 18:30:41 node-1 multipathd: uevent trigger error
<27>Oct 21 18:30:41 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:20 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:20 node-1 multipathd: uevent trigger error
<43>Oct 21 18:31:26 node-1 apache2_error [Fri Oct 21 18:31:16.194479 2016] [mpm_worker:notice] [pid 22775:tid 139825308358528] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 21 18:31:26 node-1 apache2_error [Fri Oct 21 18:31:16.392181 2016] [mpm_worker:warn] [pid 22775:tid 139825308358528] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 21 18:31:26 node-1 apache2_error [Fri Oct 21 18:31:16.399369 2016] [mpm_worker:notice] [pid 22775:tid 139825308358528] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 21 18:31:26 node-1 apache2_error [Fri Oct 21 18:31:16.399393 2016] [core:notice] [pid 22775:tid 139825308358528] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 21 18:31:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:31 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:56 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:56 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:56 node-1 multipathd: uevent trigger error
<27>Oct 21 18:31:56 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:16 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:22 node-1 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 21 18:32:31 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:31 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:32 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:36 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:36 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:36 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:36 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:36 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:42 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:55 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:55 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:55 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:55 node-1 multipathd: uevent trigger error
<27>Oct 21 18:32:59 node-1 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 21 18:33:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:10 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:26 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:40 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:40 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:40 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:40 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:40 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:47 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:47 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:47 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:48 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:48 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:52 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:52 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:53 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:53 node-1 multipathd: uevent trigger error
<27>Oct 21 18:33:53 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:06 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:06 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:06 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:06 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:06 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:11 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:11 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:11 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:11 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:11 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:11 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:15 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:19 node-1 multipathd: uevent trigger error
<27>Oct 21 18:34:19 node-1 multipathd: uevent trigger error
<11>Oct 21 18:35:01 node-1 liberasurecode[21578]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:35:01 node-1 liberasurecode[21578]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:35:01 node-1 liberasurecode[21578]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 21 18:35:01 node-1 liberasurecode[21578]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
