Jul 21 20:58:17 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8414" x-info="http://www.rsyslog.com"] start
Jul 21 20:58:17 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 21 20:58:17 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 21 20:58:17 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 21 20:58:17 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 21 20:58:17 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 21 20:58:17 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 21 20:58:17 node-2 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 21 20:58:17 node-2 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=a7f21ac5-6189-49d0-afe7-8d9b154cd9ca nomdmonddf nomdmonisw
Jul 21 20:58:17 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 21 20:58:17 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 21 20:58:17 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 21 20:58:17 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 21 20:58:17 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 21 20:58:17 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 21 20:58:17 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 21 20:58:17 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 21 20:58:17 node-2 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 21 20:58:17 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 21 20:58:17 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 21 20:58:17 node-2 kernel: [    0.000000] No AGP bridge found
Jul 21 20:58:17 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 21 20:58:17 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 21 20:58:17 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 21 20:58:17 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 21 20:58:17 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 21 20:58:17 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 21 20:58:17 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 21 20:58:17 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 21 20:58:17 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 21 20:58:17 node-2 kernel: [    0.000000]   2 disabled
Jul 21 20:58:17 node-2 kernel: [    0.000000]   3 disabled
Jul 21 20:58:17 node-2 kernel: [    0.000000]   4 disabled
Jul 21 20:58:17 node-2 kernel: [    0.000000]   5 disabled
Jul 21 20:58:17 node-2 kernel: [    0.000000]   6 disabled
Jul 21 20:58:17 node-2 kernel: [    0.000000]   7 disabled
Jul 21 20:58:17 node-2 kernel: [    0.000000]   8 disabled
Jul 21 20:58:17 node-2 kernel: [    0.000000]   9 disabled
Jul 21 20:58:17 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 21 20:58:17 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 21 20:58:17 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 21 20:58:17 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 21 20:58:17 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 21 20:58:17 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 21 20:58:17 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 21 20:58:17 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 21 20:58:17 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 21 20:58:17 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 21 20:58:17 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 21 20:58:17 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 21 20:58:17 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 21 20:58:17 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 21 20:58:17 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 21 20:58:17 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 21 20:58:17 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 21 20:58:17 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 21 20:58:17 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 21 20:58:17 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 21 20:58:17 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 21 20:58:17 node-2 kernel: [    0.000000] Zone ranges:
Jul 21 20:58:17 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 21 20:58:17 node-2 kernel: [    0.000000] Early memory node ranges
Jul 21 20:58:17 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 21 20:58:17 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 21 20:58:17 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 21 20:58:17 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 21 20:58:17 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 21 20:58:17 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 21 20:58:17 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 21 20:58:17 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 21 20:58:17 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 21 20:58:17 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 21 20:58:17 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 21 20:58:17 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 21 20:58:17 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 21 20:58:17 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 21 20:58:17 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 21 20:58:17 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 21 20:58:17 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 21 20:58:17 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 21 20:58:17 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 21 20:58:17 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 21 20:58:17 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 21 20:58:17 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 21 20:58:17 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 21 20:58:17 node-2 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 21 20:58:17 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 21 20:58:17 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 21 20:58:17 node-2 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=a7f21ac5-6189-49d0-afe7-8d9b154cd9ca nomdmonddf nomdmonisw
Jul 21 20:58:17 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 21 20:58:17 node-2 kernel: [    0.000000] Checking aperture...
Jul 21 20:58:17 node-2 kernel: [    0.000000] No AGP bridge found
Jul 21 20:58:17 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 21 20:58:17 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 21 20:58:17 node-2 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 21 20:58:17 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 21 20:58:17 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 21 20:58:17 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 21 20:58:17 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 21 20:58:17 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 21 20:58:17 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 21 20:58:17 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 21 20:58:17 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 21 20:58:17 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 21 20:58:17 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 21 20:58:17 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 21 20:58:17 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 21 20:58:17 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 21 20:58:17 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 21 20:58:17 node-2 kernel: [    0.004000] tsc: Detected 3491.781 MHz processor
Jul 21 20:58:17 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.56 BogoMIPS (lpj=13967124)
Jul 21 20:58:17 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 21 20:58:17 node-2 kernel: [    0.000046] Security Framework initialized
Jul 21 20:58:17 node-2 kernel: [    0.000064] AppArmor: AppArmor initialized
Jul 21 20:58:17 node-2 kernel: [    0.000066] Yama: becoming mindful.
Jul 21 20:58:17 node-2 kernel: [    0.001459] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.006418] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.008350] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.008378] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.008668] Initializing cgroup subsys memory
Jul 21 20:58:17 node-2 kernel: [    0.008676] Initializing cgroup subsys devices
Jul 21 20:58:17 node-2 kernel: [    0.008678] Initializing cgroup subsys freezer
Jul 21 20:58:17 node-2 kernel: [    0.008680] Initializing cgroup subsys blkio
Jul 21 20:58:17 node-2 kernel: [    0.008681] Initializing cgroup subsys perf_event
Jul 21 20:58:17 node-2 kernel: [    0.008684] Initializing cgroup subsys hugetlb
Jul 21 20:58:17 node-2 kernel: [    0.008703] CPU: Physical Processor ID: 0
Jul 21 20:58:17 node-2 kernel: [    0.008704] CPU: Processor Core ID: 0
Jul 21 20:58:17 node-2 kernel: [    0.008708] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 21 20:58:17 node-2 kernel: [    0.008708] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 21 20:58:17 node-2 kernel: [    0.009402] mce: CPU supports 22 MCE banks
Jul 21 20:58:17 node-2 kernel: [    0.009429] CPU0: Thermal monitoring enabled (TM1)
Jul 21 20:58:17 node-2 kernel: [    0.009450] process: using mwait in idle threads
Jul 21 20:58:17 node-2 kernel: [    0.009453] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 21 20:58:17 node-2 kernel: [    0.009453] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 21 20:58:17 node-2 kernel: [    0.009453] tlb_flushall_shift: 6
Jul 21 20:58:17 node-2 kernel: [    0.009542] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 21 20:58:17 node-2 kernel: [    0.010266] ACPI: Core revision 20131115
Jul 21 20:58:17 node-2 kernel: [    0.022925] ACPI: All ACPI Tables successfully acquired
Jul 21 20:58:17 node-2 kernel: [    0.023097] ftrace: allocating 28617 entries in 112 pages
Jul 21 20:58:17 node-2 kernel: [    0.031899] dmar: Host address width 46
Jul 21 20:58:17 node-2 kernel: [    0.031901] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 21 20:58:17 node-2 kernel: [    0.031907] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 21 20:58:17 node-2 kernel: [    0.031909] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 21 20:58:17 node-2 kernel: [    0.031913] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 21 20:58:17 node-2 kernel: [    0.031914] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 21 20:58:17 node-2 kernel: [    0.031915] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 21 20:58:17 node-2 kernel: [    0.031917] dmar: ATSR flags: 0x0
Jul 21 20:58:17 node-2 kernel: [    0.031918] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 21 20:58:17 node-2 kernel: [    0.031919] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 21 20:58:17 node-2 kernel: [    0.032034] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 21 20:58:17 node-2 kernel: [    0.032035] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 21 20:58:17 node-2 kernel: [    0.032036] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 21 20:58:17 node-2 kernel: [    0.032037] HPET id 0 under DRHD base 0xc7ffc000
Jul 21 20:58:17 node-2 kernel: [    0.032038] Your BIOS is broken and requested that x2apic be disabled.
Jul 21 20:58:17 node-2 kernel: [    0.032038] This will slightly decrease performance.
Jul 21 20:58:17 node-2 kernel: [    0.032038] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 21 20:58:17 node-2 kernel: [    0.032470] Enabled IRQ remapping in xapic mode
Jul 21 20:58:17 node-2 kernel: [    0.032472] x2apic not enabled, IRQ remapping is in xapic mode
Jul 21 20:58:17 node-2 kernel: [    0.032475] Switched APIC routing to physical flat.
Jul 21 20:58:17 node-2 kernel: [    0.033101] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 21 20:58:17 node-2 kernel: [    0.072749] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 21 20:58:17 node-2 kernel: [    0.072754] TSC deadline timer enabled
Jul 21 20:58:17 node-2 kernel: [    0.072762] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 21 20:58:17 node-2 kernel: [    0.072768] ... version:                3
Jul 21 20:58:17 node-2 kernel: [    0.072769] ... bit width:              48
Jul 21 20:58:17 node-2 kernel: [    0.072769] ... generic registers:      4
Jul 21 20:58:17 node-2 kernel: [    0.072770] ... value mask:             0000ffffffffffff
Jul 21 20:58:17 node-2 kernel: [    0.072771] ... max period:             0000ffffffffffff
Jul 21 20:58:17 node-2 kernel: [    0.072772] ... fixed-purpose events:   3
Jul 21 20:58:17 node-2 kernel: [    0.072773] ... event mask:             000000070000000f
Jul 21 20:58:17 node-2 kernel: [    0.074194] x86: Booting SMP configuration:
Jul 21 20:58:17 node-2 kernel: [    0.088297] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 21 20:58:17 node-2 kernel: [    0.074196] .... node  #0, CPUs:        #1  #2  #3
Jul 21 20:58:17 node-2 kernel: [    0.116203] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 21 20:58:17 node-2 kernel: [    0.270332] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 21 20:58:17 node-2 kernel: [    0.325942] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 21 20:58:17 node-2 kernel: [    0.382387] x86: Booted up 2 nodes, 16 CPUs
Jul 21 20:58:17 node-2 kernel: [    0.382390] smpboot: Total of 16 processors activated (111749.35 BogoMIPS)
Jul 21 20:58:17 node-2 kernel: [    0.405714] devtmpfs: initialized
Jul 21 20:58:17 node-2 kernel: [    0.408812] EVM: security.selinux
Jul 21 20:58:17 node-2 kernel: [    0.408813] EVM: security.SMACK64
Jul 21 20:58:17 node-2 kernel: [    0.408814] EVM: security.ima
Jul 21 20:58:17 node-2 kernel: [    0.408815] EVM: security.capability
Jul 21 20:58:17 node-2 kernel: [    0.408865] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.409536] pinctrl core: initialized pinctrl subsystem
Jul 21 20:58:17 node-2 kernel: [    0.409598] regulator-dummy: no parameters
Jul 21 20:58:17 node-2 kernel: [    0.409629] RTC time: 20:57:41, date: 07/21/16
Jul 21 20:58:17 node-2 kernel: [    0.409664] NET: Registered protocol family 16
Jul 21 20:58:17 node-2 kernel: [    0.409748] cpuidle: using governor ladder
Jul 21 20:58:17 node-2 kernel: [    0.409749] cpuidle: using governor menu
Jul 21 20:58:17 node-2 kernel: [    0.409784] ACPI: bus type PCI registered
Jul 21 20:58:17 node-2 kernel: [    0.409786] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 21 20:58:17 node-2 kernel: [    0.409832] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 21 20:58:17 node-2 kernel: [    0.409835] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 21 20:58:17 node-2 kernel: [    0.423562] PCI: Using configuration type 1 for base access
Jul 21 20:58:17 node-2 kernel: [    0.424552] bio: create slab <bio-0> at 0
Jul 21 20:58:17 node-2 kernel: [    0.424825] ACPI: Added _OSI(Module Device)
Jul 21 20:58:17 node-2 kernel: [    0.424827] ACPI: Added _OSI(Processor Device)
Jul 21 20:58:17 node-2 kernel: [    0.424828] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 21 20:58:17 node-2 kernel: [    0.424829] ACPI: Added _OSI(Processor Aggregator Device)
Jul 21 20:58:17 node-2 kernel: [    0.437496] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 21 20:58:17 node-2 kernel: [    0.449098] ACPI: Interpreter enabled
Jul 21 20:58:17 node-2 kernel: [    0.449104] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 21 20:58:17 node-2 kernel: [    0.449108] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 21 20:58:17 node-2 kernel: [    0.449111] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 21 20:58:17 node-2 kernel: [    0.449117] ACPI: (supports S0 S4 S5)
Jul 21 20:58:17 node-2 kernel: [    0.449119] ACPI: Using IOAPIC for interrupt routing
Jul 21 20:58:17 node-2 kernel: [    0.449163] HEST: Table parsing has been initialized.
Jul 21 20:58:17 node-2 kernel: [    0.449165] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 21 20:58:17 node-2 kernel: [    0.449719] ACPI: No dock devices found.
Jul 21 20:58:17 node-2 kernel: [    0.461269] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 21 20:58:17 node-2 kernel: [    0.461273] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 21 20:58:17 node-2 kernel: [    0.461277] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 21 20:58:17 node-2 kernel: [    0.461307] PCI host bridge to bus 0000:ff
Jul 21 20:58:17 node-2 kernel: [    0.461309] pci_bus 0000:ff: root bus resource [bus ff]
Jul 21 20:58:17 node-2 kernel: [    0.461317] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461354] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.461384] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461419] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461447] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.461477] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.461507] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461536] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461566] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461594] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461620] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461646] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461673] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461699] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461725] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461750] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461779] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461806] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461832] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.461859] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461884] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.461909] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461935] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.461964] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.461997] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462027] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462056] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462086] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462116] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462146] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462176] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462206] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462236] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462270] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462302] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462334] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462367] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462397] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462424] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462457] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462490] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462527] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462559] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462592] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462621] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462652] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462681] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462709] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462739] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462769] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462800] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462828] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462856] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462885] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462914] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462945] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.462976] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463033] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 21 20:58:17 node-2 kernel: [    0.463036] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 21 20:58:17 node-2 kernel: [    0.463039] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 21 20:58:17 node-2 kernel: [    0.463056] PCI host bridge to bus 0000:7f
Jul 21 20:58:17 node-2 kernel: [    0.463058] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 21 20:58:17 node-2 kernel: [    0.463063] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463090] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.463119] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463148] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463170] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.463195] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.463221] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463248] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463270] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463296] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463325] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463349] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463375] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463399] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463424] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463450] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463471] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463494] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463517] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.463540] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463563] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.463585] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463607] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463634] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 21 20:58:17 node-2 kernel: [    0.463667] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463693] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463719] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463746] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463771] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463799] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463827] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463856] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463880] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463908] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463936] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463964] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.463993] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464019] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464044] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464072] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464097] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464123] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464153] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464180] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464206] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464233] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464261] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464288] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464312] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464339] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464369] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464394] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464416] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464441] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464467] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464497] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.464523] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.465774] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 21 20:58:17 node-2 kernel: [    0.465778] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 21 20:58:17 node-2 kernel: [    0.466902] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 21 20:58:17 node-2 kernel: [    0.467419] PCI host bridge to bus 0000:00
Jul 21 20:58:17 node-2 kernel: [    0.467422] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 21 20:58:17 node-2 kernel: [    0.467423] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 21 20:58:17 node-2 kernel: [    0.467425] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 21 20:58:17 node-2 kernel: [    0.467426] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 21 20:58:17 node-2 kernel: [    0.467427] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 21 20:58:17 node-2 kernel: [    0.467429] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 21 20:58:17 node-2 kernel: [    0.467430] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 21 20:58:17 node-2 kernel: [    0.467436] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 21 20:58:17 node-2 kernel: [    0.467519] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.467549] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.467591] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 21 20:58:17 node-2 kernel: [    0.467610] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.467640] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.467680] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 21 20:58:17 node-2 kernel: [    0.467698] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.467728] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.467768] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 21 20:58:17 node-2 kernel: [    0.467785] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.467856] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.467934] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.468010] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 21 20:58:17 node-2 kernel: [    0.468015] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 21 20:58:17 node-2 kernel: [    0.468100] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 21 20:58:17 node-2 kernel: [    0.468248] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 21 20:58:17 node-2 kernel: [    0.468266] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 21 20:58:17 node-2 kernel: [    0.468343] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.468398] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 21 20:58:17 node-2 kernel: [    0.468420] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.468475] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.468519] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 21 20:58:17 node-2 kernel: [    0.468547] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.468602] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.468645] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 21 20:58:17 node-2 kernel: [    0.468669] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 21 20:58:17 node-2 kernel: [    0.468687] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 21 20:58:17 node-2 kernel: [    0.468764] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.468813] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 21 20:58:17 node-2 kernel: [    0.468840] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 21 20:58:17 node-2 kernel: [    0.469088] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 21 20:58:17 node-2 kernel: [    0.469093] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 21 20:58:17 node-2 kernel: [    0.469099] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.469105] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.469112] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 21 20:58:17 node-2 kernel: [    0.469142] pci 0000:01:00.0: supports D1 D2
Jul 21 20:58:17 node-2 kernel: [    0.479319] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 21 20:58:17 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 21 20:58:17 node-2 kernel: [    0.479325] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 21 20:58:17 node-2 kernel: [    0.479329] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 21 20:58:17 node-2 kernel: [    0.479590] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.479624] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 21 20:58:17 node-2 kernel: [    0.487315] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 21 20:58:17 node-2 kernel: [    0.487321] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.487325] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 21 20:58:17 node-2 kernel: [    0.487405] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.487491] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.487567] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.487613] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 21 20:58:17 node-2 kernel: [    0.487616] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.487618] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 21 20:58:17 node-2 kernel: [    0.487671] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.487793] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.487847] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 21 20:58:17 node-2 kernel: [    0.487849] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.487851] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 21 20:58:17 node-2 kernel: [    0.487900] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.488022] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.488064] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.488184] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.488220] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.488340] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.488375] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 21 20:58:17 node-2 kernel: [    0.488514] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 21 20:58:17 node-2 kernel: [    0.488557] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 21 20:58:17 node-2 kernel: [    0.488560] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.488562] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 21 20:58:17 node-2 kernel: [    0.488622] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 21 20:58:17 node-2 kernel: [    0.488684] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.488736] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.488778] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 21 20:58:17 node-2 kernel: [    0.488859] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 21 20:58:17 node-2 kernel: [    0.488967] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 21 20:58:17 node-2 kernel: [    0.488969] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.488971] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 21 20:58:17 node-2 kernel: [    0.489027] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 21 20:58:17 node-2 kernel: [    0.489080] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.489129] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.489339] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 21 20:58:17 node-2 kernel: [    0.489343] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 21 20:58:17 node-2 kernel: [    0.489406] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 21 20:58:17 node-2 kernel: [    0.489483] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.489531] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.489739] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 21 20:58:17 node-2 kernel: [    0.489742] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 21 20:58:17 node-2 kernel: [    0.489802] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 21 20:58:17 node-2 kernel: [    0.489862] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.489915] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 21 20:58:17 node-2 kernel: [    0.490140] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 21 20:58:17 node-2 kernel: [    0.490143] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 21 20:58:17 node-2 kernel: [    0.490317] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 21 20:58:17 node-2 kernel: [    0.490355] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 21 20:58:17 node-2 kernel: [    0.490436] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 21 20:58:17 node-2 kernel: [    0.490455] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 21 20:58:17 node-2 kernel: [    0.490468] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 21 20:58:17 node-2 kernel: [    0.490481] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 21 20:58:17 node-2 kernel: [    0.490531] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 21 20:58:17 node-2 kernel: [    0.495321] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 21 20:58:17 node-2 kernel: [    0.495330] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 21 20:58:17 node-2 kernel: [    0.495382] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 21 20:58:17 node-2 kernel: [    0.496127] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 21 20:58:17 node-2 kernel: [    0.496130] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 21 20:58:17 node-2 kernel: [    0.496250] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 21 20:58:17 node-2 kernel: [    0.496358] PCI host bridge to bus 0000:80
Jul 21 20:58:17 node-2 kernel: [    0.496360] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 21 20:58:17 node-2 kernel: [    0.496362] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 21 20:58:17 node-2 kernel: [    0.496363] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 21 20:58:17 node-2 kernel: [    0.496371] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.496435] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.496501] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 21 20:58:17 node-2 kernel: [    0.496572] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 21 20:58:17 node-2 kernel: [    0.496577] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 21 20:58:17 node-2 kernel: [    0.496648] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 21 20:58:17 node-2 kernel: [    0.496945] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 21 20:58:17 node-2 kernel: [    0.496976] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 21 20:58:17 node-2 kernel: [    0.497006] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 21 20:58:17 node-2 kernel: [    0.497034] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 21 20:58:17 node-2 kernel: [    0.497064] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 21 20:58:17 node-2 kernel: [    0.497094] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 21 20:58:17 node-2 kernel: [    0.497123] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 21 20:58:17 node-2 kernel: [    0.497153] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 21 20:58:17 node-2 kernel: [    0.497237] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 21 20:58:17 node-2 kernel: [    0.497241] ACPI: \_SB_.UNC1: notify handler is installed
Jul 21 20:58:17 node-2 kernel: [    0.497243] ACPI: \_SB_.UNC0: notify handler is installed
Jul 21 20:58:17 node-2 kernel: [    0.497257] ACPI: \_SB_.PCI0: notify handler is installed
Jul 21 20:58:17 node-2 kernel: [    0.497311] ACPI: \_SB_.PCI1: notify handler is installed
Jul 21 20:58:17 node-2 kernel: [    0.497390] Found 4 acpi root devices
Jul 21 20:58:17 node-2 kernel: [    0.497498] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 21 20:58:17 node-2 kernel: [    0.497500] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 21 20:58:17 node-2 kernel: [    0.497502] vgaarb: loaded
Jul 21 20:58:17 node-2 kernel: [    0.497503] vgaarb: bridge control possible 0000:0c:00.0
Jul 21 20:58:17 node-2 kernel: [    0.497619] SCSI subsystem initialized
Jul 21 20:58:17 node-2 kernel: [    0.497685] libata version 3.00 loaded.
Jul 21 20:58:17 node-2 kernel: [    0.497701] ACPI: bus type USB registered
Jul 21 20:58:17 node-2 kernel: [    0.497711] usbcore: registered new interface driver usbfs
Jul 21 20:58:17 node-2 kernel: [    0.497716] usbcore: registered new interface driver hub
Jul 21 20:58:17 node-2 kernel: [    0.497741] usbcore: registered new device driver usb
Jul 21 20:58:17 node-2 kernel: [    0.497910] PCI: Using ACPI for IRQ routing
Jul 21 20:58:17 node-2 kernel: [    0.501510] PCI: pci_cache_line_size set to 64 bytes
Jul 21 20:58:17 node-2 kernel: [    0.501721] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 21 20:58:17 node-2 kernel: [    0.501722] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 21 20:58:17 node-2 kernel: [    0.501723] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 21 20:58:17 node-2 kernel: [    0.501789] NetLabel: Initializing
Jul 21 20:58:17 node-2 kernel: [    0.501791] NetLabel:  domain hash size = 128
Jul 21 20:58:17 node-2 kernel: [    0.501792] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 21 20:58:17 node-2 kernel: [    0.501801] NetLabel:  unlabeled traffic allowed by default
Jul 21 20:58:17 node-2 kernel: [    0.501857] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 21 20:58:17 node-2 kernel: [    0.501861] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 21 20:58:17 node-2 kernel: [    0.503918] Switched to clocksource hpet
Jul 21 20:58:17 node-2 kernel: [    0.507891] AppArmor: AppArmor Filesystem Enabled
Jul 21 20:58:17 node-2 kernel: [    0.507905] pnp: PnP ACPI init
Jul 21 20:58:17 node-2 kernel: [    0.507918] ACPI: bus type PNP registered
Jul 21 20:58:17 node-2 kernel: [    0.508028] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 21 20:58:17 node-2 kernel: [    0.508036] pnp 00:01: [dma 4]
Jul 21 20:58:17 node-2 kernel: [    0.508048] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 21 20:58:17 node-2 kernel: [    0.508075] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 21 20:58:17 node-2 kernel: [    0.508094] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 21 20:58:17 node-2 kernel: [    0.508112] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 21 20:58:17 node-2 kernel: [    0.508145] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 21 20:58:17 node-2 kernel: [    0.508199] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508201] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 21 20:58:17 node-2 kernel: [    0.508202] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508204] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508205] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508209] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508211] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 21 20:58:17 node-2 kernel: [    0.508212] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508214] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508215] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508217] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508218] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508220] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 21 20:58:17 node-2 kernel: [    0.508222] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 21 20:58:17 node-2 kernel: [    0.508307] pnp 00:07: [dma 0 disabled]
Jul 21 20:58:17 node-2 kernel: [    0.508335] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 21 20:58:17 node-2 kernel: [    0.508409] pnp 00:08: [dma 0 disabled]
Jul 21 20:58:17 node-2 kernel: [    0.508441] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 21 20:58:17 node-2 kernel: [    0.508491] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 21 20:58:17 node-2 kernel: [    0.508837] pnp: PnP ACPI: found 10 devices
Jul 21 20:58:17 node-2 kernel: [    0.508839] ACPI: bus type PNP unregistered
Jul 21 20:58:17 node-2 kernel: [    0.515132] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 21 20:58:17 node-2 kernel: [    0.515135] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 21 20:58:17 node-2 kernel: [    0.515138] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 21 20:58:17 node-2 kernel: [    0.515142] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 21 20:58:17 node-2 kernel: [    0.515144] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.515158] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515188] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 21 20:58:17 node-2 kernel: [    0.515202] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515231] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 21 20:58:17 node-2 kernel: [    0.515245] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 21 20:58:17 node-2 kernel: [    0.515274] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 21 20:58:17 node-2 kernel: [    0.515289] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 21 20:58:17 node-2 kernel: [    0.515321] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 21 20:58:17 node-2 kernel: [    0.515323] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.515337] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515366] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 21 20:58:17 node-2 kernel: [    0.515368] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.515382] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515411] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 21 20:58:17 node-2 kernel: [    0.515413] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.515416] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515420] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 21 20:58:17 node-2 kernel: [    0.515421] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.515424] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515428] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 21 20:58:17 node-2 kernel: [    0.515432] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 21 20:58:17 node-2 kernel: [    0.515440] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 21 20:58:17 node-2 kernel: [    0.515444] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 21 20:58:17 node-2 kernel: [    0.515450] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 21 20:58:17 node-2 kernel: [    0.515451] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 21 20:58:17 node-2 kernel: [    0.515452] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 21 20:58:17 node-2 kernel: [    0.515453] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 21 20:58:17 node-2 kernel: [    0.515454] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 21 20:58:17 node-2 kernel: [    0.515455] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 21 20:58:17 node-2 kernel: [    0.515456] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 21 20:58:17 node-2 kernel: [    0.515456] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 21 20:58:17 node-2 kernel: [    0.515457] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.515458] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515459] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.515460] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515461] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.515462] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515463] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.515463] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515464] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 21 20:58:17 node-2 kernel: [    0.515465] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515466] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 21 20:58:17 node-2 kernel: [    0.515467] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 21 20:58:17 node-2 kernel: [    0.515468] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 21 20:58:17 node-2 kernel: [    0.515469] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 21 20:58:17 node-2 kernel: [    0.515471] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 21 20:58:17 node-2 kernel: [    0.515472] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 21 20:58:17 node-2 kernel: [    0.515510] NET: Registered protocol family 2
Jul 21 20:58:17 node-2 kernel: [    0.515772] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.516107] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.516254] TCP: Hash tables configured (established 262144 bind 65536)
Jul 21 20:58:17 node-2 kernel: [    0.516292] TCP: reno registered
Jul 21 20:58:17 node-2 kernel: [    0.516320] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.516417] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.516561] NET: Registered protocol family 1
Jul 21 20:58:17 node-2 kernel: [    0.552017] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 21 20:58:17 node-2 kernel: [    0.552030] PCI: CLS 64 bytes, default 64
Jul 21 20:58:17 node-2 kernel: [    0.552107] Trying to unpack rootfs image as initramfs...
Jul 21 20:58:17 node-2 kernel: [    0.771359] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 21 20:58:17 node-2 kernel: [    0.771405] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 21 20:58:17 node-2 kernel: [    0.771408] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 21 20:58:17 node-2 kernel: [    0.771818] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771824] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771829] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771835] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771847] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771877] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771886] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771895] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771903] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771912] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771918] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771924] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771931] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771939] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771946] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.771954] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 21 20:58:17 node-2 kernel: [    0.772032] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 21 20:58:17 node-2 kernel: [    0.772035] Scanning for low memory corruption every 60 seconds
Jul 21 20:58:17 node-2 kernel: [    0.772415] Initialise system trusted keyring
Jul 21 20:58:17 node-2 kernel: [    0.772467] audit: initializing netlink socket (disabled)
Jul 21 20:58:17 node-2 kernel: [    0.772483] type=2000 audit(1469134660.728:1): initialized
Jul 21 20:58:17 node-2 kernel: [    0.790375] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 21 20:58:17 node-2 kernel: [    0.791892] zbud: loaded
Jul 21 20:58:17 node-2 kernel: [    0.792018] VFS: Disk quotas dquot_6.5.2
Jul 21 20:58:17 node-2 kernel: [    0.792055] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 21 20:58:17 node-2 kernel: [    0.792437] fuse init (API version 7.22)
Jul 21 20:58:17 node-2 kernel: [    0.792498] msgmni has been set to 32768
Jul 21 20:58:17 node-2 kernel: [    0.792545] Key type big_key registered
Jul 21 20:58:17 node-2 kernel: [    0.793038] Key type asymmetric registered
Jul 21 20:58:17 node-2 kernel: [    0.793040] Asymmetric key parser 'x509' registered
Jul 21 20:58:17 node-2 kernel: [    0.793062] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 21 20:58:17 node-2 kernel: [    0.793130] io scheduler noop registered
Jul 21 20:58:17 node-2 kernel: [    0.793132] io scheduler deadline registered (default)
Jul 21 20:58:17 node-2 kernel: [    0.793150] io scheduler cfq registered
Jul 21 20:58:17 node-2 kernel: [    0.793548] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    0.793668] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    0.793780] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    0.793887] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    0.794002] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    0.794100] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    0.794510] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 21 20:58:17 node-2 kernel: [    0.794542] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 21 20:58:17 node-2 kernel: [    0.794558] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 21 20:58:17 node-2 kernel: [    0.794567] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794569] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794572] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 21 20:58:17 node-2 kernel: [    0.794577] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794578] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794580] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794581] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794583] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794584] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794585] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794587] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794589] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794590] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794591] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794593] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794595] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 21 20:58:17 node-2 kernel: [    0.794600] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794603] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 21 20:58:17 node-2 kernel: [    0.794617] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794620] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 21 20:58:17 node-2 kernel: [    0.794631] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794632] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 21 20:58:17 node-2 kernel: [    0.794636] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 21 20:58:17 node-2 kernel: [    0.794672] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 21 20:58:17 node-2 kernel: [    0.794678] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 21 20:58:17 node-2 kernel: [    0.794683] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 21 20:58:17 node-2 kernel: [    0.794692] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 21 20:58:17 node-2 kernel: [    0.794732] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 21 20:58:17 node-2 kernel: [    0.794733] vesafb: scrolling: redraw
Jul 21 20:58:17 node-2 kernel: [    0.794735] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 21 20:58:17 node-2 kernel: [    0.815330] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 21 20:58:17 node-2 kernel: [    0.823849] Console: switching to colour frame buffer device 80x30
Jul 21 20:58:17 node-2 kernel: [    0.832553] fb0: VESA VGA frame buffer device
Jul 21 20:58:17 node-2 kernel: [    0.832750] intel_idle: MWAIT substates: 0x2120
Jul 21 20:58:17 node-2 kernel: [    0.832751] intel_idle: v0.4 model 0x3F
Jul 21 20:58:17 node-2 kernel: [    0.832752] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 21 20:58:17 node-2 kernel: [    0.832975] ipmi message handler version 39.2
Jul 21 20:58:17 node-2 kernel: [    0.833254] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 21 20:58:17 node-2 kernel: [    0.833708] ACPI: AC Adapter [P111] (on-line)
Jul 21 20:58:17 node-2 kernel: [    0.838989] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 21 20:58:17 node-2 kernel: [    0.849987] ACPI: Power Button [PWRB]
Jul 21 20:58:17 node-2 kernel: [    0.855736] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 21 20:58:17 node-2 kernel: [    0.867353] ACPI: Power Button [PWRF]
Jul 21 20:58:17 node-2 kernel: [    0.885391] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 21 20:58:17 node-2 kernel: [    0.897058] pstore: Registered erst as persistent store backend
Jul 21 20:58:17 node-2 kernel: [    0.903232] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 21 20:58:17 node-2 kernel: [    0.915178] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 21 20:58:17 node-2 kernel: [    0.941909] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 21 20:58:17 node-2 kernel: [    0.975180] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 21 20:58:17 node-2 kernel: [    0.989333] Linux agpgart interface v0.103
Jul 21 20:58:17 node-2 kernel: [    0.996952] brd: module loaded
Jul 21 20:58:17 node-2 kernel: [    1.003970] loop: module loaded
Jul 21 20:58:17 node-2 kernel: [    1.010686] libphy: Fixed MDIO Bus: probed
Jul 21 20:58:17 node-2 kernel: [    1.017170] tun: Universal TUN/TAP device driver, 1.6
Jul 21 20:58:17 node-2 kernel: [    1.023647] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 21 20:58:17 node-2 kernel: [    1.030179] PPP generic driver version 2.4.2
Jul 21 20:58:17 node-2 kernel: [    1.036581] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 21 20:58:17 node-2 kernel: [    1.043024] ehci-pci: EHCI PCI platform driver
Jul 21 20:58:17 node-2 kernel: [    1.049565] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 21 20:58:17 node-2 kernel: [    1.055990] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 21 20:58:17 node-2 kernel: [    1.068547] ehci-pci 0000:00:1a.0: debug port 2
Jul 21 20:58:17 node-2 kernel: [    1.078744] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 21 20:58:17 node-2 kernel: [    1.078761] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 21 20:58:17 node-2 kernel: [    1.095421] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 21 20:58:17 node-2 kernel: [    1.101558] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 21 20:58:17 node-2 kernel: [    1.107737] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 21 20:58:17 node-2 kernel: [    1.119655] usb usb1: Product: EHCI Host Controller
Jul 21 20:58:17 node-2 kernel: [    1.125693] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 21 20:58:17 node-2 kernel: [    1.131746] usb usb1: SerialNumber: 0000:00:1a.0
Jul 21 20:58:17 node-2 kernel: [    1.137710] hub 1-0:1.0: USB hub found
Jul 21 20:58:17 node-2 kernel: [    1.143489] hub 1-0:1.0: 2 ports detected
Jul 21 20:58:17 node-2 kernel: [    1.149287] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 21 20:58:17 node-2 kernel: [    1.154876] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 21 20:58:17 node-2 kernel: [    1.165797] ehci-pci 0000:00:1d.0: debug port 2
Jul 21 20:58:17 node-2 kernel: [    1.175125] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 21 20:58:17 node-2 kernel: [    1.175128] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 21 20:58:17 node-2 kernel: [    1.191339] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 21 20:58:17 node-2 kernel: [    1.196632] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 21 20:58:17 node-2 kernel: [    1.202008] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 21 20:58:17 node-2 kernel: [    1.212721] usb usb2: Product: EHCI Host Controller
Jul 21 20:58:17 node-2 kernel: [    1.218266] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 21 20:58:17 node-2 kernel: [    1.223875] usb usb2: SerialNumber: 0000:00:1d.0
Jul 21 20:58:17 node-2 kernel: [    1.229450] hub 2-0:1.0: USB hub found
Jul 21 20:58:17 node-2 kernel: [    1.234861] hub 2-0:1.0: 2 ports detected
Jul 21 20:58:17 node-2 kernel: [    1.240201] ehci-platform: EHCI generic platform driver
Jul 21 20:58:17 node-2 kernel: [    1.245502] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 21 20:58:17 node-2 kernel: [    1.250861] ohci-pci: OHCI PCI platform driver
Jul 21 20:58:17 node-2 kernel: [    1.256203] ohci-platform: OHCI generic platform driver
Jul 21 20:58:17 node-2 kernel: [    1.261450] uhci_hcd: USB Universal Host Controller Interface driver
Jul 21 20:58:17 node-2 kernel: [    1.266841] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 21 20:58:17 node-2 kernel: [    1.467103] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 21 20:58:17 node-2 kernel: [    1.766862] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 21 20:58:17 node-2 kernel: [    1.783218] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 21 20:58:17 node-2 kernel: [    1.788840] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 21 20:58:17 node-2 kernel: [    1.794611] hub 1-1:1.0: USB hub found
Jul 21 20:58:17 node-2 kernel: [    1.800205] hub 1-1:1.0: 6 ports detected
Jul 21 20:58:17 node-2 kernel: [    1.914723] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 21 20:58:17 node-2 kernel: [    2.305537] i8042: No controller found
Jul 21 20:58:17 node-2 kernel: [    2.311084] mousedev: PS/2 mouse device common for all mice
Jul 21 20:58:17 node-2 kernel: [    2.316826] rtc_cmos 00:02: RTC can wake from S4
Jul 21 20:58:17 node-2 kernel: [    2.319209] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 21 20:58:17 node-2 kernel: [    2.319210] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 21 20:58:17 node-2 kernel: [    2.319845] hub 2-1:1.0: USB hub found
Jul 21 20:58:17 node-2 kernel: [    2.320073] hub 2-1:1.0: 8 ports detected
Jul 21 20:58:17 node-2 kernel: [    2.345242] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 21 20:58:17 node-2 kernel: [    2.351042] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 21 20:58:17 node-2 kernel: [    2.362388] device-mapper: uevent: version 1.0.3
Jul 21 20:58:17 node-2 kernel: [    2.368122] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 21 20:58:17 node-2 kernel: [    2.379534] ledtrig-cpu: registered to indicate activity on CPUs
Jul 21 20:58:17 node-2 kernel: [    2.385513] TCP: cubic registered
Jul 21 20:58:17 node-2 kernel: [    2.391397] NET: Registered protocol family 10
Jul 21 20:58:17 node-2 kernel: [    2.397462] NET: Registered protocol family 17
Jul 21 20:58:17 node-2 kernel: [    2.403254] Key type dns_resolver registered
Jul 21 20:58:17 node-2 kernel: [    2.409333] Loading compiled-in X.509 certificates
Jul 21 20:58:17 node-2 kernel: [    2.415565] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 21 20:58:17 node-2 kernel: [    2.427238] registered taskstats version 1
Jul 21 20:58:17 node-2 kernel: [    2.435383] Key type trusted registered
Jul 21 20:58:17 node-2 kernel: [    2.443048] Key type encrypted registered
Jul 21 20:58:17 node-2 kernel: [    2.448574] AppArmor: AppArmor sha1 policy hashing enabled
Jul 21 20:58:17 node-2 kernel: [    2.454109] IMA: No TPM chip found, activating TPM-bypass!
Jul 21 20:58:17 node-2 kernel: [    2.460190] regulator-dummy: disabling
Jul 21 20:58:17 node-2 kernel: [    2.465708]   Magic number: 8:150:1004
Jul 21 20:58:17 node-2 kernel: [    2.471218] input input1: hash matches
Jul 21 20:58:17 node-2 kernel: [    2.476617] system 00:06: hash matches
Jul 21 20:58:17 node-2 kernel: [    2.482033] memory memory43: hash matches
Jul 21 20:58:17 node-2 kernel: [    2.487294] rtc_cmos 00:02: setting system clock to 2016-07-21 20:57:43 UTC (1469134663)
Jul 21 20:58:17 node-2 kernel: [    2.499356] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 21 20:58:17 node-2 kernel: [    2.504781] EDD information not available.
Jul 21 20:58:17 node-2 kernel: [    2.510163] PM: Hibernation image not present or could not be loaded.
Jul 21 20:58:17 node-2 kernel: [    2.511020] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 21 20:58:17 node-2 kernel: [    2.522090] Write protecting the kernel read-only data: 12288k
Jul 21 20:58:17 node-2 kernel: [    2.528256] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 21 20:58:17 node-2 kernel: [    2.540591] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 21 20:58:17 node-2 kernel: [    2.572345] device-mapper: multipath: version 1.6.0 loaded
Jul 21 20:58:17 node-2 kernel: [    2.579873] systemd-udevd[216]: starting version 204
Jul 21 20:58:17 node-2 kernel: [    2.602145] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 21 20:58:17 node-2 kernel: [    2.614720] md: linear personality registered for level -1
Jul 21 20:58:17 node-2 kernel: [    2.622536] md: multipath personality registered for level -4
Jul 21 20:58:17 node-2 kernel: [    2.631082] md: raid0 personality registered for level 0
Jul 21 20:58:17 node-2 kernel: [    2.638886] md: raid1 personality registered for level 1
Jul 21 20:58:17 node-2 kernel: [    2.650779] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 21 20:58:17 node-2 kernel: [    2.656820] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 21 20:58:17 node-2 kernel: [    2.657120] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 21 20:58:17 node-2 kernel: [    2.669099] megasas: FW now in Ready state
Jul 21 20:58:17 node-2 kernel: [    2.670031] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 21 20:58:17 node-2 kernel: [    2.670039] 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 21 20:58:17 node-2 kernel: [    2.670061] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 21 20:58:17 node-2 kernel: [    2.670581] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.670683] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.670773] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.670906] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.671225] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.689055] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 21 20:58:17 node-2 kernel: [    2.689059] 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 21 20:58:17 node-2 kernel: [    2.689061] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 21 20:58:17 node-2 kernel: [    2.689546] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.689672] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.689787] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.689946] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.690983] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.707241] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 21 20:58:17 node-2 kernel: [    2.707243] 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 21 20:58:17 node-2 kernel: [    2.707246] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 21 20:58:17 node-2 kernel: [    2.707529] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.707579] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.707709] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.707815] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.708088] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.714219] raid6: sse2x1     753 MB/s
Jul 21 20:58:17 node-2 kernel: [    2.727221] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 21 20:58:17 node-2 kernel: [    2.727262] 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 21 20:58:17 node-2 kernel: [    2.727293] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 21 20:58:17 node-2 kernel: [    2.728001] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.728128] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.728280] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.728390] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.728756] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 21 20:58:17 node-2 kernel: [    2.754842] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 21 20:58:17 node-2 kernel: [    2.754868] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 21 20:58:17 node-2 kernel: [    2.754904] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 21 20:58:17 node-2 kernel: [    2.754904] usb 2-1.4: Manufacturer: Avocent
Jul 21 20:58:17 node-2 kernel: [    2.754905] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 21 20:58:17 node-2 kernel: [    2.782341] raid6: sse2x2     738 MB/s
Jul 21 20:58:17 node-2 kernel: [    2.850185] raid6: sse2x4    1344 MB/s
Jul 21 20:58:17 node-2 kernel: [    2.918037] raid6: avx2x1     897 MB/s
Jul 21 20:58:17 node-2 kernel: [    2.985833] raid6: avx2x2   17766 MB/s
Jul 21 20:58:17 node-2 kernel: [    3.057769] raid6: avx2x4   21299 MB/s
Jul 21 20:58:17 node-2 kernel: [    3.063431] raid6: using algorithm avx2x4 (21299 MB/s)
Jul 21 20:58:17 node-2 kernel: [    3.069050] raid6: using avx2x2 recovery algorithm
Jul 21 20:58:17 node-2 kernel: [    3.074729] Switched to clocksource tsc
Jul 21 20:58:17 node-2 kernel: [    3.074754] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.074794] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.074832] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.074871] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.074893] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.074930] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.074964] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.075003] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.075022] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.075058] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.075098] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.075126] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.075163] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.075200] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.075236] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.075275] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 21 20:58:17 node-2 kernel: [    3.075437] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 21 20:58:17 node-2 kernel: [    3.092110] xor: automatically using best checksumming function:
Jul 21 20:58:17 node-2 kernel: [    3.107626] hidraw: raw HID events driver (C) Jiri Kosina
Jul 21 20:58:17 node-2 kernel: [    3.116135] usbcore: registered new interface driver usbhid
Jul 21 20:58:17 node-2 kernel: [    3.121587] usbhid: USB HID core driver
Jul 21 20:58:17 node-2 kernel: [    3.127994] 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 21 20:58:17 node-2 kernel: [    3.133696]    avx       : 35739.000 MB/sec
Jul 21 20:58:17 node-2 kernel: [    3.144963] 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 21 20:58:17 node-2 kernel: [    3.156411] async_tx: api initialized (async)
Jul 21 20:58:17 node-2 kernel: [    3.156438] 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 21 20:58:17 node-2 kernel: [    3.156488] 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 21 20:58:17 node-2 kernel: [    3.156541] 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 21 20:58:17 node-2 kernel: [    3.156579] 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 21 20:58:17 node-2 kernel: [    3.213852] md: raid6 personality registered for level 6
Jul 21 20:58:17 node-2 kernel: [    3.220259] md: raid5 personality registered for level 5
Jul 21 20:58:17 node-2 kernel: [    3.226514] md: raid4 personality registered for level 4
Jul 21 20:58:17 node-2 kernel: [    3.235705] md: raid10 personality registered for level 10
Jul 21 20:58:17 node-2 kernel: [    3.290472] multipathd (354): /proc/354/oom_adj is deprecated, please use /proc/354/oom_score_adj instead.
Jul 21 20:58:17 node-2 kernel: [    3.413492] megasas:IOC Init cmd success
Jul 21 20:58:17 node-2 kernel: [    3.465464] megasas: INIT adapter done
Jul 21 20:58:17 node-2 kernel: [    3.541389] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 21 20:58:17 node-2 kernel: [    3.548294] scsi0 : LSI SAS based MegaRAID driver
Jul 21 20:58:17 node-2 kernel: [    3.556203] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 21 20:58:17 node-2 kernel: [    3.575281] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 21 20:58:17 node-2 kernel: [    3.591368] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 21 20:58:17 node-2 kernel: [    3.598008] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 21 20:58:17 node-2 kernel: [    3.611148] sd 0:2:0:0: [sda] Write Protect is off
Jul 21 20:58:17 node-2 kernel: [    3.617524] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 21 20:58:17 node-2 kernel: [    3.617544] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 21 20:58:17 node-2 kernel: [    3.653887]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 21 20:58:17 node-2 kernel: [    3.660618] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 21 20:58:17 node-2 kernel: [    3.789378] random: lvm urandom read with 28 bits of entropy available
Jul 21 20:58:17 node-2 kernel: [    3.926122] bio: create slab <bio-1> at 1
Jul 21 20:58:17 node-2 kernel: [    4.813530] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 21 20:58:17 node-2 kernel: [    5.342190] init: plymouth-upstart-bridge main process (573) terminated with status 1
Jul 21 20:58:17 node-2 kernel: [    5.354658] init: plymouth-upstart-bridge main process ended, respawning
Jul 21 20:58:17 node-2 kernel: [    5.487783] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 21 20:58:17 node-2 kernel: [    5.515638] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 21 20:58:17 node-2 kernel: [    5.589223] random: nonblocking pool is initialized
Jul 21 20:58:17 node-2 kernel: [    5.609688] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 21 20:58:17 node-2 kernel: [    5.645726] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 21 20:58:17 node-2 kernel: [    5.727208] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 21 20:58:17 node-2 kernel: [    5.894534] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 21 20:58:17 node-2 kernel: [    5.925013] XFS (dm-1): Mounting Filesystem
Jul 21 20:58:17 node-2 kernel: [    6.135878] XFS (dm-1): Ending clean mount
Jul 21 20:58:17 node-2 kernel: [    6.188437] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 21 20:58:17 node-2 kernel: [    6.216588] XFS (dm-2): Mounting Filesystem
Jul 21 20:58:17 node-2 kernel: [    6.400969] XFS (dm-2): Ending clean mount
Jul 21 20:58:17 node-2 kernel: [    6.485310] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 21 20:58:17 node-2 kernel: [    8.256977] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 21 20:58:17 node-2 kernel: [    8.271375] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 21 20:58:17 node-2 kernel: [    8.399864] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 21 20:58:17 node-2 kernel: [    8.399869] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 21 20:58:17 node-2 kernel: [    8.399873] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 21 20:58:17 node-2 kernel: [    8.399876] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 21 20:58:17 node-2 kernel: [    8.442780] systemd-udevd[802]: starting version 204
Jul 21 20:58:17 node-2 kernel: [    8.587815] power_meter ACPI000D:00: Found ACPI power meter.
Jul 21 20:58:17 node-2 kernel: [    8.587835] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 21 20:58:17 node-2 kernel: [    8.599384] IPMI System Interface driver.
Jul 21 20:58:17 node-2 kernel: [    8.599426] ipmi_si: probing via ACPI
Jul 21 20:58:17 node-2 kernel: [    8.599450] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 21 20:58:17 node-2 kernel: [    8.599451] ipmi_si: Adding ACPI-specified kcs state machine
Jul 21 20:58:17 node-2 kernel: [    8.599461] ipmi_si: probing via SMBIOS
Jul 21 20:58:17 node-2 kernel: [    8.599462] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 21 20:58:17 node-2 kernel: [    8.599463] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 21 20:58:17 node-2 kernel: [    8.599465] ipmi_si: probing via SPMI
Jul 21 20:58:17 node-2 kernel: [    8.599466] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 21 20:58:17 node-2 kernel: [    8.599466] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 21 20:58:17 node-2 kernel: [    8.599467] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 21 20:58:17 node-2 kernel: [    8.613908] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 21 20:58:17 node-2 kernel: [    8.613914] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 21 20:58:17 node-2 kernel: [    8.613916] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 21 20:58:17 node-2 kernel: [    8.613918] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 21 20:58:17 node-2 kernel: [    8.613961] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 21 20:58:17 node-2 kernel: [    8.618450] wmi: Mapper loaded
Jul 21 20:58:17 node-2 kernel: [    8.637841] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 21 20:58:17 node-2 kernel: [    8.701497] systemd-udevd[849]: renamed network interface eth1 to enp7s0
Jul 21 20:58:17 node-2 kernel: [    8.733313] systemd-udevd[820]: renamed network interface eth0 to enp6s0
Jul 21 20:58:17 node-2 kernel: [    8.741279] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 21 20:58:17 node-2 kernel: [    8.741286] ipmi_si 00:09: IPMI kcs interface initialized
Jul 21 20:58:17 node-2 kernel: [    8.785353] systemd-udevd[826]: renamed network interface eth2 to enp8s0
Jul 21 20:58:17 node-2 kernel: [    8.815374] systemd-udevd[822]: renamed network interface eth3 to enp9s0
Jul 21 20:58:17 node-2 kernel: [    9.102580] type=1400 audit(1469134670.118:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1068 comm="apparmor_parser"
Jul 21 20:58:17 node-2 kernel: [    9.102749] type=1400 audit(1469134670.118:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1068 comm="apparmor_parser"
Jul 21 20:58:17 node-2 kernel: [    9.102874] type=1400 audit(1469134670.118:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1068 comm="apparmor_parser"
Jul 21 20:58:17 node-2 kernel: [    9.105524] type=1400 audit(1469134670.122:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1071 comm="apparmor_parser"
Jul 21 20:58:17 node-2 kernel: [    9.105666] type=1400 audit(1469134670.122:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1071 comm="apparmor_parser"
Jul 21 20:58:17 node-2 kernel: [    9.105784] type=1400 audit(1469134670.122:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1071 comm="apparmor_parser"
Jul 21 20:58:17 node-2 kernel: [    9.112234] type=1400 audit(1469134670.126:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1099 comm="apparmor_parser"
Jul 21 20:58:17 node-2 kernel: [    9.112450] type=1400 audit(1469134670.126:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1099 comm="apparmor_parser"
Jul 21 20:58:17 node-2 kernel: [    9.112652] type=1400 audit(1469134670.130:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1099 comm="apparmor_parser"
Jul 21 20:58:17 node-2 kernel: [    9.143529] type=1400 audit(1469134670.158:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1069 comm="apparmor_parser"
Jul 21 20:58:17 node-2 kernel: [    9.608993] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 21 20:58:17 node-2 kernel: [    9.609883] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 21 20:58:17 node-2 kernel: [    9.772447] enic 0000:06:00.0 enp6s0: Link UP
Jul 21 20:58:17 node-2 kernel: [    9.772971] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 21 20:58:17 node-2 kernel: [    9.772977] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 21 20:58:17 node-2 kernel: [   19.957228] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 21 20:58:18 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 21 20:58:18 node-2 kernel: [   38.185244] init: failsafe main process (8441) killed by TERM signal
Jul 21 20:58:19 node-2 dbus[8478]: [system] AppArmor D-Bus mediation is enabled
Jul 21 20:58:19 node-2 kernel: [   38.483214] audit_printk_skb: 30 callbacks suppressed
Jul 21 20:58:19 node-2 kernel: [   38.483215] type=1400 audit(1469134699.163:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8567 comm="apparmor_parser"
Jul 21 20:58:19 node-2 kernel: [   38.483795] type=1400 audit(1469134699.167:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8566 comm="apparmor_parser"
Jul 21 20:58:19 node-2 kernel: [   38.483801] type=1400 audit(1469134699.167:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8566 comm="apparmor_parser"
Jul 21 20:58:19 node-2 kernel: [   38.483803] type=1400 audit(1469134699.167:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8566 comm="apparmor_parser"
Jul 21 20:58:19 node-2 kernel: [   38.485148] type=1400 audit(1469134699.167:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8566 comm="apparmor_parser"
Jul 21 20:58:19 node-2 kernel: [   38.485186] type=1400 audit(1469134699.167:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8566 comm="apparmor_parser"
Jul 21 20:58:19 node-2 kernel: [   38.485752] type=1400 audit(1469134699.167:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8566 comm="apparmor_parser"
Jul 21 20:58:19 node-2 kernel: [   38.559780] type=1400 audit(1469134699.243:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8569 comm="apparmor_parser"
Jul 21 20:58:19 node-2 anacron[8633]: Anacron 2.3 started on 2016-07-21
Jul 21 20:58:19 node-2 anacron[8633]: Will run job `cron.daily' in 5 min.
Jul 21 20:58:19 node-2 anacron[8633]: Will run job `cron.weekly' in 10 min.
Jul 21 20:58:19 node-2 anacron[8633]: Will run job `cron.monthly' in 15 min.
Jul 21 20:58:19 node-2 anacron[8633]: Jobs will be executed sequentially
Jul 21 20:58:19 node-2 cron[8599]: (CRON) INFO (pidfile fd = 3)
Jul 21 20:58:19 node-2 cron[8641]: (CRON) STARTUP (fork ok)
Jul 21 20:58:19 node-2 multipathd: path checkers start up
Jul 21 20:58:19 node-2 cron[8641]: (CRON) INFO (Running @reboot jobs)
Jul 21 20:58:19 node-2 postfix/master[8778]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 21 20:58:23 node-2 puppet-agent[8963]: Reopening log files
Jul 21 20:58:23 node-2 puppet-agent[8963]: Could not request certificate: Connection refused - connect(2)
Jul 21 20:58:37 node-2 puppet-user[9171]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 21 20:58:37 node-2 puppet-user[9171]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 21 20:58:38 node-2 puppet-user[9171]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 21 20:58:38 node-2 puppet-user[9171]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 21 20:58:38 node-2 puppet-user[9171]: Finished catalog run in 0.73 seconds
Jul 21 20:58:39 node-2 multipathd: uevent trigger error
Jul 21 20:58:39 node-2 puppet-user[9606]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 21 20:58:39 node-2 puppet-user[9606]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Jul 21 20:58:40 node-2 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 21 20:58:40 node-2 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 21 20:58:40 node-2 puppet-user[9606]: (/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 21 20:58:40 node-2 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 21 20:58:40 node-2 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 21 20:58:40 node-2 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 21 20:58:40 node-2 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 21 20:58:40 node-2 puppet-user[9606]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 21 20:58:40 node-2 puppet-user[9606]: Finished catalog run in 0.06 seconds
Jul 21 20:58:41 node-2 puppet-user[10247]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 21 20:58:41 node-2 puppet-user[10247]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 21 20:58:41 node-2 puppet-user[10247]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 21 20:58:41 node-2 puppet-user[10247]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 21 20:58:41 node-2 puppet-user[10247]: Finished catalog run in 0.03 seconds
Jul 21 20:58:43 node-2 puppet-user[10712]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 21 20:58:43 node-2 puppet-user[10712]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 21 20:58:43 node-2 puppet-user[10712]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 21 20:58:43 node-2 puppet-user[10712]: Finished catalog run in 0.05 seconds
Jul 21 20:58:45 node-2 puppet-user[11174]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 21 20:58:45 node-2 puppet-user[11174]: Compiled catalog for node-2.domain.tld in environment production in 0.21 seconds
Jul 21 20:58:45 node-2 puppet-user[11174]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 21 20:58:45 node-2 kernel: [   64.509885] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 21 20:58:45 node-2 kernel: [   64.509937] 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 21 20:58:45 node-2 puppet-user[11174]: (/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 21 20:58:45 node-2 puppet-user[11174]: Finished catalog run in 0.06 seconds
Jul 21 20:58:47 node-2 puppet-user[11637]: (Scope(Class[main])) MODULAR: sync_time
Jul 21 20:58:47 node-2 puppet-user[11637]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 21 20:58:47 node-2 ntpdate[12054]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 21 20:58:52 node-2 kernel: [   71.749866] init: plymouth-upstart-bridge main process ended, respawning
Jul 21 20:58:52 node-2 puppet-agent[8963]: Could not run: SIGTERM
Jul 21 20:58:52 node-2 kernel: [   72.046763] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 21 20:58:53 node-2 ec2: 
Jul 21 20:58:53 node-2 ec2: #############################################################
Jul 21 20:58:53 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 21 20:58:53 node-2 ec2: 1024 9a:18:8b:dc:02:b4:e9:bb:f2:29:7d:78:62:d1:e1:64  root@node-2.domain.tld (DSA)
Jul 21 20:58:53 node-2 ec2: 256 53:f3:f0:6b:94:18:78:1c:51:c3:49:c4:ad:9f:5d:e3  root@node-2.domain.tld (ECDSA)
Jul 21 20:58:53 node-2 ec2: 256 bf:aa:89:c2:c1:73:9f:96:1f:51:86:17:2a:f4:3c:4e  root@node-2.domain.tld (ED25519)
Jul 21 20:58:53 node-2 ec2: 2048 79:e8:fd:85:9b:f2:2d:c6:0b:08:eb:99:a2:dc:8f:0a  root@node-2.domain.tld (RSA)
Jul 21 20:58:53 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 21 20:58:53 node-2 ec2: #############################################################
Jul 21 20:58:53 node-2 ntpdate[12054]: adjust time server 10.20.0.2 offset 0.000910 sec
Jul 21 20:58:53 node-2 puppet-user[11637]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 21 20:58:53 node-2 puppet-user[11637]: Finished catalog run in 6.21 seconds
Jul 21 20:58:59 node-2 puppet-user[12427]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 21 20:58:59 node-2 puppet-user[12427]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Jul 21 20:58:59 node-2 puppet-user[12427]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 21 20:58:59 node-2 puppet-user[12427]: Finished catalog run in 0.09 seconds
Jul 21 20:59:00 node-2 puppet-user[12886]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 21 20:59:01 node-2 puppet-user[12886]: Compiled catalog for node-2.domain.tld in environment production in 0.90 seconds
Jul 21 20:59:01 node-2 CRON[13334]: (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 21 20:59:01 node-2 puppet-user[12886]: (/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 21 20:59:01 node-2 puppet-user[12886]: (/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 21 20:59:01 node-2 puppet-user[12886]: (/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 21 20:59:01 node-2 puppet-user[12886]: (/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 21 20:59:01 node-2 puppet-user[12886]: (/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 21 20:59:01 node-2 puppet-user[12886]: (/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 21 20:59:02 node-2 puppet-user[12886]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 21 20:59:02 node-2 puppet-user[12886]: (/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 21 20:59:02 node-2 puppet-user[12886]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 21 20:59:02 node-2 puppet-user[12886]: (/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 21 20:59:02 node-2 puppet-user[12886]: (/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 21 20:59:02 node-2 puppet-user[12886]: (/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 21 20:59:02 node-2 puppet-user[12886]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 21 20:59:02 node-2 puppet-user[12886]: (/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 21 20:59:02 node-2 puppet-user[12886]: (/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 21 20:59:02 node-2 puppet-user[12886]: (/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 21 20:59:02 node-2 puppet-user[12886]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 21 20:59:02 node-2 puppet-user[12886]: (/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 21 20:59:16 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 21 20:59:16 node-2 nailgun-agent: I, [2016-07-21T20:59:16.884704 #13337]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 21 20:59:19 node-2 puppet-user[12886]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 21 20:59:19 node-2 puppet-user[12886]: Finished catalog run in 17.28 seconds
Jul 21 20:59:20 node-2 puppet-user[14114]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 21 20:59:20 node-2 puppet-user[14114]: Compiled catalog for node-2.domain.tld in environment production in 0.12 seconds
Jul 21 20:59:25 node-2 puppet-user[14114]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 21 20:59:29 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 21 20:59:29 node-2 nailgun-agent: I, [2016-07-21T20:59:29.796702 #13337]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 21 21:00:00 node-2 puppet-user[14114]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 21 21:00:00 node-2 puppet-user[14114]: Finished catalog run in 39.94 seconds
Jul 21 21:00:01 node-2 CRON[16932]: (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 21 21:00:02 node-2 puppet-user[16864]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 21 21:00:03 node-2 puppet-user[16864]: Compiled catalog for node-2.domain.tld in environment production in 0.61 seconds
Jul 21 21:00:03 node-2 puppet-user[16864]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 21 21:00:03 node-2 puppet-user[16864]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 21 21:00:03 node-2 puppet-user[16864]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 21 21:00:03 node-2 puppet-user[16864]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 21 21:00:03 node-2 puppet-user[16864]: Finished catalog run in 0.08 seconds
Jul 21 21:00:05 node-2 puppet-user[17345]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 21 21:00:06 node-2 puppet-user[17345]: Compiled catalog for node-2.domain.tld in environment production in 0.85 seconds
Jul 21 21:00:06 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 21 21:00:06 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 21 21:00:06 node-2 crontab[17788]: (root) LIST (root)
Jul 21 21:00:06 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 21 21:00:06 node-2 crontab[17789]: (root) REPLACE (root)
Jul 21 21:00:09 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 21 21:00:10 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 21 21:00:10 node-2 puppet-user[17345]: (/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 21 21:00:10 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 21 21:00:11 node-2 puppet-user[17345]: (/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 21 21:00:11 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8414" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 21 21:00:11 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 21 21:00:13 node-2 multipathd: uevent trigger error
<27>Jul 21 21:00:13 node-2 multipathd: uevent trigger error
<27>Jul 21 21:00:13 node-2 multipathd: uevent trigger error
<27>Jul 21 21:00:13 node-2 multipathd: uevent trigger error
<27>Jul 21 21:00:13 node-2 multipathd: uevent trigger error
<27>Jul 21 21:00:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:00:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:00:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:00:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:00:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:01:34 node-2 ntpdate[28900]: no servers can be used, exiting
<27>Jul 21 21:02:06 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:06 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:06 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:06 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:06 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:06 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:02:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:03:38 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 21 21:03:39 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 21 21:03:45 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 21 21:03:45 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 21 21:03:50 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 21 21:03:56 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 21 21:03:56 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 21 21:04:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:16 node-2 multipathd: uevent trigger error
<129>Jul 21 21:04:18 node-2 haproxy[16756]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:19 node-2 haproxy[16765]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:20 node-2 haproxy[16765]: 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 21 21:04:20 node-2 haproxy[16765]: proxy mysqld has no server available!
<27>Jul 21 21:04:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:25 node-2 multipathd: uevent trigger error
<129>Jul 21 21:04:28 node-2 haproxy[19388]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:28 node-2 haproxy[19388]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:28 node-2 haproxy[19388]: 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 21 21:04:28 node-2 haproxy[19388]: proxy mysqld has no server available!
<129>Jul 21 21:04:29 node-2 haproxy[19392]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:29 node-2 haproxy[19392]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:29 node-2 haproxy[19392]: 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 21 21:04:29 node-2 haproxy[19392]: proxy object-storage has no server available!
<27>Jul 21 21:04:31 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:31 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:31 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:31 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:31 node-2 multipathd: uevent trigger error
<129>Jul 21 21:04:33 node-2 haproxy[20888]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:33 node-2 haproxy[20888]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:33 node-2 haproxy[20888]: 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 21 21:04:33 node-2 haproxy[20888]: proxy neutron has no server available!
<129>Jul 21 21:04:34 node-2 haproxy[20892]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:34 node-2 haproxy[20892]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:34 node-2 haproxy[20892]: 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 21 21:04:34 node-2 haproxy[20892]: proxy mysqld has no server available!
<129>Jul 21 21:04:34 node-2 haproxy[20892]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:34 node-2 haproxy[20892]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:35 node-2 haproxy[20892]: 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 21 21:04:35 node-2 haproxy[20892]: proxy object-storage has no server available!
<27>Jul 21 21:04:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:36 node-2 multipathd: uevent trigger error
<129>Jul 21 21:04:38 node-2 haproxy[22304]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:38 node-2 haproxy[22304]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:39 node-2 haproxy[22315]: 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 21 21:04:39 node-2 haproxy[22315]: proxy keystone-1 has no server available!
<129>Jul 21 21:04:39 node-2 haproxy[22315]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:39 node-2 haproxy[22315]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:39 node-2 haproxy[22315]: 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 21 21:04:39 node-2 haproxy[22315]: proxy keystone-2 has no server available!
<129>Jul 21 21:04:39 node-2 haproxy[22315]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:39 node-2 haproxy[22315]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:39 node-2 haproxy[22315]: 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 21 21:04:39 node-2 haproxy[22315]: proxy neutron has no server available!
<129>Jul 21 21:04:39 node-2 haproxy[22315]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:40 node-2 haproxy[22315]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:40 node-2 haproxy[22315]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 21 21:04:40 node-2 haproxy[22315]: proxy mysqld has no server available!
<129>Jul 21 21:04:40 node-2 haproxy[22315]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:40 node-2 haproxy[22315]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:40 node-2 haproxy[22315]: 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 21 21:04:40 node-2 haproxy[22315]: proxy object-storage has no server available!
<27>Jul 21 21:04:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:42 node-2 multipathd: uevent trigger error
<129>Jul 21 21:04:44 node-2 haproxy[23863]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:44 node-2 haproxy[23863]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:44 node-2 haproxy[23863]: 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 21 21:04:44 node-2 haproxy[23863]: proxy keystone-1 has no server available!
<129>Jul 21 21:04:44 node-2 haproxy[23863]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:44 node-2 haproxy[23863]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:44 node-2 haproxy[23863]: 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 21 21:04:44 node-2 haproxy[23863]: proxy keystone-2 has no server available!
<129>Jul 21 21:04:45 node-2 haproxy[23867]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:45 node-2 haproxy[23867]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:45 node-2 haproxy[23867]: 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 21 21:04:45 node-2 haproxy[23867]: proxy neutron has no server available!
<129>Jul 21 21:04:45 node-2 haproxy[23867]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:45 node-2 haproxy[23867]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:45 node-2 haproxy[23867]: 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 21 21:04:45 node-2 haproxy[23867]: proxy mysqld has no server available!
<129>Jul 21 21:04:45 node-2 haproxy[23867]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:45 node-2 haproxy[23867]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:45 node-2 haproxy[23867]: 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 21 21:04:45 node-2 haproxy[23867]: proxy object-storage has no server available!
<129>Jul 21 21:04:46 node-2 haproxy[23867]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:46 node-2 haproxy[23867]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:46 node-2 haproxy[23867]: 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 21 21:04:46 node-2 haproxy[23867]: proxy aodh has no server available!
<27>Jul 21 21:04:47 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:47 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:47 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:47 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:47 node-2 multipathd: uevent trigger error
<129>Jul 21 21:04:49 node-2 haproxy[25198]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:50 node-2 haproxy[25202]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:50 node-2 haproxy[25202]: 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 21 21:04:50 node-2 haproxy[25202]: proxy keystone-1 has no server available!
<129>Jul 21 21:04:50 node-2 haproxy[25202]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:50 node-2 haproxy[25202]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:50 node-2 haproxy[25202]: 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 21 21:04:50 node-2 haproxy[25202]: proxy keystone-2 has no server available!
<129>Jul 21 21:04:50 node-2 haproxy[25202]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:50 node-2 haproxy[25202]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:50 node-2 haproxy[25202]: 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 21 21:04:50 node-2 haproxy[25202]: proxy neutron has no server available!
<129>Jul 21 21:04:50 node-2 haproxy[25202]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:50 node-2 haproxy[25202]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:50 node-2 haproxy[25202]: 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 21 21:04:50 node-2 haproxy[25202]: proxy mysqld has no server available!
<129>Jul 21 21:04:51 node-2 haproxy[25202]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:51 node-2 haproxy[25202]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:51 node-2 haproxy[25202]: 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 21 21:04:51 node-2 haproxy[25202]: proxy object-storage has no server available!
<129>Jul 21 21:04:51 node-2 haproxy[25202]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:51 node-2 haproxy[25202]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:51 node-2 haproxy[25202]: 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 21 21:04:51 node-2 haproxy[25202]: proxy aodh has no server available!
<129>Jul 21 21:04:51 node-2 haproxy[25202]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:51 node-2 haproxy[25202]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:51 node-2 haproxy[25202]: 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 21 21:04:51 node-2 haproxy[25202]: proxy ceilometer has no server available!
<27>Jul 21 21:04:53 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:53 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:53 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:53 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:53 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:53 node-2 multipathd: uevent trigger error
<129>Jul 21 21:04:55 node-2 haproxy[26555]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:55 node-2 haproxy[26555]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:55 node-2 haproxy[26555]: 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 21 21:04:55 node-2 haproxy[26555]: proxy keystone-1 has no server available!
<129>Jul 21 21:04:55 node-2 haproxy[26555]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:55 node-2 haproxy[26555]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 1ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:55 node-2 haproxy[26555]: 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 21 21:04:55 node-2 haproxy[26555]: proxy keystone-2 has no server available!
<129>Jul 21 21:04:55 node-2 haproxy[26555]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:56 node-2 haproxy[26559]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:56 node-2 haproxy[26559]: 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 21 21:04:56 node-2 haproxy[26559]: proxy neutron has no server available!
<129>Jul 21 21:04:56 node-2 haproxy[26559]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:56 node-2 haproxy[26559]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:56 node-2 haproxy[26559]: 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 21 21:04:56 node-2 haproxy[26559]: proxy mysqld has no server available!
<129>Jul 21 21:04:56 node-2 haproxy[26559]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:56 node-2 haproxy[26559]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:56 node-2 haproxy[26559]: 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 21 21:04:56 node-2 haproxy[26559]: proxy object-storage has no server available!
<129>Jul 21 21:04:56 node-2 haproxy[26559]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:56 node-2 haproxy[26559]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:57 node-2 haproxy[26559]: 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 21 21:04:57 node-2 haproxy[26559]: proxy aodh has no server available!
<129>Jul 21 21:04:57 node-2 haproxy[26559]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:57 node-2 haproxy[26559]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:04:57 node-2 haproxy[26559]: 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 21 21:04:57 node-2 haproxy[26559]: proxy ceilometer has no server available!
<27>Jul 21 21:04:58 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:58 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:58 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:58 node-2 multipathd: uevent trigger error
<27>Jul 21 21:04:58 node-2 multipathd: uevent trigger error
<129>Jul 21 21:05:00 node-2 haproxy[27912]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:01 node-2 haproxy[27919]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:01 node-2 haproxy[27919]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:01 node-2 haproxy[27919]: 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 21 21:05:01 node-2 haproxy[27919]: proxy keystone-1 has no server available!
<129>Jul 21 21:05:01 node-2 haproxy[27919]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:01 node-2 haproxy[27919]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:01 node-2 haproxy[27919]: 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 21 21:05:01 node-2 haproxy[27919]: proxy keystone-2 has no server available!
<129>Jul 21 21:05:01 node-2 haproxy[27919]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:01 node-2 haproxy[27919]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:01 node-2 haproxy[27919]: 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 21 21:05:01 node-2 haproxy[27919]: proxy neutron has no server available!
<129>Jul 21 21:05:01 node-2 haproxy[27919]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:01 node-2 haproxy[27919]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:01 node-2 haproxy[27919]: 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 21 21:05:01 node-2 haproxy[27919]: proxy mysqld has no server available!
<129>Jul 21 21:05:02 node-2 haproxy[27919]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:02 node-2 haproxy[27919]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:02 node-2 haproxy[27919]: 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 21 21:05:02 node-2 haproxy[27919]: proxy object-storage has no server available!
<129>Jul 21 21:05:02 node-2 haproxy[27919]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:02 node-2 haproxy[27919]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:02 node-2 haproxy[27919]: 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 21 21:05:02 node-2 haproxy[27919]: proxy aodh has no server available!
<129>Jul 21 21:05:02 node-2 haproxy[27919]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:02 node-2 haproxy[27919]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:02 node-2 haproxy[27919]: 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 21 21:05:02 node-2 haproxy[27919]: proxy ceilometer has no server available!
<27>Jul 21 21:05:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:03 node-2 multipathd: uevent trigger error
<129>Jul 21 21:05:06 node-2 haproxy[29309]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:06 node-2 haproxy[29309]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:06 node-2 haproxy[29309]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:06 node-2 haproxy[29309]: 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 21 21:05:06 node-2 haproxy[29309]: proxy keystone-1 has no server available!
<129>Jul 21 21:05:06 node-2 haproxy[29309]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:06 node-2 haproxy[29309]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:06 node-2 haproxy[29309]: 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 21 21:05:06 node-2 haproxy[29309]: proxy keystone-2 has no server available!
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:07 node-2 haproxy[29318]: 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 21 21:05:07 node-2 haproxy[29318]: proxy glance-api has no server available!
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:07 node-2 haproxy[29318]: 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 21 21:05:07 node-2 haproxy[29318]: proxy glance-glare has no server available!
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:07 node-2 haproxy[29318]: 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 21 21:05:07 node-2 haproxy[29318]: proxy neutron has no server available!
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:07 node-2 haproxy[29318]: 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 21 21:05:07 node-2 haproxy[29318]: proxy glance-registry has no server available!
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:07 node-2 haproxy[29318]: 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 21 21:05:07 node-2 haproxy[29318]: proxy mysqld has no server available!
<129>Jul 21 21:05:07 node-2 haproxy[29318]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:08 node-2 haproxy[29318]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:08 node-2 haproxy[29318]: 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 21 21:05:08 node-2 haproxy[29318]: proxy object-storage has no server available!
<129>Jul 21 21:05:08 node-2 haproxy[29318]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:08 node-2 haproxy[29318]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:08 node-2 haproxy[29318]: 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 21 21:05:08 node-2 haproxy[29318]: proxy aodh has no server available!
<129>Jul 21 21:05:08 node-2 haproxy[29318]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:08 node-2 haproxy[29318]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:08 node-2 haproxy[29318]: 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 21 21:05:08 node-2 haproxy[29318]: proxy ceilometer has no server available!
<27>Jul 21 21:05:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:09 node-2 multipathd: uevent trigger error
<129>Jul 21 21:05:12 node-2 haproxy[30734]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:12 node-2 haproxy[30734]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:12 node-2 haproxy[30734]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:12 node-2 haproxy[30734]: 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 21 21:05:12 node-2 haproxy[30734]: proxy keystone-1 has no server available!
<129>Jul 21 21:05:12 node-2 haproxy[30734]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:12 node-2 haproxy[30734]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:12 node-2 haproxy[30734]: 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 21 21:05:12 node-2 haproxy[30734]: proxy keystone-2 has no server available!
<129>Jul 21 21:05:12 node-2 haproxy[30734]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: 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 21 21:05:13 node-2 haproxy[30738]: proxy nova-api has no server available!
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: 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 21 21:05:13 node-2 haproxy[30738]: proxy nova-metadata-api has no server available!
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: 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 21 21:05:13 node-2 haproxy[30738]: proxy glance-api has no server available!
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: 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 21 21:05:13 node-2 haproxy[30738]: proxy glance-glare has no server available!
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: 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 21 21:05:13 node-2 haproxy[30738]: proxy neutron has no server available!
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: 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 21 21:05:13 node-2 haproxy[30738]: proxy glance-registry has no server available!
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:13 node-2 haproxy[30738]: 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 21 21:05:13 node-2 haproxy[30738]: proxy mysqld has no server available!
<129>Jul 21 21:05:13 node-2 haproxy[30738]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:14 node-2 haproxy[30738]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:14 node-2 haproxy[30738]: 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 21 21:05:14 node-2 haproxy[30738]: proxy object-storage has no server available!
<129>Jul 21 21:05:14 node-2 haproxy[30738]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:14 node-2 haproxy[30738]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:14 node-2 haproxy[30738]: 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 21 21:05:14 node-2 haproxy[30738]: proxy aodh has no server available!
<129>Jul 21 21:05:14 node-2 haproxy[30738]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:14 node-2 haproxy[30738]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:14 node-2 haproxy[30738]: 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 21 21:05:14 node-2 haproxy[30738]: proxy ceilometer has no server available!
<129>Jul 21 21:05:14 node-2 haproxy[30738]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:14 node-2 haproxy[30738]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:14 node-2 haproxy[30738]: 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 21 21:05:14 node-2 haproxy[30738]: proxy nova-novncproxy has no server available!
<27>Jul 21 21:05:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:16 node-2 multipathd: uevent trigger error
<129>Jul 21 21:05:18 node-2 haproxy[32084]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:18 node-2 haproxy[32084]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:18 node-2 haproxy[32084]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:18 node-2 haproxy[32084]: 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 21 21:05:18 node-2 haproxy[32084]: proxy keystone-1 has no server available!
<129>Jul 21 21:05:18 node-2 haproxy[32084]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:18 node-2 haproxy[32084]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:18 node-2 haproxy[32084]: 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 21 21:05:18 node-2 haproxy[32084]: proxy keystone-2 has no server available!
<129>Jul 21 21:05:18 node-2 haproxy[32084]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:18 node-2 haproxy[32084]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:18 node-2 haproxy[32084]: 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 21 21:05:18 node-2 haproxy[32084]: proxy nova-api has no server available!
<129>Jul 21 21:05:18 node-2 haproxy[32084]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:18 node-2 haproxy[32084]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:18 node-2 haproxy[32084]: 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 21 21:05:18 node-2 haproxy[32084]: proxy nova-metadata-api has no server available!
<129>Jul 21 21:05:18 node-2 haproxy[32084]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: 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 21 21:05:19 node-2 haproxy[32088]: proxy cinder-api has no server available!
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: 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 21 21:05:19 node-2 haproxy[32088]: proxy glance-api has no server available!
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: 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 21 21:05:19 node-2 haproxy[32088]: proxy glance-glare has no server available!
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: 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 21 21:05:19 node-2 haproxy[32088]: proxy neutron has no server available!
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: 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 21 21:05:19 node-2 haproxy[32088]: proxy glance-registry has no server available!
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: 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 21 21:05:19 node-2 haproxy[32088]: proxy mysqld has no server available!
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: 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 21 21:05:19 node-2 haproxy[32088]: proxy object-storage has no server available!
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:19 node-2 haproxy[32088]: 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 21 21:05:19 node-2 haproxy[32088]: proxy aodh has no server available!
<129>Jul 21 21:05:20 node-2 haproxy[32088]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:20 node-2 haproxy[32088]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:20 node-2 haproxy[32088]: 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 21 21:05:20 node-2 haproxy[32088]: proxy ceilometer has no server available!
<129>Jul 21 21:05:20 node-2 haproxy[32088]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:20 node-2 haproxy[32088]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:20 node-2 haproxy[32088]: 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 21 21:05:20 node-2 haproxy[32088]: proxy nova-novncproxy has no server available!
<27>Jul 21 21:05:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:21 node-2 multipathd: uevent trigger error
<129>Jul 21 21:05:24 node-2 haproxy[1224]: Server horizon/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:24 node-2 haproxy[1224]: Server keystone-1/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:24 node-2 haproxy[1224]: Server keystone-1/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:24 node-2 haproxy[1224]: 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 21 21:05:24 node-2 haproxy[1224]: proxy keystone-1 has no server available!
<129>Jul 21 21:05:24 node-2 haproxy[1224]: Server keystone-2/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:24 node-2 haproxy[1224]: Server keystone-2/node-3 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:24 node-2 haproxy[1224]: 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 21 21:05:24 node-2 haproxy[1224]: proxy keystone-2 has no server available!
<129>Jul 21 21:05:24 node-2 haproxy[1224]: Server nova-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:24 node-2 haproxy[1224]: Server nova-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:24 node-2 haproxy[1224]: 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 21 21:05:24 node-2 haproxy[1224]: proxy nova-api has no server available!
<129>Jul 21 21:05:24 node-2 haproxy[1224]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:24 node-2 haproxy[1224]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: 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 21 21:05:25 node-2 haproxy[1228]: proxy nova-metadata-api has no server available!
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server cinder-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: 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 21 21:05:25 node-2 haproxy[1228]: proxy cinder-api has no server available!
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server glance-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server glance-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: 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 21 21:05:25 node-2 haproxy[1228]: proxy glance-api has no server available!
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server glance-glare/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server glance-glare/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: 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 21 21:05:25 node-2 haproxy[1228]: proxy glance-glare has no server available!
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server neutron/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server neutron/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: 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 21 21:05:25 node-2 haproxy[1228]: proxy neutron has no server available!
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server glance-registry/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server glance-registry/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: 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 21 21:05:25 node-2 haproxy[1228]: proxy glance-registry has no server available!
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server mysqld/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 2 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: 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 21 21:05:25 node-2 haproxy[1228]: proxy mysqld has no server available!
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server object-storage/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server object-storage/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: 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 21 21:05:25 node-2 haproxy[1228]: proxy object-storage has no server available!
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server aodh/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server aodh/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: 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 21 21:05:25 node-2 haproxy[1228]: proxy aodh has no server available!
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server ceilometer/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:25 node-2 haproxy[1228]: Server ceilometer/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:26 node-2 haproxy[1228]: 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 21 21:05:26 node-2 haproxy[1228]: proxy ceilometer has no server available!
<129>Jul 21 21:05:26 node-2 haproxy[1228]: Server heat-api/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:26 node-2 haproxy[1228]: Server heat-api/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:26 node-2 haproxy[1228]: 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 21 21:05:26 node-2 haproxy[1228]: proxy heat-api has no server available!
<129>Jul 21 21:05:26 node-2 haproxy[1228]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:26 node-2 haproxy[1228]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:26 node-2 haproxy[1228]: 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 21 21:05:26 node-2 haproxy[1228]: proxy heat-api-cfn has no server available!
<129>Jul 21 21:05:26 node-2 haproxy[1228]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:26 node-2 haproxy[1228]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:26 node-2 haproxy[1228]: 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 21 21:05:26 node-2 haproxy[1228]: proxy heat-api-cloudwatch has no server available!
<129>Jul 21 21:05:26 node-2 haproxy[1228]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:26 node-2 haproxy[1228]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 21 21:05:26 node-2 haproxy[1228]: 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 21 21:05:26 node-2 haproxy[1228]: proxy nova-novncproxy has no server available!
<27>Jul 21 21:05:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:31 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:31 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:31 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:31 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:31 node-2 multipathd: uevent trigger error
<27>Jul 21 21:05:44 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 21 21:06:04 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 21 21:06:09 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 21 21:06:11 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 21 21:06:37 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 21 21:07:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:07:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:07:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:07:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:07:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:07:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:06 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 21 21:09:20 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:20 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:20 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:20 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:20 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:20 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:32 node-2 multipathd: uevent trigger error
<43>Jul 21 21:09:52 node-2 apache2_error [Thu Jul 21 21:09:46.440179 2016] [mpm_event:notice] [pid 13500:tid 140663503005568] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 21 21:09:52 node-2 apache2_error [Thu Jul 21 21:09:46.440311 2016] [core:notice] [pid 13500:tid 140663503005568] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 21 21:09:52 node-2 apache2_error [Thu Jul 21 21:09:49.781480 2016] [mpm_event:notice] [pid 13500:tid 140663503005568] AH00491: caught SIGTERM, shutting down
<43>Jul 21 21:09:52 node-2 apache2_error [Thu Jul 21 21:09:50.879918 2016] [mpm_worker:notice] [pid 13861:tid 139698471843712] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 21 21:09:52 node-2 apache2_error [Thu Jul 21 21:09:50.879966 2016] [core:notice] [pid 13861:tid 139698471843712] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 21 21:09:55 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:55 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:55 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:55 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:55 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:58 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:58 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:58 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:58 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:58 node-2 multipathd: uevent trigger error
<27>Jul 21 21:09:58 node-2 multipathd: uevent trigger error
<43>Jul 21 21:11:22 node-2 apache2_error [Thu Jul 21 21:11:16.181037 2016] [mpm_worker:notice] [pid 13861:tid 139698471843712] AH00295: caught SIGTERM, shutting down
<43>Jul 21 21:11:22 node-2 apache2_error [Thu Jul 21 21:11:16.926543 2016] [mpm_worker:notice] [pid 29382:tid 139853138352000] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 21 21:11:22 node-2 apache2_error [Thu Jul 21 21:11:16.926591 2016] [core:notice] [pid 29382:tid 139853138352000] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 21 21:12:10 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 21 21:12:12 node-2 apache2_error [Thu Jul 21 21:12:03.268624 2016] [mpm_worker:notice] [pid 29382:tid 139853138352000] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 21 21:12:12 node-2 apache2_error [Thu Jul 21 21:12:03.465019 2016] [mpm_worker:warn] [pid 29382:tid 139853138352000] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 21 21:12:12 node-2 apache2_error [Thu Jul 21 21:12:03.469822 2016] [mpm_worker:notice] [pid 29382:tid 139853138352000] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 21 21:12:12 node-2 apache2_error [Thu Jul 21 21:12:03.469849 2016] [core:notice] [pid 29382:tid 139853138352000] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 21 21:12:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:12:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:13:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:14:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:15:15 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 21 21:15:37 node-2 multipathd: uevent trigger error
<27>Jul 21 21:15:37 node-2 multipathd: uevent trigger error
<27>Jul 21 21:15:37 node-2 multipathd: uevent trigger error
<27>Jul 21 21:15:37 node-2 multipathd: uevent trigger error
<27>Jul 21 21:15:37 node-2 multipathd: uevent trigger error
<27>Jul 21 21:15:37 node-2 multipathd: uevent trigger error
<27>Jul 21 21:16:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:16:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:16:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:16:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:16:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:16:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:16:52 node-2 multipathd: uevent trigger error
<27>Jul 21 21:17:56 node-2 multipathd: uevent trigger error
<27>Jul 21 21:17:56 node-2 multipathd: uevent trigger error
<27>Jul 21 21:17:56 node-2 multipathd: uevent trigger error
<27>Jul 21 21:17:56 node-2 multipathd: uevent trigger error
<27>Jul 21 21:17:56 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:17 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 21 21:18:17 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:17 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:17 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:17 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:17 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:23 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:23 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:23 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:23 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:23 node-2 multipathd: uevent trigger error
<27>Jul 21 21:18:23 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:18 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 21 21:21:19 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:19 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:19 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:19 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:19 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:19 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:19 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:21:24 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:14 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:14 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:14 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:14 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:14 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:14 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:35 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:35 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:35 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:35 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:35 node-2 multipathd: uevent trigger error
<27>Jul 21 21:22:35 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Jul 21 21:23:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Jul 21 21:23:30 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Jul 21 21:23:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Jul 21 21:23:31 node-2 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Jul 21 21:23:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:32 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:45 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:45 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:45 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:45 node-2 multipathd: uevent trigger error
<27>Jul 21 21:23:45 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:00 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:00 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:00 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:00 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:00 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:00 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:18 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:18 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:18 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:18 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:18 node-2 multipathd: uevent trigger error
<27>Jul 21 21:24:20 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 21 21:26:40 node-2 multipathd: uevent trigger error
<27>Jul 21 21:26:40 node-2 multipathd: uevent trigger error
<27>Jul 21 21:26:40 node-2 multipathd: uevent trigger error
<27>Jul 21 21:26:40 node-2 multipathd: uevent trigger error
<27>Jul 21 21:26:40 node-2 multipathd: uevent trigger error
<27>Jul 21 21:26:40 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:16 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:21 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 21 21:27:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:21 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:46 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:46 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:46 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:46 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:50 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:50 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:50 node-2 multipathd: uevent trigger error
<27>Jul 21 21:27:50 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:02 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:02 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:02 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:02 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:02 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:02 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:57 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:57 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:57 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:57 node-2 multipathd: uevent trigger error
<27>Jul 21 21:28:57 node-2 multipathd: uevent trigger error
<27>Jul 21 21:30:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:30:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:30:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:30:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:30:09 node-2 multipathd: uevent trigger error
<27>Jul 21 21:30:23 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 21 21:30:28 node-2 multipathd: uevent trigger error
<27>Jul 21 21:30:28 node-2 multipathd: uevent trigger error
<27>Jul 21 21:30:28 node-2 multipathd: uevent trigger error
<27>Jul 21 21:30:28 node-2 multipathd: uevent trigger error
<27>Jul 21 21:30:28 node-2 multipathd: uevent trigger error
<11>Jul 21 21:30:41 node-2 liberasurecode[28693]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:41 node-2 liberasurecode[28693]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:41 node-2 liberasurecode[28693]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:41 node-2 liberasurecode[28693]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:41 node-2 liberasurecode[28717]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:41 node-2 liberasurecode[28717]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:41 node-2 liberasurecode[28717]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:41 node-2 liberasurecode[28717]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:43 node-2 liberasurecode[29517]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:43 node-2 liberasurecode[29517]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:43 node-2 liberasurecode[29517]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:43 node-2 liberasurecode[29517]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:48 node-2 liberasurecode[31444]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:48 node-2 liberasurecode[31444]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:48 node-2 liberasurecode[31444]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:48 node-2 liberasurecode[31444]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:48 node-2 liberasurecode[31487]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:48 node-2 liberasurecode[31487]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:48 node-2 liberasurecode[31487]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:48 node-2 liberasurecode[31487]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31525]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31525]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31525]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31525]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31613]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31613]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31613]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31613]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31625]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31625]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31625]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31625]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31639]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31639]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31639]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31639]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31651]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31651]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31651]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:49 node-2 liberasurecode[31651]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:58 node-2 liberasurecode[32088]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:58 node-2 liberasurecode[32088]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:58 node-2 liberasurecode[32088]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:30:58 node-2 liberasurecode[32088]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 21 21:31:06 node-2 multipathd: uevent trigger error
<27>Jul 21 21:31:06 node-2 multipathd: uevent trigger error
<27>Jul 21 21:31:06 node-2 multipathd: uevent trigger error
<27>Jul 21 21:31:06 node-2 multipathd: uevent trigger error
<27>Jul 21 21:31:06 node-2 multipathd: uevent trigger error
<43>Jul 21 21:32:04 node-2 apache2_error [Thu Jul 21 21:31:54.550777 2016] [mpm_worker:notice] [pid 29382:tid 139853138352000] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 21 21:32:04 node-2 apache2_error [Thu Jul 21 21:31:54.935132 2016] [mpm_worker:warn] [pid 29382:tid 139853138352000] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 21 21:32:04 node-2 apache2_error [Thu Jul 21 21:31:54.947127 2016] [mpm_worker:notice] [pid 29382:tid 139853138352000] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 21 21:32:04 node-2 apache2_error [Thu Jul 21 21:31:54.947164 2016] [core:notice] [pid 29382:tid 139853138352000] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 21 21:32:34 node-2 apache2_error [Thu Jul 21 21:32:32.120943 2016] [mpm_worker:notice] [pid 29382:tid 139853138352000] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 21 21:32:34 node-2 apache2_error [Thu Jul 21 21:32:32.317737 2016] [mpm_worker:warn] [pid 29382:tid 139853138352000] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 21 21:32:34 node-2 apache2_error [Thu Jul 21 21:32:32.327305 2016] [mpm_worker:notice] [pid 29382:tid 139853138352000] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 21 21:32:34 node-2 apache2_error [Thu Jul 21 21:32:32.327351 2016] [core:notice] [pid 29382:tid 139853138352000] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 21 21:32:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:32:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:32:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:32:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:32:36 node-2 multipathd: uevent trigger error
<27>Jul 21 21:32:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:32:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:32:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:32:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:32:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:22 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:24 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 21 21:33:24 node-2 apache2_error [Thu Jul 21 21:33:18.181444 2016] [mpm_worker:notice] [pid 29382:tid 139853138352000] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 21 21:33:24 node-2 apache2_error [Thu Jul 21 21:33:18.377164 2016] [mpm_worker:warn] [pid 29382:tid 139853138352000] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 21 21:33:24 node-2 apache2_error [Thu Jul 21 21:33:18.386106 2016] [mpm_worker:notice] [pid 29382:tid 139853138352000] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 21 21:33:24 node-2 apache2_error [Thu Jul 21 21:33:18.386133 2016] [core:notice] [pid 29382:tid 139853138352000] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 21 21:33:29 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:29 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:29 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:29 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:29 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:33 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:39 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:39 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:39 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:39 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:39 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:49 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:49 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:49 node-2 multipathd: uevent trigger error
<27>Jul 21 21:33:49 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:04 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:27 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:34 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 21 21:34:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:48 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:53 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:53 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:53 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:53 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:53 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:59 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:59 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:59 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:59 node-2 multipathd: uevent trigger error
<27>Jul 21 21:34:59 node-2 multipathd: uevent trigger error
<11>Jul 21 21:35:02 node-2 liberasurecode[25197]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:35:02 node-2 liberasurecode[25197]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:35:02 node-2 liberasurecode[25197]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:35:02 node-2 liberasurecode[25197]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 21 21:35:11 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 21 21:35:11 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:11 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:11 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:11 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:11 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:38 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:42 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:43 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:56 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:56 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:56 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:56 node-2 multipathd: uevent trigger error
<27>Jul 21 21:35:56 node-2 multipathd: uevent trigger error
<27>Jul 21 21:36:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:36:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:36:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:36:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:36:03 node-2 multipathd: uevent trigger error
<27>Jul 21 21:36:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:36:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:36:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:36:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:36:08 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:25 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:30 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:30 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:30 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:30 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:30 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:34 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:34 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:34 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:34 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:34 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:39 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:39 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:39 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:39 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:39 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:44 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:44 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:44 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:44 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:44 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:49 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:49 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:49 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:49 node-2 multipathd: uevent trigger error
<27>Jul 21 21:37:49 node-2 multipathd: uevent trigger error
<11>Jul 21 21:40:01 node-2 liberasurecode[10806]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:40:01 node-2 liberasurecode[10806]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:40:01 node-2 liberasurecode[10806]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 21 21:40:01 node-2 liberasurecode[10806]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
