Sep 21 17:27:02 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8383" x-info="http://www.rsyslog.com"] start
Sep 21 17:27:02 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 21 17:27:02 node-2 rsyslogd: rsyslogd's groupid changed to 104
Sep 21 17:27:02 node-2 rsyslogd: rsyslogd's userid changed to 101
Sep 21 17:27:02 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 21 17:27:02 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 21 17:27:02 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 21 17:27:02 node-2 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 21 17:27:02 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=eccea8ce-3a10-4ebd-b294-5c54e3838530 nomdmonddf nomdmonisw
Sep 21 17:27:02 node-2 kernel: [    0.000000] KERNEL supported cpus:
Sep 21 17:27:02 node-2 kernel: [    0.000000]   Intel GenuineIntel
Sep 21 17:27:02 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Sep 21 17:27:02 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Sep 21 17:27:02 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 21 17:27:02 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 21 17:27:02 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 21 17:27:02 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 21 17:27:02 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
Sep 21 17:27:02 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 21 17:27:02 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 21 17:27:02 node-2 kernel: [    0.000000] No AGP bridge found
Sep 21 17:27:02 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 21 17:27:02 node-2 kernel: [    0.000000] MTRR default type: write-back
Sep 21 17:27:02 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 21 17:27:02 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Sep 21 17:27:02 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 21 17:27:02 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 21 17:27:02 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 21 17:27:02 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 21 17:27:02 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 21 17:27:02 node-2 kernel: [    0.000000]   2 disabled
Sep 21 17:27:02 node-2 kernel: [    0.000000]   3 disabled
Sep 21 17:27:02 node-2 kernel: [    0.000000]   4 disabled
Sep 21 17:27:02 node-2 kernel: [    0.000000]   5 disabled
Sep 21 17:27:02 node-2 kernel: [    0.000000]   6 disabled
Sep 21 17:27:02 node-2 kernel: [    0.000000]   7 disabled
Sep 21 17:27:02 node-2 kernel: [    0.000000]   8 disabled
Sep 21 17:27:02 node-2 kernel: [    0.000000]   9 disabled
Sep 21 17:27:02 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 21 17:27:02 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 21 17:27:02 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 21 17:27:02 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 21 17:27:02 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 21 17:27:02 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Sep 21 17:27:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 21 17:27:02 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 21 17:27:02 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 21 17:27:02 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 21 17:27:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 21 17:27:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 21 17:27:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 21 17:27:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Sep 21 17:27:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 21 17:27:02 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 21 17:27:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 21 17:27:02 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 21 17:27:02 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 21 17:27:02 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 21 17:27:02 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 21 17:27:02 node-2 kernel: [    0.000000] Zone ranges:
Sep 21 17:27:02 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] Movable zone start for each node
Sep 21 17:27:02 node-2 kernel: [    0.000000] Early memory node ranges
Sep 21 17:27:02 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Sep 21 17:27:02 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 21 17:27:02 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 21 17:27:02 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 21 17:27:02 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Sep 21 17:27:02 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Sep 21 17:27:02 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 21 17:27:02 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 21 17:27:02 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 21 17:27:02 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 21 17:27:02 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 21 17:27:02 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 21 17:27:02 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 21 17:27:02 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 21 17:27:02 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 21 17:27:02 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 21 17:27:02 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 21 17:27:02 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 21 17:27:02 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 21 17:27:02 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 21 17:27:02 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 21 17:27:02 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 21 17:27:02 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 21 17:27:02 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 
Sep 21 17:27:02 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Sep 21 17:27:02 node-2 kernel: [    0.000000] Policy zone: Normal
Sep 21 17:27:02 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=eccea8ce-3a10-4ebd-b294-5c54e3838530 nomdmonddf nomdmonisw
Sep 21 17:27:02 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 21 17:27:02 node-2 kernel: [    0.000000] Checking aperture...
Sep 21 17:27:02 node-2 kernel: [    0.000000] No AGP bridge found
Sep 21 17:27:02 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 21 17:27:02 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 21 17:27:02 node-2 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep 21 17:27:02 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 21 17:27:02 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 21 17:27:02 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 21 17:27:02 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 21 17:27:02 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 21 17:27:02 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 21 17:27:02 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 21 17:27:02 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 21 17:27:02 node-2 kernel: [    0.000000] console [tty0] enabled
Sep 21 17:27:02 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 21 17:27:02 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 21 17:27:02 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 21 17:27:02 node-2 kernel: [    0.000000] hpet clockevent registered
Sep 21 17:27:02 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 21 17:27:02 node-2 kernel: [    0.004000] tsc: Detected 3491.963 MHz processor
Sep 21 17:27:02 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.92 BogoMIPS (lpj=13967852)
Sep 21 17:27:02 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 21 17:27:02 node-2 kernel: [    0.000050] Security Framework initialized
Sep 21 17:27:02 node-2 kernel: [    0.000069] AppArmor: AppArmor initialized
Sep 21 17:27:02 node-2 kernel: [    0.000071] Yama: becoming mindful.
Sep 21 17:27:02 node-2 kernel: [    0.001465] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.006356] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.008286] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.008314] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.008606] Initializing cgroup subsys memory
Sep 21 17:27:02 node-2 kernel: [    0.008614] Initializing cgroup subsys devices
Sep 21 17:27:02 node-2 kernel: [    0.008616] Initializing cgroup subsys freezer
Sep 21 17:27:02 node-2 kernel: [    0.008618] Initializing cgroup subsys blkio
Sep 21 17:27:02 node-2 kernel: [    0.008619] Initializing cgroup subsys perf_event
Sep 21 17:27:02 node-2 kernel: [    0.008621] Initializing cgroup subsys hugetlb
Sep 21 17:27:02 node-2 kernel: [    0.008640] CPU: Physical Processor ID: 0
Sep 21 17:27:02 node-2 kernel: [    0.008641] CPU: Processor Core ID: 0
Sep 21 17:27:02 node-2 kernel: [    0.008645] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 21 17:27:02 node-2 kernel: [    0.008645] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 21 17:27:02 node-2 kernel: [    0.009339] mce: CPU supports 22 MCE banks
Sep 21 17:27:02 node-2 kernel: [    0.009366] CPU0: Thermal monitoring enabled (TM1)
Sep 21 17:27:02 node-2 kernel: [    0.009387] process: using mwait in idle threads
Sep 21 17:27:02 node-2 kernel: [    0.009390] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 21 17:27:02 node-2 kernel: [    0.009390] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 21 17:27:02 node-2 kernel: [    0.009390] tlb_flushall_shift: 6
Sep 21 17:27:02 node-2 kernel: [    0.009479] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 21 17:27:02 node-2 kernel: [    0.010201] ACPI: Core revision 20131115
Sep 21 17:27:02 node-2 kernel: [    0.022901] ACPI: All ACPI Tables successfully acquired
Sep 21 17:27:02 node-2 kernel: [    0.023062] ftrace: allocating 28617 entries in 112 pages
Sep 21 17:27:02 node-2 kernel: [    0.032019] dmar: Host address width 46
Sep 21 17:27:02 node-2 kernel: [    0.032021] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 21 17:27:02 node-2 kernel: [    0.032027] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 21 17:27:02 node-2 kernel: [    0.032029] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 21 17:27:02 node-2 kernel: [    0.032033] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 21 17:27:02 node-2 kernel: [    0.032034] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 21 17:27:02 node-2 kernel: [    0.032036] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 21 17:27:02 node-2 kernel: [    0.032037] dmar: ATSR flags: 0x0
Sep 21 17:27:02 node-2 kernel: [    0.032038] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 21 17:27:02 node-2 kernel: [    0.032039] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 21 17:27:02 node-2 kernel: [    0.032154] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 21 17:27:02 node-2 kernel: [    0.032156] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 21 17:27:02 node-2 kernel: [    0.032157] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 21 17:27:02 node-2 kernel: [    0.032158] HPET id 0 under DRHD base 0xc7ffc000
Sep 21 17:27:02 node-2 kernel: [    0.032159] Your BIOS is broken and requested that x2apic be disabled.
Sep 21 17:27:02 node-2 kernel: [    0.032159] This will slightly decrease performance.
Sep 21 17:27:02 node-2 kernel: [    0.032159] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 21 17:27:02 node-2 kernel: [    0.032591] Enabled IRQ remapping in xapic mode
Sep 21 17:27:02 node-2 kernel: [    0.032592] x2apic not enabled, IRQ remapping is in xapic mode
Sep 21 17:27:02 node-2 kernel: [    0.032595] Switched APIC routing to physical flat.
Sep 21 17:27:02 node-2 kernel: [    0.033212] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 21 17:27:02 node-2 kernel: [    0.072862] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 21 17:27:02 node-2 kernel: [    0.072867] TSC deadline timer enabled
Sep 21 17:27:02 node-2 kernel: [    0.072875] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 21 17:27:02 node-2 kernel: [    0.072881] ... version:                3
Sep 21 17:27:02 node-2 kernel: [    0.072882] ... bit width:              48
Sep 21 17:27:02 node-2 kernel: [    0.072883] ... generic registers:      4
Sep 21 17:27:02 node-2 kernel: [    0.072884] ... value mask:             0000ffffffffffff
Sep 21 17:27:02 node-2 kernel: [    0.072885] ... max period:             0000ffffffffffff
Sep 21 17:27:02 node-2 kernel: [    0.072886] ... fixed-purpose events:   3
Sep 21 17:27:02 node-2 kernel: [    0.072887] ... event mask:             000000070000000f
Sep 21 17:27:02 node-2 kernel: [    0.074273] x86: Booting SMP configuration:
Sep 21 17:27:02 node-2 kernel: [    0.088379] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 21 17:27:02 node-2 kernel: [    0.074275] .... node  #0, CPUs:        #1  #2  #3
Sep 21 17:27:02 node-2 kernel: [    0.116283] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 21 17:27:02 node-2 kernel: [    0.270421] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 21 17:27:02 node-2 kernel: [    0.326034] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 21 17:27:02 node-2 kernel: [    0.382878] x86: Booted up 2 nodes, 16 CPUs
Sep 21 17:27:02 node-2 kernel: [    0.382882] smpboot: Total of 16 processors activated (111754.97 BogoMIPS)
Sep 21 17:27:02 node-2 kernel: [    0.406894] devtmpfs: initialized
Sep 21 17:27:02 node-2 kernel: [    0.410004] EVM: security.selinux
Sep 21 17:27:02 node-2 kernel: [    0.410006] EVM: security.SMACK64
Sep 21 17:27:02 node-2 kernel: [    0.410007] EVM: security.ima
Sep 21 17:27:02 node-2 kernel: [    0.410008] EVM: security.capability
Sep 21 17:27:02 node-2 kernel: [    0.410058] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.410737] pinctrl core: initialized pinctrl subsystem
Sep 21 17:27:02 node-2 kernel: [    0.410799] regulator-dummy: no parameters
Sep 21 17:27:02 node-2 kernel: [    0.410831] RTC time: 17:26:22, date: 09/21/16
Sep 21 17:27:02 node-2 kernel: [    0.410866] NET: Registered protocol family 16
Sep 21 17:27:02 node-2 kernel: [    0.410952] cpuidle: using governor ladder
Sep 21 17:27:02 node-2 kernel: [    0.410954] cpuidle: using governor menu
Sep 21 17:27:02 node-2 kernel: [    0.410990] ACPI: bus type PCI registered
Sep 21 17:27:02 node-2 kernel: [    0.410992] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 21 17:27:02 node-2 kernel: [    0.411037] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 21 17:27:02 node-2 kernel: [    0.411040] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 21 17:27:02 node-2 kernel: [    0.424768] PCI: Using configuration type 1 for base access
Sep 21 17:27:02 node-2 kernel: [    0.425771] bio: create slab <bio-0> at 0
Sep 21 17:27:02 node-2 kernel: [    0.426053] ACPI: Added _OSI(Module Device)
Sep 21 17:27:02 node-2 kernel: [    0.426055] ACPI: Added _OSI(Processor Device)
Sep 21 17:27:02 node-2 kernel: [    0.426056] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 21 17:27:02 node-2 kernel: [    0.426057] ACPI: Added _OSI(Processor Aggregator Device)
Sep 21 17:27:02 node-2 kernel: [    0.438719] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 21 17:27:02 node-2 kernel: [    0.453457] ACPI: Interpreter enabled
Sep 21 17:27:02 node-2 kernel: [    0.453463] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 21 17:27:02 node-2 kernel: [    0.453467] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 21 17:27:02 node-2 kernel: [    0.453469] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 21 17:27:02 node-2 kernel: [    0.453476] ACPI: (supports S0 S4 S5)
Sep 21 17:27:02 node-2 kernel: [    0.453478] ACPI: Using IOAPIC for interrupt routing
Sep 21 17:27:02 node-2 kernel: [    0.453518] HEST: Table parsing has been initialized.
Sep 21 17:27:02 node-2 kernel: [    0.453521] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 21 17:27:02 node-2 kernel: [    0.454074] ACPI: No dock devices found.
Sep 21 17:27:02 node-2 kernel: [    0.465765] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 21 17:27:02 node-2 kernel: [    0.465770] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 21 17:27:02 node-2 kernel: [    0.465773] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 21 17:27:02 node-2 kernel: [    0.465802] PCI host bridge to bus 0000:ff
Sep 21 17:27:02 node-2 kernel: [    0.465805] pci_bus 0000:ff: root bus resource [bus ff]
Sep 21 17:27:02 node-2 kernel: [    0.465813] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.465851] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.465882] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.465917] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.465947] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.465977] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.466008] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466037] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466068] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466101] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466128] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466154] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466183] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466209] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466236] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466263] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466292] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466319] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466346] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.466374] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466400] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.466427] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466455] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466487] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.466521] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466552] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466582] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466613] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466644] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466676] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466708] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466740] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466771] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466803] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466834] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466865] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466897] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466927] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466954] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.466986] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467019] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467057] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467092] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467125] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467155] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467196] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467229] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467260] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467292] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467324] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467356] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467386] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467415] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467445] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467475] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467511] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467543] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467601] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 21 17:27:02 node-2 kernel: [    0.467604] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 21 17:27:02 node-2 kernel: [    0.467607] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 21 17:27:02 node-2 kernel: [    0.467624] PCI host bridge to bus 0000:7f
Sep 21 17:27:02 node-2 kernel: [    0.467626] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 21 17:27:02 node-2 kernel: [    0.467631] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467658] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.467687] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467716] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467738] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.467762] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.467788] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467814] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467836] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467859] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467881] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467903] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467927] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467949] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467973] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.467998] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468019] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468042] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468065] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.468088] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468112] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.468134] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468156] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468182] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 21 17:27:02 node-2 kernel: [    0.468215] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468241] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468267] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468293] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468319] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468345] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468370] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468398] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468423] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468452] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468479] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468507] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468536] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468561] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468586] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468614] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468640] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468669] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468700] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468727] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468756] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468784] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468812] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468842] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468871] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468898] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468929] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468956] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.468979] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.469006] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.469033] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.469063] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.469090] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.470352] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 21 17:27:02 node-2 kernel: [    0.470355] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 21 17:27:02 node-2 kernel: [    0.471473] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 21 17:27:02 node-2 kernel: [    0.471983] PCI host bridge to bus 0000:00
Sep 21 17:27:02 node-2 kernel: [    0.471985] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 21 17:27:02 node-2 kernel: [    0.471987] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 21 17:27:02 node-2 kernel: [    0.471988] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 21 17:27:02 node-2 kernel: [    0.471990] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 21 17:27:02 node-2 kernel: [    0.471991] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 21 17:27:02 node-2 kernel: [    0.471992] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 21 17:27:02 node-2 kernel: [    0.471994] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 21 17:27:02 node-2 kernel: [    0.471999] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 21 17:27:02 node-2 kernel: [    0.472082] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.472113] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.472155] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 21 17:27:02 node-2 kernel: [    0.472175] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.472204] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.472245] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 21 17:27:02 node-2 kernel: [    0.472265] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.472294] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.472334] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 21 17:27:02 node-2 kernel: [    0.472351] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.472423] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.472503] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.472580] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 21 17:27:02 node-2 kernel: [    0.472585] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 21 17:27:02 node-2 kernel: [    0.472670] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 21 17:27:02 node-2 kernel: [    0.472814] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 21 17:27:02 node-2 kernel: [    0.472832] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 21 17:27:02 node-2 kernel: [    0.472909] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.472964] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 21 17:27:02 node-2 kernel: [    0.472985] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.473040] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.473084] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 21 17:27:02 node-2 kernel: [    0.473111] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.473167] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.473210] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 21 17:27:02 node-2 kernel: [    0.473233] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 21 17:27:02 node-2 kernel: [    0.473250] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 21 17:27:02 node-2 kernel: [    0.473327] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.473377] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 21 17:27:02 node-2 kernel: [    0.473403] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 21 17:27:02 node-2 kernel: [    0.473650] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 21 17:27:02 node-2 kernel: [    0.473656] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 21 17:27:02 node-2 kernel: [    0.473662] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.473667] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.473675] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 21 17:27:02 node-2 kernel: [    0.473705] pci 0000:01:00.0: supports D1 D2
Sep 21 17:27:02 node-2 kernel: [    0.483514] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 21 17:27:02 node-2 kernel: [    0.483517] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 21 17:27:02 node-2 kernel: [    0.483519] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 21 17:27:02 node-2 kernel: [    0.483625] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.483659] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 21 17:27:02 node-2 kernel: [    0.495503] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 21 17:27:02 node-2 kernel: [    0.495509] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.495513] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 21 17:27:02 node-2 kernel: [    0.495583] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.495651] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.495727] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.495772] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 21 17:27:02 node-2 kernel: [    0.495775] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.495777] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 21 17:27:02 node-2 kernel: [    0.495831] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.495954] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.496007] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 21 17:27:02 node-2 kernel: [    0.496009] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.496012] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 21 17:27:02 node-2 kernel: [    0.496061] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.496202] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.496243] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.496363] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.496399] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.496518] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.496554] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 21 17:27:02 node-2 kernel: [    0.496675] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 21 17:27:02 node-2 kernel: [    0.496717] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 21 17:27:02 node-2 kernel: [    0.496719] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.496721] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 21 17:27:02 node-2 kernel: [    0.496779] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 21 17:27:02 node-2 kernel: [    0.496842] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.496894] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.496936] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 21 17:27:02 node-2 kernel: [    0.497018] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 21 17:27:02 node-2 kernel: [    0.497126] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 21 17:27:02 node-2 kernel: [    0.497128] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.497130] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 21 17:27:02 node-2 kernel: [    0.497203] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 21 17:27:02 node-2 kernel: [    0.497261] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.497309] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.497521] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 21 17:27:02 node-2 kernel: [    0.497524] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 21 17:27:02 node-2 kernel: [    0.497588] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 21 17:27:02 node-2 kernel: [    0.497641] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.497690] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.497901] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 21 17:27:02 node-2 kernel: [    0.497905] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 21 17:27:02 node-2 kernel: [    0.497965] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 21 17:27:02 node-2 kernel: [    0.498024] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.498077] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 21 17:27:02 node-2 kernel: [    0.498326] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 21 17:27:02 node-2 kernel: [    0.498329] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 21 17:27:02 node-2 kernel: [    0.498504] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 21 17:27:02 node-2 kernel: [    0.498543] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 21 17:27:02 node-2 kernel: [    0.498618] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 21 17:27:02 node-2 kernel: [    0.498637] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 21 17:27:02 node-2 kernel: [    0.498650] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 21 17:27:02 node-2 kernel: [    0.498663] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 21 17:27:02 node-2 kernel: [    0.498713] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 21 17:27:02 node-2 kernel: [    0.507508] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 21 17:27:02 node-2 kernel: [    0.507517] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 21 17:27:02 node-2 kernel: [    0.507570] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 21 17:27:02 node-2 kernel: [    0.508088] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 21 17:27:02 node-2 kernel: [    0.508091] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 21 17:27:02 node-2 kernel: [    0.508215] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 21 17:27:02 node-2 kernel: [    0.508322] PCI host bridge to bus 0000:80
Sep 21 17:27:02 node-2 kernel: [    0.508324] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 21 17:27:02 node-2 kernel: [    0.508326] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 21 17:27:02 node-2 kernel: [    0.508327] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 21 17:27:02 node-2 kernel: [    0.508335] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.508400] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.508468] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 21 17:27:02 node-2 kernel: [    0.508530] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 21 17:27:02 node-2 kernel: [    0.508536] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 21 17:27:02 node-2 kernel: [    0.508609] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 21 17:27:02 node-2 kernel: [    0.508908] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 21 17:27:02 node-2 kernel: [    0.508940] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 21 17:27:02 node-2 kernel: [    0.508969] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 21 17:27:02 node-2 kernel: [    0.508999] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 21 17:27:02 node-2 kernel: [    0.509028] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 21 17:27:02 node-2 kernel: [    0.509058] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 21 17:27:02 node-2 kernel: [    0.509088] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 21 17:27:02 node-2 kernel: [    0.509118] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 21 17:27:02 node-2 kernel: [    0.509203] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 21 17:27:02 node-2 kernel: [    0.509207] ACPI: \_SB_.UNC1: notify handler is installed
Sep 21 17:27:02 node-2 kernel: [    0.509209] ACPI: \_SB_.UNC0: notify handler is installed
Sep 21 17:27:02 node-2 kernel: [    0.509224] ACPI: \_SB_.PCI0: notify handler is installed
Sep 21 17:27:02 node-2 kernel: [    0.509277] ACPI: \_SB_.PCI1: notify handler is installed
Sep 21 17:27:02 node-2 kernel: [    0.509356] Found 4 acpi root devices
Sep 21 17:27:02 node-2 kernel: [    0.509466] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 21 17:27:02 node-2 kernel: [    0.509468] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 21 17:27:02 node-2 kernel: [    0.509470] vgaarb: loaded
Sep 21 17:27:02 node-2 kernel: [    0.509471] vgaarb: bridge control possible 0000:0c:00.0
Sep 21 17:27:02 node-2 kernel: [    0.509590] SCSI subsystem initialized
Sep 21 17:27:02 node-2 kernel: [    0.509654] libata version 3.00 loaded.
Sep 21 17:27:02 node-2 kernel: [    0.509670] ACPI: bus type USB registered
Sep 21 17:27:02 node-2 kernel: [    0.509681] usbcore: registered new interface driver usbfs
Sep 21 17:27:02 node-2 kernel: [    0.509685] usbcore: registered new interface driver hub
Sep 21 17:27:02 node-2 kernel: [    0.509710] usbcore: registered new device driver usb
Sep 21 17:27:02 node-2 kernel: [    0.509876] PCI: Using ACPI for IRQ routing
Sep 21 17:27:02 node-2 kernel: [    0.513473] PCI: pci_cache_line_size set to 64 bytes
Sep 21 17:27:02 node-2 kernel: [    0.513681] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 21 17:27:02 node-2 kernel: [    0.513682] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Sep 21 17:27:02 node-2 kernel: [    0.513683] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 21 17:27:02 node-2 kernel: [    0.513750] NetLabel: Initializing
Sep 21 17:27:02 node-2 kernel: [    0.513751] NetLabel:  domain hash size = 128
Sep 21 17:27:02 node-2 kernel: [    0.513752] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 21 17:27:02 node-2 kernel: [    0.513762] NetLabel:  unlabeled traffic allowed by default
Sep 21 17:27:02 node-2 kernel: [    0.513819] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 21 17:27:02 node-2 kernel: [    0.513823] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 21 17:27:02 node-2 kernel: [    0.515879] Switched to clocksource hpet
Sep 21 17:27:02 node-2 kernel: [    0.519995] AppArmor: AppArmor Filesystem Enabled
Sep 21 17:27:02 node-2 kernel: [    0.520008] pnp: PnP ACPI init
Sep 21 17:27:02 node-2 kernel: [    0.520015] ACPI: bus type PNP registered
Sep 21 17:27:02 node-2 kernel: [    0.520124] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 21 17:27:02 node-2 kernel: [    0.520132] pnp 00:01: [dma 4]
Sep 21 17:27:02 node-2 kernel: [    0.520144] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 21 17:27:02 node-2 kernel: [    0.520170] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 21 17:27:02 node-2 kernel: [    0.520190] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 21 17:27:02 node-2 kernel: [    0.520207] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 21 17:27:02 node-2 kernel: [    0.520241] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 21 17:27:02 node-2 kernel: [    0.520293] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520295] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 21 17:27:02 node-2 kernel: [    0.520296] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520298] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520299] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520304] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520306] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 21 17:27:02 node-2 kernel: [    0.520307] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520309] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520310] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520312] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520313] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520315] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 21 17:27:02 node-2 kernel: [    0.520317] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 21 17:27:02 node-2 kernel: [    0.520400] pnp 00:07: [dma 0 disabled]
Sep 21 17:27:02 node-2 kernel: [    0.520429] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 21 17:27:02 node-2 kernel: [    0.520504] pnp 00:08: [dma 0 disabled]
Sep 21 17:27:02 node-2 kernel: [    0.520535] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 21 17:27:02 node-2 kernel: [    0.520586] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 21 17:27:02 node-2 kernel: [    0.520940] pnp: PnP ACPI: found 10 devices
Sep 21 17:27:02 node-2 kernel: [    0.520942] ACPI: bus type PNP unregistered
Sep 21 17:27:02 node-2 kernel: [    0.527209] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 21 17:27:02 node-2 kernel: [    0.527212] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 21 17:27:02 node-2 kernel: [    0.527215] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 21 17:27:02 node-2 kernel: [    0.527219] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 21 17:27:02 node-2 kernel: [    0.527221] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.527236] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527265] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 21 17:27:02 node-2 kernel: [    0.527279] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527308] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 21 17:27:02 node-2 kernel: [    0.527323] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 21 17:27:02 node-2 kernel: [    0.527351] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 21 17:27:02 node-2 kernel: [    0.527366] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 21 17:27:02 node-2 kernel: [    0.527395] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 21 17:27:02 node-2 kernel: [    0.527397] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.527411] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527443] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 21 17:27:02 node-2 kernel: [    0.527445] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.527459] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527488] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 21 17:27:02 node-2 kernel: [    0.527490] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.527493] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527497] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 21 17:27:02 node-2 kernel: [    0.527499] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.527501] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527505] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 21 17:27:02 node-2 kernel: [    0.527509] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 21 17:27:02 node-2 kernel: [    0.527517] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 21 17:27:02 node-2 kernel: [    0.527521] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 21 17:27:02 node-2 kernel: [    0.527527] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 21 17:27:02 node-2 kernel: [    0.527528] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 21 17:27:02 node-2 kernel: [    0.527529] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 21 17:27:02 node-2 kernel: [    0.527530] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 21 17:27:02 node-2 kernel: [    0.527531] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 21 17:27:02 node-2 kernel: [    0.527532] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 21 17:27:02 node-2 kernel: [    0.527533] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 21 17:27:02 node-2 kernel: [    0.527533] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 21 17:27:02 node-2 kernel: [    0.527534] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.527535] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527536] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.527537] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527538] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.527539] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527540] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.527540] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527541] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 21 17:27:02 node-2 kernel: [    0.527542] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527543] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 21 17:27:02 node-2 kernel: [    0.527544] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 21 17:27:02 node-2 kernel: [    0.527545] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 21 17:27:02 node-2 kernel: [    0.527546] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 21 17:27:02 node-2 kernel: [    0.527548] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 21 17:27:02 node-2 kernel: [    0.527549] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 21 17:27:02 node-2 kernel: [    0.527586] NET: Registered protocol family 2
Sep 21 17:27:02 node-2 kernel: [    0.527844] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.528184] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.528330] TCP: Hash tables configured (established 262144 bind 65536)
Sep 21 17:27:02 node-2 kernel: [    0.528367] TCP: reno registered
Sep 21 17:27:02 node-2 kernel: [    0.528397] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.528493] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.528640] NET: Registered protocol family 1
Sep 21 17:27:02 node-2 kernel: [    0.567981] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 21 17:27:02 node-2 kernel: [    0.567996] PCI: CLS 64 bytes, default 64
Sep 21 17:27:02 node-2 kernel: [    0.568072] Trying to unpack rootfs image as initramfs...
Sep 21 17:27:02 node-2 kernel: [    0.788322] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep 21 17:27:02 node-2 kernel: [    0.788359] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 21 17:27:02 node-2 kernel: [    0.788362] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Sep 21 17:27:02 node-2 kernel: [    0.788751] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788757] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788762] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788767] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788777] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788788] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788796] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788805] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788813] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788822] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788828] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788835] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788842] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788849] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788857] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788865] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 21 17:27:02 node-2 kernel: [    0.788906] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 21 17:27:02 node-2 kernel: [    0.788910] Scanning for low memory corruption every 60 seconds
Sep 21 17:27:02 node-2 kernel: [    0.789226] Initialise system trusted keyring
Sep 21 17:27:02 node-2 kernel: [    0.789273] audit: initializing netlink socket (disabled)
Sep 21 17:27:02 node-2 kernel: [    0.789282] type=2000 audit(1474478782.744:1): initialized
Sep 21 17:27:02 node-2 kernel: [    0.807098] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 21 17:27:02 node-2 kernel: [    0.808584] zbud: loaded
Sep 21 17:27:02 node-2 kernel: [    0.808696] VFS: Disk quotas dquot_6.5.2
Sep 21 17:27:02 node-2 kernel: [    0.808740] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 21 17:27:02 node-2 kernel: [    0.809111] fuse init (API version 7.22)
Sep 21 17:27:02 node-2 kernel: [    0.809170] msgmni has been set to 32768
Sep 21 17:27:02 node-2 kernel: [    0.809213] Key type big_key registered
Sep 21 17:27:02 node-2 kernel: [    0.809729] Key type asymmetric registered
Sep 21 17:27:02 node-2 kernel: [    0.809731] Asymmetric key parser 'x509' registered
Sep 21 17:27:02 node-2 kernel: [    0.809761] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 21 17:27:02 node-2 kernel: [    0.809823] io scheduler noop registered
Sep 21 17:27:02 node-2 kernel: [    0.809824] io scheduler deadline registered (default)
Sep 21 17:27:02 node-2 kernel: [    0.809841] io scheduler cfq registered
Sep 21 17:27:02 node-2 kernel: [    0.810152] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    0.810242] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    0.810330] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    0.810416] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    0.810511] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    0.810578] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    0.810835] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 21 17:27:02 node-2 kernel: [    0.810853] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 21 17:27:02 node-2 kernel: [    0.810866] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 21 17:27:02 node-2 kernel: [    0.810875] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810877] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810879] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 21 17:27:02 node-2 kernel: [    0.810883] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810885] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810886] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810887] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810889] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810890] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810891] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810893] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810894] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810895] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810897] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810898] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810900] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 21 17:27:02 node-2 kernel: [    0.810904] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810906] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 21 17:27:02 node-2 kernel: [    0.810915] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810917] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 21 17:27:02 node-2 kernel: [    0.810927] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810928] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 21 17:27:02 node-2 kernel: [    0.810931] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 21 17:27:02 node-2 kernel: [    0.810944] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 21 17:27:02 node-2 kernel: [    0.811031] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 21 17:27:02 node-2 kernel: [    0.811035] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 21 17:27:02 node-2 kernel: [    0.811043] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 21 17:27:02 node-2 kernel: [    0.811081] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 21 17:27:02 node-2 kernel: [    0.811082] vesafb: scrolling: redraw
Sep 21 17:27:02 node-2 kernel: [    0.811084] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 21 17:27:02 node-2 kernel: [    0.831989] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 21 17:27:02 node-2 kernel: [    0.840512] Console: switching to colour frame buffer device 80x30
Sep 21 17:27:02 node-2 kernel: [    0.849195] fb0: VESA VGA frame buffer device
Sep 21 17:27:02 node-2 kernel: [    0.849392] intel_idle: MWAIT substates: 0x2120
Sep 21 17:27:02 node-2 kernel: [    0.849393] intel_idle: v0.4 model 0x3F
Sep 21 17:27:02 node-2 kernel: [    0.849394] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 21 17:27:02 node-2 kernel: [    0.849619] ipmi message handler version 39.2
Sep 21 17:27:02 node-2 kernel: [    0.849901] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 21 17:27:02 node-2 kernel: [    0.850341] ACPI: AC Adapter [P111] (on-line)
Sep 21 17:27:02 node-2 kernel: [    0.855606] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 21 17:27:02 node-2 kernel: [    0.866605] ACPI: Power Button [PWRB]
Sep 21 17:27:02 node-2 kernel: [    0.872367] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 21 17:27:02 node-2 kernel: [    0.883989] ACPI: Power Button [PWRF]
Sep 21 17:27:02 node-2 kernel: [    0.901360] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 21 17:27:02 node-2 kernel: [    0.913014] pstore: Registered erst as persistent store backend
Sep 21 17:27:02 node-2 kernel: [    0.919203] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 21 17:27:02 node-2 kernel: [    0.931128] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 21 17:27:02 node-2 kernel: [    0.957862] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 21 17:27:02 node-2 kernel: [    0.991140] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 21 17:27:02 node-2 kernel: [    1.005186] Linux agpgart interface v0.103
Sep 21 17:27:02 node-2 kernel: [    1.012788] brd: module loaded
Sep 21 17:27:02 node-2 kernel: [    1.019838] loop: module loaded
Sep 21 17:27:02 node-2 kernel: [    1.026529] libphy: Fixed MDIO Bus: probed
Sep 21 17:27:02 node-2 kernel: [    1.032964] tun: Universal TUN/TAP device driver, 1.6
Sep 21 17:27:02 node-2 kernel: [    1.039419] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 21 17:27:02 node-2 kernel: [    1.045924] PPP generic driver version 2.4.2
Sep 21 17:27:02 node-2 kernel: [    1.052292] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 21 17:27:02 node-2 kernel: [    1.058716] ehci-pci: EHCI PCI platform driver
Sep 21 17:27:02 node-2 kernel: [    1.065295] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 21 17:27:02 node-2 kernel: [    1.071697] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 21 17:27:02 node-2 kernel: [    1.084312] ehci-pci 0000:00:1a.0: debug port 2
Sep 21 17:27:02 node-2 kernel: [    1.094506] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 21 17:27:02 node-2 kernel: [    1.094524] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 21 17:27:02 node-2 kernel: [    1.111379] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 21 17:27:02 node-2 kernel: [    1.117447] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 21 17:27:02 node-2 kernel: [    1.123617] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 21 17:27:02 node-2 kernel: [    1.135494] usb usb1: Product: EHCI Host Controller
Sep 21 17:27:02 node-2 kernel: [    1.141520] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 21 17:27:02 node-2 kernel: [    1.147546] usb usb1: SerialNumber: 0000:00:1a.0
Sep 21 17:27:02 node-2 kernel: [    1.153482] hub 1-0:1.0: USB hub found
Sep 21 17:27:02 node-2 kernel: [    1.159244] hub 1-0:1.0: 2 ports detected
Sep 21 17:27:02 node-2 kernel: [    1.165023] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 21 17:27:02 node-2 kernel: [    1.170598] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 21 17:27:02 node-2 kernel: [    1.181481] ehci-pci 0000:00:1d.0: debug port 2
Sep 21 17:27:02 node-2 kernel: [    1.190796] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 21 17:27:02 node-2 kernel: [    1.190802] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 21 17:27:02 node-2 kernel: [    1.207297] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 21 17:27:02 node-2 kernel: [    1.212498] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 21 17:27:02 node-2 kernel: [    1.217803] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 21 17:27:02 node-2 kernel: [    1.228397] usb usb2: Product: EHCI Host Controller
Sep 21 17:27:02 node-2 kernel: [    1.233905] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 21 17:27:02 node-2 kernel: [    1.239490] usb usb2: SerialNumber: 0000:00:1d.0
Sep 21 17:27:02 node-2 kernel: [    1.245034] hub 2-0:1.0: USB hub found
Sep 21 17:27:02 node-2 kernel: [    1.250412] hub 2-0:1.0: 2 ports detected
Sep 21 17:27:02 node-2 kernel: [    1.255734] ehci-platform: EHCI generic platform driver
Sep 21 17:27:02 node-2 kernel: [    1.260998] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 21 17:27:02 node-2 kernel: [    1.266332] ohci-pci: OHCI PCI platform driver
Sep 21 17:27:02 node-2 kernel: [    1.271653] ohci-platform: OHCI generic platform driver
Sep 21 17:27:02 node-2 kernel: [    1.276878] uhci_hcd: USB Universal Host Controller Interface driver
Sep 21 17:27:02 node-2 kernel: [    1.282250] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 21 17:27:02 node-2 kernel: [    1.475077] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 21 17:27:02 node-2 kernel: [    1.647289] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 21 17:27:02 node-2 kernel: [    1.652813] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 21 17:27:02 node-2 kernel: [    1.658552] hub 1-1:1.0: USB hub found
Sep 21 17:27:02 node-2 kernel: [    1.664026] hub 1-1:1.0: 6 ports detected
Sep 21 17:27:02 node-2 kernel: [    1.778811] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 21 17:27:02 node-2 kernel: [    1.786810] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 21 17:27:02 node-2 kernel: [    2.046950] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 21 17:27:02 node-2 kernel: [    2.052499] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 21 17:27:02 node-2 kernel: [    2.058343] hub 2-1:1.0: USB hub found
Sep 21 17:27:02 node-2 kernel: [    2.064063] hub 2-1:1.0: 8 ports detected
Sep 21 17:27:02 node-2 kernel: [    2.323644] i8042: No controller found
Sep 21 17:27:02 node-2 kernel: [    2.329082] mousedev: PS/2 mouse device common for all mice
Sep 21 17:27:02 node-2 kernel: [    2.334665] rtc_cmos 00:02: RTC can wake from S4
Sep 21 17:27:02 node-2 kernel: [    2.340340] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 21 17:27:02 node-2 kernel: [    2.342397] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 21 17:27:02 node-2 kernel: [    2.351643] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 21 17:27:02 node-2 kernel: [    2.362881] device-mapper: uevent: version 1.0.3
Sep 21 17:27:02 node-2 kernel: [    2.368544] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 21 17:27:02 node-2 kernel: [    2.379848] ledtrig-cpu: registered to indicate activity on CPUs
Sep 21 17:27:02 node-2 kernel: [    2.385817] TCP: cubic registered
Sep 21 17:27:02 node-2 kernel: [    2.391796] NET: Registered protocol family 10
Sep 21 17:27:02 node-2 kernel: [    2.397858] NET: Registered protocol family 17
Sep 21 17:27:02 node-2 kernel: [    2.403626] Key type dns_resolver registered
Sep 21 17:27:02 node-2 kernel: [    2.409700] Loading compiled-in X.509 certificates
Sep 21 17:27:02 node-2 kernel: [    2.415961] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 21 17:27:02 node-2 kernel: [    2.427532] registered taskstats version 1
Sep 21 17:27:02 node-2 kernel: [    2.435548] Key type trusted registered
Sep 21 17:27:02 node-2 kernel: [    2.443154] Key type encrypted registered
Sep 21 17:27:02 node-2 kernel: [    2.448619] AppArmor: AppArmor sha1 policy hashing enabled
Sep 21 17:27:02 node-2 kernel: [    2.454107] IMA: No TPM chip found, activating TPM-bypass!
Sep 21 17:27:02 node-2 kernel: [    2.460275] regulator-dummy: disabling
Sep 21 17:27:02 node-2 kernel: [    2.465865]   Magic number: 0:774:441
Sep 21 17:27:02 node-2 kernel: [    2.471538] rtc_cmos 00:02: setting system clock to 2016-09-21 17:26:24 UTC (1474478784)
Sep 21 17:27:02 node-2 kernel: [    2.483935] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 21 17:27:02 node-2 kernel: [    2.487400] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 21 17:27:02 node-2 kernel: [    2.487401] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 21 17:27:02 node-2 kernel: [    2.487402] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 21 17:27:02 node-2 kernel: [    2.487402] usb 2-1.4: Manufacturer: Avocent
Sep 21 17:27:02 node-2 kernel: [    2.487403] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 21 17:27:02 node-2 kernel: [    2.524368] EDD information not available.
Sep 21 17:27:02 node-2 kernel: [    2.530017] PM: Hibernation image not present or could not be loaded.
Sep 21 17:27:02 node-2 kernel: [    2.530895] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 21 17:27:02 node-2 kernel: [    2.542226] Write protecting the kernel read-only data: 12288k
Sep 21 17:27:02 node-2 kernel: [    2.548518] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 21 17:27:02 node-2 kernel: [    2.561017] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 21 17:27:02 node-2 kernel: [    2.592717] device-mapper: multipath: version 1.6.0 loaded
Sep 21 17:27:02 node-2 kernel: [    2.600882] systemd-udevd[215]: starting version 204
Sep 21 17:27:02 node-2 kernel: [    2.621438] md: linear personality registered for level -1
Sep 21 17:27:02 node-2 kernel: [    2.636107] md: multipath personality registered for level -4
Sep 21 17:27:02 node-2 kernel: [    2.644071] md: raid0 personality registered for level 0
Sep 21 17:27:02 node-2 kernel: [    2.652447] md: raid1 personality registered for level 1
Sep 21 17:27:02 node-2 kernel: [    2.658839] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 21 17:27:02 node-2 kernel: [    2.665215] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 21 17:27:02 node-2 kernel: [    2.671621] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 21 17:27:02 node-2 kernel: [    2.673082] megasas: FW now in Ready state
Sep 21 17:27:02 node-2 kernel: [    2.673600] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.673733] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.673802] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.673892] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.673980] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.674228] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.674310] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.674405] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.674498] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.674555] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.674636] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.674722] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.674829] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.674930] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.674999] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.675087] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.675728] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 21 17:27:02 node-2 kernel: [    2.697145] hidraw: raw HID events driver (C) Jiri Kosina
Sep 21 17:27:02 node-2 kernel: [    2.705556] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Sep 21 17:27:02 node-2 kernel: [    2.711246] usbcore: registered new interface driver usbhid
Sep 21 17:27:02 node-2 kernel: [    2.711247] usbhid: USB HID core driver
Sep 21 17:27:02 node-2 kernel: [    2.731227] 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
Sep 21 17:27:02 node-2 kernel: [    2.738181] raid6: sse2x1    1381 MB/s
Sep 21 17:27:02 node-2 kernel: [    2.751110] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 21 17:27:02 node-2 kernel: [    2.757933] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.757942] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.757947] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.757953] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.758020] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 21 17:27:02 node-2 kernel: [    2.758125] 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
Sep 21 17:27:02 node-2 kernel: [    2.758457] 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
Sep 21 17:27:02 node-2 kernel: [    2.758666] 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
Sep 21 17:27:02 node-2 kernel: [    2.759138] 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
Sep 21 17:27:02 node-2 kernel: [    2.759414] 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
Sep 21 17:27:02 node-2 kernel: [    2.759858] 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
Sep 21 17:27:02 node-2 kernel: [    2.806240] raid6: sse2x2     595 MB/s
Sep 21 17:27:02 node-2 kernel: [    2.873891] raid6: sse2x4    3175 MB/s
Sep 21 17:27:02 node-2 kernel: [    2.945841] raid6: avx2x1   14961 MB/s
Sep 21 17:27:02 node-2 kernel: [    3.017769] raid6: avx2x2   18859 MB/s
Sep 21 17:27:02 node-2 kernel: [    3.089713] raid6: avx2x4   21210 MB/s
Sep 21 17:27:02 node-2 kernel: [    3.096508] raid6: using algorithm avx2x4 (21210 MB/s)
Sep 21 17:27:02 node-2 kernel: [    3.103240] raid6: using avx2x2 recovery algorithm
Sep 21 17:27:02 node-2 kernel: [    3.109899] megasas:IOC Init cmd success
Sep 21 17:27:02 node-2 kernel: [    3.109902] Switched to clocksource tsc
Sep 21 17:27:02 node-2 kernel: [    3.123715] xor: automatically using best checksumming function:
Sep 21 17:27:02 node-2 kernel: [    3.126291] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Sep 21 17:27:02 node-2 kernel: [    3.126313] 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
Sep 21 17:27:02 node-2 kernel: [    3.126330] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Sep 21 17:27:02 node-2 kernel: [    3.126868] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.127012] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.127103] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.127195] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.127262] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.127327] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.127844] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.145623] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Sep 21 17:27:02 node-2 kernel: [    3.145627] 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
Sep 21 17:27:02 node-2 kernel: [    3.145628] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 21 17:27:02 node-2 kernel: [    3.145972] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.146171] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.146391] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.146597] megasas: INIT adapter done
Sep 21 17:27:02 node-2 kernel: [    3.146597] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.146861] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.163447] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Sep 21 17:27:02 node-2 kernel: [    3.163462] 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
Sep 21 17:27:02 node-2 kernel: [    3.163467] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 21 17:27:02 node-2 kernel: [    3.164098] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.164263] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.164483] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.164714] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.165083] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 21 17:27:02 node-2 kernel: [    3.217653] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 21 17:27:02 node-2 kernel: [    3.219310] scsi0 : LSI SAS based MegaRAID driver
Sep 21 17:27:02 node-2 kernel: [    3.227082] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 21 17:27:02 node-2 kernel: [    3.299055] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 21 17:27:02 node-2 kernel: [    3.315816] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 21 17:27:02 node-2 kernel: [    3.323015] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 21 17:27:02 node-2 kernel: [    3.333538]    avx       : 35704.000 MB/sec
Sep 21 17:27:02 node-2 kernel: [    3.344352] sd 0:2:0:0: [sda] Write Protect is off
Sep 21 17:27:02 node-2 kernel: [    3.351204] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 21 17:27:02 node-2 kernel: [    3.351236] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 21 17:27:02 node-2 kernel: [    3.364966] async_tx: api initialized (async)
Sep 21 17:27:02 node-2 kernel: [    3.375672] md: raid6 personality registered for level 6
Sep 21 17:27:02 node-2 kernel: [    3.382453] md: raid5 personality registered for level 5
Sep 21 17:27:02 node-2 kernel: [    3.389032] md: raid4 personality registered for level 4
Sep 21 17:27:02 node-2 kernel: [    3.396941]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Sep 21 17:27:02 node-2 kernel: [    3.403571] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 21 17:27:02 node-2 kernel: [    3.409794] md: raid10 personality registered for level 10
Sep 21 17:27:02 node-2 kernel: [    3.461913] multipathd (361): /proc/361/oom_adj is deprecated, please use /proc/361/oom_score_adj instead.
Sep 21 17:27:02 node-2 kernel: [    3.580039] random: lvm urandom read with 32 bits of entropy available
Sep 21 17:27:02 node-2 kernel: [    3.693290] bio: create slab <bio-1> at 1
Sep 21 17:27:02 node-2 kernel: [    4.430980] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 21 17:27:02 node-2 kernel: [    5.129156] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 21 17:27:02 node-2 kernel: [    5.155210] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 21 17:27:02 node-2 kernel: [    5.264923] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 21 17:27:02 node-2 kernel: [    5.294589] random: nonblocking pool is initialized
Sep 21 17:27:02 node-2 kernel: [    5.301321] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 21 17:27:02 node-2 kernel: [    5.454971] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 21 17:27:02 node-2 kernel: [    5.612211] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 21 17:27:02 node-2 kernel: [    5.650392] XFS (dm-0): Mounting Filesystem
Sep 21 17:27:02 node-2 kernel: [    5.912227] XFS (dm-0): Ending clean mount
Sep 21 17:27:02 node-2 kernel: [    5.943574] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 21 17:27:02 node-2 kernel: [    5.976518] XFS (dm-1): Mounting Filesystem
Sep 21 17:27:02 node-2 kernel: [    6.150310] XFS (dm-1): Ending clean mount
Sep 21 17:27:02 node-2 kernel: [    7.746669] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 21 17:27:02 node-2 kernel: [    7.760265] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 21 17:27:02 node-2 kernel: [    7.901927] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 21 17:27:02 node-2 kernel: [    7.901932] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 21 17:27:02 node-2 kernel: [    7.901936] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 21 17:27:02 node-2 kernel: [    7.901940] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 21 17:27:02 node-2 kernel: [    7.906094] systemd-udevd[770]: starting version 204
Sep 21 17:27:02 node-2 kernel: [    8.043045] power_meter ACPI000D:00: Found ACPI power meter.
Sep 21 17:27:02 node-2 kernel: [    8.043063] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 21 17:27:02 node-2 kernel: [    8.053129] IPMI System Interface driver.
Sep 21 17:27:02 node-2 kernel: [    8.053186] ipmi_si: probing via ACPI
Sep 21 17:27:02 node-2 kernel: [    8.053198] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 21 17:27:02 node-2 kernel: [    8.053199] ipmi_si: Adding ACPI-specified kcs state machine
Sep 21 17:27:02 node-2 kernel: [    8.053226] ipmi_si: probing via SMBIOS
Sep 21 17:27:02 node-2 kernel: [    8.053227] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 21 17:27:02 node-2 kernel: [    8.053228] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 21 17:27:02 node-2 kernel: [    8.053229] ipmi_si: probing via SPMI
Sep 21 17:27:02 node-2 kernel: [    8.053230] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 21 17:27:02 node-2 kernel: [    8.053231] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 21 17:27:02 node-2 kernel: [    8.053232] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 21 17:27:02 node-2 kernel: [    8.056887] wmi: Mapper loaded
Sep 21 17:27:02 node-2 kernel: [    8.087005] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 21 17:27:02 node-2 kernel: [    8.087010] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 21 17:27:02 node-2 kernel: [    8.087013] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 21 17:27:02 node-2 kernel: [    8.087014] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 21 17:27:02 node-2 kernel: [    8.087055] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 21 17:27:02 node-2 kernel: [    8.093378] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 21 17:27:02 node-2 kernel: [    8.149888] systemd-udevd[789]: renamed network interface eth0 to enp6s0
Sep 21 17:27:02 node-2 kernel: [    8.185784] systemd-udevd[800]: renamed network interface eth1 to enp7s0
Sep 21 17:27:02 node-2 kernel: [    8.191045] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 21 17:27:02 node-2 kernel: [    8.191050] ipmi_si 00:09: IPMI kcs interface initialized
Sep 21 17:27:02 node-2 kernel: [    8.213904] systemd-udevd[794]: renamed network interface eth2 to enp8s0
Sep 21 17:27:02 node-2 kernel: [    8.229844] systemd-udevd[818]: renamed network interface eth3 to enp9s0
Sep 21 17:27:02 node-2 kernel: [    8.520045] type=1400 audit(1474478790.550:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1050 comm="apparmor_parser"
Sep 21 17:27:02 node-2 kernel: [    8.520206] type=1400 audit(1474478790.550:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1050 comm="apparmor_parser"
Sep 21 17:27:02 node-2 kernel: [    8.520339] type=1400 audit(1474478790.550:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1050 comm="apparmor_parser"
Sep 21 17:27:02 node-2 kernel: [    8.524267] type=1400 audit(1474478790.554:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1048 comm="apparmor_parser"
Sep 21 17:27:02 node-2 kernel: [    8.524410] type=1400 audit(1474478790.554:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1048 comm="apparmor_parser"
Sep 21 17:27:02 node-2 kernel: [    8.524533] type=1400 audit(1474478790.554:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1048 comm="apparmor_parser"
Sep 21 17:27:02 node-2 kernel: [    8.529382] type=1400 audit(1474478790.562:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1049 comm="apparmor_parser"
Sep 21 17:27:02 node-2 kernel: [    8.529520] type=1400 audit(1474478790.562:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1049 comm="apparmor_parser"
Sep 21 17:27:02 node-2 kernel: [    8.529641] type=1400 audit(1474478790.562:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1049 comm="apparmor_parser"
Sep 21 17:27:02 node-2 kernel: [    8.533222] type=1400 audit(1474478790.566:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1047 comm="apparmor_parser"
Sep 21 17:27:02 node-2 kernel: [    9.040754] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Sep 21 17:27:02 node-2 kernel: [    9.041392] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Sep 21 17:27:02 node-2 kernel: [    9.230344] enic 0000:06:00.0 enp6s0: Link UP
Sep 21 17:27:02 node-2 kernel: [    9.231564] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 21 17:27:02 node-2 kernel: [    9.231574] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 21 17:27:02 node-2 kernel: [   18.015859] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 21 17:27:02 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 21 17:27:03 node-2 failsafe: Failsafe of 120 seconds reached.
Sep 21 17:27:03 node-2 kernel: [   41.657995] init: failsafe main process (8410) killed by TERM signal
Sep 21 17:27:04 node-2 dbus[8518]: [system] AppArmor D-Bus mediation is enabled
Sep 21 17:27:04 node-2 kernel: [   41.886815] audit_printk_skb: 30 callbacks suppressed
Sep 21 17:27:04 node-2 kernel: [   41.886816] type=1400 audit(1474478824.182:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8528 comm="apparmor_parser"
Sep 21 17:27:04 node-2 kernel: [   41.886820] type=1400 audit(1474478824.182:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8528 comm="apparmor_parser"
Sep 21 17:27:04 node-2 kernel: [   41.886823] type=1400 audit(1474478824.182:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8528 comm="apparmor_parser"
Sep 21 17:27:04 node-2 kernel: [   41.887043] type=1400 audit(1474478824.182:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8528 comm="apparmor_parser"
Sep 21 17:27:04 node-2 kernel: [   41.887044] type=1400 audit(1474478824.182:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8528 comm="apparmor_parser"
Sep 21 17:27:04 node-2 kernel: [   41.887157] type=1400 audit(1474478824.182:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8528 comm="apparmor_parser"
Sep 21 17:27:04 node-2 kernel: [   41.890004] type=1400 audit(1474478824.186:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8529 comm="apparmor_parser"
Sep 21 17:27:04 node-2 kernel: [   41.961620] type=1400 audit(1474478824.258:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8531 comm="apparmor_parser"
Sep 21 17:27:04 node-2 anacron[8607]: Anacron 2.3 started on 2016-09-21
Sep 21 17:27:04 node-2 anacron[8607]: Will run job `cron.daily' in 5 min.
Sep 21 17:27:04 node-2 anacron[8607]: Will run job `cron.weekly' in 10 min.
Sep 21 17:27:04 node-2 anacron[8607]: Will run job `cron.monthly' in 15 min.
Sep 21 17:27:04 node-2 anacron[8607]: Jobs will be executed sequentially
Sep 21 17:27:04 node-2 cron[8568]: (CRON) INFO (pidfile fd = 3)
Sep 21 17:27:04 node-2 multipathd: path checkers start up
Sep 21 17:27:04 node-2 cron[8652]: (CRON) STARTUP (fork ok)
Sep 21 17:27:04 node-2 cron[8652]: (CRON) INFO (Running @reboot jobs)
Sep 21 17:27:04 node-2 postfix/master[8748]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 21 17:27:08 node-2 puppet-agent[8932]: Reopening log files
Sep 21 17:27:08 node-2 puppet-agent[8932]: Could not request certificate: Connection refused - connect(2)
Sep 21 17:27:19 node-2 puppet-user[9140]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 21 17:27:19 node-2 puppet-user[9140]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 21 17:27:20 node-2 puppet-user[9140]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 21 17:27:20 node-2 puppet-user[9140]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 21 17:27:20 node-2 puppet-user[9140]: Finished catalog run in 0.81 seconds
Sep 21 17:27:22 node-2 multipathd: uevent trigger error
Sep 21 17:27:22 node-2 puppet-user[9565]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 21 17:27:22 node-2 puppet-user[9565]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Sep 21 17:27:22 node-2 puppet-user[9565]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 21 17:27:22 node-2 puppet-user[9565]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 21 17:27:22 node-2 puppet-user[9565]: (/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"]'
Sep 21 17:27:22 node-2 puppet-user[9565]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 21 17:27:22 node-2 puppet-user[9565]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 21 17:27:22 node-2 puppet-user[9565]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 21 17:27:22 node-2 puppet-user[9565]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 21 17:27:22 node-2 puppet-user[9565]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 21 17:27:22 node-2 puppet-user[9565]: Finished catalog run in 0.06 seconds
Sep 21 17:27:23 node-2 puppet-user[10027]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 21 17:27:23 node-2 puppet-user[10027]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Sep 21 17:27:24 node-2 puppet-user[10027]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 21 17:27:24 node-2 puppet-user[10027]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 21 17:27:24 node-2 puppet-user[10027]: Finished catalog run in 0.04 seconds
Sep 21 17:27:25 node-2 puppet-user[10495]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 21 17:27:25 node-2 puppet-user[10495]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 21 17:27:25 node-2 puppet-user[10495]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 21 17:27:26 node-2 puppet-user[10495]: Finished catalog run in 0.04 seconds
Sep 21 17:27:27 node-2 puppet-user[10952]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 21 17:27:27 node-2 puppet-user[10952]: Compiled catalog for node-2.domain.tld in environment production in 0.16 seconds
Sep 21 17:27:27 node-2 puppet-user[10952]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 21 17:27:27 node-2 puppet-user[10952]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Sep 21 17:27:28 node-2 puppet-user[10952]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Sep 21 17:27:28 node-2 puppet-user[10952]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Sep 21 17:27:28 node-2 puppet-user[10952]: Finished catalog run in 1.17 seconds
Sep 21 17:27:29 node-2 puppet-user[11667]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 21 17:27:30 node-2 puppet-user[11667]: Compiled catalog for node-2.domain.tld in environment production in 0.23 seconds
Sep 21 17:27:30 node-2 puppet-user[11667]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Sep 21 17:27:30 node-2 puppet-user[11667]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Sep 21 17:27:30 node-2 puppet-user[11667]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 21 17:27:30 node-2 puppet-user[11667]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 21 17:27:30 node-2 puppet-user[11667]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Sep 21 17:27:30 node-2 puppet-user[11667]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 21 17:27:30 node-2 puppet-user[11667]: Finished catalog run in 0.35 seconds
Sep 21 17:27:32 node-2 puppet-user[12150]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 21 17:27:32 node-2 puppet-user[12150]: Compiled catalog for node-2.domain.tld in environment production in 0.14 seconds
Sep 21 17:27:32 node-2 puppet-user[12150]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 21 17:27:32 node-2 kernel: [   70.045564] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 21 17:27:32 node-2 kernel: [   70.045616] 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.
Sep 21 17:27:32 node-2 puppet-user[12150]: (/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'
Sep 21 17:27:32 node-2 puppet-user[12150]: Finished catalog run in 0.09 seconds
Sep 21 17:27:33 node-2 puppet-user[12607]: (Scope(Class[main])) MODULAR: sync_time
Sep 21 17:27:33 node-2 puppet-user[12607]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Sep 21 17:27:34 node-2 ntpdate[13023]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 21 17:27:40 node-2 ntpdate[13023]: adjust time server 10.20.0.2 offset -0.102390 sec
Sep 21 17:27:40 node-2 puppet-user[12607]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 21 17:27:40 node-2 puppet-user[12607]: Finished catalog run in 6.18 seconds
Sep 21 17:27:41 node-2 kernel: [   79.397429] init: plymouth-upstart-bridge main process ended, respawning
Sep 21 17:27:41 node-2 puppet-agent[8932]: Could not run: SIGTERM
Sep 21 17:27:41 node-2 kernel: [   79.659347] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 21 17:27:42 node-2 ec2: 
Sep 21 17:27:42 node-2 ec2: #############################################################
Sep 21 17:27:42 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 21 17:27:42 node-2 ec2: 1024 cd:65:c7:7b:e6:ec:c3:1b:36:df:7f:f1:88:6b:58:97  root@node-2.domain.tld (DSA)
Sep 21 17:27:42 node-2 ec2: 256 5b:fe:9b:b0:6a:cb:28:02:53:cb:ee:ea:dd:3d:41:5a  root@node-2.domain.tld (ECDSA)
Sep 21 17:27:42 node-2 ec2: 256 a2:cf:b1:eb:f4:af:06:8c:f0:13:e3:07:c6:89:be:f0  root@node-2.domain.tld (ED25519)
Sep 21 17:27:42 node-2 ec2: 2048 e4:b1:23:23:17:9a:e8:a7:e1:b8:b5:3e:b1:81:03:1f  root@node-2.domain.tld (RSA)
Sep 21 17:27:42 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 21 17:27:42 node-2 ec2: #############################################################
Sep 21 17:27:46 node-2 puppet-user[13406]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 21 17:27:46 node-2 puppet-user[13406]: Compiled catalog for node-2.domain.tld in environment production in 0.09 seconds
Sep 21 17:27:46 node-2 puppet-user[13406]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 21 17:27:46 node-2 puppet-user[13406]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Sep 21 17:27:46 node-2 puppet-user[13406]: Finished catalog run in 0.08 seconds
Sep 21 17:27:47 node-2 puppet-user[13864]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 21 17:27:48 node-2 puppet-user[13864]: Compiled catalog for node-2.domain.tld in environment production in 0.48 seconds
Sep 21 17:27:48 node-2 puppet-user[13864]: (/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
Sep 21 17:27:48 node-2 puppet-user[13864]: (/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
Sep 21 17:27:48 node-2 puppet-user[13864]: (/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
Sep 21 17:27:48 node-2 puppet-user[13864]: (/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
Sep 21 17:27:48 node-2 puppet-user[13864]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 21 17:27:48 node-2 puppet-user[13864]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 21 17:27:48 node-2 puppet-user[13864]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 21 17:27:48 node-2 puppet-user[13864]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 21 17:27:48 node-2 puppet-user[13864]: (/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
Sep 21 17:27:48 node-2 puppet-user[13864]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 21 17:27:49 node-2 puppet-user[13864]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Sep 21 17:27:49 node-2 puppet-user[13864]: Finished catalog run in 0.89 seconds
Sep 21 17:27:50 node-2 puppet-user[14379]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 21 17:27:50 node-2 puppet-user[14379]: Compiled catalog for node-2.domain.tld in environment production in 0.12 seconds
Sep 21 17:27:54 node-2 puppet-user[14379]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 21 17:28:01 node-2 CRON[16161]: (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")
Sep 21 17:28:18 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 21 17:28:18 node-2 nailgun-agent: I, [2016-09-21T17:28:18.670058 #16164]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 21 17:28:20 node-2 puppet-user[14379]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 21 17:28:21 node-2 puppet-user[14379]: Finished catalog run in 29.97 seconds
Sep 21 17:28:23 node-2 puppet-user[17340]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 21 17:28:23 node-2 puppet-user[17340]: Compiled catalog for node-2.domain.tld in environment production in 0.58 seconds
Sep 21 17:28:23 node-2 puppet-user[17340]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 21 17:28:23 node-2 puppet-user[17340]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 21 17:28:23 node-2 puppet-user[17340]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 21 17:28:23 node-2 puppet-user[17340]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 21 17:28:23 node-2 puppet-user[17340]: Finished catalog run in 0.12 seconds
Sep 21 17:28:25 node-2 puppet-user[17803]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 21 17:28:26 node-2 puppet-user[17803]: Compiled catalog for node-2.domain.tld in environment production in 0.87 seconds
Sep 21 17:28:26 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 21 17:28:26 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 21 17:28:26 node-2 crontab[18244]: (root) LIST (root)
Sep 21 17:28:26 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 21 17:28:26 node-2 crontab[18245]: (root) REPLACE (root)
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 21 17:28:28 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/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
Sep 21 17:28:29 node-2 puppet-user[17803]: (/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
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/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
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/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
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/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
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/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
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/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
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/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
Sep 21 17:28:29 node-2 puppet-user[17803]: (/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
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 21 17:28:29 node-2 puppet-user[17803]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 21 17:28:29 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8383" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 21 17:28:29 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 21 17:28:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:44 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:44 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:44 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:44 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:46 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:46 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:46 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:46 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:46 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:28:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:29:43 node-2 ntpdate[28643]: no servers can be used, exiting
<27>Sep 21 17:30:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:15 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:17 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:17 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:17 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:17 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:17 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 17:30:33 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:34 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:34 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:34 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:34 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:34 node-2 multipathd: uevent trigger error
<27>Sep 21 17:31:37 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 21 17:31:37 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 21 17:31:43 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 21 17:31:43 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 21 17:31:48 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 21 17:31:54 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 21 17:31:54 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 21 17:32:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:03 node-2 ntpdate[12754]: the NTP socket is in use, exiting
<27>Sep 21 17:32:13 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:13 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:13 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:13 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:13 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:13 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:13 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:32:45 node-2 multipathd: uevent trigger error
<129>Sep 21 17:32:47 node-2 haproxy[21344]: Server odl-neutron-endpoint/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 17:32:47 node-2 haproxy[21344]: proxy odl-neutron-endpoint has no server available!
<129>Sep 21 17:32:48 node-2 haproxy[21349]: Server odl-jetty/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 57ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 21 17:32:48 node-2 haproxy[21349]: proxy odl-jetty has no server available!
<27>Sep 21 17:33:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:11 node-2 multipathd: uevent trigger error
<129>Sep 21 17:33:13 node-2 haproxy[23593]: 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>Sep 21 17:33:13 node-2 haproxy[23593]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:14 node-2 haproxy[23599]: 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>Sep 21 17:33:14 node-2 haproxy[23599]: proxy mysqld has no server available!
<27>Sep 21 17:33:16 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:16 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:16 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:16 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:16 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:19 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:19 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:19 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:19 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:19 node-2 multipathd: uevent trigger error
<129>Sep 21 17:33:22 node-2 haproxy[26048]: 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>Sep 21 17:33:22 node-2 haproxy[26048]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:22 node-2 haproxy[26048]: 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>Sep 21 17:33:22 node-2 haproxy[26048]: proxy mysqld has no server available!
<129>Sep 21 17:33:22 node-2 haproxy[26048]: 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>Sep 21 17:33:23 node-2 haproxy[26052]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:23 node-2 haproxy[26052]: 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>Sep 21 17:33:23 node-2 haproxy[26052]: proxy object-storage has no server available!
<27>Sep 21 17:33:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:25 node-2 multipathd: uevent trigger error
<129>Sep 21 17:33:27 node-2 haproxy[27276]: 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>Sep 21 17:33:27 node-2 haproxy[27276]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:27 node-2 haproxy[27276]: 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>Sep 21 17:33:27 node-2 haproxy[27276]: proxy neutron has no server available!
<129>Sep 21 17:33:27 node-2 haproxy[27276]: 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>Sep 21 17:33:28 node-2 haproxy[27283]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:28 node-2 haproxy[27283]: 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>Sep 21 17:33:28 node-2 haproxy[27283]: proxy mysqld has no server available!
<129>Sep 21 17:33:28 node-2 haproxy[27283]: 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>Sep 21 17:33:28 node-2 haproxy[27283]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:28 node-2 haproxy[27283]: 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>Sep 21 17:33:28 node-2 haproxy[27283]: proxy object-storage has no server available!
<27>Sep 21 17:33:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:30 node-2 multipathd: uevent trigger error
<129>Sep 21 17:33:32 node-2 haproxy[28550]: 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>Sep 21 17:33:32 node-2 haproxy[28550]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:32 node-2 haproxy[28550]: 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>Sep 21 17:33:32 node-2 haproxy[28550]: proxy keystone-1 has no server available!
<129>Sep 21 17:33:32 node-2 haproxy[28550]: 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>Sep 21 17:33:33 node-2 haproxy[28556]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:33 node-2 haproxy[28556]: 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>Sep 21 17:33:33 node-2 haproxy[28556]: proxy keystone-2 has no server available!
<129>Sep 21 17:33:33 node-2 haproxy[28556]: 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>Sep 21 17:33:33 node-2 haproxy[28556]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:33 node-2 haproxy[28556]: 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>Sep 21 17:33:33 node-2 haproxy[28556]: proxy neutron has no server available!
<129>Sep 21 17:33:33 node-2 haproxy[28556]: 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>Sep 21 17:33:33 node-2 haproxy[28556]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:33 node-2 haproxy[28556]: 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>Sep 21 17:33:33 node-2 haproxy[28556]: proxy mysqld has no server available!
<129>Sep 21 17:33:34 node-2 haproxy[28556]: 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>Sep 21 17:33:34 node-2 haproxy[28556]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:34 node-2 haproxy[28556]: 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>Sep 21 17:33:34 node-2 haproxy[28556]: proxy object-storage has no server available!
<27>Sep 21 17:33:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:35 node-2 multipathd: uevent trigger error
<129>Sep 21 17:33:37 node-2 haproxy[29928]: 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>Sep 21 17:33:37 node-2 haproxy[29928]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:37 node-2 haproxy[29928]: 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>Sep 21 17:33:37 node-2 haproxy[29928]: proxy keystone-1 has no server available!
<129>Sep 21 17:33:37 node-2 haproxy[29928]: 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>Sep 21 17:33:38 node-2 haproxy[29932]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:38 node-2 haproxy[29932]: 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>Sep 21 17:33:38 node-2 haproxy[29932]: proxy keystone-2 has no server available!
<129>Sep 21 17:33:38 node-2 haproxy[29932]: 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>Sep 21 17:33:38 node-2 haproxy[29932]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:38 node-2 haproxy[29932]: 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>Sep 21 17:33:38 node-2 haproxy[29932]: proxy neutron has no server available!
<129>Sep 21 17:33:38 node-2 haproxy[29932]: 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>Sep 21 17:33:38 node-2 haproxy[29932]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:38 node-2 haproxy[29932]: 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>Sep 21 17:33:38 node-2 haproxy[29932]: proxy mysqld has no server available!
<129>Sep 21 17:33:38 node-2 haproxy[29932]: 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>Sep 21 17:33:38 node-2 haproxy[29932]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:39 node-2 haproxy[29932]: 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>Sep 21 17:33:39 node-2 haproxy[29932]: proxy object-storage has no server available!
<129>Sep 21 17:33:39 node-2 haproxy[29932]: 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>Sep 21 17:33:39 node-2 haproxy[29932]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:39 node-2 haproxy[29932]: 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>Sep 21 17:33:39 node-2 haproxy[29932]: proxy aodh has no server available!
<27>Sep 21 17:33:41 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:41 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:41 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:41 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:41 node-2 multipathd: uevent trigger error
<129>Sep 21 17:33:43 node-2 haproxy[31159]: 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>Sep 21 17:33:43 node-2 haproxy[31159]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:43 node-2 haproxy[31159]: 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>Sep 21 17:33:43 node-2 haproxy[31159]: proxy keystone-1 has no server available!
<129>Sep 21 17:33:43 node-2 haproxy[31159]: 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>Sep 21 17:33:43 node-2 haproxy[31159]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:43 node-2 haproxy[31159]: 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>Sep 21 17:33:43 node-2 haproxy[31159]: proxy keystone-2 has no server available!
<129>Sep 21 17:33:43 node-2 haproxy[31159]: 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>Sep 21 17:33:43 node-2 haproxy[31159]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:43 node-2 haproxy[31159]: 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>Sep 21 17:33:43 node-2 haproxy[31159]: proxy neutron has no server available!
<129>Sep 21 17:33:44 node-2 haproxy[31164]: 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>Sep 21 17:33:44 node-2 haproxy[31164]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:44 node-2 haproxy[31164]: 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>Sep 21 17:33:44 node-2 haproxy[31164]: proxy mysqld has no server available!
<129>Sep 21 17:33:44 node-2 haproxy[31164]: 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>Sep 21 17:33:44 node-2 haproxy[31164]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:44 node-2 haproxy[31164]: 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>Sep 21 17:33:44 node-2 haproxy[31164]: proxy object-storage has no server available!
<129>Sep 21 17:33:44 node-2 haproxy[31164]: 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>Sep 21 17:33:44 node-2 haproxy[31164]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:44 node-2 haproxy[31164]: 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>Sep 21 17:33:44 node-2 haproxy[31164]: proxy aodh has no server available!
<129>Sep 21 17:33:44 node-2 haproxy[31164]: 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>Sep 21 17:33:44 node-2 haproxy[31164]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:44 node-2 haproxy[31164]: 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>Sep 21 17:33:44 node-2 haproxy[31164]: proxy ceilometer has no server available!
<27>Sep 21 17:33:46 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:46 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:46 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:46 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:46 node-2 multipathd: uevent trigger error
<129>Sep 21 17:33:48 node-2 haproxy[32379]: 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>Sep 21 17:33:48 node-2 haproxy[32379]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:48 node-2 haproxy[32379]: 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>Sep 21 17:33:48 node-2 haproxy[32379]: proxy keystone-1 has no server available!
<129>Sep 21 17:33:48 node-2 haproxy[32379]: 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>Sep 21 17:33:48 node-2 haproxy[32379]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:49 node-2 haproxy[32383]: 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>Sep 21 17:33:49 node-2 haproxy[32383]: proxy keystone-2 has no server available!
<129>Sep 21 17:33:49 node-2 haproxy[32383]: 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>Sep 21 17:33:49 node-2 haproxy[32383]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:49 node-2 haproxy[32383]: 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>Sep 21 17:33:49 node-2 haproxy[32383]: proxy neutron has no server available!
<129>Sep 21 17:33:49 node-2 haproxy[32383]: 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>Sep 21 17:33:49 node-2 haproxy[32383]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:49 node-2 haproxy[32383]: 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>Sep 21 17:33:49 node-2 haproxy[32383]: proxy mysqld has no server available!
<129>Sep 21 17:33:49 node-2 haproxy[32383]: 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>Sep 21 17:33:49 node-2 haproxy[32383]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:49 node-2 haproxy[32383]: 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>Sep 21 17:33:49 node-2 haproxy[32383]: proxy object-storage has no server available!
<129>Sep 21 17:33:49 node-2 haproxy[32383]: 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>Sep 21 17:33:49 node-2 haproxy[32383]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:50 node-2 haproxy[32383]: 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>Sep 21 17:33:50 node-2 haproxy[32383]: proxy aodh has no server available!
<129>Sep 21 17:33:50 node-2 haproxy[32383]: 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>Sep 21 17:33:50 node-2 haproxy[32383]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:50 node-2 haproxy[32383]: 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>Sep 21 17:33:50 node-2 haproxy[32383]: proxy ceilometer has no server available!
<27>Sep 21 17:33:52 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:52 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:52 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:52 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:52 node-2 multipathd: uevent trigger error
<129>Sep 21 17:33:54 node-2 haproxy[1181]: 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>Sep 21 17:33:54 node-2 haproxy[1181]: 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>Sep 21 17:33:55 node-2 haproxy[1188]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:55 node-2 haproxy[1188]: 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>Sep 21 17:33:55 node-2 haproxy[1188]: proxy keystone-1 has no server available!
<129>Sep 21 17:33:55 node-2 haproxy[1188]: 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>Sep 21 17:33:55 node-2 haproxy[1188]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:55 node-2 haproxy[1188]: 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>Sep 21 17:33:55 node-2 haproxy[1188]: proxy keystone-2 has no server available!
<129>Sep 21 17:33:55 node-2 haproxy[1188]: 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>Sep 21 17:33:55 node-2 haproxy[1188]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:55 node-2 haproxy[1188]: 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>Sep 21 17:33:55 node-2 haproxy[1188]: proxy neutron has no server available!
<129>Sep 21 17:33:55 node-2 haproxy[1188]: 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>Sep 21 17:33:55 node-2 haproxy[1188]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:55 node-2 haproxy[1188]: 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>Sep 21 17:33:55 node-2 haproxy[1188]: proxy mysqld has no server available!
<129>Sep 21 17:33:55 node-2 haproxy[1188]: 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>Sep 21 17:33:55 node-2 haproxy[1188]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:56 node-2 haproxy[1188]: 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>Sep 21 17:33:56 node-2 haproxy[1188]: proxy object-storage has no server available!
<129>Sep 21 17:33:56 node-2 haproxy[1188]: 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>Sep 21 17:33:56 node-2 haproxy[1188]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:56 node-2 haproxy[1188]: 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>Sep 21 17:33:56 node-2 haproxy[1188]: proxy aodh has no server available!
<129>Sep 21 17:33:56 node-2 haproxy[1188]: 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>Sep 21 17:33:56 node-2 haproxy[1188]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:33:56 node-2 haproxy[1188]: 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>Sep 21 17:33:56 node-2 haproxy[1188]: proxy ceilometer has no server available!
<27>Sep 21 17:33:57 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:57 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:57 node-2 multipathd: uevent trigger error
<27>Sep 21 17:33:57 node-2 multipathd: uevent trigger error
<129>Sep 21 17:34:00 node-2 haproxy[2550]: 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>Sep 21 17:34:00 node-2 haproxy[2550]: 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>Sep 21 17:34:00 node-2 haproxy[2550]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:00 node-2 haproxy[2550]: 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>Sep 21 17:34:00 node-2 haproxy[2550]: proxy keystone-1 has no server available!
<129>Sep 21 17:34:00 node-2 haproxy[2550]: 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>Sep 21 17:34:00 node-2 haproxy[2550]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:00 node-2 haproxy[2550]: 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>Sep 21 17:34:00 node-2 haproxy[2550]: proxy keystone-2 has no server available!
<129>Sep 21 17:34:00 node-2 haproxy[2550]: 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>Sep 21 17:34:00 node-2 haproxy[2550]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: proxy glance-api has no server available!
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: proxy glance-glare has no server available!
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: proxy neutron has no server available!
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: proxy glance-registry has no server available!
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: proxy mysqld has no server available!
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: proxy object-storage has no server available!
<129>Sep 21 17:34:01 node-2 haproxy[2554]: 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>Sep 21 17:34:01 node-2 haproxy[2554]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:02 node-2 haproxy[2554]: 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>Sep 21 17:34:02 node-2 haproxy[2554]: proxy aodh has no server available!
<129>Sep 21 17:34:02 node-2 haproxy[2554]: 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>Sep 21 17:34:02 node-2 haproxy[2554]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:02 node-2 haproxy[2554]: 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>Sep 21 17:34:02 node-2 haproxy[2554]: proxy ceilometer has no server available!
<27>Sep 21 17:34:03 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:03 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:03 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:03 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:03 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:06 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: proxy keystone-1 has no server available!
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: proxy keystone-2 has no server available!
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: proxy nova-api has no server available!
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: proxy nova-metadata-api has no server available!
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: proxy glance-api has no server available!
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:06 node-2 haproxy[3915]: 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>Sep 21 17:34:06 node-2 haproxy[3915]: proxy glance-glare has no server available!
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: proxy neutron has no server available!
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: proxy glance-registry has no server available!
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: proxy mysqld has no server available!
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: proxy object-storage has no server available!
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: proxy aodh has no server available!
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: proxy ceilometer has no server available!
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:07 node-2 haproxy[3929]: 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>Sep 21 17:34:07 node-2 haproxy[3929]: proxy nova-novncproxy has no server available!
<27>Sep 21 17:34:09 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:09 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:09 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:09 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:09 node-2 multipathd: uevent trigger error
<129>Sep 21 17:34:11 node-2 haproxy[5243]: 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>Sep 21 17:34:11 node-2 haproxy[5243]: 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>Sep 21 17:34:11 node-2 haproxy[5243]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:11 node-2 haproxy[5243]: 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>Sep 21 17:34:11 node-2 haproxy[5243]: proxy keystone-1 has no server available!
<129>Sep 21 17:34:11 node-2 haproxy[5243]: 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>Sep 21 17:34:11 node-2 haproxy[5243]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:11 node-2 haproxy[5243]: 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>Sep 21 17:34:11 node-2 haproxy[5243]: proxy keystone-2 has no server available!
<129>Sep 21 17:34:11 node-2 haproxy[5243]: 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>Sep 21 17:34:11 node-2 haproxy[5243]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:11 node-2 haproxy[5243]: 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>Sep 21 17:34:11 node-2 haproxy[5243]: proxy nova-api has no server available!
<129>Sep 21 17:34:11 node-2 haproxy[5243]: 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>Sep 21 17:34:11 node-2 haproxy[5243]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:11 node-2 haproxy[5243]: 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>Sep 21 17:34:11 node-2 haproxy[5243]: proxy nova-metadata-api has no server available!
<129>Sep 21 17:34:11 node-2 haproxy[5243]: 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>Sep 21 17:34:11 node-2 haproxy[5243]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: proxy cinder-api has no server available!
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: proxy glance-api has no server available!
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: proxy glance-glare has no server available!
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: proxy neutron has no server available!
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: proxy glance-registry has no server available!
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: proxy mysqld has no server available!
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: proxy object-storage has no server available!
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:12 node-2 haproxy[5247]: proxy aodh has no server available!
<129>Sep 21 17:34:12 node-2 haproxy[5247]: 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>Sep 21 17:34:13 node-2 haproxy[5247]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:13 node-2 haproxy[5247]: 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>Sep 21 17:34:13 node-2 haproxy[5247]: proxy ceilometer has no server available!
<129>Sep 21 17:34:13 node-2 haproxy[5247]: 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>Sep 21 17:34:13 node-2 haproxy[5247]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:13 node-2 haproxy[5247]: 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>Sep 21 17:34:13 node-2 haproxy[5247]: proxy nova-novncproxy has no server available!
<27>Sep 21 17:34:13 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 21 17:34:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:14 node-2 multipathd: uevent trigger error
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: proxy keystone-1 has no server available!
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: proxy keystone-2 has no server available!
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: proxy nova-api has no server available!
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: proxy nova-metadata-api has no server available!
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: proxy cinder-api has no server available!
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: proxy glance-api has no server available!
<129>Sep 21 17:34:17 node-2 haproxy[6917]: 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>Sep 21 17:34:17 node-2 haproxy[6917]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: proxy glance-glare has no server available!
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: proxy neutron has no server available!
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: proxy glance-registry has no server available!
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: proxy mysqld has no server available!
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: proxy object-storage has no server available!
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: proxy aodh has no server available!
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: proxy ceilometer has no server available!
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: proxy heat-api has no server available!
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: proxy heat-api-cfn has no server available!
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:18 node-2 haproxy[6934]: 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>Sep 21 17:34:18 node-2 haproxy[6934]: proxy heat-api-cloudwatch has no server available!
<129>Sep 21 17:34:19 node-2 haproxy[6934]: 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>Sep 21 17:34:19 node-2 haproxy[6934]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 21 17:34:19 node-2 haproxy[6934]: 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>Sep 21 17:34:19 node-2 haproxy[6934]: proxy nova-novncproxy has no server available!
<27>Sep 21 17:34:20 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:20 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:20 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:20 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:20 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:34:30 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 21 17:34:54 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>Sep 21 17:34:56 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 21 17:35:47 node-2 multipathd: uevent trigger error
<27>Sep 21 17:35:47 node-2 multipathd: uevent trigger error
<27>Sep 21 17:35:47 node-2 multipathd: uevent trigger error
<27>Sep 21 17:35:47 node-2 multipathd: uevent trigger error
<27>Sep 21 17:37:27 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 17:38:06 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:06 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:06 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:06 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:16 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:16 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:16 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:16 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:16 node-2 multipathd: uevent trigger error
<43>Sep 21 17:38:30 node-2 apache2_error [Wed Sep 21 17:38:28.159531 2016] [mpm_event:notice] [pid 18525:tid 140347179153280] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 21 17:38:30 node-2 apache2_error [Wed Sep 21 17:38:28.159632 2016] [core:notice] [pid 18525:tid 140347179153280] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 21 17:38:30 node-2 apache2_error [Wed Sep 21 17:38:30.144789 2016] [mpm_event:notice] [pid 18525:tid 140347179153280] AH00491: caught SIGTERM, shutting down
<27>Sep 21 17:38:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:38 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:38 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:38 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:38 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:38 node-2 multipathd: uevent trigger error
<27>Sep 21 17:38:38 node-2 multipathd: uevent trigger error
<43>Sep 21 17:38:40 node-2 apache2_error [Wed Sep 21 17:38:31.235151 2016] [mpm_worker:notice] [pid 18897:tid 139909334935424] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 21 17:38:40 node-2 apache2_error [Wed Sep 21 17:38:31.235234 2016] [core:notice] [pid 18897:tid 139909334935424] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 21 17:39:40 node-2 apache2_error [Wed Sep 21 17:39:40.124057 2016] [mpm_worker:notice] [pid 18897:tid 139909334935424] AH00295: caught SIGTERM, shutting down
<43>Sep 21 17:39:50 node-2 apache2_error [Wed Sep 21 17:39:40.907559 2016] [mpm_worker:notice] [pid 30890:tid 140067274696576] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 21 17:39:50 node-2 apache2_error [Wed Sep 21 17:39:40.907604 2016] [core:notice] [pid 30890:tid 140067274696576] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 21 17:40:29 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 21 17:40:30 node-2 apache2_error [Wed Sep 21 17:40:24.837331 2016] [mpm_worker:notice] [pid 30890:tid 140067274696576] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 21 17:40:30 node-2 apache2_error [Wed Sep 21 17:40:25.033738 2016] [mpm_worker:warn] [pid 30890:tid 140067274696576] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 21 17:40:30 node-2 apache2_error [Wed Sep 21 17:40:25.037616 2016] [mpm_worker:notice] [pid 30890:tid 140067274696576] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 21 17:40:30 node-2 apache2_error [Wed Sep 21 17:40:25.037640 2016] [core:notice] [pid 30890:tid 140067274696576] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 21 17:41:09 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:09 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:09 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:09 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:09 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:14 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:30 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:48 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:53 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:53 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:53 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:53 node-2 multipathd: uevent trigger error
<27>Sep 21 17:41:53 node-2 multipathd: uevent trigger error
<27>Sep 21 17:42:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:42:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:42:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:42:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:43:00 node-2 multipathd: uevent trigger error
<27>Sep 21 17:43:00 node-2 multipathd: uevent trigger error
<27>Sep 21 17:43:00 node-2 multipathd: uevent trigger error
<27>Sep 21 17:43:00 node-2 multipathd: uevent trigger error
<27>Sep 21 17:43:00 node-2 multipathd: uevent trigger error
<27>Sep 21 17:43:31 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 17:44:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:44:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:44:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:44:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:44:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:08 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:08 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:08 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:08 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:08 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:08 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:08 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:31 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:36 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:36 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:36 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:36 node-2 multipathd: uevent trigger error
<27>Sep 21 17:45:36 node-2 multipathd: uevent trigger error
<27>Sep 21 17:46:33 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 17:47:58 node-2 multipathd: uevent trigger error
<27>Sep 21 17:47:58 node-2 multipathd: uevent trigger error
<27>Sep 21 17:47:58 node-2 multipathd: uevent trigger error
<27>Sep 21 17:47:58 node-2 multipathd: uevent trigger error
<27>Sep 21 17:47:58 node-2 multipathd: uevent trigger error
<27>Sep 21 17:47:58 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:12 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:18 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:18 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:18 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:18 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:23 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:44 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:44 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:44 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:44 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:44 node-2 multipathd: uevent trigger error
<27>Sep 21 17:48:44 node-2 multipathd: uevent trigger error
<27>Sep 21 17:49:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:49:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:49:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:49:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:49:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:49:35 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 17:50:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:11 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:26 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:42 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:42 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:42 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:42 node-2 multipathd: uevent trigger error
<27>Sep 21 17:50:42 node-2 multipathd: uevent trigger error
<27>Sep 21 17:52:36 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 17:53:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:35 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:53:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:20 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:21 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:21 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:21 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:21 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:24 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:29 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:29 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:29 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:29 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:47 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:47 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:47 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:47 node-2 multipathd: uevent trigger error
<27>Sep 21 17:54:47 node-2 multipathd: uevent trigger error
<27>Sep 21 17:55:19 node-2 multipathd: uevent trigger error
<27>Sep 21 17:55:19 node-2 multipathd: uevent trigger error
<27>Sep 21 17:55:19 node-2 multipathd: uevent trigger error
<27>Sep 21 17:55:19 node-2 multipathd: uevent trigger error
<27>Sep 21 17:55:37 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Sep 21 17:56:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:56:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:56:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:56:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:56:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:56:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:56:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:56:40 node-2 multipathd: uevent trigger error
<27>Sep 21 17:56:40 node-2 multipathd: uevent trigger error
<11>Sep 21 17:56:53 node-2 liberasurecode[5937]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:53 node-2 liberasurecode[5937]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:53 node-2 liberasurecode[5937]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:53 node-2 liberasurecode[5937]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:54 node-2 liberasurecode[5961]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:54 node-2 liberasurecode[5961]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:54 node-2 liberasurecode[5961]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:54 node-2 liberasurecode[5961]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:55 node-2 liberasurecode[6755]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:55 node-2 liberasurecode[6755]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:55 node-2 liberasurecode[6755]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:56:55 node-2 liberasurecode[6755]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8886]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8886]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8886]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8886]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8922]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8922]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8922]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8922]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8968]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8968]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8968]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[8968]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9180]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9180]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9180]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9180]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9196]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9196]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9196]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9196]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9208]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9208]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9208]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9208]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9243]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9243]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9243]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:00 node-2 liberasurecode[9243]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:17 node-2 liberasurecode[10042]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:17 node-2 liberasurecode[10042]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:17 node-2 liberasurecode[10042]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 17:57:17 node-2 liberasurecode[10042]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 21 17:57:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:57:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:57:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:57:25 node-2 multipathd: uevent trigger error
<27>Sep 21 17:57:25 node-2 multipathd: uevent trigger error
<43>Sep 21 17:58:12 node-2 apache2_error [Wed Sep 21 17:58:11.806609 2016] [mpm_worker:notice] [pid 30890:tid 140067274696576] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 21 17:58:12 node-2 apache2_error [Wed Sep 21 17:58:12.191721 2016] [mpm_worker:warn] [pid 30890:tid 140067274696576] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 21 17:58:12 node-2 apache2_error [Wed Sep 21 17:58:12.196941 2016] [mpm_worker:notice] [pid 30890:tid 140067274696576] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 21 17:58:12 node-2 apache2_error [Wed Sep 21 17:58:12.196964 2016] [core:notice] [pid 30890:tid 140067274696576] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 21 17:58:39 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Sep 21 17:58:52 node-2 apache2_error [Wed Sep 21 17:58:49.293588 2016] [mpm_worker:notice] [pid 30890:tid 140067274696576] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 21 17:58:52 node-2 apache2_error [Wed Sep 21 17:58:49.488861 2016] [mpm_worker:warn] [pid 30890:tid 140067274696576] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 21 17:58:52 node-2 apache2_error [Wed Sep 21 17:58:49.497206 2016] [mpm_worker:notice] [pid 30890:tid 140067274696576] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 21 17:58:52 node-2 apache2_error [Wed Sep 21 17:58:49.497240 2016] [core:notice] [pid 30890:tid 140067274696576] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 21 17:58:53 node-2 multipathd: uevent trigger error
<27>Sep 21 17:58:53 node-2 multipathd: uevent trigger error
<27>Sep 21 17:58:53 node-2 multipathd: uevent trigger error
<27>Sep 21 17:58:53 node-2 multipathd: uevent trigger error
<27>Sep 21 17:58:53 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:01 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:39 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:39 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:39 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:39 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:39 node-2 multipathd: uevent trigger error
<43>Sep 21 17:59:42 node-2 apache2_error [Wed Sep 21 17:59:35.230813 2016] [mpm_worker:notice] [pid 30890:tid 140067274696576] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 21 17:59:42 node-2 apache2_error [Wed Sep 21 17:59:35.617388 2016] [mpm_worker:warn] [pid 30890:tid 140067274696576] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 21 17:59:42 node-2 apache2_error [Wed Sep 21 17:59:35.628339 2016] [mpm_worker:notice] [pid 30890:tid 140067274696576] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 21 17:59:42 node-2 apache2_error [Wed Sep 21 17:59:35.628374 2016] [core:notice] [pid 30890:tid 140067274696576] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 21 17:59:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:45 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:51 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:51 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:51 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:51 node-2 multipathd: uevent trigger error
<27>Sep 21 17:59:51 node-2 multipathd: uevent trigger error
<11>Sep 21 18:00:01 node-2 liberasurecode[7307]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 18:00:01 node-2 liberasurecode[7307]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 18:00:01 node-2 liberasurecode[7307]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 18:00:01 node-2 liberasurecode[7307]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 21 18:00:08 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:08 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:08 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:08 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:28 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:34 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:34 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:34 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:34 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:40 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 21 18:00:49 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:49 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:49 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:49 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:49 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:54 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:54 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:54 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:54 node-2 multipathd: uevent trigger error
<27>Sep 21 18:00:54 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:00 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:00 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:00 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:00 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:13 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:13 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:13 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:13 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:13 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:16 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 21 18:01:26 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:26 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:26 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:26 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:42 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:42 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:42 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:42 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:42 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:46 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:46 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:46 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:46 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:59 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:59 node-2 multipathd: uevent trigger error
<27>Sep 21 18:01:59 node-2 multipathd: uevent trigger error
<27>Sep 21 18:02:00 node-2 multipathd: uevent trigger error
<27>Sep 21 18:02:00 node-2 multipathd: uevent trigger error
<27>Sep 21 18:02:04 node-2 multipathd: uevent trigger error
<27>Sep 21 18:02:04 node-2 multipathd: uevent trigger error
<27>Sep 21 18:02:04 node-2 multipathd: uevent trigger error
<27>Sep 21 18:02:04 node-2 multipathd: uevent trigger error
<27>Sep 21 18:02:04 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:21 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:21 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:21 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:21 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:21 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:35 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:35 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:35 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:35 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:35 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:40 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:40 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:40 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:40 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:40 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:45 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:45 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:45 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:45 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:52 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:52 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:52 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:52 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:52 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:52 node-2 multipathd: uevent trigger error
<129>Sep 21 18:03:53 node-2 haproxy[6934]: 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.
<27>Sep 21 18:03:57 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:57 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:57 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:57 node-2 multipathd: uevent trigger error
<27>Sep 21 18:03:57 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:01 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:01 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:01 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:01 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:01 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:05 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:05 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:05 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:05 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:05 node-2 multipathd: uevent trigger error
<27>Sep 21 18:04:12 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 21 18:04:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:15 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:20 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:21 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:27 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 21 18:04:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:32 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:35 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:36 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:39 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 21 18:04:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:39 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:41 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:42 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:44 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:51 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 21 18:04:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:51 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:53 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:56 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:04:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:00 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<11>Sep 21 18:05:01 node-2 liberasurecode[12327]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 18:05:01 node-2 liberasurecode[12327]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 18:05:01 node-2 liberasurecode[12327]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 21 18:05:01 node-2 liberasurecode[12327]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 21 18:05:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:03 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 21 18:05:03 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:03 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:12 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:13 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:14 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:15 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 21 18:05:15 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:16 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:17 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:18 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:19 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:21 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:22 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:23 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:24 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:25 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:26 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:27 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 21 18:05:27 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:28 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:29 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:33 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:34 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:35 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:36 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:37 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:38 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:40 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 21 18:05:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:40 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:41 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:41 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:43 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:44 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:45 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:46 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:47 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:48 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:49 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:50 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:52 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 21 18:05:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:52 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:53 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:53 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:54 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:55 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:56 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:57 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:58 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:05:59 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:00 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:01 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:02 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:04 node-2 ovs-vsctl: ovs|00002|vsctl|ERR|no bridge named br-ex
<27>Sep 21 18:06:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:04 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:05 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:06 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:07 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:08 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:09 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:10 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
<27>Sep 21 18:06:11 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "qg-8857b4e9-ea" in table Interface
