Aug 22 21:05:07 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8429" x-info="http://www.rsyslog.com"] start
Aug 22 21:05:07 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Aug 22 21:05:07 node-3 rsyslogd: rsyslogd's groupid changed to 104
Aug 22 21:05:07 node-3 rsyslogd: rsyslogd's userid changed to 101
Aug 22 21:05:07 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuset
Aug 22 21:05:07 node-3 kernel: [    0.000000] Initializing cgroup subsys cpu
Aug 22 21:05:07 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Aug 22 21:05:07 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 22 21:05:07 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=88142083-d94e-4a43-9af8-d66319f53dd4 nomdmonddf nomdmonisw
Aug 22 21:05:07 node-3 kernel: [    0.000000] KERNEL supported cpus:
Aug 22 21:05:07 node-3 kernel: [    0.000000]   Intel GenuineIntel
Aug 22 21:05:07 node-3 kernel: [    0.000000]   AMD AuthenticAMD
Aug 22 21:05:07 node-3 kernel: [    0.000000]   Centaur CentaurHauls
Aug 22 21:05:07 node-3 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Aug 22 21:05:07 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Aug 22 21:05:07 node-3 kernel: [    0.000000] NX (Execute Disable) protection: active
Aug 22 21:05:07 node-3 kernel: [    0.000000] SMBIOS 2.8 present.
Aug 22 21:05:07 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 22 21:05:07 node-3 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Aug 22 21:05:07 node-3 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Aug 22 21:05:07 node-3 kernel: [    0.000000] No AGP bridge found
Aug 22 21:05:07 node-3 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Aug 22 21:05:07 node-3 kernel: [    0.000000] MTRR default type: write-back
Aug 22 21:05:07 node-3 kernel: [    0.000000] MTRR fixed ranges enabled:
Aug 22 21:05:07 node-3 kernel: [    0.000000]   00000-9FFFF write-back
Aug 22 21:05:07 node-3 kernel: [    0.000000]   A0000-BFFFF uncachable
Aug 22 21:05:07 node-3 kernel: [    0.000000]   C0000-FFFFF write-protect
Aug 22 21:05:07 node-3 kernel: [    0.000000] MTRR variable ranges enabled:
Aug 22 21:05:07 node-3 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Aug 22 21:05:07 node-3 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Aug 22 21:05:07 node-3 kernel: [    0.000000]   2 disabled
Aug 22 21:05:07 node-3 kernel: [    0.000000]   3 disabled
Aug 22 21:05:07 node-3 kernel: [    0.000000]   4 disabled
Aug 22 21:05:07 node-3 kernel: [    0.000000]   5 disabled
Aug 22 21:05:07 node-3 kernel: [    0.000000]   6 disabled
Aug 22 21:05:07 node-3 kernel: [    0.000000]   7 disabled
Aug 22 21:05:07 node-3 kernel: [    0.000000]   8 disabled
Aug 22 21:05:07 node-3 kernel: [    0.000000]   9 disabled
Aug 22 21:05:07 node-3 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Aug 22 21:05:07 node-3 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Aug 22 21:05:07 node-3 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Aug 22 21:05:07 node-3 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Aug 22 21:05:07 node-3 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Aug 22 21:05:07 node-3 kernel: [    0.000000] Using GB pages for direct mapping
Aug 22 21:05:07 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Aug 22 21:05:07 node-3 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Aug 22 21:05:07 node-3 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Aug 22 21:05:07 node-3 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Aug 22 21:05:07 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Aug 22 21:05:07 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Aug 22 21:05:07 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Aug 22 21:05:07 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Aug 22 21:05:07 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Aug 22 21:05:07 node-3 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Aug 22 21:05:07 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Aug 22 21:05:07 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Aug 22 21:05:07 node-3 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Aug 22 21:05:07 node-3 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Aug 22 21:05:07 node-3 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Aug 22 21:05:07 node-3 kernel: [    0.000000] Zone ranges:
Aug 22 21:05:07 node-3 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] Movable zone start for each node
Aug 22 21:05:07 node-3 kernel: [    0.000000] Early memory node ranges
Aug 22 21:05:07 node-3 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] On node 0 totalpages: 4125820
Aug 22 21:05:07 node-3 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Aug 22 21:05:07 node-3 kernel: [    0.000000]   DMA zone: 21 pages reserved
Aug 22 21:05:07 node-3 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Aug 22 21:05:07 node-3 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Aug 22 21:05:07 node-3 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Aug 22 21:05:07 node-3 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Aug 22 21:05:07 node-3 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Aug 22 21:05:07 node-3 kernel: [    0.000000] On node 1 totalpages: 4194304
Aug 22 21:05:07 node-3 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Aug 22 21:05:07 node-3 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Aug 22 21:05:07 node-3 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Aug 22 21:05:07 node-3 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Aug 22 21:05:07 node-3 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: IRQ0 used by override.
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: IRQ2 used by override.
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: IRQ9 used by override.
Aug 22 21:05:07 node-3 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Aug 22 21:05:07 node-3 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Aug 22 21:05:07 node-3 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Aug 22 21:05:07 node-3 kernel: [    0.000000] nr_irqs_gsi: 88
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Aug 22 21:05:07 node-3 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Aug 22 21:05:07 node-3 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Aug 22 21:05:07 node-3 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Aug 22 21:05:07 node-3 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Aug 22 21:05:07 node-3 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Aug 22 21:05:07 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 22 21:05:07 node-3 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Aug 22 21:05:07 node-3 kernel: [    0.000000] Policy zone: Normal
Aug 22 21:05:07 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=88142083-d94e-4a43-9af8-d66319f53dd4 nomdmonddf nomdmonisw
Aug 22 21:05:07 node-3 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Aug 22 21:05:07 node-3 kernel: [    0.000000] Checking aperture...
Aug 22 21:05:07 node-3 kernel: [    0.000000] No AGP bridge found
Aug 22 21:05:07 node-3 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Aug 22 21:05:07 node-3 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Aug 22 21:05:07 node-3 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Aug 22 21:05:07 node-3 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Aug 22 21:05:07 node-3 kernel: [    0.000000] Hierarchical RCU implementation.
Aug 22 21:05:07 node-3 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Aug 22 21:05:07 node-3 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Aug 22 21:05:07 node-3 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Aug 22 21:05:07 node-3 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Aug 22 21:05:07 node-3 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Aug 22 21:05:07 node-3 kernel: [    0.000000] Console: colour dummy device 80x25
Aug 22 21:05:07 node-3 kernel: [    0.000000] console [tty0] enabled
Aug 22 21:05:07 node-3 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Aug 22 21:05:07 node-3 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Aug 22 21:05:07 node-3 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Aug 22 21:05:07 node-3 kernel: [    0.000000] hpet clockevent registered
Aug 22 21:05:07 node-3 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Aug 22 21:05:07 node-3 kernel: [    0.004000] tsc: Detected 3491.853 MHz processor
Aug 22 21:05:07 node-3 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.70 BogoMIPS (lpj=13967412)
Aug 22 21:05:07 node-3 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Aug 22 21:05:07 node-3 kernel: [    0.000047] Security Framework initialized
Aug 22 21:05:07 node-3 kernel: [    0.000067] AppArmor: AppArmor initialized
Aug 22 21:05:07 node-3 kernel: [    0.000068] Yama: becoming mindful.
Aug 22 21:05:07 node-3 kernel: [    0.001457] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.006362] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.008290] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.008318] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.008610] Initializing cgroup subsys memory
Aug 22 21:05:07 node-3 kernel: [    0.008618] Initializing cgroup subsys devices
Aug 22 21:05:07 node-3 kernel: [    0.008620] Initializing cgroup subsys freezer
Aug 22 21:05:07 node-3 kernel: [    0.008622] Initializing cgroup subsys blkio
Aug 22 21:05:07 node-3 kernel: [    0.008623] Initializing cgroup subsys perf_event
Aug 22 21:05:07 node-3 kernel: [    0.008625] Initializing cgroup subsys hugetlb
Aug 22 21:05:07 node-3 kernel: [    0.008645] CPU: Physical Processor ID: 0
Aug 22 21:05:07 node-3 kernel: [    0.008646] CPU: Processor Core ID: 0
Aug 22 21:05:07 node-3 kernel: [    0.008650] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Aug 22 21:05:07 node-3 kernel: [    0.008650] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Aug 22 21:05:07 node-3 kernel: [    0.009344] mce: CPU supports 22 MCE banks
Aug 22 21:05:07 node-3 kernel: [    0.009371] CPU0: Thermal monitoring enabled (TM1)
Aug 22 21:05:07 node-3 kernel: [    0.009392] process: using mwait in idle threads
Aug 22 21:05:07 node-3 kernel: [    0.009395] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Aug 22 21:05:07 node-3 kernel: [    0.009395] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Aug 22 21:05:07 node-3 kernel: [    0.009395] tlb_flushall_shift: 6
Aug 22 21:05:07 node-3 kernel: [    0.009483] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Aug 22 21:05:07 node-3 kernel: [    0.010209] ACPI: Core revision 20131115
Aug 22 21:05:07 node-3 kernel: [    0.022888] ACPI: All ACPI Tables successfully acquired
Aug 22 21:05:07 node-3 kernel: [    0.023050] ftrace: allocating 28617 entries in 112 pages
Aug 22 21:05:07 node-3 kernel: [    0.032034] dmar: Host address width 46
Aug 22 21:05:07 node-3 kernel: [    0.032036] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Aug 22 21:05:07 node-3 kernel: [    0.032042] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Aug 22 21:05:07 node-3 kernel: [    0.032044] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Aug 22 21:05:07 node-3 kernel: [    0.032048] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Aug 22 21:05:07 node-3 kernel: [    0.032049] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Aug 22 21:05:07 node-3 kernel: [    0.032050] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Aug 22 21:05:07 node-3 kernel: [    0.032051] dmar: ATSR flags: 0x0
Aug 22 21:05:07 node-3 kernel: [    0.032053] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Aug 22 21:05:07 node-3 kernel: [    0.032054] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Aug 22 21:05:07 node-3 kernel: [    0.032169] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Aug 22 21:05:07 node-3 kernel: [    0.032170] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Aug 22 21:05:07 node-3 kernel: [    0.032171] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Aug 22 21:05:07 node-3 kernel: [    0.032172] HPET id 0 under DRHD base 0xc7ffc000
Aug 22 21:05:07 node-3 kernel: [    0.032173] Your BIOS is broken and requested that x2apic be disabled.
Aug 22 21:05:07 node-3 kernel: [    0.032173] This will slightly decrease performance.
Aug 22 21:05:07 node-3 kernel: [    0.032173] Use 'intremap=no_x2apic_optout' to override BIOS request.
Aug 22 21:05:07 node-3 kernel: [    0.032607] Enabled IRQ remapping in xapic mode
Aug 22 21:05:07 node-3 kernel: [    0.032608] x2apic not enabled, IRQ remapping is in xapic mode
Aug 22 21:05:07 node-3 kernel: [    0.032612] Switched APIC routing to physical flat.
Aug 22 21:05:07 node-3 kernel: [    0.033236] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Aug 22 21:05:07 node-3 kernel: [    0.072885] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Aug 22 21:05:07 node-3 kernel: [    0.072891] TSC deadline timer enabled
Aug 22 21:05:07 node-3 kernel: [    0.072898] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Aug 22 21:05:07 node-3 kernel: [    0.072904] ... version:                3
Aug 22 21:05:07 node-3 kernel: [    0.072905] ... bit width:              48
Aug 22 21:05:07 node-3 kernel: [    0.072906] ... generic registers:      4
Aug 22 21:05:07 node-3 kernel: [    0.072907] ... value mask:             0000ffffffffffff
Aug 22 21:05:07 node-3 kernel: [    0.072908] ... max period:             0000ffffffffffff
Aug 22 21:05:07 node-3 kernel: [    0.072909] ... fixed-purpose events:   3
Aug 22 21:05:07 node-3 kernel: [    0.072910] ... event mask:             000000070000000f
Aug 22 21:05:07 node-3 kernel: [    0.074309] x86: Booting SMP configuration:
Aug 22 21:05:07 node-3 kernel: [    0.088513] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Aug 22 21:05:07 node-3 kernel: [    0.074311] .... node  #0, CPUs:        #1  #2  #3
Aug 22 21:05:07 node-3 kernel: [    0.116426] .... node  #1, CPUs:    #4  #5  #6  #7
Aug 22 21:05:07 node-3 kernel: [    0.270396] .... node  #0, CPUs:    #8  #9 #10 #11
Aug 22 21:05:07 node-3 kernel: [    0.326011] .... node  #1, CPUs:   #12 #13 #14 #15
Aug 22 21:05:07 node-3 kernel: [    0.382461] x86: Booted up 2 nodes, 16 CPUs
Aug 22 21:05:07 node-3 kernel: [    0.382465] smpboot: Total of 16 processors activated (111751.08 BogoMIPS)
Aug 22 21:05:07 node-3 kernel: [    0.405557] devtmpfs: initialized
Aug 22 21:05:07 node-3 kernel: [    0.408649] EVM: security.selinux
Aug 22 21:05:07 node-3 kernel: [    0.408651] EVM: security.SMACK64
Aug 22 21:05:07 node-3 kernel: [    0.408652] EVM: security.ima
Aug 22 21:05:07 node-3 kernel: [    0.408653] EVM: security.capability
Aug 22 21:05:07 node-3 kernel: [    0.408702] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.409385] pinctrl core: initialized pinctrl subsystem
Aug 22 21:05:07 node-3 kernel: [    0.409445] regulator-dummy: no parameters
Aug 22 21:05:07 node-3 kernel: [    0.409476] RTC time: 21:04:31, date: 08/22/16
Aug 22 21:05:07 node-3 kernel: [    0.409509] NET: Registered protocol family 16
Aug 22 21:05:07 node-3 kernel: [    0.409593] cpuidle: using governor ladder
Aug 22 21:05:07 node-3 kernel: [    0.409594] cpuidle: using governor menu
Aug 22 21:05:07 node-3 kernel: [    0.409629] ACPI: bus type PCI registered
Aug 22 21:05:07 node-3 kernel: [    0.409631] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Aug 22 21:05:07 node-3 kernel: [    0.409676] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Aug 22 21:05:07 node-3 kernel: [    0.409678] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Aug 22 21:05:07 node-3 kernel: [    0.423404] PCI: Using configuration type 1 for base access
Aug 22 21:05:07 node-3 kernel: [    0.424392] bio: create slab <bio-0> at 0
Aug 22 21:05:07 node-3 kernel: [    0.424652] ACPI: Added _OSI(Module Device)
Aug 22 21:05:07 node-3 kernel: [    0.424654] ACPI: Added _OSI(Processor Device)
Aug 22 21:05:07 node-3 kernel: [    0.424655] ACPI: Added _OSI(3.0 _SCP Extensions)
Aug 22 21:05:07 node-3 kernel: [    0.424656] ACPI: Added _OSI(Processor Aggregator Device)
Aug 22 21:05:07 node-3 kernel: [    0.437368] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Aug 22 21:05:07 node-3 kernel: [    0.447902] ACPI: Interpreter enabled
Aug 22 21:05:07 node-3 kernel: [    0.447907] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Aug 22 21:05:07 node-3 kernel: [    0.447911] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Aug 22 21:05:07 node-3 kernel: [    0.447914] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Aug 22 21:05:07 node-3 kernel: [    0.447921] ACPI: (supports S0 S4 S5)
Aug 22 21:05:07 node-3 kernel: [    0.447922] ACPI: Using IOAPIC for interrupt routing
Aug 22 21:05:07 node-3 kernel: [    0.447967] HEST: Table parsing has been initialized.
Aug 22 21:05:07 node-3 kernel: [    0.447970] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Aug 22 21:05:07 node-3 kernel: [    0.448547] ACPI: No dock devices found.
Aug 22 21:05:07 node-3 kernel: [    0.460704] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Aug 22 21:05:07 node-3 kernel: [    0.460709] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 22 21:05:07 node-3 kernel: [    0.460712] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Aug 22 21:05:07 node-3 kernel: [    0.460741] PCI host bridge to bus 0000:ff
Aug 22 21:05:07 node-3 kernel: [    0.460743] pci_bus 0000:ff: root bus resource [bus ff]
Aug 22 21:05:07 node-3 kernel: [    0.460751] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.460789] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.460819] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.460854] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.460884] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.460913] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.460944] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.460972] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461002] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461030] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461056] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461082] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461110] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461136] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461162] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461188] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461216] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461243] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461270] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.461297] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461323] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.461348] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461374] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461403] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.461437] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461468] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461498] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461528] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461558] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461589] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461622] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461654] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461685] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461715] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461746] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461776] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461807] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461836] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461863] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461895] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461927] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.461966] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462002] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462032] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462063] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462092] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462124] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462159] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462191] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462222] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462253] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462282] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462311] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462340] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462369] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462400] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462431] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462488] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Aug 22 21:05:07 node-3 kernel: [    0.462491] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 22 21:05:07 node-3 kernel: [    0.462494] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Aug 22 21:05:07 node-3 kernel: [    0.462512] PCI host bridge to bus 0000:7f
Aug 22 21:05:07 node-3 kernel: [    0.462513] pci_bus 0000:7f: root bus resource [bus 7f]
Aug 22 21:05:07 node-3 kernel: [    0.462518] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462546] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.462573] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462603] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462625] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.462649] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.462674] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462699] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462722] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462744] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462767] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462790] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462813] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462836] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462859] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462885] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462907] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462931] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.462953] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.462977] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463000] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.463023] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463046] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463073] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Aug 22 21:05:07 node-3 kernel: [    0.463107] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463135] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463163] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463192] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463217] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463246] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463274] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463304] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463329] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463355] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463384] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463412] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463441] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463466] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463493] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463523] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463549] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463577] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463607] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463635] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463661] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463688] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463714] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463745] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463772] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463798] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463828] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463853] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463876] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463902] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463927] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463956] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.463983] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.465236] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Aug 22 21:05:07 node-3 kernel: [    0.465240] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 22 21:05:07 node-3 kernel: [    0.466375] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Aug 22 21:05:07 node-3 kernel: [    0.466885] PCI host bridge to bus 0000:00
Aug 22 21:05:07 node-3 kernel: [    0.466888] pci_bus 0000:00: root bus resource [bus 00-7e]
Aug 22 21:05:07 node-3 kernel: [    0.466890] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Aug 22 21:05:07 node-3 kernel: [    0.466891] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Aug 22 21:05:07 node-3 kernel: [    0.466892] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Aug 22 21:05:07 node-3 kernel: [    0.466894] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Aug 22 21:05:07 node-3 kernel: [    0.466895] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Aug 22 21:05:07 node-3 kernel: [    0.466896] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Aug 22 21:05:07 node-3 kernel: [    0.466902] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Aug 22 21:05:07 node-3 kernel: [    0.466985] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.467016] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.467058] pci 0000:00:01.0: System wakeup disabled by ACPI
Aug 22 21:05:07 node-3 kernel: [    0.467078] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.467107] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.467148] pci 0000:00:02.0: System wakeup disabled by ACPI
Aug 22 21:05:07 node-3 kernel: [    0.467167] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.467196] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.467237] pci 0000:00:03.0: System wakeup disabled by ACPI
Aug 22 21:05:07 node-3 kernel: [    0.467254] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.467327] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.467406] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.467483] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Aug 22 21:05:07 node-3 kernel: [    0.467488] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Aug 22 21:05:07 node-3 kernel: [    0.467574] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Aug 22 21:05:07 node-3 kernel: [    0.467723] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Aug 22 21:05:07 node-3 kernel: [    0.467741] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Aug 22 21:05:07 node-3 kernel: [    0.467819] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.467872] pci 0000:00:1a.0: System wakeup disabled by ACPI
Aug 22 21:05:07 node-3 kernel: [    0.467894] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.467950] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.467993] pci 0000:00:1c.0: System wakeup disabled by ACPI
Aug 22 21:05:07 node-3 kernel: [    0.468022] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.468077] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.468121] pci 0000:00:1c.7: System wakeup disabled by ACPI
Aug 22 21:05:07 node-3 kernel: [    0.468145] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Aug 22 21:05:07 node-3 kernel: [    0.468163] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Aug 22 21:05:07 node-3 kernel: [    0.468241] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.468291] pci 0000:00:1d.0: System wakeup disabled by ACPI
Aug 22 21:05:07 node-3 kernel: [    0.468317] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Aug 22 21:05:07 node-3 kernel: [    0.468566] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Aug 22 21:05:07 node-3 kernel: [    0.468572] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Aug 22 21:05:07 node-3 kernel: [    0.468578] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Aug 22 21:05:07 node-3 kernel: [    0.468584] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Aug 22 21:05:07 node-3 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Aug 22 21:05:07 node-3 kernel: [    0.468591] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Aug 22 21:05:07 node-3 kernel: [    0.468622] pci 0000:01:00.0: supports D1 D2
Aug 22 21:05:07 node-3 kernel: [    0.478160] pci 0000:00:01.0: PCI bridge to [bus 01]
Aug 22 21:05:07 node-3 kernel: [    0.478163] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Aug 22 21:05:07 node-3 kernel: [    0.478165] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Aug 22 21:05:07 node-3 kernel: [    0.478273] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.478306] pci 0000:02:00.0: PME# supported from D0 D3hot
Aug 22 21:05:07 node-3 kernel: [    0.486166] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Aug 22 21:05:07 node-3 kernel: [    0.486172] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.486176] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 22 21:05:07 node-3 kernel: [    0.486269] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.486337] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Aug 22 21:05:07 node-3 kernel: [    0.486413] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.486459] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Aug 22 21:05:07 node-3 kernel: [    0.486462] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.486464] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 22 21:05:07 node-3 kernel: [    0.486517] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.486639] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.486693] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Aug 22 21:05:07 node-3 kernel: [    0.486696] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.486698] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 22 21:05:07 node-3 kernel: [    0.486747] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.486866] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.486905] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.487026] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.487063] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.487200] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.487237] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Aug 22 21:05:07 node-3 kernel: [    0.487356] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Aug 22 21:05:07 node-3 kernel: [    0.487400] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Aug 22 21:05:07 node-3 kernel: [    0.487403] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.487405] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 22 21:05:07 node-3 kernel: [    0.487465] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Aug 22 21:05:07 node-3 kernel: [    0.487528] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Aug 22 21:05:07 node-3 kernel: [    0.487580] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Aug 22 21:05:07 node-3 kernel: [    0.487621] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Aug 22 21:05:07 node-3 kernel: [    0.487703] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Aug 22 21:05:07 node-3 kernel: [    0.487810] pci 0000:05:00.0: PCI bridge to [bus 06]
Aug 22 21:05:07 node-3 kernel: [    0.487813] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.487815] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Aug 22 21:05:07 node-3 kernel: [    0.487870] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Aug 22 21:05:07 node-3 kernel: [    0.487924] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Aug 22 21:05:07 node-3 kernel: [    0.487975] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Aug 22 21:05:07 node-3 kernel: [    0.488209] pci 0000:05:01.0: PCI bridge to [bus 07]
Aug 22 21:05:07 node-3 kernel: [    0.488213] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Aug 22 21:05:07 node-3 kernel: [    0.488281] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Aug 22 21:05:07 node-3 kernel: [    0.488339] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Aug 22 21:05:07 node-3 kernel: [    0.488386] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Aug 22 21:05:07 node-3 kernel: [    0.488602] pci 0000:05:02.0: PCI bridge to [bus 08]
Aug 22 21:05:07 node-3 kernel: [    0.488606] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Aug 22 21:05:07 node-3 kernel: [    0.488671] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Aug 22 21:05:07 node-3 kernel: [    0.488735] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Aug 22 21:05:07 node-3 kernel: [    0.488787] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Aug 22 21:05:07 node-3 kernel: [    0.489011] pci 0000:05:03.0: PCI bridge to [bus 09]
Aug 22 21:05:07 node-3 kernel: [    0.489014] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Aug 22 21:05:07 node-3 kernel: [    0.489192] pci 0000:00:03.0: PCI bridge to [bus 0a]
Aug 22 21:05:07 node-3 kernel: [    0.489230] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Aug 22 21:05:07 node-3 kernel: [    0.489308] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Aug 22 21:05:07 node-3 kernel: [    0.489327] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Aug 22 21:05:07 node-3 kernel: [    0.489340] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Aug 22 21:05:07 node-3 kernel: [    0.489353] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Aug 22 21:05:07 node-3 kernel: [    0.489403] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Aug 22 21:05:07 node-3 kernel: [    0.494170] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Aug 22 21:05:07 node-3 kernel: [    0.494179] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Aug 22 21:05:07 node-3 kernel: [    0.494231] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Aug 22 21:05:07 node-3 kernel: [    0.494837] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Aug 22 21:05:07 node-3 kernel: [    0.494840] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Aug 22 21:05:07 node-3 kernel: [    0.494960] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Aug 22 21:05:07 node-3 kernel: [    0.495083] PCI host bridge to bus 0000:80
Aug 22 21:05:07 node-3 kernel: [    0.495085] pci_bus 0000:80: root bus resource [bus 80-fe]
Aug 22 21:05:07 node-3 kernel: [    0.495087] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Aug 22 21:05:07 node-3 kernel: [    0.495088] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Aug 22 21:05:07 node-3 kernel: [    0.495096] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.495161] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.495229] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Aug 22 21:05:07 node-3 kernel: [    0.495292] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Aug 22 21:05:07 node-3 kernel: [    0.495298] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Aug 22 21:05:07 node-3 kernel: [    0.495369] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Aug 22 21:05:07 node-3 kernel: [    0.495665] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Aug 22 21:05:07 node-3 kernel: [    0.495697] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Aug 22 21:05:07 node-3 kernel: [    0.495727] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Aug 22 21:05:07 node-3 kernel: [    0.495756] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Aug 22 21:05:07 node-3 kernel: [    0.495785] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 22 21:05:07 node-3 kernel: [    0.495815] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 22 21:05:07 node-3 kernel: [    0.495845] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 22 21:05:07 node-3 kernel: [    0.495875] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Aug 22 21:05:07 node-3 kernel: [    0.495960] ACPI: Enabled 3 GPEs in block 00 to 3F
Aug 22 21:05:07 node-3 kernel: [    0.495964] ACPI: \_SB_.UNC1: notify handler is installed
Aug 22 21:05:07 node-3 kernel: [    0.495966] ACPI: \_SB_.UNC0: notify handler is installed
Aug 22 21:05:07 node-3 kernel: [    0.495981] ACPI: \_SB_.PCI0: notify handler is installed
Aug 22 21:05:07 node-3 kernel: [    0.496034] ACPI: \_SB_.PCI1: notify handler is installed
Aug 22 21:05:07 node-3 kernel: [    0.496113] Found 4 acpi root devices
Aug 22 21:05:07 node-3 kernel: [    0.496223] vgaarb: setting as boot device: PCI:0000:0c:00.0
Aug 22 21:05:07 node-3 kernel: [    0.496225] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Aug 22 21:05:07 node-3 kernel: [    0.496227] vgaarb: loaded
Aug 22 21:05:07 node-3 kernel: [    0.496228] vgaarb: bridge control possible 0000:0c:00.0
Aug 22 21:05:07 node-3 kernel: [    0.496352] SCSI subsystem initialized
Aug 22 21:05:07 node-3 kernel: [    0.496417] libata version 3.00 loaded.
Aug 22 21:05:07 node-3 kernel: [    0.496433] ACPI: bus type USB registered
Aug 22 21:05:07 node-3 kernel: [    0.496443] usbcore: registered new interface driver usbfs
Aug 22 21:05:07 node-3 kernel: [    0.496448] usbcore: registered new interface driver hub
Aug 22 21:05:07 node-3 kernel: [    0.496473] usbcore: registered new device driver usb
Aug 22 21:05:07 node-3 kernel: [    0.496647] PCI: Using ACPI for IRQ routing
Aug 22 21:05:07 node-3 kernel: [    0.500248] PCI: pci_cache_line_size set to 64 bytes
Aug 22 21:05:07 node-3 kernel: [    0.500454] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Aug 22 21:05:07 node-3 kernel: [    0.500455] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Aug 22 21:05:07 node-3 kernel: [    0.500456] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Aug 22 21:05:07 node-3 kernel: [    0.500522] NetLabel: Initializing
Aug 22 21:05:07 node-3 kernel: [    0.500524] NetLabel:  domain hash size = 128
Aug 22 21:05:07 node-3 kernel: [    0.500524] NetLabel:  protocols = UNLABELED CIPSOv4
Aug 22 21:05:07 node-3 kernel: [    0.500534] NetLabel:  unlabeled traffic allowed by default
Aug 22 21:05:07 node-3 kernel: [    0.500591] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Aug 22 21:05:07 node-3 kernel: [    0.500596] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Aug 22 21:05:07 node-3 kernel: [    0.502655] Switched to clocksource hpet
Aug 22 21:05:07 node-3 kernel: [    0.506712] AppArmor: AppArmor Filesystem Enabled
Aug 22 21:05:07 node-3 kernel: [    0.506725] pnp: PnP ACPI init
Aug 22 21:05:07 node-3 kernel: [    0.506732] ACPI: bus type PNP registered
Aug 22 21:05:07 node-3 kernel: [    0.506843] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Aug 22 21:05:07 node-3 kernel: [    0.506851] pnp 00:01: [dma 4]
Aug 22 21:05:07 node-3 kernel: [    0.506862] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Aug 22 21:05:07 node-3 kernel: [    0.506890] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Aug 22 21:05:07 node-3 kernel: [    0.506910] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Aug 22 21:05:07 node-3 kernel: [    0.506928] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Aug 22 21:05:07 node-3 kernel: [    0.506961] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Aug 22 21:05:07 node-3 kernel: [    0.507015] system 00:06: [io  0x0500-0x057f] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507017] system 00:06: [io  0x0400-0x047f] could not be reserved
Aug 22 21:05:07 node-3 kernel: [    0.507019] system 00:06: [io  0x0580-0x059f] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507021] system 00:06: [io  0x0600-0x061f] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507022] system 00:06: [io  0x0880-0x0883] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507027] system 00:06: [io  0x0800-0x081f] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507029] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Aug 22 21:05:07 node-3 kernel: [    0.507031] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507032] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507034] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507035] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507037] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507038] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Aug 22 21:05:07 node-3 kernel: [    0.507040] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Aug 22 21:05:07 node-3 kernel: [    0.507124] pnp 00:07: [dma 0 disabled]
Aug 22 21:05:07 node-3 kernel: [    0.507153] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Aug 22 21:05:07 node-3 kernel: [    0.507228] pnp 00:08: [dma 0 disabled]
Aug 22 21:05:07 node-3 kernel: [    0.507261] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Aug 22 21:05:07 node-3 kernel: [    0.507312] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Aug 22 21:05:07 node-3 kernel: [    0.507677] pnp: PnP ACPI: found 10 devices
Aug 22 21:05:07 node-3 kernel: [    0.507679] ACPI: bus type PNP unregistered
Aug 22 21:05:07 node-3 kernel: [    0.514031] pci 0000:00:01.0: PCI bridge to [bus 01]
Aug 22 21:05:07 node-3 kernel: [    0.514034] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Aug 22 21:05:07 node-3 kernel: [    0.514037] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Aug 22 21:05:07 node-3 kernel: [    0.514041] pci 0000:05:00.0: PCI bridge to [bus 06]
Aug 22 21:05:07 node-3 kernel: [    0.514043] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.514057] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514086] pci 0000:05:01.0: PCI bridge to [bus 07]
Aug 22 21:05:07 node-3 kernel: [    0.514101] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514129] pci 0000:05:02.0: PCI bridge to [bus 08]
Aug 22 21:05:07 node-3 kernel: [    0.514144] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Aug 22 21:05:07 node-3 kernel: [    0.514187] pci 0000:05:03.0: PCI bridge to [bus 09]
Aug 22 21:05:07 node-3 kernel: [    0.514201] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Aug 22 21:05:07 node-3 kernel: [    0.514230] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Aug 22 21:05:07 node-3 kernel: [    0.514232] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.514247] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514276] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Aug 22 21:05:07 node-3 kernel: [    0.514278] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.514293] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514321] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Aug 22 21:05:07 node-3 kernel: [    0.514323] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.514326] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514330] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Aug 22 21:05:07 node-3 kernel: [    0.514332] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.514334] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514338] pci 0000:00:03.0: PCI bridge to [bus 0a]
Aug 22 21:05:07 node-3 kernel: [    0.514342] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Aug 22 21:05:07 node-3 kernel: [    0.514350] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Aug 22 21:05:07 node-3 kernel: [    0.514354] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Aug 22 21:05:07 node-3 kernel: [    0.514360] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Aug 22 21:05:07 node-3 kernel: [    0.514361] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Aug 22 21:05:07 node-3 kernel: [    0.514362] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Aug 22 21:05:07 node-3 kernel: [    0.514363] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Aug 22 21:05:07 node-3 kernel: [    0.514364] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Aug 22 21:05:07 node-3 kernel: [    0.514365] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Aug 22 21:05:07 node-3 kernel: [    0.514366] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Aug 22 21:05:07 node-3 kernel: [    0.514367] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Aug 22 21:05:07 node-3 kernel: [    0.514368] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.514368] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514369] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.514370] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514371] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.514372] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514373] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.514374] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514375] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Aug 22 21:05:07 node-3 kernel: [    0.514376] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514377] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Aug 22 21:05:07 node-3 kernel: [    0.514378] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Aug 22 21:05:07 node-3 kernel: [    0.514379] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Aug 22 21:05:07 node-3 kernel: [    0.514380] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Aug 22 21:05:07 node-3 kernel: [    0.514382] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Aug 22 21:05:07 node-3 kernel: [    0.514383] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Aug 22 21:05:07 node-3 kernel: [    0.514424] NET: Registered protocol family 2
Aug 22 21:05:07 node-3 kernel: [    0.514691] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.515020] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.515165] TCP: Hash tables configured (established 262144 bind 65536)
Aug 22 21:05:07 node-3 kernel: [    0.515209] TCP: reno registered
Aug 22 21:05:07 node-3 kernel: [    0.515240] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.515335] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.515484] NET: Registered protocol family 1
Aug 22 21:05:07 node-3 kernel: [    0.550690] pci 0000:0c:00.0: Video device with shadowed ROM
Aug 22 21:05:07 node-3 kernel: [    0.550698] PCI: CLS 64 bytes, default 64
Aug 22 21:05:07 node-3 kernel: [    0.550739] Trying to unpack rootfs image as initramfs...
Aug 22 21:05:07 node-3 kernel: [    0.770808] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Aug 22 21:05:07 node-3 kernel: [    0.770852] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Aug 22 21:05:07 node-3 kernel: [    0.770855] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Aug 22 21:05:07 node-3 kernel: [    0.771270] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771276] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771281] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771286] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771298] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771315] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771330] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771353] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771361] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771370] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771376] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771382] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771389] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771397] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771404] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771412] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Aug 22 21:05:07 node-3 kernel: [    0.771457] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Aug 22 21:05:07 node-3 kernel: [    0.771460] Scanning for low memory corruption every 60 seconds
Aug 22 21:05:07 node-3 kernel: [    0.771756] Initialise system trusted keyring
Aug 22 21:05:07 node-3 kernel: [    0.771801] audit: initializing netlink socket (disabled)
Aug 22 21:05:07 node-3 kernel: [    0.771811] type=2000 audit(1471899870.724:1): initialized
Aug 22 21:05:07 node-3 kernel: [    0.789628] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Aug 22 21:05:07 node-3 kernel: [    0.791090] zbud: loaded
Aug 22 21:05:07 node-3 kernel: [    0.791215] VFS: Disk quotas dquot_6.5.2
Aug 22 21:05:07 node-3 kernel: [    0.791252] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Aug 22 21:05:07 node-3 kernel: [    0.791620] fuse init (API version 7.22)
Aug 22 21:05:07 node-3 kernel: [    0.791679] msgmni has been set to 32768
Aug 22 21:05:07 node-3 kernel: [    0.791727] Key type big_key registered
Aug 22 21:05:07 node-3 kernel: [    0.792230] Key type asymmetric registered
Aug 22 21:05:07 node-3 kernel: [    0.792231] Asymmetric key parser 'x509' registered
Aug 22 21:05:07 node-3 kernel: [    0.792254] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Aug 22 21:05:07 node-3 kernel: [    0.792313] io scheduler noop registered
Aug 22 21:05:07 node-3 kernel: [    0.792315] io scheduler deadline registered (default)
Aug 22 21:05:07 node-3 kernel: [    0.792334] io scheduler cfq registered
Aug 22 21:05:07 node-3 kernel: [    0.792650] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    0.792742] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    0.792831] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    0.792919] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    0.793017] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    0.793085] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    0.793352] aer 0000:00:01.0:pcie02: service driver aer loaded
Aug 22 21:05:07 node-3 kernel: [    0.793370] aer 0000:00:02.0:pcie02: service driver aer loaded
Aug 22 21:05:07 node-3 kernel: [    0.793383] aer 0000:00:03.0:pcie02: service driver aer loaded
Aug 22 21:05:07 node-3 kernel: [    0.793393] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793396] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793398] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Aug 22 21:05:07 node-3 kernel: [    0.793402] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793403] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793405] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793406] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793407] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793409] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793410] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793412] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793413] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793415] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793416] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793418] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793420] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Aug 22 21:05:07 node-3 kernel: [    0.793423] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793425] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Aug 22 21:05:07 node-3 kernel: [    0.793434] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793437] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Aug 22 21:05:07 node-3 kernel: [    0.793446] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793448] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Aug 22 21:05:07 node-3 kernel: [    0.793451] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Aug 22 21:05:07 node-3 kernel: [    0.793464] ioapic: probe of 0000:00:05.4 failed with error -22
Aug 22 21:05:07 node-3 kernel: [    0.793551] ioapic: probe of 0000:80:05.4 failed with error -22
Aug 22 21:05:07 node-3 kernel: [    0.793555] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Aug 22 21:05:07 node-3 kernel: [    0.793564] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Aug 22 21:05:07 node-3 kernel: [    0.793603] vesafb: mode is 640x480x32, linelength=2560, pages=0
Aug 22 21:05:07 node-3 kernel: [    0.793604] vesafb: scrolling: redraw
Aug 22 21:05:07 node-3 kernel: [    0.793606] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Aug 22 21:05:07 node-3 kernel: [    0.814358] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Aug 22 21:05:07 node-3 kernel: [    0.822864] Console: switching to colour frame buffer device 80x30
Aug 22 21:05:07 node-3 kernel: [    0.831547] fb0: VESA VGA frame buffer device
Aug 22 21:05:07 node-3 kernel: [    0.831748] intel_idle: MWAIT substates: 0x2120
Aug 22 21:05:07 node-3 kernel: [    0.831749] intel_idle: v0.4 model 0x3F
Aug 22 21:05:07 node-3 kernel: [    0.831750] intel_idle: lapic_timer_reliable_states 0xffffffff
Aug 22 21:05:07 node-3 kernel: [    0.831987] ipmi message handler version 39.2
Aug 22 21:05:07 node-3 kernel: [    0.832254] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Aug 22 21:05:07 node-3 kernel: [    0.832686] ACPI: AC Adapter [P111] (on-line)
Aug 22 21:05:07 node-3 kernel: [    0.837910] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Aug 22 21:05:07 node-3 kernel: [    0.848968] ACPI: Power Button [PWRB]
Aug 22 21:05:07 node-3 kernel: [    0.854824] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Aug 22 21:05:07 node-3 kernel: [    0.866532] ACPI: Power Button [PWRF]
Aug 22 21:05:07 node-3 kernel: [    0.892285] ERST: Error Record Serialization Table (ERST) support is initialized.
Aug 22 21:05:07 node-3 kernel: [    0.903948] pstore: Registered erst as persistent store backend
Aug 22 21:05:07 node-3 kernel: [    0.910161] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Aug 22 21:05:07 node-3 kernel: [    0.922129] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Aug 22 21:05:07 node-3 kernel: [    0.948892] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Aug 22 21:05:07 node-3 kernel: [    0.982181] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Aug 22 21:05:07 node-3 kernel: [    0.996258] Linux agpgart interface v0.103
Aug 22 21:05:07 node-3 kernel: [    1.003943] brd: module loaded
Aug 22 21:05:07 node-3 kernel: [    1.011008] loop: module loaded
Aug 22 21:05:07 node-3 kernel: [    1.017740] libphy: Fixed MDIO Bus: probed
Aug 22 21:05:07 node-3 kernel: [    1.024215] tun: Universal TUN/TAP device driver, 1.6
Aug 22 21:05:07 node-3 kernel: [    1.030698] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Aug 22 21:05:07 node-3 kernel: [    1.037232] PPP generic driver version 2.4.2
Aug 22 21:05:07 node-3 kernel: [    1.043616] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Aug 22 21:05:07 node-3 kernel: [    1.050053] ehci-pci: EHCI PCI platform driver
Aug 22 21:05:07 node-3 kernel: [    1.056695] ehci-pci 0000:00:1a.0: EHCI Host Controller
Aug 22 21:05:07 node-3 kernel: [    1.063160] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Aug 22 21:05:07 node-3 kernel: [    1.075765] ehci-pci 0000:00:1a.0: debug port 2
Aug 22 21:05:07 node-3 kernel: [    1.085987] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Aug 22 21:05:07 node-3 kernel: [    1.086005] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Aug 22 21:05:07 node-3 kernel: [    1.102150] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Aug 22 21:05:07 node-3 kernel: [    1.108308] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Aug 22 21:05:07 node-3 kernel: [    1.114576] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 22 21:05:07 node-3 kernel: [    1.126676] usb usb1: Product: EHCI Host Controller
Aug 22 21:05:07 node-3 kernel: [    1.132757] usb usb1: Manufacturer: Linux 3.13.0-93-generic ehci_hcd
Aug 22 21:05:07 node-3 kernel: [    1.138843] usb usb1: SerialNumber: 0000:00:1a.0
Aug 22 21:05:07 node-3 kernel: [    1.144802] hub 1-0:1.0: USB hub found
Aug 22 21:05:07 node-3 kernel: [    1.150585] hub 1-0:1.0: 2 ports detected
Aug 22 21:05:07 node-3 kernel: [    1.156384] ehci-pci 0000:00:1d.0: EHCI Host Controller
Aug 22 21:05:07 node-3 kernel: [    1.161979] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Aug 22 21:05:07 node-3 kernel: [    1.172907] ehci-pci 0000:00:1d.0: debug port 2
Aug 22 21:05:07 node-3 kernel: [    1.182213] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Aug 22 21:05:07 node-3 kernel: [    1.182216] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Aug 22 21:05:07 node-3 kernel: [    1.198068] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Aug 22 21:05:07 node-3 kernel: [    1.203277] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Aug 22 21:05:07 node-3 kernel: [    1.208597] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Aug 22 21:05:07 node-3 kernel: [    1.219191] usb usb2: Product: EHCI Host Controller
Aug 22 21:05:07 node-3 kernel: [    1.224660] usb usb2: Manufacturer: Linux 3.13.0-93-generic ehci_hcd
Aug 22 21:05:07 node-3 kernel: [    1.230213] usb usb2: SerialNumber: 0000:00:1d.0
Aug 22 21:05:07 node-3 kernel: [    1.235734] hub 2-0:1.0: USB hub found
Aug 22 21:05:07 node-3 kernel: [    1.241085] hub 2-0:1.0: 2 ports detected
Aug 22 21:05:07 node-3 kernel: [    1.246420] ehci-platform: EHCI generic platform driver
Aug 22 21:05:07 node-3 kernel: [    1.251740] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Aug 22 21:05:07 node-3 kernel: [    1.257162] ohci-pci: OHCI PCI platform driver
Aug 22 21:05:07 node-3 kernel: [    1.262454] ohci-platform: OHCI generic platform driver
Aug 22 21:05:07 node-3 kernel: [    1.267643] uhci_hcd: USB Universal Host Controller Interface driver
Aug 22 21:05:07 node-3 kernel: [    1.272975] i8042: PNP: No PS/2 controller found. Probing ports directly.
Aug 22 21:05:07 node-3 kernel: [    1.469845] usb 1-1: new high-speed USB device number 2 using ehci-pci
Aug 22 21:05:07 node-3 kernel: [    1.630074] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Aug 22 21:05:07 node-3 kernel: [    1.635591] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 22 21:05:07 node-3 kernel: [    1.641337] hub 1-1:1.0: USB hub found
Aug 22 21:05:07 node-3 kernel: [    1.646812] hub 1-1:1.0: 6 ports detected
Aug 22 21:05:07 node-3 kernel: [    1.761589] usb 2-1: new high-speed USB device number 2 using ehci-pci
Aug 22 21:05:07 node-3 kernel: [    1.769597] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Aug 22 21:05:07 node-3 kernel: [    2.029735] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Aug 22 21:05:07 node-3 kernel: [    2.035286] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Aug 22 21:05:07 node-3 kernel: [    2.041129] hub 2-1:1.0: USB hub found
Aug 22 21:05:07 node-3 kernel: [    2.046723] hub 2-1:1.0: 8 ports detected
Aug 22 21:05:07 node-3 kernel: [    2.314350] i8042: No controller found
Aug 22 21:05:07 node-3 kernel: [    2.319751] mousedev: PS/2 mouse device common for all mice
Aug 22 21:05:07 node-3 kernel: [    2.325246] rtc_cmos 00:02: RTC can wake from S4
Aug 22 21:05:07 node-3 kernel: [    2.330815] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Aug 22 21:05:07 node-3 kernel: [    2.333154] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Aug 22 21:05:07 node-3 kernel: [    2.341948] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Aug 22 21:05:07 node-3 kernel: [    2.353060] device-mapper: uevent: version 1.0.3
Aug 22 21:05:07 node-3 kernel: [    2.358688] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Aug 22 21:05:07 node-3 kernel: [    2.369923] ledtrig-cpu: registered to indicate activity on CPUs
Aug 22 21:05:07 node-3 kernel: [    2.375847] TCP: cubic registered
Aug 22 21:05:07 node-3 kernel: [    2.381812] NET: Registered protocol family 10
Aug 22 21:05:07 node-3 kernel: [    2.387795] NET: Registered protocol family 17
Aug 22 21:05:07 node-3 kernel: [    2.393481] Key type dns_resolver registered
Aug 22 21:05:07 node-3 kernel: [    2.399463] Loading compiled-in X.509 certificates
Aug 22 21:05:07 node-3 kernel: [    2.405640] Loaded X.509 cert 'Magrathea: Glacier signing key: d5fcc7f0ec194773d05665948935931e3b1336a9'
Aug 22 21:05:07 node-3 kernel: [    2.417042] registered taskstats version 1
Aug 22 21:05:07 node-3 kernel: [    2.424970] Key type trusted registered
Aug 22 21:05:07 node-3 kernel: [    2.432536] Key type encrypted registered
Aug 22 21:05:07 node-3 kernel: [    2.438008] AppArmor: AppArmor sha1 policy hashing enabled
Aug 22 21:05:07 node-3 kernel: [    2.443519] IMA: No TPM chip found, activating TPM-bypass!
Aug 22 21:05:07 node-3 kernel: [    2.449651] regulator-dummy: disabling
Aug 22 21:05:07 node-3 kernel: [    2.455236]   Magic number: 12:407:96
Aug 22 21:05:07 node-3 kernel: [    2.460810] memory memory249: hash matches
Aug 22 21:05:07 node-3 kernel: [    2.466240] rtc_cmos 00:02: setting system clock to 2016-08-22 21:04:33 UTC (1471899873)
Aug 22 21:05:07 node-3 kernel: [    2.469944] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Aug 22 21:05:07 node-3 kernel: [    2.469946] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Aug 22 21:05:07 node-3 kernel: [    2.469948] usb 2-1.4: Product: Cisco USB Composite Device-0
Aug 22 21:05:07 node-3 kernel: [    2.469949] usb 2-1.4: Manufacturer: Avocent
Aug 22 21:05:07 node-3 kernel: [    2.469951] usb 2-1.4: SerialNumber: 20111102-00000001
Aug 22 21:05:07 node-3 kernel: [    2.512954] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Aug 22 21:05:07 node-3 kernel: [    2.518635] EDD information not available.
Aug 22 21:05:07 node-3 kernel: [    2.524192] PM: Hibernation image not present or could not be loaded.
Aug 22 21:05:07 node-3 kernel: [    2.525059] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Aug 22 21:05:07 node-3 kernel: [    2.536317] Write protecting the kernel read-only data: 12288k
Aug 22 21:05:07 node-3 kernel: [    2.542463] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Aug 22 21:05:07 node-3 kernel: [    2.554863] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Aug 22 21:05:07 node-3 kernel: [    2.587628] device-mapper: multipath: version 1.6.0 loaded
Aug 22 21:05:07 node-3 kernel: [    2.595770] systemd-udevd[214]: starting version 204
Aug 22 21:05:07 node-3 kernel: [    2.619968] md: linear personality registered for level -1
Aug 22 21:05:07 node-3 kernel: [    2.633876] md: multipath personality registered for level -4
Aug 22 21:05:07 node-3 kernel: [    2.641996] md: raid0 personality registered for level 0
Aug 22 21:05:07 node-3 kernel: [    2.650185] md: raid1 personality registered for level 1
Aug 22 21:05:07 node-3 kernel: [    2.659337] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Aug 22 21:05:07 node-3 kernel: [    2.665774] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Aug 22 21:05:07 node-3 kernel: [    2.665681] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Aug 22 21:05:07 node-3 kernel: [    2.684653] hidraw: raw HID events driver (C) Jiri Kosina
Aug 22 21:05:07 node-3 kernel: [    2.685396] megasas: FW now in Ready state
Aug 22 21:05:07 node-3 kernel: [    2.685489] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685531] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685569] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685603] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685647] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685682] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685719] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685756] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685795] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685840] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685875] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685912] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685950] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.685985] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.686021] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.686053] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.686221] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Aug 22 21:05:07 node-3 kernel: [    2.694868] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Aug 22 21:05:07 node-3 kernel: [    2.694869] 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 22 21:05:07 node-3 kernel: [    2.694870] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 22 21:05:07 node-3 kernel: [    2.694922] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.694964] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.695003] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.695025] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.695101] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.707017] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Aug 22 21:05:07 node-3 kernel: [    2.707019] 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 22 21:05:07 node-3 kernel: [    2.707020] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 22 21:05:07 node-3 kernel: [    2.707091] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.707128] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.707166] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.707203] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.707273] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.714902] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Aug 22 21:05:07 node-3 kernel: [    2.714903] 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 22 21:05:07 node-3 kernel: [    2.714904] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 22 21:05:07 node-3 kernel: [    2.714963] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.714996] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.715040] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.715077] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.715162] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.724826] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Aug 22 21:05:07 node-3 kernel: [    2.724827] 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 22 21:05:07 node-3 kernel: [    2.724828] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Aug 22 21:05:07 node-3 kernel: [    2.724912] raid6: sse2x1    1967 MB/s
Aug 22 21:05:07 node-3 kernel: [    2.724923] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.724960] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.724998] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.725035] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.725120] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Aug 22 21:05:07 node-3 kernel: [    2.793011] raid6: sse2x2     708 MB/s
Aug 22 21:05:07 node-3 kernel: [    2.860908] raid6: sse2x4    1614 MB/s
Aug 22 21:05:07 node-3 kernel: [    2.928619] raid6: avx2x1    2990 MB/s
Aug 22 21:05:07 node-3 kernel: [    3.000554] raid6: avx2x2   18870 MB/s
Aug 22 21:05:07 node-3 kernel: [    3.072494] raid6: avx2x4   21403 MB/s
Aug 22 21:05:07 node-3 kernel: [    3.078630] raid6: using algorithm avx2x4 (21403 MB/s)
Aug 22 21:05:07 node-3 kernel: [    3.084906] raid6: using avx2x2 recovery algorithm
Aug 22 21:05:07 node-3 kernel: [    3.091070] megasas:IOC Init cmd success
Aug 22 21:05:07 node-3 kernel: [    3.091073] Switched to clocksource tsc
Aug 22 21:05:07 node-3 kernel: [    3.103758] xor: automatically using best checksumming function:
Aug 22 21:05:07 node-3 kernel: [    3.111925] usbcore: registered new interface driver usbhid
Aug 22 21:05:07 node-3 kernel: [    3.117701] usbhid: USB HID core driver
Aug 22 21:05:07 node-3 kernel: [    3.124376] 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 22 21:05:07 node-3 kernel: [    3.124472] megasas: INIT adapter done
Aug 22 21:05:07 node-3 kernel: [    3.142142] 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 22 21:05:07 node-3 kernel: [    3.148499]    avx       : 35679.000 MB/sec
Aug 22 21:05:07 node-3 kernel: [    3.159765] 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 22 21:05:07 node-3 kernel: [    3.171750] async_tx: api initialized (async)
Aug 22 21:05:07 node-3 kernel: [    3.171829] 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 22 21:05:07 node-3 kernel: [    3.172180] 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 22 21:05:07 node-3 kernel: [    3.172923] 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 22 21:05:07 node-3 kernel: [    3.217964] md: raid6 personality registered for level 6
Aug 22 21:05:07 node-3 kernel: [    3.224095] md: raid5 personality registered for level 5
Aug 22 21:05:07 node-3 kernel: [    3.230005] md: raid4 personality registered for level 4
Aug 22 21:05:07 node-3 kernel: [    3.238904] md: raid10 personality registered for level 10
Aug 22 21:05:07 node-3 kernel: [    3.291468] multipathd (357): /proc/357/oom_adj is deprecated, please use /proc/357/oom_score_adj instead.
Aug 22 21:05:07 node-3 kernel: [    3.292652] megaraid_sas 0000:01:00.0: Controller type: iMR
Aug 22 21:05:07 node-3 kernel: [    3.295501] scsi0 : LSI SAS based MegaRAID driver
Aug 22 21:05:07 node-3 kernel: [    3.303523] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Aug 22 21:05:07 node-3 kernel: [    3.340438] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Aug 22 21:05:07 node-3 kernel: [    3.356112] sd 0:2:0:0: Attached scsi generic sg0 type 0
Aug 22 21:05:07 node-3 kernel: [    3.362691] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Aug 22 21:05:07 node-3 kernel: [    3.375898] sd 0:2:0:0: [sda] Write Protect is off
Aug 22 21:05:07 node-3 kernel: [    3.382363] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Aug 22 21:05:07 node-3 kernel: [    3.382394] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Aug 22 21:05:07 node-3 kernel: [    3.418559]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Aug 22 21:05:07 node-3 kernel: [    3.425389] sd 0:2:0:0: [sda] Attached SCSI disk
Aug 22 21:05:07 node-3 kernel: [    3.550480] random: lvm urandom read with 28 bits of entropy available
Aug 22 21:05:07 node-3 kernel: [    3.675627] bio: create slab <bio-1> at 1
Aug 22 21:05:07 node-3 kernel: [    4.535076] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Aug 22 21:05:07 node-3 kernel: [    5.215633] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Aug 22 21:05:07 node-3 kernel: [    5.249147] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Aug 22 21:05:07 node-3 kernel: [    5.366991] random: nonblocking pool is initialized
Aug 22 21:05:07 node-3 kernel: [    5.409330] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Aug 22 21:05:07 node-3 kernel: [    5.439263] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Aug 22 21:05:07 node-3 kernel: [    5.502896] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Aug 22 21:05:07 node-3 kernel: [    5.670934] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Aug 22 21:05:07 node-3 kernel: [    5.701663] XFS (dm-1): Mounting Filesystem
Aug 22 21:05:07 node-3 kernel: [    5.971389] XFS (dm-1): Ending clean mount
Aug 22 21:05:07 node-3 kernel: [    6.029890] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Aug 22 21:05:07 node-3 kernel: [    6.065034] XFS (dm-2): Mounting Filesystem
Aug 22 21:05:07 node-3 kernel: [    6.140094] XFS (dm-2): Ending clean mount
Aug 22 21:05:07 node-3 kernel: [    6.272982] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Aug 22 21:05:07 node-3 kernel: [    8.006718] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Aug 22 21:05:07 node-3 kernel: [    8.029419] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Aug 22 21:05:07 node-3 kernel: [    8.154456] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Aug 22 21:05:07 node-3 kernel: [    8.154462] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Aug 22 21:05:07 node-3 kernel: [    8.154467] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Aug 22 21:05:07 node-3 kernel: [    8.154471] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Aug 22 21:05:07 node-3 kernel: [    8.203607] systemd-udevd[802]: starting version 204
Aug 22 21:05:07 node-3 kernel: [    8.440559] power_meter ACPI000D:00: Found ACPI power meter.
Aug 22 21:05:07 node-3 kernel: [    8.440570] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Aug 22 21:05:07 node-3 kernel: [    8.470365] IPMI System Interface driver.
Aug 22 21:05:07 node-3 kernel: [    8.470416] ipmi_si: probing via ACPI
Aug 22 21:05:07 node-3 kernel: [    8.470432] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Aug 22 21:05:07 node-3 kernel: [    8.470433] ipmi_si: Adding ACPI-specified kcs state machine
Aug 22 21:05:07 node-3 kernel: [    8.470451] ipmi_si: probing via SMBIOS
Aug 22 21:05:07 node-3 kernel: [    8.470453] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Aug 22 21:05:07 node-3 kernel: [    8.470454] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Aug 22 21:05:07 node-3 kernel: [    8.470456] ipmi_si: probing via SPMI
Aug 22 21:05:07 node-3 kernel: [    8.470457] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Aug 22 21:05:07 node-3 kernel: [    8.470458] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Aug 22 21:05:07 node-3 kernel: [    8.470460] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Aug 22 21:05:07 node-3 kernel: [    8.478941] wmi: Mapper loaded
Aug 22 21:05:07 node-3 kernel: [    8.484644] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Aug 22 21:05:07 node-3 kernel: [    8.492722] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Aug 22 21:05:07 node-3 kernel: [    8.492726] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Aug 22 21:05:07 node-3 kernel: [    8.492729] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Aug 22 21:05:07 node-3 kernel: [    8.492730] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Aug 22 21:05:07 node-3 kernel: [    8.492743] lpc_ich: Resource conflict(s) found affecting gpio_ich
Aug 22 21:05:07 node-3 kernel: [    8.576274] systemd-udevd[846]: renamed network interface eth2 to enp8s0
Aug 22 21:05:07 node-3 kernel: [    8.592269] systemd-udevd[822]: renamed network interface eth1 to enp7s0
Aug 22 21:05:07 node-3 kernel: [    8.628149] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Aug 22 21:05:07 node-3 kernel: [    8.628155] systemd-udevd[843]: renamed network interface eth0 to enp6s0
Aug 22 21:05:07 node-3 kernel: [    8.628156] ipmi_si 00:09: IPMI kcs interface initialized
Aug 22 21:05:07 node-3 kernel: [    8.652166] systemd-udevd[820]: renamed network interface eth3 to enp9s0
Aug 22 21:05:07 node-3 kernel: [    8.976797] type=1400 audit(1471899880.014:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1095 comm="apparmor_parser"
Aug 22 21:05:07 node-3 kernel: [    8.976943] type=1400 audit(1471899880.014:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1095 comm="apparmor_parser"
Aug 22 21:05:07 node-3 kernel: [    8.977066] type=1400 audit(1471899880.014:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1095 comm="apparmor_parser"
Aug 22 21:05:07 node-3 kernel: [    8.977249] type=1400 audit(1471899880.014:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1096 comm="apparmor_parser"
Aug 22 21:05:07 node-3 kernel: [    8.977397] type=1400 audit(1471899880.014:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1096 comm="apparmor_parser"
Aug 22 21:05:07 node-3 kernel: [    8.977529] type=1400 audit(1471899880.014:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1096 comm="apparmor_parser"
Aug 22 21:05:07 node-3 kernel: [    8.981671] type=1400 audit(1471899880.018:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1079 comm="apparmor_parser"
Aug 22 21:05:07 node-3 kernel: [    8.981819] type=1400 audit(1471899880.018:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1079 comm="apparmor_parser"
Aug 22 21:05:07 node-3 kernel: [    8.981946] type=1400 audit(1471899880.018:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1079 comm="apparmor_parser"
Aug 22 21:05:07 node-3 kernel: [    8.985194] type=1400 audit(1471899880.022:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1102 comm="apparmor_parser"
Aug 22 21:05:07 node-3 kernel: [    9.540327] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Aug 22 21:05:07 node-3 kernel: [    9.543048] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Aug 22 21:05:07 node-3 kernel: [    9.746855] enic 0000:06:00.0 enp6s0: Link UP
Aug 22 21:05:07 node-3 kernel: [    9.748264] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Aug 22 21:05:07 node-3 kernel: [    9.748268] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Aug 22 21:05:07 node-3 kernel: [   19.518620] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Aug 22 21:05:08 node-3 failsafe: Failsafe of 120 seconds reached.
Aug 22 21:05:08 node-3 kernel: [   38.218991] init: failsafe main process (8456) killed by TERM signal
Aug 22 21:05:09 node-3 dbus[8497]: [system] AppArmor D-Bus mediation is enabled
Aug 22 21:05:09 node-3 kernel: [   38.419449] audit_printk_skb: 30 callbacks suppressed
Aug 22 21:05:09 node-3 kernel: [   38.419451] type=1400 audit(1471899909.169:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8582 comm="apparmor_parser"
Aug 22 21:05:09 node-3 kernel: [   38.420652] type=1400 audit(1471899909.169:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8581 comm="apparmor_parser"
Aug 22 21:05:09 node-3 kernel: [   38.420656] type=1400 audit(1471899909.169:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8581 comm="apparmor_parser"
Aug 22 21:05:09 node-3 kernel: [   38.420658] type=1400 audit(1471899909.169:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8581 comm="apparmor_parser"
Aug 22 21:05:09 node-3 kernel: [   38.420870] type=1400 audit(1471899909.169:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8581 comm="apparmor_parser"
Aug 22 21:05:09 node-3 kernel: [   38.420872] type=1400 audit(1471899909.169:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8581 comm="apparmor_parser"
Aug 22 21:05:09 node-3 kernel: [   38.420983] type=1400 audit(1471899909.169:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8581 comm="apparmor_parser"
Aug 22 21:05:09 node-3 kernel: [   38.507303] type=1400 audit(1471899909.257:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8584 comm="apparmor_parser"
Aug 22 21:05:09 node-3 anacron[8647]: Anacron 2.3 started on 2016-08-22
Aug 22 21:05:09 node-3 anacron[8647]: Will run job `cron.daily' in 5 min.
Aug 22 21:05:09 node-3 anacron[8647]: Will run job `cron.weekly' in 10 min.
Aug 22 21:05:09 node-3 anacron[8647]: Will run job `cron.monthly' in 15 min.
Aug 22 21:05:09 node-3 anacron[8647]: Jobs will be executed sequentially
Aug 22 21:05:09 node-3 cron[8612]: (CRON) INFO (pidfile fd = 3)
Aug 22 21:05:09 node-3 cron[8672]: (CRON) STARTUP (fork ok)
Aug 22 21:05:09 node-3 multipathd: path checkers start up
Aug 22 21:05:09 node-3 cron[8672]: (CRON) INFO (Running @reboot jobs)
Aug 22 21:05:09 node-3 postfix/master[8793]: daemon started -- version 2.11.0, configuration /etc/postfix
Aug 22 21:05:13 node-3 puppet-agent[8977]: Reopening log files
Aug 22 21:05:15 node-3 puppet-agent[8977]: Could not request certificate: Connection refused - connect(2)
Aug 22 21:05:24 node-3 puppet-user[9185]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Aug 22 21:05:24 node-3 puppet-user[9185]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Aug 22 21:05:25 node-3 puppet-user[9185]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Aug 22 21:05:25 node-3 puppet-user[9185]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Aug 22 21:05:25 node-3 puppet-user[9185]: Finished catalog run in 0.69 seconds
Aug 22 21:05:26 node-3 multipathd: uevent trigger error
Aug 22 21:05:26 node-3 puppet-user[9610]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Aug 22 21:05:27 node-3 puppet-user[9610]: Compiled catalog for node-3.domain.tld in environment production in 0.09 seconds
Aug 22 21:05:27 node-3 puppet-user[9610]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Aug 22 21:05:27 node-3 puppet-user[9610]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Aug 22 21:05:27 node-3 puppet-user[9610]: (/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 22 21:05:27 node-3 puppet-user[9610]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Aug 22 21:05:27 node-3 puppet-user[9610]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Aug 22 21:05:27 node-3 puppet-user[9610]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Aug 22 21:05:27 node-3 puppet-user[9610]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Aug 22 21:05:27 node-3 puppet-user[9610]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Aug 22 21:05:27 node-3 puppet-user[9610]: Finished catalog run in 0.06 seconds
Aug 22 21:05:28 node-3 puppet-user[10101]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Aug 22 21:05:28 node-3 puppet-user[10101]: Compiled catalog for node-3.domain.tld in environment production in 0.07 seconds
Aug 22 21:05:28 node-3 puppet-user[10101]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Aug 22 21:05:28 node-3 puppet-user[10101]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Aug 22 21:05:28 node-3 puppet-user[10101]: Finished catalog run in 0.03 seconds
Aug 22 21:05:30 node-3 puppet-user[10715]: (Scope(Class[main])) MODULAR: configuration_symlink
Aug 22 21:05:30 node-3 puppet-user[10715]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Aug 22 21:05:30 node-3 puppet-user[10715]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Aug 22 21:05:30 node-3 puppet-user[10715]: Finished catalog run in 0.03 seconds
Aug 22 21:05:31 node-3 puppet-user[11169]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Aug 22 21:05:31 node-3 puppet-user[11169]: Compiled catalog for node-3.domain.tld in environment production in 0.18 seconds
Aug 22 21:05:31 node-3 puppet-user[11169]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Aug 22 21:05:33 node-3 puppet-user[11169]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/onos-0.9/]/Exec[rsync /etc/fuel/plugins/onos-0.9/]/returns) executed successfully
Aug 22 21:05:33 node-3 puppet-user[11169]: Finished catalog run in 2.10 seconds
Aug 22 21:05:35 node-3 puppet-user[11710]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Aug 22 21:05:35 node-3 puppet-user[11710]: Compiled catalog for node-3.domain.tld in environment production in 0.21 seconds
Aug 22 21:05:35 node-3 puppet-user[11710]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Aug 22 21:05:35 node-3 puppet-user[11710]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[onos-0.9.0]/Apt::Setting[list-onos-0.9.0]/File[/etc/apt/sources.list.d/onos-0.9.0.list]/ensure) created
Aug 22 21:05:35 node-3 puppet-user[11710]: (/Stage[main]/Apt/File[preferences]/ensure) created
Aug 22 21:05:35 node-3 puppet-user[11710]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Aug 22 21:05:35 node-3 puppet-user[11710]: Finished catalog run in 0.22 seconds
Aug 22 21:05:36 node-3 puppet-user[12199]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Aug 22 21:05:37 node-3 puppet-user[12199]: Compiled catalog for node-3.domain.tld in environment production in 0.15 seconds
Aug 22 21:05:37 node-3 puppet-user[12199]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Aug 22 21:05:37 node-3 kernel: [   66.485282] nr_pdflush_threads exported in /proc is scheduled for removal
Aug 22 21:05:37 node-3 kernel: [   66.485330] 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 22 21:05:37 node-3 puppet-user[12199]: (/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 22 21:05:37 node-3 puppet-user[12199]: Finished catalog run in 0.06 seconds
Aug 22 21:05:38 node-3 puppet-user[12663]: (Scope(Class[main])) MODULAR: sync_time
Aug 22 21:05:38 node-3 puppet-user[12663]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Aug 22 21:05:39 node-3 ntpdate[13080]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Aug 22 21:05:39 node-3 kernel: [   69.027056] init: plymouth-upstart-bridge main process ended, respawning
Aug 22 21:05:40 node-3 puppet-agent[8977]: Could not run: SIGTERM
Aug 22 21:05:40 node-3 kernel: [   69.340918] ip_tables: (C) 2000-2006 Netfilter Core Team
Aug 22 21:05:40 node-3 ec2: 
Aug 22 21:05:40 node-3 ec2: #############################################################
Aug 22 21:05:40 node-3 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Aug 22 21:05:40 node-3 ec2: 1024 5e:fd:94:ac:0b:85:f0:7f:43:0f:8b:49:2e:04:35:ae  root@node-3.domain.tld (DSA)
Aug 22 21:05:40 node-3 ec2: 256 d3:c9:ca:6e:e8:91:1c:8c:c8:60:1d:8d:02:f7:dc:01  root@node-3.domain.tld (ECDSA)
Aug 22 21:05:40 node-3 ec2: 256 67:43:3b:34:5f:9d:2d:6f:b7:d4:f3:3f:9a:cb:d9:2b  root@node-3.domain.tld (ED25519)
Aug 22 21:05:40 node-3 ec2: 2048 83:82:16:d0:d7:0a:7f:28:ce:78:04:2a:2a:cf:a7:cd  root@node-3.domain.tld (RSA)
Aug 22 21:05:40 node-3 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Aug 22 21:05:40 node-3 ec2: #############################################################
Aug 22 21:05:45 node-3 ntpdate[13080]: adjust time server 10.20.0.2 offset 0.001696 sec
Aug 22 21:05:45 node-3 puppet-user[12663]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Aug 22 21:05:45 node-3 puppet-user[12663]: Finished catalog run in 6.18 seconds
Aug 22 21:05:52 node-3 puppet-user[13452]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Aug 22 21:05:52 node-3 puppet-user[13452]: Compiled catalog for node-3.domain.tld in environment production in 0.09 seconds
Aug 22 21:05:52 node-3 puppet-user[13452]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Aug 22 21:05:52 node-3 puppet-user[13452]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Aug 22 21:05:52 node-3 puppet-user[13452]: Finished catalog run in 0.07 seconds
Aug 22 21:05:53 node-3 puppet-user[13907]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Aug 22 21:05:54 node-3 puppet-user[13907]: Compiled catalog for node-3.domain.tld in environment production in 1.01 seconds
Aug 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Aug 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Aug 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:05:55 node-3 puppet-user[13907]: (/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 22 21:06:01 node-3 CRON[14587]: (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 22 21:06:15 node-3 puppet-user[13907]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Aug 22 21:06:15 node-3 puppet-user[13907]: Finished catalog run in 20.27 seconds
Aug 22 21:06:17 node-3 puppet-user[14953]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Aug 22 21:06:17 node-3 puppet-user[14953]: Compiled catalog for node-3.domain.tld in environment production in 0.15 seconds
Aug 22 21:06:22 node-3 puppet-user[14953]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Aug 22 21:06:24 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 22 21:06:24 node-3 nailgun-agent: I, [2016-08-22T21:06:24.683522 #14590]  INFO -- : API URL is https://10.20.0.2:8443/api
Aug 22 21:06:37 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 22 21:06:37 node-3 nailgun-agent: I, [2016-08-22T21:06:37.853542 #14590]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Aug 22 21:06:59 node-3 puppet-user[14953]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Aug 22 21:06:59 node-3 puppet-user[14953]: Finished catalog run in 41.63 seconds
Aug 22 21:07:01 node-3 puppet-user[17827]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Aug 22 21:07:01 node-3 puppet-user[17827]: Compiled catalog for node-3.domain.tld in environment production in 0.66 seconds
Aug 22 21:07:01 node-3 CRON[18247]: (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 22 21:07:01 node-3 puppet-user[17827]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Aug 22 21:07:01 node-3 puppet-user[17827]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Aug 22 21:07:01 node-3 puppet-user[17827]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Aug 22 21:07:01 node-3 puppet-user[17827]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Aug 22 21:07:02 node-3 puppet-user[17827]: Finished catalog run in 0.11 seconds
Aug 22 21:07:03 node-3 puppet-user[18293]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Aug 22 21:07:04 node-3 puppet-user[18293]: Compiled catalog for node-3.domain.tld in environment production in 0.94 seconds
Aug 22 21:07:05 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Aug 22 21:07:05 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Aug 22 21:07:05 node-3 crontab[18721]: (root) LIST (root)
Aug 22 21:07:05 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Aug 22 21:07:05 node-3 crontab[18722]: (root) REPLACE (root)
Aug 22 21:07:06 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Aug 22 21:07:06 node-3 nailgun-agent: I, [2016-08-22T21:07:06.035795 #18250]  INFO -- : API URL is https://10.20.0.2:8443/api
Aug 22 21:07:08 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Aug 22 21:07:09 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Aug 22 21:07:09 node-3 puppet-user[18293]: (/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 22 21:07:09 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Aug 22 21:07:10 node-3 puppet-user[18293]: (/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 22 21:07:10 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8429" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Aug 22 21:07:10 node-3 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Aug 22 21:07:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:07:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:07:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:07:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:07:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:07:31 node-3 multipathd: uevent trigger error
<27>Aug 22 21:07:31 node-3 multipathd: uevent trigger error
<27>Aug 22 21:07:31 node-3 multipathd: uevent trigger error
<27>Aug 22 21:07:31 node-3 multipathd: uevent trigger error
<27>Aug 22 21:08:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:08:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:08:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:08:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:08:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:08:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:08:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:06 node-3 ntpdate[2615]: no servers can be used, exiting
<27>Aug 22 21:09:06 node-3 ntpdate[2830]: no servers can be used, exiting
<27>Aug 22 21:09:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:41 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:41 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:41 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:41 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:53 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:53 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:53 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:53 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:09:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:01 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:01 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:01 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:01 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:01 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:01 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:01 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:12 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 22 21:11:12 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 22 21:11:18 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 22 21:11:18 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 22 21:11:24 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 22 21:11:29 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 22 21:11:29 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 22 21:11:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:49 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:50 node-3 multipathd: uevent trigger error
<129>Aug 22 21:11:52 node-3 haproxy[23413]: 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 22 21:11:52 node-3 haproxy[23413]: 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 22 21:11:53 node-3 haproxy[23420]: 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 22 21:11:53 node-3 haproxy[23420]: proxy mysqld has no server available!
<27>Aug 22 21:11:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:11:59 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:01 node-3 haproxy[26062]: 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 22 21:12:01 node-3 haproxy[26062]: 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 22 21:12:02 node-3 haproxy[26069]: 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 22 21:12:02 node-3 haproxy[26069]: proxy mysqld has no server available!
<129>Aug 22 21:12:02 node-3 haproxy[26069]: 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 22 21:12:02 node-3 haproxy[26069]: 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 22 21:12:03 node-3 haproxy[26069]: 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 22 21:12:03 node-3 haproxy[26069]: proxy object-storage has no server available!
<27>Aug 22 21:12:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:04 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:07 node-3 haproxy[27598]: 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 22 21:12:07 node-3 haproxy[27598]: 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 22 21:12:07 node-3 haproxy[27598]: 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 22 21:12:07 node-3 haproxy[27598]: proxy neutron has no server available!
<129>Aug 22 21:12:07 node-3 haproxy[27598]: 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 22 21:12:07 node-3 haproxy[27598]: 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 22 21:12:08 node-3 haproxy[27602]: 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 22 21:12:08 node-3 haproxy[27602]: proxy mysqld has no server available!
<129>Aug 22 21:12:08 node-3 haproxy[27602]: 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 22 21:12:08 node-3 haproxy[27602]: 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 22 21:12:08 node-3 haproxy[27602]: 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 22 21:12:08 node-3 haproxy[27602]: proxy object-storage has no server available!
<27>Aug 22 21:12:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:10 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:12 node-3 haproxy[29026]: 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 22 21:12:12 node-3 haproxy[29026]: 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 22 21:12:12 node-3 haproxy[29026]: 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 22 21:12:12 node-3 haproxy[29026]: proxy keystone-1 has no server available!
<129>Aug 22 21:12:13 node-3 haproxy[29032]: 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 22 21:12:13 node-3 haproxy[29032]: 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 22 21:12:13 node-3 haproxy[29032]: 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 22 21:12:13 node-3 haproxy[29032]: proxy keystone-2 has no server available!
<129>Aug 22 21:12:13 node-3 haproxy[29032]: 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 22 21:12:13 node-3 haproxy[29032]: 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 22 21:12:13 node-3 haproxy[29032]: 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 22 21:12:13 node-3 haproxy[29032]: proxy neutron has no server available!
<129>Aug 22 21:12:13 node-3 haproxy[29032]: 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 22 21:12:13 node-3 haproxy[29032]: 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 22 21:12:14 node-3 haproxy[29032]: 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 22 21:12:14 node-3 haproxy[29032]: proxy mysqld has no server available!
<129>Aug 22 21:12:14 node-3 haproxy[29032]: 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 22 21:12:14 node-3 haproxy[29032]: 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 22 21:12:14 node-3 haproxy[29032]: 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 22 21:12:14 node-3 haproxy[29032]: proxy object-storage has no server available!
<27>Aug 22 21:12:15 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:15 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:15 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:15 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:15 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:15 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:18 node-3 haproxy[30512]: 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 22 21:12:18 node-3 haproxy[30512]: 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 22 21:12:18 node-3 haproxy[30512]: 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 22 21:12:18 node-3 haproxy[30512]: proxy keystone-1 has no server available!
<129>Aug 22 21:12:18 node-3 haproxy[30512]: 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 22 21:12:18 node-3 haproxy[30512]: 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 22 21:12:18 node-3 haproxy[30512]: 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 22 21:12:18 node-3 haproxy[30512]: proxy keystone-2 has no server available!
<129>Aug 22 21:12:18 node-3 haproxy[30512]: 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 22 21:12:18 node-3 haproxy[30512]: 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 22 21:12:19 node-3 haproxy[30532]: 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 22 21:12:19 node-3 haproxy[30532]: proxy neutron has no server available!
<129>Aug 22 21:12:19 node-3 haproxy[30532]: 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 22 21:12:19 node-3 haproxy[30532]: 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 22 21:12:19 node-3 haproxy[30532]: 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 22 21:12:19 node-3 haproxy[30532]: proxy mysqld has no server available!
<129>Aug 22 21:12:19 node-3 haproxy[30532]: 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 22 21:12:19 node-3 haproxy[30532]: 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 22 21:12:19 node-3 haproxy[30532]: 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 22 21:12:19 node-3 haproxy[30532]: proxy object-storage has no server available!
<129>Aug 22 21:12:19 node-3 haproxy[30532]: 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 22 21:12:19 node-3 haproxy[30532]: 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 22 21:12:20 node-3 haproxy[30532]: 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 22 21:12:20 node-3 haproxy[30532]: proxy aodh has no server available!
<27>Aug 22 21:12:21 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:21 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:21 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:21 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:21 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:21 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:21 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:23 node-3 haproxy[31938]: 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 22 21:12:24 node-3 haproxy[31942]: 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 22 21:12:24 node-3 haproxy[31942]: 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 22 21:12:24 node-3 haproxy[31942]: proxy keystone-1 has no server available!
<129>Aug 22 21:12:24 node-3 haproxy[31942]: 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 22 21:12:24 node-3 haproxy[31942]: 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 22 21:12:24 node-3 haproxy[31942]: 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 22 21:12:24 node-3 haproxy[31942]: proxy keystone-2 has no server available!
<129>Aug 22 21:12:24 node-3 haproxy[31942]: 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 22 21:12:24 node-3 haproxy[31942]: 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 22 21:12:24 node-3 haproxy[31942]: 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 22 21:12:24 node-3 haproxy[31942]: proxy neutron has no server available!
<129>Aug 22 21:12:24 node-3 haproxy[31942]: 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 22 21:12:24 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: proxy mysqld has no server available!
<129>Aug 22 21:12:25 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: proxy object-storage has no server available!
<129>Aug 22 21:12:25 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: proxy aodh has no server available!
<129>Aug 22 21:12:25 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: 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 22 21:12:25 node-3 haproxy[31942]: proxy ceilometer has no server available!
<27>Aug 22 21:12:27 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:27 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:27 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:27 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:27 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:29 node-3 haproxy[885]: 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 22 21:12:29 node-3 haproxy[885]: 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 22 21:12:29 node-3 haproxy[885]: 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 22 21:12:29 node-3 haproxy[885]: proxy keystone-1 has no server available!
<129>Aug 22 21:12:29 node-3 haproxy[885]: 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 22 21:12:30 node-3 haproxy[889]: 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 22 21:12:30 node-3 haproxy[889]: 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 22 21:12:30 node-3 haproxy[889]: proxy keystone-2 has no server available!
<129>Aug 22 21:12:30 node-3 haproxy[889]: 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 22 21:12:30 node-3 haproxy[889]: 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 22 21:12:30 node-3 haproxy[889]: 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 22 21:12:30 node-3 haproxy[889]: proxy neutron has no server available!
<129>Aug 22 21:12:30 node-3 haproxy[889]: 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 22 21:12:30 node-3 haproxy[889]: 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 22 21:12:30 node-3 haproxy[889]: 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 22 21:12:30 node-3 haproxy[889]: proxy mysqld has no server available!
<129>Aug 22 21:12:30 node-3 haproxy[889]: 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 22 21:12:30 node-3 haproxy[889]: 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 22 21:12:31 node-3 haproxy[889]: 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 22 21:12:31 node-3 haproxy[889]: proxy object-storage has no server available!
<129>Aug 22 21:12:31 node-3 haproxy[889]: 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 22 21:12:31 node-3 haproxy[889]: 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 22 21:12:31 node-3 haproxy[889]: 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 22 21:12:31 node-3 haproxy[889]: proxy aodh has no server available!
<129>Aug 22 21:12:31 node-3 haproxy[889]: 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 22 21:12:31 node-3 haproxy[889]: 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 22 21:12:31 node-3 haproxy[889]: 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 22 21:12:31 node-3 haproxy[889]: proxy ceilometer has no server available!
<27>Aug 22 21:12:32 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:32 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:32 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:32 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:32 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:35 node-3 haproxy[2258]: 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 22 21:12:35 node-3 haproxy[2258]: 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 22 21:12:35 node-3 haproxy[2258]: 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 22 21:12:35 node-3 haproxy[2258]: 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 22 21:12:35 node-3 haproxy[2258]: proxy keystone-1 has no server available!
<129>Aug 22 21:12:35 node-3 haproxy[2258]: 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 22 21:12:35 node-3 haproxy[2258]: 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 22 21:12:35 node-3 haproxy[2258]: 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 22 21:12:35 node-3 haproxy[2258]: proxy keystone-2 has no server available!
<129>Aug 22 21:12:35 node-3 haproxy[2258]: 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 22 21:12:35 node-3 haproxy[2258]: 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 22 21:12:35 node-3 haproxy[2258]: 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 22 21:12:35 node-3 haproxy[2258]: proxy neutron has no server available!
<129>Aug 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: proxy mysqld has no server available!
<129>Aug 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: proxy object-storage has no server available!
<129>Aug 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: proxy aodh has no server available!
<129>Aug 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: 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 22 21:12:36 node-3 haproxy[2262]: proxy ceilometer has no server available!
<27>Aug 22 21:12:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:38 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: proxy keystone-1 has no server available!
<129>Aug 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: proxy keystone-2 has no server available!
<129>Aug 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: proxy glance-api has no server available!
<129>Aug 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: proxy glance-glare has no server available!
<129>Aug 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:41 node-3 haproxy[3631]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: proxy neutron has no server available!
<129>Aug 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: proxy glance-registry has no server available!
<129>Aug 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: proxy mysqld has no server available!
<129>Aug 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: proxy object-storage has no server available!
<129>Aug 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: proxy aodh has no server available!
<129>Aug 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: 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 22 21:12:42 node-3 haproxy[3639]: proxy ceilometer has no server available!
<27>Aug 22 21:12:44 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:44 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:44 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:44 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:44 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:46 node-3 haproxy[5034]: 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 22 21:12:46 node-3 haproxy[5034]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: proxy keystone-1 has no server available!
<129>Aug 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: proxy keystone-2 has no server available!
<129>Aug 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: proxy nova-api has no server available!
<129>Aug 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: proxy nova-metadata-api has no server available!
<129>Aug 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: proxy glance-api has no server available!
<129>Aug 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: proxy glance-glare has no server available!
<129>Aug 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:47 node-3 haproxy[5038]: proxy neutron has no server available!
<129>Aug 22 21:12:47 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: proxy glance-registry has no server available!
<129>Aug 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: proxy mysqld has no server available!
<129>Aug 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: proxy object-storage has no server available!
<129>Aug 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: proxy aodh has no server available!
<129>Aug 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: proxy ceilometer has no server available!
<129>Aug 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: 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 22 21:12:48 node-3 haproxy[5038]: proxy nova-novncproxy has no server available!
<27>Aug 22 21:12:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:50 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:52 node-3 haproxy[6360]: 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 22 21:12:52 node-3 haproxy[6360]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: proxy keystone-1 has no server available!
<129>Aug 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: proxy keystone-2 has no server available!
<129>Aug 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: proxy nova-api has no server available!
<129>Aug 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: proxy nova-metadata-api has no server available!
<129>Aug 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: proxy cinder-api has no server available!
<129>Aug 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: proxy glance-api has no server available!
<129>Aug 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: proxy glance-glare has no server available!
<129>Aug 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: 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 22 21:12:53 node-3 haproxy[6365]: proxy neutron has no server available!
<129>Aug 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: proxy glance-registry has no server available!
<129>Aug 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: proxy mysqld has no server available!
<129>Aug 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: proxy object-storage has no server available!
<129>Aug 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: proxy aodh has no server available!
<129>Aug 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: proxy ceilometer has no server available!
<129>Aug 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: 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 22 21:12:54 node-3 haproxy[6365]: proxy nova-novncproxy has no server available!
<27>Aug 22 21:12:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:12:56 node-3 multipathd: uevent trigger error
<129>Aug 22 21:12:58 node-3 haproxy[7756]: 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 22 21:12:58 node-3 haproxy[7756]: 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 22 21:12:58 node-3 haproxy[7756]: 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 22 21:12:58 node-3 haproxy[7756]: 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 22 21:12:58 node-3 haproxy[7756]: proxy keystone-1 has no server available!
<129>Aug 22 21:12:58 node-3 haproxy[7756]: 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 22 21:12:58 node-3 haproxy[7756]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: proxy keystone-2 has no server available!
<129>Aug 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: proxy nova-api has no server available!
<129>Aug 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: proxy nova-metadata-api has no server available!
<129>Aug 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: proxy cinder-api has no server available!
<129>Aug 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: proxy glance-api has no server available!
<129>Aug 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: proxy glance-glare has no server available!
<129>Aug 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: proxy neutron has no server available!
<129>Aug 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: proxy glance-registry has no server available!
<129>Aug 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: proxy mysqld has no server available!
<129>Aug 22 21:12:59 node-3 haproxy[7760]: 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 22 21:12:59 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: proxy object-storage has no server available!
<129>Aug 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: proxy aodh has no server available!
<129>Aug 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: proxy ceilometer has no server available!
<129>Aug 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: proxy heat-api has no server available!
<129>Aug 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: proxy heat-api-cfn has no server available!
<129>Aug 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: proxy heat-api-cloudwatch has no server available!
<129>Aug 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: 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 22 21:13:00 node-3 haproxy[7760]: proxy nova-novncproxy has no server available!
<27>Aug 22 21:13:01 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:02 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:02 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:02 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:02 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:02 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:05 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:05 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:05 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:05 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:05 node-3 multipathd: uevent trigger error
<27>Aug 22 21:13:17 node-3 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Aug 22 21:13:42 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 22 21:13:44 node-3 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Aug 22 21:14:14 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 22 21:14:20 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 22 21:14:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:14:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:14:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:14:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:14:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:14:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:16:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:16:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:16:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:16:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:16:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:07 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:07 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:07 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:07 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:07 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:17 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Aug 22 21:17:31 node-3 apache2_error [Mon Aug 22 21:17:26.165656 2016] [mpm_event:notice] [pid 20329:tid 140475309643648] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Aug 22 21:17:31 node-3 apache2_error [Mon Aug 22 21:17:26.165739 2016] [core:notice] [pid 20329:tid 140475309643648] AH00094: Command line: '/usr/sbin/apache2'
<43>Aug 22 21:17:31 node-3 apache2_error [Mon Aug 22 21:17:29.521633 2016] [mpm_event:notice] [pid 20329:tid 140475309643648] AH00491: caught SIGTERM, shutting down
<43>Aug 22 21:17:31 node-3 apache2_error [Mon Aug 22 21:17:30.617972 2016] [mpm_worker:notice] [pid 20681:tid 140451391043456] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Aug 22 21:17:31 node-3 apache2_error [Mon Aug 22 21:17:30.618026 2016] [core:notice] [pid 20681:tid 140451391043456] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 22 21:17:34 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:34 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:34 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:34 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:34 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:34 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:34 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:17:38 node-3 multipathd: uevent trigger error
<43>Aug 22 21:19:01 node-3 apache2_error [Mon Aug 22 21:18:55.199150 2016] [mpm_worker:notice] [pid 20681:tid 140451391043456] AH00295: caught SIGTERM, shutting down
<43>Aug 22 21:19:01 node-3 apache2_error [Mon Aug 22 21:18:55.963756 2016] [mpm_worker:notice] [pid 3097:tid 139817255298944] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 22 21:19:01 node-3 apache2_error [Mon Aug 22 21:18:55.963785 2016] [core:notice] [pid 3097:tid 139817255298944] AH00094: Command line: '/usr/sbin/apache2'
<43>Aug 22 21:19:41 node-3 apache2_error [Mon Aug 22 21:19:41.871444 2016] [mpm_worker:notice] [pid 3097:tid 139817255298944] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 22 21:19:51 node-3 apache2_error [Mon Aug 22 21:19:42.065352 2016] [mpm_worker:warn] [pid 3097:tid 139817255298944] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 22 21:19:51 node-3 apache2_error [Mon Aug 22 21:19:42.068969 2016] [mpm_worker:notice] [pid 3097:tid 139817255298944] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 22 21:19:51 node-3 apache2_error [Mon Aug 22 21:19:42.068989 2016] [core:notice] [pid 3097:tid 139817255298944] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 22 21:20:18 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 22 21:20:27 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:32 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:32 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:32 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:32 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:32 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:20:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:21:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:22:28 node-3 multipathd: uevent trigger error
<27>Aug 22 21:23:19 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 22 21:23:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:23:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:23:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:23:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:23:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:24:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:24:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:24:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:24:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:24:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:25:40 node-3 multipathd: uevent trigger error
<27>Aug 22 21:25:40 node-3 multipathd: uevent trigger error
<27>Aug 22 21:25:40 node-3 multipathd: uevent trigger error
<27>Aug 22 21:25:40 node-3 multipathd: uevent trigger error
<27>Aug 22 21:25:40 node-3 multipathd: uevent trigger error
<27>Aug 22 21:25:40 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:06 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:06 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:06 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:06 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:06 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:12 node-3 multipathd: uevent trigger error
<27>Aug 22 21:26:29 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 22 21:28:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:28:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:28:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:28:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:28:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:28:52 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:08 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:08 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:08 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:08 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:08 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:08 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:14 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:14 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:14 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:14 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:14 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:14 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:31 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 22 21:29:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:29:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:25 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:25 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:25 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:25 node-3 multipathd: uevent trigger error
<27>Aug 22 21:30:25 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:16 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Aug 22 21:31:16 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Aug 22 21:31:16 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Aug 22 21:31:17 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Aug 22 21:31:17 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Aug 22 21:31:18 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:18 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:18 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:18 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:18 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:18 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:18 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:29 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:29 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:29 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:29 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:29 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:29 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:29 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:31:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:32:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:32:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:32:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:32:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:32:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:32:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:32:33 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 22 21:34:26 node-3 multipathd: uevent trigger error
<27>Aug 22 21:34:26 node-3 multipathd: uevent trigger error
<27>Aug 22 21:34:26 node-3 multipathd: uevent trigger error
<27>Aug 22 21:34:26 node-3 multipathd: uevent trigger error
<27>Aug 22 21:34:26 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:11 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:11 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:11 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:11 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:11 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:11 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:34 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 22 21:35:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:42 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:46 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:46 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:46 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:46 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:46 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:51 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:51 node-3 multipathd: uevent trigger error
<27>Aug 22 21:35:51 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:36:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:38:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:38:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:38:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:38:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:38:03 node-3 multipathd: uevent trigger error
<27>Aug 22 21:38:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:38:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:38:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:38:22 node-3 multipathd: uevent trigger error
<27>Aug 22 21:38:22 node-3 multipathd: uevent trigger error
<11>Aug 22 21:38:35 node-3 liberasurecode[5685]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:35 node-3 liberasurecode[5685]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:35 node-3 liberasurecode[5685]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:35 node-3 liberasurecode[5685]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:35 node-3 liberasurecode[5714]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:35 node-3 liberasurecode[5714]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:35 node-3 liberasurecode[5714]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:35 node-3 liberasurecode[5714]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Aug 22 21:38:35 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<11>Aug 22 21:38:37 node-3 liberasurecode[6184]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:37 node-3 liberasurecode[6184]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:37 node-3 liberasurecode[6184]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:37 node-3 liberasurecode[6184]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8464]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8464]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8464]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8464]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8503]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8503]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8503]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8503]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8546]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8546]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8546]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8546]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8609]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8609]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8609]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8609]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8627]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8627]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8627]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:43 node-3 liberasurecode[8627]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:44 node-3 liberasurecode[8639]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:44 node-3 liberasurecode[8639]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:44 node-3 liberasurecode[8639]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:44 node-3 liberasurecode[8639]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:44 node-3 liberasurecode[8653]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:44 node-3 liberasurecode[8653]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:44 node-3 liberasurecode[8653]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:38:44 node-3 liberasurecode[8653]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Aug 22 21:39:00 node-3 liberasurecode[9425]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:39:00 node-3 liberasurecode[9425]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:39:00 node-3 liberasurecode[9425]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:39:00 node-3 liberasurecode[9425]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Aug 22 21:39:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:39:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:39:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:39:09 node-3 multipathd: uevent trigger error
<27>Aug 22 21:39:09 node-3 multipathd: uevent trigger error
<11>Aug 22 21:40:01 node-3 liberasurecode[19097]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:40:01 node-3 liberasurecode[19097]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:40:01 node-3 liberasurecode[19097]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:40:01 node-3 liberasurecode[19097]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<43>Aug 22 21:40:05 node-3 apache2_error [Mon Aug 22 21:39:56.449722 2016] [mpm_worker:notice] [pid 3097:tid 139817255298944] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 22 21:40:05 node-3 apache2_error [Mon Aug 22 21:39:56.837478 2016] [mpm_worker:warn] [pid 3097:tid 139817255298944] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 22 21:40:05 node-3 apache2_error [Mon Aug 22 21:39:56.841471 2016] [mpm_worker:notice] [pid 3097:tid 139817255298944] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 22 21:40:05 node-3 apache2_error [Mon Aug 22 21:39:56.841486 2016] [core:notice] [pid 3097:tid 139817255298944] AH00094: Command line: '/usr/sbin/apache2'
<43>Aug 22 21:40:35 node-3 apache2_error [Mon Aug 22 21:40:33.860854 2016] [mpm_worker:notice] [pid 3097:tid 139817255298944] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 22 21:40:35 node-3 apache2_error [Mon Aug 22 21:40:34.245992 2016] [mpm_worker:warn] [pid 3097:tid 139817255298944] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 22 21:40:35 node-3 apache2_error [Mon Aug 22 21:40:34.255841 2016] [mpm_worker:notice] [pid 3097:tid 139817255298944] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 22 21:40:35 node-3 apache2_error [Mon Aug 22 21:40:34.255874 2016] [core:notice] [pid 3097:tid 139817255298944] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 22 21:40:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:40:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:40:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:40:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:40:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:40:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:40:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:40:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:40:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:40:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:40:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:23 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:24 node-3 multipathd: uevent trigger error
<43>Aug 22 21:41:25 node-3 apache2_error [Mon Aug 22 21:41:19.764276 2016] [mpm_worker:notice] [pid 3097:tid 139817255298944] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Aug 22 21:41:25 node-3 apache2_error [Mon Aug 22 21:41:19.959739 2016] [mpm_worker:warn] [pid 3097:tid 139817255298944] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Aug 22 21:41:25 node-3 apache2_error [Mon Aug 22 21:41:19.968029 2016] [mpm_worker:notice] [pid 3097:tid 139817255298944] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Aug 22 21:41:25 node-3 apache2_error [Mon Aug 22 21:41:19.968057 2016] [core:notice] [pid 3097:tid 139817255298944] AH00094: Command line: '/usr/sbin/apache2'
<27>Aug 22 21:41:30 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:30 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:30 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:30 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:30 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:30 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:36 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:37 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Aug 22 21:41:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:41:56 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:19 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:26 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:26 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:26 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:26 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:26 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:34 node-3 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Aug 22 21:42:43 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:43 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:43 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:43 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:43 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:48 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:48 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:48 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:48 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:48 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:53 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:53 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:53 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:53 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:53 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:53 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:42:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:24 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:24 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:24 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:24 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:24 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:25 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:30 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 22 21:43:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:37 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:45 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:50 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:43:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:00 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:00 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:00 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:00 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:00 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:04 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:10 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:14 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Aug 22 21:44:14 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Aug 22 21:44:15 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:15 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:15 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:15 node-3 multipathd: uevent trigger error
<27>Aug 22 21:44:15 node-3 multipathd: uevent trigger error
<11>Aug 22 21:45:01 node-3 liberasurecode[26502]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:45:01 node-3 liberasurecode[26502]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:45:01 node-3 liberasurecode[26502]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Aug 22 21:45:01 node-3 liberasurecode[26502]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Aug 22 21:45:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:38 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:47 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:47 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:47 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:47 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:47 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:58 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:59 node-3 multipathd: uevent trigger error
<27>Aug 22 21:45:59 node-3 multipathd: uevent trigger error
<129>Aug 22 21:46:08 node-3 haproxy[32066]: 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 22 21:46:08 node-3 haproxy[32066]: 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 22 21:46:48 node-3 haproxy[32066]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Aug 22 21:46:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:46:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:46:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:46:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:46:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:46:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:46:55 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:00 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:00 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:00 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:01 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:01 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:05 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:05 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:05 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:05 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:05 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:17 node-3 multipathd: uevent trigger error
<27>Aug 22 21:47:17 node-3 multipathd: uevent trigger error
