Aug 20 18:23:18 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8384" x-info="http://www.rsyslog.com"] start
Aug 20 18:23:18 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Aug 20 18:23:18 node-3 rsyslogd: rsyslogd's groupid changed to 104
Aug 20 18:23:18 node-3 rsyslogd: rsyslogd's userid changed to 101
Aug 20 18:23:18 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuset
Aug 20 18:23:18 node-3 kernel: [    0.000000] Initializing cgroup subsys cpu
Aug 20 18:23:18 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Aug 20 18:23:18 node-3 kernel: [    0.000000] Linux version 3.13.0-93-generic (buildd@lgw01-13) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #140-Ubuntu SMP Mon Jul 18 21:21:05 UTC 2016 (Ubuntu 3.13.0-93.140-generic 3.13.11-ckt39)
Aug 20 18:23:18 node-3 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-93-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=91e59ea6-f880-4552-95fa-e549fd4702da nomdmonddf nomdmonisw
Aug 20 18:23:18 node-3 kernel: [    0.000000] KERNEL supported cpus:
Aug 20 18:23:18 node-3 kernel: [    0.000000]   Intel GenuineIntel
Aug 20 18:23:18 node-3 kernel: [    0.000000]   AMD AuthenticAMD
Aug 20 18:23:18 node-3 kernel: [    0.000000]   Centaur CentaurHauls
Aug 20 18:23:18 node-3 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Aug 20 18:23:18 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Aug 20 18:23:18 node-3 kernel: [    0.000000] NX (Execute Disable) protection: active
Aug 20 18:23:18 node-3 kernel: [    0.000000] SMBIOS 2.8 present.
Aug 20 18:23:18 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
Aug 20 18:23:18 node-3 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Aug 20 18:23:18 node-3 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Aug 20 18:23:18 node-3 kernel: [    0.000000] No AGP bridge found
Aug 20 18:23:18 node-3 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Aug 20 18:23:18 node-3 kernel: [    0.000000] MTRR default type: write-back
Aug 20 18:23:18 node-3 kernel: [    0.000000] MTRR fixed ranges enabled:
Aug 20 18:23:18 node-3 kernel: [    0.000000]   00000-9FFFF write-back
Aug 20 18:23:18 node-3 kernel: [    0.000000]   A0000-BFFFF uncachable
Aug 20 18:23:18 node-3 kernel: [    0.000000]   C0000-FFFFF write-protect
Aug 20 18:23:18 node-3 kernel: [    0.000000] MTRR variable ranges enabled:
Aug 20 18:23:18 node-3 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Aug 20 18:23:18 node-3 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Aug 20 18:23:18 node-3 kernel: [    0.000000]   2 disabled
Aug 20 18:23:18 node-3 kernel: [    0.000000]   3 disabled
Aug 20 18:23:18 node-3 kernel: [    0.000000]   4 disabled
Aug 20 18:23:18 node-3 kernel: [    0.000000]   5 disabled
Aug 20 18:23:18 node-3 kernel: [    0.000000]   6 disabled
Aug 20 18:23:18 node-3 kernel: [    0.000000]   7 disabled
Aug 20 18:23:18 node-3 kernel: [    0.000000]   8 disabled
Aug 20 18:23:18 node-3 kernel: [    0.000000]   9 disabled
Aug 20 18:23:18 node-3 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Aug 20 18:23:18 node-3 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Aug 20 18:23:18 node-3 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Aug 20 18:23:18 node-3 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Aug 20 18:23:18 node-3 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Aug 20 18:23:18 node-3 kernel: [    0.000000] Using GB pages for direct mapping
Aug 20 18:23:18 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Aug 20 18:23:18 node-3 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Aug 20 18:23:18 node-3 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Aug 20 18:23:18 node-3 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Aug 20 18:23:18 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Aug 20 18:23:18 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Aug 20 18:23:18 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Aug 20 18:23:18 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Aug 20 18:23:18 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Aug 20 18:23:18 node-3 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Aug 20 18:23:18 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Aug 20 18:23:18 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Aug 20 18:23:18 node-3 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Aug 20 18:23:18 node-3 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Aug 20 18:23:18 node-3 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Aug 20 18:23:18 node-3 kernel: [    0.000000] Zone ranges:
Aug 20 18:23:18 node-3 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] Movable zone start for each node
Aug 20 18:23:18 node-3 kernel: [    0.000000] Early memory node ranges
Aug 20 18:23:18 node-3 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] On node 0 totalpages: 4125855
Aug 20 18:23:18 node-3 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Aug 20 18:23:18 node-3 kernel: [    0.000000]   DMA zone: 21 pages reserved
Aug 20 18:23:18 node-3 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Aug 20 18:23:18 node-3 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Aug 20 18:23:18 node-3 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Aug 20 18:23:18 node-3 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Aug 20 18:23:18 node-3 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Aug 20 18:23:18 node-3 kernel: [    0.000000] On node 1 totalpages: 4194304
Aug 20 18:23:18 node-3 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Aug 20 18:23:18 node-3 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Aug 20 18:23:18 node-3 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Aug 20 18:23:18 node-3 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Aug 20 18:23:18 node-3 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: IRQ0 used by override.
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: IRQ2 used by override.
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: IRQ9 used by override.
Aug 20 18:23:18 node-3 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Aug 20 18:23:18 node-3 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Aug 20 18:23:18 node-3 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Aug 20 18:23:18 node-3 kernel: [    0.000000] nr_irqs_gsi: 88
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Aug 20 18:23:18 node-3 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Aug 20 18:23:18 node-3 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Aug 20 18:23:18 node-3 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Aug 20 18:23:18 node-3 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Aug 20 18:23:18 node-3 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Aug 20 18:23:18 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 
Aug 20 18:23:18 node-3 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Aug 20 18:23:18 node-3 kernel: [    0.000000] Policy zone: Normal
Aug 20 18:23:18 node-3 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-93-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=91e59ea6-f880-4552-95fa-e549fd4702da nomdmonddf nomdmonisw
Aug 20 18:23:18 node-3 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Aug 20 18:23:18 node-3 kernel: [    0.000000] Checking aperture...
Aug 20 18:23:18 node-3 kernel: [    0.000000] No AGP bridge found
Aug 20 18:23:18 node-3 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Aug 20 18:23:18 node-3 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Aug 20 18:23:18 node-3 kernel: [    0.000000] Memory: 32653452K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Aug 20 18:23:18 node-3 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Aug 20 18:23:18 node-3 kernel: [    0.000000] Hierarchical RCU implementation.
Aug 20 18:23:18 node-3 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Aug 20 18:23:18 node-3 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Aug 20 18:23:18 node-3 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Aug 20 18:23:18 node-3 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Aug 20 18:23:18 node-3 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Aug 20 18:23:18 node-3 kernel: [    0.000000] Console: colour dummy device 80x25
Aug 20 18:23:18 node-3 kernel: [    0.000000] console [tty0] enabled
Aug 20 18:23:18 node-3 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Aug 20 18:23:18 node-3 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Aug 20 18:23:18 node-3 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Aug 20 18:23:18 node-3 kernel: [    0.000000] hpet clockevent registered
Aug 20 18:23:18 node-3 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Aug 20 18:23:18 node-3 kernel: [    0.004000] tsc: Detected 3491.919 MHz processor
Aug 20 18:23:18 node-3 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.83 BogoMIPS (lpj=13967676)
Aug 20 18:23:18 node-3 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Aug 20 18:23:18 node-3 kernel: [    0.000046] Security Framework initialized
Aug 20 18:23:18 node-3 kernel: [    0.000064] AppArmor: AppArmor initialized
Aug 20 18:23:18 node-3 kernel: [    0.000065] Yama: becoming mindful.
Aug 20 18:23:18 node-3 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Aug 20 18:23:18 node-3 kernel: [    0.001457] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.006347] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.008281] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.008310] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.008604] Initializing cgroup subsys memory
Aug 20 18:23:18 node-3 kernel: [    0.008613] Initializing cgroup subsys devices
Aug 20 18:23:18 node-3 kernel: [    0.008614] Initializing cgroup subsys freezer
Aug 20 18:23:18 node-3 kernel: [    0.008616] Initializing cgroup subsys blkio
Aug 20 18:23:18 node-3 kernel: [    0.008618] Initializing cgroup subsys perf_event
Aug 20 18:23:18 node-3 kernel: [    0.008620] Initializing cgroup subsys hugetlb
Aug 20 18:23:18 node-3 kernel: [    0.008639] CPU: Physical Processor ID: 0
Aug 20 18:23:18 node-3 kernel: [    0.008641] CPU: Processor Core ID: 0
Aug 20 18:23:18 node-3 kernel: [    0.008644] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Aug 20 18:23:18 node-3 kernel: [    0.008644] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Aug 20 18:23:18 node-3 kernel: [    0.009338] mce: CPU supports 22 MCE banks
Aug 20 18:23:18 node-3 kernel: [    0.009365] CPU0: Thermal monitoring enabled (TM1)
Aug 20 18:23:18 node-3 kernel: [    0.009386] process: using mwait in idle threads
Aug 20 18:23:18 node-3 kernel: [    0.009389] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Aug 20 18:23:18 node-3 kernel: [    0.009389] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Aug 20 18:23:18 node-3 kernel: [    0.009389] tlb_flushall_shift: 6
Aug 20 18:23:18 node-3 kernel: [    0.009477] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Aug 20 18:23:18 node-3 kernel: [    0.010203] ACPI: Core revision 20131115
Aug 20 18:23:18 node-3 kernel: [    0.022894] ACPI: All ACPI Tables successfully acquired
Aug 20 18:23:18 node-3 kernel: [    0.023057] ftrace: allocating 28617 entries in 112 pages
Aug 20 18:23:18 node-3 kernel: [    0.032033] dmar: Host address width 46
Aug 20 18:23:18 node-3 kernel: [    0.032035] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Aug 20 18:23:18 node-3 kernel: [    0.032041] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Aug 20 18:23:18 node-3 kernel: [    0.032042] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Aug 20 18:23:18 node-3 kernel: [    0.032046] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Aug 20 18:23:18 node-3 kernel: [    0.032048] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Aug 20 18:23:18 node-3 kernel: [    0.032049] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Aug 20 18:23:18 node-3 kernel: [    0.032050] dmar: ATSR flags: 0x0
Aug 20 18:23:18 node-3 kernel: [    0.032051] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Aug 20 18:23:18 node-3 kernel: [    0.032052] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Aug 20 18:23:18 node-3 kernel: [    0.032167] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Aug 20 18:23:18 node-3 kernel: [    0.032169] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Aug 20 18:23:18 node-3 kernel: [    0.032170] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Aug 20 18:23:18 node-3 kernel: [    0.032171] HPET id 0 under DRHD base 0xc7ffc000
Aug 20 18:23:18 node-3 kernel: [    0.032172] Your BIOS is broken and requested that x2apic be disabled.
Aug 20 18:23:18 node-3 kernel: [    0.032172] This will slightly decrease performance.
Aug 20 18:23:18 node-3 kernel: [    0.032172] Use 'intremap=no_x2apic_optout' to override BIOS request.
Aug 20 18:23:18 node-3 kernel: [    0.032604] Enabled IRQ remapping in xapic mode
Aug 20 18:23:18 node-3 kernel: [    0.032605] x2apic not enabled, IRQ remapping is in xapic mode
Aug 20 18:23:18 node-3 kernel: [    0.032609] Switched APIC routing to physical flat.
Aug 20 18:23:18 node-3 kernel: [    0.033183] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Aug 20 18:23:18 node-3 kernel: [    0.072832] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Aug 20 18:23:18 node-3 kernel: [    0.072838] TSC deadline timer enabled
Aug 20 18:23:18 node-3 kernel: [    0.072846] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Aug 20 18:23:18 node-3 kernel: [    0.072852] ... version:                3
Aug 20 18:23:18 node-3 kernel: [    0.072853] ... bit width:              48
Aug 20 18:23:18 node-3 kernel: [    0.072854] ... generic registers:      4
Aug 20 18:23:18 node-3 kernel: [    0.072855] ... value mask:             0000ffffffffffff
Aug 20 18:23:18 node-3 kernel: [    0.072856] ... max period:             0000ffffffffffff
Aug 20 18:23:18 node-3 kernel: [    0.072857] ... fixed-purpose events:   3
Aug 20 18:23:18 node-3 kernel: [    0.072858] ... event mask:             000000070000000f
Aug 20 18:23:18 node-3 kernel: [    0.074253] x86: Booting SMP configuration:
Aug 20 18:23:18 node-3 kernel: [    0.088361] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Aug 20 18:23:18 node-3 kernel: [    0.074255] .... node  #0, CPUs:        #1  #2  #3
Aug 20 18:23:18 node-3 kernel: [    0.116275] .... node  #1, CPUs:    #4  #5  #6  #7
Aug 20 18:23:18 node-3 kernel: [    0.270240] .... node  #0, CPUs:    #8  #9 #10 #11
Aug 20 18:23:18 node-3 kernel: [    0.325854] .... node  #1, CPUs:   #12 #13 #14 #15
Aug 20 18:23:18 node-3 kernel: [    0.382721] x86: Booted up 2 nodes, 16 CPUs
Aug 20 18:23:18 node-3 kernel: [    0.382725] smpboot: Total of 16 processors activated (111753.96 BogoMIPS)
Aug 20 18:23:18 node-3 kernel: [    0.406717] devtmpfs: initialized
Aug 20 18:23:18 node-3 kernel: [    0.409822] EVM: security.selinux
Aug 20 18:23:18 node-3 kernel: [    0.409823] EVM: security.SMACK64
Aug 20 18:23:18 node-3 kernel: [    0.409824] EVM: security.ima
Aug 20 18:23:18 node-3 kernel: [    0.409825] EVM: security.capability
Aug 20 18:23:18 node-3 kernel: [    0.409875] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.410573] pinctrl core: initialized pinctrl subsystem
Aug 20 18:23:18 node-3 kernel: [    0.410635] regulator-dummy: no parameters
Aug 20 18:23:18 node-3 kernel: [    0.410667] RTC time: 18:22:42, date: 08/20/16
Aug 20 18:23:18 node-3 kernel: [    0.410702] NET: Registered protocol family 16
Aug 20 18:23:18 node-3 kernel: [    0.410788] cpuidle: using governor ladder
Aug 20 18:23:18 node-3 kernel: [    0.410790] cpuidle: using governor menu
Aug 20 18:23:18 node-3 kernel: [    0.410826] ACPI: bus type PCI registered
Aug 20 18:23:18 node-3 kernel: [    0.410828] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Aug 20 18:23:18 node-3 kernel: [    0.410873] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Aug 20 18:23:18 node-3 kernel: [    0.410876] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Aug 20 18:23:18 node-3 kernel: [    0.424607] PCI: Using configuration type 1 for base access
Aug 20 18:23:18 node-3 kernel: [    0.425621] bio: create slab <bio-0> at 0
Aug 20 18:23:18 node-3 kernel: [    0.425896] ACPI: Added _OSI(Module Device)
Aug 20 18:23:18 node-3 kernel: [    0.425898] ACPI: Added _OSI(Processor Device)
Aug 20 18:23:18 node-3 kernel: [    0.425899] ACPI: Added _OSI(3.0 _SCP Extensions)
Aug 20 18:23:18 node-3 kernel: [    0.425900] ACPI: Added _OSI(Processor Aggregator Device)
Aug 20 18:23:18 node-3 kernel: [    0.438616] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Aug 20 18:23:18 node-3 kernel: [    0.449226] ACPI: Interpreter enabled
Aug 20 18:23:18 node-3 kernel: [    0.449232] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Aug 20 18:23:18 node-3 kernel: [    0.449236] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Aug 20 18:23:18 node-3 kernel: [    0.449239] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Aug 20 18:23:18 node-3 kernel: [    0.449246] ACPI: (supports S0 S4 S5)
Aug 20 18:23:18 node-3 kernel: [    0.449247] ACPI: Using IOAPIC for interrupt routing
Aug 20 18:23:18 node-3 kernel: [    0.449288] HEST: Table parsing has been initialized.
Aug 20 18:23:18 node-3 kernel: [    0.449291] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Aug 20 18:23:18 node-3 kernel: [    0.449846] ACPI: No dock devices found.
Aug 20 18:23:18 node-3 kernel: [    0.461524] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Aug 20 18:23:18 node-3 kernel: [    0.461529] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 20 18:23:18 node-3 kernel: [    0.461532] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Aug 20 18:23:18 node-3 kernel: [    0.461561] PCI host bridge to bus 0000:ff
Aug 20 18:23:18 node-3 kernel: [    0.461563] pci_bus 0000:ff: root bus resource [bus ff]
Aug 20 18:23:18 node-3 kernel: [    0.461571] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461609] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.461640] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461675] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461705] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.461735] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.461766] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461795] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461830] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461858] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461884] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461911] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461939] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461967] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.461994] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462023] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462054] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462082] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462109] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.462137] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462163] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.462189] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462215] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462245] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.462279] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462310] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462339] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462370] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462401] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462432] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462462] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462495] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462526] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462558] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462590] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462622] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462656] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462686] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462714] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462746] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462780] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462819] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462854] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462886] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462915] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462946] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.462978] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463009] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463041] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463072] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463104] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463134] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463163] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463192] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463221] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463253] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463284] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463341] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Aug 20 18:23:18 node-3 kernel: [    0.463344] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 20 18:23:18 node-3 kernel: [    0.463347] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Aug 20 18:23:18 node-3 kernel: [    0.463365] PCI host bridge to bus 0000:7f
Aug 20 18:23:18 node-3 kernel: [    0.463366] pci_bus 0000:7f: root bus resource [bus 7f]
Aug 20 18:23:18 node-3 kernel: [    0.463371] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463402] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.463431] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463461] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463483] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.463507] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.463534] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463561] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463583] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463606] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463629] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463651] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463675] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463698] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463721] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463747] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463769] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463792] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463815] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.463840] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463863] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.463885] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463907] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463933] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Aug 20 18:23:18 node-3 kernel: [    0.463966] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.463992] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464018] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464044] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464069] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464098] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464125] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464152] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464177] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464205] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464232] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464260] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464289] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464313] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464337] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464365] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464391] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464417] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464447] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464475] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464500] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464525] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464552] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464578] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464605] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464632] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464661] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464687] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464709] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464735] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464760] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464789] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.464816] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.466056] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Aug 20 18:23:18 node-3 kernel: [    0.466060] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 20 18:23:18 node-3 kernel: [    0.467192] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Aug 20 18:23:18 node-3 kernel: [    0.467703] PCI host bridge to bus 0000:00
Aug 20 18:23:18 node-3 kernel: [    0.467706] pci_bus 0000:00: root bus resource [bus 00-7e]
Aug 20 18:23:18 node-3 kernel: [    0.467707] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Aug 20 18:23:18 node-3 kernel: [    0.467709] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Aug 20 18:23:18 node-3 kernel: [    0.467710] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Aug 20 18:23:18 node-3 kernel: [    0.467711] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Aug 20 18:23:18 node-3 kernel: [    0.467713] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Aug 20 18:23:18 node-3 kernel: [    0.467714] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Aug 20 18:23:18 node-3 kernel: [    0.467720] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Aug 20 18:23:18 node-3 kernel: [    0.467802] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.467833] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.467875] pci 0000:00:01.0: System wakeup disabled by ACPI
Aug 20 18:23:18 node-3 kernel: [    0.467894] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.467923] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.467964] pci 0000:00:02.0: System wakeup disabled by ACPI
Aug 20 18:23:18 node-3 kernel: [    0.467983] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.468013] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.468056] pci 0000:00:03.0: System wakeup disabled by ACPI
Aug 20 18:23:18 node-3 kernel: [    0.468074] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.468145] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.468223] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.468300] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Aug 20 18:23:18 node-3 kernel: [    0.468305] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Aug 20 18:23:18 node-3 kernel: [    0.468391] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Aug 20 18:23:18 node-3 kernel: [    0.468540] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Aug 20 18:23:18 node-3 kernel: [    0.468557] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Aug 20 18:23:18 node-3 kernel: [    0.468635] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.468690] pci 0000:00:1a.0: System wakeup disabled by ACPI
Aug 20 18:23:18 node-3 kernel: [    0.468713] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.468768] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.468812] pci 0000:00:1c.0: System wakeup disabled by ACPI
Aug 20 18:23:18 node-3 kernel: [    0.468841] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.468897] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.468940] pci 0000:00:1c.7: System wakeup disabled by ACPI
Aug 20 18:23:18 node-3 kernel: [    0.468965] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Aug 20 18:23:18 node-3 kernel: [    0.468983] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Aug 20 18:23:18 node-3 kernel: [    0.469060] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.469110] pci 0000:00:1d.0: System wakeup disabled by ACPI
Aug 20 18:23:18 node-3 kernel: [    0.469137] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Aug 20 18:23:18 node-3 kernel: [    0.469387] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Aug 20 18:23:18 node-3 kernel: [    0.469393] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Aug 20 18:23:18 node-3 kernel: [    0.469399] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.469404] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.469412] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Aug 20 18:23:18 node-3 kernel: [    0.469442] pci 0000:01:00.0: supports D1 D2
Aug 20 18:23:18 node-3 kernel: [    0.475412] pci 0000:00:01.0: PCI bridge to [bus 01]
Aug 20 18:23:18 node-3 kernel: [    0.475415] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Aug 20 18:23:18 node-3 kernel: [    0.475417] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Aug 20 18:23:18 node-3 kernel: [    0.475525] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.475558] pci 0000:02:00.0: PME# supported from D0 D3hot
Aug 20 18:23:18 node-3 kernel: [    0.483410] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Aug 20 18:23:18 node-3 kernel: [    0.483413] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.483415] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 20 18:23:18 node-3 kernel: [    0.483470] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.483538] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.483614] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.483659] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Aug 20 18:23:18 node-3 kernel: [    0.483663] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.483664] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 20 18:23:18 node-3 kernel: [    0.483718] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.483840] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.483894] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Aug 20 18:23:18 node-3 kernel: [    0.483897] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.483899] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 20 18:23:18 node-3 kernel: [    0.483948] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.484088] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.484131] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.484251] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.484287] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.484409] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.484445] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Aug 20 18:23:18 node-3 kernel: [    0.484564] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Aug 20 18:23:18 node-3 kernel: [    0.484605] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Aug 20 18:23:18 node-3 kernel: [    0.484608] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.484610] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 20 18:23:18 node-3 kernel: [    0.484670] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Aug 20 18:23:18 node-3 kernel: [    0.484733] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.484785] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.484826] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Aug 20 18:23:18 node-3 kernel: [    0.484908] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Aug 20 18:23:18 node-3 kernel: [    0.485017] pci 0000:05:00.0: PCI bridge to [bus 06]
Aug 20 18:23:18 node-3 kernel: [    0.485019] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.485021] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Aug 20 18:23:18 node-3 kernel: [    0.485092] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Aug 20 18:23:18 node-3 kernel: [    0.485150] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.485199] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.485412] pci 0000:05:01.0: PCI bridge to [bus 07]
Aug 20 18:23:18 node-3 kernel: [    0.485416] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Aug 20 18:23:18 node-3 kernel: [    0.485479] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Aug 20 18:23:18 node-3 kernel: [    0.485532] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.485580] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.485789] pci 0000:05:02.0: PCI bridge to [bus 08]
Aug 20 18:23:18 node-3 kernel: [    0.485793] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Aug 20 18:23:18 node-3 kernel: [    0.485851] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Aug 20 18:23:18 node-3 kernel: [    0.485911] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.485963] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Aug 20 18:23:18 node-3 kernel: [    0.486234] pci 0000:05:03.0: PCI bridge to [bus 09]
Aug 20 18:23:18 node-3 kernel: [    0.486238] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Aug 20 18:23:18 node-3 kernel: [    0.486413] pci 0000:00:03.0: PCI bridge to [bus 0a]
Aug 20 18:23:18 node-3 kernel: [    0.486452] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Aug 20 18:23:18 node-3 kernel: [    0.486527] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Aug 20 18:23:18 node-3 kernel: [    0.486546] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Aug 20 18:23:18 node-3 kernel: [    0.486559] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Aug 20 18:23:18 node-3 kernel: [    0.486572] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Aug 20 18:23:18 node-3 kernel: [    0.486622] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Aug 20 18:23:18 node-3 kernel: [    0.491424] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Aug 20 18:23:18 node-3 kernel: [    0.491433] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Aug 20 18:23:18 node-3 kernel: [    0.491485] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Aug 20 18:23:18 node-3 kernel: [    0.492178] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Aug 20 18:23:18 node-3 kernel: [    0.492181] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 20 18:23:18 node-3 kernel: [    0.492305] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Aug 20 18:23:18 node-3 kernel: [    0.492413] PCI host bridge to bus 0000:80
Aug 20 18:23:18 node-3 kernel: [    0.492415] pci_bus 0000:80: root bus resource [bus 80-fe]
Aug 20 18:23:18 node-3 kernel: [    0.492417] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Aug 20 18:23:18 node-3 kernel: [    0.492418] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Aug 20 18:23:18 node-3 kernel: [    0.492426] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.492490] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.492559] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Aug 20 18:23:18 node-3 kernel: [    0.492621] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Aug 20 18:23:18 node-3 kernel: [    0.492627] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Aug 20 18:23:18 node-3 kernel: [    0.492700] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Aug 20 18:23:18 node-3 kernel: [    0.493000] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Aug 20 18:23:18 node-3 kernel: [    0.493031] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Aug 20 18:23:18 node-3 kernel: [    0.493061] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Aug 20 18:23:18 node-3 kernel: [    0.493090] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Aug 20 18:23:18 node-3 kernel: [    0.493120] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 20 18:23:18 node-3 kernel: [    0.493150] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 20 18:23:18 node-3 kernel: [    0.493179] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 20 18:23:18 node-3 kernel: [    0.493209] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 20 18:23:18 node-3 kernel: [    0.493295] ACPI: Enabled 3 GPEs in block 00 to 3F
Aug 20 18:23:18 node-3 kernel: [    0.493299] ACPI: \_SB_.UNC1: notify handler is installed
Aug 20 18:23:18 node-3 kernel: [    0.493300] ACPI: \_SB_.UNC0: notify handler is installed
Aug 20 18:23:18 node-3 kernel: [    0.493315] ACPI: \_SB_.PCI0: notify handler is installed
Aug 20 18:23:18 node-3 kernel: [    0.493368] ACPI: \_SB_.PCI1: notify handler is installed
Aug 20 18:23:18 node-3 kernel: [    0.493448] Found 4 acpi root devices
Aug 20 18:23:18 node-3 kernel: [    0.493555] vgaarb: setting as boot device: PCI:0000:0c:00.0
Aug 20 18:23:18 node-3 kernel: [    0.493557] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Aug 20 18:23:18 node-3 kernel: [    0.493559] vgaarb: loaded
Aug 20 18:23:18 node-3 kernel: [    0.493560] vgaarb: bridge control possible 0000:0c:00.0
Aug 20 18:23:18 node-3 kernel: [    0.493674] SCSI subsystem initialized
Aug 20 18:23:18 node-3 kernel: [    0.493739] libata version 3.00 loaded.
Aug 20 18:23:18 node-3 kernel: [    0.493754] ACPI: bus type USB registered
Aug 20 18:23:18 node-3 kernel: [    0.493764] usbcore: registered new interface driver usbfs
Aug 20 18:23:18 node-3 kernel: [    0.493769] usbcore: registered new interface driver hub
Aug 20 18:23:18 node-3 kernel: [    0.493793] usbcore: registered new device driver usb
Aug 20 18:23:18 node-3 kernel: [    0.493958] PCI: Using ACPI for IRQ routing
Aug 20 18:23:18 node-3 kernel: [    0.497552] PCI: pci_cache_line_size set to 64 bytes
Aug 20 18:23:18 node-3 kernel: [    0.497762] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Aug 20 18:23:18 node-3 kernel: [    0.497764] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Aug 20 18:23:18 node-3 kernel: [    0.497764] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Aug 20 18:23:18 node-3 kernel: [    0.497828] NetLabel: Initializing
Aug 20 18:23:18 node-3 kernel: [    0.497830] NetLabel:  domain hash size = 128
Aug 20 18:23:18 node-3 kernel: [    0.497831] NetLabel:  protocols = UNLABELED CIPSOv4
Aug 20 18:23:18 node-3 kernel: [    0.497841] NetLabel:  unlabeled traffic allowed by default
Aug 20 18:23:18 node-3 kernel: [    0.497897] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Aug 20 18:23:18 node-3 kernel: [    0.497901] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Aug 20 18:23:18 node-3 kernel: [    0.499959] Switched to clocksource hpet
Aug 20 18:23:18 node-3 kernel: [    0.503867] AppArmor: AppArmor Filesystem Enabled
Aug 20 18:23:18 node-3 kernel: [    0.503882] pnp: PnP ACPI init
Aug 20 18:23:18 node-3 kernel: [    0.503889] ACPI: bus type PNP registered
Aug 20 18:23:18 node-3 kernel: [    0.504012] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Aug 20 18:23:18 node-3 kernel: [    0.504020] pnp 00:01: [dma 4]
Aug 20 18:23:18 node-3 kernel: [    0.504031] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Aug 20 18:23:18 node-3 kernel: [    0.504057] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Aug 20 18:23:18 node-3 kernel: [    0.504077] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Aug 20 18:23:18 node-3 kernel: [    0.504094] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Aug 20 18:23:18 node-3 kernel: [    0.504127] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Aug 20 18:23:18 node-3 kernel: [    0.504179] system 00:06: [io  0x0500-0x057f] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504181] system 00:06: [io  0x0400-0x047f] could not be reserved
Aug 20 18:23:18 node-3 kernel: [    0.504183] system 00:06: [io  0x0580-0x059f] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504185] system 00:06: [io  0x0600-0x061f] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504186] system 00:06: [io  0x0880-0x0883] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504190] system 00:06: [io  0x0800-0x081f] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504192] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Aug 20 18:23:18 node-3 kernel: [    0.504194] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504195] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504197] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504198] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504200] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504201] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Aug 20 18:23:18 node-3 kernel: [    0.504203] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Aug 20 18:23:18 node-3 kernel: [    0.504287] pnp 00:07: [dma 0 disabled]
Aug 20 18:23:18 node-3 kernel: [    0.504315] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Aug 20 18:23:18 node-3 kernel: [    0.504390] pnp 00:08: [dma 0 disabled]
Aug 20 18:23:18 node-3 kernel: [    0.504421] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Aug 20 18:23:18 node-3 kernel: [    0.504471] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Aug 20 18:23:18 node-3 kernel: [    0.504820] pnp: PnP ACPI: found 10 devices
Aug 20 18:23:18 node-3 kernel: [    0.504822] ACPI: bus type PNP unregistered
Aug 20 18:23:18 node-3 kernel: [    0.511052] pci 0000:00:01.0: PCI bridge to [bus 01]
Aug 20 18:23:18 node-3 kernel: [    0.511055] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Aug 20 18:23:18 node-3 kernel: [    0.511058] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Aug 20 18:23:18 node-3 kernel: [    0.511062] pci 0000:05:00.0: PCI bridge to [bus 06]
Aug 20 18:23:18 node-3 kernel: [    0.511064] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.511082] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511111] pci 0000:05:01.0: PCI bridge to [bus 07]
Aug 20 18:23:18 node-3 kernel: [    0.511126] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511154] pci 0000:05:02.0: PCI bridge to [bus 08]
Aug 20 18:23:18 node-3 kernel: [    0.511169] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Aug 20 18:23:18 node-3 kernel: [    0.511198] pci 0000:05:03.0: PCI bridge to [bus 09]
Aug 20 18:23:18 node-3 kernel: [    0.511212] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Aug 20 18:23:18 node-3 kernel: [    0.511244] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Aug 20 18:23:18 node-3 kernel: [    0.511246] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.511260] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511289] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Aug 20 18:23:18 node-3 kernel: [    0.511291] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.511306] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511334] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Aug 20 18:23:18 node-3 kernel: [    0.511336] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.511338] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511343] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Aug 20 18:23:18 node-3 kernel: [    0.511344] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.511347] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511350] pci 0000:00:03.0: PCI bridge to [bus 0a]
Aug 20 18:23:18 node-3 kernel: [    0.511355] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Aug 20 18:23:18 node-3 kernel: [    0.511363] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Aug 20 18:23:18 node-3 kernel: [    0.511367] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Aug 20 18:23:18 node-3 kernel: [    0.511373] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Aug 20 18:23:18 node-3 kernel: [    0.511374] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Aug 20 18:23:18 node-3 kernel: [    0.511375] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Aug 20 18:23:18 node-3 kernel: [    0.511376] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Aug 20 18:23:18 node-3 kernel: [    0.511377] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Aug 20 18:23:18 node-3 kernel: [    0.511377] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Aug 20 18:23:18 node-3 kernel: [    0.511378] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Aug 20 18:23:18 node-3 kernel: [    0.511379] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Aug 20 18:23:18 node-3 kernel: [    0.511380] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.511381] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511382] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.511383] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511384] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.511385] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511386] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.511386] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511387] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Aug 20 18:23:18 node-3 kernel: [    0.511388] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511389] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Aug 20 18:23:18 node-3 kernel: [    0.511390] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Aug 20 18:23:18 node-3 kernel: [    0.511391] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Aug 20 18:23:18 node-3 kernel: [    0.511392] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Aug 20 18:23:18 node-3 kernel: [    0.511394] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Aug 20 18:23:18 node-3 kernel: [    0.511395] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Aug 20 18:23:18 node-3 kernel: [    0.511431] NET: Registered protocol family 2
Aug 20 18:23:18 node-3 kernel: [    0.511688] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.512029] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.512175] TCP: Hash tables configured (established 262144 bind 65536)
Aug 20 18:23:18 node-3 kernel: [    0.512210] TCP: reno registered
Aug 20 18:23:18 node-3 kernel: [    0.512241] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.512336] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.512480] NET: Registered protocol family 1
Aug 20 18:23:18 node-3 kernel: [    0.552063] pci 0000:0c:00.0: Video device with shadowed ROM
Aug 20 18:23:18 node-3 kernel: [    0.552079] PCI: CLS 64 bytes, default 64
Aug 20 18:23:18 node-3 kernel: [    0.552157] Trying to unpack rootfs image as initramfs...
Aug 20 18:23:18 node-3 kernel: [    0.772463] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Aug 20 18:23:18 node-3 kernel: [    0.772501] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Aug 20 18:23:18 node-3 kernel: [    0.772503] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Aug 20 18:23:18 node-3 kernel: [    0.772904] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.772910] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.772915] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.772920] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.772932] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.772949] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.772975] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.772984] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.772992] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.773000] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.773006] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.773012] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.773019] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.773027] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.773035] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.773042] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Aug 20 18:23:18 node-3 kernel: [    0.773083] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Aug 20 18:23:18 node-3 kernel: [    0.773086] Scanning for low memory corruption every 60 seconds
Aug 20 18:23:18 node-3 kernel: [    0.773378] Initialise system trusted keyring
Aug 20 18:23:18 node-3 kernel: [    0.773423] audit: initializing netlink socket (disabled)
Aug 20 18:23:18 node-3 kernel: [    0.773432] type=2000 audit(1471717361.728:1): initialized
Aug 20 18:23:18 node-3 kernel: [    0.791244] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Aug 20 18:23:18 node-3 kernel: [    0.792742] zbud: loaded
Aug 20 18:23:18 node-3 kernel: [    0.792853] VFS: Disk quotas dquot_6.5.2
Aug 20 18:23:18 node-3 kernel: [    0.792889] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Aug 20 18:23:18 node-3 kernel: [    0.793256] fuse init (API version 7.22)
Aug 20 18:23:18 node-3 kernel: [    0.793314] msgmni has been set to 32768
Aug 20 18:23:18 node-3 kernel: [    0.793359] Key type big_key registered
Aug 20 18:23:18 node-3 kernel: [    0.793924] Key type asymmetric registered
Aug 20 18:23:18 node-3 kernel: [    0.793926] Asymmetric key parser 'x509' registered
Aug 20 18:23:18 node-3 kernel: [    0.793949] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Aug 20 18:23:18 node-3 kernel: [    0.794004] io scheduler noop registered
Aug 20 18:23:18 node-3 kernel: [    0.794005] io scheduler deadline registered (default)
Aug 20 18:23:18 node-3 kernel: [    0.794023] io scheduler cfq registered
Aug 20 18:23:18 node-3 kernel: [    0.794342] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    0.794434] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    0.794522] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    0.794610] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    0.794707] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    0.794774] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    0.795060] aer 0000:00:01.0:pcie02: service driver aer loaded
Aug 20 18:23:18 node-3 kernel: [    0.795079] aer 0000:00:02.0:pcie02: service driver aer loaded
Aug 20 18:23:18 node-3 kernel: [    0.795092] aer 0000:00:03.0:pcie02: service driver aer loaded
Aug 20 18:23:18 node-3 kernel: [    0.795102] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795104] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795106] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Aug 20 18:23:18 node-3 kernel: [    0.795110] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795111] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795112] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795114] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795115] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795117] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795118] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795120] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795121] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795122] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795124] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795125] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795128] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Aug 20 18:23:18 node-3 kernel: [    0.795131] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795133] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Aug 20 18:23:18 node-3 kernel: [    0.795142] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795145] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Aug 20 18:23:18 node-3 kernel: [    0.795153] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795155] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Aug 20 18:23:18 node-3 kernel: [    0.795158] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Aug 20 18:23:18 node-3 kernel: [    0.795171] ioapic: probe of 0000:00:05.4 failed with error -22
Aug 20 18:23:18 node-3 kernel: [    0.795261] ioapic: probe of 0000:80:05.4 failed with error -22
Aug 20 18:23:18 node-3 kernel: [    0.795265] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Aug 20 18:23:18 node-3 kernel: [    0.795273] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Aug 20 18:23:18 node-3 kernel: [    0.795309] vesafb: mode is 640x480x32, linelength=2560, pages=0
Aug 20 18:23:18 node-3 kernel: [    0.795310] vesafb: scrolling: redraw
Aug 20 18:23:18 node-3 kernel: [    0.795312] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Aug 20 18:23:18 node-3 kernel: [    0.816215] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Aug 20 18:23:18 node-3 kernel: [    0.824755] Console: switching to colour frame buffer device 80x30
Aug 20 18:23:18 node-3 kernel: [    0.833426] fb0: VESA VGA frame buffer device
Aug 20 18:23:18 node-3 kernel: [    0.833627] intel_idle: MWAIT substates: 0x2120
Aug 20 18:23:18 node-3 kernel: [    0.833628] intel_idle: v0.4 model 0x3F
Aug 20 18:23:18 node-3 kernel: [    0.833628] intel_idle: lapic_timer_reliable_states 0xffffffff
Aug 20 18:23:18 node-3 kernel: [    0.833869] ipmi message handler version 39.2
Aug 20 18:23:18 node-3 kernel: [    0.834152] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Aug 20 18:23:18 node-3 kernel: [    0.834592] ACPI: AC Adapter [P111] (on-line)
Aug 20 18:23:18 node-3 kernel: [    0.839823] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Aug 20 18:23:18 node-3 kernel: [    0.850820] ACPI: Power Button [PWRB]
Aug 20 18:23:18 node-3 kernel: [    0.856575] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Aug 20 18:23:18 node-3 kernel: [    0.868213] ACPI: Power Button [PWRF]
Aug 20 18:23:18 node-3 kernel: [    0.885481] ERST: Error Record Serialization Table (ERST) support is initialized.
Aug 20 18:23:18 node-3 kernel: [    0.897122] pstore: Registered erst as persistent store backend
Aug 20 18:23:18 node-3 kernel: [    0.903310] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Aug 20 18:23:18 node-3 kernel: [    0.915252] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Aug 20 18:23:18 node-3 kernel: [    0.942020] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Aug 20 18:23:18 node-3 kernel: [    0.975382] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Aug 20 18:23:18 node-3 kernel: [    0.989701] Linux agpgart interface v0.103
Aug 20 18:23:18 node-3 kernel: [    0.997394] brd: module loaded
Aug 20 18:23:18 node-3 kernel: [    1.004512] loop: module loaded
Aug 20 18:23:18 node-3 kernel: [    1.011283] libphy: Fixed MDIO Bus: probed
Aug 20 18:23:18 node-3 kernel: [    1.017854] tun: Universal TUN/TAP device driver, 1.6
Aug 20 18:23:18 node-3 kernel: [    1.024433] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Aug 20 18:23:18 node-3 kernel: [    1.031056] PPP generic driver version 2.4.2
Aug 20 18:23:18 node-3 kernel: [    1.037516] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Aug 20 18:23:18 node-3 kernel: [    1.043999] ehci-pci: EHCI PCI platform driver
Aug 20 18:23:18 node-3 kernel: [    1.050604] ehci-pci 0000:00:1a.0: EHCI Host Controller
Aug 20 18:23:18 node-3 kernel: [    1.057027] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Aug 20 18:23:18 node-3 kernel: [    1.069574] ehci-pci 0000:00:1a.0: debug port 2
Aug 20 18:23:18 node-3 kernel: [    1.079782] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Aug 20 18:23:18 node-3 kernel: [    1.079801] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Aug 20 18:23:18 node-3 kernel: [    1.095459] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Aug 20 18:23:18 node-3 kernel: [    1.101548] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Aug 20 18:23:18 node-3 kernel: [    1.107727] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 20 18:23:18 node-3 kernel: [    1.119653] usb usb1: Product: EHCI Host Controller
Aug 20 18:23:18 node-3 kernel: [    1.125692] usb usb1: Manufacturer: Linux 3.13.0-93-generic ehci_hcd
Aug 20 18:23:18 node-3 kernel: [    1.131752] usb usb1: SerialNumber: 0000:00:1a.0
Aug 20 18:23:18 node-3 kernel: [    1.137708] hub 1-0:1.0: USB hub found
Aug 20 18:23:18 node-3 kernel: [    1.143482] hub 1-0:1.0: 2 ports detected
Aug 20 18:23:18 node-3 kernel: [    1.149275] ehci-pci 0000:00:1d.0: EHCI Host Controller
Aug 20 18:23:18 node-3 kernel: [    1.154858] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Aug 20 18:23:18 node-3 kernel: [    1.165766] ehci-pci 0000:00:1d.0: debug port 2
Aug 20 18:23:18 node-3 kernel: [    1.175068] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Aug 20 18:23:18 node-3 kernel: [    1.175071] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Aug 20 18:23:18 node-3 kernel: [    1.191378] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Aug 20 18:23:18 node-3 kernel: [    1.196585] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Aug 20 18:23:18 node-3 kernel: [    1.201895] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 20 18:23:18 node-3 kernel: [    1.212464] usb usb2: Product: EHCI Host Controller
Aug 20 18:23:18 node-3 kernel: [    1.217930] usb usb2: Manufacturer: Linux 3.13.0-93-generic ehci_hcd
Aug 20 18:23:18 node-3 kernel: [    1.223463] usb usb2: SerialNumber: 0000:00:1d.0
Aug 20 18:23:18 node-3 kernel: [    1.228979] hub 2-0:1.0: USB hub found
Aug 20 18:23:18 node-3 kernel: [    1.234320] hub 2-0:1.0: 2 ports detected
Aug 20 18:23:18 node-3 kernel: [    1.239625] ehci-platform: EHCI generic platform driver
Aug 20 18:23:18 node-3 kernel: [    1.244846] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Aug 20 18:23:18 node-3 kernel: [    1.250158] ohci-pci: OHCI PCI platform driver
Aug 20 18:23:18 node-3 kernel: [    1.255459] ohci-platform: OHCI generic platform driver
Aug 20 18:23:18 node-3 kernel: [    1.260649] uhci_hcd: USB Universal Host Controller Interface driver
Aug 20 18:23:18 node-3 kernel: [    1.265983] i8042: PNP: No PS/2 controller found. Probing ports directly.
Aug 20 18:23:18 node-3 kernel: [    1.459155] usb 1-1: new high-speed USB device number 2 using ehci-pci
Aug 20 18:23:18 node-3 kernel: [    1.631331] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Aug 20 18:23:18 node-3 kernel: [    1.636852] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 20 18:23:18 node-3 kernel: [    1.642594] hub 1-1:1.0: USB hub found
Aug 20 18:23:18 node-3 kernel: [    1.648067] hub 1-1:1.0: 6 ports detected
Aug 20 18:23:18 node-3 kernel: [    1.762891] usb 2-1: new high-speed USB device number 2 using ehci-pci
Aug 20 18:23:18 node-3 kernel: [    1.770887] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Aug 20 18:23:18 node-3 kernel: [    2.030992] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Aug 20 18:23:18 node-3 kernel: [    2.036529] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 20 18:23:18 node-3 kernel: [    2.042385] hub 2-1:1.0: USB hub found
Aug 20 18:23:18 node-3 kernel: [    2.048104] hub 2-1:1.0: 8 ports detected
Aug 20 18:23:18 node-3 kernel: [    2.307279] i8042: No controller found
Aug 20 18:23:18 node-3 kernel: [    2.312681] mousedev: PS/2 mouse device common for all mice
Aug 20 18:23:18 node-3 kernel: [    2.318175] rtc_cmos 00:02: RTC can wake from S4
Aug 20 18:23:18 node-3 kernel: [    2.323736] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Aug 20 18:23:18 node-3 kernel: [    2.326483] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Aug 20 18:23:18 node-3 kernel: [    2.334897] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Aug 20 18:23:18 node-3 kernel: [    2.346008] device-mapper: uevent: version 1.0.3
Aug 20 18:23:18 node-3 kernel: [    2.351644] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Aug 20 18:23:18 node-3 kernel: [    2.362890] ledtrig-cpu: registered to indicate activity on CPUs
Aug 20 18:23:18 node-3 kernel: [    2.368942] TCP: cubic registered
Aug 20 18:23:18 node-3 kernel: [    2.374923] NET: Registered protocol family 10
Aug 20 18:23:18 node-3 kernel: [    2.380990] NET: Registered protocol family 17
Aug 20 18:23:18 node-3 kernel: [    2.386794] Key type dns_resolver registered
Aug 20 18:23:18 node-3 kernel: [    2.392835] Loading compiled-in X.509 certificates
Aug 20 18:23:18 node-3 kernel: [    2.399098] Loaded X.509 cert 'Magrathea: Glacier signing key: d5fcc7f0ec194773d05665948935931e3b1336a9'
Aug 20 18:23:18 node-3 kernel: [    2.410656] registered taskstats version 1
Aug 20 18:23:18 node-3 kernel: [    2.418728] Key type trusted registered
Aug 20 18:23:18 node-3 kernel: [    2.426346] Key type encrypted registered
Aug 20 18:23:18 node-3 kernel: [    2.431812] AppArmor: AppArmor sha1 policy hashing enabled
Aug 20 18:23:18 node-3 kernel: [    2.437308] IMA: No TPM chip found, activating TPM-bypass!
Aug 20 18:23:18 node-3 kernel: [    2.443469] regulator-dummy: disabling
Aug 20 18:23:18 node-3 kernel: [    2.449073]   Magic number: 12:248:393
Aug 20 18:23:18 node-3 kernel: [    2.454507] thermal cooling_device8: hash matches
Aug 20 18:23:18 node-3 kernel: [    2.460148] rtc_cmos 00:02: setting system clock to 2016-08-20 18:22:44 UTC (1471717364)
Aug 20 18:23:18 node-3 kernel: [    2.467323] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Aug 20 18:23:18 node-3 kernel: [    2.467325] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 20 18:23:18 node-3 kernel: [    2.467327] usb 2-1.4: Product: Cisco USB Composite Device-0
Aug 20 18:23:18 node-3 kernel: [    2.467329] usb 2-1.4: Manufacturer: Avocent
Aug 20 18:23:18 node-3 kernel: [    2.467330] usb 2-1.4: SerialNumber: 20111102-00000001
Aug 20 18:23:18 node-3 kernel: [    2.507379] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Aug 20 18:23:18 node-3 kernel: [    2.513122] EDD information not available.
Aug 20 18:23:18 node-3 kernel: [    2.518813] PM: Hibernation image not present or could not be loaded.
Aug 20 18:23:18 node-3 kernel: [    2.519689] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Aug 20 18:23:18 node-3 kernel: [    2.531210] Write protecting the kernel read-only data: 12288k
Aug 20 18:23:18 node-3 kernel: [    2.537462] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Aug 20 18:23:18 node-3 kernel: [    2.550047] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Aug 20 18:23:18 node-3 kernel: [    2.582577] device-mapper: multipath: version 1.6.0 loaded
Aug 20 18:23:18 node-3 kernel: [    2.590693] systemd-udevd[215]: starting version 204
Aug 20 18:23:18 node-3 kernel: [    2.616415] md: linear personality registered for level -1
Aug 20 18:23:18 node-3 kernel: [    2.630473] md: multipath personality registered for level -4
Aug 20 18:23:18 node-3 kernel: [    2.638779] md: raid0 personality registered for level 0
Aug 20 18:23:18 node-3 kernel: [    2.647111] md: raid1 personality registered for level 1
Aug 20 18:23:18 node-3 kernel: [    2.657245] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Aug 20 18:23:18 node-3 kernel: [    2.663661] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Aug 20 18:23:18 node-3 kernel: [    2.670039] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Aug 20 18:23:18 node-3 kernel: [    2.670845] megasas: FW now in Ready state
Aug 20 18:23:18 node-3 kernel: [    2.671007] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671050] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671104] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671144] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671183] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671222] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671261] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671316] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671371] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671398] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671432] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671469] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671518] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671577] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671615] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671652] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.671865] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Aug 20 18:23:18 node-3 kernel: [    2.695863] hidraw: raw HID events driver (C) Jiri Kosina
Aug 20 18:23:18 node-3 kernel: [    2.704128] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Aug 20 18:23:18 node-3 kernel: [    2.717029] 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
Aug 20 18:23:18 node-3 kernel: [    2.722360] raid6: sse2x1    2734 MB/s
Aug 20 18:23:18 node-3 kernel: [    2.737100] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 20 18:23:18 node-3 kernel: [    2.744032] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.744037] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.744041] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.744045] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.744086] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.757819] usbcore: registered new interface driver usbhid
Aug 20 18:23:18 node-3 kernel: [    2.764406] usbhid: USB HID core driver
Aug 20 18:23:18 node-3 kernel: [    2.767974] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Aug 20 18:23:18 node-3 kernel: [    2.767976] enic 0000:07: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
Aug 20 18:23:18 node-3 kernel: [    2.767977] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 20 18:23:18 node-3 kernel: [    2.768043] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.768081] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.768118] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.768152] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.768241] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 20 18:23:18 node-3 kernel: [    2.778307] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Aug 20 18:23:18 node-3 kernel: [    2.778309] 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
Aug 20 18:23:18 node-3 kernel: [    2.778310] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 20 18:23:18 node-3 kernel: [    2.790160] raid6: sse2x2    4873 MB/s
Aug 20 18:23:18 node-3 kernel: [    2.857972] raid6: sse2x4    9572 MB/s
Aug 20 18:23:18 node-3 kernel: [    2.929922] raid6: avx2x1   14940 MB/s
Aug 20 18:23:18 node-3 kernel: [    3.001851] raid6: avx2x2   18858 MB/s
Aug 20 18:23:18 node-3 kernel: [    3.073794] raid6: avx2x4   21319 MB/s
Aug 20 18:23:18 node-3 kernel: [    3.080038] raid6: using algorithm avx2x4 (21319 MB/s)
Aug 20 18:23:18 node-3 kernel: [    3.086214] raid6: using avx2x2 recovery algorithm
Aug 20 18:23:18 node-3 kernel: [    3.092301] megasas:IOC Init cmd success
Aug 20 18:23:18 node-3 kernel: [    3.092302] Switched to clocksource tsc
Aug 20 18:23:18 node-3 kernel: [    3.092347] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    3.092389] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    3.092430] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    3.092463] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    3.092549] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 20 18:23:18 node-3 kernel: [    3.100978] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Aug 20 18:23:18 node-3 kernel: [    3.100980] 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
Aug 20 18:23:18 node-3 kernel: [    3.100981] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 20 18:23:18 node-3 kernel: [    3.101045] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    3.101081] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    3.101118] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    3.101154] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Aug 20 18:23:18 node-3 kernel: [    3.101263] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 20 18:23:18 node-3 kernel: [    3.113783] megasas: INIT adapter done
Aug 20 18:23:18 node-3 kernel: [    3.163420] xor: automatically using best checksumming function:
Aug 20 18:23:18 node-3 kernel: [    3.169453] 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
Aug 20 18:23:18 node-3 kernel: [    3.181280] 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
Aug 20 18:23:18 node-3 kernel: [    3.185684] megaraid_sas 0000:01:00.0: Controller type: iMR
Aug 20 18:23:18 node-3 kernel: [    3.186016] scsi0 : LSI SAS based MegaRAID driver
Aug 20 18:23:18 node-3 kernel: [    3.193024] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Aug 20 18:23:18 node-3 kernel: [    3.204236] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Aug 20 18:23:18 node-3 kernel: [    3.205676]    avx       : 36558.000 MB/sec
Aug 20 18:23:18 node-3 kernel: [    3.208681] sd 0:2:0:0: Attached scsi generic sg0 type 0
Aug 20 18:23:18 node-3 kernel: [    3.208833] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Aug 20 18:23:18 node-3 kernel: [    3.209193] sd 0:2:0:0: [sda] Write Protect is off
Aug 20 18:23:18 node-3 kernel: [    3.209194] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Aug 20 18:23:18 node-3 kernel: [    3.209259] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Aug 20 18:23:18 node-3 kernel: [    3.236944]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Aug 20 18:23:18 node-3 kernel: [    3.238402] sd 0:2:0:0: [sda] Attached SCSI disk
Aug 20 18:23:18 node-3 kernel: [    3.287535] 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
Aug 20 18:23:18 node-3 kernel: [    3.301101] async_tx: api initialized (async)
Aug 20 18:23:18 node-3 kernel: [    3.301119] 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
Aug 20 18:23:18 node-3 kernel: [    3.301174] 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
Aug 20 18:23:18 node-3 kernel: [    3.301218] 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
Aug 20 18:23:18 node-3 kernel: [    3.352698] md: raid6 personality registered for level 6
Aug 20 18:23:18 node-3 kernel: [    3.359817] md: raid5 personality registered for level 5
Aug 20 18:23:18 node-3 kernel: [    3.366728] md: raid4 personality registered for level 4
Aug 20 18:23:18 node-3 kernel: [    3.376418] md: raid10 personality registered for level 10
Aug 20 18:23:18 node-3 kernel: [    3.425232] random: lvm urandom read with 28 bits of entropy available
Aug 20 18:23:18 node-3 kernel: [    3.436173] multipathd (367): /proc/367/oom_adj is deprecated, please use /proc/367/oom_score_adj instead.
Aug 20 18:23:18 node-3 kernel: [    3.587862] bio: create slab <bio-1> at 1
Aug 20 18:23:18 node-3 kernel: [    4.398196] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Aug 20 18:23:18 node-3 kernel: [    5.077946] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Aug 20 18:23:18 node-3 kernel: [    5.088126] random: nonblocking pool is initialized
Aug 20 18:23:18 node-3 kernel: [    5.154647] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Aug 20 18:23:18 node-3 kernel: [    5.284749] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Aug 20 18:23:18 node-3 kernel: [    5.332651] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Aug 20 18:23:18 node-3 kernel: [    5.449809] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Aug 20 18:23:18 node-3 kernel: [    5.585165] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Aug 20 18:23:18 node-3 kernel: [    5.656219] XFS (dm-0): Mounting Filesystem
Aug 20 18:23:18 node-3 kernel: [    5.945067] XFS (dm-0): Ending clean mount
Aug 20 18:23:18 node-3 kernel: [    6.000532] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Aug 20 18:23:18 node-3 kernel: [    6.027196] XFS (dm-1): Mounting Filesystem
Aug 20 18:23:18 node-3 kernel: [    6.152882] XFS (dm-1): Ending clean mount
Aug 20 18:23:18 node-3 kernel: [    7.969627] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Aug 20 18:23:18 node-3 kernel: [    7.998108] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Aug 20 18:23:18 node-3 kernel: [    8.180483] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 20 18:23:18 node-3 kernel: [    8.180488] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Aug 20 18:23:18 node-3 kernel: [    8.180492] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Aug 20 18:23:18 node-3 kernel: [    8.180495] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Aug 20 18:23:18 node-3 kernel: [    8.217543] systemd-udevd[777]: starting version 204
Aug 20 18:23:18 node-3 kernel: [    8.387428] power_meter ACPI000D:00: Found ACPI power meter.
Aug 20 18:23:18 node-3 kernel: [    8.387477] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Aug 20 18:23:18 node-3 kernel: [    8.439014] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Aug 20 18:23:18 node-3 kernel: [    8.439021] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Aug 20 18:23:18 node-3 kernel: [    8.439025] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Aug 20 18:23:18 node-3 kernel: [    8.439028] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Aug 20 18:23:18 node-3 kernel: [    8.439067] lpc_ich: Resource conflict(s) found affecting gpio_ich
Aug 20 18:23:18 node-3 kernel: [    8.443256] IPMI System Interface driver.
Aug 20 18:23:18 node-3 kernel: [    8.443303] ipmi_si: probing via ACPI
Aug 20 18:23:18 node-3 kernel: [    8.443327] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Aug 20 18:23:18 node-3 kernel: [    8.443328] ipmi_si: Adding ACPI-specified kcs state machine
Aug 20 18:23:18 node-3 kernel: [    8.443343] ipmi_si: probing via SMBIOS
Aug 20 18:23:18 node-3 kernel: [    8.443344] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Aug 20 18:23:18 node-3 kernel: [    8.443345] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Aug 20 18:23:18 node-3 kernel: [    8.443346] ipmi_si: probing via SPMI
Aug 20 18:23:18 node-3 kernel: [    8.443347] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Aug 20 18:23:18 node-3 kernel: [    8.443348] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Aug 20 18:23:18 node-3 kernel: [    8.443349] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Aug 20 18:23:18 node-3 kernel: [    8.459021] wmi: Mapper loaded
Aug 20 18:23:18 node-3 kernel: [    8.460142] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Aug 20 18:23:18 node-3 kernel: [    8.550064] systemd-udevd[796]: renamed network interface eth0 to enp6s0
Aug 20 18:23:18 node-3 kernel: [    8.573370] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Aug 20 18:23:18 node-3 kernel: [    8.573375] ipmi_si 00:09: IPMI kcs interface initialized
Aug 20 18:23:18 node-3 kernel: [    8.589647] systemd-udevd[794]: renamed network interface eth1 to enp7s0
Aug 20 18:23:18 node-3 kernel: [    8.613437] systemd-udevd[795]: renamed network interface eth2 to enp8s0
Aug 20 18:23:18 node-3 kernel: [    8.629459] systemd-udevd[797]: renamed network interface eth3 to enp9s0
Aug 20 18:23:18 node-3 kernel: [    9.012891] type=1400 audit(1471717371.054:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Aug 20 18:23:18 node-3 kernel: [    9.013038] type=1400 audit(1471717371.054:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1061 comm="apparmor_parser"
Aug 20 18:23:18 node-3 kernel: [    9.013163] type=1400 audit(1471717371.054:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1061 comm="apparmor_parser"
Aug 20 18:23:18 node-3 kernel: [    9.013636] type=1400 audit(1471717371.054:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Aug 20 18:23:18 node-3 kernel: [    9.013776] type=1400 audit(1471717371.054:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1060 comm="apparmor_parser"
Aug 20 18:23:18 node-3 kernel: [    9.013901] type=1400 audit(1471717371.054:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1060 comm="apparmor_parser"
Aug 20 18:23:18 node-3 kernel: [    9.023981] type=1400 audit(1471717371.062:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1056 comm="apparmor_parser"
Aug 20 18:23:18 node-3 kernel: [    9.024100] type=1400 audit(1471717371.062:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1056 comm="apparmor_parser"
Aug 20 18:23:18 node-3 kernel: [    9.024229] type=1400 audit(1471717371.062:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1056 comm="apparmor_parser"
Aug 20 18:23:18 node-3 kernel: [    9.024984] type=1400 audit(1471717371.066:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1064 comm="apparmor_parser"
Aug 20 18:23:18 node-3 kernel: [    9.677622] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Aug 20 18:23:18 node-3 kernel: [    9.678821] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Aug 20 18:23:18 node-3 kernel: [    9.871698] enic 0000:06:00.0 enp6s0: Link UP
Aug 20 18:23:18 node-3 kernel: [    9.872223] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Aug 20 18:23:18 node-3 kernel: [    9.872232] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Aug 20 18:23:18 node-3 kernel: [   19.128206] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Aug 20 18:23:19 node-3 failsafe: Failsafe of 120 seconds reached.
Aug 20 18:23:19 node-3 kernel: [   38.462246] init: failsafe main process (8411) killed by TERM signal
Aug 20 18:23:19 node-3 dbus[8443]: [system] AppArmor D-Bus mediation is enabled
Aug 20 18:23:20 node-3 kernel: [   38.669424] audit_printk_skb: 30 callbacks suppressed
Aug 20 18:23:20 node-3 kernel: [   38.669426] type=1400 audit(1471717400.085:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8539 comm="apparmor_parser"
Aug 20 18:23:20 node-3 kernel: [   38.673381] type=1400 audit(1471717400.089:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8538 comm="apparmor_parser"
Aug 20 18:23:20 node-3 kernel: [   38.673385] type=1400 audit(1471717400.089:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8538 comm="apparmor_parser"
Aug 20 18:23:20 node-3 kernel: [   38.673387] type=1400 audit(1471717400.089:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Aug 20 18:23:20 node-3 kernel: [   38.673610] type=1400 audit(1471717400.089:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8538 comm="apparmor_parser"
Aug 20 18:23:20 node-3 kernel: [   38.673613] type=1400 audit(1471717400.089:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Aug 20 18:23:20 node-3 kernel: [   38.673738] type=1400 audit(1471717400.089:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Aug 20 18:23:20 node-3 kernel: [   38.751339] type=1400 audit(1471717400.165:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8541 comm="apparmor_parser"
Aug 20 18:23:20 node-3 anacron[8601]: Anacron 2.3 started on 2016-08-20
Aug 20 18:23:20 node-3 cron[8569]: (CRON) INFO (pidfile fd = 3)
Aug 20 18:23:20 node-3 cron[8608]: (CRON) STARTUP (fork ok)
Aug 20 18:23:20 node-3 anacron[8601]: Will run job `cron.daily' in 5 min.
Aug 20 18:23:20 node-3 anacron[8601]: Will run job `cron.weekly' in 10 min.
Aug 20 18:23:20 node-3 anacron[8601]: Will run job `cron.monthly' in 15 min.
Aug 20 18:23:20 node-3 anacron[8601]: Jobs will be executed sequentially
Aug 20 18:23:20 node-3 multipathd: path checkers start up
Aug 20 18:23:20 node-3 cron[8608]: (CRON) INFO (Running @reboot jobs)
Aug 20 18:23:20 node-3 postfix/master[8749]: daemon started -- version 2.11.0, configuration /etc/postfix
Aug 20 18:23:24 node-3 puppet-agent[8934]: Reopening log files
Aug 20 18:23:24 node-3 puppet-agent[8934]: Could not request certificate: Connection refused - connect(2)
Aug 20 18:23:38 node-3 puppet-user[9142]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Aug 20 18:23:38 node-3 puppet-user[9142]: Compiled catalog for node-3.domain.tld in environment production in 0.04 seconds
Aug 20 18:23:39 node-3 puppet-user[9142]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Aug 20 18:23:39 node-3 puppet-user[9142]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Aug 20 18:23:39 node-3 puppet-user[9142]: Finished catalog run in 0.87 seconds
Aug 20 18:23:40 node-3 multipathd: uevent trigger error
Aug 20 18:23:41 node-3 puppet-user[9577]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Aug 20 18:23:41 node-3 puppet-user[9577]: Compiled catalog for node-3.domain.tld in environment production in 0.09 seconds
Aug 20 18:23:41 node-3 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Aug 20 18:23:41 node-3 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Aug 20 18:23:41 node-3 puppet-user[9577]: (/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"]'
Aug 20 18:23:41 node-3 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Aug 20 18:23:41 node-3 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Aug 20 18:23:41 node-3 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Aug 20 18:23:41 node-3 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Aug 20 18:23:41 node-3 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Aug 20 18:23:41 node-3 puppet-user[9577]: Finished catalog run in 0.06 seconds
Aug 20 18:23:42 node-3 puppet-user[10222]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Aug 20 18:23:42 node-3 puppet-user[10222]: Compiled catalog for node-3.domain.tld in environment production in 0.07 seconds
Aug 20 18:23:42 node-3 puppet-user[10222]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Aug 20 18:23:42 node-3 puppet-user[10222]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Aug 20 18:23:42 node-3 puppet-user[10222]: Finished catalog run in 0.02 seconds
Aug 20 18:23:44 node-3 puppet-user[10684]: (Scope(Class[main])) MODULAR: configuration_symlink
Aug 20 18:23:44 node-3 puppet-user[10684]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Aug 20 18:23:44 node-3 puppet-user[10684]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Aug 20 18:23:44 node-3 puppet-user[10684]: Finished catalog run in 0.04 seconds
Aug 20 18:23:45 node-3 puppet-user[11130]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Aug 20 18:23:45 node-3 puppet-user[11130]: Compiled catalog for node-3.domain.tld in environment production in 0.17 seconds
Aug 20 18:23:45 node-3 puppet-user[11130]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Aug 20 18:23:46 node-3 puppet-user[11130]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Aug 20 18:23:46 node-3 puppet-user[11130]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Aug 20 18:23:46 node-3 puppet-user[11130]: Finished catalog run in 0.79 seconds
Aug 20 18:23:47 node-3 puppet-user[11631]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Aug 20 18:23:47 node-3 puppet-user[11631]: Compiled catalog for node-3.domain.tld in environment production in 0.21 seconds
Aug 20 18:23:48 node-3 puppet-user[11631]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Aug 20 18:23:48 node-3 puppet-user[11631]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Aug 20 18:23:48 node-3 puppet-user[11631]: (/Stage[main]/Apt/File[preferences]/ensure) created
Aug 20 18:23:48 node-3 puppet-user[11631]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Aug 20 18:23:48 node-3 puppet-user[11631]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Aug 20 18:23:48 node-3 puppet-user[11631]: Finished catalog run in 0.31 seconds
Aug 20 18:23:49 node-3 puppet-user[12108]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Aug 20 18:23:49 node-3 puppet-user[12108]: Compiled catalog for node-3.domain.tld in environment production in 0.15 seconds
Aug 20 18:23:50 node-3 puppet-user[12108]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Aug 20 18:23:50 node-3 kernel: [   68.681753] nr_pdflush_threads exported in /proc is scheduled for removal
Aug 20 18:23:50 node-3 kernel: [   68.681802] 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.
Aug 20 18:23:50 node-3 puppet-user[12108]: (/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'
Aug 20 18:23:50 node-3 puppet-user[12108]: Finished catalog run in 0.05 seconds
Aug 20 18:23:52 node-3 puppet-user[12579]: (Scope(Class[main])) MODULAR: sync_time
Aug 20 18:23:52 node-3 puppet-user[12579]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Aug 20 18:23:52 node-3 ntpdate[12994]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Aug 20 18:23:53 node-3 kernel: [   71.645751] init: plymouth-upstart-bridge main process ended, respawning
Aug 20 18:23:53 node-3 puppet-agent[8934]: Could not run: SIGTERM
Aug 20 18:23:53 node-3 kernel: [   71.928479] ip_tables: (C) 2000-2006 Netfilter Core Team
Aug 20 18:23:53 node-3 ec2: 
Aug 20 18:23:53 node-3 ec2: #############################################################
Aug 20 18:23:53 node-3 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Aug 20 18:23:53 node-3 ec2: 1024 a7:1a:f4:f7:71:d8:54:a2:aa:29:d2:24:43:75:91:d2  root@node-3.domain.tld (DSA)
Aug 20 18:23:53 node-3 ec2: 256 67:e7:50:bb:5d:17:37:3f:67:4b:d9:1e:54:04:ad:28  root@node-3.domain.tld (ECDSA)
Aug 20 18:23:53 node-3 ec2: 256 4a:67:53:e8:e6:5a:a6:ad:13:32:58:7a:54:3e:c9:0b  root@node-3.domain.tld (ED25519)
Aug 20 18:23:53 node-3 ec2: 2048 ff:e2:79:0f:af:81:fc:48:67:73:3d:30:22:10:6a:f8  root@node-3.domain.tld (RSA)
Aug 20 18:23:53 node-3 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Aug 20 18:23:53 node-3 ec2: #############################################################
Aug 20 18:23:58 node-3 ntpdate[12994]: adjust time server 10.20.0.2 offset 0.327039 sec
Aug 20 18:23:58 node-3 puppet-user[12579]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Aug 20 18:23:58 node-3 puppet-user[12579]: Finished catalog run in 6.18 seconds
Aug 20 18:24:01 node-3 CRON[13336]: (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")
Aug 20 18:24:07 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 20 18:24:07 node-3 nailgun-agent: I, [2016-08-20T18:24:07.554035 #13339]  INFO -- : API URL is https://10.20.0.2:8443/api
Aug 20 18:24:20 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 20 18:24:20 node-3 nailgun-agent: I, [2016-08-20T18:24:20.310904 #13339]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Aug 20 18:24:45 node-3 puppet-user[13675]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Aug 20 18:24:45 node-3 puppet-user[13675]: Compiled catalog for node-3.domain.tld in environment production in 0.10 seconds
Aug 20 18:24:46 node-3 puppet-user[13675]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Aug 20 18:24:46 node-3 puppet-user[13675]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Aug 20 18:24:46 node-3 puppet-user[13675]: Finished catalog run in 0.08 seconds
Aug 20 18:24:47 node-3 puppet-user[14136]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Aug 20 18:24:49 node-3 puppet-user[14136]: Compiled catalog for node-3.domain.tld in environment production in 1.74 seconds
Aug 20 18:24:49 node-3 puppet-user[14136]: (/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
Aug 20 18:24:49 node-3 puppet-user[14136]: (/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
Aug 20 18:24:50 node-3 puppet-user[14136]: (/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
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Aug 20 18:24:50 node-3 puppet-user[14136]: (/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
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Aug 20 18:24:50 node-3 puppet-user[14136]: (/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
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Aug 20 18:24:50 node-3 puppet-user[14136]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Aug 20 18:25:01 node-3 CRON[14894]: (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")
Aug 20 18:25:04 node-3 puppet-user[14136]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Aug 20 18:25:04 node-3 puppet-user[14136]: Finished catalog run in 14.44 seconds
Aug 20 18:25:06 node-3 puppet-user[15012]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Aug 20 18:25:06 node-3 puppet-user[15012]: Compiled catalog for node-3.domain.tld in environment production in 0.13 seconds
Aug 20 18:25:11 node-3 puppet-user[15012]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Aug 20 18:25:18 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 20 18:25:18 node-3 nailgun-agent: I, [2016-08-20T18:25:18.485367 #14897]  INFO -- : API URL is https://10.20.0.2:8443/api
Aug 20 18:25:31 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 20 18:25:31 node-3 nailgun-agent: I, [2016-08-20T18:25:31.706167 #14897]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Aug 20 18:25:42 node-3 puppet-user[15012]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Aug 20 18:25:42 node-3 puppet-user[15012]: Finished catalog run in 35.73 seconds
Aug 20 18:25:44 node-3 puppet-user[17793]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Aug 20 18:25:44 node-3 puppet-user[17793]: Compiled catalog for node-3.domain.tld in environment production in 0.59 seconds
Aug 20 18:25:45 node-3 puppet-user[17793]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Aug 20 18:25:45 node-3 puppet-user[17793]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Aug 20 18:25:45 node-3 puppet-user[17793]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Aug 20 18:25:45 node-3 puppet-user[17793]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Aug 20 18:25:45 node-3 puppet-user[17793]: Finished catalog run in 0.08 seconds
Aug 20 18:25:46 node-3 puppet-user[18250]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Aug 20 18:25:47 node-3 puppet-user[18250]: Compiled catalog for node-3.domain.tld in environment production in 0.89 seconds
Aug 20 18:25:48 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Aug 20 18:25:48 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Aug 20 18:25:48 node-3 crontab[18694]: (root) LIST (root)
Aug 20 18:25:48 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Aug 20 18:25:48 node-3 crontab[18695]: (root) REPLACE (root)
Aug 20 18:25:50 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Aug 20 18:25:51 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Aug 20 18:25:51 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Aug 20 18:25:51 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Aug 20 18:25:51 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Aug 20 18:25:51 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Aug 20 18:25:51 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Aug 20 18:25:51 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Aug 20 18:25:51 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Aug 20 18:25:51 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/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
Aug 20 18:25:52 node-3 puppet-user[18250]: (/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
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/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
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/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
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/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
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/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
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/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
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/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
Aug 20 18:25:52 node-3 puppet-user[18250]: (/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
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Aug 20 18:25:52 node-3 puppet-user[18250]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Aug 20 18:25:52 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8384" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 20 18:25:52 node-3 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Aug 20 18:25:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:25:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:25:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:25:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:25:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:25:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:16 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:16 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:16 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:16 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:16 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:19 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:19 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:19 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:19 node-3 multipathd: uevent trigger error
<27>Aug 20 18:26:19 node-3 multipathd: uevent trigger error
<27>Aug 20 18:27:18 node-3 ntpdate[29882]: no servers can be used, exiting
<27>Aug 20 18:27:51 node-3 multipathd: uevent trigger error
<27>Aug 20 18:27:51 node-3 multipathd: uevent trigger error
<27>Aug 20 18:27:51 node-3 multipathd: uevent trigger error
<27>Aug 20 18:27:51 node-3 multipathd: uevent trigger error
<27>Aug 20 18:27:51 node-3 multipathd: uevent trigger error
<27>Aug 20 18:27:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:27:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:27:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:27:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:27:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:28:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:28:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:28:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:28:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:28:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:28:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:28:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:28:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:28:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:28:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:23 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 20 18:29:23 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 20 18:29:29 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 20 18:29:29 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 20 18:29:35 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 20 18:29:40 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 20 18:29:40 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 20 18:29:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:29:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:01 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:01 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:01 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:01 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:01 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:01 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:01 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:06 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:06 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:06 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:06 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:06 node-3 multipathd: uevent trigger error
<129>Aug 20 18:30:09 node-3 haproxy[19660]: 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>Aug 20 18:30:09 node-3 haproxy[19660]: 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>Aug 20 18:30:09 node-3 haproxy[19660]: 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>Aug 20 18:30:09 node-3 haproxy[19660]: proxy mysqld has no server available!
<27>Aug 20 18:30:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:12 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:15 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:15 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:15 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:15 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:15 node-3 multipathd: uevent trigger error
<129>Aug 20 18:30:18 node-3 haproxy[22315]: 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>Aug 20 18:30:18 node-3 haproxy[22315]: 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>Aug 20 18:30:18 node-3 haproxy[22315]: 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>Aug 20 18:30:18 node-3 haproxy[22315]: proxy mysqld has no server available!
<129>Aug 20 18:30:18 node-3 haproxy[22315]: 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>Aug 20 18:30:19 node-3 haproxy[22319]: 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>Aug 20 18:30:19 node-3 haproxy[22319]: 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>Aug 20 18:30:19 node-3 haproxy[22319]: proxy object-storage has no server available!
<27>Aug 20 18:30:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:21 node-3 multipathd: uevent trigger error
<129>Aug 20 18:30:23 node-3 haproxy[23942]: 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>Aug 20 18:30:23 node-3 haproxy[23942]: 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>Aug 20 18:30:23 node-3 haproxy[23942]: 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>Aug 20 18:30:23 node-3 haproxy[23942]: proxy neutron has no server available!
<129>Aug 20 18:30:23 node-3 haproxy[23942]: 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>Aug 20 18:30:24 node-3 haproxy[23951]: 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>Aug 20 18:30:24 node-3 haproxy[23951]: 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>Aug 20 18:30:24 node-3 haproxy[23951]: proxy mysqld has no server available!
<129>Aug 20 18:30:24 node-3 haproxy[23951]: 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>Aug 20 18:30:24 node-3 haproxy[23951]: 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>Aug 20 18:30:24 node-3 haproxy[23951]: 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>Aug 20 18:30:24 node-3 haproxy[23951]: proxy object-storage has no server available!
<27>Aug 20 18:30:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:26 node-3 multipathd: uevent trigger error
<129>Aug 20 18:30:29 node-3 haproxy[25420]: 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>Aug 20 18:30:29 node-3 haproxy[25420]: 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>Aug 20 18:30:29 node-3 haproxy[25420]: 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>Aug 20 18:30:29 node-3 haproxy[25420]: proxy keystone-1 has no server available!
<129>Aug 20 18:30:29 node-3 haproxy[25420]: 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>Aug 20 18:30:29 node-3 haproxy[25420]: 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>Aug 20 18:30:29 node-3 haproxy[25420]: 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>Aug 20 18:30:29 node-3 haproxy[25420]: proxy keystone-2 has no server available!
<129>Aug 20 18:30:29 node-3 haproxy[25420]: 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>Aug 20 18:30:29 node-3 haproxy[25420]: 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>Aug 20 18:30:30 node-3 haproxy[25424]: 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>Aug 20 18:30:30 node-3 haproxy[25424]: proxy neutron has no server available!
<129>Aug 20 18:30:30 node-3 haproxy[25424]: 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>Aug 20 18:30:30 node-3 haproxy[25424]: 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>Aug 20 18:30:30 node-3 haproxy[25424]: 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>Aug 20 18:30:30 node-3 haproxy[25424]: proxy mysqld has no server available!
<129>Aug 20 18:30:30 node-3 haproxy[25424]: 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>Aug 20 18:30:30 node-3 haproxy[25424]: 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>Aug 20 18:30:30 node-3 haproxy[25424]: 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>Aug 20 18:30:30 node-3 haproxy[25424]: proxy object-storage has no server available!
<27>Aug 20 18:30:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:32 node-3 multipathd: uevent trigger error
<129>Aug 20 18:30:34 node-3 haproxy[26807]: 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>Aug 20 18:30:34 node-3 haproxy[26807]: 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>Aug 20 18:30:34 node-3 haproxy[26807]: 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>Aug 20 18:30:34 node-3 haproxy[26807]: proxy keystone-1 has no server available!
<129>Aug 20 18:30:34 node-3 haproxy[26807]: 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>Aug 20 18:30:34 node-3 haproxy[26807]: 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>Aug 20 18:30:34 node-3 haproxy[26807]: 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>Aug 20 18:30:34 node-3 haproxy[26807]: proxy keystone-2 has no server available!
<129>Aug 20 18:30:35 node-3 haproxy[26811]: 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>Aug 20 18:30:35 node-3 haproxy[26811]: 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>Aug 20 18:30:35 node-3 haproxy[26811]: 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>Aug 20 18:30:35 node-3 haproxy[26811]: proxy neutron has no server available!
<129>Aug 20 18:30:35 node-3 haproxy[26811]: 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>Aug 20 18:30:35 node-3 haproxy[26811]: 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>Aug 20 18:30:35 node-3 haproxy[26811]: 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>Aug 20 18:30:35 node-3 haproxy[26811]: proxy mysqld has no server available!
<129>Aug 20 18:30:35 node-3 haproxy[26811]: 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>Aug 20 18:30:35 node-3 haproxy[26811]: 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>Aug 20 18:30:35 node-3 haproxy[26811]: 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>Aug 20 18:30:35 node-3 haproxy[26811]: proxy object-storage has no server available!
<129>Aug 20 18:30:35 node-3 haproxy[26811]: 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>Aug 20 18:30:36 node-3 haproxy[26811]: 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>Aug 20 18:30:36 node-3 haproxy[26811]: 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>Aug 20 18:30:36 node-3 haproxy[26811]: proxy aodh has no server available!
<27>Aug 20 18:30:37 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:37 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:37 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:37 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:37 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:37 node-3 multipathd: uevent trigger error
<129>Aug 20 18:30:39 node-3 haproxy[28232]: 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>Aug 20 18:30:39 node-3 haproxy[28232]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: proxy keystone-1 has no server available!
<129>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: proxy keystone-2 has no server available!
<129>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: proxy neutron has no server available!
<129>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:40 node-3 haproxy[28236]: proxy mysqld has no server available!
<129>Aug 20 18:30:40 node-3 haproxy[28236]: 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>Aug 20 18:30:41 node-3 haproxy[28236]: 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>Aug 20 18:30:41 node-3 haproxy[28236]: 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>Aug 20 18:30:41 node-3 haproxy[28236]: proxy object-storage has no server available!
<129>Aug 20 18:30:41 node-3 haproxy[28236]: 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>Aug 20 18:30:41 node-3 haproxy[28236]: 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>Aug 20 18:30:41 node-3 haproxy[28236]: 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>Aug 20 18:30:41 node-3 haproxy[28236]: proxy aodh has no server available!
<129>Aug 20 18:30:41 node-3 haproxy[28236]: 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>Aug 20 18:30:41 node-3 haproxy[28236]: 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>Aug 20 18:30:41 node-3 haproxy[28236]: 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>Aug 20 18:30:41 node-3 haproxy[28236]: proxy ceilometer has no server available!
<27>Aug 20 18:30:43 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:43 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:43 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:43 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:43 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:43 node-3 multipathd: uevent trigger error
<129>Aug 20 18:30:45 node-3 haproxy[29650]: 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>Aug 20 18:30:45 node-3 haproxy[29650]: 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>Aug 20 18:30:45 node-3 haproxy[29650]: 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>Aug 20 18:30:45 node-3 haproxy[29650]: proxy keystone-1 has no server available!
<129>Aug 20 18:30:45 node-3 haproxy[29650]: 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>Aug 20 18:30:45 node-3 haproxy[29650]: 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>Aug 20 18:30:45 node-3 haproxy[29650]: 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>Aug 20 18:30:45 node-3 haproxy[29650]: proxy keystone-2 has no server available!
<129>Aug 20 18:30:45 node-3 haproxy[29650]: 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>Aug 20 18:30:45 node-3 haproxy[29650]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: proxy neutron has no server available!
<129>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: proxy mysqld has no server available!
<129>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: proxy object-storage has no server available!
<129>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: proxy aodh has no server available!
<129>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:46 node-3 haproxy[29659]: 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>Aug 20 18:30:47 node-3 haproxy[29659]: 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>Aug 20 18:30:47 node-3 haproxy[29659]: proxy ceilometer has no server available!
<27>Aug 20 18:30:48 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:48 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:48 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:48 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:48 node-3 multipathd: uevent trigger error
<129>Aug 20 18:30:50 node-3 haproxy[31064]: 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>Aug 20 18:30:50 node-3 haproxy[31064]: 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>Aug 20 18:30:50 node-3 haproxy[31064]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: proxy keystone-1 has no server available!
<129>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: proxy keystone-2 has no server available!
<129>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: proxy neutron has no server available!
<129>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: proxy mysqld has no server available!
<129>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: 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>Aug 20 18:30:51 node-3 haproxy[31068]: proxy object-storage has no server available!
<129>Aug 20 18:30:52 node-3 haproxy[31068]: 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>Aug 20 18:30:52 node-3 haproxy[31068]: 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>Aug 20 18:30:52 node-3 haproxy[31068]: 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>Aug 20 18:30:52 node-3 haproxy[31068]: proxy aodh has no server available!
<129>Aug 20 18:30:52 node-3 haproxy[31068]: 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>Aug 20 18:30:52 node-3 haproxy[31068]: 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>Aug 20 18:30:52 node-3 haproxy[31068]: 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>Aug 20 18:30:52 node-3 haproxy[31068]: proxy ceilometer has no server available!
<27>Aug 20 18:30:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:53 node-3 multipathd: uevent trigger error
<129>Aug 20 18:30:56 node-3 haproxy[32554]: 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>Aug 20 18:30:56 node-3 haproxy[32554]: 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>Aug 20 18:30:56 node-3 haproxy[32554]: 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>Aug 20 18:30:56 node-3 haproxy[32554]: 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>Aug 20 18:30:56 node-3 haproxy[32554]: proxy keystone-1 has no server available!
<129>Aug 20 18:30:56 node-3 haproxy[32554]: 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>Aug 20 18:30:56 node-3 haproxy[32554]: 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>Aug 20 18:30:56 node-3 haproxy[32554]: 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>Aug 20 18:30:56 node-3 haproxy[32554]: proxy keystone-2 has no server available!
<129>Aug 20 18:30:56 node-3 haproxy[32554]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: proxy glance-api has no server available!
<129>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: proxy glance-glare has no server available!
<129>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: proxy neutron has no server available!
<129>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: proxy glance-registry has no server available!
<129>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: proxy mysqld has no server available!
<129>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: 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>Aug 20 18:30:57 node-3 haproxy[32558]: proxy object-storage has no server available!
<129>Aug 20 18:30:58 node-3 haproxy[32558]: 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>Aug 20 18:30:58 node-3 haproxy[32558]: 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>Aug 20 18:30:58 node-3 haproxy[32558]: 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>Aug 20 18:30:58 node-3 haproxy[32558]: proxy aodh has no server available!
<129>Aug 20 18:30:58 node-3 haproxy[32558]: 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>Aug 20 18:30:58 node-3 haproxy[32558]: 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>Aug 20 18:30:58 node-3 haproxy[32558]: 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>Aug 20 18:30:58 node-3 haproxy[32558]: proxy ceilometer has no server available!
<27>Aug 20 18:30:59 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:59 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:59 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:59 node-3 multipathd: uevent trigger error
<27>Aug 20 18:30:59 node-3 multipathd: uevent trigger error
<129>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:02 node-3 haproxy[1591]: proxy keystone-1 has no server available!
<129>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:02 node-3 haproxy[1591]: proxy keystone-2 has no server available!
<129>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:02 node-3 haproxy[1591]: proxy nova-api has no server available!
<129>Aug 20 18:31:02 node-3 haproxy[1591]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: proxy nova-metadata-api has no server available!
<129>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: proxy glance-api has no server available!
<129>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: proxy glance-glare has no server available!
<129>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: proxy neutron has no server available!
<129>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: proxy glance-registry has no server available!
<129>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: proxy mysqld has no server available!
<129>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: proxy object-storage has no server available!
<129>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:03 node-3 haproxy[1598]: 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>Aug 20 18:31:04 node-3 haproxy[1598]: 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>Aug 20 18:31:04 node-3 haproxy[1598]: proxy aodh has no server available!
<129>Aug 20 18:31:04 node-3 haproxy[1598]: 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>Aug 20 18:31:04 node-3 haproxy[1598]: 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>Aug 20 18:31:04 node-3 haproxy[1598]: 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>Aug 20 18:31:04 node-3 haproxy[1598]: proxy ceilometer has no server available!
<129>Aug 20 18:31:04 node-3 haproxy[1598]: 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>Aug 20 18:31:04 node-3 haproxy[1598]: 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>Aug 20 18:31:04 node-3 haproxy[1598]: 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>Aug 20 18:31:04 node-3 haproxy[1598]: proxy nova-novncproxy has no server available!
<27>Aug 20 18:31:05 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:05 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:05 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:05 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:05 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:05 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:05 node-3 multipathd: uevent trigger error
<129>Aug 20 18:31:07 node-3 haproxy[3147]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: proxy keystone-1 has no server available!
<129>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: proxy keystone-2 has no server available!
<129>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: proxy nova-api has no server available!
<129>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: proxy nova-metadata-api has no server available!
<129>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: proxy cinder-api has no server available!
<129>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: proxy glance-api has no server available!
<129>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: proxy glance-glare has no server available!
<129>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:08 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: proxy neutron has no server available!
<129>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: proxy glance-registry has no server available!
<129>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: proxy mysqld has no server available!
<129>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: proxy object-storage has no server available!
<129>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: proxy aodh has no server available!
<129>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: proxy ceilometer has no server available!
<129>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: 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>Aug 20 18:31:09 node-3 haproxy[3151]: proxy nova-novncproxy has no server available!
<27>Aug 20 18:31:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:11 node-3 multipathd: uevent trigger error
<129>Aug 20 18:31:13 node-3 haproxy[4643]: 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>Aug 20 18:31:13 node-3 haproxy[4643]: 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>Aug 20 18:31:13 node-3 haproxy[4643]: 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>Aug 20 18:31:13 node-3 haproxy[4643]: 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>Aug 20 18:31:13 node-3 haproxy[4643]: proxy keystone-1 has no server available!
<129>Aug 20 18:31:13 node-3 haproxy[4643]: 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>Aug 20 18:31:13 node-3 haproxy[4643]: 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>Aug 20 18:31:13 node-3 haproxy[4643]: 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>Aug 20 18:31:13 node-3 haproxy[4643]: proxy keystone-2 has no server available!
<129>Aug 20 18:31:13 node-3 haproxy[4643]: 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>Aug 20 18:31:13 node-3 haproxy[4643]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: proxy nova-api has no server available!
<129>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: proxy nova-metadata-api has no server available!
<129>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: proxy cinder-api has no server available!
<129>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: proxy glance-api has no server available!
<129>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: proxy glance-glare has no server available!
<129>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: proxy neutron has no server available!
<129>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: proxy glance-registry has no server available!
<129>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: proxy mysqld has no server available!
<129>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: proxy object-storage has no server available!
<129>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: 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>Aug 20 18:31:14 node-3 haproxy[4647]: proxy aodh has no server available!
<129>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: proxy ceilometer has no server available!
<129>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: proxy heat-api has no server available!
<129>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: proxy heat-api-cfn has no server available!
<129>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: proxy heat-api-cloudwatch has no server available!
<129>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: 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>Aug 20 18:31:15 node-3 haproxy[4647]: proxy nova-novncproxy has no server available!
<27>Aug 20 18:31:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:20 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:20 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:20 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:20 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:20 node-3 multipathd: uevent trigger error
<27>Aug 20 18:31:32 node-3 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Aug 20 18:31:57 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>Aug 20 18:31:59 node-3 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Aug 20 18:32:38 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 20 18:32:45 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 20 18:32:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:32:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:32:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:32:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:32:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:32:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:32:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:34:54 node-3 multipathd: uevent trigger error
<43>Aug 20 18:35:13 node-3 apache2_error [Sat Aug 20 18:35:06.721213 2016] [mpm_event:notice] [pid 11839:tid 140207222597504] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Aug 20 18:35:13 node-3 apache2_error [Sat Aug 20 18:35:06.721305 2016] [core:notice] [pid 11839:tid 140207222597504] AH00094: Command line: '/usr/sbin/apache2'
<43>Aug 20 18:35:13 node-3 apache2_error [Sat Aug 20 18:35:08.796862 2016] [mpm_event:notice] [pid 11839:tid 140207222597504] AH00491: caught SIGTERM, shutting down
<43>Aug 20 18:35:13 node-3 apache2_error [Sat Aug 20 18:35:09.874820 2016] [mpm_worker:notice] [pid 12300:tid 140493501134720] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Aug 20 18:35:13 node-3 apache2_error [Sat Aug 20 18:35:09.874950 2016] [core:notice] [pid 12300:tid 140493501134720] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 20 18:35:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:35:52 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 20 18:36:03 node-3 multipathd: uevent trigger error
<27>Aug 20 18:36:03 node-3 multipathd: uevent trigger error
<27>Aug 20 18:36:03 node-3 multipathd: uevent trigger error
<27>Aug 20 18:36:03 node-3 multipathd: uevent trigger error
<27>Aug 20 18:36:03 node-3 multipathd: uevent trigger error
<43>Aug 20 18:36:04 node-3 apache2_error [Sat Aug 20 18:36:00.141010 2016] [mpm_worker:notice] [pid 12300:tid 140493501134720] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 20 18:36:04 node-3 apache2_error [Sat Aug 20 18:36:00.148686 2016] [mpm_worker:warn] [pid 12300:tid 140493501134720] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 20 18:36:04 node-3 apache2_error [Sat Aug 20 18:36:00.149650 2016] [mpm_worker:notice] [pid 12300:tid 140493501134720] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Aug 20 18:36:04 node-3 apache2_error [Sat Aug 20 18:36:00.149658 2016] [core:notice] [pid 12300:tid 140493501134720] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 20 18:36:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:36:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:36:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:36:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:36:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:36:08 node-3 multipathd: uevent trigger error
<43>Aug 20 18:37:24 node-3 apache2_error [Sat Aug 20 18:37:17.642467 2016] [mpm_worker:notice] [pid 12300:tid 140493501134720] AH00295: caught SIGTERM, shutting down
<43>Aug 20 18:37:24 node-3 apache2_error [Sat Aug 20 18:37:18.388066 2016] [mpm_worker:notice] [pid 1903:tid 139728944256896] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 20 18:37:24 node-3 apache2_error [Sat Aug 20 18:37:18.388098 2016] [core:notice] [pid 1903:tid 139728944256896] AH00094: Command line: '/usr/sbin/apache2'
<43>Aug 20 18:38:04 node-3 apache2_error [Sat Aug 20 18:38:02.291713 2016] [mpm_worker:notice] [pid 1903:tid 139728944256896] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 20 18:38:04 node-3 apache2_error [Sat Aug 20 18:38:02.302223 2016] [mpm_worker:warn] [pid 1903:tid 139728944256896] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 20 18:38:04 node-3 apache2_error [Sat Aug 20 18:38:02.307016 2016] [mpm_worker:notice] [pid 1903:tid 139728944256896] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 20 18:38:04 node-3 apache2_error [Sat Aug 20 18:38:02.307042 2016] [core:notice] [pid 1903:tid 139728944256896] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 20 18:38:55 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 20 18:39:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:27 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:27 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:27 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:27 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:27 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:39:47 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:09 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:09 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:09 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:09 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:09 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:09 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:09 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:40:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:41:25 node-3 multipathd: uevent trigger error
<27>Aug 20 18:41:25 node-3 multipathd: uevent trigger error
<27>Aug 20 18:41:25 node-3 multipathd: uevent trigger error
<27>Aug 20 18:41:25 node-3 multipathd: uevent trigger error
<27>Aug 20 18:41:25 node-3 multipathd: uevent trigger error
<27>Aug 20 18:41:25 node-3 multipathd: uevent trigger error
<27>Aug 20 18:41:26 node-3 multipathd: uevent trigger error
<27>Aug 20 18:41:57 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 20 18:42:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:42:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:42:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:42:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:42:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:42:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:42:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:43:40 node-3 multipathd: uevent trigger error
<27>Aug 20 18:43:40 node-3 multipathd: uevent trigger error
<27>Aug 20 18:43:40 node-3 multipathd: uevent trigger error
<27>Aug 20 18:43:40 node-3 multipathd: uevent trigger error
<27>Aug 20 18:43:40 node-3 multipathd: uevent trigger error
<27>Aug 20 18:43:40 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:03 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:03 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:03 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:03 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:03 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:08 node-3 multipathd: uevent trigger error
<27>Aug 20 18:44:59 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 20 18:46:36 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:36 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:36 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:36 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:36 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:52 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:46:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:04 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:04 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:04 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:04 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:04 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:28 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:47:32 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:00 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 20 18:48:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:48:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:33 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:33 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:33 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:33 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:33 node-3 multipathd: uevent trigger error
<27>Aug 20 18:49:33 node-3 multipathd: uevent trigger error
<27>Aug 20 18:51:01 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 20 18:51:56 node-3 multipathd: uevent trigger error
<27>Aug 20 18:51:56 node-3 multipathd: uevent trigger error
<27>Aug 20 18:51:56 node-3 multipathd: uevent trigger error
<27>Aug 20 18:51:56 node-3 multipathd: uevent trigger error
<27>Aug 20 18:51:56 node-3 multipathd: uevent trigger error
<27>Aug 20 18:51:56 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:18 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:18 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:18 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:18 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:18 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:18 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:18 node-3 multipathd: uevent trigger error
<27>Aug 20 18:52:19 node-3 multipathd: sda: spurious uevent, path already in pathvec
<27>Aug 20 18:53:16 node-3 multipathd: uevent trigger error
<27>Aug 20 18:53:16 node-3 multipathd: uevent trigger error
<27>Aug 20 18:53:16 node-3 multipathd: uevent trigger error
<27>Aug 20 18:53:16 node-3 multipathd: uevent trigger error
<27>Aug 20 18:53:16 node-3 multipathd: uevent trigger error
<27>Aug 20 18:53:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:53:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:53:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:53:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:53:21 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:02 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 20 18:54:02 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:02 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:02 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:02 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:02 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:06 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:07 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:07 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:07 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:07 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:07 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:11 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:23 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:29 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:29 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:29 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:29 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:29 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:54:54 node-3 multipathd: uevent trigger error
<27>Aug 20 18:55:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:55:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:55:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:55:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:55:58 node-3 multipathd: uevent trigger error
<27>Aug 20 18:56:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:56:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:56:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:56:14 node-3 multipathd: uevent trigger error
<27>Aug 20 18:56:14 node-3 multipathd: uevent trigger error
<11>Aug 20 18:56:27 node-3 liberasurecode[60167]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:27 node-3 liberasurecode[60167]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:27 node-3 liberasurecode[60167]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:27 node-3 liberasurecode[60167]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:27 node-3 liberasurecode[60196]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:27 node-3 liberasurecode[60196]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:27 node-3 liberasurecode[60196]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:27 node-3 liberasurecode[60196]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:29 node-3 liberasurecode[60702]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:29 node-3 liberasurecode[60702]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:29 node-3 liberasurecode[60702]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:29 node-3 liberasurecode[60702]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61483]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61483]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61483]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61483]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61524]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61524]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61524]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61524]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61574]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61574]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61574]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:35 node-3 liberasurecode[61574]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61632]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61632]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61632]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61632]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61646]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61646]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61646]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61646]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61663]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61663]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61663]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61663]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61675]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61675]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61675]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:36 node-3 liberasurecode[61675]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:44 node-3 liberasurecode[62087]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:44 node-3 liberasurecode[62087]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:44 node-3 liberasurecode[62087]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 18:56:44 node-3 liberasurecode[62087]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Aug 20 18:56:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:56:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:56:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:56:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:56:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:56:53 node-3 multipathd: uevent trigger error
<27>Aug 20 18:57:03 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Aug 20 18:57:45 node-3 apache2_error [Sat Aug 20 18:57:41.207540 2016] [mpm_worker:notice] [pid 1903:tid 139728944256896] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 20 18:57:45 node-3 apache2_error [Sat Aug 20 18:57:41.590642 2016] [mpm_worker:warn] [pid 1903:tid 139728944256896] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 20 18:57:45 node-3 apache2_error [Sat Aug 20 18:57:41.594693 2016] [mpm_worker:notice] [pid 1903:tid 139728944256896] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 20 18:57:45 node-3 apache2_error [Sat Aug 20 18:57:41.594710 2016] [core:notice] [pid 1903:tid 139728944256896] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 20 18:58:22 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:22 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:22 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:22 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:22 node-3 multipathd: uevent trigger error
<43>Aug 20 18:58:25 node-3 apache2_error [Sat Aug 20 18:58:18.466716 2016] [mpm_worker:notice] [pid 1903:tid 139728944256896] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 20 18:58:25 node-3 apache2_error [Sat Aug 20 18:58:18.667107 2016] [mpm_worker:warn] [pid 1903:tid 139728944256896] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 20 18:58:25 node-3 apache2_error [Sat Aug 20 18:58:18.677128 2016] [mpm_worker:notice] [pid 1903:tid 139728944256896] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 20 18:58:25 node-3 apache2_error [Sat Aug 20 18:58:18.677162 2016] [core:notice] [pid 1903:tid 139728944256896] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 20 18:58:29 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:29 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:29 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:29 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:29 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:35 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:35 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:35 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:35 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:35 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:58:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:17 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:24 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:24 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:24 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:24 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:24 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:32 node-3 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Aug 20 18:59:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:41 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:46 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:46 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:46 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:46 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:46 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:55 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:56 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:56 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:56 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:56 node-3 multipathd: uevent trigger error
<27>Aug 20 18:59:56 node-3 multipathd: uevent trigger error
<11>Aug 20 19:00:01 node-3 liberasurecode[105736]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 19:00:01 node-3 liberasurecode[105736]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 19:00:01 node-3 liberasurecode[105736]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 20 19:00:01 node-3 liberasurecode[105736]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Aug 20 19:00:01 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:01 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:01 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:01 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:01 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:17 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 20 19:00:18 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:18 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:18 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:18 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:18 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:45 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:45 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:45 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:45 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:45 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:58 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:58 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:58 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:58 node-3 multipathd: uevent trigger error
<27>Aug 20 19:00:58 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:05 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:05 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:05 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:05 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:05 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:10 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:10 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:10 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:10 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:23 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:23 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:23 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:23 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:23 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:53 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:53 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:53 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:53 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:53 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:53 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:58 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:58 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:58 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:58 node-3 multipathd: uevent trigger error
<27>Aug 20 19:01:58 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:03 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:03 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:03 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:03 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:03 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:07 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:07 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:07 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:07 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:07 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:13 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:17 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:18 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:18 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:18 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:18 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:22 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:22 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:22 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:22 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:22 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:27 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:27 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:27 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:27 node-3 multipathd: uevent trigger error
<27>Aug 20 19:02:27 node-3 multipathd: uevent trigger error
