Nov  5 05:56:11 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8393" x-info="http://www.rsyslog.com"] start
Nov  5 05:56:11 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Nov  5 05:56:11 node-3 rsyslogd: rsyslogd's groupid changed to 104
Nov  5 05:56:11 node-3 rsyslogd: rsyslogd's userid changed to 101
Nov  5 05:56:11 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuset
Nov  5 05:56:11 node-3 kernel: [    0.000000] Initializing cgroup subsys cpu
Nov  5 05:56:11 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Nov  5 05:56:11 node-3 kernel: [    0.000000] Linux version 3.13.0-100-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #147-Ubuntu SMP Tue Oct 18 16:48:51 UTC 2016 (Ubuntu 3.13.0-100.147-generic 3.13.11-ckt39)
Nov  5 05:56:11 node-3 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=bd9f69e0-e47b-46b0-8a48-ccd1cf4b9d5f nomdmonddf nomdmonisw
Nov  5 05:56:11 node-3 kernel: [    0.000000] KERNEL supported cpus:
Nov  5 05:56:11 node-3 kernel: [    0.000000]   Intel GenuineIntel
Nov  5 05:56:11 node-3 kernel: [    0.000000]   AMD AuthenticAMD
Nov  5 05:56:11 node-3 kernel: [    0.000000]   Centaur CentaurHauls
Nov  5 05:56:11 node-3 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Nov  5 05:56:11 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Nov  5 05:56:11 node-3 kernel: [    0.000000] NX (Execute Disable) protection: active
Nov  5 05:56:11 node-3 kernel: [    0.000000] SMBIOS 2.8 present.
Nov  5 05:56:11 node-3 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Nov  5 05:56:11 node-3 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Nov  5 05:56:11 node-3 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Nov  5 05:56:11 node-3 kernel: [    0.000000] No AGP bridge found
Nov  5 05:56:11 node-3 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Nov  5 05:56:11 node-3 kernel: [    0.000000] MTRR default type: write-back
Nov  5 05:56:11 node-3 kernel: [    0.000000] MTRR fixed ranges enabled:
Nov  5 05:56:11 node-3 kernel: [    0.000000]   00000-9FFFF write-back
Nov  5 05:56:11 node-3 kernel: [    0.000000]   A0000-BFFFF uncachable
Nov  5 05:56:11 node-3 kernel: [    0.000000]   C0000-FFFFF write-protect
Nov  5 05:56:11 node-3 kernel: [    0.000000] MTRR variable ranges enabled:
Nov  5 05:56:11 node-3 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Nov  5 05:56:11 node-3 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Nov  5 05:56:11 node-3 kernel: [    0.000000]   2 disabled
Nov  5 05:56:11 node-3 kernel: [    0.000000]   3 disabled
Nov  5 05:56:11 node-3 kernel: [    0.000000]   4 disabled
Nov  5 05:56:11 node-3 kernel: [    0.000000]   5 disabled
Nov  5 05:56:11 node-3 kernel: [    0.000000]   6 disabled
Nov  5 05:56:11 node-3 kernel: [    0.000000]   7 disabled
Nov  5 05:56:11 node-3 kernel: [    0.000000]   8 disabled
Nov  5 05:56:11 node-3 kernel: [    0.000000]   9 disabled
Nov  5 05:56:11 node-3 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Nov  5 05:56:11 node-3 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Nov  5 05:56:11 node-3 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Nov  5 05:56:11 node-3 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Nov  5 05:56:11 node-3 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Nov  5 05:56:11 node-3 kernel: [    0.000000] Using GB pages for direct mapping
Nov  5 05:56:11 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Nov  5 05:56:11 node-3 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Nov  5 05:56:11 node-3 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Nov  5 05:56:11 node-3 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Nov  5 05:56:11 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Nov  5 05:56:11 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Nov  5 05:56:11 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Nov  5 05:56:11 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Nov  5 05:56:11 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Nov  5 05:56:11 node-3 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Nov  5 05:56:11 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Nov  5 05:56:11 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Nov  5 05:56:11 node-3 kernel: [    0.000000] RAMDISK: [mem 0x35826000-0x36c0afff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Nov  5 05:56:11 node-3 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Nov  5 05:56:11 node-3 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Nov  5 05:56:11 node-3 kernel: [    0.000000] Zone ranges:
Nov  5 05:56:11 node-3 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] Movable zone start for each node
Nov  5 05:56:11 node-3 kernel: [    0.000000] Early memory node ranges
Nov  5 05:56:11 node-3 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] On node 0 totalpages: 4125855
Nov  5 05:56:11 node-3 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Nov  5 05:56:11 node-3 kernel: [    0.000000]   DMA zone: 21 pages reserved
Nov  5 05:56:11 node-3 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Nov  5 05:56:11 node-3 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Nov  5 05:56:11 node-3 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Nov  5 05:56:11 node-3 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Nov  5 05:56:11 node-3 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Nov  5 05:56:11 node-3 kernel: [    0.000000] On node 1 totalpages: 4194304
Nov  5 05:56:11 node-3 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Nov  5 05:56:11 node-3 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Nov  5 05:56:11 node-3 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Nov  5 05:56:11 node-3 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Nov  5 05:56:11 node-3 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: IRQ0 used by override.
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: IRQ2 used by override.
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: IRQ9 used by override.
Nov  5 05:56:11 node-3 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Nov  5 05:56:11 node-3 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Nov  5 05:56:11 node-3 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Nov  5 05:56:11 node-3 kernel: [    0.000000] nr_irqs_gsi: 88
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Nov  5 05:56:11 node-3 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Nov  5 05:56:11 node-3 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Nov  5 05:56:11 node-3 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Nov  5 05:56:11 node-3 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Nov  5 05:56:11 node-3 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Nov  5 05:56:11 node-3 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Nov  5 05:56:11 node-3 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Nov  5 05:56:11 node-3 kernel: [    0.000000] Policy zone: Normal
Nov  5 05:56:11 node-3 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-100-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=bd9f69e0-e47b-46b0-8a48-ccd1cf4b9d5f nomdmonddf nomdmonisw
Nov  5 05:56:11 node-3 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Nov  5 05:56:11 node-3 kernel: [    0.000000] Checking aperture...
Nov  5 05:56:11 node-3 kernel: [    0.000000] No AGP bridge found
Nov  5 05:56:11 node-3 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Nov  5 05:56:11 node-3 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Nov  5 05:56:11 node-3 kernel: [    0.000000] Memory: 32653464K/33280636K available (7421K kernel code, 1146K rwdata, 3420K rodata, 1336K init, 1448K bss, 627172K reserved)
Nov  5 05:56:11 node-3 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Nov  5 05:56:11 node-3 kernel: [    0.000000] Hierarchical RCU implementation.
Nov  5 05:56:11 node-3 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Nov  5 05:56:11 node-3 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Nov  5 05:56:11 node-3 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Nov  5 05:56:11 node-3 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Nov  5 05:56:11 node-3 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Nov  5 05:56:11 node-3 kernel: [    0.000000] Console: colour dummy device 80x25
Nov  5 05:56:11 node-3 kernel: [    0.000000] console [tty0] enabled
Nov  5 05:56:11 node-3 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Nov  5 05:56:11 node-3 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Nov  5 05:56:11 node-3 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Nov  5 05:56:11 node-3 kernel: [    0.000000] hpet clockevent registered
Nov  5 05:56:11 node-3 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Nov  5 05:56:11 node-3 kernel: [    0.004000] tsc: Detected 3492.018 MHz processor
Nov  5 05:56:11 node-3 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.03 BogoMIPS (lpj=13968072)
Nov  5 05:56:11 node-3 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Nov  5 05:56:11 node-3 kernel: [    0.000044] Security Framework initialized
Nov  5 05:56:11 node-3 kernel: [    0.000062] AppArmor: AppArmor initialized
Nov  5 05:56:11 node-3 kernel: [    0.000064] Yama: becoming mindful.
Nov  5 05:56:11 node-3 kernel: [    0.001469] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.006438] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.008364] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.008392] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.008679] Initializing cgroup subsys memory
Nov  5 05:56:11 node-3 kernel: [    0.008687] Initializing cgroup subsys devices
Nov  5 05:56:11 node-3 kernel: [    0.008689] Initializing cgroup subsys freezer
Nov  5 05:56:11 node-3 kernel: [    0.008691] Initializing cgroup subsys blkio
Nov  5 05:56:11 node-3 kernel: [    0.008692] Initializing cgroup subsys perf_event
Nov  5 05:56:11 node-3 kernel: [    0.008695] Initializing cgroup subsys hugetlb
Nov  5 05:56:11 node-3 kernel: [    0.008714] CPU: Physical Processor ID: 0
Nov  5 05:56:11 node-3 kernel: [    0.008716] CPU: Processor Core ID: 0
Nov  5 05:56:11 node-3 kernel: [    0.008719] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Nov  5 05:56:11 node-3 kernel: [    0.008719] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Nov  5 05:56:11 node-3 kernel: [    0.009413] mce: CPU supports 22 MCE banks
Nov  5 05:56:11 node-3 kernel: [    0.009440] CPU0: Thermal monitoring enabled (TM1)
Nov  5 05:56:11 node-3 kernel: [    0.009461] process: using mwait in idle threads
Nov  5 05:56:11 node-3 kernel: [    0.009464] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Nov  5 05:56:11 node-3 kernel: [    0.009464] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Nov  5 05:56:11 node-3 kernel: [    0.009464] tlb_flushall_shift: 6
Nov  5 05:56:11 node-3 kernel: [    0.009552] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Nov  5 05:56:11 node-3 kernel: [    0.010275] ACPI: Core revision 20131115
Nov  5 05:56:11 node-3 kernel: [    0.023067] ACPI: All ACPI Tables successfully acquired
Nov  5 05:56:11 node-3 kernel: [    0.023228] ftrace: allocating 28622 entries in 112 pages
Nov  5 05:56:11 node-3 kernel: [    0.031984] dmar: Host address width 46
Nov  5 05:56:11 node-3 kernel: [    0.031986] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Nov  5 05:56:11 node-3 kernel: [    0.031992] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  5 05:56:11 node-3 kernel: [    0.031994] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Nov  5 05:56:11 node-3 kernel: [    0.031998] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Nov  5 05:56:11 node-3 kernel: [    0.032000] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Nov  5 05:56:11 node-3 kernel: [    0.032001] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Nov  5 05:56:11 node-3 kernel: [    0.032002] dmar: ATSR flags: 0x0
Nov  5 05:56:11 node-3 kernel: [    0.032003] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Nov  5 05:56:11 node-3 kernel: [    0.032005] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Nov  5 05:56:11 node-3 kernel: [    0.032120] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Nov  5 05:56:11 node-3 kernel: [    0.032121] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Nov  5 05:56:11 node-3 kernel: [    0.032122] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Nov  5 05:56:11 node-3 kernel: [    0.032123] HPET id 0 under DRHD base 0xc7ffc000
Nov  5 05:56:11 node-3 kernel: [    0.032124] Your BIOS is broken and requested that x2apic be disabled.
Nov  5 05:56:11 node-3 kernel: [    0.032124] This will slightly decrease performance.
Nov  5 05:56:11 node-3 kernel: [    0.032124] Use 'intremap=no_x2apic_optout' to override BIOS request.
Nov  5 05:56:11 node-3 kernel: [    0.032556] Enabled IRQ remapping in xapic mode
Nov  5 05:56:11 node-3 kernel: [    0.032558] x2apic not enabled, IRQ remapping is in xapic mode
Nov  5 05:56:11 node-3 kernel: [    0.032561] Switched APIC routing to physical flat.
Nov  5 05:56:11 node-3 kernel: [    0.033146] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Nov  5 05:56:11 node-3 kernel: [    0.072797] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Nov  5 05:56:11 node-3 kernel: [    0.072802] TSC deadline timer enabled
Nov  5 05:56:11 node-3 kernel: [    0.072810] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Nov  5 05:56:11 node-3 kernel: [    0.072816] ... version:                3
Nov  5 05:56:11 node-3 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Nov  5 05:56:11 node-3 kernel: [    0.072817] ... bit width:              48
Nov  5 05:56:11 node-3 kernel: [    0.072818] ... generic registers:      4
Nov  5 05:56:11 node-3 kernel: [    0.072819] ... value mask:             0000ffffffffffff
Nov  5 05:56:11 node-3 kernel: [    0.072820] ... max period:             0000ffffffffffff
Nov  5 05:56:11 node-3 kernel: [    0.072821] ... fixed-purpose events:   3
Nov  5 05:56:11 node-3 kernel: [    0.072822] ... event mask:             000000070000000f
Nov  5 05:56:11 node-3 kernel: [    0.074220] x86: Booting SMP configuration:
Nov  5 05:56:11 node-3 kernel: [    0.088327] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Nov  5 05:56:11 node-3 kernel: [    0.074222] .... node  #0, CPUs:        #1  #2  #3
Nov  5 05:56:11 node-3 kernel: [    0.116236] .... node  #1, CPUs:    #4  #5  #6  #7
Nov  5 05:56:11 node-3 kernel: [    0.270392] .... node  #0, CPUs:    #8  #9 #10 #11
Nov  5 05:56:11 node-3 kernel: [    0.326011] .... node  #1, CPUs:   #12 #13 #14 #15
Nov  5 05:56:11 node-3 kernel: [    0.383061] x86: Booted up 2 nodes, 16 CPUs
Nov  5 05:56:11 node-3 kernel: [    0.383064] smpboot: Total of 16 processors activated (111757.45 BogoMIPS)
Nov  5 05:56:11 node-3 kernel: [    0.407218] devtmpfs: initialized
Nov  5 05:56:11 node-3 kernel: [    0.409556] EVM: security.selinux
Nov  5 05:56:11 node-3 kernel: [    0.409558] EVM: security.SMACK64
Nov  5 05:56:11 node-3 kernel: [    0.409559] EVM: security.ima
Nov  5 05:56:11 node-3 kernel: [    0.409560] EVM: security.capability
Nov  5 05:56:11 node-3 kernel: [    0.409611] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.410257] pinctrl core: initialized pinctrl subsystem
Nov  5 05:56:11 node-3 kernel: [    0.410317] regulator-dummy: no parameters
Nov  5 05:56:11 node-3 kernel: [    0.410349] RTC time:  5:55:35, date: 11/05/16
Nov  5 05:56:11 node-3 kernel: [    0.410382] NET: Registered protocol family 16
Nov  5 05:56:11 node-3 kernel: [    0.410466] cpuidle: using governor ladder
Nov  5 05:56:11 node-3 kernel: [    0.410467] cpuidle: using governor menu
Nov  5 05:56:11 node-3 kernel: [    0.410502] ACPI: bus type PCI registered
Nov  5 05:56:11 node-3 kernel: [    0.410504] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Nov  5 05:56:11 node-3 kernel: [    0.410547] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Nov  5 05:56:11 node-3 kernel: [    0.410550] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Nov  5 05:56:11 node-3 kernel: [    0.424293] PCI: Using configuration type 1 for base access
Nov  5 05:56:11 node-3 kernel: [    0.425283] bio: create slab <bio-0> at 0
Nov  5 05:56:11 node-3 kernel: [    0.425563] ACPI: Added _OSI(Module Device)
Nov  5 05:56:11 node-3 kernel: [    0.425565] ACPI: Added _OSI(Processor Device)
Nov  5 05:56:11 node-3 kernel: [    0.425566] ACPI: Added _OSI(3.0 _SCP Extensions)
Nov  5 05:56:11 node-3 kernel: [    0.425567] ACPI: Added _OSI(Processor Aggregator Device)
Nov  5 05:56:11 node-3 kernel: [    0.438284] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Nov  5 05:56:11 node-3 kernel: [    0.449779] ACPI: Interpreter enabled
Nov  5 05:56:11 node-3 kernel: [    0.449784] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Nov  5 05:56:11 node-3 kernel: [    0.449788] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Nov  5 05:56:11 node-3 kernel: [    0.449791] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Nov  5 05:56:11 node-3 kernel: [    0.449798] ACPI: (supports S0 S4 S5)
Nov  5 05:56:11 node-3 kernel: [    0.449800] ACPI: Using IOAPIC for interrupt routing
Nov  5 05:56:11 node-3 kernel: [    0.449840] HEST: Table parsing has been initialized.
Nov  5 05:56:11 node-3 kernel: [    0.449843] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Nov  5 05:56:11 node-3 kernel: [    0.450396] ACPI: No dock devices found.
Nov  5 05:56:11 node-3 kernel: [    0.461936] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Nov  5 05:56:11 node-3 kernel: [    0.461941] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 05:56:11 node-3 kernel: [    0.461945] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  5 05:56:11 node-3 kernel: [    0.461973] PCI host bridge to bus 0000:ff
Nov  5 05:56:11 node-3 kernel: [    0.461975] pci_bus 0000:ff: root bus resource [bus ff]
Nov  5 05:56:11 node-3 kernel: [    0.461984] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462023] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.462053] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462089] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462119] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.462149] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.462181] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462211] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462242] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462270] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462297] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462324] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462352] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462378] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462405] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462432] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462461] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462488] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462515] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.462543] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462569] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.462594] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462620] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462650] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.462685] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462716] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462746] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462777] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462808] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462839] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462870] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462902] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462933] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462965] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.462998] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463031] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463064] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463094] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463122] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463154] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463186] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463223] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463258] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463290] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463321] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463352] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463384] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463415] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463447] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463478] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463510] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463539] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463569] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463598] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463627] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463658] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463690] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463747] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Nov  5 05:56:11 node-3 kernel: [    0.463749] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 05:56:11 node-3 kernel: [    0.463752] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Nov  5 05:56:11 node-3 kernel: [    0.463770] PCI host bridge to bus 0000:7f
Nov  5 05:56:11 node-3 kernel: [    0.463772] pci_bus 0000:7f: root bus resource [bus 7f]
Nov  5 05:56:11 node-3 kernel: [    0.463777] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463804] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.463832] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463861] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463883] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.463907] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.463932] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463958] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.463980] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464002] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464025] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464047] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464071] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464097] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464123] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464153] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464175] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464202] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464226] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.464249] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464271] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.464293] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464316] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464342] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Nov  5 05:56:11 node-3 kernel: [    0.464374] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464400] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464426] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464451] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464476] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464502] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464529] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464556] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464581] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464607] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464632] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464660] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464688] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464713] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464740] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464767] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464792] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464818] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464846] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464874] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464900] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464925] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464950] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.464976] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.465002] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.465028] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.465057] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.465082] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.465104] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.465128] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.465153] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.465183] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.465210] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.466468] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Nov  5 05:56:11 node-3 kernel: [    0.466471] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 05:56:11 node-3 kernel: [    0.467591] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  5 05:56:11 node-3 kernel: [    0.468105] PCI host bridge to bus 0000:00
Nov  5 05:56:11 node-3 kernel: [    0.468108] pci_bus 0000:00: root bus resource [bus 00-7e]
Nov  5 05:56:11 node-3 kernel: [    0.468110] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Nov  5 05:56:11 node-3 kernel: [    0.468111] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Nov  5 05:56:11 node-3 kernel: [    0.468112] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Nov  5 05:56:11 node-3 kernel: [    0.468114] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Nov  5 05:56:11 node-3 kernel: [    0.468115] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Nov  5 05:56:11 node-3 kernel: [    0.468117] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Nov  5 05:56:11 node-3 kernel: [    0.468122] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Nov  5 05:56:11 node-3 kernel: [    0.468206] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.468237] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.468278] pci 0000:00:01.0: System wakeup disabled by ACPI
Nov  5 05:56:11 node-3 kernel: [    0.468298] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.468328] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.468368] pci 0000:00:02.0: System wakeup disabled by ACPI
Nov  5 05:56:11 node-3 kernel: [    0.468387] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.468417] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.468457] pci 0000:00:03.0: System wakeup disabled by ACPI
Nov  5 05:56:11 node-3 kernel: [    0.468475] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.468546] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.468624] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.468702] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Nov  5 05:56:11 node-3 kernel: [    0.468707] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Nov  5 05:56:11 node-3 kernel: [    0.468792] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Nov  5 05:56:11 node-3 kernel: [    0.468941] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Nov  5 05:56:11 node-3 kernel: [    0.468958] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Nov  5 05:56:11 node-3 kernel: [    0.469035] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.469089] pci 0000:00:1a.0: System wakeup disabled by ACPI
Nov  5 05:56:11 node-3 kernel: [    0.469110] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.469166] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.469209] pci 0000:00:1c.0: System wakeup disabled by ACPI
Nov  5 05:56:11 node-3 kernel: [    0.469236] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.469292] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.469335] pci 0000:00:1c.7: System wakeup disabled by ACPI
Nov  5 05:56:11 node-3 kernel: [    0.469359] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Nov  5 05:56:11 node-3 kernel: [    0.469376] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Nov  5 05:56:11 node-3 kernel: [    0.469454] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.469503] pci 0000:00:1d.0: System wakeup disabled by ACPI
Nov  5 05:56:11 node-3 kernel: [    0.469531] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Nov  5 05:56:11 node-3 kernel: [    0.469776] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Nov  5 05:56:11 node-3 kernel: [    0.469782] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Nov  5 05:56:11 node-3 kernel: [    0.469788] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.469794] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.469801] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Nov  5 05:56:11 node-3 kernel: [    0.469831] pci 0000:01:00.0: supports D1 D2
Nov  5 05:56:11 node-3 kernel: [    0.480106] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  5 05:56:11 node-3 kernel: [    0.480113] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  5 05:56:11 node-3 kernel: [    0.480117] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  5 05:56:11 node-3 kernel: [    0.480326] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.480360] pci 0000:02:00.0: PME# supported from D0 D3hot
Nov  5 05:56:11 node-3 kernel: [    0.488104] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  5 05:56:11 node-3 kernel: [    0.488110] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.488114] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 05:56:11 node-3 kernel: [    0.488205] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.488273] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.488350] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.488394] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  5 05:56:11 node-3 kernel: [    0.488398] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.488400] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 05:56:11 node-3 kernel: [    0.488452] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.488578] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.488631] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  5 05:56:11 node-3 kernel: [    0.488634] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.488636] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 05:56:11 node-3 kernel: [    0.488685] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.488804] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.488842] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.488961] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.488997] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.489131] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.489167] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Nov  5 05:56:11 node-3 kernel: [    0.489286] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Nov  5 05:56:11 node-3 kernel: [    0.489327] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  5 05:56:11 node-3 kernel: [    0.489329] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.489331] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 05:56:11 node-3 kernel: [    0.489389] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Nov  5 05:56:11 node-3 kernel: [    0.489454] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.489506] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.489548] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Nov  5 05:56:11 node-3 kernel: [    0.489630] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Nov  5 05:56:11 node-3 kernel: [    0.489734] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  5 05:56:11 node-3 kernel: [    0.489737] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.489739] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  5 05:56:11 node-3 kernel: [    0.489795] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Nov  5 05:56:11 node-3 kernel: [    0.489848] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.489897] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.490120] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  5 05:56:11 node-3 kernel: [    0.490123] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  5 05:56:11 node-3 kernel: [    0.490189] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Nov  5 05:56:11 node-3 kernel: [    0.490245] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.490294] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.490504] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  5 05:56:11 node-3 kernel: [    0.490508] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  5 05:56:11 node-3 kernel: [    0.490567] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Nov  5 05:56:11 node-3 kernel: [    0.490627] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.490679] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Nov  5 05:56:11 node-3 kernel: [    0.490901] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  5 05:56:11 node-3 kernel: [    0.490905] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  5 05:56:11 node-3 kernel: [    0.491082] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  5 05:56:11 node-3 kernel: [    0.491120] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  5 05:56:11 node-3 kernel: [    0.491199] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Nov  5 05:56:11 node-3 kernel: [    0.491217] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Nov  5 05:56:11 node-3 kernel: [    0.491230] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Nov  5 05:56:11 node-3 kernel: [    0.491244] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Nov  5 05:56:11 node-3 kernel: [    0.491294] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Nov  5 05:56:11 node-3 kernel: [    0.496118] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  5 05:56:11 node-3 kernel: [    0.496127] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  5 05:56:11 node-3 kernel: [    0.496179] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Nov  5 05:56:11 node-3 kernel: [    0.496698] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Nov  5 05:56:11 node-3 kernel: [    0.496701] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Nov  5 05:56:11 node-3 kernel: [    0.496821] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Nov  5 05:56:11 node-3 kernel: [    0.496929] PCI host bridge to bus 0000:80
Nov  5 05:56:11 node-3 kernel: [    0.496931] pci_bus 0000:80: root bus resource [bus 80-fe]
Nov  5 05:56:11 node-3 kernel: [    0.496933] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Nov  5 05:56:11 node-3 kernel: [    0.496934] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Nov  5 05:56:11 node-3 kernel: [    0.496942] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.497006] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.497074] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Nov  5 05:56:11 node-3 kernel: [    0.497139] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Nov  5 05:56:11 node-3 kernel: [    0.497144] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Nov  5 05:56:11 node-3 kernel: [    0.497217] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Nov  5 05:56:11 node-3 kernel: [    0.497514] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Nov  5 05:56:11 node-3 kernel: [    0.497545] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Nov  5 05:56:11 node-3 kernel: [    0.497575] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Nov  5 05:56:11 node-3 kernel: [    0.497604] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Nov  5 05:56:11 node-3 kernel: [    0.497633] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 05:56:11 node-3 kernel: [    0.497663] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 05:56:11 node-3 kernel: [    0.497692] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 05:56:11 node-3 kernel: [    0.497722] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Nov  5 05:56:11 node-3 kernel: [    0.497808] ACPI: Enabled 3 GPEs in block 00 to 3F
Nov  5 05:56:11 node-3 kernel: [    0.497813] ACPI: \_SB_.UNC1: notify handler is installed
Nov  5 05:56:11 node-3 kernel: [    0.497814] ACPI: \_SB_.UNC0: notify handler is installed
Nov  5 05:56:11 node-3 kernel: [    0.497829] ACPI: \_SB_.PCI0: notify handler is installed
Nov  5 05:56:11 node-3 kernel: [    0.497881] ACPI: \_SB_.PCI1: notify handler is installed
Nov  5 05:56:11 node-3 kernel: [    0.497961] Found 4 acpi root devices
Nov  5 05:56:11 node-3 kernel: [    0.498071] vgaarb: setting as boot device: PCI:0000:0c:00.0
Nov  5 05:56:11 node-3 kernel: [    0.498073] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Nov  5 05:56:11 node-3 kernel: [    0.498075] vgaarb: loaded
Nov  5 05:56:11 node-3 kernel: [    0.498076] vgaarb: bridge control possible 0000:0c:00.0
Nov  5 05:56:11 node-3 kernel: [    0.498197] SCSI subsystem initialized
Nov  5 05:56:11 node-3 kernel: [    0.498261] libata version 3.00 loaded.
Nov  5 05:56:11 node-3 kernel: [    0.498277] ACPI: bus type USB registered
Nov  5 05:56:11 node-3 kernel: [    0.498288] usbcore: registered new interface driver usbfs
Nov  5 05:56:11 node-3 kernel: [    0.498292] usbcore: registered new interface driver hub
Nov  5 05:56:11 node-3 kernel: [    0.498316] usbcore: registered new device driver usb
Nov  5 05:56:11 node-3 kernel: [    0.498483] PCI: Using ACPI for IRQ routing
Nov  5 05:56:11 node-3 kernel: [    0.502072] PCI: pci_cache_line_size set to 64 bytes
Nov  5 05:56:11 node-3 kernel: [    0.502279] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Nov  5 05:56:11 node-3 kernel: [    0.502280] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Nov  5 05:56:11 node-3 kernel: [    0.502281] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Nov  5 05:56:11 node-3 kernel: [    0.502347] NetLabel: Initializing
Nov  5 05:56:11 node-3 kernel: [    0.502348] NetLabel:  domain hash size = 128
Nov  5 05:56:11 node-3 kernel: [    0.502349] NetLabel:  protocols = UNLABELED CIPSOv4
Nov  5 05:56:11 node-3 kernel: [    0.502359] NetLabel:  unlabeled traffic allowed by default
Nov  5 05:56:11 node-3 kernel: [    0.502416] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Nov  5 05:56:11 node-3 kernel: [    0.502420] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Nov  5 05:56:11 node-3 kernel: [    0.504486] Switched to clocksource hpet
Nov  5 05:56:11 node-3 kernel: [    0.508527] AppArmor: AppArmor Filesystem Enabled
Nov  5 05:56:11 node-3 kernel: [    0.508542] pnp: PnP ACPI init
Nov  5 05:56:11 node-3 kernel: [    0.508548] ACPI: bus type PNP registered
Nov  5 05:56:11 node-3 kernel: [    0.508656] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Nov  5 05:56:11 node-3 kernel: [    0.508664] pnp 00:01: [dma 4]
Nov  5 05:56:11 node-3 kernel: [    0.508676] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Nov  5 05:56:11 node-3 kernel: [    0.508703] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Nov  5 05:56:11 node-3 kernel: [    0.508722] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Nov  5 05:56:11 node-3 kernel: [    0.508741] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Nov  5 05:56:11 node-3 kernel: [    0.508774] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Nov  5 05:56:11 node-3 kernel: [    0.508827] system 00:06: [io  0x0500-0x057f] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508829] system 00:06: [io  0x0400-0x047f] could not be reserved
Nov  5 05:56:11 node-3 kernel: [    0.508831] system 00:06: [io  0x0580-0x059f] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508832] system 00:06: [io  0x0600-0x061f] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508833] system 00:06: [io  0x0880-0x0883] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508838] system 00:06: [io  0x0800-0x081f] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508840] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Nov  5 05:56:11 node-3 kernel: [    0.508842] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508843] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508845] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508846] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508848] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508849] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Nov  5 05:56:11 node-3 kernel: [    0.508851] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Nov  5 05:56:11 node-3 kernel: [    0.508935] pnp 00:07: [dma 0 disabled]
Nov  5 05:56:11 node-3 kernel: [    0.508963] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  5 05:56:11 node-3 kernel: [    0.509038] pnp 00:08: [dma 0 disabled]
Nov  5 05:56:11 node-3 kernel: [    0.509070] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Nov  5 05:56:11 node-3 kernel: [    0.509121] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Nov  5 05:56:11 node-3 kernel: [    0.509466] pnp: PnP ACPI: found 10 devices
Nov  5 05:56:11 node-3 kernel: [    0.509468] ACPI: bus type PNP unregistered
Nov  5 05:56:11 node-3 kernel: [    0.515800] pci 0000:00:01.0: PCI bridge to [bus 01]
Nov  5 05:56:11 node-3 kernel: [    0.515803] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Nov  5 05:56:11 node-3 kernel: [    0.515806] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Nov  5 05:56:11 node-3 kernel: [    0.515810] pci 0000:05:00.0: PCI bridge to [bus 06]
Nov  5 05:56:11 node-3 kernel: [    0.515812] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.515827] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Nov  5 05:56:11 node-3 kernel: [    0.515859] pci 0000:05:01.0: PCI bridge to [bus 07]
Nov  5 05:56:11 node-3 kernel: [    0.515874] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Nov  5 05:56:11 node-3 kernel: [    0.515903] pci 0000:05:02.0: PCI bridge to [bus 08]
Nov  5 05:56:11 node-3 kernel: [    0.515917] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Nov  5 05:56:11 node-3 kernel: [    0.515946] pci 0000:05:03.0: PCI bridge to [bus 09]
Nov  5 05:56:11 node-3 kernel: [    0.515960] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Nov  5 05:56:11 node-3 kernel: [    0.515989] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Nov  5 05:56:11 node-3 kernel: [    0.515991] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.516005] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 05:56:11 node-3 kernel: [    0.516034] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Nov  5 05:56:11 node-3 kernel: [    0.516036] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.516050] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Nov  5 05:56:11 node-3 kernel: [    0.516093] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Nov  5 05:56:11 node-3 kernel: [    0.516094] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.516097] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 05:56:11 node-3 kernel: [    0.516101] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Nov  5 05:56:11 node-3 kernel: [    0.516103] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.516105] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Nov  5 05:56:11 node-3 kernel: [    0.516109] pci 0000:00:03.0: PCI bridge to [bus 0a]
Nov  5 05:56:11 node-3 kernel: [    0.516114] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Nov  5 05:56:11 node-3 kernel: [    0.516122] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Nov  5 05:56:11 node-3 kernel: [    0.516125] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Nov  5 05:56:11 node-3 kernel: [    0.516132] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Nov  5 05:56:11 node-3 kernel: [    0.516133] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Nov  5 05:56:11 node-3 kernel: [    0.516133] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Nov  5 05:56:11 node-3 kernel: [    0.516134] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Nov  5 05:56:11 node-3 kernel: [    0.516135] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Nov  5 05:56:11 node-3 kernel: [    0.516136] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Nov  5 05:56:11 node-3 kernel: [    0.516137] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Nov  5 05:56:11 node-3 kernel: [    0.516138] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Nov  5 05:56:11 node-3 kernel: [    0.516139] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.516140] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  5 05:56:11 node-3 kernel: [    0.516140] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.516141] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Nov  5 05:56:11 node-3 kernel: [    0.516142] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.516143] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  5 05:56:11 node-3 kernel: [    0.516144] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.516145] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Nov  5 05:56:11 node-3 kernel: [    0.516146] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Nov  5 05:56:11 node-3 kernel: [    0.516147] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Nov  5 05:56:11 node-3 kernel: [    0.516148] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Nov  5 05:56:11 node-3 kernel: [    0.516149] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Nov  5 05:56:11 node-3 kernel: [    0.516150] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Nov  5 05:56:11 node-3 kernel: [    0.516151] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Nov  5 05:56:11 node-3 kernel: [    0.516153] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Nov  5 05:56:11 node-3 kernel: [    0.516154] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Nov  5 05:56:11 node-3 kernel: [    0.516194] NET: Registered protocol family 2
Nov  5 05:56:11 node-3 kernel: [    0.516458] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.516793] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.516940] TCP: Hash tables configured (established 262144 bind 65536)
Nov  5 05:56:11 node-3 kernel: [    0.516977] TCP: reno registered
Nov  5 05:56:11 node-3 kernel: [    0.517008] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.517103] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.517252] NET: Registered protocol family 1
Nov  5 05:56:11 node-3 kernel: [    0.552586] pci 0000:0c:00.0: Video device with shadowed ROM
Nov  5 05:56:11 node-3 kernel: [    0.552600] PCI: CLS 64 bytes, default 64
Nov  5 05:56:11 node-3 kernel: [    0.552676] Trying to unpack rootfs image as initramfs...
Nov  5 05:56:11 node-3 kernel: [    0.772252] Freeing initrd memory: 20372K (ffff880035826000 - ffff880036c0b000)
Nov  5 05:56:11 node-3 kernel: [    0.772292] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Nov  5 05:56:11 node-3 kernel: [    0.772294] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Nov  5 05:56:11 node-3 kernel: [    0.772687] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772693] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772698] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772703] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772715] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772732] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772748] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772763] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772775] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772784] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772790] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772797] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772806] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772818] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772831] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772844] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Nov  5 05:56:11 node-3 kernel: [    0.772897] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Nov  5 05:56:11 node-3 kernel: [    0.772901] Scanning for low memory corruption every 60 seconds
Nov  5 05:56:11 node-3 kernel: [    0.773194] Initialise system trusted keyring
Nov  5 05:56:11 node-3 kernel: [    0.773239] audit: initializing netlink socket (disabled)
Nov  5 05:56:11 node-3 kernel: [    0.773249] type=2000 audit(1478325335.724:1): initialized
Nov  5 05:56:11 node-3 kernel: [    0.790951] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Nov  5 05:56:11 node-3 kernel: [    0.792427] zbud: loaded
Nov  5 05:56:11 node-3 kernel: [    0.792536] VFS: Disk quotas dquot_6.5.2
Nov  5 05:56:11 node-3 kernel: [    0.792575] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Nov  5 05:56:11 node-3 kernel: [    0.792953] fuse init (API version 7.22)
Nov  5 05:56:11 node-3 kernel: [    0.793011] msgmni has been set to 32768
Nov  5 05:56:11 node-3 kernel: [    0.793055] Key type big_key registered
Nov  5 05:56:11 node-3 kernel: [    0.793530] Key type asymmetric registered
Nov  5 05:56:11 node-3 kernel: [    0.793532] Asymmetric key parser 'x509' registered
Nov  5 05:56:11 node-3 kernel: [    0.793553] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Nov  5 05:56:11 node-3 kernel: [    0.793618] io scheduler noop registered
Nov  5 05:56:11 node-3 kernel: [    0.793619] io scheduler deadline registered (default)
Nov  5 05:56:11 node-3 kernel: [    0.793637] io scheduler cfq registered
Nov  5 05:56:11 node-3 kernel: [    0.793950] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    0.794042] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    0.794134] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    0.794220] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    0.794314] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    0.794380] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    0.794640] aer 0000:00:01.0:pcie02: service driver aer loaded
Nov  5 05:56:11 node-3 kernel: [    0.794658] aer 0000:00:02.0:pcie02: service driver aer loaded
Nov  5 05:56:11 node-3 kernel: [    0.794671] aer 0000:00:03.0:pcie02: service driver aer loaded
Nov  5 05:56:11 node-3 kernel: [    0.794680] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794683] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794685] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Nov  5 05:56:11 node-3 kernel: [    0.794689] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794690] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794691] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794693] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794694] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794695] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794697] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794698] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794700] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794701] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794702] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794704] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794706] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Nov  5 05:56:11 node-3 kernel: [    0.794710] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794712] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Nov  5 05:56:11 node-3 kernel: [    0.794720] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794723] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Nov  5 05:56:11 node-3 kernel: [    0.794733] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794734] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Nov  5 05:56:11 node-3 kernel: [    0.794737] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Nov  5 05:56:11 node-3 kernel: [    0.794750] ioapic: probe of 0000:00:05.4 failed with error -22
Nov  5 05:56:11 node-3 kernel: [    0.794838] ioapic: probe of 0000:80:05.4 failed with error -22
Nov  5 05:56:11 node-3 kernel: [    0.794842] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Nov  5 05:56:11 node-3 kernel: [    0.794851] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Nov  5 05:56:11 node-3 kernel: [    0.794887] vesafb: mode is 640x480x32, linelength=2560, pages=0
Nov  5 05:56:11 node-3 kernel: [    0.794888] vesafb: scrolling: redraw
Nov  5 05:56:11 node-3 kernel: [    0.794890] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Nov  5 05:56:11 node-3 kernel: [    0.815892] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Nov  5 05:56:11 node-3 kernel: [    0.824407] Console: switching to colour frame buffer device 80x30
Nov  5 05:56:11 node-3 kernel: [    0.833091] fb0: VESA VGA frame buffer device
Nov  5 05:56:11 node-3 kernel: [    0.833290] intel_idle: MWAIT substates: 0x2120
Nov  5 05:56:11 node-3 kernel: [    0.833291] intel_idle: v0.4 model 0x3F
Nov  5 05:56:11 node-3 kernel: [    0.833292] intel_idle: lapic_timer_reliable_states 0xffffffff
Nov  5 05:56:11 node-3 kernel: [    0.833516] ipmi message handler version 39.2
Nov  5 05:56:11 node-3 kernel: [    0.833785] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Nov  5 05:56:11 node-3 kernel: [    0.834215] ACPI: AC Adapter [P111] (on-line)
Nov  5 05:56:11 node-3 kernel: [    0.839442] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Nov  5 05:56:11 node-3 kernel: [    0.850447] ACPI: Power Button [PWRB]
Nov  5 05:56:11 node-3 kernel: [    0.856216] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Nov  5 05:56:11 node-3 kernel: [    0.867843] ACPI: Power Button [PWRF]
Nov  5 05:56:11 node-3 kernel: [    0.894132] ERST: Error Record Serialization Table (ERST) support is initialized.
Nov  5 05:56:11 node-3 kernel: [    0.905815] pstore: Registered erst as persistent store backend
Nov  5 05:56:11 node-3 kernel: [    0.912012] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Nov  5 05:56:11 node-3 kernel: [    0.923979] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Nov  5 05:56:11 node-3 kernel: [    0.950729] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Nov  5 05:56:11 node-3 kernel: [    0.984019] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Nov  5 05:56:11 node-3 kernel: [    0.998049] Linux agpgart interface v0.103
Nov  5 05:56:11 node-3 kernel: [    1.005695] brd: module loaded
Nov  5 05:56:11 node-3 kernel: [    1.012726] loop: module loaded
Nov  5 05:56:11 node-3 kernel: [    1.019440] libphy: Fixed MDIO Bus: probed
Nov  5 05:56:11 node-3 kernel: [    1.025901] tun: Universal TUN/TAP device driver, 1.6
Nov  5 05:56:11 node-3 kernel: [    1.032371] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Nov  5 05:56:11 node-3 kernel: [    1.038879] PPP generic driver version 2.4.2
Nov  5 05:56:11 node-3 kernel: [    1.045261] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Nov  5 05:56:11 node-3 kernel: [    1.051697] ehci-pci: EHCI PCI platform driver
Nov  5 05:56:11 node-3 kernel: [    1.058265] ehci-pci 0000:00:1a.0: EHCI Host Controller
Nov  5 05:56:11 node-3 kernel: [    1.064665] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Nov  5 05:56:11 node-3 kernel: [    1.077166] ehci-pci 0000:00:1a.0: debug port 2
Nov  5 05:56:11 node-3 kernel: [    1.087344] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Nov  5 05:56:11 node-3 kernel: [    1.087363] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Nov  5 05:56:11 node-3 kernel: [    1.104004] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Nov  5 05:56:11 node-3 kernel: [    1.110078] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Nov  5 05:56:11 node-3 kernel: [    1.116245] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  5 05:56:11 node-3 kernel: [    1.128117] usb usb1: Product: EHCI Host Controller
Nov  5 05:56:11 node-3 kernel: [    1.134126] usb usb1: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  5 05:56:11 node-3 kernel: [    1.140158] usb usb1: SerialNumber: 0000:00:1a.0
Nov  5 05:56:11 node-3 kernel: [    1.146104] hub 1-0:1.0: USB hub found
Nov  5 05:56:11 node-3 kernel: [    1.151864] hub 1-0:1.0: 2 ports detected
Nov  5 05:56:11 node-3 kernel: [    1.157644] ehci-pci 0000:00:1d.0: EHCI Host Controller
Nov  5 05:56:11 node-3 kernel: [    1.163210] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Nov  5 05:56:11 node-3 kernel: [    1.174081] ehci-pci 0000:00:1d.0: debug port 2
Nov  5 05:56:11 node-3 kernel: [    1.183361] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Nov  5 05:56:11 node-3 kernel: [    1.183364] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Nov  5 05:56:11 node-3 kernel: [    1.199923] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Nov  5 05:56:11 node-3 kernel: [    1.205125] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Nov  5 05:56:11 node-3 kernel: [    1.210417] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Nov  5 05:56:11 node-3 kernel: [    1.220975] usb usb2: Product: EHCI Host Controller
Nov  5 05:56:11 node-3 kernel: [    1.226437] usb usb2: Manufacturer: Linux 3.13.0-100-generic ehci_hcd
Nov  5 05:56:11 node-3 kernel: [    1.231972] usb usb2: SerialNumber: 0000:00:1d.0
Nov  5 05:56:11 node-3 kernel: [    1.237490] hub 2-0:1.0: USB hub found
Nov  5 05:56:11 node-3 kernel: [    1.242843] hub 2-0:1.0: 2 ports detected
Nov  5 05:56:11 node-3 kernel: [    1.248151] ehci-platform: EHCI generic platform driver
Nov  5 05:56:11 node-3 kernel: [    1.253382] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Nov  5 05:56:11 node-3 kernel: [    1.258689] ohci-pci: OHCI PCI platform driver
Nov  5 05:56:11 node-3 kernel: [    1.263994] ohci-platform: OHCI generic platform driver
Nov  5 05:56:11 node-3 kernel: [    1.269190] uhci_hcd: USB Universal Host Controller Interface driver
Nov  5 05:56:11 node-3 kernel: [    1.274531] i8042: PNP: No PS/2 controller found. Probing ports directly.
Nov  5 05:56:11 node-3 kernel: [    1.467679] usb 1-1: new high-speed USB device number 2 using ehci-pci
Nov  5 05:56:11 node-3 kernel: [    1.627874] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Nov  5 05:56:11 node-3 kernel: [    1.633433] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  5 05:56:11 node-3 kernel: [    1.639271] hub 1-1:1.0: USB hub found
Nov  5 05:56:11 node-3 kernel: [    1.644735] hub 1-1:1.0: 6 ports detected
Nov  5 05:56:11 node-3 kernel: [    1.759450] usb 2-1: new high-speed USB device number 2 using ehci-pci
Nov  5 05:56:11 node-3 kernel: [    1.771426] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Nov  5 05:56:11 node-3 kernel: [    2.027535] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Nov  5 05:56:11 node-3 kernel: [    2.033087] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov  5 05:56:11 node-3 kernel: [    2.038933] hub 2-1:1.0: USB hub found
Nov  5 05:56:11 node-3 kernel: [    2.044646] hub 2-1:1.0: 8 ports detected
Nov  5 05:56:11 node-3 kernel: [    2.316047] i8042: No controller found
Nov  5 05:56:11 node-3 kernel: [    2.321490] mousedev: PS/2 mouse device common for all mice
Nov  5 05:56:11 node-3 kernel: [    2.323075] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Nov  5 05:56:11 node-3 kernel: [    2.332655] rtc_cmos 00:02: RTC can wake from S4
Nov  5 05:56:11 node-3 kernel: [    2.338426] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Nov  5 05:56:11 node-3 kernel: [    2.344056] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Nov  5 05:56:11 node-3 kernel: [    2.355151] device-mapper: uevent: version 1.0.3
Nov  5 05:56:11 node-3 kernel: [    2.360804] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Nov  5 05:56:11 node-3 kernel: [    2.372033] ledtrig-cpu: registered to indicate activity on CPUs
Nov  5 05:56:11 node-3 kernel: [    2.377960] TCP: cubic registered
Nov  5 05:56:11 node-3 kernel: [    2.383851] NET: Registered protocol family 10
Nov  5 05:56:11 node-3 kernel: [    2.389830] NET: Registered protocol family 17
Nov  5 05:56:11 node-3 kernel: [    2.395510] Key type dns_resolver registered
Nov  5 05:56:11 node-3 kernel: [    2.401478] Loading compiled-in X.509 certificates
Nov  5 05:56:11 node-3 kernel: [    2.407660] Loaded X.509 cert 'Magrathea: Glacier signing key: db4b16354c147008e161439191dae8c83268d04b'
Nov  5 05:56:11 node-3 kernel: [    2.419043] registered taskstats version 1
Nov  5 05:56:11 node-3 kernel: [    2.426973] Key type trusted registered
Nov  5 05:56:11 node-3 kernel: [    2.434522] Key type encrypted registered
Nov  5 05:56:11 node-3 kernel: [    2.439974] AppArmor: AppArmor sha1 policy hashing enabled
Nov  5 05:56:11 node-3 kernel: [    2.445470] IMA: No TPM chip found, activating TPM-bypass!
Nov  5 05:56:11 node-3 kernel: [    2.451633] regulator-dummy: disabling
Nov  5 05:56:11 node-3 kernel: [    2.455485] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Nov  5 05:56:11 node-3 kernel: [    2.455486] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  5 05:56:11 node-3 kernel: [    2.455487] usb 2-1.4: Product: Cisco USB Composite Device-0
Nov  5 05:56:11 node-3 kernel: [    2.455488] usb 2-1.4: Manufacturer: Avocent
Nov  5 05:56:11 node-3 kernel: [    2.455488] usb 2-1.4: SerialNumber: 20111102-00000001
Nov  5 05:56:11 node-3 kernel: [    2.490673]   Magic number: 8:823:920
Nov  5 05:56:11 node-3 kernel: [    2.496254] clockevents clockevent13: hash matches
Nov  5 05:56:11 node-3 kernel: [    2.501862] acpi device:ee: hash matches
Nov  5 05:56:11 node-3 kernel: [    2.507632] rtc_cmos 00:02: setting system clock to 2016-11-05 05:55:37 UTC (1478325337)
Nov  5 05:56:11 node-3 kernel: [    2.520318] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Nov  5 05:56:11 node-3 kernel: [    2.525957] EDD information not available.
Nov  5 05:56:11 node-3 kernel: [    2.531554] PM: Hibernation image not present or could not be loaded.
Nov  5 05:56:11 node-3 kernel: [    2.532403] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Nov  5 05:56:11 node-3 kernel: [    2.543609] Write protecting the kernel read-only data: 12288k
Nov  5 05:56:11 node-3 kernel: [    2.549719] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Nov  5 05:56:11 node-3 kernel: [    2.562163] Freeing unused kernel memory: 676K (ffff880001b57000 - ffff880001c00000)
Nov  5 05:56:11 node-3 kernel: [    2.594933] device-mapper: multipath: version 1.6.0 loaded
Nov  5 05:56:11 node-3 kernel: [    2.603180] systemd-udevd[217]: starting version 204
Nov  5 05:56:11 node-3 kernel: [    2.627822] md: linear personality registered for level -1
Nov  5 05:56:11 node-3 kernel: [    2.642279] md: multipath personality registered for level -4
Nov  5 05:56:11 node-3 kernel: [    2.650444] md: raid0 personality registered for level 0
Nov  5 05:56:11 node-3 kernel: [    2.658687] md: raid1 personality registered for level 1
Nov  5 05:56:11 node-3 kernel: [    2.669216] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Nov  5 05:56:11 node-3 kernel: [    2.675666] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Nov  5 05:56:11 node-3 kernel: [    2.675820] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Nov  5 05:56:11 node-3 kernel: [    2.677440] megasas: FW now in Ready state
Nov  5 05:56:11 node-3 kernel: [    2.677848] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.677959] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.678086] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.678234] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.678347] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.678419] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.678584] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.678782] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.678886] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.679028] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.679122] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.679251] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.679441] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.679535] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.679673] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.679786] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.680408] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Nov  5 05:56:11 node-3 kernel: [    2.707281] hidraw: raw HID events driver (C) Jiri Kosina
Nov  5 05:56:11 node-3 kernel: [    2.715729] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Nov  5 05:56:11 node-3 kernel: [    2.721869] usbcore: registered new interface driver usbhid
Nov  5 05:56:11 node-3 kernel: [    2.721874] usbhid: USB HID core driver
Nov  5 05:56:11 node-3 kernel: [    2.734902] raid6: sse2x1    4713 MB/s
Nov  5 05:56:11 node-3 kernel: [    2.749138] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Nov  5 05:56:11 node-3 kernel: [    2.762428] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  5 05:56:11 node-3 kernel: [    2.769323] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Nov  5 05:56:11 node-3 kernel: [    2.770475] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.770511] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.770550] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.770779] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.770880] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  5 05:56:11 node-3 kernel: [    2.781048] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Nov  5 05:56:11 node-3 kernel: [    2.781050] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss yes intr mode any type min timer 125 usec loopback tag 0x0000
Nov  5 05:56:11 node-3 kernel: [    2.781051] enic 0000:07:00.0: vNIC resources avail: wq 2 rq 2 cq 4 intr 6
Nov  5 05:56:11 node-3 kernel: [    2.802737] raid6: sse2x2    6131 MB/s
Nov  5 05:56:11 node-3 kernel: [    2.870501] raid6: sse2x4    6104 MB/s
Nov  5 05:56:11 node-3 kernel: [    2.942440] raid6: avx2x1   14933 MB/s
Nov  5 05:56:11 node-3 kernel: [    3.014368] raid6: avx2x2   18922 MB/s
Nov  5 05:56:11 node-3 kernel: [    3.086318] raid6: avx2x4   21338 MB/s
Nov  5 05:56:11 node-3 kernel: [    3.092672] raid6: using algorithm avx2x4 (21338 MB/s)
Nov  5 05:56:11 node-3 kernel: [    3.099019] raid6: using avx2x2 recovery algorithm
Nov  5 05:56:11 node-3 kernel: [    3.105252] megasas:IOC Init cmd success
Nov  5 05:56:11 node-3 kernel: [    3.105255] Switched to clocksource tsc
Nov  5 05:56:11 node-3 kernel: [    3.105338] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Nov  5 05:56:11 node-3 kernel: [    3.105403] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Nov  5 05:56:11 node-3 kernel: [    3.105456] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Nov  5 05:56:11 node-3 kernel: [    3.105508] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Nov  5 05:56:11 node-3 kernel: [    3.105562] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Nov  5 05:56:11 node-3 kernel: [    3.105843] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.105873] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.105913] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.105953] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.105989] enic 0000:07:00.0: irq 120 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.106037] enic 0000:07:00.0: irq 121 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.106150] enic 0000:07:00.0: vNIC resources used:  wq 2 rq 2 cq 4 intr 6 intr mode MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.195572] xor: automatically using best checksumming function:
Nov  5 05:56:11 node-3 kernel: [    3.204115] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Nov  5 05:56:11 node-3 kernel: [    3.217244] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Nov  5 05:56:11 node-3 kernel: [    3.230571] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  5 05:56:11 node-3 kernel: [    3.237303] megasas: INIT adapter done
Nov  5 05:56:11 node-3 kernel: [    3.242158]    avx       : 35719.000 MB/sec
Nov  5 05:56:11 node-3 kernel: [    3.250206] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.250211] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.250215] enic 0000:08:00.0: irq 124 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.250219] enic 0000:08:00.0: irq 125 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.250270] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.263301] async_tx: api initialized (async)
Nov  5 05:56:11 node-3 kernel: [    3.269587] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Nov  5 05:56:11 node-3 kernel: [    3.269589] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Nov  5 05:56:11 node-3 kernel: [    3.269590] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Nov  5 05:56:11 node-3 kernel: [    3.269647] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.269681] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.269718] enic 0000:09:00.0: irq 128 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.269755] enic 0000:09:00.0: irq 129 for MSI/MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.269840] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Nov  5 05:56:11 node-3 kernel: [    3.322096] megaraid_sas 0000:01:00.0: Controller type: iMR
Nov  5 05:56:11 node-3 kernel: [    3.329649] scsi0 : LSI SAS based MegaRAID driver
Nov  5 05:56:11 node-3 kernel: [    3.337706] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  5 05:56:11 node-3 kernel: [    3.352208] md: raid6 personality registered for level 6
Nov  5 05:56:11 node-3 kernel: [    3.359307] md: raid5 personality registered for level 5
Nov  5 05:56:11 node-3 kernel: [    3.363357] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Nov  5 05:56:11 node-3 kernel: [    3.367504] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Nov  5 05:56:11 node-3 kernel: [    3.367606] sd 0:2:0:0: Attached scsi generic sg0 type 0
Nov  5 05:56:11 node-3 kernel: [    3.367842] sd 0:2:0:0: [sda] Write Protect is off
Nov  5 05:56:11 node-3 kernel: [    3.367843] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Nov  5 05:56:11 node-3 kernel: [    3.367916] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Nov  5 05:56:11 node-3 kernel: [    3.408552]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Nov  5 05:56:11 node-3 kernel: [    3.410008] sd 0:2:0:0: [sda] Attached SCSI disk
Nov  5 05:56:11 node-3 kernel: [    3.431827] md: raid4 personality registered for level 4
Nov  5 05:56:11 node-3 kernel: [    3.441316] md: raid10 personality registered for level 10
Nov  5 05:56:11 node-3 kernel: [    3.493116] multipathd (361): /proc/361/oom_adj is deprecated, please use /proc/361/oom_score_adj instead.
Nov  5 05:56:11 node-3 kernel: [    3.542748] random: lvm urandom read with 23 bits of entropy available
Nov  5 05:56:11 node-3 kernel: [    3.670655] bio: create slab <bio-1> at 1
Nov  5 05:56:11 node-3 kernel: [    4.423681] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Nov  5 05:56:11 node-3 kernel: [    5.123374] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Nov  5 05:56:11 node-3 kernel: [    5.151325] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Nov  5 05:56:11 node-3 kernel: [    5.336172] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Nov  5 05:56:11 node-3 kernel: [    5.390058] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Nov  5 05:56:11 node-3 kernel: [    5.477199] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Nov  5 05:56:11 node-3 kernel: [    5.562032] random: nonblocking pool is initialized
Nov  5 05:56:11 node-3 kernel: [    5.649502] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Nov  5 05:56:11 node-3 kernel: [    5.690306] XFS (dm-0): Mounting Filesystem
Nov  5 05:56:11 node-3 kernel: [    6.020410] XFS (dm-0): Ending clean mount
Nov  5 05:56:11 node-3 kernel: [    6.099891] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Nov  5 05:56:11 node-3 kernel: [    6.139064] XFS (dm-1): Mounting Filesystem
Nov  5 05:56:11 node-3 kernel: [    6.207806] XFS (dm-1): Ending clean mount
Nov  5 05:56:11 node-3 kernel: [    8.033443] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  5 05:56:11 node-3 kernel: [    8.047021] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  5 05:56:11 node-3 kernel: [    8.234966] systemd-udevd[778]: starting version 204
Nov  5 05:56:11 node-3 kernel: [    8.424381] wmi: Mapper loaded
Nov  5 05:56:11 node-3 kernel: [    8.428139] power_meter ACPI000D:00: Found ACPI power meter.
Nov  5 05:56:11 node-3 kernel: [    8.428148] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Nov  5 05:56:11 node-3 kernel: [    8.458957] IPMI System Interface driver.
Nov  5 05:56:11 node-3 kernel: [    8.458998] ipmi_si: probing via ACPI
Nov  5 05:56:11 node-3 kernel: [    8.459017] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Nov  5 05:56:11 node-3 kernel: [    8.459018] ipmi_si: Adding ACPI-specified kcs state machine
Nov  5 05:56:11 node-3 kernel: [    8.459025] ipmi_si: probing via SMBIOS
Nov  5 05:56:11 node-3 kernel: [    8.459026] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Nov  5 05:56:11 node-3 kernel: [    8.459026] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Nov  5 05:56:11 node-3 kernel: [    8.459028] ipmi_si: probing via SPMI
Nov  5 05:56:11 node-3 kernel: [    8.459029] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Nov  5 05:56:11 node-3 kernel: [    8.459029] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Nov  5 05:56:11 node-3 kernel: [    8.459030] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Nov  5 05:56:11 node-3 kernel: [    8.468514] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Nov  5 05:56:11 node-3 kernel: [    8.468519] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  5 05:56:11 node-3 kernel: [    8.468521] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Nov  5 05:56:11 node-3 kernel: [    8.468523] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Nov  5 05:56:11 node-3 kernel: [    8.468540] lpc_ich: Resource conflict(s) found affecting gpio_ich
Nov  5 05:56:11 node-3 kernel: [    8.483969] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Nov  5 05:56:11 node-3 kernel: [    8.530154] systemd-udevd[817]: renamed network interface eth0 to enp6s0
Nov  5 05:56:11 node-3 kernel: [    8.550018] systemd-udevd[821]: renamed network interface eth2 to enp8s0
Nov  5 05:56:11 node-3 kernel: [    8.570050] systemd-udevd[799]: renamed network interface eth1 to enp7s0
Nov  5 05:56:11 node-3 kernel: [    8.601152] systemd-udevd[807]: renamed network interface eth3 to enp9s0
Nov  5 05:56:11 node-3 kernel: [    8.602386] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Nov  5 05:56:11 node-3 kernel: [    8.602394] ipmi_si 00:09: IPMI kcs interface initialized
Nov  5 05:56:11 node-3 kernel: [    8.974576] type=1400 audit(1478325343.967:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1021 comm="apparmor_parser"
Nov  5 05:56:11 node-3 kernel: [    8.974724] type=1400 audit(1478325343.967:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1021 comm="apparmor_parser"
Nov  5 05:56:11 node-3 kernel: [    8.974848] type=1400 audit(1478325343.967:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1021 comm="apparmor_parser"
Nov  5 05:56:11 node-3 kernel: [    8.980707] type=1400 audit(1478325343.971:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1022 comm="apparmor_parser"
Nov  5 05:56:11 node-3 kernel: [    8.980864] type=1400 audit(1478325343.971:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1022 comm="apparmor_parser"
Nov  5 05:56:11 node-3 kernel: [    8.980990] type=1400 audit(1478325343.971:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1022 comm="apparmor_parser"
Nov  5 05:56:11 node-3 kernel: [    8.993148] type=1400 audit(1478325343.983:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1025 comm="apparmor_parser"
Nov  5 05:56:11 node-3 kernel: [    8.993306] type=1400 audit(1478325343.987:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1025 comm="apparmor_parser"
Nov  5 05:56:11 node-3 kernel: [    8.993432] type=1400 audit(1478325343.987:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1025 comm="apparmor_parser"
Nov  5 05:56:11 node-3 kernel: [    8.996493] type=1400 audit(1478325343.987:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1023 comm="apparmor_parser"
Nov  5 05:56:11 node-3 kernel: [    9.566167] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Nov  5 05:56:11 node-3 kernel: [    9.570342] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Nov  5 05:56:11 node-3 kernel: [    9.753042] enic 0000:06:00.0 enp6s0: Link UP
Nov  5 05:56:11 node-3 kernel: [    9.753863] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Nov  5 05:56:11 node-3 kernel: [    9.753873] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Nov  5 05:56:11 node-3 kernel: [   19.608275] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Nov  5 05:56:12 node-3 failsafe: Failsafe of 120 seconds reached.
Nov  5 05:56:12 node-3 kernel: [   37.576387] init: failsafe main process (8420) killed by TERM signal
Nov  5 05:56:13 node-3 dbus[8469]: [system] AppArmor D-Bus mediation is enabled
Nov  5 05:56:13 node-3 kernel: [   37.835587] audit_printk_skb: 30 callbacks suppressed
Nov  5 05:56:13 node-3 kernel: [   37.835589] type=1400 audit(1478325373.172:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8546 comm="apparmor_parser"
Nov  5 05:56:13 node-3 kernel: [   37.835930] type=1400 audit(1478325373.172:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8545 comm="apparmor_parser"
Nov  5 05:56:13 node-3 kernel: [   37.835935] type=1400 audit(1478325373.172:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8545 comm="apparmor_parser"
Nov  5 05:56:13 node-3 kernel: [   37.835937] type=1400 audit(1478325373.172:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8545 comm="apparmor_parser"
Nov  5 05:56:13 node-3 kernel: [   37.836155] type=1400 audit(1478325373.172:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8545 comm="apparmor_parser"
Nov  5 05:56:13 node-3 kernel: [   37.836157] type=1400 audit(1478325373.172:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8545 comm="apparmor_parser"
Nov  5 05:56:13 node-3 kernel: [   37.836269] type=1400 audit(1478325373.172:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8545 comm="apparmor_parser"
Nov  5 05:56:13 node-3 kernel: [   37.894426] type=1400 audit(1478325373.232:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8548 comm="apparmor_parser"
Nov  5 05:56:13 node-3 anacron[8615]: Anacron 2.3 started on 2016-11-05
Nov  5 05:56:13 node-3 anacron[8615]: Will run job `cron.daily' in 5 min.
Nov  5 05:56:13 node-3 anacron[8615]: Will run job `cron.weekly' in 10 min.
Nov  5 05:56:13 node-3 anacron[8615]: Will run job `cron.monthly' in 15 min.
Nov  5 05:56:13 node-3 anacron[8615]: Jobs will be executed sequentially
Nov  5 05:56:13 node-3 cron[8578]: (CRON) INFO (pidfile fd = 3)
Nov  5 05:56:13 node-3 cron[8620]: (CRON) STARTUP (fork ok)
Nov  5 05:56:13 node-3 multipathd: path checkers start up
Nov  5 05:56:13 node-3 cron[8620]: (CRON) INFO (Running @reboot jobs)
Nov  5 05:56:13 node-3 postfix/master[8757]: daemon started -- version 2.11.0, configuration /etc/postfix
Nov  5 05:56:17 node-3 puppet-agent[8941]: Reopening log files
Nov  5 05:56:17 node-3 puppet-agent[8941]: Could not request certificate: Connection refused - connect(2)
Nov  5 05:56:32 node-3 puppet-user[9126]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Nov  5 05:56:32 node-3 puppet-user[9126]: Compiled catalog for node-3.domain.tld in environment production in 0.01 seconds
Nov  5 05:56:33 node-3 puppet-user[9126]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Nov  5 05:56:33 node-3 puppet-user[9126]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Nov  5 05:56:34 node-3 puppet-user[9126]: Finished catalog run in 1.83 seconds
Nov  5 05:56:35 node-3 multipathd: uevent trigger error
Nov  5 05:56:35 node-3 puppet-user[9634]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  5 05:56:35 node-3 puppet-user[9634]: Compiled catalog for node-3.domain.tld in environment production in 0.08 seconds
Nov  5 05:56:35 node-3 puppet-user[9634]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Nov  5 05:56:35 node-3 puppet-user[9634]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Nov  5 05:56:35 node-3 puppet-user[9634]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Nov  5 05:56:35 node-3 puppet-user[9634]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Nov  5 05:56:35 node-3 puppet-user[9634]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Nov  5 05:56:35 node-3 puppet-user[9634]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Nov  5 05:56:35 node-3 puppet-user[9634]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Nov  5 05:56:35 node-3 puppet-user[9634]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Nov  5 05:56:35 node-3 puppet-user[9634]: Finished catalog run in 0.05 seconds
Nov  5 05:56:36 node-3 puppet-user[10104]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Nov  5 05:56:36 node-3 puppet-user[10104]: Compiled catalog for node-3.domain.tld in environment production in 0.07 seconds
Nov  5 05:56:36 node-3 puppet-user[10104]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Nov  5 05:56:36 node-3 puppet-user[10104]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Nov  5 05:56:36 node-3 puppet-user[10104]: Finished catalog run in 0.03 seconds
Nov  5 05:56:38 node-3 puppet-user[10571]: (Scope(Class[main])) MODULAR: configuration_symlink
Nov  5 05:56:38 node-3 puppet-user[10571]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Nov  5 05:56:38 node-3 puppet-user[10571]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Nov  5 05:56:38 node-3 puppet-user[10571]: Finished catalog run in 0.03 seconds
Nov  5 05:56:39 node-3 puppet-user[11022]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Nov  5 05:56:39 node-3 puppet-user[11022]: Compiled catalog for node-3.domain.tld in environment production in 0.17 seconds
Nov  5 05:56:39 node-3 puppet-user[11022]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Nov  5 05:56:42 node-3 puppet-user[11022]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Nov  5 05:56:42 node-3 puppet-user[11022]: Finished catalog run in 2.47 seconds
Nov  5 05:56:43 node-3 puppet-user[11599]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Nov  5 05:56:43 node-3 puppet-user[11599]: Compiled catalog for node-3.domain.tld in environment production in 0.22 seconds
Nov  5 05:56:43 node-3 puppet-user[11599]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Nov  5 05:56:43 node-3 puppet-user[11599]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Nov  5 05:56:43 node-3 puppet-user[11599]: (/Stage[main]/Apt/File[preferences]/ensure) created
Nov  5 05:56:44 node-3 puppet-user[11599]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Nov  5 05:56:44 node-3 puppet-user[11599]: Finished catalog run in 0.21 seconds
Nov  5 05:56:45 node-3 puppet-user[12272]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Nov  5 05:56:45 node-3 puppet-user[12272]: Compiled catalog for node-3.domain.tld in environment production in 0.17 seconds
Nov  5 05:56:45 node-3 puppet-user[12272]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Nov  5 05:56:45 node-3 kernel: [   70.560524] nr_pdflush_threads exported in /proc is scheduled for removal
Nov  5 05:56:45 node-3 kernel: [   70.560572] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Nov  5 05:56:45 node-3 puppet-user[12272]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Nov  5 05:56:45 node-3 puppet-user[12272]: Finished catalog run in 0.05 seconds
Nov  5 05:56:47 node-3 puppet-user[12738]: (Scope(Class[main])) MODULAR: sync_time
Nov  5 05:56:47 node-3 puppet-user[12738]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Nov  5 05:56:47 node-3 ntpdate[13160]: ntpdate 4.2.6p5@1.2349-o Wed Oct  5 12:35:26 UTC 2016 (1)
Nov  5 05:56:53 node-3 ntpdate[13160]: adjust time server 10.20.0.2 offset 0.000345 sec
Nov  5 05:56:53 node-3 puppet-user[12738]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Nov  5 05:56:53 node-3 puppet-user[12738]: Finished catalog run in 6.19 seconds
Nov  5 05:56:55 node-3 kernel: [   80.659903] init: plymouth-upstart-bridge main process ended, respawning
Nov  5 05:56:56 node-3 puppet-agent[8941]: Could not run: SIGTERM
Nov  5 05:56:56 node-3 kernel: [   80.942537] ip_tables: (C) 2000-2006 Netfilter Core Team
Nov  5 05:56:56 node-3 ec2: 
Nov  5 05:56:56 node-3 ec2: #############################################################
Nov  5 05:56:56 node-3 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Nov  5 05:56:56 node-3 ec2: 1024 99:ab:60:5d:b2:37:69:7e:c2:7c:81:fe:70:9f:b0:e9  root@node-3.domain.tld (DSA)
Nov  5 05:56:56 node-3 ec2: 256 6c:96:1d:60:57:94:dd:71:0b:52:47:18:c8:6d:af:48  root@node-3.domain.tld (ECDSA)
Nov  5 05:56:56 node-3 ec2: 256 fa:84:d2:99:86:1f:08:fa:c7:76:45:24:04:13:b0:2a  root@node-3.domain.tld (ED25519)
Nov  5 05:56:56 node-3 ec2: 2048 a1:9b:90:82:90:c9:1e:5e:9b:74:f7:ce:b2:22:ac:1d  root@node-3.domain.tld (RSA)
Nov  5 05:56:56 node-3 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Nov  5 05:56:56 node-3 ec2: #############################################################
Nov  5 05:56:59 node-3 puppet-user[13545]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Nov  5 05:56:59 node-3 puppet-user[13545]: Compiled catalog for node-3.domain.tld in environment production in 0.08 seconds
Nov  5 05:56:59 node-3 puppet-user[13545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Nov  5 05:56:59 node-3 puppet-user[13545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Nov  5 05:57:00 node-3 puppet-user[13545]: Finished catalog run in 0.07 seconds
Nov  5 05:57:01 node-3 puppet-user[14016]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Nov  5 05:57:01 node-3 CRON[14437]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Nov  5 05:57:01 node-3 puppet-user[14016]: Compiled catalog for node-3.domain.tld in environment production in 0.47 seconds
Nov  5 05:57:01 node-3 puppet-user[14016]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Nov  5 05:57:01 node-3 puppet-user[14016]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Nov  5 05:57:01 node-3 puppet-user[14016]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Nov  5 05:57:01 node-3 puppet-user[14016]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Nov  5 05:57:01 node-3 puppet-user[14016]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Nov  5 05:57:02 node-3 puppet-user[14016]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Nov  5 05:57:02 node-3 puppet-user[14016]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Nov  5 05:57:02 node-3 puppet-user[14016]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Nov  5 05:57:02 node-3 puppet-user[14016]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Nov  5 05:57:02 node-3 puppet-user[14016]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Nov  5 05:57:02 node-3 puppet-user[14016]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 6 events
Nov  5 05:57:02 node-3 puppet-user[14016]: Finished catalog run in 0.82 seconds
Nov  5 05:57:04 node-3 puppet-user[14546]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Nov  5 05:57:04 node-3 puppet-user[14546]: Compiled catalog for node-3.domain.tld in environment production in 0.12 seconds
Nov  5 05:57:07 node-3 puppet-user[14546]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Nov  5 05:57:21 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  5 05:57:21 node-3 nailgun-agent: I, [2016-11-05T05:57:21.521038 #14440]  INFO -- : API URL is https://10.20.0.2:8443/api
Nov  5 05:57:34 node-3 puppet-user[14546]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Nov  5 05:57:34 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Nov  5 05:57:34 node-3 puppet-user[14546]: Finished catalog run in 30.10 seconds
Nov  5 05:57:34 node-3 nailgun-agent: I, [2016-11-05T05:57:34.620373 #14440]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Nov  5 05:57:36 node-3 puppet-user[17373]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Nov  5 05:57:36 node-3 puppet-user[17373]: Compiled catalog for node-3.domain.tld in environment production in 0.62 seconds
Nov  5 05:57:37 node-3 puppet-user[17373]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Nov  5 05:57:37 node-3 puppet-user[17373]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Nov  5 05:57:37 node-3 puppet-user[17373]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Nov  5 05:57:37 node-3 puppet-user[17373]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Nov  5 05:57:37 node-3 puppet-user[17373]: Finished catalog run in 0.08 seconds
Nov  5 05:57:39 node-3 puppet-user[17849]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Nov  5 05:57:40 node-3 puppet-user[17849]: Compiled catalog for node-3.domain.tld in environment production in 0.81 seconds
Nov  5 05:57:40 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Nov  5 05:57:40 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Nov  5 05:57:40 node-3 crontab[18308]: (root) LIST (root)
Nov  5 05:57:40 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Nov  5 05:57:40 node-3 crontab[18309]: (root) REPLACE (root)
Nov  5 05:57:41 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Nov  5 05:57:42 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Nov  5 05:57:43 node-3 puppet-user[17849]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Nov  5 05:57:43 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8393" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Nov  5 05:57:43 node-3 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Nov  5 05:57:45 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:45 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:45 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:45 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:45 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:45 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:57 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:57 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:57 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:57 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:57 node-3 multipathd: uevent trigger error
<27>Nov  5 05:57:57 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:47 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:47 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:47 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:47 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:47 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:50 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:50 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:50 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:50 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:50 node-3 multipathd: uevent trigger error
<27>Nov  5 05:58:50 node-3 multipathd: uevent trigger error
<27>Nov  5 05:59:30 node-3 ntpdate[1744]: no servers can be used, exiting
<27>Nov  5 05:59:30 node-3 ntpdate[1982]: no servers can be used, exiting
<27>Nov  5 06:00:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:00:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:24 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 06:01:24 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 06:01:30 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 06:01:30 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 06:01:36 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 06:01:42 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 06:01:42 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Nov  5 06:01:48 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:48 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:48 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:48 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:48 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:01:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:11 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:11 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:11 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:11 node-3 multipathd: uevent trigger error
<129>Nov  5 06:02:14 node-3 haproxy[23731]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:14 node-3 haproxy[23731]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:15 node-3 haproxy[23737]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:15 node-3 haproxy[23737]: proxy mysqld has no server available!
<27>Nov  5 06:02:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:20 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:20 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:20 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:20 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:20 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:20 node-3 multipathd: uevent trigger error
<129>Nov  5 06:02:22 node-3 haproxy[26319]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:23 node-3 haproxy[26323]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:23 node-3 haproxy[26323]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:23 node-3 haproxy[26323]: proxy mysqld has no server available!
<129>Nov  5 06:02:23 node-3 haproxy[26323]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:24 node-3 haproxy[26323]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:24 node-3 haproxy[26323]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:24 node-3 haproxy[26323]: proxy object-storage has no server available!
<27>Nov  5 06:02:25 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:25 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:25 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:25 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:25 node-3 multipathd: uevent trigger error
<129>Nov  5 06:02:28 node-3 haproxy[27825]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:28 node-3 haproxy[27825]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:28 node-3 haproxy[27825]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:28 node-3 haproxy[27825]: proxy neutron has no server available!
<129>Nov  5 06:02:28 node-3 haproxy[27825]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:29 node-3 haproxy[27829]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:29 node-3 haproxy[27829]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:29 node-3 haproxy[27829]: proxy mysqld has no server available!
<129>Nov  5 06:02:29 node-3 haproxy[27829]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:29 node-3 haproxy[27829]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:29 node-3 haproxy[27829]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:29 node-3 haproxy[27829]: proxy object-storage has no server available!
<27>Nov  5 06:02:31 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:31 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:31 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:31 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:31 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:31 node-3 multipathd: uevent trigger error
<129>Nov  5 06:02:33 node-3 haproxy[29252]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:33 node-3 haproxy[29252]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:33 node-3 haproxy[29252]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:33 node-3 haproxy[29252]: proxy keystone-1 has no server available!
<129>Nov  5 06:02:34 node-3 haproxy[29260]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:34 node-3 haproxy[29260]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:34 node-3 haproxy[29260]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:34 node-3 haproxy[29260]: proxy keystone-2 has no server available!
<129>Nov  5 06:02:34 node-3 haproxy[29260]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:34 node-3 haproxy[29260]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:34 node-3 haproxy[29260]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:34 node-3 haproxy[29260]: proxy neutron has no server available!
<129>Nov  5 06:02:34 node-3 haproxy[29260]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:34 node-3 haproxy[29260]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:35 node-3 haproxy[29260]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:35 node-3 haproxy[29260]: proxy mysqld has no server available!
<129>Nov  5 06:02:35 node-3 haproxy[29260]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:35 node-3 haproxy[29260]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:35 node-3 haproxy[29260]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:35 node-3 haproxy[29260]: proxy object-storage has no server available!
<27>Nov  5 06:02:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:36 node-3 multipathd: uevent trigger error
<129>Nov  5 06:02:39 node-3 haproxy[30666]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:39 node-3 haproxy[30666]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:39 node-3 haproxy[30666]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:39 node-3 haproxy[30666]: proxy keystone-1 has no server available!
<129>Nov  5 06:02:39 node-3 haproxy[30666]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:39 node-3 haproxy[30666]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:39 node-3 haproxy[30666]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:39 node-3 haproxy[30666]: proxy keystone-2 has no server available!
<129>Nov  5 06:02:39 node-3 haproxy[30666]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:39 node-3 haproxy[30666]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:39 node-3 haproxy[30666]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:39 node-3 haproxy[30666]: proxy neutron has no server available!
<129>Nov  5 06:02:40 node-3 haproxy[30670]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:40 node-3 haproxy[30670]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:40 node-3 haproxy[30670]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:40 node-3 haproxy[30670]: proxy mysqld has no server available!
<129>Nov  5 06:02:40 node-3 haproxy[30670]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:40 node-3 haproxy[30670]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:40 node-3 haproxy[30670]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:40 node-3 haproxy[30670]: proxy object-storage has no server available!
<129>Nov  5 06:02:40 node-3 haproxy[30670]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:40 node-3 haproxy[30670]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:40 node-3 haproxy[30670]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:40 node-3 haproxy[30670]: proxy aodh has no server available!
<27>Nov  5 06:02:42 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:42 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:42 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:42 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:42 node-3 multipathd: uevent trigger error
<129>Nov  5 06:02:44 node-3 haproxy[32010]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:44 node-3 haproxy[32010]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:44 node-3 haproxy[32010]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:44 node-3 haproxy[32010]: proxy keystone-1 has no server available!
<129>Nov  5 06:02:44 node-3 haproxy[32010]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:45 node-3 haproxy[32016]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:45 node-3 haproxy[32016]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:45 node-3 haproxy[32016]: proxy keystone-2 has no server available!
<129>Nov  5 06:02:45 node-3 haproxy[32016]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:45 node-3 haproxy[32016]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:45 node-3 haproxy[32016]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:45 node-3 haproxy[32016]: proxy neutron has no server available!
<129>Nov  5 06:02:45 node-3 haproxy[32016]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:45 node-3 haproxy[32016]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:45 node-3 haproxy[32016]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:45 node-3 haproxy[32016]: proxy mysqld has no server available!
<129>Nov  5 06:02:45 node-3 haproxy[32016]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:45 node-3 haproxy[32016]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:46 node-3 haproxy[32016]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:46 node-3 haproxy[32016]: proxy object-storage has no server available!
<129>Nov  5 06:02:46 node-3 haproxy[32016]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:46 node-3 haproxy[32016]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:46 node-3 haproxy[32016]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:46 node-3 haproxy[32016]: proxy aodh has no server available!
<129>Nov  5 06:02:46 node-3 haproxy[32016]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:46 node-3 haproxy[32016]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:46 node-3 haproxy[32016]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:46 node-3 haproxy[32016]: proxy ceilometer has no server available!
<27>Nov  5 06:02:47 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:47 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:47 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:47 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:47 node-3 multipathd: uevent trigger error
<129>Nov  5 06:02:50 node-3 haproxy[935]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:50 node-3 haproxy[935]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:50 node-3 haproxy[935]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:50 node-3 haproxy[935]: proxy keystone-1 has no server available!
<129>Nov  5 06:02:50 node-3 haproxy[935]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:50 node-3 haproxy[935]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:50 node-3 haproxy[935]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:50 node-3 haproxy[935]: proxy keystone-2 has no server available!
<129>Nov  5 06:02:50 node-3 haproxy[935]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:50 node-3 haproxy[935]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:50 node-3 haproxy[935]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:50 node-3 haproxy[935]: proxy neutron has no server available!
<129>Nov  5 06:02:51 node-3 haproxy[939]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:51 node-3 haproxy[939]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:51 node-3 haproxy[939]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:51 node-3 haproxy[939]: proxy mysqld has no server available!
<129>Nov  5 06:02:51 node-3 haproxy[939]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:51 node-3 haproxy[939]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:51 node-3 haproxy[939]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:51 node-3 haproxy[939]: proxy object-storage has no server available!
<129>Nov  5 06:02:51 node-3 haproxy[939]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:51 node-3 haproxy[939]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:51 node-3 haproxy[939]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:51 node-3 haproxy[939]: proxy aodh has no server available!
<129>Nov  5 06:02:51 node-3 haproxy[939]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:52 node-3 haproxy[939]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:52 node-3 haproxy[939]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:52 node-3 haproxy[939]: proxy ceilometer has no server available!
<27>Nov  5 06:02:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:53 node-3 multipathd: uevent trigger error
<129>Nov  5 06:02:55 node-3 haproxy[2277]: Server horizon/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:55 node-3 haproxy[2277]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:55 node-3 haproxy[2277]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:55 node-3 haproxy[2277]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:55 node-3 haproxy[2277]: proxy keystone-1 has no server available!
<129>Nov  5 06:02:55 node-3 haproxy[2277]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:56 node-3 haproxy[2281]: proxy keystone-2 has no server available!
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:56 node-3 haproxy[2281]: proxy neutron has no server available!
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:56 node-3 haproxy[2281]: proxy mysqld has no server available!
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:56 node-3 haproxy[2281]: proxy object-storage has no server available!
<129>Nov  5 06:02:56 node-3 haproxy[2281]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:57 node-3 haproxy[2281]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:57 node-3 haproxy[2281]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:57 node-3 haproxy[2281]: proxy aodh has no server available!
<129>Nov  5 06:02:57 node-3 haproxy[2281]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:57 node-3 haproxy[2281]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:02:57 node-3 haproxy[2281]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:02:57 node-3 haproxy[2281]: proxy ceilometer has no server available!
<27>Nov  5 06:02:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:02:58 node-3 multipathd: uevent trigger error
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server horizon/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:01 node-3 haproxy[3670]: proxy keystone-1 has no server available!
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:01 node-3 haproxy[3670]: proxy keystone-2 has no server available!
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:01 node-3 haproxy[3670]: proxy glance-api has no server available!
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:01 node-3 haproxy[3670]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:02 node-3 haproxy[3674]: proxy glance-glare has no server available!
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:02 node-3 haproxy[3674]: proxy neutron has no server available!
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:02 node-3 haproxy[3674]: proxy glance-registry has no server available!
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:02 node-3 haproxy[3674]: proxy mysqld has no server available!
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:02 node-3 haproxy[3674]: proxy object-storage has no server available!
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:02 node-3 haproxy[3674]: proxy aodh has no server available!
<129>Nov  5 06:03:02 node-3 haproxy[3674]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:03 node-3 haproxy[3674]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:03 node-3 haproxy[3674]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:03 node-3 haproxy[3674]: proxy ceilometer has no server available!
<27>Nov  5 06:03:04 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:04 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:04 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:04 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:04 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:04 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:04 node-3 multipathd: uevent trigger error
<129>Nov  5 06:03:06 node-3 haproxy[5229]: Server horizon/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:07 node-3 haproxy[5233]: proxy keystone-1 has no server available!
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:07 node-3 haproxy[5233]: proxy keystone-2 has no server available!
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:07 node-3 haproxy[5233]: proxy nova-api has no server available!
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:07 node-3 haproxy[5233]: proxy nova-metadata-api has no server available!
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:07 node-3 haproxy[5233]: proxy glance-api has no server available!
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:07 node-3 haproxy[5233]: proxy glance-glare has no server available!
<129>Nov  5 06:03:07 node-3 haproxy[5233]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:08 node-3 haproxy[5233]: proxy neutron has no server available!
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:08 node-3 haproxy[5233]: proxy glance-registry has no server available!
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:08 node-3 haproxy[5233]: proxy mysqld has no server available!
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:08 node-3 haproxy[5233]: proxy object-storage has no server available!
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:08 node-3 haproxy[5233]: proxy aodh has no server available!
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:08 node-3 haproxy[5233]: proxy ceilometer has no server available!
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:08 node-3 haproxy[5233]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:08 node-3 haproxy[5233]: proxy nova-novncproxy has no server available!
<27>Nov  5 06:03:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:10 node-3 multipathd: uevent trigger error
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server horizon/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:12 node-3 haproxy[6568]: proxy keystone-1 has no server available!
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:12 node-3 haproxy[6568]: proxy keystone-2 has no server available!
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:12 node-3 haproxy[6568]: proxy nova-api has no server available!
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:12 node-3 haproxy[6568]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:12 node-3 haproxy[6568]: proxy nova-metadata-api has no server available!
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 1ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:13 node-3 haproxy[6572]: proxy cinder-api has no server available!
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:13 node-3 haproxy[6572]: proxy glance-api has no server available!
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:13 node-3 haproxy[6572]: proxy glance-glare has no server available!
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:13 node-3 haproxy[6572]: proxy neutron has no server available!
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:13 node-3 haproxy[6572]: proxy glance-registry has no server available!
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:13 node-3 haproxy[6572]: proxy mysqld has no server available!
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:13 node-3 haproxy[6572]: proxy object-storage has no server available!
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:13 node-3 haproxy[6572]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:14 node-3 haproxy[6572]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:14 node-3 haproxy[6572]: proxy aodh has no server available!
<129>Nov  5 06:03:14 node-3 haproxy[6572]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:14 node-3 haproxy[6572]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:14 node-3 haproxy[6572]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:14 node-3 haproxy[6572]: proxy ceilometer has no server available!
<129>Nov  5 06:03:14 node-3 haproxy[6572]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:14 node-3 haproxy[6572]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:14 node-3 haproxy[6572]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:14 node-3 haproxy[6572]: proxy nova-novncproxy has no server available!
<27>Nov  5 06:03:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:15 node-3 multipathd: uevent trigger error
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server horizon/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server keystone-1/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:18 node-3 haproxy[8148]: proxy keystone-1 has no server available!
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server keystone-2/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:18 node-3 haproxy[8148]: proxy keystone-2 has no server available!
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:18 node-3 haproxy[8148]: proxy nova-api has no server available!
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:18 node-3 haproxy[8148]: proxy nova-metadata-api has no server available!
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:18 node-3 haproxy[8148]: proxy cinder-api has no server available!
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:18 node-3 haproxy[8148]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:19 node-3 haproxy[8152]: proxy glance-api has no server available!
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:19 node-3 haproxy[8152]: proxy glance-glare has no server available!
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:19 node-3 haproxy[8152]: proxy neutron has no server available!
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:19 node-3 haproxy[8152]: proxy glance-registry has no server available!
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:19 node-3 haproxy[8152]: proxy mysqld has no server available!
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:19 node-3 haproxy[8152]: proxy object-storage has no server available!
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:19 node-3 haproxy[8152]: proxy aodh has no server available!
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:19 node-3 haproxy[8152]: proxy ceilometer has no server available!
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:19 node-3 haproxy[8152]: proxy heat-api has no server available!
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:19 node-3 haproxy[8152]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:20 node-3 haproxy[8152]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:20 node-3 haproxy[8152]: proxy heat-api-cfn has no server available!
<129>Nov  5 06:03:20 node-3 haproxy[8152]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:20 node-3 haproxy[8152]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:20 node-3 haproxy[8152]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:20 node-3 haproxy[8152]: proxy heat-api-cloudwatch has no server available!
<129>Nov  5 06:03:20 node-3 haproxy[8152]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:20 node-3 haproxy[8152]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:03:20 node-3 haproxy[8152]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:03:20 node-3 haproxy[8152]: proxy nova-novncproxy has no server available!
<27>Nov  5 06:03:21 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:21 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:21 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:21 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:21 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:03:32 node-3 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Nov  5 06:03:56 node-3 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Nov  5 06:03:58 node-3 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Nov  5 06:04:20 node-3 ocf-mysql-wss: ERROR: p_mysqld: validate_gtid(): GTID have wrong format: wsrep_local_state_uuid:0
<27>Nov  5 06:04:20 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 06:04:24 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Nov  5 06:04:49 node-3 multipathd: uevent trigger error
<27>Nov  5 06:04:49 node-3 multipathd: uevent trigger error
<27>Nov  5 06:04:49 node-3 multipathd: uevent trigger error
<27>Nov  5 06:04:49 node-3 multipathd: uevent trigger error
<27>Nov  5 06:04:49 node-3 multipathd: uevent trigger error
<27>Nov  5 06:04:49 node-3 multipathd: uevent trigger error
<27>Nov  5 06:04:49 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:09 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:09 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:09 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:09 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:09 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:22 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  5 06:07:24 node-3 apache2_error [Sat Nov 05 06:07:20.341181 2016] [mpm_event:notice] [pid 16353:tid 140086741321600] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  5 06:07:24 node-3 apache2_error [Sat Nov 05 06:07:20.341313 2016] [core:notice] [pid 16353:tid 140086741321600] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  5 06:07:24 node-3 apache2_error [Sat Nov 05 06:07:23.316158 2016] [mpm_event:notice] [pid 16353:tid 140086741321600] AH00491: caught SIGTERM, shutting down
<27>Nov  5 06:07:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:33 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:33 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:33 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:33 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:33 node-3 multipathd: uevent trigger error
<43>Nov  5 06:07:34 node-3 apache2_error [Sat Nov 05 06:07:24.407824 2016] [mpm_worker:notice] [pid 18070:tid 139808297215872] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Nov  5 06:07:34 node-3 apache2_error [Sat Nov 05 06:07:24.407853 2016] [core:notice] [pid 18070:tid 139808297215872] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 06:07:37 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:37 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:37 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:37 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:37 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:37 node-3 multipathd: uevent trigger error
<27>Nov  5 06:07:37 node-3 multipathd: uevent trigger error
<43>Nov  5 06:08:44 node-3 apache2_error [Sat Nov 05 06:08:39.345706 2016] [mpm_worker:notice] [pid 18070:tid 139808297215872] AH00295: caught SIGTERM, shutting down
<43>Nov  5 06:08:44 node-3 apache2_error [Sat Nov 05 06:08:40.101076 2016] [mpm_worker:notice] [pid 31795:tid 140249997219712] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 06:08:44 node-3 apache2_error [Sat Nov 05 06:08:40.101102 2016] [core:notice] [pid 31795:tid 140249997219712] AH00094: Command line: '/usr/sbin/apache2'
<43>Nov  5 06:09:24 node-3 apache2_error [Sat Nov 05 06:09:23.650114 2016] [mpm_worker:notice] [pid 31795:tid 140249997219712] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 06:09:24 node-3 apache2_error [Sat Nov 05 06:09:23.845756 2016] [mpm_worker:warn] [pid 31795:tid 140249997219712] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 06:09:24 node-3 apache2_error [Sat Nov 05 06:09:23.850587 2016] [mpm_worker:notice] [pid 31795:tid 140249997219712] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 06:09:24 node-3 apache2_error [Sat Nov 05 06:09:23.850609 2016] [core:notice] [pid 31795:tid 140249997219712] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 06:10:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:24 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 06:10:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:10:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:11:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:11:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:11:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:11:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:11:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:11:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:12:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:12:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:12:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:12:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:12:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:13:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:13:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:13:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:13:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:13:08 node-3 multipathd: uevent trigger error
<27>Nov  5 06:13:26 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 06:14:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:30 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:30 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:30 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:30 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:14:36 node-3 multipathd: uevent trigger error
<27>Nov  5 06:16:27 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 06:16:56 node-3 multipathd: uevent trigger error
<27>Nov  5 06:16:56 node-3 multipathd: uevent trigger error
<27>Nov  5 06:16:56 node-3 multipathd: uevent trigger error
<27>Nov  5 06:16:56 node-3 multipathd: uevent trigger error
<27>Nov  5 06:16:56 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:13 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:17:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:00 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:00 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:00 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:00 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:00 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:00 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:26 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:26 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:26 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:26 node-3 multipathd: uevent trigger error
<27>Nov  5 06:18:26 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:16 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Nov  5 06:19:16 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Nov  5 06:19:17 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Nov  5 06:19:18 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Nov  5 06:19:18 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Nov  5 06:19:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:18 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:29 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 06:19:31 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:31 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:31 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:31 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:32 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:32 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:19:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:20:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:20:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:20:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:20:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:20:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:20:03 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:22 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:31 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 06:22:34 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:35 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:35 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:22:46 node-3 multipathd: sda: spurious uevent, path already in pathvec
<27>Nov  5 06:23:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:23:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:23:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:23:53 node-3 multipathd: uevent trigger error
<27>Nov  5 06:23:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:23:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:23:58 node-3 multipathd: uevent trigger error
<27>Nov  5 06:23:59 node-3 multipathd: uevent trigger error
<27>Nov  5 06:23:59 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:44 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:44 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:44 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:44 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:44 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:44 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:48 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:48 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:48 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:48 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:48 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:52 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:52 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:52 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:52 node-3 multipathd: uevent trigger error
<27>Nov  5 06:24:52 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:04 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:04 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:04 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:04 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:11 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:11 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:11 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:32 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Nov  5 06:25:40 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:40 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:40 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:40 node-3 multipathd: uevent trigger error
<27>Nov  5 06:25:40 node-3 multipathd: uevent trigger error
<27>Nov  5 06:26:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:26:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:26:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:26:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:26:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:27:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:27:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:27:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:27:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:27:02 node-3 multipathd: uevent trigger error
<27>Nov  5 06:27:02 node-3 multipathd: uevent trigger error
<11>Nov  5 06:27:14 node-3 liberasurecode[84654]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:14 node-3 liberasurecode[84654]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:14 node-3 liberasurecode[84654]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:14 node-3 liberasurecode[84654]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:15 node-3 liberasurecode[84680]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:15 node-3 liberasurecode[84680]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:15 node-3 liberasurecode[84680]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:15 node-3 liberasurecode[84680]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:16 node-3 liberasurecode[85126]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:16 node-3 liberasurecode[85126]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:16 node-3 liberasurecode[85126]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:16 node-3 liberasurecode[85126]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:20 node-3 liberasurecode[86990]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:20 node-3 liberasurecode[86990]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:20 node-3 liberasurecode[86990]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:20 node-3 liberasurecode[86990]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87041]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87041]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87041]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87041]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87235]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87235]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87235]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87235]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87347]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87347]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87347]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87347]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87332]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87332]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87332]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87332]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87361]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87361]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87361]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87361]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87375]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87375]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87375]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:21 node-3 liberasurecode[87375]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:38 node-3 liberasurecode[88499]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:38 node-3 liberasurecode[88499]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:38 node-3 liberasurecode[88499]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:27:38 node-3 liberasurecode[88499]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Nov  5 06:27:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:27:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:27:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:27:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:27:46 node-3 multipathd: uevent trigger error
<27>Nov  5 06:28:34 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Nov  5 06:28:36 node-3 apache2_error [Sat Nov 05 06:28:33.053326 2016] [mpm_worker:notice] [pid 31795:tid 140249997219712] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 06:28:36 node-3 apache2_error [Sat Nov 05 06:28:33.439770 2016] [mpm_worker:warn] [pid 31795:tid 140249997219712] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 06:28:36 node-3 apache2_error [Sat Nov 05 06:28:33.444810 2016] [mpm_worker:notice] [pid 31795:tid 140249997219712] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 06:28:36 node-3 apache2_error [Sat Nov 05 06:28:33.444850 2016] [core:notice] [pid 31795:tid 140249997219712] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 06:29:14 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:14 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:14 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:14 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:14 node-3 multipathd: uevent trigger error
<43>Nov  5 06:29:16 node-3 apache2_error [Sat Nov 05 06:29:10.305604 2016] [mpm_worker:notice] [pid 31795:tid 140249997219712] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Nov  5 06:29:16 node-3 apache2_error [Sat Nov 05 06:29:10.498076 2016] [mpm_worker:warn] [pid 31795:tid 140249997219712] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 06:29:16 node-3 apache2_error [Sat Nov 05 06:29:10.504193 2016] [mpm_worker:notice] [pid 31795:tid 140249997219712] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 06:29:16 node-3 apache2_error [Sat Nov 05 06:29:10.504231 2016] [core:notice] [pid 31795:tid 140249997219712] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 06:29:21 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:21 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:21 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:21 node-3 multipathd: uevent trigger error
<43>Nov  5 06:29:56 node-3 apache2_error [Sat Nov 05 06:29:55.948762 2016] [mpm_worker:notice] [pid 31795:tid 140249997219712] AH00297: SIGUSR1 received.  Doing graceful restart
<27>Nov  5 06:29:59 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:59 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:59 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:59 node-3 multipathd: uevent trigger error
<27>Nov  5 06:29:59 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:00 node-3 multipathd: uevent trigger error
<11>Nov  5 06:30:01 node-3 liberasurecode[112508]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:30:01 node-3 liberasurecode[112508]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:30:01 node-3 liberasurecode[112508]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:30:01 node-3 liberasurecode[112508]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Nov  5 06:30:06 node-3 apache2_error [Sat Nov 05 06:29:56.143588 2016] [mpm_worker:warn] [pid 31795:tid 140249997219712] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Nov  5 06:30:06 node-3 apache2_error [Sat Nov 05 06:29:56.148792 2016] [mpm_worker:notice] [pid 31795:tid 140249997219712] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Nov  5 06:30:06 node-3 apache2_error [Sat Nov 05 06:29:56.148812 2016] [core:notice] [pid 31795:tid 140249997219712] AH00094: Command line: '/usr/sbin/apache2'
<27>Nov  5 06:30:06 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:06 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:06 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:06 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:06 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:50 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:57 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:57 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:57 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:57 node-3 multipathd: uevent trigger error
<27>Nov  5 06:30:57 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:03 node-3 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Nov  5 06:31:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:12 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:17 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:26 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:26 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:26 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:26 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:26 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:32 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:32 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:32 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:32 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:32 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:32 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:45 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:50 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:50 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:50 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:50 node-3 multipathd: uevent trigger error
<27>Nov  5 06:31:50 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:05 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:10 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:19 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:24 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:32:29 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:15 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:23 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:23 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:23 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:23 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:23 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:34 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:34 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:34 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:34 node-3 multipathd: uevent trigger error
<27>Nov  5 06:34:34 node-3 multipathd: uevent trigger error
<129>Nov  5 06:34:44 node-3 haproxy[168468]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Nov  5 06:34:45 node-3 haproxy[168468]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<11>Nov  5 06:35:01 node-3 liberasurecode[175573]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:35:01 node-3 liberasurecode[175573]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:35:01 node-3 liberasurecode[175573]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Nov  5 06:35:01 node-3 liberasurecode[175573]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<129>Nov  5 06:35:14 node-3 haproxy[168468]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Nov  5 06:35:14 node-3 haproxy[168468]: proxy neutron has no server available!
<27>Nov  5 06:35:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:28 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:34 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:34 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:34 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:34 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:34 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:39 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:39 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:39 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:39 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:39 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:39 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:50 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:50 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:50 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:50 node-3 multipathd: uevent trigger error
<27>Nov  5 06:35:50 node-3 multipathd: uevent trigger error
