Nov  5 08:56:27 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8423" x-info="http://www.rsyslog.com"] start
Nov  5 08:56:27 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov  5 08:56:27 node-2 rsyslogd: rsyslogd's groupid changed to 104
Nov  5 08:56:27 node-2 rsyslogd: rsyslogd's userid changed to 101
Nov  5 08:56:27 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov  5 08:56:27 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov  5 08:56:27 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov  5 08:56:27 node-2 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Nov  5 08:56:27 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=75a5626e-434b-4b3e-8661-9d67771b59af nomdmonddf nomdmonisw
Nov  5 08:56:27 node-2 kernel: [    0.000000] KERNEL supported cpus:
Nov  5 08:56:27 node-2 kernel: [    0.000000]   Intel GenuineIntel
Nov  5 08:56:27 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Nov  5 08:56:27 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Nov  5 08:56:27 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov  5 08:56:27 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov  5 08:56:27 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov  5 08:56:27 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Nov  5 08:56:27 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Nov  5 08:56:27 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov  5 08:56:27 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov  5 08:56:27 node-2 kernel: [    0.000000] No AGP bridge found
Nov  5 08:56:27 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov  5 08:56:27 node-2 kernel: [    0.000000] MTRR default type: write-back
Nov  5 08:56:27 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov  5 08:56:27 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Nov  5 08:56:27 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov  5 08:56:27 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov  5 08:56:27 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Nov  5 08:56:27 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov  5 08:56:27 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov  5 08:56:27 node-2 kernel: [    0.000000]   2 disabled
Nov  5 08:56:27 node-2 kernel: [    0.000000]   3 disabled
Nov  5 08:56:27 node-2 kernel: [    0.000000]   4 disabled
Nov  5 08:56:27 node-2 kernel: [    0.000000]   5 disabled
Nov  5 08:56:27 node-2 kernel: [    0.000000]   6 disabled
Nov  5 08:56:27 node-2 kernel: [    0.000000]   7 disabled
Nov  5 08:56:27 node-2 kernel: [    0.000000]   8 disabled
Nov  5 08:56:27 node-2 kernel: [    0.000000]   9 disabled
Nov  5 08:56:27 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov  5 08:56:27 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov  5 08:56:27 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov  5 08:56:27 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov  5 08:56:27 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov  5 08:56:27 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Nov  5 08:56:27 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov  5 08:56:27 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov  5 08:56:27 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov  5 08:56:27 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov  5 08:56:27 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov  5 08:56:27 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov  5 08:56:27 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov  5 08:56:27 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Nov  5 08:56:27 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov  5 08:56:27 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov  5 08:56:27 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov  5 08:56:27 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov  5 08:56:27 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov  5 08:56:27 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov  5 08:56:27 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov  5 08:56:27 node-2 kernel: [    0.000000] Zone ranges:
Nov  5 08:56:27 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] Movable zone start for each node
Nov  5 08:56:27 node-2 kernel: [    0.000000] Early memory node ranges
Nov  5 08:56:27 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Nov  5 08:56:27 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov  5 08:56:27 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov  5 08:56:27 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov  5 08:56:27 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Nov  5 08:56:27 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Nov  5 08:56:27 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov  5 08:56:27 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov  5 08:56:27 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov  5 08:56:27 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov  5 08:56:27 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov  5 08:56:27 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov  5 08:56:27 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov  5 08:56:27 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov  5 08:56:27 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov  5 08:56:27 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov  5 08:56:27 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov  5 08:56:27 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov  5 08:56:27 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov  5 08:56:27 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov  5 08:56:27 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov  5 08:56:27 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov  5 08:56:27 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov  5 08:56:27 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Nov  5 08:56:27 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Nov  5 08:56:27 node-2 kernel: [    0.000000] Policy zone: Normal
Nov  5 08:56:27 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=75a5626e-434b-4b3e-8661-9d67771b59af nomdmonddf nomdmonisw
Nov  5 08:56:27 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov  5 08:56:27 node-2 kernel: [    0.000000] Checking aperture...
Nov  5 08:56:27 node-2 kernel: [    0.000000] No AGP bridge found
Nov  5 08:56:27 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov  5 08:56:27 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov  5 08:56:27 node-2 kernel: [    0.000000] Memory: 32653312K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627184K reserved)
Nov  5 08:56:27 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov  5 08:56:27 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Nov  5 08:56:27 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov  5 08:56:27 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov  5 08:56:27 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov  5 08:56:27 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov  5 08:56:27 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov  5 08:56:27 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Nov  5 08:56:27 node-2 kernel: [    0.000000] console [tty0] enabled
Nov  5 08:56:27 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov  5 08:56:27 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov  5 08:56:27 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov  5 08:56:27 node-2 kernel: [    0.000000] hpet clockevent registered
Nov  5 08:56:27 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov  5 08:56:27 node-2 kernel: [    0.004000] tsc: Detected 3492.236 MHz processor
Nov  5 08:56:27 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.47 BogoMIPS (lpj=13968944)
Nov  5 08:56:27 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov  5 08:56:27 node-2 kernel: [    0.000042] Security Framework initialized
Nov  5 08:56:27 node-2 kernel: [    0.000060] AppArmor: AppArmor initialized
Nov  5 08:56:27 node-2 kernel: [    0.000062] Yama: becoming mindful.
Nov  5 08:56:27 node-2 kernel: [    0.001459] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.006379] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.008309] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.008338] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.008628] Initializing cgroup subsys memory
Nov  5 08:56:27 node-2 kernel: [    0.008637] Initializing cgroup subsys devices
Nov  5 08:56:27 node-2 kernel: [    0.008639] Initializing cgroup subsys freezer
Nov  5 08:56:27 node-2 kernel: [    0.008640] Initializing cgroup subsys blkio
Nov  5 08:56:27 node-2 kernel: [    0.008642] Initializing cgroup subsys perf_event
Nov  5 08:56:27 node-2 kernel: [    0.008644] Initializing cgroup subsys hugetlb
Nov  5 08:56:27 node-2 kernel: [    0.008663] CPU: Physical Processor ID: 0
Nov  5 08:56:27 node-2 kernel: [    0.008665] CPU: Processor Core ID: 0
Nov  5 08:56:27 node-2 kernel: [    0.008668] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov  5 08:56:27 node-2 kernel: [    0.008668] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov  5 08:56:27 node-2 kernel: [    0.009362] mce: CPU supports 22 MCE banks
Nov  5 08:56:27 node-2 kernel: [    0.009390] CPU0: Thermal monitoring enabled (TM1)
Nov  5 08:56:27 node-2 kernel: [    0.009411] process: using mwait in idle threads
Nov  5 08:56:27 node-2 kernel: [    0.009414] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov  5 08:56:27 node-2 kernel: [    0.009414] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov  5 08:56:27 node-2 kernel: [    0.009414] tlb_flushall_shift: 6
Nov  5 08:56:27 node-2 kernel: [    0.009503] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov  5 08:56:27 node-2 kernel: [    0.010225] ACPI: Core revision 20131115
Nov  5 08:56:27 node-2 kernel: [    0.023048] ACPI: All ACPI Tables successfully acquired
Nov  5 08:56:27 node-2 kernel: [    0.023208] ftrace: allocating 28622 entries in 112 pages
Nov  5 08:56:27 node-2 kernel: [    0.031954] dmar: Host address width 46
Nov  5 08:56:27 node-2 kernel: [    0.031956] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov  5 08:56:27 node-2 kernel: [    0.031962] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  5 08:56:27 node-2 kernel: [    0.031964] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov  5 08:56:27 node-2 kernel: [    0.031968] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  5 08:56:27 node-2 kernel: [    0.031970] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov  5 08:56:27 node-2 kernel: [    0.031971] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov  5 08:56:27 node-2 kernel: [    0.031972] dmar: ATSR flags: 0x0
Nov  5 08:56:27 node-2 kernel: [    0.031973] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov  5 08:56:27 node-2 kernel: [    0.031974] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov  5 08:56:27 node-2 kernel: [    0.032090] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov  5 08:56:27 node-2 kernel: [    0.032091] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov  5 08:56:27 node-2 kernel: [    0.032092] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov  5 08:56:27 node-2 kernel: [    0.032093] HPET id 0 under DRHD base 0xc7ffc000
Nov  5 08:56:27 node-2 kernel: [    0.032094] Your BIOS is broken and requested that x2apic be disabled.
Nov  5 08:56:27 node-2 kernel: [    0.032094] This will slightly decrease performance.
Nov  5 08:56:27 node-2 kernel: [    0.032094] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov  5 08:56:27 node-2 kernel: [    0.032527] Enabled IRQ remapping in xapic mode
Nov  5 08:56:27 node-2 kernel: [    0.032528] x2apic not enabled, IRQ remapping is in xapic mode
Nov  5 08:56:27 node-2 kernel: [    0.032532] Switched APIC routing to physical flat.
Nov  5 08:56:27 node-2 kernel: [    0.033154] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov  5 08:56:27 node-2 kernel: [    0.072807] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov  5 08:56:27 node-2 kernel: [    0.072812] TSC deadline timer enabled
Nov  5 08:56:27 node-2 kernel: [    0.072820] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov  5 08:56:27 node-2 kernel: [    0.072826] ... version:                3
Nov  5 08:56:27 node-2 kernel: [    0.072827] ... bit width:              48
Nov  5 08:56:27 node-2 kernel: [    0.072827] ... generic registers:      4
Nov  5 08:56:27 node-2 kernel: [    0.072828] ... value mask:             0000ffffffffffff
Nov  5 08:56:27 node-2 kernel: [    0.072829] ... max period:             0000ffffffffffff
Nov  5 08:56:27 node-2 kernel: [    0.072830] ... fixed-purpose events:   3
Nov  5 08:56:27 node-2 kernel: [    0.072831] ... event mask:             000000070000000f
Nov  5 08:56:27 node-2 kernel: [    0.074234] x86: Booting SMP configuration:
Nov  5 08:56:27 node-2 kernel: [    0.088341] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov  5 08:56:27 node-2 kernel: [    0.074236] .... node  #0, CPUs:        #1  #2  #3
Nov  5 08:56:27 node-2 kernel: [    0.116265] .... node  #1, CPUs:    #4  #5  #6  #7
Nov  5 08:56:27 node-2 kernel: [    0.270127] .... node  #0, CPUs:    #8  #9 #10 #11
Nov  5 08:56:27 node-2 kernel: [    0.325744] .... node  #1, CPUs:   #12 #13 #14 #15
Nov  5 08:56:27 node-2 kernel: [    0.382604] x86: Booted up 2 nodes, 16 CPUs
Nov  5 08:56:27 node-2 kernel: [    0.382607] smpboot: Total of 16 processors activated (111763.68 BogoMIPS)
Nov  5 08:56:27 node-2 kernel: [    0.407540] devtmpfs: initialized
Nov  5 08:56:27 node-2 kernel: [    0.409882] EVM: security.selinux
Nov  5 08:56:27 node-2 kernel: [    0.409883] EVM: security.SMACK64
Nov  5 08:56:27 node-2 kernel: [    0.409884] EVM: security.ima
Nov  5 08:56:27 node-2 kernel: [    0.409885] EVM: security.capability
Nov  5 08:56:27 node-2 kernel: [    0.409936] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.410596] pinctrl core: initialized pinctrl subsystem
Nov  5 08:56:27 node-2 kernel: [    0.410659] regulator-dummy: no parameters
Nov  5 08:56:27 node-2 kernel: [    0.410691] RTC time:  8:55:49, date: 11/05/16
Nov  5 08:56:27 node-2 kernel: [    0.410724] NET: Registered protocol family 16
Nov  5 08:56:27 node-2 kernel: [    0.410808] cpuidle: using governor ladder
Nov  5 08:56:27 node-2 kernel: [    0.410809] cpuidle: using governor menu
Nov  5 08:56:27 node-2 kernel: [    0.410842] ACPI: bus type PCI registered
Nov  5 08:56:27 node-2 kernel: [    0.410844] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov  5 08:56:27 node-2 kernel: [    0.410889] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov  5 08:56:27 node-2 kernel: [    0.410892] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov  5 08:56:27 node-2 kernel: [    0.424633] PCI: Using configuration type 1 for base access
Nov  5 08:56:27 node-2 kernel: [    0.425626] bio: create slab <bio-0> at 0
Nov  5 08:56:27 node-2 kernel: [    0.425912] ACPI: Added _OSI(Module Device)
Nov  5 08:56:27 node-2 kernel: [    0.425913] ACPI: Added _OSI(Processor Device)
Nov  5 08:56:27 node-2 kernel: [    0.425915] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov  5 08:56:27 node-2 kernel: [    0.425916] ACPI: Added _OSI(Processor Aggregator Device)
Nov  5 08:56:27 node-2 kernel: [    0.438605] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov  5 08:56:27 node-2 kernel: [    0.449114] ACPI: Interpreter enabled
Nov  5 08:56:27 node-2 kernel: [    0.449120] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov  5 08:56:27 node-2 kernel: [    0.449124] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov  5 08:56:27 node-2 kernel: [    0.449127] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov  5 08:56:27 node-2 kernel: [    0.449134] ACPI: (supports S0 S4 S5)
Nov  5 08:56:27 node-2 kernel: [    0.449135] ACPI: Using IOAPIC for interrupt routing
Nov  5 08:56:27 node-2 kernel: [    0.449176] HEST: Table parsing has been initialized.
Nov  5 08:56:27 node-2 kernel: [    0.449179] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov  5 08:56:27 node-2 kernel: [    0.449754] ACPI: No dock devices found.
Nov  5 08:56:27 node-2 kernel: [    0.461710] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov  5 08:56:27 node-2 kernel: [    0.461715] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 08:56:27 node-2 kernel: [    0.461719] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  5 08:56:27 node-2 kernel: [    0.461747] PCI host bridge to bus 0000:ff
Nov  5 08:56:27 node-2 kernel: [    0.461749] pci_bus 0000:ff: root bus resource [bus ff]
Nov  5 08:56:27 node-2 kernel: [    0.461757] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.461796] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.461826] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.461861] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.461890] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.461919] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.461950] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.461979] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462009] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462037] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462063] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462089] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462117] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462142] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462169] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462195] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462223] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462250] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462277] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.462305] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462330] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.462356] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462382] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462411] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.462447] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462477] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462507] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462537] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462567] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462600] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462632] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462665] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462696] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462729] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462759] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462792] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462824] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462854] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462881] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462913] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462946] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.462982] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463017] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463048] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463077] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463107] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463138] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463168] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463199] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463230] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463261] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463289] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463318] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463347] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463376] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463411] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463442] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463499] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov  5 08:56:27 node-2 kernel: [    0.463502] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 08:56:27 node-2 kernel: [    0.463505] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  5 08:56:27 node-2 kernel: [    0.463525] PCI host bridge to bus 0000:7f
Nov  5 08:56:27 node-2 kernel: [    0.463526] pci_bus 0000:7f: root bus resource [bus 7f]
Nov  5 08:56:27 node-2 kernel: [    0.463531] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463558] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.463586] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463615] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463637] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.463661] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.463687] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463712] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463734] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463756] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463778] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463800] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463824] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463846] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463869] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463894] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463915] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463938] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.463960] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.463983] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464005] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.464027] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464049] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464075] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov  5 08:56:27 node-2 kernel: [    0.464107] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464133] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464159] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464184] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464209] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464235] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464261] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464288] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464314] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464344] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464371] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464398] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464425] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464449] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464473] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464501] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464526] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464555] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464585] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464614] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464639] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464664] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464692] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464721] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464748] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464775] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464806] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464832] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464855] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464881] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464907] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464937] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.464964] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.466220] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov  5 08:56:27 node-2 kernel: [    0.466224] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 08:56:27 node-2 kernel: [    0.467341] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  5 08:56:27 node-2 kernel: [    0.467850] PCI host bridge to bus 0000:00
Nov  5 08:56:27 node-2 kernel: [    0.467852] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov  5 08:56:27 node-2 kernel: [    0.467854] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov  5 08:56:27 node-2 kernel: [    0.467855] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov  5 08:56:27 node-2 kernel: [    0.467856] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov  5 08:56:27 node-2 kernel: [    0.467858] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov  5 08:56:27 node-2 kernel: [    0.467859] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov  5 08:56:27 node-2 kernel: [    0.467860] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov  5 08:56:27 node-2 kernel: [    0.467866] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov  5 08:56:27 node-2 kernel: [    0.467948] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.467979] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.468020] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov  5 08:56:27 node-2 kernel: [    0.468039] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.468069] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.468109] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov  5 08:56:27 node-2 kernel: [    0.468125] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.468155] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.468197] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov  5 08:56:27 node-2 kernel: [    0.468214] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.468283] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.468360] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.468435] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov  5 08:56:27 node-2 kernel: [    0.468440] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov  5 08:56:27 node-2 kernel: [    0.468524] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov  5 08:56:27 node-2 kernel: [    0.468670] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov  5 08:56:27 node-2 kernel: [    0.468687] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov  5 08:56:27 node-2 kernel: [    0.468765] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.468819] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov  5 08:56:27 node-2 kernel: [    0.468840] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.468895] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.468939] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov  5 08:56:27 node-2 kernel: [    0.468965] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.469021] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.469063] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov  5 08:56:27 node-2 kernel: [    0.469087] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov  5 08:56:27 node-2 kernel: [    0.469105] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov  5 08:56:27 node-2 kernel: [    0.469182] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.469231] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov  5 08:56:27 node-2 kernel: [    0.469257] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov  5 08:56:27 node-2 kernel: [    0.469503] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov  5 08:56:27 node-2 kernel: [    0.469509] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov  5 08:56:27 node-2 kernel: [    0.469515] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.469521] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.469528] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov  5 08:56:27 node-2 kernel: [    0.469558] pci 0000:01:00.0: supports D1 D2
Nov  5 08:56:27 node-2 kernel: [    0.475401] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  5 08:56:27 node-2 kernel: [    0.475408] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  5 08:56:27 node-2 kernel: [    0.475412] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  5 08:56:27 node-2 kernel: [    0.475535] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.475568] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov  5 08:56:27 node-2 kernel: [    0.483399] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  5 08:56:27 node-2 kernel: [    0.483405] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.483409] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 08:56:27 node-2 kernel: [    0.483499] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.483593] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.483675] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.483724] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  5 08:56:27 node-2 kernel: [    0.483727] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.483729] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 08:56:27 node-2 kernel: [    0.483787] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.483912] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.483968] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  5 08:56:27 node-2 kernel: [    0.483971] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.483973] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 08:56:27 node-2 kernel: [    0.484025] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.484153] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.484194] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.484317] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.484355] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.484474] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.484512] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov  5 08:56:27 node-2 kernel: [    0.484654] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov  5 08:56:27 node-2 kernel: [    0.484695] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  5 08:56:27 node-2 kernel: [    0.484698] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.484700] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 08:56:27 node-2 kernel: [    0.484760] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov  5 08:56:27 node-2 kernel: [    0.484823] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.484875] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.484917] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov  5 08:56:27 node-2 kernel: [    0.484999] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov  5 08:56:27 node-2 kernel: [    0.485104] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  5 08:56:27 node-2 kernel: [    0.485106] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.485108] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  5 08:56:27 node-2 kernel: [    0.485164] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov  5 08:56:27 node-2 kernel: [    0.485219] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.485268] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.485479] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  5 08:56:27 node-2 kernel: [    0.485483] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  5 08:56:27 node-2 kernel: [    0.485566] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov  5 08:56:27 node-2 kernel: [    0.485623] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.485671] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.485884] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  5 08:56:27 node-2 kernel: [    0.485887] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  5 08:56:27 node-2 kernel: [    0.485946] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov  5 08:56:27 node-2 kernel: [    0.486006] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.486058] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov  5 08:56:27 node-2 kernel: [    0.486281] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  5 08:56:27 node-2 kernel: [    0.486285] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  5 08:56:27 node-2 kernel: [    0.486459] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  5 08:56:27 node-2 kernel: [    0.486497] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  5 08:56:27 node-2 kernel: [    0.486571] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov  5 08:56:27 node-2 kernel: [    0.486590] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov  5 08:56:27 node-2 kernel: [    0.486603] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov  5 08:56:27 node-2 kernel: [    0.486616] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov  5 08:56:27 node-2 kernel: [    0.486666] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov  5 08:56:27 node-2 kernel: [    0.491409] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  5 08:56:27 node-2 kernel: [    0.491418] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  5 08:56:27 node-2 kernel: [    0.491471] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov  5 08:56:27 node-2 kernel: [    0.492195] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov  5 08:56:27 node-2 kernel: [    0.492198] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 08:56:27 node-2 kernel: [    0.492322] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  5 08:56:27 node-2 kernel: [    0.492427] PCI host bridge to bus 0000:80
Nov  5 08:56:27 node-2 kernel: [    0.492429] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov  5 08:56:27 node-2 kernel: [    0.492430] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov  5 08:56:27 node-2 kernel: [    0.492432] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov  5 08:56:27 node-2 kernel: [    0.492440] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.492502] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.492569] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov  5 08:56:27 node-2 kernel: [    0.492630] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov  5 08:56:27 node-2 kernel: [    0.492636] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov  5 08:56:27 node-2 kernel: [    0.492707] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov  5 08:56:27 node-2 kernel: [    0.493006] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov  5 08:56:27 node-2 kernel: [    0.493038] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov  5 08:56:27 node-2 kernel: [    0.493067] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov  5 08:56:27 node-2 kernel: [    0.493096] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov  5 08:56:27 node-2 kernel: [    0.493126] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 08:56:27 node-2 kernel: [    0.493156] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 08:56:27 node-2 kernel: [    0.493185] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 08:56:27 node-2 kernel: [    0.493215] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 08:56:27 node-2 kernel: [    0.493299] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov  5 08:56:27 node-2 kernel: [    0.493303] ACPI: \_SB_.UNC1: notify handler is installed
Nov  5 08:56:27 node-2 kernel: [    0.493305] ACPI: \_SB_.UNC0: notify handler is installed
Nov  5 08:56:27 node-2 kernel: [    0.493320] ACPI: \_SB_.PCI0: notify handler is installed
Nov  5 08:56:27 node-2 kernel: [    0.493372] ACPI: \_SB_.PCI1: notify handler is installed
Nov  5 08:56:27 node-2 kernel: [    0.493451] Found 4 acpi root devices
Nov  5 08:56:27 node-2 kernel: [    0.493559] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov  5 08:56:27 node-2 kernel: [    0.493561] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov  5 08:56:27 node-2 kernel: [    0.493562] vgaarb: loaded
Nov  5 08:56:27 node-2 kernel: [    0.493563] vgaarb: bridge control possible 0000:0c:00.0
Nov  5 08:56:27 node-2 kernel: [    0.493680] SCSI subsystem initialized
Nov  5 08:56:27 node-2 kernel: [    0.493745] libata version 3.00 loaded.
Nov  5 08:56:27 node-2 kernel: [    0.493760] ACPI: bus type USB registered
Nov  5 08:56:27 node-2 kernel: [    0.493771] usbcore: registered new interface driver usbfs
Nov  5 08:56:27 node-2 kernel: [    0.493776] usbcore: registered new interface driver hub
Nov  5 08:56:27 node-2 kernel: [    0.493800] usbcore: registered new device driver usb
Nov  5 08:56:27 node-2 kernel: [    0.493967] PCI: Using ACPI for IRQ routing
Nov  5 08:56:27 node-2 kernel: [    0.497554] PCI: pci_cache_line_size set to 64 bytes
Nov  5 08:56:27 node-2 kernel: [    0.497761] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov  5 08:56:27 node-2 kernel: [    0.497762] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Nov  5 08:56:27 node-2 kernel: [    0.497763] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov  5 08:56:27 node-2 kernel: [    0.497827] NetLabel: Initializing
Nov  5 08:56:27 node-2 kernel: [    0.497829] NetLabel:  domain hash size = 128
Nov  5 08:56:27 node-2 kernel: [    0.497830] NetLabel:  protocols = UNLABELED CIPSOv4
Nov  5 08:56:27 node-2 kernel: [    0.497839] NetLabel:  unlabeled traffic allowed by default
Nov  5 08:56:27 node-2 kernel: [    0.497893] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov  5 08:56:27 node-2 kernel: [    0.497897] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov  5 08:56:27 node-2 kernel: [    0.499965] Switched to clocksource hpet
Nov  5 08:56:27 node-2 kernel: [    0.504393] AppArmor: AppArmor Filesystem Enabled
Nov  5 08:56:27 node-2 kernel: [    0.504432] pnp: PnP ACPI init
Nov  5 08:56:27 node-2 kernel: [    0.504444] ACPI: bus type PNP registered
Nov  5 08:56:27 node-2 kernel: [    0.504621] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov  5 08:56:27 node-2 kernel: [    0.504633] pnp 00:01: [dma 4]
Nov  5 08:56:27 node-2 kernel: [    0.504651] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov  5 08:56:27 node-2 kernel: [    0.504685] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov  5 08:56:27 node-2 kernel: [    0.504710] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov  5 08:56:27 node-2 kernel: [    0.504731] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov  5 08:56:27 node-2 kernel: [    0.504778] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov  5 08:56:27 node-2 kernel: [    0.504889] system 00:06: [io  0x0500-0x057f] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504891] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov  5 08:56:27 node-2 kernel: [    0.504893] system 00:06: [io  0x0580-0x059f] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504895] system 00:06: [io  0x0600-0x061f] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504896] system 00:06: [io  0x0880-0x0883] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504898] system 00:06: [io  0x0800-0x081f] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504901] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov  5 08:56:27 node-2 kernel: [    0.504903] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504904] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504906] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504907] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504909] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504910] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov  5 08:56:27 node-2 kernel: [    0.504913] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov  5 08:56:27 node-2 kernel: [    0.505012] pnp 00:07: [dma 0 disabled]
Nov  5 08:56:27 node-2 kernel: [    0.505045] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  5 08:56:27 node-2 kernel: [    0.505127] pnp 00:08: [dma 0 disabled]
Nov  5 08:56:27 node-2 kernel: [    0.505163] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  5 08:56:27 node-2 kernel: [    0.505221] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov  5 08:56:27 node-2 kernel: [    0.505657] pnp: PnP ACPI: found 10 devices
Nov  5 08:56:27 node-2 kernel: [    0.505659] ACPI: bus type PNP unregistered
Nov  5 08:56:27 node-2 kernel: [    0.511636] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  5 08:56:27 node-2 kernel: [    0.511640] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  5 08:56:27 node-2 kernel: [    0.511643] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  5 08:56:27 node-2 kernel: [    0.511648] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  5 08:56:27 node-2 kernel: [    0.511650] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.511665] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511694] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  5 08:56:27 node-2 kernel: [    0.511708] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511738] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  5 08:56:27 node-2 kernel: [    0.511752] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  5 08:56:27 node-2 kernel: [    0.511781] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  5 08:56:27 node-2 kernel: [    0.511796] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  5 08:56:27 node-2 kernel: [    0.511824] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  5 08:56:27 node-2 kernel: [    0.511826] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.511841] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511870] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  5 08:56:27 node-2 kernel: [    0.511872] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.511887] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511918] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  5 08:56:27 node-2 kernel: [    0.511919] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.511922] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511927] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  5 08:56:27 node-2 kernel: [    0.511929] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.511932] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511936] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  5 08:56:27 node-2 kernel: [    0.511946] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  5 08:56:27 node-2 kernel: [    0.511955] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  5 08:56:27 node-2 kernel: [    0.511959] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  5 08:56:27 node-2 kernel: [    0.511966] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov  5 08:56:27 node-2 kernel: [    0.511967] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov  5 08:56:27 node-2 kernel: [    0.511967] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov  5 08:56:27 node-2 kernel: [    0.511968] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov  5 08:56:27 node-2 kernel: [    0.511969] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov  5 08:56:27 node-2 kernel: [    0.511970] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov  5 08:56:27 node-2 kernel: [    0.511971] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov  5 08:56:27 node-2 kernel: [    0.511972] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov  5 08:56:27 node-2 kernel: [    0.511973] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.511974] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511975] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.511976] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511977] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.511978] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511979] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.511980] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511981] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov  5 08:56:27 node-2 kernel: [    0.511982] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511983] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov  5 08:56:27 node-2 kernel: [    0.511985] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov  5 08:56:27 node-2 kernel: [    0.511986] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov  5 08:56:27 node-2 kernel: [    0.511987] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov  5 08:56:27 node-2 kernel: [    0.511990] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov  5 08:56:27 node-2 kernel: [    0.511991] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov  5 08:56:27 node-2 kernel: [    0.512032] NET: Registered protocol family 2
Nov  5 08:56:27 node-2 kernel: [    0.512330] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.512707] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.512875] TCP: Hash tables configured (established 262144 bind 65536)
Nov  5 08:56:27 node-2 kernel: [    0.512920] TCP: reno registered
Nov  5 08:56:27 node-2 kernel: [    0.512954] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.513061] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.513221] NET: Registered protocol family 1
Nov  5 08:56:27 node-2 kernel: [    0.552055] pci 0000:0c:00.0: Video device with shadowed ROM
Nov  5 08:56:27 node-2 kernel: [    0.552069] PCI: CLS 64 bytes, default 64
Nov  5 08:56:27 node-2 kernel: [    0.552154] Trying to unpack rootfs image as initramfs...
Nov  5 08:56:27 node-2 kernel: [    0.773970] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Nov  5 08:56:27 node-2 kernel: [    0.774029] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov  5 08:56:27 node-2 kernel: [    0.774039] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Nov  5 08:56:27 node-2 kernel: [    0.774494] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774500] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774507] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774514] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774522] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774531] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774541] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774548] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774556] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774562] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774569] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774575] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774582] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774589] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774595] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774602] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 08:56:27 node-2 kernel: [    0.774671] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov  5 08:56:27 node-2 kernel: [    0.774674] Scanning for low memory corruption every 60 seconds
Nov  5 08:56:27 node-2 kernel: [    0.774995] Initialise system trusted keyring
Nov  5 08:56:27 node-2 kernel: [    0.775042] audit: initializing netlink socket (disabled)
Nov  5 08:56:27 node-2 kernel: [    0.775054] type=2000 audit(1478336149.716:1): initialized
Nov  5 08:56:27 node-2 kernel: [    0.792804] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov  5 08:56:27 node-2 kernel: [    0.794251] zbud: loaded
Nov  5 08:56:27 node-2 kernel: [    0.794370] VFS: Disk quotas dquot_6.5.2
Nov  5 08:56:27 node-2 kernel: [    0.794411] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov  5 08:56:27 node-2 kernel: [    0.794758] fuse init (API version 7.22)
Nov  5 08:56:27 node-2 kernel: [    0.794808] msgmni has been set to 32768
Nov  5 08:56:27 node-2 kernel: [    0.794853] Key type big_key registered
Nov  5 08:56:27 node-2 kernel: [    0.795399] Key type asymmetric registered
Nov  5 08:56:27 node-2 kernel: [    0.795401] Asymmetric key parser 'x509' registered
Nov  5 08:56:27 node-2 kernel: [    0.795424] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov  5 08:56:27 node-2 kernel: [    0.795488] io scheduler noop registered
Nov  5 08:56:27 node-2 kernel: [    0.795489] io scheduler deadline registered (default)
Nov  5 08:56:27 node-2 kernel: [    0.795508] io scheduler cfq registered
Nov  5 08:56:27 node-2 kernel: [    0.795948] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    0.796120] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    0.796242] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    0.796376] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    0.796501] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    0.796592] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    0.797003] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov  5 08:56:27 node-2 kernel: [    0.797061] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov  5 08:56:27 node-2 kernel: [    0.797078] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov  5 08:56:27 node-2 kernel: [    0.797092] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797094] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797097] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov  5 08:56:27 node-2 kernel: [    0.797102] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797103] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797105] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797106] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797108] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797109] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797111] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797112] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797113] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797115] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797116] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797118] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797120] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov  5 08:56:27 node-2 kernel: [    0.797133] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797136] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov  5 08:56:27 node-2 kernel: [    0.797147] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797150] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov  5 08:56:27 node-2 kernel: [    0.797161] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797163] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov  5 08:56:27 node-2 kernel: [    0.797166] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov  5 08:56:27 node-2 kernel: [    0.797195] ioapic: probe of 0000:00:05.4 failed with error -22
Nov  5 08:56:27 node-2 kernel: [    0.797200] ioapic: probe of 0000:80:05.4 failed with error -22
Nov  5 08:56:27 node-2 kernel: [    0.797204] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov  5 08:56:27 node-2 kernel: [    0.797212] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov  5 08:56:27 node-2 kernel: [    0.797250] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov  5 08:56:27 node-2 kernel: [    0.797251] vesafb: scrolling: redraw
Nov  5 08:56:27 node-2 kernel: [    0.797253] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov  5 08:56:27 node-2 kernel: [    0.817526] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov  5 08:56:27 node-2 kernel: [    0.826025] Console: switching to colour frame buffer device 80x30
Nov  5 08:56:27 node-2 kernel: [    0.834696] fb0: VESA VGA frame buffer device
Nov  5 08:56:27 node-2 kernel: [    0.834896] intel_idle: MWAIT substates: 0x2120
Nov  5 08:56:27 node-2 kernel: [    0.834898] intel_idle: v0.4 model 0x3F
Nov  5 08:56:27 node-2 kernel: [    0.834898] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov  5 08:56:27 node-2 kernel: [    0.835133] ipmi message handler version 39.2
Nov  5 08:56:27 node-2 kernel: [    0.835415] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov  5 08:56:27 node-2 kernel: [    0.835856] ACPI: AC Adapter [P111] (on-line)
Nov  5 08:56:27 node-2 kernel: [    0.841092] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov  5 08:56:27 node-2 kernel: [    0.852101] ACPI: Power Button [PWRB]
Nov  5 08:56:27 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov  5 08:56:27 node-2 kernel: [    0.857865] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov  5 08:56:27 node-2 kernel: [    0.869484] ACPI: Power Button [PWRF]
Nov  5 08:56:27 node-2 kernel: [    0.889515] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov  5 08:56:27 node-2 kernel: [    0.901162] pstore: Registered erst as persistent store backend
Nov  5 08:56:27 node-2 kernel: [    0.907385] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov  5 08:56:27 node-2 kernel: [    0.919327] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov  5 08:56:27 node-2 kernel: [    0.946083] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov  5 08:56:27 node-2 kernel: [    0.979357] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov  5 08:56:27 node-2 kernel: [    0.993457] Linux agpgart interface v0.103
Nov  5 08:56:27 node-2 kernel: [    1.001128] brd: module loaded
Nov  5 08:56:27 node-2 kernel: [    1.008185] loop: module loaded
Nov  5 08:56:27 node-2 kernel: [    1.014894] libphy: Fixed MDIO Bus: probed
Nov  5 08:56:27 node-2 kernel: [    1.021362] tun: Universal TUN/TAP device driver, 1.6
Nov  5 08:56:27 node-2 kernel: [    1.027830] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov  5 08:56:27 node-2 kernel: [    1.034341] PPP generic driver version 2.4.2
Nov  5 08:56:27 node-2 kernel: [    1.040730] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov  5 08:56:27 node-2 kernel: [    1.047154] ehci-pci: EHCI PCI platform driver
Nov  5 08:56:27 node-2 kernel: [    1.053675] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov  5 08:56:27 node-2 kernel: [    1.060089] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov  5 08:56:27 node-2 kernel: [    1.072620] ehci-pci 0000:00:1a.0: debug port 2
Nov  5 08:56:27 node-2 kernel: [    1.082815] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov  5 08:56:27 node-2 kernel: [    1.082834] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov  5 08:56:27 node-2 kernel: [    1.099450] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov  5 08:56:27 node-2 kernel: [    1.105521] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov  5 08:56:27 node-2 kernel: [    1.111694] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  5 08:56:27 node-2 kernel: [    1.123783] usb usb1: Product: EHCI Host Controller
Nov  5 08:56:27 node-2 kernel: [    1.129880] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  5 08:56:27 node-2 kernel: [    1.136021] usb usb1: SerialNumber: 0000:00:1a.0
Nov  5 08:56:27 node-2 kernel: [    1.142072] hub 1-0:1.0: USB hub found
Nov  5 08:56:27 node-2 kernel: [    1.147854] hub 1-0:1.0: 2 ports detected
Nov  5 08:56:27 node-2 kernel: [    1.153689] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov  5 08:56:27 node-2 kernel: [    1.159282] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov  5 08:56:27 node-2 kernel: [    1.170240] ehci-pci 0000:00:1d.0: debug port 2
Nov  5 08:56:27 node-2 kernel: [    1.179561] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov  5 08:56:27 node-2 kernel: [    1.179564] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov  5 08:56:27 node-2 kernel: [    1.195368] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov  5 08:56:27 node-2 kernel: [    1.200583] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov  5 08:56:27 node-2 kernel: [    1.205902] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  5 08:56:27 node-2 kernel: [    1.216498] usb usb2: Product: EHCI Host Controller
Nov  5 08:56:27 node-2 kernel: [    1.221986] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  5 08:56:27 node-2 kernel: [    1.227628] usb usb2: SerialNumber: 0000:00:1d.0
Nov  5 08:56:27 node-2 kernel: [    1.233165] hub 2-0:1.0: USB hub found
Nov  5 08:56:27 node-2 kernel: [    1.238536] hub 2-0:1.0: 2 ports detected
Nov  5 08:56:27 node-2 kernel: [    1.243873] ehci-platform: EHCI generic platform driver
Nov  5 08:56:27 node-2 kernel: [    1.249133] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov  5 08:56:27 node-2 kernel: [    1.254471] ohci-pci: OHCI PCI platform driver
Nov  5 08:56:27 node-2 kernel: [    1.259782] ohci-platform: OHCI generic platform driver
Nov  5 08:56:27 node-2 kernel: [    1.264996] uhci_hcd: USB Universal Host Controller Interface driver
Nov  5 08:56:27 node-2 kernel: [    1.270359] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov  5 08:56:27 node-2 kernel: [    1.463148] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov  5 08:56:27 node-2 kernel: [    1.635367] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov  5 08:56:27 node-2 kernel: [    1.640917] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  5 08:56:27 node-2 kernel: [    1.646635] hub 1-1:1.0: USB hub found
Nov  5 08:56:27 node-2 kernel: [    1.652104] hub 1-1:1.0: 6 ports detected
Nov  5 08:56:27 node-2 kernel: [    1.766882] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov  5 08:56:27 node-2 kernel: [    1.794855] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov  5 08:56:27 node-2 kernel: [    2.035028] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov  5 08:56:27 node-2 kernel: [    2.040574] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  5 08:56:27 node-2 kernel: [    2.046420] hub 2-1:1.0: USB hub found
Nov  5 08:56:27 node-2 kernel: [    2.052139] hub 2-1:1.0: 8 ports detected
Nov  5 08:56:27 node-2 kernel: [    2.311951] i8042: No controller found
Nov  5 08:56:27 node-2 kernel: [    2.317372] mousedev: PS/2 mouse device common for all mice
Nov  5 08:56:27 node-2 kernel: [    2.322909] rtc_cmos 00:02: RTC can wake from S4
Nov  5 08:56:27 node-2 kernel: [    2.328513] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov  5 08:56:27 node-2 kernel: [    2.330477] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov  5 08:56:27 node-2 kernel: [    2.339683] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov  5 08:56:27 node-2 kernel: [    2.350817] device-mapper: uevent: version 1.0.3
Nov  5 08:56:27 node-2 kernel: [    2.356467] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov  5 08:56:27 node-2 kernel: [    2.367730] ledtrig-cpu: registered to indicate activity on CPUs
Nov  5 08:56:27 node-2 kernel: [    2.373664] TCP: cubic registered
Nov  5 08:56:27 node-2 kernel: [    2.379561] NET: Registered protocol family 10
Nov  5 08:56:27 node-2 kernel: [    2.385552] NET: Registered protocol family 17
Nov  5 08:56:27 node-2 kernel: [    2.391241] Key type dns_resolver registered
Nov  5 08:56:27 node-2 kernel: [    2.397212] Loading compiled-in X.509 certificates
Nov  5 08:56:27 node-2 kernel: [    2.403388] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov  5 08:56:27 node-2 kernel: [    2.414800] registered taskstats version 1
Nov  5 08:56:27 node-2 kernel: [    2.422760] Key type trusted registered
Nov  5 08:56:27 node-2 kernel: [    2.430697] Key type encrypted registered
Nov  5 08:56:27 node-2 kernel: [    2.436157] AppArmor: AppArmor sha1 policy hashing enabled
Nov  5 08:56:27 node-2 kernel: [    2.441643] IMA: No TPM chip found, activating TPM-bypass!
Nov  5 08:56:27 node-2 kernel: [    2.447811] regulator-dummy: disabling
Nov  5 08:56:27 node-2 kernel: [    2.453367]   Magic number: 8:144:927
Nov  5 08:56:27 node-2 kernel: [    2.458808] pci 0000:ff:0c.2: hash matches
Nov  5 08:56:27 node-2 kernel: [    2.462611] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov  5 08:56:27 node-2 kernel: [    2.462612] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  5 08:56:27 node-2 kernel: [    2.462613] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov  5 08:56:27 node-2 kernel: [    2.462614] usb 2-1.4: Manufacturer: Avocent
Nov  5 08:56:27 node-2 kernel: [    2.462614] usb 2-1.4: SerialNumber: 20111102-00000001
Nov  5 08:56:27 node-2 kernel: [    2.497358] rtc_cmos 00:02: setting system clock to 2016-11-05 08:55:51 UTC (1478336151)
Nov  5 08:56:27 node-2 kernel: [    2.510040] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov  5 08:56:27 node-2 kernel: [    2.515710] EDD information not available.
Nov  5 08:56:27 node-2 kernel: [    2.521259] PM: Hibernation image not present or could not be loaded.
Nov  5 08:56:27 node-2 kernel: [    2.522106] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov  5 08:56:27 node-2 kernel: [    2.533345] Write protecting the kernel read-only data: 12288k
Nov  5 08:56:27 node-2 kernel: [    2.539497] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov  5 08:56:27 node-2 kernel: [    2.551857] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov  5 08:56:27 node-2 kernel: [    2.584852] device-mapper: multipath: version 1.6.0 loaded
Nov  5 08:56:27 node-2 kernel: [    2.593018] systemd-udevd[215]: starting version 204
Nov  5 08:56:27 node-2 kernel: [    2.614217] md: linear personality registered for level -1
Nov  5 08:56:27 node-2 kernel: [    2.627936] md: multipath personality registered for level -4
Nov  5 08:56:27 node-2 kernel: [    2.635982] md: raid0 personality registered for level 0
Nov  5 08:56:27 node-2 kernel: [    2.644232] md: raid1 personality registered for level 1
Nov  5 08:56:27 node-2 kernel: [    2.652849] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov  5 08:56:27 node-2 kernel: [    2.659110] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov  5 08:56:27 node-2 kernel: [    2.665445] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov  5 08:56:27 node-2 kernel: [    2.671987] hidraw: raw HID events driver (C) Jiri Kosina
Nov  5 08:56:27 node-2 kernel: [    2.672223] megasas: FW now in Ready state
Nov  5 08:56:27 node-2 kernel: [    2.672304] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672344] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672385] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672422] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672459] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672498] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672538] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672578] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672616] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672645] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672678] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672718] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672756] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672792] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672831] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.672871] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.673033] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov  5 08:56:27 node-2 kernel: [    2.680755] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Nov  5 08:56:27 node-2 kernel: [    2.680756] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Nov  5 08:56:27 node-2 kernel: [    2.680757] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  5 08:56:27 node-2 kernel: [    2.680859] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.680910] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.680953] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.680997] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.681071] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.692633] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Nov  5 08:56:27 node-2 kernel: [    2.692635] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Nov  5 08:56:27 node-2 kernel: [    2.692636] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov  5 08:56:27 node-2 kernel: [    2.692713] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.692760] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.692797] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.692844] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.692880] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.692920] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.693014] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.704136] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Nov  5 08:56:27 node-2 kernel: [    2.704137] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Nov  5 08:56:27 node-2 kernel: [    2.704138] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  5 08:56:27 node-2 kernel: [    2.704285] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.704324] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.704363] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.704403] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.704491] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.715945] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Nov  5 08:56:27 node-2 kernel: [    2.715946] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Nov  5 08:56:27 node-2 kernel: [    2.715947] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  5 08:56:27 node-2 kernel: [    2.716016] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.716067] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.716105] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.716141] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.716206] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  5 08:56:27 node-2 kernel: [    2.726238] raid6: sse2x1    1200 MB/s
Nov  5 08:56:27 node-2 kernel: [    2.794217] raid6: sse2x2     863 MB/s
Nov  5 08:56:27 node-2 kernel: [    2.862514] raid6: sse2x4    1162 MB/s
Nov  5 08:56:27 node-2 kernel: [    2.929910] raid6: avx2x1    5707 MB/s
Nov  5 08:56:27 node-2 kernel: [    3.001852] raid6: avx2x2   18870 MB/s
Nov  5 08:56:27 node-2 kernel: [    3.073792] raid6: avx2x4   21400 MB/s
Nov  5 08:56:27 node-2 kernel: [    3.079593] raid6: using algorithm avx2x4 (21400 MB/s)
Nov  5 08:56:27 node-2 kernel: [    3.085534] raid6: using avx2x2 recovery algorithm
Nov  5 08:56:27 node-2 kernel: [    3.091346] megasas:IOC Init cmd success
Nov  5 08:56:27 node-2 kernel: [    3.091346] Switched to clocksource tsc
Nov  5 08:56:27 node-2 kernel: [    3.103384] xor: automatically using best checksumming function:
Nov  5 08:56:27 node-2 kernel: [    3.110667] usbcore: registered new interface driver usbhid
Nov  5 08:56:27 node-2 kernel: [    3.116111] usbhid: USB HID core driver
Nov  5 08:56:27 node-2 kernel: [    3.121404] megasas: INIT adapter done
Nov  5 08:56:27 node-2 kernel: [    3.127670] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Nov  5 08:56:27 node-2 kernel: [    3.138637] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Nov  5 08:56:27 node-2 kernel: [    3.149699]    avx       : 35783.000 MB/sec
Nov  5 08:56:27 node-2 kernel: [    3.149706] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Nov  5 08:56:27 node-2 kernel: [    3.149762] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Nov  5 08:56:27 node-2 kernel: [    3.149815] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Nov  5 08:56:27 node-2 kernel: [    3.149859] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Nov  5 08:56:27 node-2 kernel: [    3.198367] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov  5 08:56:27 node-2 kernel: [    3.201025] scsi0 : LSI SAS based MegaRAID driver
Nov  5 08:56:27 node-2 kernel: [    3.208810] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  5 08:56:27 node-2 kernel: [    3.225764] async_tx: api initialized (async)
Nov  5 08:56:27 node-2 kernel: [    3.235213] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  5 08:56:27 node-2 kernel: [    3.248234] md: raid6 personality registered for level 6
Nov  5 08:56:27 node-2 kernel: [    3.254988] md: raid5 personality registered for level 5
Nov  5 08:56:27 node-2 kernel: [    3.261647] md: raid4 personality registered for level 4
Nov  5 08:56:27 node-2 kernel: [    3.269661] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov  5 08:56:27 node-2 kernel: [    3.276445] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov  5 08:56:27 node-2 kernel: [    3.289881] md: raid10 personality registered for level 10
Nov  5 08:56:27 node-2 kernel: [    3.290106] sd 0:2:0:0: [sda] Write Protect is off
Nov  5 08:56:27 node-2 kernel: [    3.290132] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov  5 08:56:27 node-2 kernel: [    3.290528] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov  5 08:56:27 node-2 kernel: [    3.319792]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Nov  5 08:56:27 node-2 kernel: [    3.323458] sd 0:2:0:0: [sda] Attached SCSI disk
Nov  5 08:56:27 node-2 kernel: [    3.377170] multipathd (361): /proc/361/oom_adj is deprecated, please use /proc/361/oom_score_adj instead.
Nov  5 08:56:27 node-2 kernel: [    3.457038] random: lvm urandom read with 28 bits of entropy available
Nov  5 08:56:27 node-2 kernel: [    3.653188] bio: create slab <bio-1> at 1
Nov  5 08:56:27 node-2 kernel: [    4.479394] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Nov  5 08:56:27 node-2 kernel: [    5.206001] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Nov  5 08:56:27 node-2 kernel: [    5.256754] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov  5 08:56:27 node-2 kernel: [    5.387255] random: nonblocking pool is initialized
Nov  5 08:56:27 node-2 kernel: [    5.429646] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov  5 08:56:27 node-2 kernel: [    5.471550] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov  5 08:56:27 node-2 kernel: [    5.565338] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov  5 08:56:27 node-2 kernel: [    5.779571] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov  5 08:56:27 node-2 kernel: [    5.811251] XFS (dm-1): Mounting Filesystem
Nov  5 08:56:27 node-2 kernel: [    6.111463] XFS (dm-1): Ending clean mount
Nov  5 08:56:27 node-2 kernel: [    6.163920] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov  5 08:56:27 node-2 kernel: [    6.204542] XFS (dm-2): Mounting Filesystem
Nov  5 08:56:27 node-2 kernel: [    6.334616] XFS (dm-2): Ending clean mount
Nov  5 08:56:27 node-2 kernel: [    6.479744] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Nov  5 08:56:27 node-2 kernel: [    8.340057] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  5 08:56:27 node-2 kernel: [    8.354858] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  5 08:56:27 node-2 kernel: [    8.526671] systemd-udevd[800]: starting version 204
Nov  5 08:56:27 node-2 kernel: [    8.800310] IPMI System Interface driver.
Nov  5 08:56:27 node-2 kernel: [    8.800425] ipmi_si: probing via ACPI
Nov  5 08:56:27 node-2 kernel: [    8.800441] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov  5 08:56:27 node-2 kernel: [    8.800442] ipmi_si: Adding ACPI-specified kcs state machine
Nov  5 08:56:27 node-2 kernel: [    8.800455] ipmi_si: probing via SMBIOS
Nov  5 08:56:27 node-2 kernel: [    8.800456] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov  5 08:56:27 node-2 kernel: [    8.800457] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov  5 08:56:27 node-2 kernel: [    8.800460] ipmi_si: probing via SPMI
Nov  5 08:56:27 node-2 kernel: [    8.800461] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov  5 08:56:27 node-2 kernel: [    8.800462] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov  5 08:56:27 node-2 kernel: [    8.800464] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov  5 08:56:27 node-2 kernel: [    8.801983] wmi: Mapper loaded
Nov  5 08:56:27 node-2 kernel: [    8.804412] power_meter ACPI000D:00: Found ACPI power meter.
Nov  5 08:56:27 node-2 kernel: [    8.804442] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov  5 08:56:27 node-2 kernel: [    8.812391] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov  5 08:56:27 node-2 kernel: [    8.812396] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  5 08:56:27 node-2 kernel: [    8.812398] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov  5 08:56:27 node-2 kernel: [    8.812400] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  5 08:56:27 node-2 kernel: [    8.812413] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov  5 08:56:27 node-2 kernel: [    8.853882] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov  5 08:56:27 node-2 kernel: [    8.930404] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov  5 08:56:27 node-2 kernel: [    8.930409] ipmi_si 00:09: IPMI kcs interface initialized
Nov  5 08:56:27 node-2 kernel: [    8.941925] systemd-udevd[846]: renamed network interface eth2 to enp8s0
Nov  5 08:56:27 node-2 kernel: [    8.961756] systemd-udevd[818]: renamed network interface eth0 to enp6s0
Nov  5 08:56:27 node-2 kernel: [    9.001263] systemd-udevd[828]: renamed network interface eth1 to enp7s0
Nov  5 08:56:27 node-2 kernel: [    9.021143] systemd-udevd[820]: renamed network interface eth3 to enp9s0
Nov  5 08:56:27 node-2 kernel: [    9.340709] type=1400 audit(1478336158.348:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1086 comm="apparmor_parser"
Nov  5 08:56:27 node-2 kernel: [    9.340874] type=1400 audit(1478336158.348:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1086 comm="apparmor_parser"
Nov  5 08:56:27 node-2 kernel: [    9.341000] type=1400 audit(1478336158.348:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1086 comm="apparmor_parser"
Nov  5 08:56:27 node-2 kernel: [    9.354556] type=1400 audit(1478336158.360:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1088 comm="apparmor_parser"
Nov  5 08:56:27 node-2 kernel: [    9.354709] type=1400 audit(1478336158.360:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1088 comm="apparmor_parser"
Nov  5 08:56:27 node-2 kernel: [    9.354826] type=1400 audit(1478336158.360:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1088 comm="apparmor_parser"
Nov  5 08:56:27 node-2 kernel: [    9.368452] type=1400 audit(1478336158.376:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1084 comm="apparmor_parser"
Nov  5 08:56:27 node-2 kernel: [    9.368677] type=1400 audit(1478336158.376:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1084 comm="apparmor_parser"
Nov  5 08:56:27 node-2 kernel: [    9.368874] type=1400 audit(1478336158.376:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1084 comm="apparmor_parser"
Nov  5 08:56:27 node-2 kernel: [    9.370533] type=1400 audit(1478336158.376:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1085 comm="apparmor_parser"
Nov  5 08:56:27 node-2 kernel: [    9.973253] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  5 08:56:27 node-2 kernel: [    9.982146] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  5 08:56:27 node-2 kernel: [   10.256926] enic 0000:06:00.0 enp6s0: Link UP
Nov  5 08:56:27 node-2 kernel: [   10.257554] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov  5 08:56:27 node-2 kernel: [   10.257565] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov  5 08:56:27 node-2 kernel: [   20.563634] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov  5 08:56:29 node-2 failsafe: Failsafe of 120 seconds reached.
Nov  5 08:56:29 node-2 kernel: [   39.624561] init: failsafe main process (8450) killed by TERM signal
Nov  5 08:56:29 node-2 dbus[8500]: [system] AppArmor D-Bus mediation is enabled
Nov  5 08:56:29 node-2 kernel: [   39.838082] audit_printk_skb: 30 callbacks suppressed
Nov  5 08:56:29 node-2 kernel: [   39.838087] type=1400 audit(1478336189.397:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8577 comm="apparmor_parser"
Nov  5 08:56:29 node-2 kernel: [   39.839230] type=1400 audit(1478336189.397:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8576 comm="apparmor_parser"
Nov  5 08:56:29 node-2 kernel: [   39.839235] type=1400 audit(1478336189.397:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8576 comm="apparmor_parser"
Nov  5 08:56:29 node-2 kernel: [   39.839239] type=1400 audit(1478336189.397:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8576 comm="apparmor_parser"
Nov  5 08:56:29 node-2 kernel: [   39.839476] type=1400 audit(1478336189.397:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8576 comm="apparmor_parser"
Nov  5 08:56:29 node-2 kernel: [   39.839478] type=1400 audit(1478336189.397:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8576 comm="apparmor_parser"
Nov  5 08:56:29 node-2 kernel: [   39.839609] type=1400 audit(1478336189.397:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8576 comm="apparmor_parser"
Nov  5 08:56:29 node-2 kernel: [   39.932346] type=1400 audit(1478336189.489:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8579 comm="apparmor_parser"
Nov  5 08:56:29 node-2 anacron[8644]: Anacron 2.3 started on 2016-11-05
Nov  5 08:56:29 node-2 anacron[8644]: Will run job `cron.daily' in 5 min.
Nov  5 08:56:29 node-2 anacron[8644]: Will run job `cron.weekly' in 10 min.
Nov  5 08:56:29 node-2 anacron[8644]: Will run job `cron.monthly' in 15 min.
Nov  5 08:56:29 node-2 anacron[8644]: Jobs will be executed sequentially
Nov  5 08:56:29 node-2 multipathd: path checkers start up
Nov  5 08:56:29 node-2 cron[8609]: (CRON) INFO (pidfile fd = 3)
Nov  5 08:56:29 node-2 cron[8685]: (CRON) STARTUP (fork ok)
Nov  5 08:56:29 node-2 cron[8685]: (CRON) INFO (Running @reboot jobs)
Nov  5 08:56:30 node-2 postfix/master[8788]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov  5 08:56:33 node-2 puppet-agent[9087]: Reopening log files
Nov  5 08:56:34 node-2 puppet-agent[9087]: Could not request certificate: Connection refused - connect(2)
Nov  5 08:56:58 node-2 kernel: [   69.542254] init: plymouth-upstart-bridge main process ended, respawning
Nov  5 08:56:59 node-2 puppet-agent[9087]: Could not run: SIGTERM
Nov  5 08:56:59 node-2 kernel: [   69.910277] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov  5 08:56:59 node-2 ec2: 
Nov  5 08:56:59 node-2 ec2: #############################################################
Nov  5 08:56:59 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov  5 08:56:59 node-2 ec2: 1024 8e:3c:ff:d9:50:b6:24:6d:7e:fd:6e:b3:d6:7e:dc:7b  root@node-2.domain.tld (DSA)
Nov  5 08:56:59 node-2 ec2: 256 df:03:cc:bc:49:b1:8c:52:1c:3c:4f:a7:30:a6:d4:8f  root@node-2.domain.tld (ECDSA)
Nov  5 08:56:59 node-2 ec2: 256 83:d8:af:5a:38:9d:a5:a2:52:0f:61:20:99:8e:51:5e  root@node-2.domain.tld (ED25519)
Nov  5 08:56:59 node-2 ec2: 2048 57:4c:1c:2c:7f:e8:c0:e2:9f:43:18:f3:2a:52:9b:af  root@node-2.domain.tld (RSA)
Nov  5 08:56:59 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov  5 08:56:59 node-2 ec2: #############################################################
Nov  5 08:57:01 node-2 CRON[9494]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  5 08:57:03 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  5 08:57:03 node-2 nailgun-agent: I, [2016-11-05T08:57:03.604119 #9497]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  5 08:57:16 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  5 08:57:16 node-2 nailgun-agent: I, [2016-11-05T08:57:16.340223 #9497]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Nov  5 08:57:20 node-2 puppet-user[9848]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov  5 08:57:20 node-2 puppet-user[9848]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Nov  5 08:57:22 node-2 puppet-user[9848]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov  5 08:57:22 node-2 puppet-user[9848]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov  5 08:57:22 node-2 puppet-user[9848]: Finished catalog run in 1.58 seconds
Nov  5 08:57:23 node-2 multipathd: uevent trigger error
Nov  5 08:57:24 node-2 puppet-user[10308]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  5 08:57:24 node-2 puppet-user[10308]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Nov  5 08:57:24 node-2 puppet-user[10308]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov  5 08:57:24 node-2 puppet-user[10308]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov  5 08:57:24 node-2 puppet-user[10308]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Nov  5 08:57:24 node-2 puppet-user[10308]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov  5 08:57:24 node-2 puppet-user[10308]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov  5 08:57:24 node-2 puppet-user[10308]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov  5 08:57:24 node-2 puppet-user[10308]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov  5 08:57:24 node-2 puppet-user[10308]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov  5 08:57:24 node-2 puppet-user[10308]: Finished catalog run in 0.07 seconds
Nov  5 08:57:25 node-2 puppet-user[10771]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov  5 08:57:25 node-2 puppet-user[10771]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Nov  5 08:57:25 node-2 puppet-user[10771]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov  5 08:57:25 node-2 puppet-user[10771]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov  5 08:57:25 node-2 puppet-user[10771]: Finished catalog run in 0.03 seconds
Nov  5 08:57:27 node-2 puppet-user[11235]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov  5 08:57:27 node-2 puppet-user[11235]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Nov  5 08:57:27 node-2 puppet-user[11235]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov  5 08:57:27 node-2 puppet-user[11235]: Finished catalog run in 0.04 seconds
Nov  5 08:57:29 node-2 puppet-user[11692]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov  5 08:57:29 node-2 puppet-user[11692]: Compiled catalog for node-2.domain.tld in environment production in 0.19 seconds
Nov  5 08:57:29 node-2 puppet-user[11692]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov  5 08:57:31 node-2 puppet-user[11692]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Nov  5 08:57:31 node-2 puppet-user[11692]: Finished catalog run in 2.05 seconds
Nov  5 08:57:33 node-2 puppet-user[12214]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov  5 08:57:33 node-2 puppet-user[12214]: Compiled catalog for node-2.domain.tld in environment production in 0.29 seconds
Nov  5 08:57:33 node-2 puppet-user[12214]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov  5 08:57:33 node-2 puppet-user[12214]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Nov  5 08:57:33 node-2 puppet-user[12214]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov  5 08:57:33 node-2 puppet-user[12214]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov  5 08:57:33 node-2 puppet-user[12214]: Finished catalog run in 0.29 seconds
Nov  5 08:57:35 node-2 puppet-user[12699]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov  5 08:57:36 node-2 puppet-user[12699]: Compiled catalog for node-2.domain.tld in environment production in 0.20 seconds
Nov  5 08:57:36 node-2 puppet-user[12699]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov  5 08:57:36 node-2 kernel: [  106.861816] nr_pdflush_threads exported in /proc is scheduled for removal
Nov  5 08:57:36 node-2 kernel: [  106.861870] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Nov  5 08:57:36 node-2 puppet-user[12699]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Nov  5 08:57:36 node-2 puppet-user[12699]: Finished catalog run in 0.08 seconds
Nov  5 08:57:38 node-2 puppet-user[13163]: (Scope(Class[main])) MODULAR: sync_time
Nov  5 08:57:38 node-2 puppet-user[13163]: Compiled catalog for node-2.domain.tld in environment production in 0.04 seconds
Nov  5 08:57:38 node-2 ntpdate[13581]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov  5 08:57:44 node-2 ntpdate[13581]: adjust time server 10.20.0.2 offset 0.002796 sec
Nov  5 08:57:44 node-2 puppet-user[13163]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov  5 08:57:44 node-2 puppet-user[13163]: Finished catalog run in 6.19 seconds
Nov  5 08:57:51 node-2 puppet-user[13753]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  5 08:57:51 node-2 puppet-user[13753]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Nov  5 08:57:52 node-2 puppet-user[13753]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov  5 08:57:52 node-2 puppet-user[13753]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Nov  5 08:57:52 node-2 puppet-user[13753]: Finished catalog run in 0.07 seconds
Nov  5 08:57:53 node-2 puppet-user[14199]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov  5 08:57:54 node-2 puppet-user[14199]: Compiled catalog for node-2.domain.tld in environment production in 0.68 seconds
Nov  5 08:57:54 node-2 puppet-user[14199]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Nov  5 08:57:54 node-2 puppet-user[14199]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Nov  5 08:57:54 node-2 puppet-user[14199]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Nov  5 08:57:54 node-2 puppet-user[14199]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Nov  5 08:57:54 node-2 puppet-user[14199]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov  5 08:57:54 node-2 puppet-user[14199]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Nov  5 08:57:54 node-2 puppet-user[14199]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov  5 08:57:54 node-2 puppet-user[14199]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Nov  5 08:57:54 node-2 puppet-user[14199]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Nov  5 08:57:54 node-2 puppet-user[14199]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Nov  5 08:57:55 node-2 puppet-user[14199]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov  5 08:57:55 node-2 puppet-user[14199]: Finished catalog run in 0.94 seconds
Nov  5 08:57:58 node-2 puppet-user[14705]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov  5 08:57:58 node-2 puppet-user[14705]: Compiled catalog for node-2.domain.tld in environment production in 0.15 seconds
Nov  5 08:58:01 node-2 CRON[15706]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  5 08:58:02 node-2 puppet-user[14705]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov  5 08:58:14 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  5 08:58:14 node-2 nailgun-agent: I, [2016-11-05T08:58:14.521050 #15713]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  5 08:58:27 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  5 08:58:27 node-2 nailgun-agent: I, [2016-11-05T08:58:27.792419 #15713]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Nov  5 08:58:34 node-2 puppet-user[14705]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov  5 08:58:35 node-2 puppet-user[14705]: Finished catalog run in 36.65 seconds
Nov  5 08:58:36 node-2 puppet-user[17865]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov  5 08:58:37 node-2 puppet-user[17865]: Compiled catalog for node-2.domain.tld in environment production in 0.54 seconds
Nov  5 08:58:37 node-2 puppet-user[17865]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov  5 08:58:37 node-2 puppet-user[17865]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov  5 08:58:37 node-2 puppet-user[17865]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov  5 08:58:37 node-2 puppet-user[17865]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov  5 08:58:37 node-2 puppet-user[17865]: Finished catalog run in 0.10 seconds
Nov  5 08:58:39 node-2 puppet-user[18335]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov  5 08:58:40 node-2 puppet-user[18335]: Compiled catalog for node-2.domain.tld in environment production in 0.90 seconds
Nov  5 08:58:40 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov  5 08:58:40 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov  5 08:58:40 node-2 crontab[18758]: (root) LIST (root)
Nov  5 08:58:40 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov  5 08:58:40 node-2 crontab[18759]: (root) REPLACE (root)
Nov  5 08:58:41 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov  5 08:58:42 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov  5 08:58:43 node-2 puppet-user[18335]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Nov  5 08:58:43 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8423" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 08:58:43 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov  5 08:58:45 node-2 multipathd: uevent trigger error
<27>Nov  5 08:58:45 node-2 multipathd: uevent trigger error
<27>Nov  5 08:58:45 node-2 multipathd: uevent trigger error
<27>Nov  5 08:58:45 node-2 multipathd: uevent trigger error
<27>Nov  5 08:58:45 node-2 multipathd: uevent trigger error
<27>Nov  5 08:58:59 node-2 multipathd: uevent trigger error
<27>Nov  5 08:58:59 node-2 multipathd: uevent trigger error
<27>Nov  5 08:58:59 node-2 multipathd: uevent trigger error
<27>Nov  5 08:58:59 node-2 multipathd: uevent trigger error
<27>Nov  5 08:58:59 node-2 multipathd: uevent trigger error
<27>Nov  5 08:59:49 node-2 multipathd: uevent trigger error
<27>Nov  5 08:59:49 node-2 multipathd: uevent trigger error
<27>Nov  5 08:59:49 node-2 multipathd: uevent trigger error
<27>Nov  5 08:59:49 node-2 multipathd: uevent trigger error
<27>Nov  5 08:59:49 node-2 multipathd: uevent trigger error
<27>Nov  5 08:59:49 node-2 multipathd: uevent trigger error
<27>Nov  5 09:00:30 node-2 ntpdate[1693]: no servers can be used, exiting
<27>Nov  5 09:00:30 node-2 ntpdate[1876]: no servers can be used, exiting
<27>Nov  5 09:01:02 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:02 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:02 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:02 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:02 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:02 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:05 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:05 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:05 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:05 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:05 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:17 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:17 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:17 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:17 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:17 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:01:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:27 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:27 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:27 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:27 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:27 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:29 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 09:02:29 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 09:02:35 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 09:02:35 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 09:02:41 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 09:02:46 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 09:02:46 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 09:02:53 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:53 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:53 node-2 multipathd: uevent trigger error
<27>Nov  5 09:02:53 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:16 node-2 multipathd: uevent trigger error
<129>Nov  5 09:03:18 node-2 haproxy[23560]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:19 node-2 haproxy[23567]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:20 node-2 haproxy[23567]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:20 node-2 haproxy[23567]: proxy mysqld has no server available!
<27>Nov  5 09:03:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:25 node-2 multipathd: uevent trigger error
<129>Nov  5 09:03:28 node-2 haproxy[26160]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:28 node-2 haproxy[26160]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:28 node-2 haproxy[26160]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:28 node-2 haproxy[26160]: proxy mysqld has no server available!
<129>Nov  5 09:03:29 node-2 haproxy[26164]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:29 node-2 haproxy[26164]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:29 node-2 haproxy[26164]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:29 node-2 haproxy[26164]: proxy object-storage has no server available!
<27>Nov  5 09:03:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:31 node-2 multipathd: uevent trigger error
<129>Nov  5 09:03:33 node-2 haproxy[27651]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:33 node-2 haproxy[27651]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:33 node-2 haproxy[27651]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:33 node-2 haproxy[27651]: proxy neutron has no server available!
<129>Nov  5 09:03:34 node-2 haproxy[27655]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:34 node-2 haproxy[27655]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:34 node-2 haproxy[27655]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:34 node-2 haproxy[27655]: proxy mysqld has no server available!
<129>Nov  5 09:03:34 node-2 haproxy[27655]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:35 node-2 haproxy[27655]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:35 node-2 haproxy[27655]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:35 node-2 haproxy[27655]: proxy object-storage has no server available!
<27>Nov  5 09:03:36 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:36 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:36 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:36 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:36 node-2 multipathd: uevent trigger error
<129>Nov  5 09:03:38 node-2 haproxy[29073]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:38 node-2 haproxy[29073]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:39 node-2 haproxy[29077]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:39 node-2 haproxy[29077]: proxy keystone-1 has no server available!
<129>Nov  5 09:03:39 node-2 haproxy[29077]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:39 node-2 haproxy[29077]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:39 node-2 haproxy[29077]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:39 node-2 haproxy[29077]: proxy keystone-2 has no server available!
<129>Nov  5 09:03:39 node-2 haproxy[29077]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:39 node-2 haproxy[29077]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:39 node-2 haproxy[29077]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:39 node-2 haproxy[29077]: proxy neutron has no server available!
<129>Nov  5 09:03:39 node-2 haproxy[29077]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:40 node-2 haproxy[29077]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:40 node-2 haproxy[29077]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:40 node-2 haproxy[29077]: proxy mysqld has no server available!
<129>Nov  5 09:03:40 node-2 haproxy[29077]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:40 node-2 haproxy[29077]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:40 node-2 haproxy[29077]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:40 node-2 haproxy[29077]: proxy object-storage has no server available!
<27>Nov  5 09:03:41 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:41 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:41 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:41 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:41 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:42 node-2 multipathd: uevent trigger error
<129>Nov  5 09:03:44 node-2 haproxy[30606]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:44 node-2 haproxy[30606]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:44 node-2 haproxy[30606]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:44 node-2 haproxy[30606]: proxy keystone-1 has no server available!
<129>Nov  5 09:03:44 node-2 haproxy[30606]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:44 node-2 haproxy[30606]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:44 node-2 haproxy[30606]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:44 node-2 haproxy[30606]: proxy keystone-2 has no server available!
<129>Nov  5 09:03:44 node-2 haproxy[30606]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:44 node-2 haproxy[30606]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:45 node-2 haproxy[30610]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:45 node-2 haproxy[30610]: proxy neutron has no server available!
<129>Nov  5 09:03:45 node-2 haproxy[30610]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:45 node-2 haproxy[30610]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:45 node-2 haproxy[30610]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:45 node-2 haproxy[30610]: proxy mysqld has no server available!
<129>Nov  5 09:03:45 node-2 haproxy[30610]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:45 node-2 haproxy[30610]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:45 node-2 haproxy[30610]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:45 node-2 haproxy[30610]: proxy object-storage has no server available!
<129>Nov  5 09:03:45 node-2 haproxy[30610]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:45 node-2 haproxy[30610]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:46 node-2 haproxy[30610]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:46 node-2 haproxy[30610]: proxy aodh has no server available!
<27>Nov  5 09:03:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:47 node-2 multipathd: uevent trigger error
<129>Nov  5 09:03:49 node-2 haproxy[31955]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:49 node-2 haproxy[31955]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:49 node-2 haproxy[31955]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:49 node-2 haproxy[31955]: proxy keystone-1 has no server available!
<129>Nov  5 09:03:49 node-2 haproxy[31955]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:49 node-2 haproxy[31955]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:49 node-2 haproxy[31955]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:49 node-2 haproxy[31955]: proxy keystone-2 has no server available!
<129>Nov  5 09:03:50 node-2 haproxy[31959]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:50 node-2 haproxy[31959]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:50 node-2 haproxy[31959]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:50 node-2 haproxy[31959]: proxy neutron has no server available!
<129>Nov  5 09:03:50 node-2 haproxy[31959]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:50 node-2 haproxy[31959]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:50 node-2 haproxy[31959]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:50 node-2 haproxy[31959]: proxy mysqld has no server available!
<129>Nov  5 09:03:50 node-2 haproxy[31959]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:50 node-2 haproxy[31959]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:50 node-2 haproxy[31959]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:50 node-2 haproxy[31959]: proxy object-storage has no server available!
<129>Nov  5 09:03:50 node-2 haproxy[31959]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:51 node-2 haproxy[31959]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:51 node-2 haproxy[31959]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:51 node-2 haproxy[31959]: proxy aodh has no server available!
<129>Nov  5 09:03:51 node-2 haproxy[31959]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:51 node-2 haproxy[31959]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:51 node-2 haproxy[31959]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:51 node-2 haproxy[31959]: proxy ceilometer has no server available!
<27>Nov  5 09:03:54 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:54 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:54 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:54 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:54 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:54 node-2 multipathd: uevent trigger error
<129>Nov  5 09:03:56 node-2 haproxy[891]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:56 node-2 haproxy[891]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:56 node-2 haproxy[891]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:56 node-2 haproxy[891]: proxy keystone-1 has no server available!
<129>Nov  5 09:03:56 node-2 haproxy[891]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:56 node-2 haproxy[891]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:57 node-2 haproxy[910]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:57 node-2 haproxy[910]: proxy keystone-2 has no server available!
<129>Nov  5 09:03:57 node-2 haproxy[910]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:57 node-2 haproxy[910]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:57 node-2 haproxy[910]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:57 node-2 haproxy[910]: proxy neutron has no server available!
<129>Nov  5 09:03:57 node-2 haproxy[910]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:57 node-2 haproxy[910]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:57 node-2 haproxy[910]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:57 node-2 haproxy[910]: proxy mysqld has no server available!
<129>Nov  5 09:03:57 node-2 haproxy[910]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:57 node-2 haproxy[910]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:57 node-2 haproxy[910]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:57 node-2 haproxy[910]: proxy object-storage has no server available!
<129>Nov  5 09:03:58 node-2 haproxy[910]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:58 node-2 haproxy[910]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:58 node-2 haproxy[910]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:58 node-2 haproxy[910]: proxy aodh has no server available!
<129>Nov  5 09:03:58 node-2 haproxy[910]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:58 node-2 haproxy[910]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:03:58 node-2 haproxy[910]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:03:58 node-2 haproxy[910]: proxy ceilometer has no server available!
<27>Nov  5 09:03:59 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:59 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:59 node-2 multipathd: uevent trigger error
<27>Nov  5 09:03:59 node-2 multipathd: uevent trigger error
<129>Nov  5 09:04:01 node-2 haproxy[2246]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:02 node-2 haproxy[2250]: proxy keystone-1 has no server available!
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:02 node-2 haproxy[2250]: proxy keystone-2 has no server available!
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:02 node-2 haproxy[2250]: proxy neutron has no server available!
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:02 node-2 haproxy[2250]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:02 node-2 haproxy[2250]: proxy mysqld has no server available!
<129>Nov  5 09:04:03 node-2 haproxy[2250]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:03 node-2 haproxy[2250]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:03 node-2 haproxy[2250]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:03 node-2 haproxy[2250]: proxy object-storage has no server available!
<129>Nov  5 09:04:03 node-2 haproxy[2250]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:03 node-2 haproxy[2250]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:03 node-2 haproxy[2250]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:03 node-2 haproxy[2250]: proxy aodh has no server available!
<129>Nov  5 09:04:03 node-2 haproxy[2250]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:03 node-2 haproxy[2250]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:03 node-2 haproxy[2250]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:03 node-2 haproxy[2250]: proxy ceilometer has no server available!
<27>Nov  5 09:04:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:04 node-2 multipathd: uevent trigger error
<129>Nov  5 09:04:07 node-2 haproxy[3667]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:07 node-2 haproxy[3667]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:07 node-2 haproxy[3667]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:08 node-2 haproxy[3671]: proxy keystone-1 has no server available!
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:08 node-2 haproxy[3671]: proxy keystone-2 has no server available!
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:08 node-2 haproxy[3671]: proxy glance-api has no server available!
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:08 node-2 haproxy[3671]: proxy glance-glare has no server available!
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:08 node-2 haproxy[3671]: proxy neutron has no server available!
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:08 node-2 haproxy[3671]: proxy glance-registry has no server available!
<129>Nov  5 09:04:08 node-2 haproxy[3671]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:09 node-2 haproxy[3671]: proxy mysqld has no server available!
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:09 node-2 haproxy[3671]: proxy object-storage has no server available!
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:09 node-2 haproxy[3671]: proxy aodh has no server available!
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:09 node-2 haproxy[3671]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:09 node-2 haproxy[3671]: proxy ceilometer has no server available!
<27>Nov  5 09:04:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:10 node-2 multipathd: uevent trigger error
<129>Nov  5 09:04:13 node-2 haproxy[5069]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:13 node-2 haproxy[5069]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:13 node-2 haproxy[5069]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:13 node-2 haproxy[5069]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:13 node-2 haproxy[5069]: proxy keystone-1 has no server available!
<129>Nov  5 09:04:13 node-2 haproxy[5069]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:13 node-2 haproxy[5069]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:13 node-2 haproxy[5069]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:13 node-2 haproxy[5069]: proxy keystone-2 has no server available!
<129>Nov  5 09:04:13 node-2 haproxy[5069]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:13 node-2 haproxy[5069]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:14 node-2 haproxy[5073]: proxy nova-api has no server available!
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:14 node-2 haproxy[5073]: proxy nova-metadata-api has no server available!
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:14 node-2 haproxy[5073]: proxy glance-api has no server available!
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:14 node-2 haproxy[5073]: proxy glance-glare has no server available!
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:14 node-2 haproxy[5073]: proxy neutron has no server available!
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:14 node-2 haproxy[5073]: proxy glance-registry has no server available!
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:14 node-2 haproxy[5073]: proxy mysqld has no server available!
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:14 node-2 haproxy[5073]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:15 node-2 haproxy[5073]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:15 node-2 haproxy[5073]: proxy object-storage has no server available!
<129>Nov  5 09:04:15 node-2 haproxy[5073]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:15 node-2 haproxy[5073]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:15 node-2 haproxy[5073]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:15 node-2 haproxy[5073]: proxy aodh has no server available!
<129>Nov  5 09:04:15 node-2 haproxy[5073]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:15 node-2 haproxy[5073]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:15 node-2 haproxy[5073]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:15 node-2 haproxy[5073]: proxy ceilometer has no server available!
<129>Nov  5 09:04:15 node-2 haproxy[5073]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:15 node-2 haproxy[5073]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:15 node-2 haproxy[5073]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:15 node-2 haproxy[5073]: proxy nova-novncproxy has no server available!
<27>Nov  5 09:04:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:16 node-2 multipathd: uevent trigger error
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:19 node-2 haproxy[6413]: proxy keystone-1 has no server available!
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:19 node-2 haproxy[6413]: proxy keystone-2 has no server available!
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:19 node-2 haproxy[6413]: proxy nova-api has no server available!
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:19 node-2 haproxy[6413]: proxy nova-metadata-api has no server available!
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:19 node-2 haproxy[6413]: proxy cinder-api has no server available!
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:19 node-2 haproxy[6413]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:19 node-2 haproxy[6413]: proxy glance-api has no server available!
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:20 node-2 haproxy[6422]: proxy glance-glare has no server available!
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:20 node-2 haproxy[6422]: proxy neutron has no server available!
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:20 node-2 haproxy[6422]: proxy glance-registry has no server available!
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:20 node-2 haproxy[6422]: proxy mysqld has no server available!
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:20 node-2 haproxy[6422]: proxy object-storage has no server available!
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:20 node-2 haproxy[6422]: proxy aodh has no server available!
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:20 node-2 haproxy[6422]: proxy ceilometer has no server available!
<129>Nov  5 09:04:20 node-2 haproxy[6422]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:21 node-2 haproxy[6422]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:21 node-2 haproxy[6422]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:21 node-2 haproxy[6422]: proxy nova-novncproxy has no server available!
<27>Nov  5 09:04:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:22 node-2 multipathd: uevent trigger error
<129>Nov  5 09:04:24 node-2 haproxy[7925]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:24 node-2 haproxy[7925]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:24 node-2 haproxy[7925]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:25 node-2 haproxy[7929]: proxy keystone-1 has no server available!
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:25 node-2 haproxy[7929]: proxy keystone-2 has no server available!
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:25 node-2 haproxy[7929]: proxy nova-api has no server available!
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:25 node-2 haproxy[7929]: proxy nova-metadata-api has no server available!
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:25 node-2 haproxy[7929]: proxy cinder-api has no server available!
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:25 node-2 haproxy[7929]: proxy glance-api has no server available!
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:25 node-2 haproxy[7929]: proxy glance-glare has no server available!
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:25 node-2 haproxy[7929]: proxy neutron has no server available!
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:25 node-2 haproxy[7929]: proxy glance-registry has no server available!
<129>Nov  5 09:04:25 node-2 haproxy[7929]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:26 node-2 haproxy[7929]: proxy mysqld has no server available!
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:26 node-2 haproxy[7929]: proxy object-storage has no server available!
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:26 node-2 haproxy[7929]: proxy aodh has no server available!
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:26 node-2 haproxy[7929]: proxy ceilometer has no server available!
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:26 node-2 haproxy[7929]: proxy heat-api has no server available!
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:26 node-2 haproxy[7929]: proxy heat-api-cfn has no server available!
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:26 node-2 haproxy[7929]: proxy heat-api-cloudwatch has no server available!
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:04:26 node-2 haproxy[7929]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 09:04:26 node-2 haproxy[7929]: proxy nova-novncproxy has no server available!
<27>Nov  5 09:04:28 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:28 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:28 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:28 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:28 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:28 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:04:39 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov  5 09:04:50 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 09:05:00 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 09:05:06 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Nov  5 09:05:08 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov  5 09:05:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:05:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:05:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:05:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:05:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:05:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:07:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:00 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  5 09:08:04 node-2 apache2_error [Sat Nov 05 09:08:00.516117 2016] [mpm_event:notice] [pid 17551:tid 139872743704448] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  5 09:08:04 node-2 apache2_error [Sat Nov 05 09:08:00.516212 2016] [core:notice] [pid 17551:tid 139872743704448] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  5 09:08:04 node-2 apache2_error [Sat Nov 05 09:08:03.838697 2016] [mpm_event:notice] [pid 17551:tid 139872743704448] AH00491: caught SIGTERM, shutting down
<27>Nov  5 09:08:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:14 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:14 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:14 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:14 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:14 node-2 multipathd: uevent trigger error
<43>Nov  5 09:08:14 node-2 apache2_error [Sat Nov 05 09:08:04.924171 2016] [mpm_worker:notice] [pid 18522:tid 140352256616320] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  5 09:08:14 node-2 apache2_error [Sat Nov 05 09:08:04.924225 2016] [core:notice] [pid 18522:tid 140352256616320] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 09:08:17 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:17 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:17 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:08:18 node-2 multipathd: uevent trigger error
<43>Nov  5 09:09:34 node-2 apache2_error [Sat Nov 05 09:09:27.267296 2016] [mpm_worker:notice] [pid 18522:tid 140352256616320] AH00295: caught SIGTERM, shutting down
<43>Nov  5 09:09:34 node-2 apache2_error [Sat Nov 05 09:09:28.020031 2016] [mpm_worker:notice] [pid 31989:tid 140270691911552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 09:09:34 node-2 apache2_error [Sat Nov 05 09:09:28.020086 2016] [core:notice] [pid 31989:tid 140270691911552] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  5 09:10:14 node-2 apache2_error [Sat Nov 05 09:10:13.695295 2016] [mpm_worker:notice] [pid 31989:tid 140270691911552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 09:10:14 node-2 apache2_error [Sat Nov 05 09:10:13.888360 2016] [mpm_worker:warn] [pid 31989:tid 140270691911552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 09:10:14 node-2 apache2_error [Sat Nov 05 09:10:13.892699 2016] [mpm_worker:notice] [pid 31989:tid 140270691911552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 09:10:14 node-2 apache2_error [Sat Nov 05 09:10:13.892713 2016] [core:notice] [pid 31989:tid 140270691911552] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 09:10:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:10:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:10:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:10:59 node-2 multipathd: uevent trigger error
<27>Nov  5 09:10:59 node-2 multipathd: uevent trigger error
<27>Nov  5 09:10:59 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:01 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 09:11:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:03 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:18 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:45 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:45 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:45 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:45 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:45 node-2 multipathd: uevent trigger error
<27>Nov  5 09:11:45 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:46 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:46 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:12:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:13:38 node-2 multipathd: uevent trigger error
<27>Nov  5 09:13:38 node-2 multipathd: uevent trigger error
<27>Nov  5 09:13:38 node-2 multipathd: uevent trigger error
<27>Nov  5 09:13:38 node-2 multipathd: uevent trigger error
<27>Nov  5 09:13:38 node-2 multipathd: uevent trigger error
<27>Nov  5 09:13:38 node-2 multipathd: uevent trigger error
<27>Nov  5 09:14:03 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 09:14:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:14:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:14:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:14:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:14:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:14:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:15:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:15:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:15:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:15:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:15:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:16:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:17:04 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 09:18:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:18:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:18:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:18:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:18:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:18:48 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:51 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:51 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:51 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:51 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:51 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:57 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:57 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:57 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:57 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:57 node-2 multipathd: uevent trigger error
<27>Nov  5 09:19:57 node-2 multipathd: uevent trigger error
<27>Nov  5 09:20:05 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 09:20:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:20:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:20:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:20:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:20:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:11 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:11 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:11 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:11 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:11 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:11 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:17 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Nov  5 09:21:18 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Nov  5 09:21:18 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Nov  5 09:21:19 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Nov  5 09:21:19 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Nov  5 09:21:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:33 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:33 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:33 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:33 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:33 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:21:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:22:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:22:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:22:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:22:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:22:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:22:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:23:06 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 09:24:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:24:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:24:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:24:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:24:22 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:40 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:44 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:44 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:44 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:44 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:44 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:49 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:49 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:49 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:49 node-2 multipathd: uevent trigger error
<27>Nov  5 09:25:49 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:01 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:01 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:01 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:01 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:07 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 09:26:08 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:08 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:08 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:08 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:08 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:08 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:26:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:27:52 node-2 multipathd: uevent trigger error
<27>Nov  5 09:27:52 node-2 multipathd: uevent trigger error
<27>Nov  5 09:27:52 node-2 multipathd: uevent trigger error
<27>Nov  5 09:27:52 node-2 multipathd: uevent trigger error
<27>Nov  5 09:28:08 node-2 multipathd: uevent trigger error
<27>Nov  5 09:28:08 node-2 multipathd: uevent trigger error
<27>Nov  5 09:28:08 node-2 multipathd: uevent trigger error
<27>Nov  5 09:28:08 node-2 multipathd: uevent trigger error
<27>Nov  5 09:28:09 node-2 multipathd: uevent trigger error
<11>Nov  5 09:28:21 node-2 liberasurecode[21601]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:21 node-2 liberasurecode[21601]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:21 node-2 liberasurecode[21601]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:21 node-2 liberasurecode[21601]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:21 node-2 liberasurecode[21626]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:21 node-2 liberasurecode[21626]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:21 node-2 liberasurecode[21626]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:21 node-2 liberasurecode[21626]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:23 node-2 liberasurecode[22201]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:23 node-2 liberasurecode[22201]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:23 node-2 liberasurecode[22201]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:23 node-2 liberasurecode[22201]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24193]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24193]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24193]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24193]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24241]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24241]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24241]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24241]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:27 node-2 liberasurecode[24283]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24348]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24348]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24348]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24348]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24360]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24360]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24360]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24360]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24374]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24374]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24396]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24396]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24396]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:28 node-2 liberasurecode[24396]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:36 node-2 liberasurecode[25000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:36 node-2 liberasurecode[25000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:36 node-2 liberasurecode[25000]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:28:36 node-2 liberasurecode[25000]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  5 09:28:44 node-2 multipathd: uevent trigger error
<27>Nov  5 09:28:44 node-2 multipathd: uevent trigger error
<27>Nov  5 09:28:44 node-2 multipathd: uevent trigger error
<27>Nov  5 09:28:44 node-2 multipathd: uevent trigger error
<27>Nov  5 09:28:44 node-2 multipathd: uevent trigger error
<27>Nov  5 09:29:11 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  5 09:29:36 node-2 apache2_error [Sat Nov 05 09:29:30.676999 2016] [mpm_worker:notice] [pid 31989:tid 140270691911552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 09:29:36 node-2 apache2_error [Sat Nov 05 09:29:31.060442 2016] [mpm_worker:warn] [pid 31989:tid 140270691911552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 09:29:36 node-2 apache2_error [Sat Nov 05 09:29:31.064893 2016] [mpm_worker:notice] [pid 31989:tid 140270691911552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 09:29:36 node-2 apache2_error [Sat Nov 05 09:29:31.064914 2016] [core:notice] [pid 31989:tid 140270691911552] AH00094: Command line: '/usr/sbin/apache2'
<11>Nov  5 09:30:02 node-2 liberasurecode[4529]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:30:02 node-2 liberasurecode[4529]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:30:02 node-2 liberasurecode[4529]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:30:02 node-2 liberasurecode[4529]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  5 09:30:12 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:12 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:12 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:12 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:12 node-2 multipathd: uevent trigger error
<43>Nov  5 09:30:16 node-2 apache2_error [Sat Nov 05 09:30:08.426867 2016] [mpm_worker:notice] [pid 31989:tid 140270691911552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 09:30:16 node-2 apache2_error [Sat Nov 05 09:30:08.623445 2016] [mpm_worker:warn] [pid 31989:tid 140270691911552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 09:30:16 node-2 apache2_error [Sat Nov 05 09:30:08.629123 2016] [mpm_worker:notice] [pid 31989:tid 140270691911552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 09:30:16 node-2 apache2_error [Sat Nov 05 09:30:08.629158 2016] [core:notice] [pid 31989:tid 140270691911552] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 09:30:19 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:19 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:19 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:20 node-2 multipathd: uevent trigger error
<43>Nov  5 09:30:56 node-2 apache2_error [Sat Nov 05 09:30:54.426840 2016] [mpm_worker:notice] [pid 31989:tid 140270691911552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 09:30:56 node-2 apache2_error [Sat Nov 05 09:30:54.622294 2016] [mpm_worker:warn] [pid 31989:tid 140270691911552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 09:30:56 node-2 apache2_error [Sat Nov 05 09:30:54.626230 2016] [mpm_worker:notice] [pid 31989:tid 140270691911552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 09:30:56 node-2 apache2_error [Sat Nov 05 09:30:54.626246 2016] [core:notice] [pid 31989:tid 140270691911552] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 09:30:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:30:58 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:04 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:09 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:31:54 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:00 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:00 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:01 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:01 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:07 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov  5 09:32:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:16 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:32:47 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:00 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:00 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:00 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:00 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:05 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:05 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:05 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:05 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:05 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:10 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:15 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:25 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:30 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:30 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:30 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:30 node-2 multipathd: uevent trigger error
<27>Nov  5 09:33:30 node-2 multipathd: uevent trigger error
<11>Nov  5 09:35:01 node-2 liberasurecode[7386]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:35:01 node-2 liberasurecode[7386]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:35:01 node-2 liberasurecode[7386]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 09:35:01 node-2 liberasurecode[7386]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  5 09:35:12 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:12 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:12 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:12 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:12 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:12 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:20 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:21 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:35:31 node-2 multipathd: uevent trigger error
<129>Nov  5 09:35:42 node-2 haproxy[10996]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:35:42 node-2 haproxy[10996]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 09:36:12 node-2 haproxy[10996]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Nov  5 09:36:21 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:21 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:21 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:21 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:21 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:26 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:26 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:26 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:26 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:26 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:31 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:42 node-2 multipathd: uevent trigger error
<27>Nov  5 09:36:42 node-2 multipathd: uevent trigger error
