Jul 31 21:48:58 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8371" x-info="http://www.rsyslog.com"] start
Jul 31 21:48:58 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 31 21:48:58 node-3 rsyslogd: rsyslogd's groupid changed to 104
Jul 31 21:48:58 node-3 rsyslogd: rsyslogd's userid changed to 101
Jul 31 21:48:58 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 31 21:48:58 node-3 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 31 21:48:58 node-3 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 31 21:48:58 node-3 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 31 21:48:58 node-3 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=f816b2d5-c973-4b12-8097-26e007c56e5c nomdmonddf nomdmonisw
Jul 31 21:48:58 node-3 kernel: [    0.000000] KERNEL supported cpus:
Jul 31 21:48:58 node-3 kernel: [    0.000000]   Intel GenuineIntel
Jul 31 21:48:58 node-3 kernel: [    0.000000]   AMD AuthenticAMD
Jul 31 21:48:58 node-3 kernel: [    0.000000]   Centaur CentaurHauls
Jul 31 21:48:58 node-3 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 31 21:48:58 node-3 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 31 21:48:58 node-3 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 31 21:48:58 node-3 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 31 21:48:58 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
Jul 31 21:48:58 node-3 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 31 21:48:58 node-3 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 31 21:48:58 node-3 kernel: [    0.000000] No AGP bridge found
Jul 31 21:48:58 node-3 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 31 21:48:58 node-3 kernel: [    0.000000] MTRR default type: write-back
Jul 31 21:48:58 node-3 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 31 21:48:58 node-3 kernel: [    0.000000]   00000-9FFFF write-back
Jul 31 21:48:58 node-3 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 31 21:48:58 node-3 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 31 21:48:58 node-3 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 31 21:48:58 node-3 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 31 21:48:58 node-3 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 31 21:48:58 node-3 kernel: [    0.000000]   2 disabled
Jul 31 21:48:58 node-3 kernel: [    0.000000]   3 disabled
Jul 31 21:48:58 node-3 kernel: [    0.000000]   4 disabled
Jul 31 21:48:58 node-3 kernel: [    0.000000]   5 disabled
Jul 31 21:48:58 node-3 kernel: [    0.000000]   6 disabled
Jul 31 21:48:58 node-3 kernel: [    0.000000]   7 disabled
Jul 31 21:48:58 node-3 kernel: [    0.000000]   8 disabled
Jul 31 21:48:58 node-3 kernel: [    0.000000]   9 disabled
Jul 31 21:48:58 node-3 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 31 21:48:58 node-3 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 31 21:48:58 node-3 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 31 21:48:58 node-3 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 31 21:48:58 node-3 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 31 21:48:58 node-3 kernel: [    0.000000] Using GB pages for direct mapping
Jul 31 21:48:58 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 31 21:48:58 node-3 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 31 21:48:58 node-3 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 31 21:48:58 node-3 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 31 21:48:58 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 31 21:48:58 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 31 21:48:58 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 31 21:48:58 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 31 21:48:58 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 31 21:48:58 node-3 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 31 21:48:58 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 31 21:48:58 node-3 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 31 21:48:58 node-3 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 31 21:48:58 node-3 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 31 21:48:58 node-3 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 31 21:48:58 node-3 kernel: [    0.000000] Zone ranges:
Jul 31 21:48:58 node-3 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] Movable zone start for each node
Jul 31 21:48:58 node-3 kernel: [    0.000000] Early memory node ranges
Jul 31 21:48:58 node-3 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 31 21:48:58 node-3 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 31 21:48:58 node-3 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 31 21:48:58 node-3 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 31 21:48:58 node-3 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 31 21:48:58 node-3 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 31 21:48:58 node-3 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 31 21:48:58 node-3 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 31 21:48:58 node-3 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 31 21:48:58 node-3 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 31 21:48:58 node-3 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 31 21:48:58 node-3 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 31 21:48:58 node-3 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 31 21:48:58 node-3 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 31 21:48:58 node-3 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 31 21:48:58 node-3 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 31 21:48:58 node-3 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 31 21:48:58 node-3 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 31 21:48:58 node-3 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 31 21:48:58 node-3 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 31 21:48:58 node-3 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 31 21:48:58 node-3 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 31 21:48:58 node-3 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 31 21:48:58 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 
Jul 31 21:48:58 node-3 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 31 21:48:58 node-3 kernel: [    0.000000] Policy zone: Normal
Jul 31 21:48:58 node-3 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=f816b2d5-c973-4b12-8097-26e007c56e5c nomdmonddf nomdmonisw
Jul 31 21:48:58 node-3 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 31 21:48:58 node-3 kernel: [    0.000000] Checking aperture...
Jul 31 21:48:58 node-3 kernel: [    0.000000] No AGP bridge found
Jul 31 21:48:58 node-3 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 31 21:48:58 node-3 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 31 21:48:58 node-3 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 31 21:48:58 node-3 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 31 21:48:58 node-3 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 31 21:48:58 node-3 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 31 21:48:58 node-3 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 31 21:48:58 node-3 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 31 21:48:58 node-3 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 31 21:48:58 node-3 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 31 21:48:58 node-3 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 31 21:48:58 node-3 kernel: [    0.000000] console [tty0] enabled
Jul 31 21:48:58 node-3 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 31 21:48:58 node-3 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 31 21:48:58 node-3 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 31 21:48:58 node-3 kernel: [    0.000000] hpet clockevent registered
Jul 31 21:48:58 node-3 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 31 21:48:58 node-3 kernel: [    0.004000] tsc: Detected 3492.020 MHz processor
Jul 31 21:48:58 node-3 kernel: [    0.000004] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.04 BogoMIPS (lpj=13968080)
Jul 31 21:48:58 node-3 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Jul 31 21:48:58 node-3 kernel: [    0.000045] Security Framework initialized
Jul 31 21:48:58 node-3 kernel: [    0.000064] AppArmor: AppArmor initialized
Jul 31 21:48:58 node-3 kernel: [    0.000065] Yama: becoming mindful.
Jul 31 21:48:58 node-3 kernel: [    0.001456] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.006308] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.008236] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.008263] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.008556] Initializing cgroup subsys memory
Jul 31 21:48:58 node-3 kernel: [    0.008563] Initializing cgroup subsys devices
Jul 31 21:48:58 node-3 kernel: [    0.008565] Initializing cgroup subsys freezer
Jul 31 21:48:58 node-3 kernel: [    0.008567] Initializing cgroup subsys blkio
Jul 31 21:48:58 node-3 kernel: [    0.008569] Initializing cgroup subsys perf_event
Jul 31 21:48:58 node-3 kernel: [    0.008571] Initializing cgroup subsys hugetlb
Jul 31 21:48:58 node-3 kernel: [    0.008590] CPU: Physical Processor ID: 0
Jul 31 21:48:58 node-3 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 31 21:48:58 node-3 kernel: [    0.008591] CPU: Processor Core ID: 0
Jul 31 21:48:58 node-3 kernel: [    0.008595] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 31 21:48:58 node-3 kernel: [    0.008595] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 31 21:48:58 node-3 kernel: [    0.009288] mce: CPU supports 22 MCE banks
Jul 31 21:48:58 node-3 kernel: [    0.009316] CPU0: Thermal monitoring enabled (TM1)
Jul 31 21:48:58 node-3 kernel: [    0.009336] process: using mwait in idle threads
Jul 31 21:48:58 node-3 kernel: [    0.009339] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 31 21:48:58 node-3 kernel: [    0.009339] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 31 21:48:58 node-3 kernel: [    0.009339] tlb_flushall_shift: 6
Jul 31 21:48:58 node-3 kernel: [    0.009429] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 31 21:48:58 node-3 kernel: [    0.010154] ACPI: Core revision 20131115
Jul 31 21:48:58 node-3 kernel: [    0.022841] ACPI: All ACPI Tables successfully acquired
Jul 31 21:48:58 node-3 kernel: [    0.023003] ftrace: allocating 28617 entries in 112 pages
Jul 31 21:48:58 node-3 kernel: [    0.031821] dmar: Host address width 46
Jul 31 21:48:58 node-3 kernel: [    0.031824] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 31 21:48:58 node-3 kernel: [    0.031830] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 31 21:48:58 node-3 kernel: [    0.031831] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 31 21:48:58 node-3 kernel: [    0.031835] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 31 21:48:58 node-3 kernel: [    0.031837] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 31 21:48:58 node-3 kernel: [    0.031838] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 31 21:48:58 node-3 kernel: [    0.031839] dmar: ATSR flags: 0x0
Jul 31 21:48:58 node-3 kernel: [    0.031840] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 31 21:48:58 node-3 kernel: [    0.031841] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 31 21:48:58 node-3 kernel: [    0.031958] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 31 21:48:58 node-3 kernel: [    0.031959] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 31 21:48:58 node-3 kernel: [    0.031960] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 31 21:48:58 node-3 kernel: [    0.031961] HPET id 0 under DRHD base 0xc7ffc000
Jul 31 21:48:58 node-3 kernel: [    0.031962] Your BIOS is broken and requested that x2apic be disabled.
Jul 31 21:48:58 node-3 kernel: [    0.031962] This will slightly decrease performance.
Jul 31 21:48:58 node-3 kernel: [    0.031962] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 31 21:48:58 node-3 kernel: [    0.032394] Enabled IRQ remapping in xapic mode
Jul 31 21:48:58 node-3 kernel: [    0.032395] x2apic not enabled, IRQ remapping is in xapic mode
Jul 31 21:48:58 node-3 kernel: [    0.032398] Switched APIC routing to physical flat.
Jul 31 21:48:58 node-3 kernel: [    0.033017] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 31 21:48:58 node-3 kernel: [    0.072668] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 31 21:48:58 node-3 kernel: [    0.072673] TSC deadline timer enabled
Jul 31 21:48:58 node-3 kernel: [    0.072681] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 31 21:48:58 node-3 kernel: [    0.072687] ... version:                3
Jul 31 21:48:58 node-3 kernel: [    0.072688] ... bit width:              48
Jul 31 21:48:58 node-3 kernel: [    0.072689] ... generic registers:      4
Jul 31 21:48:58 node-3 kernel: [    0.072690] ... value mask:             0000ffffffffffff
Jul 31 21:48:58 node-3 kernel: [    0.072691] ... max period:             0000ffffffffffff
Jul 31 21:48:58 node-3 kernel: [    0.072692] ... fixed-purpose events:   3
Jul 31 21:48:58 node-3 kernel: [    0.072693] ... event mask:             000000070000000f
Jul 31 21:48:58 node-3 kernel: [    0.074132] x86: Booting SMP configuration:
Jul 31 21:48:58 node-3 kernel: [    0.088237] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 31 21:48:58 node-3 kernel: [    0.074134] .... node  #0, CPUs:        #1  #2  #3
Jul 31 21:48:58 node-3 kernel: [    0.116145] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 31 21:48:58 node-3 kernel: [    0.270288] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 31 21:48:58 node-3 kernel: [    0.325905] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 31 21:48:58 node-3 kernel: [    0.382553] x86: Booted up 2 nodes, 16 CPUs
Jul 31 21:48:58 node-3 kernel: [    0.382556] smpboot: Total of 16 processors activated (111756.72 BogoMIPS)
Jul 31 21:48:58 node-3 kernel: [    0.406073] devtmpfs: initialized
Jul 31 21:48:58 node-3 kernel: [    0.409130] EVM: security.selinux
Jul 31 21:48:58 node-3 kernel: [    0.409132] EVM: security.SMACK64
Jul 31 21:48:58 node-3 kernel: [    0.409132] EVM: security.ima
Jul 31 21:48:58 node-3 kernel: [    0.409133] EVM: security.capability
Jul 31 21:48:58 node-3 kernel: [    0.409184] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.409830] pinctrl core: initialized pinctrl subsystem
Jul 31 21:48:58 node-3 kernel: [    0.409890] regulator-dummy: no parameters
Jul 31 21:48:58 node-3 kernel: [    0.409922] RTC time: 21:48:22, date: 07/31/16
Jul 31 21:48:58 node-3 kernel: [    0.409955] NET: Registered protocol family 16
Jul 31 21:48:58 node-3 kernel: [    0.410037] cpuidle: using governor ladder
Jul 31 21:48:58 node-3 kernel: [    0.410038] cpuidle: using governor menu
Jul 31 21:48:58 node-3 kernel: [    0.410073] ACPI: bus type PCI registered
Jul 31 21:48:58 node-3 kernel: [    0.410075] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 31 21:48:58 node-3 kernel: [    0.410119] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 31 21:48:58 node-3 kernel: [    0.410122] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 31 21:48:58 node-3 kernel: [    0.423852] PCI: Using configuration type 1 for base access
Jul 31 21:48:58 node-3 kernel: [    0.424845] bio: create slab <bio-0> at 0
Jul 31 21:48:58 node-3 kernel: [    0.425124] ACPI: Added _OSI(Module Device)
Jul 31 21:48:58 node-3 kernel: [    0.425126] ACPI: Added _OSI(Processor Device)
Jul 31 21:48:58 node-3 kernel: [    0.425127] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 31 21:48:58 node-3 kernel: [    0.425128] ACPI: Added _OSI(Processor Aggregator Device)
Jul 31 21:48:58 node-3 kernel: [    0.437798] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 31 21:48:58 node-3 kernel: [    0.448274] ACPI: Interpreter enabled
Jul 31 21:48:58 node-3 kernel: [    0.448280] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 31 21:48:58 node-3 kernel: [    0.448284] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 31 21:48:58 node-3 kernel: [    0.448286] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 31 21:48:58 node-3 kernel: [    0.448293] ACPI: (supports S0 S4 S5)
Jul 31 21:48:58 node-3 kernel: [    0.448294] ACPI: Using IOAPIC for interrupt routing
Jul 31 21:48:58 node-3 kernel: [    0.448336] HEST: Table parsing has been initialized.
Jul 31 21:48:58 node-3 kernel: [    0.448339] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 31 21:48:58 node-3 kernel: [    0.448892] ACPI: No dock devices found.
Jul 31 21:48:58 node-3 kernel: [    0.460472] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 31 21:48:58 node-3 kernel: [    0.460476] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 21:48:58 node-3 kernel: [    0.460480] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 31 21:48:58 node-3 kernel: [    0.460508] PCI host bridge to bus 0000:ff
Jul 31 21:48:58 node-3 kernel: [    0.460510] pci_bus 0000:ff: root bus resource [bus ff]
Jul 31 21:48:58 node-3 kernel: [    0.460518] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460556] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.460586] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460621] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460650] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.460679] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.460710] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460738] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460768] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460796] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460822] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460849] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460877] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460904] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460930] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460957] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.460984] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461011] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461037] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.461064] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461090] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.461115] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461140] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461169] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.461203] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461234] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461263] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461293] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461323] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461353] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461383] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461413] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461442] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461472] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461502] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461534] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461567] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461597] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461624] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461656] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461688] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461724] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461758] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461790] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461820] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461850] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461879] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461909] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461941] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.461971] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462002] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462030] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462056] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462085] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462113] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462144] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462174] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462231] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 31 21:48:58 node-3 kernel: [    0.462233] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 21:48:58 node-3 kernel: [    0.462236] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 31 21:48:58 node-3 kernel: [    0.462253] PCI host bridge to bus 0000:7f
Jul 31 21:48:58 node-3 kernel: [    0.462255] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 31 21:48:58 node-3 kernel: [    0.462260] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462287] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.462315] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462343] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462365] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.462389] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.462415] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462440] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462463] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462485] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462507] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462530] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462553] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462575] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462605] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462635] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462657] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462682] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462706] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.462731] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462753] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.462775] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462797] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462823] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 31 21:48:58 node-3 kernel: [    0.462855] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462881] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462909] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462937] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462962] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.462988] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463013] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463041] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463065] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463093] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463120] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463147] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463176] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463200] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463224] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463252] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463277] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463303] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463331] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463357] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463382] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463409] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463434] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463460] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463486] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463512] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463541] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463566] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463588] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463612] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463637] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463666] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.463691] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.464933] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 31 21:48:58 node-3 kernel: [    0.464936] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 21:48:58 node-3 kernel: [    0.466053] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 31 21:48:58 node-3 kernel: [    0.466560] PCI host bridge to bus 0000:00
Jul 31 21:48:58 node-3 kernel: [    0.466562] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 31 21:48:58 node-3 kernel: [    0.466564] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 31 21:48:58 node-3 kernel: [    0.466565] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 31 21:48:58 node-3 kernel: [    0.466566] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 31 21:48:58 node-3 kernel: [    0.466568] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 31 21:48:58 node-3 kernel: [    0.466569] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 31 21:48:58 node-3 kernel: [    0.466570] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 31 21:48:58 node-3 kernel: [    0.466579] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 31 21:48:58 node-3 kernel: [    0.466662] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.466693] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.466734] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-3 kernel: [    0.466753] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.466782] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.466822] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-3 kernel: [    0.466839] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.466868] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.466910] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-3 kernel: [    0.466927] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.466997] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.467074] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.467147] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 31 21:48:58 node-3 kernel: [    0.467152] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 31 21:48:58 node-3 kernel: [    0.467235] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 31 21:48:58 node-3 kernel: [    0.467374] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 31 21:48:58 node-3 kernel: [    0.467391] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 31 21:48:58 node-3 kernel: [    0.467469] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.467524] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-3 kernel: [    0.467545] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.467601] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.467644] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-3 kernel: [    0.467670] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.467726] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.467769] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 31 21:48:58 node-3 kernel: [    0.467793] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 31 21:48:58 node-3 kernel: [    0.467810] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 31 21:48:58 node-3 kernel: [    0.467888] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.467937] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 31 21:48:58 node-3 kernel: [    0.467963] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 31 21:48:58 node-3 kernel: [    0.468209] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 31 21:48:58 node-3 kernel: [    0.468215] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 31 21:48:58 node-3 kernel: [    0.468221] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.468226] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.468234] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 31 21:48:58 node-3 kernel: [    0.468264] pci 0000:01:00.0: supports D1 D2
Jul 31 21:48:58 node-3 kernel: [    0.474605] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 31 21:48:58 node-3 kernel: [    0.474611] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 31 21:48:58 node-3 kernel: [    0.474616] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 31 21:48:58 node-3 kernel: [    0.474877] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.474910] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 31 21:48:58 node-3 kernel: [    0.482601] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 31 21:48:58 node-3 kernel: [    0.482607] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.482611] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-3 kernel: [    0.482695] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.482785] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.482883] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.482964] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 31 21:48:58 node-3 kernel: [    0.482971] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.482976] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-3 kernel: [    0.483047] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.483169] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.483222] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 31 21:48:58 node-3 kernel: [    0.483224] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.483226] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-3 kernel: [    0.483275] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.483394] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.483434] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.483553] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.483591] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.483712] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.483749] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 31 21:48:58 node-3 kernel: [    0.483882] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 31 21:48:58 node-3 kernel: [    0.483924] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 31 21:48:58 node-3 kernel: [    0.483927] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.483929] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-3 kernel: [    0.483987] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 31 21:48:58 node-3 kernel: [    0.484049] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.484101] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.484142] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 31 21:48:58 node-3 kernel: [    0.484227] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 31 21:48:58 node-3 kernel: [    0.484332] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 31 21:48:58 node-3 kernel: [    0.484334] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.484336] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 31 21:48:58 node-3 kernel: [    0.484392] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 31 21:48:58 node-3 kernel: [    0.484445] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.484494] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.484705] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 31 21:48:58 node-3 kernel: [    0.484709] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 31 21:48:58 node-3 kernel: [    0.484782] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 31 21:48:58 node-3 kernel: [    0.484839] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.484887] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.485096] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 31 21:48:58 node-3 kernel: [    0.485100] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 31 21:48:58 node-3 kernel: [    0.485158] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 31 21:48:58 node-3 kernel: [    0.485218] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.485273] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 31 21:48:58 node-3 kernel: [    0.485494] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 31 21:48:58 node-3 kernel: [    0.485498] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 31 21:48:58 node-3 kernel: [    0.485671] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 31 21:48:58 node-3 kernel: [    0.485709] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 31 21:48:58 node-3 kernel: [    0.485783] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 31 21:48:58 node-3 kernel: [    0.485802] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 31 21:48:58 node-3 kernel: [    0.485815] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 31 21:48:58 node-3 kernel: [    0.485828] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 31 21:48:58 node-3 kernel: [    0.485878] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 31 21:48:58 node-3 kernel: [    0.490600] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 31 21:48:58 node-3 kernel: [    0.490604] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 31 21:48:58 node-3 kernel: [    0.490636] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 31 21:48:58 node-3 kernel: [    0.491124] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 31 21:48:58 node-3 kernel: [    0.491126] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 31 21:48:58 node-3 kernel: [    0.491250] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 31 21:48:58 node-3 kernel: [    0.491355] PCI host bridge to bus 0000:80
Jul 31 21:48:58 node-3 kernel: [    0.491357] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 31 21:48:58 node-3 kernel: [    0.491359] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 31 21:48:58 node-3 kernel: [    0.491360] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 31 21:48:58 node-3 kernel: [    0.491368] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.491431] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.491498] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 31 21:48:58 node-3 kernel: [    0.491562] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 31 21:48:58 node-3 kernel: [    0.491568] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 31 21:48:58 node-3 kernel: [    0.491641] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 31 21:48:58 node-3 kernel: [    0.491957] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 31 21:48:58 node-3 kernel: [    0.491989] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 31 21:48:58 node-3 kernel: [    0.492018] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 31 21:48:58 node-3 kernel: [    0.492047] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 31 21:48:58 node-3 kernel: [    0.492077] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 21:48:58 node-3 kernel: [    0.492106] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 21:48:58 node-3 kernel: [    0.492136] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 21:48:58 node-3 kernel: [    0.492166] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 31 21:48:58 node-3 kernel: [    0.492252] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 31 21:48:58 node-3 kernel: [    0.492256] ACPI: \_SB_.UNC1: notify handler is installed
Jul 31 21:48:58 node-3 kernel: [    0.492257] ACPI: \_SB_.UNC0: notify handler is installed
Jul 31 21:48:58 node-3 kernel: [    0.492272] ACPI: \_SB_.PCI0: notify handler is installed
Jul 31 21:48:58 node-3 kernel: [    0.492325] ACPI: \_SB_.PCI1: notify handler is installed
Jul 31 21:48:58 node-3 kernel: [    0.492404] Found 4 acpi root devices
Jul 31 21:48:58 node-3 kernel: [    0.492514] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 31 21:48:58 node-3 kernel: [    0.492516] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 31 21:48:58 node-3 kernel: [    0.492517] vgaarb: loaded
Jul 31 21:48:58 node-3 kernel: [    0.492519] vgaarb: bridge control possible 0000:0c:00.0
Jul 31 21:48:58 node-3 kernel: [    0.492631] SCSI subsystem initialized
Jul 31 21:48:58 node-3 kernel: [    0.492707] libata version 3.00 loaded.
Jul 31 21:48:58 node-3 kernel: [    0.492722] ACPI: bus type USB registered
Jul 31 21:48:58 node-3 kernel: [    0.492732] usbcore: registered new interface driver usbfs
Jul 31 21:48:58 node-3 kernel: [    0.492737] usbcore: registered new interface driver hub
Jul 31 21:48:58 node-3 kernel: [    0.492758] usbcore: registered new device driver usb
Jul 31 21:48:58 node-3 kernel: [    0.492920] PCI: Using ACPI for IRQ routing
Jul 31 21:48:58 node-3 kernel: [    0.496548] PCI: pci_cache_line_size set to 64 bytes
Jul 31 21:48:58 node-3 kernel: [    0.496752] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 31 21:48:58 node-3 kernel: [    0.496753] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 31 21:48:58 node-3 kernel: [    0.496754] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 31 21:48:58 node-3 kernel: [    0.496821] NetLabel: Initializing
Jul 31 21:48:58 node-3 kernel: [    0.496822] NetLabel:  domain hash size = 128
Jul 31 21:48:58 node-3 kernel: [    0.496823] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 31 21:48:58 node-3 kernel: [    0.496833] NetLabel:  unlabeled traffic allowed by default
Jul 31 21:48:58 node-3 kernel: [    0.496889] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 31 21:48:58 node-3 kernel: [    0.496893] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 31 21:48:58 node-3 kernel: [    0.498951] Switched to clocksource hpet
Jul 31 21:48:58 node-3 kernel: [    0.502985] AppArmor: AppArmor Filesystem Enabled
Jul 31 21:48:58 node-3 kernel: [    0.502999] pnp: PnP ACPI init
Jul 31 21:48:58 node-3 kernel: [    0.503006] ACPI: bus type PNP registered
Jul 31 21:48:58 node-3 kernel: [    0.503113] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 31 21:48:58 node-3 kernel: [    0.503121] pnp 00:01: [dma 4]
Jul 31 21:48:58 node-3 kernel: [    0.503132] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 31 21:48:58 node-3 kernel: [    0.503159] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 31 21:48:58 node-3 kernel: [    0.503178] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 31 21:48:58 node-3 kernel: [    0.503195] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 31 21:48:58 node-3 kernel: [    0.503228] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 31 21:48:58 node-3 kernel: [    0.503279] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503281] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 31 21:48:58 node-3 kernel: [    0.503283] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503284] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503286] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503290] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503292] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 31 21:48:58 node-3 kernel: [    0.503294] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503295] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503297] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503298] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503300] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503301] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 31 21:48:58 node-3 kernel: [    0.503304] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 31 21:48:58 node-3 kernel: [    0.503386] pnp 00:07: [dma 0 disabled]
Jul 31 21:48:58 node-3 kernel: [    0.503415] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 31 21:48:58 node-3 kernel: [    0.503489] pnp 00:08: [dma 0 disabled]
Jul 31 21:48:58 node-3 kernel: [    0.503520] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 31 21:48:58 node-3 kernel: [    0.503571] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 31 21:48:58 node-3 kernel: [    0.503914] pnp: PnP ACPI: found 10 devices
Jul 31 21:48:58 node-3 kernel: [    0.503916] ACPI: bus type PNP unregistered
Jul 31 21:48:58 node-3 kernel: [    0.510374] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 31 21:48:58 node-3 kernel: [    0.510377] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 31 21:48:58 node-3 kernel: [    0.510380] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 31 21:48:58 node-3 kernel: [    0.510384] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 31 21:48:58 node-3 kernel: [    0.510386] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.510401] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510430] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 31 21:48:58 node-3 kernel: [    0.510444] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510473] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 31 21:48:58 node-3 kernel: [    0.510488] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 31 21:48:58 node-3 kernel: [    0.510520] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 31 21:48:58 node-3 kernel: [    0.510534] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 31 21:48:58 node-3 kernel: [    0.510563] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 31 21:48:58 node-3 kernel: [    0.510565] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.510579] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510608] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 31 21:48:58 node-3 kernel: [    0.510610] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.510625] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510653] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 31 21:48:58 node-3 kernel: [    0.510655] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.510658] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510662] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 31 21:48:58 node-3 kernel: [    0.510664] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.510666] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510670] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 31 21:48:58 node-3 kernel: [    0.510674] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 31 21:48:58 node-3 kernel: [    0.510682] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 31 21:48:58 node-3 kernel: [    0.510686] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 31 21:48:58 node-3 kernel: [    0.510692] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 31 21:48:58 node-3 kernel: [    0.510693] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 31 21:48:58 node-3 kernel: [    0.510694] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 31 21:48:58 node-3 kernel: [    0.510695] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 31 21:48:58 node-3 kernel: [    0.510696] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 31 21:48:58 node-3 kernel: [    0.510697] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 31 21:48:58 node-3 kernel: [    0.510698] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 31 21:48:58 node-3 kernel: [    0.510698] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 31 21:48:58 node-3 kernel: [    0.510699] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.510700] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510701] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.510702] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510703] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.510704] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510705] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.510705] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510706] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 31 21:48:58 node-3 kernel: [    0.510707] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510708] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 31 21:48:58 node-3 kernel: [    0.510709] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 31 21:48:58 node-3 kernel: [    0.510710] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 31 21:48:58 node-3 kernel: [    0.510711] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 31 21:48:58 node-3 kernel: [    0.510713] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 31 21:48:58 node-3 kernel: [    0.510714] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 31 21:48:58 node-3 kernel: [    0.510751] NET: Registered protocol family 2
Jul 31 21:48:58 node-3 kernel: [    0.511025] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.511352] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.511496] TCP: Hash tables configured (established 262144 bind 65536)
Jul 31 21:48:58 node-3 kernel: [    0.511533] TCP: reno registered
Jul 31 21:48:58 node-3 kernel: [    0.511562] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.511658] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.511804] NET: Registered protocol family 1
Jul 31 21:48:58 node-3 kernel: [    0.551019] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 31 21:48:58 node-3 kernel: [    0.551026] PCI: CLS 64 bytes, default 64
Jul 31 21:48:58 node-3 kernel: [    0.551068] Trying to unpack rootfs image as initramfs...
Jul 31 21:48:58 node-3 kernel: [    0.770326] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 31 21:48:58 node-3 kernel: [    0.770381] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 31 21:48:58 node-3 kernel: [    0.770384] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 31 21:48:58 node-3 kernel: [    0.770815] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770822] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770826] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770832] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770841] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770852] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770861] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770870] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770878] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770886] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770893] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770898] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770905] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770914] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770921] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.770928] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 31 21:48:58 node-3 kernel: [    0.771006] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 31 21:48:58 node-3 kernel: [    0.771009] Scanning for low memory corruption every 60 seconds
Jul 31 21:48:58 node-3 kernel: [    0.771421] Initialise system trusted keyring
Jul 31 21:48:58 node-3 kernel: [    0.771476] audit: initializing netlink socket (disabled)
Jul 31 21:48:58 node-3 kernel: [    0.771493] type=2000 audit(1470001701.728:1): initialized
Jul 31 21:48:58 node-3 kernel: [    0.789402] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 31 21:48:58 node-3 kernel: [    0.790908] zbud: loaded
Jul 31 21:48:58 node-3 kernel: [    0.791047] VFS: Disk quotas dquot_6.5.2
Jul 31 21:48:58 node-3 kernel: [    0.791083] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 31 21:48:58 node-3 kernel: [    0.791459] fuse init (API version 7.22)
Jul 31 21:48:58 node-3 kernel: [    0.791515] msgmni has been set to 32768
Jul 31 21:48:58 node-3 kernel: [    0.791567] Key type big_key registered
Jul 31 21:48:58 node-3 kernel: [    0.792091] Key type asymmetric registered
Jul 31 21:48:58 node-3 kernel: [    0.792093] Asymmetric key parser 'x509' registered
Jul 31 21:48:58 node-3 kernel: [    0.792115] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 31 21:48:58 node-3 kernel: [    0.792181] io scheduler noop registered
Jul 31 21:48:58 node-3 kernel: [    0.792183] io scheduler deadline registered (default)
Jul 31 21:48:58 node-3 kernel: [    0.792202] io scheduler cfq registered
Jul 31 21:48:58 node-3 kernel: [    0.792629] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    0.792757] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    0.792873] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    0.792984] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    0.793098] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    0.793194] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    0.793633] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 31 21:48:58 node-3 kernel: [    0.793672] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 31 21:48:58 node-3 kernel: [    0.793699] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 31 21:48:58 node-3 kernel: [    0.793722] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793727] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793733] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 31 21:48:58 node-3 kernel: [    0.793744] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793748] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793751] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793755] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793759] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793763] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793767] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793771] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793774] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793778] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793781] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793785] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793791] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 31 21:48:58 node-3 kernel: [    0.793801] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793806] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 31 21:48:58 node-3 kernel: [    0.793826] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793833] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 31 21:48:58 node-3 kernel: [    0.793852] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793856] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 31 21:48:58 node-3 kernel: [    0.793862] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 31 21:48:58 node-3 kernel: [    0.793910] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 31 21:48:58 node-3 kernel: [    0.793922] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 31 21:48:58 node-3 kernel: [    0.793932] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 31 21:48:58 node-3 kernel: [    0.793964] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 31 21:48:58 node-3 kernel: [    0.794049] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 31 21:48:58 node-3 kernel: [    0.794050] vesafb: scrolling: redraw
Jul 31 21:48:58 node-3 kernel: [    0.794052] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 31 21:48:58 node-3 kernel: [    0.814832] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 31 21:48:58 node-3 kernel: [    0.823355] Console: switching to colour frame buffer device 80x30
Jul 31 21:48:58 node-3 kernel: [    0.832027] fb0: VESA VGA frame buffer device
Jul 31 21:48:58 node-3 kernel: [    0.832229] intel_idle: MWAIT substates: 0x2120
Jul 31 21:48:58 node-3 kernel: [    0.832231] intel_idle: v0.4 model 0x3F
Jul 31 21:48:58 node-3 kernel: [    0.832231] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 31 21:48:58 node-3 kernel: [    0.832463] ipmi message handler version 39.2
Jul 31 21:48:58 node-3 kernel: [    0.832735] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 31 21:48:58 node-3 kernel: [    0.833169] ACPI: AC Adapter [P111] (on-line)
Jul 31 21:48:58 node-3 kernel: [    0.838421] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 31 21:48:58 node-3 kernel: [    0.849469] ACPI: Power Button [PWRB]
Jul 31 21:48:58 node-3 kernel: [    0.855246] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 31 21:48:58 node-3 kernel: [    0.866908] ACPI: Power Button [PWRF]
Jul 31 21:48:58 node-3 kernel: [    0.884456] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 31 21:48:58 node-3 kernel: [    0.896351] pstore: Registered erst as persistent store backend
Jul 31 21:48:58 node-3 kernel: [    0.902642] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 31 21:48:58 node-3 kernel: [    0.914604] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 31 21:48:58 node-3 kernel: [    0.941382] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 31 21:48:58 node-3 kernel: [    0.974745] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 31 21:48:58 node-3 kernel: [    0.988807] Linux agpgart interface v0.103
Jul 31 21:48:58 node-3 kernel: [    0.996457] brd: module loaded
Jul 31 21:48:58 node-3 kernel: [    1.003518] loop: module loaded
Jul 31 21:48:58 node-3 kernel: [    1.010238] libphy: Fixed MDIO Bus: probed
Jul 31 21:48:58 node-3 kernel: [    1.016690] tun: Universal TUN/TAP device driver, 1.6
Jul 31 21:48:58 node-3 kernel: [    1.023166] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 31 21:48:58 node-3 kernel: [    1.029685] PPP generic driver version 2.4.2
Jul 31 21:48:58 node-3 kernel: [    1.036075] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 31 21:48:58 node-3 kernel: [    1.042518] ehci-pci: EHCI PCI platform driver
Jul 31 21:48:58 node-3 kernel: [    1.049047] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 31 21:48:58 node-3 kernel: [    1.055457] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 31 21:48:58 node-3 kernel: [    1.067979] ehci-pci 0000:00:1a.0: debug port 2
Jul 31 21:48:58 node-3 kernel: [    1.078174] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 31 21:48:58 node-3 kernel: [    1.078192] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 31 21:48:58 node-3 kernel: [    1.094449] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 31 21:48:58 node-3 kernel: [    1.100517] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 31 21:48:58 node-3 kernel: [    1.106689] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 21:48:58 node-3 kernel: [    1.118593] usb usb1: Product: EHCI Host Controller
Jul 31 21:48:58 node-3 kernel: [    1.124634] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 31 21:48:58 node-3 kernel: [    1.130681] usb usb1: SerialNumber: 0000:00:1a.0
Jul 31 21:48:58 node-3 kernel: [    1.136636] hub 1-0:1.0: USB hub found
Jul 31 21:48:58 node-3 kernel: [    1.142436] hub 1-0:1.0: 2 ports detected
Jul 31 21:48:58 node-3 kernel: [    1.148226] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 31 21:48:58 node-3 kernel: [    1.153785] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 31 21:48:58 node-3 kernel: [    1.164650] ehci-pci 0000:00:1d.0: debug port 2
Jul 31 21:48:58 node-3 kernel: [    1.173947] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 31 21:48:58 node-3 kernel: [    1.173950] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 31 21:48:58 node-3 kernel: [    1.190367] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 31 21:48:58 node-3 kernel: [    1.195549] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 31 21:48:58 node-3 kernel: [    1.200840] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 31 21:48:58 node-3 kernel: [    1.211398] usb usb2: Product: EHCI Host Controller
Jul 31 21:48:58 node-3 kernel: [    1.216843] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 31 21:48:58 node-3 kernel: [    1.222376] usb usb2: SerialNumber: 0000:00:1d.0
Jul 31 21:48:58 node-3 kernel: [    1.227876] hub 2-0:1.0: USB hub found
Jul 31 21:48:58 node-3 kernel: [    1.233209] hub 2-0:1.0: 2 ports detected
Jul 31 21:48:58 node-3 kernel: [    1.238487] ehci-platform: EHCI generic platform driver
Jul 31 21:48:58 node-3 kernel: [    1.243706] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 31 21:48:58 node-3 kernel: [    1.248999] ohci-pci: OHCI PCI platform driver
Jul 31 21:48:58 node-3 kernel: [    1.254282] ohci-platform: OHCI generic platform driver
Jul 31 21:48:58 node-3 kernel: [    1.259461] uhci_hcd: USB Universal Host Controller Interface driver
Jul 31 21:48:58 node-3 kernel: [    1.264778] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 31 21:48:58 node-3 kernel: [    1.458146] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 31 21:48:58 node-3 kernel: [    1.630344] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 31 21:48:58 node-3 kernel: [    1.635848] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 21:48:58 node-3 kernel: [    1.641612] hub 1-1:1.0: USB hub found
Jul 31 21:48:58 node-3 kernel: [    1.647079] hub 1-1:1.0: 6 ports detected
Jul 31 21:48:58 node-3 kernel: [    1.761882] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 31 21:48:58 node-3 kernel: [    1.766299] tsc: Refined TSC clocksource calibration: 3491.889 MHz
Jul 31 21:48:58 node-3 kernel: [    2.030007] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 31 21:48:58 node-3 kernel: [    2.035544] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 31 21:48:58 node-3 kernel: [    2.041399] hub 2-1:1.0: USB hub found
Jul 31 21:48:58 node-3 kernel: [    2.047117] hub 2-1:1.0: 8 ports detected
Jul 31 21:48:58 node-3 kernel: [    2.306207] i8042: No controller found
Jul 31 21:48:58 node-3 kernel: [    2.311624] mousedev: PS/2 mouse device common for all mice
Jul 31 21:48:58 node-3 kernel: [    2.317131] rtc_cmos 00:02: RTC can wake from S4
Jul 31 21:48:58 node-3 kernel: [    2.322720] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 31 21:48:58 node-3 kernel: [    2.325474] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 31 21:48:58 node-3 kernel: [    2.333858] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 31 21:48:58 node-3 kernel: [    2.344962] device-mapper: uevent: version 1.0.3
Jul 31 21:48:58 node-3 kernel: [    2.350623] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 31 21:48:58 node-3 kernel: [    2.361856] ledtrig-cpu: registered to indicate activity on CPUs
Jul 31 21:48:58 node-3 kernel: [    2.367792] TCP: cubic registered
Jul 31 21:48:58 node-3 kernel: [    2.373688] NET: Registered protocol family 10
Jul 31 21:48:58 node-3 kernel: [    2.379674] NET: Registered protocol family 17
Jul 31 21:48:58 node-3 kernel: [    2.385366] Key type dns_resolver registered
Jul 31 21:48:58 node-3 kernel: [    2.391324] Loading compiled-in X.509 certificates
Jul 31 21:48:58 node-3 kernel: [    2.397499] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 31 21:48:58 node-3 kernel: [    2.408901] registered taskstats version 1
Jul 31 21:48:58 node-3 kernel: [    2.416836] Key type trusted registered
Jul 31 21:48:58 node-3 kernel: [    2.424393] Key type encrypted registered
Jul 31 21:48:58 node-3 kernel: [    2.429869] AppArmor: AppArmor sha1 policy hashing enabled
Jul 31 21:48:58 node-3 kernel: [    2.435375] IMA: No TPM chip found, activating TPM-bypass!
Jul 31 21:48:58 node-3 kernel: [    2.441579] regulator-dummy: disabling
Jul 31 21:48:58 node-3 kernel: [    2.447169]   Magic number: 8:353:855
Jul 31 21:48:58 node-3 kernel: [    2.452659] acpi device:d2: hash matches
Jul 31 21:48:58 node-3 kernel: [    2.458165] rtc_cmos 00:02: setting system clock to 2016-07-31 21:48:24 UTC (1470001704)
Jul 31 21:48:58 node-3 kernel: [    2.462208] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 31 21:48:58 node-3 kernel: [    2.462209] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 31 21:48:58 node-3 kernel: [    2.462209] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 31 21:48:58 node-3 kernel: [    2.462210] usb 2-1.4: Manufacturer: Avocent
Jul 31 21:48:58 node-3 kernel: [    2.462210] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 31 21:48:58 node-3 kernel: [    2.504684] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 31 21:48:58 node-3 kernel: [    2.510342] EDD information not available.
Jul 31 21:48:58 node-3 kernel: [    2.515884] PM: Hibernation image not present or could not be loaded.
Jul 31 21:48:58 node-3 kernel: [    2.516764] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 31 21:48:58 node-3 kernel: [    2.527966] Write protecting the kernel read-only data: 12288k
Jul 31 21:48:58 node-3 kernel: [    2.534120] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 31 21:48:58 node-3 kernel: [    2.546461] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 31 21:48:58 node-3 kernel: [    2.579242] device-mapper: multipath: version 1.6.0 loaded
Jul 31 21:48:58 node-3 kernel: [    2.587258] systemd-udevd[215]: starting version 204
Jul 31 21:48:58 node-3 kernel: [    2.611728] md: linear personality registered for level -1
Jul 31 21:48:58 node-3 kernel: [    2.626257] md: multipath personality registered for level -4
Jul 31 21:48:58 node-3 kernel: [    2.634351] md: raid0 personality registered for level 0
Jul 31 21:48:58 node-3 kernel: [    2.642723] md: raid1 personality registered for level 1
Jul 31 21:48:58 node-3 kernel: [    2.651932] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 31 21:48:58 node-3 kernel: [    2.658399] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 31 21:48:58 node-3 kernel: [    2.670178] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 31 21:48:58 node-3 kernel: [    2.670191] 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
Jul 31 21:48:58 node-3 kernel: [    2.670192] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 21:48:58 node-3 kernel: [    2.670580] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.670719] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.670879] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.670965] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.671301] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.688827] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 31 21:48:58 node-3 kernel: [    2.688844] 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
Jul 31 21:48:58 node-3 kernel: [    2.688875] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 21:48:58 node-3 kernel: [    2.689373] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.689487] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.689645] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.689797] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.690109] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.707405] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 31 21:48:58 node-3 kernel: [    2.707420] 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
Jul 31 21:48:58 node-3 kernel: [    2.707426] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 21:48:58 node-3 kernel: [    2.708038] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.708159] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.708291] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.708393] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.708590] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.717868] raid6: sse2x1   11500 MB/s
Jul 31 21:48:58 node-3 kernel: [    2.725796] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 31 21:48:58 node-3 kernel: [    2.725801] 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
Jul 31 21:48:58 node-3 kernel: [    2.725829] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 31 21:48:58 node-3 kernel: [    2.726231] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.726437] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.726535] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.726689] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.726932] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 31 21:48:58 node-3 kernel: [    2.866951] raid6: sse2x2   24668 MB/s
Jul 31 21:48:58 node-3 kernel: [    2.658286] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 31 21:48:58 node-3 kernel: [    2.940901] raid6: sse2x4   10142 MB/s
Jul 31 21:48:58 node-3 kernel: [    3.020826] raid6: avx2x1   14955 MB/s
Jul 31 21:48:58 node-3 kernel: [    3.092764] raid6: avx2x2   18879 MB/s
Jul 31 21:48:58 node-3 kernel: [    3.164709] raid6: avx2x4   21390 MB/s
Jul 31 21:48:58 node-3 kernel: [    3.170749] raid6: using algorithm sse2x2 (24668 MB/s)
Jul 31 21:48:58 node-3 kernel: [    3.176740] raid6: using avx2x2 recovery algorithm
Jul 31 21:48:58 node-3 kernel: [    3.182570] Switched to clocksource tsc
Jul 31 21:48:58 node-3 kernel: [    3.182590] hidraw: raw HID events driver (C) Jiri Kosina
Jul 31 21:48:58 node-3 kernel: [    3.182810] megasas: FW now in Ready state
Jul 31 21:48:58 node-3 kernel: [    3.183263] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.183368] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.183479] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.183587] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.183689] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.183768] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.183873] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.183979] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.184082] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.184196] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.184318] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.184360] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.184454] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.184565] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.184880] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.185021] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 31 21:48:58 node-3 kernel: [    3.185858] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 31 21:48:58 node-3 kernel: [    3.211208] xor: automatically using best checksumming function:
Jul 31 21:48:58 node-3 kernel: [    3.218844] usbcore: registered new interface driver usbhid
Jul 31 21:48:58 node-3 kernel: [    3.224500] usbhid: USB HID core driver
Jul 31 21:48:58 node-3 kernel: [    3.234251] 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
Jul 31 21:48:58 node-3 kernel: [    3.245447] 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
Jul 31 21:48:58 node-3 kernel: [    3.256764]    avx       : 36384.000 MB/sec
Jul 31 21:48:58 node-3 kernel: [    3.262768] 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
Jul 31 21:48:58 node-3 kernel: [    3.274722] async_tx: api initialized (async)
Jul 31 21:48:58 node-3 kernel: [    3.274955] 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
Jul 31 21:48:58 node-3 kernel: [    3.275897] 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
Jul 31 21:48:58 node-3 kernel: [    3.276562] 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
Jul 31 21:48:58 node-3 kernel: [    3.320733] md: raid6 personality registered for level 6
Jul 31 21:48:58 node-3 kernel: [    3.327140] md: raid5 personality registered for level 5
Jul 31 21:48:58 node-3 kernel: [    3.333443] md: raid4 personality registered for level 4
Jul 31 21:48:58 node-3 kernel: [    3.342771] md: raid10 personality registered for level 10
Jul 31 21:48:58 node-3 kernel: [    3.397499] multipathd (356): /proc/356/oom_adj is deprecated, please use /proc/356/oom_score_adj instead.
Jul 31 21:48:58 node-3 kernel: [    3.524420] megasas:IOC Init cmd success
Jul 31 21:48:58 node-3 kernel: [    3.552411] megasas: INIT adapter done
Jul 31 21:48:58 node-3 kernel: [    3.652318] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 31 21:48:58 node-3 kernel: [    3.659217] scsi0 : LSI SAS based MegaRAID driver
Jul 31 21:48:58 node-3 kernel: [    3.666665] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 31 21:48:58 node-3 kernel: [    3.685456] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 31 21:48:58 node-3 kernel: [    3.701128] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 31 21:48:58 node-3 kernel: [    3.707714] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 31 21:48:58 node-3 kernel: [    3.720718] sd 0:2:0:0: [sda] Write Protect is off
Jul 31 21:48:58 node-3 kernel: [    3.727139] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 31 21:48:58 node-3 kernel: [    3.727158] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 31 21:48:58 node-3 kernel: [    3.771475]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 31 21:48:58 node-3 kernel: [    3.778074] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 31 21:48:58 node-3 kernel: [    3.917183] random: lvm urandom read with 28 bits of entropy available
Jul 31 21:48:58 node-3 kernel: [    4.047813] bio: create slab <bio-1> at 1
Jul 31 21:48:58 node-3 kernel: [    4.799097] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 21:48:58 node-3 kernel: [    5.485804] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 31 21:48:58 node-3 kernel: [    5.541242] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 31 21:48:58 node-3 kernel: [    5.681452] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 31 21:48:58 node-3 kernel: [    5.729319] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 31 21:48:58 node-3 kernel: [    5.762997] random: nonblocking pool is initialized
Jul 31 21:48:58 node-3 kernel: [    5.787499] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 21:48:58 node-3 kernel: [    5.969137] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 31 21:48:58 node-3 kernel: [    6.018855] XFS (dm-0): Mounting Filesystem
Jul 31 21:48:58 node-3 kernel: [    6.263067] XFS (dm-0): Ending clean mount
Jul 31 21:48:58 node-3 kernel: [    6.348208] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 31 21:48:58 node-3 kernel: [    6.380867] XFS (dm-1): Mounting Filesystem
Jul 31 21:48:58 node-3 kernel: [    6.473487] XFS (dm-1): Ending clean mount
Jul 31 21:48:58 node-3 kernel: [    8.691608] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 31 21:48:58 node-3 kernel: [    8.716027] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 31 21:48:58 node-3 kernel: [    8.871172] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 31 21:48:58 node-3 kernel: [    8.871177] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 31 21:48:58 node-3 kernel: [    8.871181] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 31 21:48:58 node-3 kernel: [    8.871185] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 31 21:48:58 node-3 kernel: [    8.895132] systemd-udevd[776]: starting version 204
Jul 31 21:48:58 node-3 kernel: [    9.128519] power_meter ACPI000D:00: Found ACPI power meter.
Jul 31 21:48:58 node-3 kernel: [    9.128528] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 31 21:48:58 node-3 kernel: [    9.151233] IPMI System Interface driver.
Jul 31 21:48:58 node-3 kernel: [    9.151273] ipmi_si: probing via ACPI
Jul 31 21:48:58 node-3 kernel: [    9.151295] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 31 21:48:58 node-3 kernel: [    9.151296] ipmi_si: Adding ACPI-specified kcs state machine
Jul 31 21:48:58 node-3 kernel: [    9.151303] ipmi_si: probing via SMBIOS
Jul 31 21:48:58 node-3 kernel: [    9.151304] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 31 21:48:58 node-3 kernel: [    9.151305] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 31 21:48:58 node-3 kernel: [    9.151307] ipmi_si: probing via SPMI
Jul 31 21:48:58 node-3 kernel: [    9.151307] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 31 21:48:58 node-3 kernel: [    9.151308] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 31 21:48:58 node-3 kernel: [    9.151309] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 31 21:48:58 node-3 kernel: [    9.184374] wmi: Mapper loaded
Jul 31 21:48:58 node-3 kernel: [    9.192388] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 31 21:48:58 node-3 kernel: [    9.192392] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 31 21:48:58 node-3 kernel: [    9.192395] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 31 21:48:58 node-3 kernel: [    9.192397] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 31 21:48:58 node-3 kernel: [    9.192410] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 31 21:48:58 node-3 kernel: [    9.196460] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 31 21:48:58 node-3 kernel: [    9.268079] systemd-udevd[804]: renamed network interface eth2 to enp8s0
Jul 31 21:48:58 node-3 kernel: [    9.295124] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 31 21:48:58 node-3 kernel: [    9.295133] ipmi_si 00:09: IPMI kcs interface initialized
Jul 31 21:48:58 node-3 kernel: [    9.303989] systemd-udevd[798]: renamed network interface eth1 to enp7s0
Jul 31 21:48:58 node-3 kernel: [    9.315855] systemd-udevd[794]: renamed network interface eth3 to enp9s0
Jul 31 21:48:58 node-3 kernel: [    9.339812] systemd-udevd[793]: renamed network interface eth0 to enp6s0
Jul 31 21:48:58 node-3 kernel: [    9.649185] type=1400 audit(1470001711.692:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1035 comm="apparmor_parser"
Jul 31 21:48:58 node-3 kernel: [    9.649341] type=1400 audit(1470001711.692:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1035 comm="apparmor_parser"
Jul 31 21:48:58 node-3 kernel: [    9.649472] type=1400 audit(1470001711.692:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1035 comm="apparmor_parser"
Jul 31 21:48:58 node-3 kernel: [    9.653528] type=1400 audit(1470001711.696:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1036 comm="apparmor_parser"
Jul 31 21:48:58 node-3 kernel: [    9.653674] type=1400 audit(1470001711.696:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1036 comm="apparmor_parser"
Jul 31 21:48:58 node-3 kernel: [    9.653793] type=1400 audit(1470001711.696:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1036 comm="apparmor_parser"
Jul 31 21:48:58 node-3 kernel: [    9.657603] type=1400 audit(1470001711.700:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1037 comm="apparmor_parser"
Jul 31 21:48:58 node-3 kernel: [    9.657741] type=1400 audit(1470001711.700:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1037 comm="apparmor_parser"
Jul 31 21:48:58 node-3 kernel: [    9.657859] type=1400 audit(1470001711.700:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1037 comm="apparmor_parser"
Jul 31 21:48:58 node-3 kernel: [    9.662905] type=1400 audit(1470001711.704:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1042 comm="apparmor_parser"
Jul 31 21:48:58 node-3 kernel: [   10.144938] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 31 21:48:58 node-3 kernel: [   10.145837] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 31 21:48:58 node-3 kernel: [   10.335895] enic 0000:06:00.0 enp6s0: Link UP
Jul 31 21:48:58 node-3 kernel: [   10.336319] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 31 21:48:58 node-3 kernel: [   10.336324] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 31 21:48:58 node-3 kernel: [   19.597458] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 31 21:48:59 node-3 failsafe: Failsafe of 120 seconds reached.
Jul 31 21:49:00 node-3 kernel: [   38.251124] init: failsafe main process (8399) killed by TERM signal
Jul 31 21:49:00 node-3 dbus[8449]: [system] AppArmor D-Bus mediation is enabled
Jul 31 21:49:00 node-3 kernel: [   38.439527] audit_printk_skb: 30 callbacks suppressed
Jul 31 21:49:00 node-3 kernel: [   38.439529] type=1400 audit(1470001740.223:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8520 comm="apparmor_parser"
Jul 31 21:49:00 node-3 kernel: [   38.439621] type=1400 audit(1470001740.223:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8519 comm="apparmor_parser"
Jul 31 21:49:00 node-3 kernel: [   38.439626] type=1400 audit(1470001740.223:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8519 comm="apparmor_parser"
Jul 31 21:49:00 node-3 kernel: [   38.439629] type=1400 audit(1470001740.223:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8519 comm="apparmor_parser"
Jul 31 21:49:00 node-3 kernel: [   38.439851] type=1400 audit(1470001740.223:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8519 comm="apparmor_parser"
Jul 31 21:49:00 node-3 kernel: [   38.439854] type=1400 audit(1470001740.223:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8519 comm="apparmor_parser"
Jul 31 21:49:00 node-3 kernel: [   38.439970] type=1400 audit(1470001740.223:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8519 comm="apparmor_parser"
Jul 31 21:49:00 node-3 kernel: [   38.507944] type=1400 audit(1470001740.291:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8522 comm="apparmor_parser"
Jul 31 21:49:00 node-3 anacron[8591]: Anacron 2.3 started on 2016-07-31
Jul 31 21:49:00 node-3 anacron[8591]: Will run job `cron.daily' in 5 min.
Jul 31 21:49:00 node-3 anacron[8591]: Will run job `cron.weekly' in 10 min.
Jul 31 21:49:00 node-3 anacron[8591]: Will run job `cron.monthly' in 15 min.
Jul 31 21:49:00 node-3 anacron[8591]: Jobs will be executed sequentially
Jul 31 21:49:00 node-3 cron[8557]: (CRON) INFO (pidfile fd = 3)
Jul 31 21:49:00 node-3 multipathd: path checkers start up
Jul 31 21:49:00 node-3 cron[8636]: (CRON) STARTUP (fork ok)
Jul 31 21:49:00 node-3 cron[8636]: (CRON) INFO (Running @reboot jobs)
Jul 31 21:49:00 node-3 postfix/master[8733]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 31 21:49:04 node-3 puppet-agent[8917]: Reopening log files
Jul 31 21:49:04 node-3 puppet-agent[8917]: Could not request certificate: Connection refused - connect(2)
Jul 31 21:49:17 node-3 puppet-user[9125]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 31 21:49:17 node-3 puppet-user[9125]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Jul 31 21:49:18 node-3 puppet-user[9125]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 31 21:49:18 node-3 puppet-user[9125]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 31 21:49:18 node-3 puppet-user[9125]: Finished catalog run in 0.88 seconds
Jul 31 21:49:20 node-3 multipathd: uevent trigger error
Jul 31 21:49:20 node-3 puppet-user[9555]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 31 21:49:20 node-3 puppet-user[9555]: Compiled catalog for node-3.domain.tld in environment production in 0.09 seconds
Jul 31 21:49:20 node-3 puppet-user[9555]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 31 21:49:20 node-3 puppet-user[9555]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 31 21:49:20 node-3 puppet-user[9555]: (/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"]'
Jul 31 21:49:20 node-3 puppet-user[9555]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 31 21:49:20 node-3 puppet-user[9555]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 31 21:49:20 node-3 puppet-user[9555]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 31 21:49:20 node-3 puppet-user[9555]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 31 21:49:20 node-3 puppet-user[9555]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 31 21:49:20 node-3 puppet-user[9555]: Finished catalog run in 0.05 seconds
Jul 31 21:49:22 node-3 puppet-user[10021]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 31 21:49:22 node-3 puppet-user[10021]: Compiled catalog for node-3.domain.tld in environment production in 0.07 seconds
Jul 31 21:49:22 node-3 puppet-user[10021]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 31 21:49:22 node-3 puppet-user[10021]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 31 21:49:22 node-3 puppet-user[10021]: Finished catalog run in 0.03 seconds
Jul 31 21:49:24 node-3 puppet-user[10484]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 31 21:49:24 node-3 puppet-user[10484]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Jul 31 21:49:24 node-3 puppet-user[10484]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 31 21:49:24 node-3 puppet-user[10484]: Finished catalog run in 0.04 seconds
Jul 31 21:49:25 node-3 puppet-user[10946]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 31 21:49:25 node-3 puppet-user[10946]: Compiled catalog for node-3.domain.tld in environment production in 0.17 seconds
Jul 31 21:49:25 node-3 puppet-user[10946]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 31 21:49:27 node-3 puppet-user[10946]: (/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
Jul 31 21:49:27 node-3 puppet-user[10946]: Finished catalog run in 2.04 seconds
Jul 31 21:49:29 node-3 puppet-user[11645]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 31 21:49:29 node-3 puppet-user[11645]: Compiled catalog for node-3.domain.tld in environment production in 0.20 seconds
Jul 31 21:49:29 node-3 puppet-user[11645]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 31 21:49:29 node-3 puppet-user[11645]: (/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
Jul 31 21:49:29 node-3 puppet-user[11645]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 31 21:49:29 node-3 puppet-user[11645]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 31 21:49:29 node-3 puppet-user[11645]: Finished catalog run in 0.24 seconds
Jul 31 21:49:31 node-3 puppet-user[12124]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 31 21:49:31 node-3 puppet-user[12124]: Compiled catalog for node-3.domain.tld in environment production in 0.13 seconds
Jul 31 21:49:31 node-3 puppet-user[12124]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 31 21:49:31 node-3 kernel: [   69.647645] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 31 21:49:31 node-3 kernel: [   69.647696] 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.
Jul 31 21:49:31 node-3 puppet-user[12124]: (/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'
Jul 31 21:49:31 node-3 puppet-user[12124]: Finished catalog run in 0.05 seconds
Jul 31 21:49:33 node-3 puppet-user[12581]: (Scope(Class[main])) MODULAR: sync_time
Jul 31 21:49:33 node-3 puppet-user[12581]: Compiled catalog for node-3.domain.tld in environment production in 0.02 seconds
Jul 31 21:49:33 node-3 ntpdate[12992]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 31 21:49:37 node-3 kernel: [   75.449622] init: plymouth-upstart-bridge main process ended, respawning
Jul 31 21:49:37 node-3 puppet-agent[8917]: Could not run: SIGTERM
Jul 31 21:49:37 node-3 kernel: [   75.726343] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 31 21:49:37 node-3 ec2: 
Jul 31 21:49:37 node-3 ec2: #############################################################
Jul 31 21:49:37 node-3 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 31 21:49:37 node-3 ec2: 1024 c5:9c:6d:b1:99:8a:7c:04:b4:b2:39:96:3e:b6:4f:e1  root@node-3.domain.tld (DSA)
Jul 31 21:49:37 node-3 ec2: 256 66:f8:69:b5:bb:c8:cd:77:09:b7:b3:37:6a:41:61:b3  root@node-3.domain.tld (ECDSA)
Jul 31 21:49:37 node-3 ec2: 256 0a:43:66:a7:28:b9:de:de:a3:c7:f5:f5:1d:f3:b2:52  root@node-3.domain.tld (ED25519)
Jul 31 21:49:37 node-3 ec2: 2048 30:a1:66:ed:0b:71:5e:60:6d:8a:2a:bb:d9:d0:d6:20  root@node-3.domain.tld (RSA)
Jul 31 21:49:37 node-3 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 31 21:49:37 node-3 ec2: #############################################################
Jul 31 21:49:39 node-3 ntpdate[12992]: adjust time server 10.20.0.2 offset 0.139942 sec
Jul 31 21:49:39 node-3 puppet-user[12581]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 31 21:49:39 node-3 puppet-user[12581]: Finished catalog run in 6.18 seconds
Jul 31 21:49:44 node-3 puppet-user[13360]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 31 21:49:44 node-3 puppet-user[13360]: Compiled catalog for node-3.domain.tld in environment production in 0.08 seconds
Jul 31 21:49:44 node-3 puppet-user[13360]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 31 21:49:44 node-3 puppet-user[13360]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/onos"]'
Jul 31 21:49:44 node-3 puppet-user[13360]: Finished catalog run in 0.07 seconds
Jul 31 21:49:46 node-3 puppet-user[13822]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 31 21:49:48 node-3 puppet-user[13822]: Compiled catalog for node-3.domain.tld in environment production in 2.03 seconds
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 31 21:49:48 node-3 puppet-user[13822]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 31 21:49:48 node-3 puppet-user[13822]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/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
Jul 31 21:49:48 node-3 puppet-user[13822]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 31 21:50:01 node-3 CRON[14723]: (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")
Jul 31 21:50:04 node-3 puppet-user[13822]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 31 21:50:04 node-3 puppet-user[13822]: Finished catalog run in 16.74 seconds
Jul 31 21:50:07 node-3 puppet-user[14836]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 31 21:50:07 node-3 puppet-user[14836]: Compiled catalog for node-3.domain.tld in environment production in 0.13 seconds
Jul 31 21:50:11 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 21:50:11 node-3 nailgun-agent: I, [2016-07-31T21:50:11.767131 #14726]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 31 21:50:12 node-3 puppet-user[14836]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 31 21:50:24 node-3 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 31 21:50:24 node-3 nailgun-agent: I, [2016-07-31T21:50:24.831268 #14726]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 3
Jul 31 21:50:42 node-3 puppet-user[14836]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 31 21:50:42 node-3 puppet-user[14836]: Finished catalog run in 35.00 seconds
Jul 31 21:50:44 node-3 puppet-user[17591]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 31 21:50:45 node-3 puppet-user[17591]: Compiled catalog for node-3.domain.tld in environment production in 0.59 seconds
Jul 31 21:50:45 node-3 puppet-user[17591]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 31 21:50:45 node-3 puppet-user[17591]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 31 21:50:45 node-3 puppet-user[17591]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 31 21:50:45 node-3 puppet-user[17591]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 31 21:50:45 node-3 puppet-user[17591]: Finished catalog run in 0.07 seconds
Jul 31 21:50:47 node-3 puppet-user[18049]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 31 21:50:48 node-3 puppet-user[18049]: Compiled catalog for node-3.domain.tld in environment production in 0.89 seconds
Jul 31 21:50:48 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 31 21:50:48 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 31 21:50:48 node-3 crontab[18499]: (root) LIST (root)
Jul 31 21:50:48 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 31 21:50:48 node-3 crontab[18500]: (root) REPLACE (root)
Jul 31 21:50:50 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/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
Jul 31 21:50:52 node-3 puppet-user[18049]: (/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
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/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
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/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
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/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
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/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
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 31 21:50:52 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 31 21:50:53 node-3 puppet-user[18049]: (/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
Jul 31 21:50:53 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 31 21:50:53 node-3 puppet-user[18049]: (/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
Jul 31 21:50:53 node-3 puppet-user[18049]: (/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
Jul 31 21:50:53 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 31 21:50:53 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 31 21:50:53 node-3 puppet-user[18049]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 31 21:50:53 node-3 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8371" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 31 21:50:53 node-3 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 31 21:50:55 node-3 multipathd: uevent trigger error
<27>Jul 31 21:50:55 node-3 multipathd: uevent trigger error
<27>Jul 31 21:50:55 node-3 multipathd: uevent trigger error
<27>Jul 31 21:50:55 node-3 multipathd: uevent trigger error
<27>Jul 31 21:51:13 node-3 multipathd: uevent trigger error
<27>Jul 31 21:51:13 node-3 multipathd: uevent trigger error
<27>Jul 31 21:51:13 node-3 multipathd: uevent trigger error
<27>Jul 31 21:51:13 node-3 multipathd: uevent trigger error
<27>Jul 31 21:52:02 node-3 multipathd: uevent trigger error
<27>Jul 31 21:52:02 node-3 multipathd: uevent trigger error
<27>Jul 31 21:52:02 node-3 multipathd: uevent trigger error
<27>Jul 31 21:52:02 node-3 multipathd: uevent trigger error
<27>Jul 31 21:52:02 node-3 multipathd: uevent trigger error
<27>Jul 31 21:52:05 node-3 multipathd: uevent trigger error
<27>Jul 31 21:52:05 node-3 multipathd: uevent trigger error
<27>Jul 31 21:52:05 node-3 multipathd: uevent trigger error
<27>Jul 31 21:52:05 node-3 multipathd: uevent trigger error
<27>Jul 31 21:52:48 node-3 ntpdate[2265]: no servers can be used, exiting
<27>Jul 31 21:52:48 node-3 ntpdate[2512]: no servers can be used, exiting
<27>Jul 31 21:53:19 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:19 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:19 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:19 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:19 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:19 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:19 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:24 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:24 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:24 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:24 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:24 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:35 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:35 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:35 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:35 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:35 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:38 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:38 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:38 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:38 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:38 node-3 multipathd: uevent trigger error
<27>Jul 31 21:53:39 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:40 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:40 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:40 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:40 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:40 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:49 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:49 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:49 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:49 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:49 node-3 multipathd: uevent trigger error
<27>Jul 31 21:54:51 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 21:54:52 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 21:54:58 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 21:54:58 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 21:55:03 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 21:55:09 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 21:55:09 node-3 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 31 21:55:16 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:16 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:16 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:16 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:16 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:16 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:28 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:28 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:28 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:28 node-3 multipathd: uevent trigger error
<129>Jul 31 21:55:31 node-3 haproxy[23010]: 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>Jul 31 21:55:31 node-3 haproxy[23010]: 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>Jul 31 21:55:32 node-3 haproxy[23017]: 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>Jul 31 21:55:32 node-3 haproxy[23017]: proxy mysqld has no server available!
<27>Jul 31 21:55:34 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:34 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:34 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:34 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:34 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:34 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:34 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:38 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:38 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:38 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:38 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:38 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:38 node-3 multipathd: uevent trigger error
<129>Jul 31 21:55:40 node-3 haproxy[25584]: 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>Jul 31 21:55:41 node-3 haproxy[25588]: 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>Jul 31 21:55:41 node-3 haproxy[25588]: 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>Jul 31 21:55:41 node-3 haproxy[25588]: proxy mysqld has no server available!
<129>Jul 31 21:55:41 node-3 haproxy[25588]: 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>Jul 31 21:55:42 node-3 haproxy[25588]: 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>Jul 31 21:55:42 node-3 haproxy[25588]: 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>Jul 31 21:55:42 node-3 haproxy[25588]: proxy object-storage has no server available!
<27>Jul 31 21:55:44 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:44 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:44 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:44 node-3 multipathd: uevent trigger error
<129>Jul 31 21:55:46 node-3 haproxy[26954]: 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>Jul 31 21:55:46 node-3 haproxy[26954]: 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>Jul 31 21:55:46 node-3 haproxy[26954]: 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>Jul 31 21:55:46 node-3 haproxy[26954]: proxy neutron has no server available!
<129>Jul 31 21:55:46 node-3 haproxy[26954]: 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>Jul 31 21:55:47 node-3 haproxy[26958]: 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>Jul 31 21:55:47 node-3 haproxy[26958]: 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>Jul 31 21:55:47 node-3 haproxy[26958]: proxy mysqld has no server available!
<129>Jul 31 21:55:47 node-3 haproxy[26958]: 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>Jul 31 21:55:47 node-3 haproxy[26958]: 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>Jul 31 21:55:48 node-3 haproxy[26958]: 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>Jul 31 21:55:48 node-3 haproxy[26958]: proxy object-storage has no server available!
<27>Jul 31 21:55:49 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:49 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:49 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:49 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:49 node-3 multipathd: uevent trigger error
<129>Jul 31 21:55:51 node-3 haproxy[28415]: 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>Jul 31 21:55:51 node-3 haproxy[28415]: 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>Jul 31 21:55:52 node-3 haproxy[28419]: 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>Jul 31 21:55:52 node-3 haproxy[28419]: proxy keystone-1 has no server available!
<129>Jul 31 21:55:52 node-3 haproxy[28419]: 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>Jul 31 21:55:52 node-3 haproxy[28419]: 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>Jul 31 21:55:52 node-3 haproxy[28419]: 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>Jul 31 21:55:52 node-3 haproxy[28419]: proxy keystone-2 has no server available!
<129>Jul 31 21:55:52 node-3 haproxy[28419]: 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>Jul 31 21:55:52 node-3 haproxy[28419]: 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>Jul 31 21:55:52 node-3 haproxy[28419]: 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>Jul 31 21:55:52 node-3 haproxy[28419]: proxy neutron has no server available!
<129>Jul 31 21:55:52 node-3 haproxy[28419]: 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>Jul 31 21:55:53 node-3 haproxy[28419]: 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>Jul 31 21:55:53 node-3 haproxy[28419]: 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>Jul 31 21:55:53 node-3 haproxy[28419]: proxy mysqld has no server available!
<129>Jul 31 21:55:53 node-3 haproxy[28419]: 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>Jul 31 21:55:53 node-3 haproxy[28419]: 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>Jul 31 21:55:53 node-3 haproxy[28419]: 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>Jul 31 21:55:53 node-3 haproxy[28419]: proxy object-storage has no server available!
<27>Jul 31 21:55:54 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:54 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:54 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:54 node-3 multipathd: uevent trigger error
<27>Jul 31 21:55:54 node-3 multipathd: uevent trigger error
<129>Jul 31 21:55:57 node-3 haproxy[29800]: 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>Jul 31 21:55:57 node-3 haproxy[29800]: 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>Jul 31 21:55:57 node-3 haproxy[29800]: 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>Jul 31 21:55:57 node-3 haproxy[29800]: proxy keystone-1 has no server available!
<129>Jul 31 21:55:57 node-3 haproxy[29800]: 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>Jul 31 21:55:57 node-3 haproxy[29800]: 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>Jul 31 21:55:57 node-3 haproxy[29800]: 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>Jul 31 21:55:57 node-3 haproxy[29800]: proxy keystone-2 has no server available!
<129>Jul 31 21:55:57 node-3 haproxy[29800]: 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>Jul 31 21:55:58 node-3 haproxy[29804]: 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>Jul 31 21:55:58 node-3 haproxy[29804]: 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>Jul 31 21:55:58 node-3 haproxy[29804]: proxy neutron has no server available!
<129>Jul 31 21:55:58 node-3 haproxy[29804]: 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>Jul 31 21:55:58 node-3 haproxy[29804]: 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>Jul 31 21:55:58 node-3 haproxy[29804]: 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>Jul 31 21:55:58 node-3 haproxy[29804]: proxy mysqld has no server available!
<129>Jul 31 21:55:58 node-3 haproxy[29804]: 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>Jul 31 21:55:58 node-3 haproxy[29804]: 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>Jul 31 21:55:58 node-3 haproxy[29804]: 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>Jul 31 21:55:58 node-3 haproxy[29804]: proxy object-storage has no server available!
<129>Jul 31 21:55:58 node-3 haproxy[29804]: 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>Jul 31 21:55:59 node-3 haproxy[29804]: 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>Jul 31 21:55:59 node-3 haproxy[29804]: 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>Jul 31 21:55:59 node-3 haproxy[29804]: proxy aodh has no server available!
<27>Jul 31 21:56:00 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:00 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:00 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:00 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:00 node-3 multipathd: uevent trigger error
<129>Jul 31 21:56:02 node-3 haproxy[31136]: 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>Jul 31 21:56:02 node-3 haproxy[31136]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: proxy keystone-1 has no server available!
<129>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: proxy keystone-2 has no server available!
<129>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: proxy neutron has no server available!
<129>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:03 node-3 haproxy[31140]: proxy mysqld has no server available!
<129>Jul 31 21:56:03 node-3 haproxy[31140]: 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>Jul 31 21:56:04 node-3 haproxy[31140]: 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>Jul 31 21:56:04 node-3 haproxy[31140]: 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>Jul 31 21:56:04 node-3 haproxy[31140]: proxy object-storage has no server available!
<129>Jul 31 21:56:04 node-3 haproxy[31140]: 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>Jul 31 21:56:04 node-3 haproxy[31140]: 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>Jul 31 21:56:04 node-3 haproxy[31140]: 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>Jul 31 21:56:04 node-3 haproxy[31140]: proxy aodh has no server available!
<129>Jul 31 21:56:04 node-3 haproxy[31140]: 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>Jul 31 21:56:04 node-3 haproxy[31140]: 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>Jul 31 21:56:04 node-3 haproxy[31140]: 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>Jul 31 21:56:04 node-3 haproxy[31140]: proxy ceilometer has no server available!
<27>Jul 31 21:56:06 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:06 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:06 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:06 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:06 node-3 multipathd: uevent trigger error
<129>Jul 31 21:56:08 node-3 haproxy[32487]: 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>Jul 31 21:56:08 node-3 haproxy[32487]: 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>Jul 31 21:56:08 node-3 haproxy[32487]: 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>Jul 31 21:56:08 node-3 haproxy[32487]: proxy keystone-1 has no server available!
<129>Jul 31 21:56:08 node-3 haproxy[32487]: 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>Jul 31 21:56:08 node-3 haproxy[32487]: 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>Jul 31 21:56:08 node-3 haproxy[32487]: 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>Jul 31 21:56:08 node-3 haproxy[32487]: proxy keystone-2 has no server available!
<129>Jul 31 21:56:08 node-3 haproxy[32487]: 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>Jul 31 21:56:08 node-3 haproxy[32487]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: proxy neutron has no server available!
<129>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: proxy mysqld has no server available!
<129>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: proxy object-storage has no server available!
<129>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:09 node-3 haproxy[32491]: proxy aodh has no server available!
<129>Jul 31 21:56:09 node-3 haproxy[32491]: 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>Jul 31 21:56:10 node-3 haproxy[32491]: 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>Jul 31 21:56:10 node-3 haproxy[32491]: 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>Jul 31 21:56:10 node-3 haproxy[32491]: proxy ceilometer has no server available!
<27>Jul 31 21:56:11 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:11 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:11 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:11 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:11 node-3 multipathd: uevent trigger error
<129>Jul 31 21:56:13 node-3 haproxy[1423]: 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>Jul 31 21:56:13 node-3 haproxy[1423]: 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>Jul 31 21:56:13 node-3 haproxy[1423]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: proxy keystone-1 has no server available!
<129>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: proxy keystone-2 has no server available!
<129>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: proxy neutron has no server available!
<129>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: proxy mysqld has no server available!
<129>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:14 node-3 haproxy[1427]: 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>Jul 31 21:56:15 node-3 haproxy[1427]: 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>Jul 31 21:56:15 node-3 haproxy[1427]: proxy object-storage has no server available!
<129>Jul 31 21:56:15 node-3 haproxy[1427]: 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>Jul 31 21:56:15 node-3 haproxy[1427]: 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>Jul 31 21:56:15 node-3 haproxy[1427]: 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>Jul 31 21:56:15 node-3 haproxy[1427]: proxy aodh has no server available!
<129>Jul 31 21:56:15 node-3 haproxy[1427]: 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>Jul 31 21:56:15 node-3 haproxy[1427]: 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>Jul 31 21:56:15 node-3 haproxy[1427]: 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>Jul 31 21:56:15 node-3 haproxy[1427]: proxy ceilometer has no server available!
<27>Jul 31 21:56:16 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:16 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:16 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:16 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:16 node-3 multipathd: uevent trigger error
<129>Jul 31 21:56:19 node-3 haproxy[2811]: 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>Jul 31 21:56:19 node-3 haproxy[2811]: 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>Jul 31 21:56:19 node-3 haproxy[2811]: 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>Jul 31 21:56:19 node-3 haproxy[2811]: 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>Jul 31 21:56:19 node-3 haproxy[2811]: proxy keystone-1 has no server available!
<129>Jul 31 21:56:19 node-3 haproxy[2811]: 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>Jul 31 21:56:19 node-3 haproxy[2811]: 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>Jul 31 21:56:19 node-3 haproxy[2811]: 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>Jul 31 21:56:19 node-3 haproxy[2811]: proxy keystone-2 has no server available!
<129>Jul 31 21:56:19 node-3 haproxy[2811]: 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>Jul 31 21:56:19 node-3 haproxy[2811]: 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>Jul 31 21:56:19 node-3 haproxy[2811]: 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>Jul 31 21:56:19 node-3 haproxy[2811]: proxy glance-api has no server available!
<129>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: proxy glance-glare has no server available!
<129>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: proxy neutron has no server available!
<129>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: proxy glance-registry has no server available!
<129>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: proxy mysqld has no server available!
<129>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: proxy object-storage has no server available!
<129>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:20 node-3 haproxy[2815]: 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>Jul 31 21:56:21 node-3 haproxy[2815]: 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>Jul 31 21:56:21 node-3 haproxy[2815]: proxy aodh has no server available!
<129>Jul 31 21:56:21 node-3 haproxy[2815]: 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>Jul 31 21:56:21 node-3 haproxy[2815]: 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>Jul 31 21:56:21 node-3 haproxy[2815]: 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>Jul 31 21:56:21 node-3 haproxy[2815]: proxy ceilometer has no server available!
<27>Jul 31 21:56:22 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:22 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:22 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:22 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:22 node-3 multipathd: uevent trigger error
<129>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: proxy keystone-1 has no server available!
<129>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: proxy keystone-2 has no server available!
<129>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: proxy nova-api has no server available!
<129>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: proxy nova-metadata-api has no server available!
<129>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: 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>Jul 31 21:56:25 node-3 haproxy[4343]: proxy glance-api has no server available!
<129>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: proxy glance-glare has no server available!
<129>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: proxy neutron has no server available!
<129>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: proxy glance-registry has no server available!
<129>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: proxy mysqld has no server available!
<129>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: proxy object-storage has no server available!
<129>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: proxy aodh has no server available!
<129>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: 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>Jul 31 21:56:26 node-3 haproxy[4354]: proxy ceilometer has no server available!
<129>Jul 31 21:56:27 node-3 haproxy[4354]: 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>Jul 31 21:56:27 node-3 haproxy[4354]: 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>Jul 31 21:56:27 node-3 haproxy[4354]: 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>Jul 31 21:56:27 node-3 haproxy[4354]: proxy nova-novncproxy has no server available!
<27>Jul 31 21:56:28 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:28 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:28 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:28 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:28 node-3 multipathd: uevent trigger error
<129>Jul 31 21:56:30 node-3 haproxy[5680]: 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>Jul 31 21:56:30 node-3 haproxy[5680]: 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>Jul 31 21:56:30 node-3 haproxy[5680]: 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>Jul 31 21:56:30 node-3 haproxy[5680]: 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>Jul 31 21:56:30 node-3 haproxy[5680]: proxy keystone-1 has no server available!
<129>Jul 31 21:56:30 node-3 haproxy[5680]: 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>Jul 31 21:56:30 node-3 haproxy[5680]: 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>Jul 31 21:56:30 node-3 haproxy[5680]: 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>Jul 31 21:56:30 node-3 haproxy[5680]: proxy keystone-2 has no server available!
<129>Jul 31 21:56:30 node-3 haproxy[5680]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: proxy nova-api has no server available!
<129>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: proxy nova-metadata-api has no server available!
<129>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: proxy cinder-api has no server available!
<129>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: proxy glance-api has no server available!
<129>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: proxy glance-glare has no server available!
<129>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: proxy neutron has no server available!
<129>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: proxy glance-registry has no server available!
<129>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: 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>Jul 31 21:56:31 node-3 haproxy[5684]: proxy mysqld has no server available!
<129>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: proxy object-storage has no server available!
<129>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: proxy aodh has no server available!
<129>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: proxy ceilometer has no server available!
<129>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: 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>Jul 31 21:56:32 node-3 haproxy[5684]: proxy nova-novncproxy has no server available!
<27>Jul 31 21:56:33 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:33 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:33 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:33 node-3 multipathd: uevent trigger error
<129>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: proxy keystone-1 has no server available!
<129>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: proxy keystone-2 has no server available!
<129>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: proxy nova-api has no server available!
<129>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: proxy nova-metadata-api has no server available!
<129>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: proxy cinder-api has no server available!
<129>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:36 node-3 haproxy[7189]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: proxy glance-api has no server available!
<129>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: proxy glance-glare has no server available!
<129>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: proxy neutron has no server available!
<129>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: proxy glance-registry has no server available!
<129>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: proxy mysqld has no server available!
<129>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: proxy object-storage has no server available!
<129>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: proxy aodh has no server available!
<129>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: proxy ceilometer has no server available!
<129>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: proxy heat-api has no server available!
<129>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:37 node-3 haproxy[7193]: 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>Jul 31 21:56:38 node-3 haproxy[7193]: 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>Jul 31 21:56:38 node-3 haproxy[7193]: proxy heat-api-cfn has no server available!
<129>Jul 31 21:56:38 node-3 haproxy[7193]: 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>Jul 31 21:56:38 node-3 haproxy[7193]: 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>Jul 31 21:56:38 node-3 haproxy[7193]: 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>Jul 31 21:56:38 node-3 haproxy[7193]: proxy heat-api-cloudwatch has no server available!
<129>Jul 31 21:56:38 node-3 haproxy[7193]: 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>Jul 31 21:56:38 node-3 haproxy[7193]: 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>Jul 31 21:56:38 node-3 haproxy[7193]: 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>Jul 31 21:56:38 node-3 haproxy[7193]: proxy nova-novncproxy has no server available!
<27>Jul 31 21:56:39 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:39 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:39 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:39 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:39 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:42 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:42 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:43 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:43 node-3 multipathd: uevent trigger error
<27>Jul 31 21:56:53 node-3 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 31 21:57:18 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>Jul 31 21:57:20 node-3 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 31 21:57:47 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 21:57:53 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 21:58:13 node-3 multipathd: uevent trigger error
<27>Jul 31 21:58:13 node-3 multipathd: uevent trigger error
<27>Jul 31 21:58:13 node-3 multipathd: uevent trigger error
<27>Jul 31 21:58:13 node-3 multipathd: uevent trigger error
<27>Jul 31 21:58:13 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:07 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:07 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:07 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:07 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:07 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:14 node-3 multipathd: uevent trigger error
<43>Jul 31 22:00:34 node-3 apache2_error [Sun Jul 31 22:00:26.782538 2016] [mpm_event:notice] [pid 13212:tid 139809004820352] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 22:00:34 node-3 apache2_error [Sun Jul 31 22:00:26.782655 2016] [core:notice] [pid 13212:tid 139809004820352] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 22:00:34 node-3 apache2_error [Sun Jul 31 22:00:29.827879 2016] [mpm_event:notice] [pid 13212:tid 139809004820352] AH00491: caught SIGTERM, shutting down
<43>Jul 31 22:00:34 node-3 apache2_error [Sun Jul 31 22:00:30.914957 2016] [mpm_worker:notice] [pid 13645:tid 140269409703808] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 31 22:00:34 node-3 apache2_error [Sun Jul 31 22:00:30.915039 2016] [core:notice] [pid 13645:tid 140269409703808] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 22:00:35 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:35 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:35 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:35 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:38 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:38 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:38 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:38 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:38 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:00:52 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 22:01:17 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:17 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:17 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:21 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:21 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:21 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:21 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:21 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:21 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:26 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:26 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:26 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:26 node-3 multipathd: uevent trigger error
<27>Jul 31 22:01:26 node-3 multipathd: uevent trigger error
<43>Jul 31 22:02:44 node-3 apache2_error [Sun Jul 31 22:02:35.166919 2016] [mpm_worker:notice] [pid 13645:tid 140269409703808] AH00295: caught SIGTERM, shutting down
<43>Jul 31 22:02:44 node-3 apache2_error [Sun Jul 31 22:02:35.923162 2016] [mpm_worker:notice] [pid 2459:tid 140298238334848] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 22:02:44 node-3 apache2_error [Sun Jul 31 22:02:35.923189 2016] [core:notice] [pid 2459:tid 140298238334848] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 22:03:24 node-3 apache2_error [Sun Jul 31 22:03:20.082527 2016] [mpm_worker:notice] [pid 2459:tid 140298238334848] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 22:03:24 node-3 apache2_error [Sun Jul 31 22:03:20.279114 2016] [mpm_worker:warn] [pid 2459:tid 140298238334848] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 22:03:24 node-3 apache2_error [Sun Jul 31 22:03:20.284557 2016] [mpm_worker:notice] [pid 2459:tid 140298238334848] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 22:03:24 node-3 apache2_error [Sun Jul 31 22:03:20.284595 2016] [core:notice] [pid 2459:tid 140298238334848] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 22:04:01 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 22:04:05 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:05 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:05 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:05 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:05 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:46 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:46 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:46 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:46 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:46 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:51 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:51 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:51 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:51 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:51 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:51 node-3 multipathd: uevent trigger error
<27>Jul 31 22:04:51 node-3 multipathd: uevent trigger error
<27>Jul 31 22:05:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:05:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:05:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:05:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:05:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:06:07 node-3 multipathd: uevent trigger error
<27>Jul 31 22:06:07 node-3 multipathd: uevent trigger error
<27>Jul 31 22:06:07 node-3 multipathd: uevent trigger error
<27>Jul 31 22:06:07 node-3 multipathd: uevent trigger error
<27>Jul 31 22:06:07 node-3 multipathd: uevent trigger error
<27>Jul 31 22:07:03 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 22:07:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:07:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:07:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:07:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:07:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:18 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:18 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:18 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:18 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:18 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:23 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:23 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:23 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:23 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:23 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:47 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:47 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:47 node-3 multipathd: uevent trigger error
<27>Jul 31 22:08:47 node-3 multipathd: uevent trigger error
<27>Jul 31 22:10:05 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 22:11:13 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:13 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:13 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:13 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:13 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:28 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:28 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:28 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:28 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:28 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:11:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:44 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:44 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:44 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:44 node-3 multipathd: uevent trigger error
<27>Jul 31 22:12:44 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:07 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 22:13:30 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:30 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:30 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:30 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:30 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:30 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:38 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Interface
<27>Jul 31 22:13:38 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "int-br-floating" in table Port
<27>Jul 31 22:13:38 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "phy-br-floating" in table Port
<27>Jul 31 22:13:39 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-tun" in table Port
<27>Jul 31 22:13:39 node-3 ovs-vsctl: ovs|00001|db_ctl_base|ERR|no row "patch-int" in table Port
<27>Jul 31 22:13:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:13:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:14:08 node-3 multipathd: uevent trigger error
<27>Jul 31 22:14:08 node-3 multipathd: uevent trigger error
<27>Jul 31 22:14:08 node-3 multipathd: uevent trigger error
<27>Jul 31 22:14:08 node-3 multipathd: uevent trigger error
<27>Jul 31 22:14:26 node-3 multipathd: uevent trigger error
<27>Jul 31 22:14:26 node-3 multipathd: uevent trigger error
<27>Jul 31 22:14:26 node-3 multipathd: uevent trigger error
<27>Jul 31 22:14:26 node-3 multipathd: uevent trigger error
<27>Jul 31 22:14:26 node-3 multipathd: uevent trigger error
<27>Jul 31 22:14:26 node-3 multipathd: uevent trigger error
<27>Jul 31 22:16:09 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 22:16:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:16:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:16:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:16:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:16:48 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:45 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:45 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:45 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:45 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:49 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:49 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:49 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:49 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:49 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:17:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:06 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:06 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:06 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:06 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:06 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:12 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:12 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:12 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:12 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:59 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:59 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:59 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:59 node-3 multipathd: uevent trigger error
<27>Jul 31 22:18:59 node-3 multipathd: uevent trigger error
<27>Jul 31 22:19:10 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 31 22:20:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:20:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:20:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:20:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:20:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:20:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:20:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:20:25 node-3 multipathd: uevent trigger error
<27>Jul 31 22:20:25 node-3 multipathd: uevent trigger error
<11>Jul 31 22:20:38 node-3 liberasurecode[23616]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:38 node-3 liberasurecode[23616]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:38 node-3 liberasurecode[23616]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:38 node-3 liberasurecode[23616]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:38 node-3 liberasurecode[23640]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:38 node-3 liberasurecode[23640]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:38 node-3 liberasurecode[23640]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:38 node-3 liberasurecode[23640]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:41 node-3 liberasurecode[24856]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:41 node-3 liberasurecode[24856]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:41 node-3 liberasurecode[24856]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:41 node-3 liberasurecode[24856]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:46 node-3 liberasurecode[26456]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:46 node-3 liberasurecode[26456]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:46 node-3 liberasurecode[26456]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:46 node-3 liberasurecode[26456]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:46 node-3 liberasurecode[26496]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:46 node-3 liberasurecode[26496]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:46 node-3 liberasurecode[26496]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:46 node-3 liberasurecode[26496]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26541]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26541]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26541]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26541]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26598]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26598]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26598]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26598]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26615]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26615]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26615]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26615]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26629]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26629]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26629]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26629]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26641]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26641]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26641]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:20:47 node-3 liberasurecode[26641]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:03 node-3 liberasurecode[27488]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:03 node-3 liberasurecode[27488]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:04 node-3 liberasurecode[27488]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:21:04 node-3 liberasurecode[27488]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 22:21:12 node-3 multipathd: uevent trigger error
<27>Jul 31 22:21:12 node-3 multipathd: uevent trigger error
<27>Jul 31 22:21:12 node-3 multipathd: uevent trigger error
<27>Jul 31 22:21:12 node-3 multipathd: uevent trigger error
<27>Jul 31 22:21:12 node-3 multipathd: uevent trigger error
<43>Jul 31 22:22:06 node-3 apache2_error [Sun Jul 31 22:21:58.458515 2016] [mpm_worker:notice] [pid 2459:tid 140298238334848] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 22:22:06 node-3 apache2_error [Sun Jul 31 22:21:58.842907 2016] [mpm_worker:warn] [pid 2459:tid 140298238334848] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 22:22:06 node-3 apache2_error [Sun Jul 31 22:21:58.848107 2016] [mpm_worker:notice] [pid 2459:tid 140298238334848] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 22:22:06 node-3 apache2_error [Sun Jul 31 22:21:58.848140 2016] [core:notice] [pid 2459:tid 140298238334848] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 22:22:11 node-3 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 31 22:22:36 node-3 apache2_error [Sun Jul 31 22:22:35.882982 2016] [mpm_worker:notice] [pid 2459:tid 140298238334848] AH00297: SIGUSR1 received.  Doing graceful restart
<27>Jul 31 22:22:39 node-3 multipathd: uevent trigger error
<27>Jul 31 22:22:39 node-3 multipathd: uevent trigger error
<27>Jul 31 22:22:39 node-3 multipathd: uevent trigger error
<27>Jul 31 22:22:39 node-3 multipathd: uevent trigger error
<27>Jul 31 22:22:39 node-3 multipathd: uevent trigger error
<43>Jul 31 22:22:46 node-3 apache2_error [Sun Jul 31 22:22:36.080402 2016] [mpm_worker:warn] [pid 2459:tid 140298238334848] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 22:22:46 node-3 apache2_error [Sun Jul 31 22:22:36.090605 2016] [mpm_worker:notice] [pid 2459:tid 140298238334848] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 22:22:46 node-3 apache2_error [Sun Jul 31 22:22:36.090637 2016] [core:notice] [pid 2459:tid 140298238334848] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 31 22:23:16 node-3 apache2_error [Sun Jul 31 22:23:13.995435 2016] [mpm_worker:notice] [pid 2459:tid 140298238334848] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 31 22:23:16 node-3 apache2_error [Sun Jul 31 22:23:14.190489 2016] [mpm_worker:warn] [pid 2459:tid 140298238334848] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 31 22:23:16 node-3 apache2_error [Sun Jul 31 22:23:14.199669 2016] [mpm_worker:notice] [pid 2459:tid 140298238334848] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 31 22:23:16 node-3 apache2_error [Sun Jul 31 22:23:14.199696 2016] [core:notice] [pid 2459:tid 140298238334848] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 31 22:23:17 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:17 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:17 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:17 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:17 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:24 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:24 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:24 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:24 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:24 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:30 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:30 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:30 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:30 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:55 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:55 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:55 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:55 node-3 multipathd: uevent trigger error
<27>Jul 31 22:23:55 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:16 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:23 node-3 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 31 22:24:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:38 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:38 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:38 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:38 node-3 multipathd: uevent trigger error
<27>Jul 31 22:24:38 node-3 multipathd: uevent trigger error
<11>Jul 31 22:25:01 node-3 liberasurecode[12459]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:25:01 node-3 liberasurecode[12459]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:25:01 node-3 liberasurecode[12459]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:25:01 node-3 liberasurecode[12459]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 22:25:19 node-3 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 31 22:27:27 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:27 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:27 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:27 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:27 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:33 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:41 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:41 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:41 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:41 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:41 node-3 multipathd: uevent trigger error
<129>Jul 31 22:27:52 node-3 haproxy[6718]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 31 22:27:52 node-3 haproxy[6718]: 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.
<27>Jul 31 22:27:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:27:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:16 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:16 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:16 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:16 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:16 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:22 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:22 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:22 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:22 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:22 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:35 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:35 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:35 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:35 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:35 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:40 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:28:53 node-3 multipathd: uevent trigger error
<27>Jul 31 22:29:04 node-3 multipathd: uevent trigger error
<27>Jul 31 22:29:04 node-3 multipathd: uevent trigger error
<27>Jul 31 22:29:04 node-3 multipathd: uevent trigger error
<27>Jul 31 22:29:04 node-3 multipathd: uevent trigger error
<129>Jul 31 22:29:11 node-3 haproxy[6718]: 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.
<27>Jul 31 22:29:55 node-3 multipathd: uevent trigger error
<27>Jul 31 22:29:55 node-3 multipathd: uevent trigger error
<27>Jul 31 22:29:55 node-3 multipathd: uevent trigger error
<27>Jul 31 22:29:55 node-3 multipathd: uevent trigger error
<27>Jul 31 22:29:55 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:00 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:00 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:00 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:00 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:00 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:00 node-3 multipathd: uevent trigger error
<11>Jul 31 22:30:01 node-3 liberasurecode[12598]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:30:01 node-3 liberasurecode[12598]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:30:01 node-3 liberasurecode[12598]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 31 22:30:01 node-3 liberasurecode[12598]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 31 22:30:05 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:05 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:05 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:05 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:05 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:09 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:10 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:10 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:10 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:10 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:14 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:18 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:19 node-3 multipathd: uevent trigger error
<27>Jul 31 22:30:19 node-3 multipathd: uevent trigger error
