Oct 23 09:24:06 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8389" x-info="http://www.rsyslog.com"] start
Oct 23 09:24:06 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Oct 23 09:24:06 node-2 rsyslogd: rsyslogd's groupid changed to 104
Oct 23 09:24:06 node-2 rsyslogd: rsyslogd's userid changed to 101
Oct 23 09:24:06 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Oct 23 09:24:06 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Oct 23 09:24:06 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Oct 23 09:24:06 node-2 kernel: [    0.000000] Linux version 3.13.0-98-generic (buildd@lgw01-45) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #145-Ubuntu SMP Sat Oct 8 20:13:07 UTC 2016 (Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39)
Oct 23 09:24:06 node-2 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-98-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=1119c54a-1b16-4572-8342-77ea08f012ea nomdmonddf nomdmonisw
Oct 23 09:24:06 node-2 kernel: [    0.000000] KERNEL supported cpus:
Oct 23 09:24:06 node-2 kernel: [    0.000000]   Intel GenuineIntel
Oct 23 09:24:06 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Oct 23 09:24:06 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Oct 23 09:24:06 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 23 09:24:06 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Oct 23 09:24:06 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Oct 23 09:24:06 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Oct 23 09:24:06 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
Oct 23 09:24:06 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Oct 23 09:24:06 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Oct 23 09:24:06 node-2 kernel: [    0.000000] No AGP bridge found
Oct 23 09:24:06 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Oct 23 09:24:06 node-2 kernel: [    0.000000] MTRR default type: write-back
Oct 23 09:24:06 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Oct 23 09:24:06 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Oct 23 09:24:06 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Oct 23 09:24:06 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Oct 23 09:24:06 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Oct 23 09:24:06 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Oct 23 09:24:06 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Oct 23 09:24:06 node-2 kernel: [    0.000000]   2 disabled
Oct 23 09:24:06 node-2 kernel: [    0.000000]   3 disabled
Oct 23 09:24:06 node-2 kernel: [    0.000000]   4 disabled
Oct 23 09:24:06 node-2 kernel: [    0.000000]   5 disabled
Oct 23 09:24:06 node-2 kernel: [    0.000000]   6 disabled
Oct 23 09:24:06 node-2 kernel: [    0.000000]   7 disabled
Oct 23 09:24:06 node-2 kernel: [    0.000000]   8 disabled
Oct 23 09:24:06 node-2 kernel: [    0.000000]   9 disabled
Oct 23 09:24:06 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Oct 23 09:24:06 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Oct 23 09:24:06 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Oct 23 09:24:06 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Oct 23 09:24:06 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Oct 23 09:24:06 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Oct 23 09:24:06 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Oct 23 09:24:06 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Oct 23 09:24:06 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Oct 23 09:24:06 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Oct 23 09:24:06 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Oct 23 09:24:06 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Oct 23 09:24:06 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Oct 23 09:24:06 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Oct 23 09:24:06 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Oct 23 09:24:06 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Oct 23 09:24:06 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Oct 23 09:24:06 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Oct 23 09:24:06 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Oct 23 09:24:06 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Oct 23 09:24:06 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Oct 23 09:24:06 node-2 kernel: [    0.000000] Zone ranges:
Oct 23 09:24:06 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] Movable zone start for each node
Oct 23 09:24:06 node-2 kernel: [    0.000000] Early memory node ranges
Oct 23 09:24:06 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Oct 23 09:24:06 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Oct 23 09:24:06 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Oct 23 09:24:06 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Oct 23 09:24:06 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Oct 23 09:24:06 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Oct 23 09:24:06 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Oct 23 09:24:06 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Oct 23 09:24:06 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Oct 23 09:24:06 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Oct 23 09:24:06 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Oct 23 09:24:06 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Oct 23 09:24:06 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Oct 23 09:24:06 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Oct 23 09:24:06 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Oct 23 09:24:06 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Oct 23 09:24:06 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Oct 23 09:24:06 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Oct 23 09:24:06 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Oct 23 09:24:06 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Oct 23 09:24:06 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Oct 23 09:24:06 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Oct 23 09:24:06 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Oct 23 09:24:06 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 
Oct 23 09:24:06 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Oct 23 09:24:06 node-2 kernel: [    0.000000] Policy zone: Normal
Oct 23 09:24:06 node-2 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-98-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=1119c54a-1b16-4572-8342-77ea08f012ea nomdmonddf nomdmonisw
Oct 23 09:24:06 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Oct 23 09:24:06 node-2 kernel: [    0.000000] Checking aperture...
Oct 23 09:24:06 node-2 kernel: [    0.000000] No AGP bridge found
Oct 23 09:24:06 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Oct 23 09:24:06 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Oct 23 09:24:06 node-2 kernel: [    0.000000] Memory: 32653320K/33280496K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627176K reserved)
Oct 23 09:24:06 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Oct 23 09:24:06 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Oct 23 09:24:06 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Oct 23 09:24:06 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Oct 23 09:24:06 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Oct 23 09:24:06 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Oct 23 09:24:06 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Oct 23 09:24:06 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Oct 23 09:24:06 node-2 kernel: [    0.000000] console [tty0] enabled
Oct 23 09:24:06 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Oct 23 09:24:06 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Oct 23 09:24:06 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Oct 23 09:24:06 node-2 kernel: [    0.000000] hpet clockevent registered
Oct 23 09:24:06 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Oct 23 09:24:06 node-2 kernel: [    0.004000] tsc: Detected 3491.891 MHz processor
Oct 23 09:24:06 node-2 kernel: [    0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.78 BogoMIPS (lpj=13967564)
Oct 23 09:24:06 node-2 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Oct 23 09:24:06 node-2 kernel: [    0.000042] Security Framework initialized
Oct 23 09:24:06 node-2 kernel: [    0.000060] AppArmor: AppArmor initialized
Oct 23 09:24:06 node-2 kernel: [    0.000062] Yama: becoming mindful.
Oct 23 09:24:06 node-2 kernel: [    0.001477] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.006363] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.008289] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.008317] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.008603] Initializing cgroup subsys memory
Oct 23 09:24:06 node-2 kernel: [    0.008612] Initializing cgroup subsys devices
Oct 23 09:24:06 node-2 kernel: [    0.008613] Initializing cgroup subsys freezer
Oct 23 09:24:06 node-2 kernel: [    0.008615] Initializing cgroup subsys blkio
Oct 23 09:24:06 node-2 kernel: [    0.008616] Initializing cgroup subsys perf_event
Oct 23 09:24:06 node-2 kernel: [    0.008619] Initializing cgroup subsys hugetlb
Oct 23 09:24:06 node-2 kernel: [    0.008639] CPU: Physical Processor ID: 0
Oct 23 09:24:06 node-2 kernel: [    0.008640] CPU: Processor Core ID: 0
Oct 23 09:24:06 node-2 kernel: [    0.008644] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 23 09:24:06 node-2 kernel: [    0.008644] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Oct 23 09:24:06 node-2 kernel: [    0.009337] mce: CPU supports 22 MCE banks
Oct 23 09:24:06 node-2 kernel: [    0.009365] CPU0: Thermal monitoring enabled (TM1)
Oct 23 09:24:06 node-2 kernel: [    0.009385] process: using mwait in idle threads
Oct 23 09:24:06 node-2 kernel: [    0.009389] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Oct 23 09:24:06 node-2 kernel: [    0.009389] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Oct 23 09:24:06 node-2 kernel: [    0.009389] tlb_flushall_shift: 6
Oct 23 09:24:06 node-2 kernel: [    0.009478] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Oct 23 09:24:06 node-2 kernel: [    0.010202] ACPI: Core revision 20131115
Oct 23 09:24:06 node-2 kernel: [    0.023010] ACPI: All ACPI Tables successfully acquired
Oct 23 09:24:06 node-2 kernel: [    0.023168] ftrace: allocating 28622 entries in 112 pages
Oct 23 09:24:06 node-2 kernel: [    0.031921] dmar: Host address width 46
Oct 23 09:24:06 node-2 kernel: [    0.031923] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Oct 23 09:24:06 node-2 kernel: [    0.031929] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 23 09:24:06 node-2 kernel: [    0.031931] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Oct 23 09:24:06 node-2 kernel: [    0.031935] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Oct 23 09:24:06 node-2 kernel: [    0.031937] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Oct 23 09:24:06 node-2 kernel: [    0.031938] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Oct 23 09:24:06 node-2 kernel: [    0.031939] dmar: ATSR flags: 0x0
Oct 23 09:24:06 node-2 kernel: [    0.031940] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Oct 23 09:24:06 node-2 kernel: [    0.031941] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Oct 23 09:24:06 node-2 kernel: [    0.032056] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Oct 23 09:24:06 node-2 kernel: [    0.032057] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Oct 23 09:24:06 node-2 kernel: [    0.032058] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Oct 23 09:24:06 node-2 kernel: [    0.032060] HPET id 0 under DRHD base 0xc7ffc000
Oct 23 09:24:06 node-2 kernel: [    0.032061] Your BIOS is broken and requested that x2apic be disabled.
Oct 23 09:24:06 node-2 kernel: [    0.032061] This will slightly decrease performance.
Oct 23 09:24:06 node-2 kernel: [    0.032061] Use 'intremap=no_x2apic_optout' to override BIOS request.
Oct 23 09:24:06 node-2 kernel: [    0.032493] Enabled IRQ remapping in xapic mode
Oct 23 09:24:06 node-2 kernel: [    0.032494] x2apic not enabled, IRQ remapping is in xapic mode
Oct 23 09:24:06 node-2 kernel: [    0.032498] Switched APIC routing to physical flat.
Oct 23 09:24:06 node-2 kernel: [    0.033126] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Oct 23 09:24:06 node-2 kernel: [    0.072775] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Oct 23 09:24:06 node-2 kernel: [    0.072780] TSC deadline timer enabled
Oct 23 09:24:06 node-2 kernel: [    0.072788] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Oct 23 09:24:06 node-2 kernel: [    0.072794] ... version:                3
Oct 23 09:24:06 node-2 kernel: [    0.072795] ... bit width:              48
Oct 23 09:24:06 node-2 kernel: [    0.072796] ... generic registers:      4
Oct 23 09:24:06 node-2 kernel: [    0.072797] ... value mask:             0000ffffffffffff
Oct 23 09:24:06 node-2 kernel: [    0.072798] ... max period:             0000ffffffffffff
Oct 23 09:24:06 node-2 kernel: [    0.072799] ... fixed-purpose events:   3
Oct 23 09:24:06 node-2 kernel: [    0.072800] ... event mask:             000000070000000f
Oct 23 09:24:06 node-2 kernel: [    0.074211] x86: Booting SMP configuration:
Oct 23 09:24:06 node-2 kernel: [    0.088315] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Oct 23 09:24:06 node-2 kernel: [    0.074213] .... node  #0, CPUs:        #1  #2  #3
Oct 23 09:24:06 node-2 kernel: [    0.116235] .... node  #1, CPUs:    #4  #5  #6  #7
Oct 23 09:24:06 node-2 kernel: [    0.270392] .... node  #0, CPUs:    #8  #9 #10 #11
Oct 23 09:24:06 node-2 kernel: [    0.326058] .... node  #1, CPUs:   #12 #13 #14 #15
Oct 23 09:24:06 node-2 kernel: [    0.382923] x86: Booted up 2 nodes, 16 CPUs
Oct 23 09:24:06 node-2 kernel: [    0.382926] smpboot: Total of 16 processors activated (111753.09 BogoMIPS)
Oct 23 09:24:06 node-2 kernel: [    0.406095] devtmpfs: initialized
Oct 23 09:24:06 node-2 kernel: [    0.408544] EVM: security.selinux
Oct 23 09:24:06 node-2 kernel: [    0.408545] EVM: security.SMACK64
Oct 23 09:24:06 node-2 kernel: [    0.408546] EVM: security.ima
Oct 23 09:24:06 node-2 kernel: [    0.408547] EVM: security.capability
Oct 23 09:24:06 node-2 kernel: [    0.408598] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.409253] pinctrl core: initialized pinctrl subsystem
Oct 23 09:24:06 node-2 kernel: [    0.409316] regulator-dummy: no parameters
Oct 23 09:24:06 node-2 kernel: [    0.409348] RTC time:  9:23:31, date: 10/23/16
Oct 23 09:24:06 node-2 kernel: [    0.409382] NET: Registered protocol family 16
Oct 23 09:24:06 node-2 kernel: [    0.409467] cpuidle: using governor ladder
Oct 23 09:24:06 node-2 kernel: [    0.409468] cpuidle: using governor menu
Oct 23 09:24:06 node-2 kernel: [    0.409502] ACPI: bus type PCI registered
Oct 23 09:24:06 node-2 kernel: [    0.409504] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Oct 23 09:24:06 node-2 kernel: [    0.409549] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Oct 23 09:24:06 node-2 kernel: [    0.409551] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Oct 23 09:24:06 node-2 kernel: [    0.423291] PCI: Using configuration type 1 for base access
Oct 23 09:24:06 node-2 kernel: [    0.424299] bio: create slab <bio-0> at 0
Oct 23 09:24:06 node-2 kernel: [    0.424580] ACPI: Added _OSI(Module Device)
Oct 23 09:24:06 node-2 kernel: [    0.424581] ACPI: Added _OSI(Processor Device)
Oct 23 09:24:06 node-2 kernel: [    0.424583] ACPI: Added _OSI(3.0 _SCP Extensions)
Oct 23 09:24:06 node-2 kernel: [    0.424584] ACPI: Added _OSI(Processor Aggregator Device)
Oct 23 09:24:06 node-2 kernel: [    0.437284] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Oct 23 09:24:06 node-2 kernel: [    0.447801] ACPI: Interpreter enabled
Oct 23 09:24:06 node-2 kernel: [    0.447807] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Oct 23 09:24:06 node-2 kernel: [    0.447811] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Oct 23 09:24:06 node-2 kernel: [    0.447813] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Oct 23 09:24:06 node-2 kernel: [    0.447820] ACPI: (supports S0 S4 S5)
Oct 23 09:24:06 node-2 kernel: [    0.447821] ACPI: Using IOAPIC for interrupt routing
Oct 23 09:24:06 node-2 kernel: [    0.447864] HEST: Table parsing has been initialized.
Oct 23 09:24:06 node-2 kernel: [    0.447868] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Oct 23 09:24:06 node-2 kernel: [    0.448424] ACPI: No dock devices found.
Oct 23 09:24:06 node-2 kernel: [    0.459931] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Oct 23 09:24:06 node-2 kernel: [    0.459935] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 23 09:24:06 node-2 kernel: [    0.459939] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 23 09:24:06 node-2 kernel: [    0.459967] PCI host bridge to bus 0000:ff
Oct 23 09:24:06 node-2 kernel: [    0.459969] pci_bus 0000:ff: root bus resource [bus ff]
Oct 23 09:24:06 node-2 kernel: [    0.459978] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460016] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.460046] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460081] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460111] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.460140] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.460171] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460200] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460230] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460258] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460284] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460310] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460338] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460364] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460391] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460417] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460446] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460474] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460500] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.460528] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460554] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.460579] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460605] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460634] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.460668] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460699] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460728] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460759] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460789] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460820] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460850] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460882] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460911] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460942] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.460974] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461005] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461038] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461067] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461094] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461126] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461160] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461195] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461229] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461262] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461290] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461320] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461349] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461379] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461410] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461440] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461471] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461500] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461528] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461556] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461585] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461615] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461646] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461702] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Oct 23 09:24:06 node-2 kernel: [    0.461705] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 23 09:24:06 node-2 kernel: [    0.461708] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Oct 23 09:24:06 node-2 kernel: [    0.461725] PCI host bridge to bus 0000:7f
Oct 23 09:24:06 node-2 kernel: [    0.461727] pci_bus 0000:7f: root bus resource [bus 7f]
Oct 23 09:24:06 node-2 kernel: [    0.461732] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461759] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.461787] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461816] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461838] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.461862] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.461887] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461914] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461936] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461959] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.461981] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462003] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462026] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462048] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462077] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462105] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462127] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462151] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462175] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.462201] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462223] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.462244] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462267] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462292] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Oct 23 09:24:06 node-2 kernel: [    0.462324] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462350] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462376] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462402] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462427] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462453] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462478] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462506] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462530] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462557] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462585] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462612] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462641] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462667] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462692] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462720] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462745] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462771] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462801] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462830] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462857] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462883] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462909] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462935] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462962] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.462989] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.463019] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.463044] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.463066] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.463091] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.463115] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.463147] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.463173] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.464429] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Oct 23 09:24:06 node-2 kernel: [    0.464432] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 23 09:24:06 node-2 kernel: [    0.465559] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 23 09:24:06 node-2 kernel: [    0.466070] PCI host bridge to bus 0000:00
Oct 23 09:24:06 node-2 kernel: [    0.466073] pci_bus 0000:00: root bus resource [bus 00-7e]
Oct 23 09:24:06 node-2 kernel: [    0.466074] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Oct 23 09:24:06 node-2 kernel: [    0.466076] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Oct 23 09:24:06 node-2 kernel: [    0.466077] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Oct 23 09:24:06 node-2 kernel: [    0.466078] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Oct 23 09:24:06 node-2 kernel: [    0.466080] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Oct 23 09:24:06 node-2 kernel: [    0.466081] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Oct 23 09:24:06 node-2 kernel: [    0.466087] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Oct 23 09:24:06 node-2 kernel: [    0.466171] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.466201] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.466243] pci 0000:00:01.0: System wakeup disabled by ACPI
Oct 23 09:24:06 node-2 kernel: [    0.466263] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.466292] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.466332] pci 0000:00:02.0: System wakeup disabled by ACPI
Oct 23 09:24:06 node-2 kernel: [    0.466349] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.466378] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.466422] pci 0000:00:03.0: System wakeup disabled by ACPI
Oct 23 09:24:06 node-2 kernel: [    0.466440] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.466510] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.466587] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.466664] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Oct 23 09:24:06 node-2 kernel: [    0.466669] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Oct 23 09:24:06 node-2 kernel: [    0.466754] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Oct 23 09:24:06 node-2 kernel: [    0.466903] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Oct 23 09:24:06 node-2 kernel: [    0.466920] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Oct 23 09:24:06 node-2 kernel: [    0.466998] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.467051] pci 0000:00:1a.0: System wakeup disabled by ACPI
Oct 23 09:24:06 node-2 kernel: [    0.467073] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.467129] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.467172] pci 0000:00:1c.0: System wakeup disabled by ACPI
Oct 23 09:24:06 node-2 kernel: [    0.467201] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.467256] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.467299] pci 0000:00:1c.7: System wakeup disabled by ACPI
Oct 23 09:24:06 node-2 kernel: [    0.467324] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Oct 23 09:24:06 node-2 kernel: [    0.467342] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Oct 23 09:24:06 node-2 kernel: [    0.467419] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.467469] pci 0000:00:1d.0: System wakeup disabled by ACPI
Oct 23 09:24:06 node-2 kernel: [    0.467494] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Oct 23 09:24:06 node-2 kernel: [    0.467741] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Oct 23 09:24:06 node-2 kernel: [    0.467747] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Oct 23 09:24:06 node-2 kernel: [    0.467753] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.467759] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.467766] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Oct 23 09:24:06 node-2 kernel: [    0.467796] pci 0000:01:00.0: supports D1 D2
Oct 23 09:24:06 node-2 kernel: [    0.478082] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 23 09:24:06 node-2 kernel: [    0.478084] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 23 09:24:06 node-2 kernel: [    0.478086] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 23 09:24:06 node-2 kernel: [    0.478194] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.478227] pci 0000:02:00.0: PME# supported from D0 D3hot
Oct 23 09:24:06 node-2 kernel: [    0.486095] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 23 09:24:06 node-2 kernel: [    0.486098] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.486099] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 23 09:24:06 node-2 kernel: [    0.486154] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.486236] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.486311] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.486357] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 23 09:24:06 node-2 kernel: [    0.486361] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.486362] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 23 09:24:06 node-2 kernel: [    0.486417] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.486540] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.486598] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 23 09:24:06 node-2 kernel: [    0.486601] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.486603] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 23 09:24:06 node-2 kernel: [    0.486652] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.486770] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.486813] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.486932] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.486971] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.487093] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.487131] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Oct 23 09:24:06 node-2 kernel: [    0.487270] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Oct 23 09:24:06 node-2 kernel: [    0.487314] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 23 09:24:06 node-2 kernel: [    0.487316] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.487318] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 23 09:24:06 node-2 kernel: [    0.487378] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Oct 23 09:24:06 node-2 kernel: [    0.487441] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.487493] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.487535] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Oct 23 09:24:06 node-2 kernel: [    0.487619] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Oct 23 09:24:06 node-2 kernel: [    0.487725] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 23 09:24:06 node-2 kernel: [    0.487728] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.487730] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 23 09:24:06 node-2 kernel: [    0.487785] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Oct 23 09:24:06 node-2 kernel: [    0.487839] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.487887] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.488100] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 23 09:24:06 node-2 kernel: [    0.488104] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 23 09:24:06 node-2 kernel: [    0.488169] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Oct 23 09:24:06 node-2 kernel: [    0.488238] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.488285] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.488493] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 23 09:24:06 node-2 kernel: [    0.488497] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 23 09:24:06 node-2 kernel: [    0.488556] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Oct 23 09:24:06 node-2 kernel: [    0.488617] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.488672] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Oct 23 09:24:06 node-2 kernel: [    0.488895] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 23 09:24:06 node-2 kernel: [    0.488898] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 23 09:24:06 node-2 kernel: [    0.489073] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 23 09:24:06 node-2 kernel: [    0.489111] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 23 09:24:06 node-2 kernel: [    0.489186] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Oct 23 09:24:06 node-2 kernel: [    0.489205] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Oct 23 09:24:06 node-2 kernel: [    0.489218] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Oct 23 09:24:06 node-2 kernel: [    0.489231] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Oct 23 09:24:06 node-2 kernel: [    0.489282] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Oct 23 09:24:06 node-2 kernel: [    0.494095] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 23 09:24:06 node-2 kernel: [    0.494104] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 23 09:24:06 node-2 kernel: [    0.494156] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Oct 23 09:24:06 node-2 kernel: [    0.494739] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Oct 23 09:24:06 node-2 kernel: [    0.494742] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Oct 23 09:24:06 node-2 kernel: [    0.494867] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Oct 23 09:24:06 node-2 kernel: [    0.494974] PCI host bridge to bus 0000:80
Oct 23 09:24:06 node-2 kernel: [    0.494976] pci_bus 0000:80: root bus resource [bus 80-fe]
Oct 23 09:24:06 node-2 kernel: [    0.494978] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Oct 23 09:24:06 node-2 kernel: [    0.494979] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Oct 23 09:24:06 node-2 kernel: [    0.494987] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.495050] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.495118] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Oct 23 09:24:06 node-2 kernel: [    0.495180] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Oct 23 09:24:06 node-2 kernel: [    0.495185] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Oct 23 09:24:06 node-2 kernel: [    0.495260] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Oct 23 09:24:06 node-2 kernel: [    0.495559] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Oct 23 09:24:06 node-2 kernel: [    0.495590] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Oct 23 09:24:06 node-2 kernel: [    0.495620] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Oct 23 09:24:06 node-2 kernel: [    0.495649] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Oct 23 09:24:06 node-2 kernel: [    0.495678] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 23 09:24:06 node-2 kernel: [    0.495708] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 23 09:24:06 node-2 kernel: [    0.495738] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 23 09:24:06 node-2 kernel: [    0.495768] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Oct 23 09:24:06 node-2 kernel: [    0.495852] ACPI: Enabled 3 GPEs in block 00 to 3F
Oct 23 09:24:06 node-2 kernel: [    0.495857] ACPI: \_SB_.UNC1: notify handler is installed
Oct 23 09:24:06 node-2 kernel: [    0.495858] ACPI: \_SB_.UNC0: notify handler is installed
Oct 23 09:24:06 node-2 kernel: [    0.495873] ACPI: \_SB_.PCI0: notify handler is installed
Oct 23 09:24:06 node-2 kernel: [    0.495925] ACPI: \_SB_.PCI1: notify handler is installed
Oct 23 09:24:06 node-2 kernel: [    0.496005] Found 4 acpi root devices
Oct 23 09:24:06 node-2 kernel: [    0.496112] vgaarb: setting as boot device: PCI:0000:0c:00.0
Oct 23 09:24:06 node-2 kernel: [    0.496114] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Oct 23 09:24:06 node-2 kernel: [    0.496116] vgaarb: loaded
Oct 23 09:24:06 node-2 kernel: [    0.496117] vgaarb: bridge control possible 0000:0c:00.0
Oct 23 09:24:06 node-2 kernel: [    0.496233] SCSI subsystem initialized
Oct 23 09:24:06 node-2 kernel: [    0.496299] libata version 3.00 loaded.
Oct 23 09:24:06 node-2 kernel: [    0.496314] ACPI: bus type USB registered
Oct 23 09:24:06 node-2 kernel: [    0.496324] usbcore: registered new interface driver usbfs
Oct 23 09:24:06 node-2 kernel: [    0.496329] usbcore: registered new interface driver hub
Oct 23 09:24:06 node-2 kernel: [    0.496353] usbcore: registered new device driver usb
Oct 23 09:24:06 node-2 kernel: [    0.496524] PCI: Using ACPI for IRQ routing
Oct 23 09:24:06 node-2 kernel: [    0.500121] PCI: pci_cache_line_size set to 64 bytes
Oct 23 09:24:06 node-2 kernel: [    0.500345] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Oct 23 09:24:06 node-2 kernel: [    0.500347] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Oct 23 09:24:06 node-2 kernel: [    0.500347] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Oct 23 09:24:06 node-2 kernel: [    0.500410] NetLabel: Initializing
Oct 23 09:24:06 node-2 kernel: [    0.500412] NetLabel:  domain hash size = 128
Oct 23 09:24:06 node-2 kernel: [    0.500413] NetLabel:  protocols = UNLABELED CIPSOv4
Oct 23 09:24:06 node-2 kernel: [    0.500423] NetLabel:  unlabeled traffic allowed by default
Oct 23 09:24:06 node-2 kernel: [    0.500490] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Oct 23 09:24:06 node-2 kernel: [    0.500494] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Oct 23 09:24:06 node-2 kernel: [    0.502566] Switched to clocksource hpet
Oct 23 09:24:06 node-2 kernel: [    0.507092] AppArmor: AppArmor Filesystem Enabled
Oct 23 09:24:06 node-2 kernel: [    0.507130] pnp: PnP ACPI init
Oct 23 09:24:06 node-2 kernel: [    0.507142] ACPI: bus type PNP registered
Oct 23 09:24:06 node-2 kernel: [    0.507323] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Oct 23 09:24:06 node-2 kernel: [    0.507334] pnp 00:01: [dma 4]
Oct 23 09:24:06 node-2 kernel: [    0.507352] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Oct 23 09:24:06 node-2 kernel: [    0.507387] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Oct 23 09:24:06 node-2 kernel: [    0.507412] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Oct 23 09:24:06 node-2 kernel: [    0.507434] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Oct 23 09:24:06 node-2 kernel: [    0.507482] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Oct 23 09:24:06 node-2 kernel: [    0.507594] system 00:06: [io  0x0500-0x057f] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507597] system 00:06: [io  0x0400-0x047f] could not be reserved
Oct 23 09:24:06 node-2 kernel: [    0.507598] system 00:06: [io  0x0580-0x059f] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507600] system 00:06: [io  0x0600-0x061f] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507601] system 00:06: [io  0x0880-0x0883] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507603] system 00:06: [io  0x0800-0x081f] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507606] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Oct 23 09:24:06 node-2 kernel: [    0.507608] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507610] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507611] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507613] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507614] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507616] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Oct 23 09:24:06 node-2 kernel: [    0.507618] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Oct 23 09:24:06 node-2 kernel: [    0.507718] pnp 00:07: [dma 0 disabled]
Oct 23 09:24:06 node-2 kernel: [    0.507751] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 23 09:24:06 node-2 kernel: [    0.507833] pnp 00:08: [dma 0 disabled]
Oct 23 09:24:06 node-2 kernel: [    0.507871] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Oct 23 09:24:06 node-2 kernel: [    0.507929] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Oct 23 09:24:06 node-2 kernel: [    0.508374] pnp: PnP ACPI: found 10 devices
Oct 23 09:24:06 node-2 kernel: [    0.508376] ACPI: bus type PNP unregistered
Oct 23 09:24:06 node-2 kernel: [    0.514380] pci 0000:00:01.0: PCI bridge to [bus 01]
Oct 23 09:24:06 node-2 kernel: [    0.514384] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Oct 23 09:24:06 node-2 kernel: [    0.514387] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Oct 23 09:24:06 node-2 kernel: [    0.514392] pci 0000:05:00.0: PCI bridge to [bus 06]
Oct 23 09:24:06 node-2 kernel: [    0.514394] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.514409] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514438] pci 0000:05:01.0: PCI bridge to [bus 07]
Oct 23 09:24:06 node-2 kernel: [    0.514453] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514482] pci 0000:05:02.0: PCI bridge to [bus 08]
Oct 23 09:24:06 node-2 kernel: [    0.514496] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Oct 23 09:24:06 node-2 kernel: [    0.514528] pci 0000:05:03.0: PCI bridge to [bus 09]
Oct 23 09:24:06 node-2 kernel: [    0.514545] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Oct 23 09:24:06 node-2 kernel: [    0.514574] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Oct 23 09:24:06 node-2 kernel: [    0.514576] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.514591] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514620] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Oct 23 09:24:06 node-2 kernel: [    0.514622] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.514636] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514665] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Oct 23 09:24:06 node-2 kernel: [    0.514667] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.514670] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514675] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Oct 23 09:24:06 node-2 kernel: [    0.514677] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.514680] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514684] pci 0000:00:03.0: PCI bridge to [bus 0a]
Oct 23 09:24:06 node-2 kernel: [    0.514690] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Oct 23 09:24:06 node-2 kernel: [    0.514699] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Oct 23 09:24:06 node-2 kernel: [    0.514702] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Oct 23 09:24:06 node-2 kernel: [    0.514709] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Oct 23 09:24:06 node-2 kernel: [    0.514710] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Oct 23 09:24:06 node-2 kernel: [    0.514711] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Oct 23 09:24:06 node-2 kernel: [    0.514712] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Oct 23 09:24:06 node-2 kernel: [    0.514713] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Oct 23 09:24:06 node-2 kernel: [    0.514714] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Oct 23 09:24:06 node-2 kernel: [    0.514715] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Oct 23 09:24:06 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Oct 23 09:24:06 node-2 kernel: [    0.514716] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Oct 23 09:24:06 node-2 kernel: [    0.514717] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.514718] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514719] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.514720] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514721] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.514722] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514723] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.514724] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514725] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Oct 23 09:24:06 node-2 kernel: [    0.514726] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514727] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Oct 23 09:24:06 node-2 kernel: [    0.514728] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Oct 23 09:24:06 node-2 kernel: [    0.514729] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Oct 23 09:24:06 node-2 kernel: [    0.514731] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Oct 23 09:24:06 node-2 kernel: [    0.514733] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Oct 23 09:24:06 node-2 kernel: [    0.514734] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Oct 23 09:24:06 node-2 kernel: [    0.514775] NET: Registered protocol family 2
Oct 23 09:24:06 node-2 kernel: [    0.515068] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.515444] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.515611] TCP: Hash tables configured (established 262144 bind 65536)
Oct 23 09:24:06 node-2 kernel: [    0.515653] TCP: reno registered
Oct 23 09:24:06 node-2 kernel: [    0.515683] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.515790] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.515953] NET: Registered protocol family 1
Oct 23 09:24:06 node-2 kernel: [    0.554652] pci 0000:0c:00.0: Video device with shadowed ROM
Oct 23 09:24:06 node-2 kernel: [    0.554667] PCI: CLS 64 bytes, default 64
Oct 23 09:24:06 node-2 kernel: [    0.554754] Trying to unpack rootfs image as initramfs...
Oct 23 09:24:06 node-2 kernel: [    0.776709] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Oct 23 09:24:06 node-2 kernel: [    0.776743] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Oct 23 09:24:06 node-2 kernel: [    0.776746] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Oct 23 09:24:06 node-2 kernel: [    0.777158] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777171] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777185] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777197] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777208] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777215] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777221] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777228] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777237] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777259] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777267] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777274] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777281] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777288] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777293] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777299] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Oct 23 09:24:06 node-2 kernel: [    0.777346] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Oct 23 09:24:06 node-2 kernel: [    0.777349] Scanning for low memory corruption every 60 seconds
Oct 23 09:24:06 node-2 kernel: [    0.777629] Initialise system trusted keyring
Oct 23 09:24:06 node-2 kernel: [    0.777675] audit: initializing netlink socket (disabled)
Oct 23 09:24:06 node-2 kernel: [    0.777685] type=2000 audit(1477214610.728:1): initialized
Oct 23 09:24:06 node-2 kernel: [    0.795418] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Oct 23 09:24:06 node-2 kernel: [    0.796904] zbud: loaded
Oct 23 09:24:06 node-2 kernel: [    0.797035] VFS: Disk quotas dquot_6.5.2
Oct 23 09:24:06 node-2 kernel: [    0.797072] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Oct 23 09:24:06 node-2 kernel: [    0.797428] fuse init (API version 7.22)
Oct 23 09:24:06 node-2 kernel: [    0.797480] msgmni has been set to 32768
Oct 23 09:24:06 node-2 kernel: [    0.797527] Key type big_key registered
Oct 23 09:24:06 node-2 kernel: [    0.798021] Key type asymmetric registered
Oct 23 09:24:06 node-2 kernel: [    0.798022] Asymmetric key parser 'x509' registered
Oct 23 09:24:06 node-2 kernel: [    0.798045] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Oct 23 09:24:06 node-2 kernel: [    0.798116] io scheduler noop registered
Oct 23 09:24:06 node-2 kernel: [    0.798117] io scheduler deadline registered (default)
Oct 23 09:24:06 node-2 kernel: [    0.798137] io scheduler cfq registered
Oct 23 09:24:06 node-2 kernel: [    0.798670] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    0.798841] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    0.798960] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    0.799076] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    0.799204] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    0.799294] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    0.799658] aer 0000:00:01.0:pcie02: service driver aer loaded
Oct 23 09:24:06 node-2 kernel: [    0.799683] aer 0000:00:02.0:pcie02: service driver aer loaded
Oct 23 09:24:06 node-2 kernel: [    0.799700] aer 0000:00:03.0:pcie02: service driver aer loaded
Oct 23 09:24:06 node-2 kernel: [    0.799713] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799715] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799718] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Oct 23 09:24:06 node-2 kernel: [    0.799723] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799724] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799726] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799727] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799728] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799730] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799731] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799732] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799734] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799735] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799736] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799738] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799740] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Oct 23 09:24:06 node-2 kernel: [    0.799753] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799755] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Oct 23 09:24:06 node-2 kernel: [    0.799766] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799769] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Oct 23 09:24:06 node-2 kernel: [    0.799780] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799782] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Oct 23 09:24:06 node-2 kernel: [    0.799785] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Oct 23 09:24:06 node-2 kernel: [    0.799812] ioapic: probe of 0000:00:05.4 failed with error -22
Oct 23 09:24:06 node-2 kernel: [    0.799818] ioapic: probe of 0000:80:05.4 failed with error -22
Oct 23 09:24:06 node-2 kernel: [    0.799822] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Oct 23 09:24:06 node-2 kernel: [    0.799831] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Oct 23 09:24:06 node-2 kernel: [    0.799868] vesafb: mode is 640x480x32, linelength=2560, pages=0
Oct 23 09:24:06 node-2 kernel: [    0.799869] vesafb: scrolling: redraw
Oct 23 09:24:06 node-2 kernel: [    0.799870] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Oct 23 09:24:06 node-2 kernel: [    0.820235] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Oct 23 09:24:06 node-2 kernel: [    0.828725] Console: switching to colour frame buffer device 80x30
Oct 23 09:24:06 node-2 kernel: [    0.837386] fb0: VESA VGA frame buffer device
Oct 23 09:24:06 node-2 kernel: [    0.837586] intel_idle: MWAIT substates: 0x2120
Oct 23 09:24:06 node-2 kernel: [    0.837587] intel_idle: v0.4 model 0x3F
Oct 23 09:24:06 node-2 kernel: [    0.837588] intel_idle: lapic_timer_reliable_states 0xffffffff
Oct 23 09:24:06 node-2 kernel: [    0.837830] ipmi message handler version 39.2
Oct 23 09:24:06 node-2 kernel: [    0.838105] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Oct 23 09:24:06 node-2 kernel: [    0.838546] ACPI: AC Adapter [P111] (on-line)
Oct 23 09:24:06 node-2 kernel: [    0.843785] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Oct 23 09:24:06 node-2 kernel: [    0.854813] ACPI: Power Button [PWRB]
Oct 23 09:24:06 node-2 kernel: [    0.860583] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Oct 23 09:24:06 node-2 kernel: [    0.872225] ACPI: Power Button [PWRF]
Oct 23 09:24:06 node-2 kernel: [    0.888154] ERST: Error Record Serialization Table (ERST) support is initialized.
Oct 23 09:24:06 node-2 kernel: [    0.899832] pstore: Registered erst as persistent store backend
Oct 23 09:24:06 node-2 kernel: [    0.906020] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Oct 23 09:24:06 node-2 kernel: [    0.918001] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Oct 23 09:24:06 node-2 kernel: [    0.944752] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Oct 23 09:24:06 node-2 kernel: [    0.978047] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Oct 23 09:24:06 node-2 kernel: [    0.992153] Linux agpgart interface v0.103
Oct 23 09:24:06 node-2 kernel: [    0.999820] brd: module loaded
Oct 23 09:24:06 node-2 kernel: [    1.006914] loop: module loaded
Oct 23 09:24:06 node-2 kernel: [    1.013706] libphy: Fixed MDIO Bus: probed
Oct 23 09:24:06 node-2 kernel: [    1.020265] tun: Universal TUN/TAP device driver, 1.6
Oct 23 09:24:06 node-2 kernel: [    1.026853] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Oct 23 09:24:06 node-2 kernel: [    1.033464] PPP generic driver version 2.4.2
Oct 23 09:24:06 node-2 kernel: [    1.039976] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Oct 23 09:24:06 node-2 kernel: [    1.046508] ehci-pci: EHCI PCI platform driver
Oct 23 09:24:06 node-2 kernel: [    1.053126] ehci-pci 0000:00:1a.0: EHCI Host Controller
Oct 23 09:24:06 node-2 kernel: [    1.059586] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Oct 23 09:24:06 node-2 kernel: [    1.072124] ehci-pci 0000:00:1a.0: debug port 2
Oct 23 09:24:06 node-2 kernel: [    1.082323] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Oct 23 09:24:06 node-2 kernel: [    1.082342] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Oct 23 09:24:06 node-2 kernel: [    1.098052] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Oct 23 09:24:06 node-2 kernel: [    1.104113] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Oct 23 09:24:06 node-2 kernel: [    1.110289] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 23 09:24:06 node-2 kernel: [    1.122207] usb usb1: Product: EHCI Host Controller
Oct 23 09:24:06 node-2 kernel: [    1.128245] usb usb1: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 23 09:24:06 node-2 kernel: [    1.134289] usb usb1: SerialNumber: 0000:00:1a.0
Oct 23 09:24:06 node-2 kernel: [    1.140239] hub 1-0:1.0: USB hub found
Oct 23 09:24:06 node-2 kernel: [    1.146008] hub 1-0:1.0: 2 ports detected
Oct 23 09:24:06 node-2 kernel: [    1.151784] ehci-pci 0000:00:1d.0: EHCI Host Controller
Oct 23 09:24:06 node-2 kernel: [    1.157362] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Oct 23 09:24:06 node-2 kernel: [    1.168252] ehci-pci 0000:00:1d.0: debug port 2
Oct 23 09:24:06 node-2 kernel: [    1.177547] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Oct 23 09:24:06 node-2 kernel: [    1.177550] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Oct 23 09:24:06 node-2 kernel: [    1.193970] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Oct 23 09:24:06 node-2 kernel: [    1.199155] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Oct 23 09:24:06 node-2 kernel: [    1.204442] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Oct 23 09:24:06 node-2 kernel: [    1.215004] usb usb2: Product: EHCI Host Controller
Oct 23 09:24:06 node-2 kernel: [    1.220469] usb usb2: Manufacturer: Linux 3.13.0-98-generic ehci_hcd
Oct 23 09:24:06 node-2 kernel: [    1.226007] usb usb2: SerialNumber: 0000:00:1d.0
Oct 23 09:24:06 node-2 kernel: [    1.231518] hub 2-0:1.0: USB hub found
Oct 23 09:24:06 node-2 kernel: [    1.236861] hub 2-0:1.0: 2 ports detected
Oct 23 09:24:06 node-2 kernel: [    1.242151] ehci-platform: EHCI generic platform driver
Oct 23 09:24:06 node-2 kernel: [    1.247359] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Oct 23 09:24:06 node-2 kernel: [    1.252657] ohci-pci: OHCI PCI platform driver
Oct 23 09:24:06 node-2 kernel: [    1.257942] ohci-platform: OHCI generic platform driver
Oct 23 09:24:06 node-2 kernel: [    1.263125] uhci_hcd: USB Universal Host Controller Interface driver
Oct 23 09:24:06 node-2 kernel: [    1.268451] i8042: PNP: No PS/2 controller found. Probing ports directly.
Oct 23 09:24:06 node-2 kernel: [    1.461747] usb 1-1: new high-speed USB device number 2 using ehci-pci
Oct 23 09:24:06 node-2 kernel: [    1.633998] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Oct 23 09:24:06 node-2 kernel: [    1.639504] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 23 09:24:06 node-2 kernel: [    1.645265] hub 1-1:1.0: USB hub found
Oct 23 09:24:06 node-2 kernel: [    1.650734] hub 1-1:1.0: 6 ports detected
Oct 23 09:24:06 node-2 kernel: [    1.765484] usb 2-1: new high-speed USB device number 2 using ehci-pci
Oct 23 09:24:06 node-2 kernel: [    1.773497] tsc: Refined TSC clocksource calibration: 3491.911 MHz
Oct 23 09:24:06 node-2 kernel: [    2.033660] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Oct 23 09:24:06 node-2 kernel: [    2.039192] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Oct 23 09:24:06 node-2 kernel: [    2.045049] hub 2-1:1.0: USB hub found
Oct 23 09:24:06 node-2 kernel: [    2.050646] hub 2-1:1.0: 8 ports detected
Oct 23 09:24:06 node-2 kernel: [    2.310393] i8042: No controller found
Oct 23 09:24:06 node-2 kernel: [    2.315847] mousedev: PS/2 mouse device common for all mice
Oct 23 09:24:06 node-2 kernel: [    2.321451] rtc_cmos 00:02: RTC can wake from S4
Oct 23 09:24:06 node-2 kernel: [    2.327123] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Oct 23 09:24:06 node-2 kernel: [    2.329079] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Oct 23 09:24:06 node-2 kernel: [    2.338315] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Oct 23 09:24:06 node-2 kernel: [    2.349417] device-mapper: uevent: version 1.0.3
Oct 23 09:24:06 node-2 kernel: [    2.355057] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Oct 23 09:24:06 node-2 kernel: [    2.366266] ledtrig-cpu: registered to indicate activity on CPUs
Oct 23 09:24:06 node-2 kernel: [    2.372176] TCP: cubic registered
Oct 23 09:24:06 node-2 kernel: [    2.378059] NET: Registered protocol family 10
Oct 23 09:24:06 node-2 kernel: [    2.384006] NET: Registered protocol family 17
Oct 23 09:24:06 node-2 kernel: [    2.389693] Key type dns_resolver registered
Oct 23 09:24:06 node-2 kernel: [    2.395629] Loading compiled-in X.509 certificates
Oct 23 09:24:06 node-2 kernel: [    2.401792] Loaded X.509 cert 'Magrathea: Glacier signing key: c29c39823a6b07000b1e1e4c1cabc3708bc09796'
Oct 23 09:24:06 node-2 kernel: [    2.413168] registered taskstats version 1
Oct 23 09:24:06 node-2 kernel: [    2.421148] Key type trusted registered
Oct 23 09:24:06 node-2 kernel: [    2.428759] Key type encrypted registered
Oct 23 09:24:06 node-2 kernel: [    2.434207] AppArmor: AppArmor sha1 policy hashing enabled
Oct 23 09:24:06 node-2 kernel: [    2.439688] IMA: No TPM chip found, activating TPM-bypass!
Oct 23 09:24:06 node-2 kernel: [    2.445844] regulator-dummy: disabling
Oct 23 09:24:06 node-2 kernel: [    2.451399]   Magic number: 4:529:374
Oct 23 09:24:06 node-2 kernel: [    2.457130] rtc_cmos 00:02: setting system clock to 2016-10-23 09:23:33 UTC (1477214613)
Oct 23 09:24:06 node-2 kernel: [    2.468958] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Oct 23 09:24:06 node-2 kernel: [    2.474656] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 23 09:24:06 node-2 kernel: [    2.474886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Oct 23 09:24:06 node-2 kernel: [    2.474886] EDD information not available.
Oct 23 09:24:06 node-2 kernel: [    2.474929] PM: Hibernation image not present or could not be loaded.
Oct 23 09:24:06 node-2 kernel: [    2.497777] usb 2-1.4: Product: Cisco USB Composite Device-0
Oct 23 09:24:06 node-2 kernel: [    2.497778] usb 2-1.4: Manufacturer: Avocent
Oct 23 09:24:06 node-2 kernel: [    2.497778] usb 2-1.4: SerialNumber: 20111102-00000001
Oct 23 09:24:06 node-2 kernel: [    2.516145] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Oct 23 09:24:06 node-2 kernel: [    2.527473] Write protecting the kernel read-only data: 12288k
Oct 23 09:24:06 node-2 kernel: [    2.533784] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Oct 23 09:24:06 node-2 kernel: [    2.546287] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Oct 23 09:24:06 node-2 kernel: [    2.577972] device-mapper: multipath: version 1.6.0 loaded
Oct 23 09:24:06 node-2 kernel: [    2.586126] systemd-udevd[216]: starting version 204
Oct 23 09:24:06 node-2 kernel: [    2.608608] md: linear personality registered for level -1
Oct 23 09:24:06 node-2 kernel: [    2.622725] md: multipath personality registered for level -4
Oct 23 09:24:06 node-2 kernel: [    2.630883] md: raid0 personality registered for level 0
Oct 23 09:24:06 node-2 kernel: [    2.639027] md: raid1 personality registered for level 1
Oct 23 09:24:06 node-2 kernel: [    2.645862] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Oct 23 09:24:06 node-2 kernel: [    2.652266] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Oct 23 09:24:06 node-2 kernel: [    2.652480] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Oct 23 09:24:06 node-2 kernel: [    2.652918] megasas: FW now in Ready state
Oct 23 09:24:06 node-2 kernel: [    2.652973] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653010] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653044] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653083] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653120] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653157] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653192] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653229] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653267] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653299] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653324] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653378] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653416] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653451] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653490] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653524] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.653696] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Oct 23 09:24:06 node-2 kernel: [    2.684311] hidraw: raw HID events driver (C) Jiri Kosina
Oct 23 09:24:06 node-2 kernel: [    2.693203] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Oct 23 09:24:06 node-2 kernel: [    2.706149] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 23 09:24:06 node-2 kernel: [    2.719334] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 23 09:24:06 node-2 kernel: [    2.726096] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.726101] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.726105] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.726109] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.726157] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.740251] usbcore: registered new interface driver usbhid
Oct 23 09:24:06 node-2 kernel: [    2.747098] usbhid: USB HID core driver
Oct 23 09:24:06 node-2 kernel: [    2.749005] raid6: sse2x1    5211 MB/s
Oct 23 09:24:06 node-2 kernel: [    2.750748] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Oct 23 09:24:06 node-2 kernel: [    2.750751] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Oct 23 09:24:06 node-2 kernel: [    2.750786] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Oct 23 09:24:06 node-2 kernel: [    2.751698] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.751898] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.752001] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.752093] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.752154] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.752238] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.752618] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.770021] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Oct 23 09:24:06 node-2 kernel: [    2.770072] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 23 09:24:06 node-2 kernel: [    2.770086] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 23 09:24:06 node-2 kernel: [    2.770366] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.770448] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.770527] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.770607] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.770789] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 23 09:24:06 node-2 kernel: [    2.816729] raid6: sse2x2   10316 MB/s
Oct 23 09:24:06 node-2 kernel: [    2.884546] raid6: sse2x4    9793 MB/s
Oct 23 09:24:06 node-2 kernel: [    2.956490] raid6: avx2x1   14933 MB/s
Oct 23 09:24:06 node-2 kernel: [    3.028423] raid6: avx2x2   18850 MB/s
Oct 23 09:24:06 node-2 kernel: [    3.100363] raid6: avx2x4   21305 MB/s
Oct 23 09:24:06 node-2 kernel: [    3.106340] raid6: using algorithm avx2x4 (21305 MB/s)
Oct 23 09:24:06 node-2 kernel: [    3.112288] raid6: using avx2x2 recovery algorithm
Oct 23 09:24:06 node-2 kernel: [    3.118119] megasas:IOC Init cmd success
Oct 23 09:24:06 node-2 kernel: [    3.118119] Switched to clocksource tsc
Oct 23 09:24:06 node-2 kernel: [    3.123461] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Oct 23 09:24:06 node-2 kernel: [    3.123462] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Oct 23 09:24:06 node-2 kernel: [    3.123463] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Oct 23 09:24:06 node-2 kernel: [    3.123609] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    3.123649] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    3.123687] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    3.123725] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Oct 23 09:24:06 node-2 kernel: [    3.123784] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Oct 23 09:24:06 node-2 kernel: [    3.140376] megasas: INIT adapter done
Oct 23 09:24:06 node-2 kernel: [    3.175159] xor: automatically using best checksumming function:
Oct 23 09:24:06 node-2 kernel: [    3.180885] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Oct 23 09:24:06 node-2 kernel: [    3.192157] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Oct 23 09:24:06 node-2 kernel: [    3.204040] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Oct 23 09:24:06 node-2 kernel: [    3.212253] megaraid_sas 0000:01:00.0: Controller type: iMR
Oct 23 09:24:06 node-2 kernel: [    3.212609] scsi0 : LSI SAS based MegaRAID driver
Oct 23 09:24:06 node-2 kernel: [    3.219645] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 23 09:24:06 node-2 kernel: [    3.228279]    avx       : 51233.000 MB/sec
Oct 23 09:24:06 node-2 kernel: [    3.232081] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Oct 23 09:24:06 node-2 kernel: [    3.236322] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Oct 23 09:24:06 node-2 kernel: [    3.236409] sd 0:2:0:0: Attached scsi generic sg0 type 0
Oct 23 09:24:06 node-2 kernel: [    3.236595] sd 0:2:0:0: [sda] Write Protect is off
Oct 23 09:24:06 node-2 kernel: [    3.236597] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Oct 23 09:24:06 node-2 kernel: [    3.236672] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Oct 23 09:24:06 node-2 kernel: [    3.264221]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Oct 23 09:24:06 node-2 kernel: [    3.265737] sd 0:2:0:0: [sda] Attached SCSI disk
Oct 23 09:24:06 node-2 kernel: [    3.309165] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Oct 23 09:24:06 node-2 kernel: [    3.322943] async_tx: api initialized (async)
Oct 23 09:24:06 node-2 kernel: [    3.322948] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Oct 23 09:24:06 node-2 kernel: [    3.323601] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Oct 23 09:24:06 node-2 kernel: [    3.361379] md: raid6 personality registered for level 6
Oct 23 09:24:06 node-2 kernel: [    3.368649] md: raid5 personality registered for level 5
Oct 23 09:24:06 node-2 kernel: [    3.375659] md: raid4 personality registered for level 4
Oct 23 09:24:06 node-2 kernel: [    3.385434] md: raid10 personality registered for level 10
Oct 23 09:24:06 node-2 kernel: [    3.438849] multipathd (362): /proc/362/oom_adj is deprecated, please use /proc/362/oom_score_adj instead.
Oct 23 09:24:06 node-2 kernel: [    3.457444] random: lvm urandom read with 29 bits of entropy available
Oct 23 09:24:06 node-2 kernel: [    3.571199] bio: create slab <bio-1> at 1
Oct 23 09:24:06 node-2 kernel: [    4.318185] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Oct 23 09:24:06 node-2 kernel: [    5.030143] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Oct 23 09:24:06 node-2 kernel: [    5.055090] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Oct 23 09:24:06 node-2 kernel: [    5.177890] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Oct 23 09:24:06 node-2 kernel: [    5.207879] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Oct 23 09:24:06 node-2 kernel: [    5.278259] random: nonblocking pool is initialized
Oct 23 09:24:06 node-2 kernel: [    5.301912] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Oct 23 09:24:06 node-2 kernel: [    5.459320] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Oct 23 09:24:06 node-2 kernel: [    5.511598] XFS (dm-0): Mounting Filesystem
Oct 23 09:24:06 node-2 kernel: [    5.693553] XFS (dm-0): Ending clean mount
Oct 23 09:24:06 node-2 kernel: [    5.790990] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Oct 23 09:24:06 node-2 kernel: [    5.825749] XFS (dm-1): Mounting Filesystem
Oct 23 09:24:06 node-2 kernel: [    6.022342] XFS (dm-1): Ending clean mount
Oct 23 09:24:06 node-2 kernel: [    7.842620] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 23 09:24:06 node-2 kernel: [    7.871424] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 23 09:24:06 node-2 kernel: [    8.054630] systemd-udevd[778]: starting version 204
Oct 23 09:24:06 node-2 kernel: [    8.264602] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Oct 23 09:24:06 node-2 kernel: [    8.264609] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 23 09:24:06 node-2 kernel: [    8.264612] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Oct 23 09:24:06 node-2 kernel: [    8.264614] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 23 09:24:06 node-2 kernel: [    8.264725] lpc_ich: Resource conflict(s) found affecting gpio_ich
Oct 23 09:24:06 node-2 kernel: [    8.269567] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Oct 23 09:24:06 node-2 kernel: [    8.270694] power_meter ACPI000D:00: Found ACPI power meter.
Oct 23 09:24:06 node-2 kernel: [    8.270732] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Oct 23 09:24:06 node-2 kernel: [    8.288906] IPMI System Interface driver.
Oct 23 09:24:06 node-2 kernel: [    8.288933] ipmi_si: probing via ACPI
Oct 23 09:24:06 node-2 kernel: [    8.288958] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Oct 23 09:24:06 node-2 kernel: [    8.288959] ipmi_si: Adding ACPI-specified kcs state machine
Oct 23 09:24:06 node-2 kernel: [    8.288971] ipmi_si: probing via SMBIOS
Oct 23 09:24:06 node-2 kernel: [    8.288973] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Oct 23 09:24:06 node-2 kernel: [    8.288973] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Oct 23 09:24:06 node-2 kernel: [    8.288975] ipmi_si: probing via SPMI
Oct 23 09:24:06 node-2 kernel: [    8.288977] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Oct 23 09:24:06 node-2 kernel: [    8.288977] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Oct 23 09:24:06 node-2 kernel: [    8.288979] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Oct 23 09:24:06 node-2 kernel: [    8.343656] wmi: Mapper loaded
Oct 23 09:24:06 node-2 kernel: [    8.364397] systemd-udevd[813]: renamed network interface eth0 to enp6s0
Oct 23 09:24:06 node-2 kernel: [    8.400295] systemd-udevd[815]: renamed network interface eth3 to enp9s0
Oct 23 09:24:06 node-2 kernel: [    8.435136] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Oct 23 09:24:06 node-2 kernel: [    8.435141] ipmi_si 00:09: IPMI kcs interface initialized
Oct 23 09:24:06 node-2 kernel: [    8.436478] systemd-udevd[816]: renamed network interface eth1 to enp7s0
Oct 23 09:24:06 node-2 kernel: [    8.472185] systemd-udevd[817]: renamed network interface eth2 to enp8s0
Oct 23 09:24:06 node-2 kernel: [    8.686016] type=1400 audit(1477214619.730:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Oct 23 09:24:06 node-2 kernel: [    8.686175] type=1400 audit(1477214619.730:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1061 comm="apparmor_parser"
Oct 23 09:24:06 node-2 kernel: [    8.686306] type=1400 audit(1477214619.730:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1061 comm="apparmor_parser"
Oct 23 09:24:06 node-2 kernel: [    8.688472] type=1400 audit(1477214619.734:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1063 comm="apparmor_parser"
Oct 23 09:24:06 node-2 kernel: [    8.688609] type=1400 audit(1477214619.734:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1063 comm="apparmor_parser"
Oct 23 09:24:06 node-2 kernel: [    8.688737] type=1400 audit(1477214619.734:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1063 comm="apparmor_parser"
Oct 23 09:24:06 node-2 kernel: [    8.696597] type=1400 audit(1477214619.742:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1065 comm="apparmor_parser"
Oct 23 09:24:06 node-2 kernel: [    8.696748] type=1400 audit(1477214619.742:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1065 comm="apparmor_parser"
Oct 23 09:24:06 node-2 kernel: [    8.696864] type=1400 audit(1477214619.742:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1065 comm="apparmor_parser"
Oct 23 09:24:06 node-2 kernel: [    8.697898] type=1400 audit(1477214619.742:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1064 comm="apparmor_parser"
Oct 23 09:24:06 node-2 kernel: [    9.215113] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Oct 23 09:24:06 node-2 kernel: [    9.215896] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Oct 23 09:24:06 node-2 kernel: [    9.415266] enic 0000:06:00.0 enp6s0: Link UP
Oct 23 09:24:06 node-2 kernel: [    9.416308] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Oct 23 09:24:06 node-2 kernel: [    9.416318] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Oct 23 09:24:06 node-2 kernel: [   18.779763] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Oct 23 09:24:07 node-2 failsafe: Failsafe of 120 seconds reached.
Oct 23 09:24:07 node-2 kernel: [   37.434389] init: failsafe main process (8416) killed by TERM signal
Oct 23 09:24:07 node-2 dbus[8448]: [system] AppArmor D-Bus mediation is enabled
Oct 23 09:24:08 node-2 kernel: [   37.703471] audit_printk_skb: 30 callbacks suppressed
Oct 23 09:24:08 node-2 kernel: [   37.703473] type=1400 audit(1477214648.129:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8542 comm="apparmor_parser"
Oct 23 09:24:08 node-2 kernel: [   37.703777] type=1400 audit(1477214648.129:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8541 comm="apparmor_parser"
Oct 23 09:24:08 node-2 kernel: [   37.703782] type=1400 audit(1477214648.129:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8541 comm="apparmor_parser"
Oct 23 09:24:08 node-2 kernel: [   37.703785] type=1400 audit(1477214648.129:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Oct 23 09:24:08 node-2 kernel: [   37.704002] type=1400 audit(1477214648.129:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8541 comm="apparmor_parser"
Oct 23 09:24:08 node-2 kernel: [   37.704004] type=1400 audit(1477214648.129:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Oct 23 09:24:08 node-2 kernel: [   37.704116] type=1400 audit(1477214648.129:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8541 comm="apparmor_parser"
Oct 23 09:24:08 node-2 kernel: [   37.770190] type=1400 audit(1477214648.193:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8544 comm="apparmor_parser"
Oct 23 09:24:08 node-2 anacron[8608]: Anacron 2.3 started on 2016-10-23
Oct 23 09:24:08 node-2 anacron[8608]: Will run job `cron.daily' in 5 min.
Oct 23 09:24:08 node-2 anacron[8608]: Will run job `cron.weekly' in 10 min.
Oct 23 09:24:08 node-2 anacron[8608]: Will run job `cron.monthly' in 15 min.
Oct 23 09:24:08 node-2 anacron[8608]: Jobs will be executed sequentially
Oct 23 09:24:08 node-2 cron[8574]: (CRON) INFO (pidfile fd = 3)
Oct 23 09:24:08 node-2 cron[8616]: (CRON) STARTUP (fork ok)
Oct 23 09:24:08 node-2 multipathd: path checkers start up
Oct 23 09:24:08 node-2 cron[8616]: (CRON) INFO (Running @reboot jobs)
Oct 23 09:24:08 node-2 postfix/master[8753]: daemon started -- version 2.11.0, configuration /etc/postfix
Oct 23 09:24:11 node-2 puppet-agent[8937]: Reopening log files
Oct 23 09:24:11 node-2 puppet-agent[8937]: Could not request certificate: Connection refused - connect(2)
Oct 23 09:24:24 node-2 puppet-user[9016]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Oct 23 09:24:24 node-2 puppet-user[9016]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Oct 23 09:24:25 node-2 puppet-user[9016]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Oct 23 09:24:25 node-2 puppet-user[9016]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Oct 23 09:24:25 node-2 puppet-user[9016]: Finished catalog run in 0.78 seconds
Oct 23 09:24:26 node-2 multipathd: uevent trigger error
Oct 23 09:24:27 node-2 puppet-user[9456]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 23 09:24:27 node-2 puppet-user[9456]: Compiled catalog for node-2.domain.tld in environment production in 0.11 seconds
Oct 23 09:24:27 node-2 puppet-user[9456]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Oct 23 09:24:27 node-2 puppet-user[9456]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Oct 23 09:24:27 node-2 puppet-user[9456]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Oct 23 09:24:27 node-2 puppet-user[9456]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Oct 23 09:24:27 node-2 puppet-user[9456]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Oct 23 09:24:27 node-2 puppet-user[9456]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Oct 23 09:24:27 node-2 puppet-user[9456]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Oct 23 09:24:27 node-2 puppet-user[9456]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Oct 23 09:24:27 node-2 puppet-user[9456]: Finished catalog run in 0.06 seconds
Oct 23 09:24:28 node-2 puppet-user[9913]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Oct 23 09:24:28 node-2 puppet-user[9913]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Oct 23 09:24:28 node-2 puppet-user[9913]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Oct 23 09:24:28 node-2 puppet-user[9913]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Oct 23 09:24:28 node-2 puppet-user[9913]: Finished catalog run in 0.04 seconds
Oct 23 09:24:30 node-2 puppet-user[10376]: (Scope(Class[main])) MODULAR: configuration_symlink
Oct 23 09:24:30 node-2 puppet-user[10376]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Oct 23 09:24:30 node-2 puppet-user[10376]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Oct 23 09:24:30 node-2 puppet-user[10376]: Finished catalog run in 0.04 seconds
Oct 23 09:24:31 node-2 puppet-user[10890]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Oct 23 09:24:31 node-2 puppet-user[10890]: Compiled catalog for node-2.domain.tld in environment production in 0.18 seconds
Oct 23 09:24:32 node-2 puppet-user[10890]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Oct 23 09:24:34 node-2 puppet-user[10890]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Oct 23 09:24:34 node-2 puppet-user[10890]: Finished catalog run in 2.08 seconds
Oct 23 09:24:35 node-2 puppet-user[11496]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Oct 23 09:24:35 node-2 puppet-user[11496]: Compiled catalog for node-2.domain.tld in environment production in 0.19 seconds
Oct 23 09:24:35 node-2 puppet-user[11496]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Oct 23 09:24:35 node-2 puppet-user[11496]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Oct 23 09:24:35 node-2 puppet-user[11496]: (/Stage[main]/Apt/File[preferences]/ensure) created
Oct 23 09:24:35 node-2 puppet-user[11496]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Oct 23 09:24:35 node-2 puppet-user[11496]: Finished catalog run in 0.21 seconds
Oct 23 09:24:37 node-2 puppet-user[11985]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Oct 23 09:24:37 node-2 puppet-user[11985]: Compiled catalog for node-2.domain.tld in environment production in 0.13 seconds
Oct 23 09:24:37 node-2 puppet-user[11985]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Oct 23 09:24:37 node-2 kernel: [   67.415350] nr_pdflush_threads exported in /proc is scheduled for removal
Oct 23 09:24:37 node-2 kernel: [   67.415399] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Oct 23 09:24:37 node-2 puppet-user[11985]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Oct 23 09:24:37 node-2 puppet-user[11985]: Finished catalog run in 0.05 seconds
Oct 23 09:24:39 node-2 puppet-user[12442]: (Scope(Class[main])) MODULAR: sync_time
Oct 23 09:24:39 node-2 puppet-user[12442]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Oct 23 09:24:39 node-2 ntpdate[12861]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Oct 23 09:24:45 node-2 ntpdate[12861]: adjust time server 10.20.0.2 offset 0.325543 sec
Oct 23 09:24:45 node-2 puppet-user[12442]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Oct 23 09:24:45 node-2 puppet-user[12442]: Finished catalog run in 6.16 seconds
Oct 23 09:24:50 node-2 puppet-user[13255]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Oct 23 09:24:50 node-2 puppet-user[13255]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Oct 23 09:24:50 node-2 puppet-user[13255]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Oct 23 09:24:50 node-2 puppet-user[13255]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Oct 23 09:24:50 node-2 puppet-user[13255]: Finished catalog run in 0.07 seconds
Oct 23 09:24:51 node-2 puppet-user[13718]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Oct 23 09:24:52 node-2 puppet-user[13718]: Compiled catalog for node-2.domain.tld in environment production in 0.46 seconds
Oct 23 09:24:52 node-2 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Oct 23 09:24:52 node-2 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Oct 23 09:24:52 node-2 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Oct 23 09:24:52 node-2 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Oct 23 09:24:52 node-2 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Oct 23 09:24:52 node-2 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Oct 23 09:24:52 node-2 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Oct 23 09:24:52 node-2 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Oct 23 09:24:52 node-2 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Oct 23 09:24:52 node-2 puppet-user[13718]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Oct 23 09:24:53 node-2 puppet-user[13718]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Oct 23 09:24:53 node-2 puppet-user[13718]: Finished catalog run in 0.76 seconds
Oct 23 09:24:54 node-2 puppet-user[14228]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Oct 23 09:24:54 node-2 puppet-user[14228]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Oct 23 09:24:55 node-2 kernel: [   85.355146] init: plymouth-upstart-bridge main process ended, respawning
Oct 23 09:24:56 node-2 puppet-agent[8937]: Could not run: SIGTERM
Oct 23 09:24:56 node-2 kernel: [   85.666738] ip_tables: (C) 2000-2006 Netfilter Core Team
Oct 23 09:24:56 node-2 ec2: 
Oct 23 09:24:56 node-2 ec2: #############################################################
Oct 23 09:24:56 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Oct 23 09:24:56 node-2 ec2: 1024 e6:22:de:e5:a8:9c:ff:bd:00:4e:af:3f:a9:01:67:ae  root@node-2.domain.tld (DSA)
Oct 23 09:24:56 node-2 ec2: 256 c7:22:db:14:a0:e0:28:4e:63:c4:ca:b7:2f:39:95:d4  root@node-2.domain.tld (ECDSA)
Oct 23 09:24:56 node-2 ec2: 256 fc:8f:ba:88:5e:23:55:c4:34:98:52:70:48:1a:26:4c  root@node-2.domain.tld (ED25519)
Oct 23 09:24:56 node-2 ec2: 2048 b1:f9:e7:a5:94:fa:92:90:f3:d0:b3:66:32:97:aa:c1  root@node-2.domain.tld (RSA)
Oct 23 09:24:56 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Oct 23 09:24:56 node-2 ec2: #############################################################
Oct 23 09:24:58 node-2 puppet-user[14228]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Oct 23 09:25:01 node-2 CRON[15559]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Oct 23 09:25:15 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 23 09:25:15 node-2 nailgun-agent: I, [2016-10-23T09:25:15.665923 #15562]  INFO -- : API URL is https://10.20.0.2:8443/api
Oct 23 09:25:24 node-2 puppet-user[14228]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Oct 23 09:25:24 node-2 puppet-user[14228]: Finished catalog run in 30.06 seconds
Oct 23 09:25:27 node-2 puppet-user[16985]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Oct 23 09:25:27 node-2 puppet-user[16985]: Compiled catalog for node-2.domain.tld in environment production in 0.56 seconds
Oct 23 09:25:27 node-2 puppet-user[16985]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Oct 23 09:25:27 node-2 puppet-user[16985]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Oct 23 09:25:27 node-2 puppet-user[16985]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Oct 23 09:25:27 node-2 puppet-user[16985]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Oct 23 09:25:27 node-2 puppet-user[16985]: Finished catalog run in 0.08 seconds
Oct 23 09:25:28 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Oct 23 09:25:28 node-2 nailgun-agent: I, [2016-10-23T09:25:28.779939 #15562]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Oct 23 09:25:29 node-2 puppet-user[17444]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Oct 23 09:25:30 node-2 puppet-user[17444]: Compiled catalog for node-2.domain.tld in environment production in 0.81 seconds
Oct 23 09:25:30 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Oct 23 09:25:30 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Oct 23 09:25:30 node-2 crontab[18054]: (root) LIST (root)
Oct 23 09:25:30 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Oct 23 09:25:30 node-2 crontab[18055]: (root) REPLACE (root)
Oct 23 09:25:31 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Oct 23 09:25:32 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Oct 23 09:25:33 node-2 puppet-user[17444]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Oct 23 09:25:33 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8389" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Oct 23 09:25:33 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Oct 23 09:25:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:25:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:25:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:25:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:25:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:25:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:25:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:25:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:25:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:25:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:26:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:26:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:26:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:26:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:26:37 node-2 multipathd: uevent trigger error
<27>Oct 23 09:26:37 node-2 multipathd: uevent trigger error
<27>Oct 23 09:26:37 node-2 multipathd: uevent trigger error
<27>Oct 23 09:26:37 node-2 multipathd: uevent trigger error
<27>Oct 23 09:26:37 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:17 node-2 ntpdate[1376]: no servers can be used, exiting
<27>Oct 23 09:27:18 node-2 ntpdate[1585]: no servers can be used, exiting
<27>Oct 23 09:27:49 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:49 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:52 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:53 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:53 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:53 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:53 node-2 multipathd: uevent trigger error
<27>Oct 23 09:27:53 node-2 multipathd: uevent trigger error
<27>Oct 23 09:28:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:28:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:28:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:28:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:28:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:28:07 node-2 multipathd: uevent trigger error
<27>Oct 23 09:28:07 node-2 multipathd: uevent trigger error
<27>Oct 23 09:28:07 node-2 multipathd: uevent trigger error
<27>Oct 23 09:28:07 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:00 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:00 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:00 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:00 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:08 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:08 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:08 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:09 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:09 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:11 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 23 09:29:11 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 23 09:29:17 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 23 09:29:17 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 23 09:29:23 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 23 09:29:28 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 23 09:29:28 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Oct 23 09:29:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:38 node-2 ntpdate[19629]: the NTP socket is in use, exiting
<27>Oct 23 09:29:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:48 node-2 multipathd: uevent trigger error
<129>Oct 23 09:29:50 node-2 haproxy[21816]: 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>Oct 23 09:29:51 node-2 haproxy[21827]: 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>Oct 23 09:29:51 node-2 haproxy[21827]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:29:51 node-2 haproxy[21827]: proxy mysqld has no server available!
<27>Oct 23 09:29:53 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:53 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:53 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:53 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:53 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:57 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:57 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:57 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:57 node-2 multipathd: uevent trigger error
<27>Oct 23 09:29:57 node-2 multipathd: uevent trigger error
<129>Oct 23 09:29:59 node-2 haproxy[24464]: 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>Oct 23 09:30:00 node-2 haproxy[24468]: 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>Oct 23 09:30:00 node-2 haproxy[24468]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:00 node-2 haproxy[24468]: proxy mysqld has no server available!
<129>Oct 23 09:30:00 node-2 haproxy[24468]: 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>Oct 23 09:30:01 node-2 haproxy[24468]: 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>Oct 23 09:30:01 node-2 haproxy[24468]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:01 node-2 haproxy[24468]: proxy object-storage has no server available!
<27>Oct 23 09:30:02 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:02 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:02 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:02 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:02 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:02 node-2 multipathd: uevent trigger error
<129>Oct 23 09:30:05 node-2 haproxy[25976]: 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>Oct 23 09:30:05 node-2 haproxy[25976]: 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>Oct 23 09:30:05 node-2 haproxy[25976]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:05 node-2 haproxy[25976]: proxy neutron has no server available!
<129>Oct 23 09:30:05 node-2 haproxy[25976]: 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>Oct 23 09:30:05 node-2 haproxy[25976]: 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>Oct 23 09:30:06 node-2 haproxy[25985]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:06 node-2 haproxy[25985]: proxy mysqld has no server available!
<129>Oct 23 09:30:06 node-2 haproxy[25985]: 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>Oct 23 09:30:06 node-2 haproxy[25985]: 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>Oct 23 09:30:06 node-2 haproxy[25985]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:06 node-2 haproxy[25985]: proxy object-storage has no server available!
<27>Oct 23 09:30:08 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:08 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:08 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:08 node-2 multipathd: uevent trigger error
<129>Oct 23 09:30:10 node-2 haproxy[27336]: 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>Oct 23 09:30:10 node-2 haproxy[27336]: 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>Oct 23 09:30:10 node-2 haproxy[27336]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:10 node-2 haproxy[27336]: proxy keystone-1 has no server available!
<129>Oct 23 09:30:10 node-2 haproxy[27336]: 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>Oct 23 09:30:10 node-2 haproxy[27336]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 23 09:30:11 node-2 haproxy[27340]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:11 node-2 haproxy[27340]: proxy keystone-2 has no server available!
<129>Oct 23 09:30:11 node-2 haproxy[27340]: 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>Oct 23 09:30:11 node-2 haproxy[27340]: 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>Oct 23 09:30:11 node-2 haproxy[27340]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:11 node-2 haproxy[27340]: proxy neutron has no server available!
<129>Oct 23 09:30:11 node-2 haproxy[27340]: 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>Oct 23 09:30:11 node-2 haproxy[27340]: 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>Oct 23 09:30:11 node-2 haproxy[27340]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:11 node-2 haproxy[27340]: proxy mysqld has no server available!
<129>Oct 23 09:30:11 node-2 haproxy[27340]: 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>Oct 23 09:30:12 node-2 haproxy[27340]: 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>Oct 23 09:30:12 node-2 haproxy[27340]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:12 node-2 haproxy[27340]: proxy object-storage has no server available!
<27>Oct 23 09:30:13 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:13 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:13 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:13 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:13 node-2 multipathd: uevent trigger error
<129>Oct 23 09:30:15 node-2 haproxy[28855]: 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>Oct 23 09:30:15 node-2 haproxy[28855]: 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>Oct 23 09:30:15 node-2 haproxy[28855]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:15 node-2 haproxy[28855]: proxy keystone-1 has no server available!
<129>Oct 23 09:30:15 node-2 haproxy[28855]: 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>Oct 23 09:30:16 node-2 haproxy[28859]: 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>Oct 23 09:30:16 node-2 haproxy[28859]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:16 node-2 haproxy[28859]: proxy keystone-2 has no server available!
<129>Oct 23 09:30:16 node-2 haproxy[28859]: 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>Oct 23 09:30:16 node-2 haproxy[28859]: 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>Oct 23 09:30:16 node-2 haproxy[28859]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:16 node-2 haproxy[28859]: proxy neutron has no server available!
<129>Oct 23 09:30:16 node-2 haproxy[28859]: 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>Oct 23 09:30:16 node-2 haproxy[28859]: 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>Oct 23 09:30:16 node-2 haproxy[28859]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:16 node-2 haproxy[28859]: proxy mysqld has no server available!
<129>Oct 23 09:30:16 node-2 haproxy[28859]: 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>Oct 23 09:30:17 node-2 haproxy[28859]: 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>Oct 23 09:30:17 node-2 haproxy[28859]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:17 node-2 haproxy[28859]: proxy object-storage has no server available!
<129>Oct 23 09:30:17 node-2 haproxy[28859]: 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>Oct 23 09:30:17 node-2 haproxy[28859]: 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>Oct 23 09:30:17 node-2 haproxy[28859]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:17 node-2 haproxy[28859]: proxy aodh has no server available!
<27>Oct 23 09:30:19 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:19 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:19 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:19 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:19 node-2 multipathd: uevent trigger error
<129>Oct 23 09:30:21 node-2 haproxy[30249]: 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>Oct 23 09:30:21 node-2 haproxy[30249]: 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>Oct 23 09:30:21 node-2 haproxy[30249]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:21 node-2 haproxy[30249]: proxy keystone-1 has no server available!
<129>Oct 23 09:30:21 node-2 haproxy[30249]: 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>Oct 23 09:30:21 node-2 haproxy[30249]: 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>Oct 23 09:30:21 node-2 haproxy[30249]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:21 node-2 haproxy[30249]: proxy keystone-2 has no server available!
<129>Oct 23 09:30:21 node-2 haproxy[30249]: 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>Oct 23 09:30:21 node-2 haproxy[30249]: 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>Oct 23 09:30:21 node-2 haproxy[30249]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:21 node-2 haproxy[30249]: proxy neutron has no server available!
<129>Oct 23 09:30:22 node-2 haproxy[30255]: 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>Oct 23 09:30:22 node-2 haproxy[30255]: 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>Oct 23 09:30:22 node-2 haproxy[30255]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:22 node-2 haproxy[30255]: proxy mysqld has no server available!
<129>Oct 23 09:30:22 node-2 haproxy[30255]: 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>Oct 23 09:30:22 node-2 haproxy[30255]: 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>Oct 23 09:30:22 node-2 haproxy[30255]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:22 node-2 haproxy[30255]: proxy object-storage has no server available!
<129>Oct 23 09:30:22 node-2 haproxy[30255]: 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>Oct 23 09:30:22 node-2 haproxy[30255]: 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>Oct 23 09:30:22 node-2 haproxy[30255]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:22 node-2 haproxy[30255]: proxy aodh has no server available!
<129>Oct 23 09:30:22 node-2 haproxy[30255]: 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>Oct 23 09:30:22 node-2 haproxy[30255]: 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>Oct 23 09:30:23 node-2 haproxy[30255]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:23 node-2 haproxy[30255]: proxy ceilometer has no server available!
<27>Oct 23 09:30:24 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:24 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:24 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:24 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:24 node-2 multipathd: uevent trigger error
<129>Oct 23 09:30:26 node-2 haproxy[31632]: 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>Oct 23 09:30:26 node-2 haproxy[31632]: 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>Oct 23 09:30:26 node-2 haproxy[31632]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:26 node-2 haproxy[31632]: proxy keystone-1 has no server available!
<129>Oct 23 09:30:27 node-2 haproxy[31636]: 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>Oct 23 09:30:27 node-2 haproxy[31636]: 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>Oct 23 09:30:27 node-2 haproxy[31636]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:27 node-2 haproxy[31636]: proxy keystone-2 has no server available!
<129>Oct 23 09:30:27 node-2 haproxy[31636]: 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>Oct 23 09:30:27 node-2 haproxy[31636]: 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>Oct 23 09:30:27 node-2 haproxy[31636]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:27 node-2 haproxy[31636]: proxy neutron has no server available!
<129>Oct 23 09:30:27 node-2 haproxy[31636]: 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>Oct 23 09:30:27 node-2 haproxy[31636]: 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>Oct 23 09:30:27 node-2 haproxy[31636]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:27 node-2 haproxy[31636]: proxy mysqld has no server available!
<129>Oct 23 09:30:27 node-2 haproxy[31636]: 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>Oct 23 09:30:28 node-2 haproxy[31636]: 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>Oct 23 09:30:28 node-2 haproxy[31636]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:28 node-2 haproxy[31636]: proxy object-storage has no server available!
<129>Oct 23 09:30:28 node-2 haproxy[31636]: 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>Oct 23 09:30:28 node-2 haproxy[31636]: 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>Oct 23 09:30:28 node-2 haproxy[31636]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:28 node-2 haproxy[31636]: proxy aodh has no server available!
<129>Oct 23 09:30:28 node-2 haproxy[31636]: 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>Oct 23 09:30:28 node-2 haproxy[31636]: 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>Oct 23 09:30:28 node-2 haproxy[31636]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:28 node-2 haproxy[31636]: proxy ceilometer has no server available!
<27>Oct 23 09:30:29 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:30 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:30 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:30 node-2 multipathd: uevent trigger error
<129>Oct 23 09:30:32 node-2 haproxy[533]: 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>Oct 23 09:30:32 node-2 haproxy[533]: 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>Oct 23 09:30:32 node-2 haproxy[533]: 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>Oct 23 09:30:32 node-2 haproxy[533]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:32 node-2 haproxy[533]: proxy keystone-1 has no server available!
<129>Oct 23 09:30:32 node-2 haproxy[533]: 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>Oct 23 09:30:32 node-2 haproxy[533]: 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>Oct 23 09:30:32 node-2 haproxy[533]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:32 node-2 haproxy[533]: proxy keystone-2 has no server available!
<129>Oct 23 09:30:32 node-2 haproxy[533]: 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>Oct 23 09:30:33 node-2 haproxy[537]: 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>Oct 23 09:30:33 node-2 haproxy[537]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:33 node-2 haproxy[537]: proxy neutron has no server available!
<129>Oct 23 09:30:33 node-2 haproxy[537]: 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>Oct 23 09:30:33 node-2 haproxy[537]: 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>Oct 23 09:30:33 node-2 haproxy[537]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:33 node-2 haproxy[537]: proxy mysqld has no server available!
<129>Oct 23 09:30:33 node-2 haproxy[537]: 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>Oct 23 09:30:33 node-2 haproxy[537]: 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>Oct 23 09:30:33 node-2 haproxy[537]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:33 node-2 haproxy[537]: proxy object-storage has no server available!
<129>Oct 23 09:30:33 node-2 haproxy[537]: 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>Oct 23 09:30:33 node-2 haproxy[537]: 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>Oct 23 09:30:33 node-2 haproxy[537]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:33 node-2 haproxy[537]: proxy aodh has no server available!
<129>Oct 23 09:30:33 node-2 haproxy[537]: 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>Oct 23 09:30:34 node-2 haproxy[537]: 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>Oct 23 09:30:34 node-2 haproxy[537]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:34 node-2 haproxy[537]: proxy ceilometer has no server available!
<27>Oct 23 09:30:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:35 node-2 multipathd: uevent trigger error
<129>Oct 23 09:30:37 node-2 haproxy[1963]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:38 node-2 haproxy[1967]: proxy keystone-1 has no server available!
<129>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:38 node-2 haproxy[1967]: proxy keystone-2 has no server available!
<129>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:38 node-2 haproxy[1967]: proxy glance-api has no server available!
<129>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:38 node-2 haproxy[1967]: proxy glance-glare has no server available!
<129>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:38 node-2 haproxy[1967]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:38 node-2 haproxy[1967]: proxy neutron has no server available!
<129>Oct 23 09:30:38 node-2 haproxy[1967]: 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>Oct 23 09:30:39 node-2 haproxy[1967]: 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>Oct 23 09:30:39 node-2 haproxy[1967]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:39 node-2 haproxy[1967]: proxy glance-registry has no server available!
<129>Oct 23 09:30:39 node-2 haproxy[1967]: 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>Oct 23 09:30:39 node-2 haproxy[1967]: 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>Oct 23 09:30:39 node-2 haproxy[1967]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:39 node-2 haproxy[1967]: proxy mysqld has no server available!
<129>Oct 23 09:30:39 node-2 haproxy[1967]: 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>Oct 23 09:30:39 node-2 haproxy[1967]: 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>Oct 23 09:30:39 node-2 haproxy[1967]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:39 node-2 haproxy[1967]: proxy object-storage has no server available!
<129>Oct 23 09:30:39 node-2 haproxy[1967]: 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>Oct 23 09:30:39 node-2 haproxy[1967]: 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>Oct 23 09:30:39 node-2 haproxy[1967]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:39 node-2 haproxy[1967]: proxy aodh has no server available!
<129>Oct 23 09:30:39 node-2 haproxy[1967]: 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>Oct 23 09:30:39 node-2 haproxy[1967]: 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>Oct 23 09:30:39 node-2 haproxy[1967]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:39 node-2 haproxy[1967]: proxy ceilometer has no server available!
<27>Oct 23 09:30:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:41 node-2 multipathd: uevent trigger error
<129>Oct 23 09:30:43 node-2 haproxy[3325]: 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>Oct 23 09:30:43 node-2 haproxy[3325]: 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>Oct 23 09:30:43 node-2 haproxy[3325]: 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>Oct 23 09:30:43 node-2 haproxy[3325]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:43 node-2 haproxy[3325]: proxy keystone-1 has no server available!
<129>Oct 23 09:30:43 node-2 haproxy[3325]: 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>Oct 23 09:30:43 node-2 haproxy[3325]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:44 node-2 haproxy[3332]: proxy keystone-2 has no server available!
<129>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:44 node-2 haproxy[3332]: proxy nova-api has no server available!
<129>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:44 node-2 haproxy[3332]: proxy nova-metadata-api has no server available!
<129>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:44 node-2 haproxy[3332]: proxy glance-api has no server available!
<129>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:44 node-2 haproxy[3332]: proxy glance-glare has no server available!
<129>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:44 node-2 haproxy[3332]: proxy neutron has no server available!
<129>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:44 node-2 haproxy[3332]: proxy glance-registry has no server available!
<129>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:44 node-2 haproxy[3332]: 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>Oct 23 09:30:45 node-2 haproxy[3332]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:45 node-2 haproxy[3332]: proxy mysqld has no server available!
<129>Oct 23 09:30:45 node-2 haproxy[3332]: 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>Oct 23 09:30:45 node-2 haproxy[3332]: 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>Oct 23 09:30:45 node-2 haproxy[3332]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:45 node-2 haproxy[3332]: proxy object-storage has no server available!
<129>Oct 23 09:30:45 node-2 haproxy[3332]: 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>Oct 23 09:30:45 node-2 haproxy[3332]: 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>Oct 23 09:30:45 node-2 haproxy[3332]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:45 node-2 haproxy[3332]: proxy aodh has no server available!
<129>Oct 23 09:30:45 node-2 haproxy[3332]: 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>Oct 23 09:30:45 node-2 haproxy[3332]: 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>Oct 23 09:30:45 node-2 haproxy[3332]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:45 node-2 haproxy[3332]: proxy ceilometer has no server available!
<129>Oct 23 09:30:45 node-2 haproxy[3332]: 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>Oct 23 09:30:45 node-2 haproxy[3332]: 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>Oct 23 09:30:45 node-2 haproxy[3332]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:45 node-2 haproxy[3332]: proxy nova-novncproxy has no server available!
<27>Oct 23 09:30:46 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:46 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:46 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:46 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:46 node-2 multipathd: uevent trigger error
<129>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:49 node-2 haproxy[4672]: proxy keystone-1 has no server available!
<129>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:49 node-2 haproxy[4672]: proxy keystone-2 has no server available!
<129>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:49 node-2 haproxy[4672]: proxy nova-api has no server available!
<129>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:49 node-2 haproxy[4672]: proxy nova-metadata-api has no server available!
<129>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:49 node-2 haproxy[4672]: proxy cinder-api has no server available!
<129>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:49 node-2 haproxy[4672]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:50 node-2 haproxy[4681]: proxy glance-api has no server available!
<129>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:50 node-2 haproxy[4681]: proxy glance-glare has no server available!
<129>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:50 node-2 haproxy[4681]: proxy neutron has no server available!
<129>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:50 node-2 haproxy[4681]: proxy glance-registry has no server available!
<129>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:50 node-2 haproxy[4681]: proxy mysqld has no server available!
<129>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:50 node-2 haproxy[4681]: proxy object-storage has no server available!
<129>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:50 node-2 haproxy[4681]: proxy aodh has no server available!
<129>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:50 node-2 haproxy[4681]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:50 node-2 haproxy[4681]: proxy ceilometer has no server available!
<129>Oct 23 09:30:50 node-2 haproxy[4681]: 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>Oct 23 09:30:51 node-2 haproxy[4681]: 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>Oct 23 09:30:51 node-2 haproxy[4681]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:51 node-2 haproxy[4681]: proxy nova-novncproxy has no server available!
<27>Oct 23 09:30:52 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:52 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:52 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:52 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:52 node-2 multipathd: uevent trigger error
<129>Oct 23 09:30:54 node-2 haproxy[6065]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:55 node-2 haproxy[6070]: proxy keystone-1 has no server available!
<129>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:55 node-2 haproxy[6070]: proxy keystone-2 has no server available!
<129>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:55 node-2 haproxy[6070]: proxy nova-api has no server available!
<129>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:55 node-2 haproxy[6070]: proxy nova-metadata-api has no server available!
<129>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:55 node-2 haproxy[6070]: proxy cinder-api has no server available!
<129>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:55 node-2 haproxy[6070]: proxy glance-api has no server available!
<129>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:55 node-2 haproxy[6070]: proxy glance-glare has no server available!
<129>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:55 node-2 haproxy[6070]: proxy neutron has no server available!
<129>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:55 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:56 node-2 haproxy[6070]: proxy glance-registry has no server available!
<129>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:56 node-2 haproxy[6070]: proxy mysqld has no server available!
<129>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:56 node-2 haproxy[6070]: proxy object-storage has no server available!
<129>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:56 node-2 haproxy[6070]: proxy aodh has no server available!
<129>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:56 node-2 haproxy[6070]: proxy ceilometer has no server available!
<129>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:56 node-2 haproxy[6070]: proxy heat-api has no server available!
<129>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:56 node-2 haproxy[6070]: proxy heat-api-cfn has no server available!
<129>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:56 node-2 haproxy[6070]: proxy heat-api-cloudwatch has no server available!
<129>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: 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>Oct 23 09:30:56 node-2 haproxy[6070]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Oct 23 09:30:56 node-2 haproxy[6070]: proxy nova-novncproxy has no server available!
<27>Oct 23 09:30:58 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:58 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:58 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:58 node-2 multipathd: uevent trigger error
<27>Oct 23 09:30:58 node-2 multipathd: uevent trigger error
<27>Oct 23 09:31:01 node-2 multipathd: uevent trigger error
<27>Oct 23 09:31:01 node-2 multipathd: uevent trigger error
<27>Oct 23 09:31:01 node-2 multipathd: uevent trigger error
<27>Oct 23 09:31:01 node-2 multipathd: uevent trigger error
<27>Oct 23 09:31:01 node-2 multipathd: uevent trigger error
<27>Oct 23 09:31:08 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Oct 23 09:31:32 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>Oct 23 09:31:34 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Oct 23 09:32:01 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 23 09:32:06 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Oct 23 09:32:30 node-2 multipathd: uevent trigger error
<27>Oct 23 09:32:30 node-2 multipathd: uevent trigger error
<27>Oct 23 09:32:30 node-2 multipathd: uevent trigger error
<27>Oct 23 09:32:30 node-2 multipathd: uevent trigger error
<27>Oct 23 09:32:30 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:48 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:54 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:54 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:54 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:54 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:54 node-2 multipathd: uevent trigger error
<27>Oct 23 09:34:54 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:04 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Oct 23 09:35:04 node-2 apache2_error [Sun Oct 23 09:35:04.533103 2016] [mpm_event:notice] [pid 14695:tid 140329004701568] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 23 09:35:04 node-2 apache2_error [Sun Oct 23 09:35:04.533239 2016] [core:notice] [pid 14695:tid 140329004701568] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 23 09:35:13 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:13 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:13 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:13 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:13 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:13 node-2 multipathd: uevent trigger error
<43>Oct 23 09:35:14 node-2 apache2_error [Sun Oct 23 09:35:07.517541 2016] [mpm_event:notice] [pid 14695:tid 140329004701568] AH00491: caught SIGTERM, shutting down
<43>Oct 23 09:35:14 node-2 apache2_error [Sun Oct 23 09:35:08.603233 2016] [mpm_worker:notice] [pid 16390:tid 139867235280768] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Oct 23 09:35:14 node-2 apache2_error [Sun Oct 23 09:35:08.603268 2016] [core:notice] [pid 16390:tid 139867235280768] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 23 09:35:17 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:17 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:17 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:17 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:17 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:21 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:21 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:21 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:21 node-2 multipathd: uevent trigger error
<27>Oct 23 09:35:21 node-2 multipathd: uevent trigger error
<43>Oct 23 09:36:24 node-2 apache2_error [Sun Oct 23 09:36:22.182636 2016] [mpm_worker:notice] [pid 16390:tid 139867235280768] AH00295: caught SIGTERM, shutting down
<43>Oct 23 09:36:24 node-2 apache2_error [Sun Oct 23 09:36:22.942053 2016] [mpm_worker:notice] [pid 29325:tid 140268003911552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 23 09:36:24 node-2 apache2_error [Sun Oct 23 09:36:22.942100 2016] [core:notice] [pid 29325:tid 140268003911552] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 23 09:37:14 node-2 apache2_error [Sun Oct 23 09:37:06.672296 2016] [mpm_worker:notice] [pid 29325:tid 140268003911552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 23 09:37:14 node-2 apache2_error [Sun Oct 23 09:37:06.868607 2016] [mpm_worker:warn] [pid 29325:tid 140268003911552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 23 09:37:14 node-2 apache2_error [Sun Oct 23 09:37:06.871914 2016] [mpm_worker:notice] [pid 29325:tid 140268003911552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 23 09:37:14 node-2 apache2_error [Sun Oct 23 09:37:06.871937 2016] [core:notice] [pid 29325:tid 140268003911552] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 23 09:37:51 node-2 multipathd: uevent trigger error
<27>Oct 23 09:37:51 node-2 multipathd: uevent trigger error
<27>Oct 23 09:37:51 node-2 multipathd: uevent trigger error
<27>Oct 23 09:37:51 node-2 multipathd: uevent trigger error
<27>Oct 23 09:37:51 node-2 multipathd: uevent trigger error
<27>Oct 23 09:37:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:37:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:37:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:37:56 node-2 multipathd: uevent trigger error
<27>Oct 23 09:37:56 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:06 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 23 09:38:11 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:11 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:11 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:11 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:11 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:32 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:32 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:32 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:32 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:32 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:37 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:37 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:37 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:37 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:37 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:52 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:52 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:52 node-2 multipathd: uevent trigger error
<27>Oct 23 09:38:52 node-2 multipathd: uevent trigger error
<27>Oct 23 09:39:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:39:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:39:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:39:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:40:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:40:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:40:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:40:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:40:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:41:07 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 23 09:41:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:41:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:41:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:41:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:41:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:09 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:09 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:09 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:09 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:09 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:15 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:15 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:15 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:15 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:15 node-2 multipathd: uevent trigger error
<27>Oct 23 09:42:15 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:09 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 23 09:44:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:44:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:05 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:05 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:05 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:05 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:05 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:50 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:51 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:51 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:51 node-2 multipathd: uevent trigger error
<27>Oct 23 09:45:51 node-2 multipathd: uevent trigger error
<27>Oct 23 09:46:12 node-2 multipathd: uevent trigger error
<27>Oct 23 09:46:12 node-2 multipathd: uevent trigger error
<27>Oct 23 09:46:12 node-2 multipathd: uevent trigger error
<27>Oct 23 09:46:12 node-2 multipathd: uevent trigger error
<27>Oct 23 09:46:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:46:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:46:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:46:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:46:55 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:02 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Oct 23 09:47:02 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Oct 23 09:47:02 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Oct 23 09:47:03 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Oct 23 09:47:03 node-2 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Oct 23 09:47:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:11 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 23 09:47:16 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:16 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:16 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:16 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:16 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:31 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:31 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:31 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:31 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:31 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:47 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:47 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:47 node-2 multipathd: uevent trigger error
<27>Oct 23 09:47:47 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:06 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:06 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:06 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:06 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:06 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:13 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 23 09:50:33 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:33 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:33 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:33 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:33 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:39 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:39 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:39 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:39 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:39 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:59 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:59 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:59 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:59 node-2 multipathd: uevent trigger error
<27>Oct 23 09:50:59 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:03 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:03 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:03 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:03 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:03 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:08 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:08 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:08 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:08 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:19 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:19 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:20 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:20 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:26 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:26 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:26 node-2 multipathd: uevent trigger error
<27>Oct 23 09:51:26 node-2 multipathd: uevent trigger error
<27>Oct 23 09:52:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:52:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:52:04 node-2 multipathd: uevent trigger error
<27>Oct 23 09:53:14 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 23 09:53:17 node-2 multipathd: uevent trigger error
<27>Oct 23 09:53:17 node-2 multipathd: uevent trigger error
<27>Oct 23 09:53:17 node-2 multipathd: uevent trigger error
<27>Oct 23 09:53:17 node-2 multipathd: uevent trigger error
<27>Oct 23 09:53:17 node-2 multipathd: uevent trigger error
<27>Oct 23 09:53:33 node-2 multipathd: uevent trigger error
<27>Oct 23 09:53:33 node-2 multipathd: uevent trigger error
<27>Oct 23 09:53:33 node-2 multipathd: uevent trigger error
<27>Oct 23 09:53:33 node-2 multipathd: uevent trigger error
<27>Oct 23 09:53:33 node-2 multipathd: uevent trigger error
<11>Oct 23 09:53:45 node-2 liberasurecode[9076]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:45 node-2 liberasurecode[9076]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:45 node-2 liberasurecode[9076]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:45 node-2 liberasurecode[9076]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:45 node-2 liberasurecode[9107]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:45 node-2 liberasurecode[9107]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:45 node-2 liberasurecode[9107]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:45 node-2 liberasurecode[9107]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:47 node-2 liberasurecode[9531]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:47 node-2 liberasurecode[9531]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:47 node-2 liberasurecode[9531]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:47 node-2 liberasurecode[9531]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:51 node-2 liberasurecode[10036]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:51 node-2 liberasurecode[10036]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:51 node-2 liberasurecode[10036]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:51 node-2 liberasurecode[10036]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10072]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10072]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10072]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10072]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10116]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10116]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10116]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10116]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10182]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10182]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10182]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10182]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10194]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10194]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10194]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10194]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10222]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10222]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10222]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10222]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10236]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10236]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10236]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:53:52 node-2 liberasurecode[10236]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Oct 23 09:54:01 node-2 liberasurecode[10621]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:54:01 node-2 liberasurecode[10621]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:54:01 node-2 liberasurecode[10621]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:54:01 node-2 liberasurecode[10621]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 23 09:54:10 node-2 multipathd: uevent trigger error
<27>Oct 23 09:54:10 node-2 multipathd: uevent trigger error
<27>Oct 23 09:54:10 node-2 multipathd: uevent trigger error
<27>Oct 23 09:54:10 node-2 multipathd: uevent trigger error
<27>Oct 23 09:54:10 node-2 multipathd: uevent trigger error
<27>Oct 23 09:54:10 node-2 multipathd: uevent trigger error
<27>Oct 23 09:54:10 node-2 multipathd: uevent trigger error
<11>Oct 23 09:55:01 node-2 liberasurecode[19769]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:55:01 node-2 liberasurecode[19769]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:55:01 node-2 liberasurecode[19769]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 09:55:01 node-2 liberasurecode[19769]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Oct 23 09:55:06 node-2 apache2_error [Sun Oct 23 09:54:56.871255 2016] [mpm_worker:notice] [pid 29325:tid 140268003911552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 23 09:55:06 node-2 apache2_error [Sun Oct 23 09:54:57.255924 2016] [mpm_worker:warn] [pid 29325:tid 140268003911552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 23 09:55:06 node-2 apache2_error [Sun Oct 23 09:54:57.261610 2016] [mpm_worker:notice] [pid 29325:tid 140268003911552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 23 09:55:06 node-2 apache2_error [Sun Oct 23 09:54:57.261642 2016] [core:notice] [pid 29325:tid 140268003911552] AH00094: Command line: '/usr/sbin/apache2'
<43>Oct 23 09:55:36 node-2 apache2_error [Sun Oct 23 09:55:34.691467 2016] [mpm_worker:notice] [pid 29325:tid 140268003911552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 23 09:55:36 node-2 apache2_error [Sun Oct 23 09:55:34.885565 2016] [mpm_worker:warn] [pid 29325:tid 140268003911552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 23 09:55:36 node-2 apache2_error [Sun Oct 23 09:55:34.890460 2016] [mpm_worker:notice] [pid 29325:tid 140268003911552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 23 09:55:36 node-2 apache2_error [Sun Oct 23 09:55:34.890483 2016] [core:notice] [pid 29325:tid 140268003911552] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 23 09:55:38 node-2 multipathd: uevent trigger error
<27>Oct 23 09:55:38 node-2 multipathd: uevent trigger error
<27>Oct 23 09:55:38 node-2 multipathd: uevent trigger error
<27>Oct 23 09:55:38 node-2 multipathd: uevent trigger error
<27>Oct 23 09:55:38 node-2 multipathd: uevent trigger error
<27>Oct 23 09:55:46 node-2 multipathd: uevent trigger error
<27>Oct 23 09:55:46 node-2 multipathd: uevent trigger error
<27>Oct 23 09:55:46 node-2 multipathd: uevent trigger error
<27>Oct 23 09:55:46 node-2 multipathd: uevent trigger error
<27>Oct 23 09:55:46 node-2 multipathd: uevent trigger error
<27>Oct 23 09:55:46 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:15 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Oct 23 09:56:24 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:24 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:24 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:25 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:25 node-2 multipathd: uevent trigger error
<43>Oct 23 09:56:26 node-2 apache2_error [Sun Oct 23 09:56:20.707263 2016] [mpm_worker:notice] [pid 29325:tid 140268003911552] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Oct 23 09:56:26 node-2 apache2_error [Sun Oct 23 09:56:20.903121 2016] [mpm_worker:warn] [pid 29325:tid 140268003911552] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Oct 23 09:56:26 node-2 apache2_error [Sun Oct 23 09:56:20.908662 2016] [mpm_worker:notice] [pid 29325:tid 140268003911552] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Oct 23 09:56:26 node-2 apache2_error [Sun Oct 23 09:56:20.908689 2016] [core:notice] [pid 29325:tid 140268003911552] AH00094: Command line: '/usr/sbin/apache2'
<27>Oct 23 09:56:31 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:31 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:31 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:31 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:31 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:35 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:41 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:57 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:57 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:57 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:57 node-2 multipathd: uevent trigger error
<27>Oct 23 09:56:57 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:18 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:25 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:25 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:25 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:25 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:25 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:31 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Oct 23 09:57:40 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:40 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:40 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:40 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:57:45 node-2 multipathd: uevent trigger error
<27>Oct 23 09:58:26 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<11>Oct 23 10:00:01 node-2 liberasurecode[16273]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 10:00:01 node-2 liberasurecode[16273]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 10:00:01 node-2 liberasurecode[16273]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 10:00:01 node-2 liberasurecode[16273]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Oct 23 10:00:34 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:34 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:34 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:34 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:34 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:40 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:40 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:40 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:40 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:40 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:48 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:48 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:48 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:48 node-2 multipathd: uevent trigger error
<27>Oct 23 10:00:48 node-2 multipathd: uevent trigger error
<129>Oct 23 10:01:00 node-2 haproxy[26066]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Oct 23 10:01:00 node-2 haproxy[26066]: 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.
<27>Oct 23 10:01:00 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:00 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:00 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:00 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:16 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:16 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:16 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:16 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:23 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:23 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:23 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:23 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:23 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:38 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:38 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:38 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:39 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:39 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:52 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:52 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:52 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:52 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:52 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:57 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:57 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:57 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:57 node-2 multipathd: uevent trigger error
<27>Oct 23 10:01:57 node-2 multipathd: uevent trigger error
<27>Oct 23 10:02:10 node-2 multipathd: uevent trigger error
<27>Oct 23 10:02:10 node-2 multipathd: uevent trigger error
<27>Oct 23 10:02:10 node-2 multipathd: uevent trigger error
<27>Oct 23 10:02:10 node-2 multipathd: uevent trigger error
<27>Oct 23 10:02:10 node-2 multipathd: uevent trigger error
<27>Oct 23 10:02:21 node-2 multipathd: uevent trigger error
<27>Oct 23 10:02:21 node-2 multipathd: uevent trigger error
<27>Oct 23 10:02:21 node-2 multipathd: uevent trigger error
<27>Oct 23 10:02:21 node-2 multipathd: uevent trigger error
<27>Oct 23 10:02:21 node-2 multipathd: uevent trigger error
<129>Oct 23 10:02:30 node-2 haproxy[26066]: 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>Oct 23 10:03:11 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:11 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:11 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:11 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:11 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:15 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:15 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:15 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:15 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:15 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:20 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:20 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:20 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:20 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:20 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:25 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:25 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:25 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:25 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:25 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:29 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:29 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:29 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:29 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:29 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:33 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:33 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:33 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:33 node-2 multipathd: uevent trigger error
<27>Oct 23 10:03:33 node-2 multipathd: uevent trigger error
<11>Oct 23 10:05:01 node-2 liberasurecode[19870]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 10:05:01 node-2 liberasurecode[19870]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 10:05:01 node-2 liberasurecode[19870]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Oct 23 10:05:01 node-2 liberasurecode[19870]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
