Jul 25 16:50:46 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8372" x-info="http://www.rsyslog.com"] start
Jul 25 16:50:46 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 25 16:50:46 node-2 rsyslogd: rsyslogd's groupid changed to 104
Jul 25 16:50:46 node-2 rsyslogd: rsyslogd's userid changed to 101
Jul 25 16:50:46 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 25 16:50:46 node-2 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 25 16:50:46 node-2 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 25 16:50:46 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 25 16:50:46 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=1681dc78-cc21-4aa3-9b24-23d745c98720 nomdmonddf nomdmonisw
Jul 25 16:50:46 node-2 kernel: [    0.000000] KERNEL supported cpus:
Jul 25 16:50:46 node-2 kernel: [    0.000000]   Intel GenuineIntel
Jul 25 16:50:46 node-2 kernel: [    0.000000]   AMD AuthenticAMD
Jul 25 16:50:46 node-2 kernel: [    0.000000]   Centaur CentaurHauls
Jul 25 16:50:46 node-2 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 25 16:50:46 node-2 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 25 16:50:46 node-2 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 25 16:50:46 node-2 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 25 16:50:46 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 25 16:50:46 node-2 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 25 16:50:46 node-2 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 25 16:50:46 node-2 kernel: [    0.000000] No AGP bridge found
Jul 25 16:50:46 node-2 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 25 16:50:46 node-2 kernel: [    0.000000] MTRR default type: write-back
Jul 25 16:50:46 node-2 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 25 16:50:46 node-2 kernel: [    0.000000]   00000-9FFFF write-back
Jul 25 16:50:46 node-2 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 25 16:50:46 node-2 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 25 16:50:46 node-2 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 25 16:50:46 node-2 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 25 16:50:46 node-2 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 25 16:50:46 node-2 kernel: [    0.000000]   2 disabled
Jul 25 16:50:46 node-2 kernel: [    0.000000]   3 disabled
Jul 25 16:50:46 node-2 kernel: [    0.000000]   4 disabled
Jul 25 16:50:46 node-2 kernel: [    0.000000]   5 disabled
Jul 25 16:50:46 node-2 kernel: [    0.000000]   6 disabled
Jul 25 16:50:46 node-2 kernel: [    0.000000]   7 disabled
Jul 25 16:50:46 node-2 kernel: [    0.000000]   8 disabled
Jul 25 16:50:46 node-2 kernel: [    0.000000]   9 disabled
Jul 25 16:50:46 node-2 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 25 16:50:46 node-2 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 25 16:50:46 node-2 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 25 16:50:46 node-2 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 25 16:50:46 node-2 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 25 16:50:46 node-2 kernel: [    0.000000] Using GB pages for direct mapping
Jul 25 16:50:46 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 25 16:50:46 node-2 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 25 16:50:46 node-2 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 25 16:50:46 node-2 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 25 16:50:46 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 25 16:50:46 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 25 16:50:46 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 25 16:50:46 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 25 16:50:46 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 25 16:50:46 node-2 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 25 16:50:46 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 25 16:50:46 node-2 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 25 16:50:46 node-2 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 25 16:50:46 node-2 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 25 16:50:46 node-2 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 25 16:50:46 node-2 kernel: [    0.000000] Zone ranges:
Jul 25 16:50:46 node-2 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] Movable zone start for each node
Jul 25 16:50:46 node-2 kernel: [    0.000000] Early memory node ranges
Jul 25 16:50:46 node-2 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 25 16:50:46 node-2 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 25 16:50:46 node-2 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 25 16:50:46 node-2 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 25 16:50:46 node-2 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 25 16:50:46 node-2 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 25 16:50:46 node-2 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 25 16:50:46 node-2 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 25 16:50:46 node-2 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 25 16:50:46 node-2 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 25 16:50:46 node-2 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 25 16:50:46 node-2 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 25 16:50:46 node-2 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 25 16:50:46 node-2 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 25 16:50:46 node-2 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 25 16:50:46 node-2 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 25 16:50:46 node-2 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 25 16:50:46 node-2 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 25 16:50:46 node-2 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 25 16:50:46 node-2 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 25 16:50:46 node-2 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 25 16:50:46 node-2 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 25 16:50:46 node-2 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 25 16:50:46 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 25 16:50:46 node-2 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 25 16:50:46 node-2 kernel: [    0.000000] Policy zone: Normal
Jul 25 16:50:46 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=1681dc78-cc21-4aa3-9b24-23d745c98720 nomdmonddf nomdmonisw
Jul 25 16:50:46 node-2 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 25 16:50:46 node-2 kernel: [    0.000000] Checking aperture...
Jul 25 16:50:46 node-2 kernel: [    0.000000] No AGP bridge found
Jul 25 16:50:46 node-2 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 25 16:50:46 node-2 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 25 16:50:46 node-2 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 25 16:50:46 node-2 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 25 16:50:46 node-2 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 25 16:50:46 node-2 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 25 16:50:46 node-2 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 25 16:50:46 node-2 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 25 16:50:46 node-2 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 25 16:50:46 node-2 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 25 16:50:46 node-2 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 25 16:50:46 node-2 kernel: [    0.000000] console [tty0] enabled
Jul 25 16:50:46 node-2 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 25 16:50:46 node-2 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 25 16:50:46 node-2 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 25 16:50:46 node-2 kernel: [    0.000000] hpet clockevent registered
Jul 25 16:50:46 node-2 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 25 16:50:46 node-2 kernel: [    0.004000] tsc: Detected 3491.920 MHz processor
Jul 25 16:50:46 node-2 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.84 BogoMIPS (lpj=13967680)
Jul 25 16:50:46 node-2 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 25 16:50:46 node-2 kernel: [    0.000043] Security Framework initialized
Jul 25 16:50:46 node-2 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 25 16:50:46 node-2 kernel: [    0.000063] Yama: becoming mindful.
Jul 25 16:50:46 node-2 kernel: [    0.001458] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.006403] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.008328] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.008356] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.008646] Initializing cgroup subsys memory
Jul 25 16:50:46 node-2 kernel: [    0.008654] Initializing cgroup subsys devices
Jul 25 16:50:46 node-2 kernel: [    0.008655] Initializing cgroup subsys freezer
Jul 25 16:50:46 node-2 kernel: [    0.008657] Initializing cgroup subsys blkio
Jul 25 16:50:46 node-2 kernel: [    0.008659] Initializing cgroup subsys perf_event
Jul 25 16:50:46 node-2 kernel: [    0.008661] Initializing cgroup subsys hugetlb
Jul 25 16:50:46 node-2 kernel: [    0.008680] CPU: Physical Processor ID: 0
Jul 25 16:50:46 node-2 kernel: [    0.008681] CPU: Processor Core ID: 0
Jul 25 16:50:46 node-2 kernel: [    0.008685] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 25 16:50:46 node-2 kernel: [    0.008685] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 25 16:50:46 node-2 kernel: [    0.009379] mce: CPU supports 22 MCE banks
Jul 25 16:50:46 node-2 kernel: [    0.009406] CPU0: Thermal monitoring enabled (TM1)
Jul 25 16:50:46 node-2 kernel: [    0.009427] process: using mwait in idle threads
Jul 25 16:50:46 node-2 kernel: [    0.009430] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 25 16:50:46 node-2 kernel: [    0.009430] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 25 16:50:46 node-2 kernel: [    0.009430] tlb_flushall_shift: 6
Jul 25 16:50:46 node-2 kernel: [    0.009519] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 25 16:50:46 node-2 kernel: [    0.010242] ACPI: Core revision 20131115
Jul 25 16:50:46 node-2 kernel: [    0.022901] ACPI: All ACPI Tables successfully acquired
Jul 25 16:50:46 node-2 kernel: [    0.023058] ftrace: allocating 28617 entries in 112 pages
Jul 25 16:50:46 node-2 kernel: [    0.031871] dmar: Host address width 46
Jul 25 16:50:46 node-2 kernel: [    0.031873] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 25 16:50:46 node-2 kernel: [    0.031879] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 25 16:50:46 node-2 kernel: [    0.031881] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 25 16:50:46 node-2 kernel: [    0.031885] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 25 16:50:46 node-2 kernel: [    0.031886] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 25 16:50:46 node-2 kernel: [    0.031887] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 25 16:50:46 node-2 kernel: [    0.031888] dmar: ATSR flags: 0x0
Jul 25 16:50:46 node-2 kernel: [    0.031890] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 25 16:50:46 node-2 kernel: [    0.031891] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 25 16:50:46 node-2 kernel: [    0.032007] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 25 16:50:46 node-2 kernel: [    0.032008] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 25 16:50:46 node-2 kernel: [    0.032009] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 25 16:50:46 node-2 kernel: [    0.032010] HPET id 0 under DRHD base 0xc7ffc000
Jul 25 16:50:46 node-2 kernel: [    0.032011] Your BIOS is broken and requested that x2apic be disabled.
Jul 25 16:50:46 node-2 kernel: [    0.032011] This will slightly decrease performance.
Jul 25 16:50:46 node-2 kernel: [    0.032011] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 25 16:50:46 node-2 kernel: [    0.032443] Enabled IRQ remapping in xapic mode
Jul 25 16:50:46 node-2 kernel: [    0.032444] x2apic not enabled, IRQ remapping is in xapic mode
Jul 25 16:50:46 node-2 kernel: [    0.032447] Switched APIC routing to physical flat.
Jul 25 16:50:46 node-2 kernel: [    0.033066] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 25 16:50:46 node-2 kernel: [    0.072716] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 25 16:50:46 node-2 kernel: [    0.072721] TSC deadline timer enabled
Jul 25 16:50:46 node-2 kernel: [    0.072729] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 25 16:50:46 node-2 kernel: [    0.072735] ... version:                3
Jul 25 16:50:46 node-2 kernel: [    0.072736] ... bit width:              48
Jul 25 16:50:46 node-2 kernel: [    0.072737] ... generic registers:      4
Jul 25 16:50:46 node-2 kernel: [    0.072738] ... value mask:             0000ffffffffffff
Jul 25 16:50:46 node-2 kernel: [    0.072739] ... max period:             0000ffffffffffff
Jul 25 16:50:46 node-2 kernel: [    0.072740] ... fixed-purpose events:   3
Jul 25 16:50:46 node-2 kernel: [    0.072741] ... event mask:             000000070000000f
Jul 25 16:50:46 node-2 kernel: [    0.074165] x86: Booting SMP configuration:
Jul 25 16:50:46 node-2 kernel: [    0.088268] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 25 16:50:46 node-2 kernel: [    0.074167] .... node  #0, CPUs:        #1  #2  #3
Jul 25 16:50:46 node-2 kernel: [    0.116179] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 25 16:50:46 node-2 kernel: [    0.270315] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 25 16:50:46 node-2 kernel: [    0.325930] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 25 16:50:46 node-2 kernel: [    0.382987] x86: Booted up 2 nodes, 16 CPUs
Jul 25 16:50:46 node-2 kernel: [    0.382990] smpboot: Total of 16 processors activated (111753.54 BogoMIPS)
Jul 25 16:50:46 node-2 kernel: [    0.406936] devtmpfs: initialized
Jul 25 16:50:46 node-2 kernel: [    0.410017] EVM: security.selinux
Jul 25 16:50:46 node-2 kernel: [    0.410019] EVM: security.SMACK64
Jul 25 16:50:46 node-2 kernel: [    0.410020] EVM: security.ima
Jul 25 16:50:46 node-2 kernel: [    0.410021] EVM: security.capability
Jul 25 16:50:46 node-2 kernel: [    0.410070] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.410737] pinctrl core: initialized pinctrl subsystem
Jul 25 16:50:46 node-2 kernel: [    0.410801] regulator-dummy: no parameters
Jul 25 16:50:46 node-2 kernel: [    0.410833] RTC time: 16:50:11, date: 07/25/16
Jul 25 16:50:46 node-2 kernel: [    0.410868] NET: Registered protocol family 16
Jul 25 16:50:46 node-2 kernel: [    0.410950] cpuidle: using governor ladder
Jul 25 16:50:46 node-2 kernel: [    0.410951] cpuidle: using governor menu
Jul 25 16:50:46 node-2 kernel: [    0.410984] ACPI: bus type PCI registered
Jul 25 16:50:46 node-2 kernel: [    0.410986] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 25 16:50:46 node-2 kernel: [    0.411032] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 25 16:50:46 node-2 kernel: [    0.411035] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 25 16:50:46 node-2 kernel: [    0.424768] PCI: Using configuration type 1 for base access
Jul 25 16:50:46 node-2 kernel: [    0.425752] bio: create slab <bio-0> at 0
Jul 25 16:50:46 node-2 kernel: [    0.426031] ACPI: Added _OSI(Module Device)
Jul 25 16:50:46 node-2 kernel: [    0.426032] ACPI: Added _OSI(Processor Device)
Jul 25 16:50:46 node-2 kernel: [    0.426034] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 25 16:50:46 node-2 kernel: [    0.426035] ACPI: Added _OSI(Processor Aggregator Device)
Jul 25 16:50:46 node-2 kernel: [    0.438669] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 25 16:50:46 node-2 kernel: [    0.449240] ACPI: Interpreter enabled
Jul 25 16:50:46 node-2 kernel: [    0.449246] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 25 16:50:46 node-2 kernel: [    0.449250] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 25 16:50:46 node-2 kernel: [    0.449252] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 25 16:50:46 node-2 kernel: [    0.449259] ACPI: (supports S0 S4 S5)
Jul 25 16:50:46 node-2 kernel: [    0.449261] ACPI: Using IOAPIC for interrupt routing
Jul 25 16:50:46 node-2 kernel: [    0.449301] HEST: Table parsing has been initialized.
Jul 25 16:50:46 node-2 kernel: [    0.449304] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 25 16:50:46 node-2 kernel: [    0.449854] ACPI: No dock devices found.
Jul 25 16:50:46 node-2 kernel: [    0.461537] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 25 16:50:46 node-2 kernel: [    0.461542] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 16:50:46 node-2 kernel: [    0.461545] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 25 16:50:46 node-2 kernel: [    0.461574] PCI host bridge to bus 0000:ff
Jul 25 16:50:46 node-2 kernel: [    0.461576] pci_bus 0000:ff: root bus resource [bus ff]
Jul 25 16:50:46 node-2 kernel: [    0.461584] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461622] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.461653] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461688] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461717] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.461747] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.461778] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461807] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461836] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461865] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461891] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461917] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461945] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461971] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.461998] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462024] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462053] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462080] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462107] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.462135] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462162] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.462187] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462213] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462243] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.462278] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462309] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462339] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462369] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462400] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462431] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462462] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462492] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462523] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462554] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462587] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462620] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462653] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462684] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462711] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462743] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462775] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462813] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462849] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462881] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462909] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462940] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.462972] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463002] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463035] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463066] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463098] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463127] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463156] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463186] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463218] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463249] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463281] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463338] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 25 16:50:46 node-2 kernel: [    0.463341] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 16:50:46 node-2 kernel: [    0.463344] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 25 16:50:46 node-2 kernel: [    0.463362] PCI host bridge to bus 0000:7f
Jul 25 16:50:46 node-2 kernel: [    0.463364] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 25 16:50:46 node-2 kernel: [    0.463369] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463396] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.463425] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463459] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463481] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.463506] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.463533] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463557] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463579] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463602] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463625] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463649] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463674] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463698] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463723] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463751] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463773] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463796] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463818] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.463842] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463864] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.463885] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463908] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463935] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 25 16:50:46 node-2 kernel: [    0.463967] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.463993] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464019] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464047] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464072] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464099] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464125] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464152] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464178] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464206] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464233] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464261] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464289] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464313] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464338] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464367] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464392] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464420] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464449] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464477] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464504] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464528] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464554] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464580] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464606] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464632] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464661] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464684] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464706] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464731] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464756] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464785] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.464811] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.466051] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 25 16:50:46 node-2 kernel: [    0.466055] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 16:50:46 node-2 kernel: [    0.467172] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 25 16:50:46 node-2 kernel: [    0.467681] PCI host bridge to bus 0000:00
Jul 25 16:50:46 node-2 kernel: [    0.467683] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 25 16:50:46 node-2 kernel: [    0.467685] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 25 16:50:46 node-2 kernel: [    0.467686] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 25 16:50:46 node-2 kernel: [    0.467687] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 25 16:50:46 node-2 kernel: [    0.467689] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 25 16:50:46 node-2 kernel: [    0.467690] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 25 16:50:46 node-2 kernel: [    0.467692] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 25 16:50:46 node-2 kernel: [    0.467697] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 25 16:50:46 node-2 kernel: [    0.467779] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.467809] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.467851] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 25 16:50:46 node-2 kernel: [    0.467869] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.467899] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.467939] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 25 16:50:46 node-2 kernel: [    0.467957] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.467986] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.468029] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 25 16:50:46 node-2 kernel: [    0.468046] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.468115] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.468191] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.468267] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 25 16:50:46 node-2 kernel: [    0.468272] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 25 16:50:46 node-2 kernel: [    0.468356] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 25 16:50:46 node-2 kernel: [    0.468503] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 25 16:50:46 node-2 kernel: [    0.468521] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 25 16:50:46 node-2 kernel: [    0.468599] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.468653] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 25 16:50:46 node-2 kernel: [    0.468674] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.468730] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.468773] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 25 16:50:46 node-2 kernel: [    0.468800] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.468856] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.468898] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 25 16:50:46 node-2 kernel: [    0.468922] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 25 16:50:46 node-2 kernel: [    0.468939] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 25 16:50:46 node-2 kernel: [    0.469018] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.469067] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 25 16:50:46 node-2 kernel: [    0.469092] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 25 16:50:46 node-2 kernel: [    0.469340] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 25 16:50:46 node-2 kernel: [    0.469346] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 25 16:50:46 node-2 kernel: [    0.469352] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.469358] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.469365] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 25 16:50:46 node-2 kernel: [    0.469395] pci 0000:01:00.0: supports D1 D2
Jul 25 16:50:46 node-2 kernel: [    0.475465] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 25 16:50:46 node-2 kernel: [    0.475471] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 25 16:50:46 node-2 kernel: [    0.475476] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 25 16:50:46 node-2 kernel: [    0.475738] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.475771] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 25 16:50:46 node-2 kernel: [    0.483461] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 25 16:50:46 node-2 kernel: [    0.483464] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.483465] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 16:50:46 node-2 kernel: [    0.483521] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.483588] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.483668] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.483713] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 25 16:50:46 node-2 kernel: [    0.483717] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.483719] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 16:50:46 node-2 kernel: [    0.483771] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.483894] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.483947] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 25 16:50:46 node-2 kernel: [    0.483950] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.483952] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 16:50:46 node-2 kernel: [    0.484001] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.484120] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.484176] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.484300] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.484338] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.484457] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.484497] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 25 16:50:46 node-2 kernel: [    0.484622] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 25 16:50:46 node-2 kernel: [    0.484668] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 25 16:50:46 node-2 kernel: [    0.484671] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.484672] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 16:50:46 node-2 kernel: [    0.484740] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 25 16:50:46 node-2 kernel: [    0.484806] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.484857] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.484898] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 25 16:50:46 node-2 kernel: [    0.484979] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 25 16:50:46 node-2 kernel: [    0.485085] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 25 16:50:46 node-2 kernel: [    0.485087] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.485089] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 25 16:50:46 node-2 kernel: [    0.485146] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 25 16:50:46 node-2 kernel: [    0.485218] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.485265] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.485476] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 25 16:50:46 node-2 kernel: [    0.485480] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 25 16:50:46 node-2 kernel: [    0.485543] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 25 16:50:46 node-2 kernel: [    0.485596] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.485644] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.485856] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 25 16:50:46 node-2 kernel: [    0.485860] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 25 16:50:46 node-2 kernel: [    0.485919] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 25 16:50:46 node-2 kernel: [    0.485979] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.486031] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 25 16:50:46 node-2 kernel: [    0.486275] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 25 16:50:46 node-2 kernel: [    0.486278] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 25 16:50:46 node-2 kernel: [    0.486453] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 25 16:50:46 node-2 kernel: [    0.486491] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 25 16:50:46 node-2 kernel: [    0.486568] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 25 16:50:46 node-2 kernel: [    0.486587] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 25 16:50:46 node-2 kernel: [    0.486601] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 25 16:50:46 node-2 kernel: [    0.486614] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 25 16:50:46 node-2 kernel: [    0.486664] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 25 16:50:46 node-2 kernel: [    0.491475] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 25 16:50:46 node-2 kernel: [    0.491484] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 25 16:50:46 node-2 kernel: [    0.491536] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 25 16:50:46 node-2 kernel: [    0.492160] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 25 16:50:46 node-2 kernel: [    0.492163] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 25 16:50:46 node-2 kernel: [    0.492288] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 25 16:50:46 node-2 kernel: [    0.492395] PCI host bridge to bus 0000:80
Jul 25 16:50:46 node-2 kernel: [    0.492397] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 25 16:50:46 node-2 kernel: [    0.492398] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 25 16:50:46 node-2 kernel: [    0.492400] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 25 16:50:46 node-2 kernel: [    0.492407] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.492471] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.492539] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 25 16:50:46 node-2 kernel: [    0.492601] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 25 16:50:46 node-2 kernel: [    0.492607] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 25 16:50:46 node-2 kernel: [    0.492680] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 25 16:50:46 node-2 kernel: [    0.492979] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 25 16:50:46 node-2 kernel: [    0.493011] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 25 16:50:46 node-2 kernel: [    0.493041] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 25 16:50:46 node-2 kernel: [    0.493070] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 25 16:50:46 node-2 kernel: [    0.493099] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 16:50:46 node-2 kernel: [    0.493129] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 16:50:46 node-2 kernel: [    0.493158] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 16:50:46 node-2 kernel: [    0.493188] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 25 16:50:46 node-2 kernel: [    0.493274] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 25 16:50:46 node-2 kernel: [    0.493278] ACPI: \_SB_.UNC1: notify handler is installed
Jul 25 16:50:46 node-2 kernel: [    0.493279] ACPI: \_SB_.UNC0: notify handler is installed
Jul 25 16:50:46 node-2 kernel: [    0.493294] ACPI: \_SB_.PCI0: notify handler is installed
Jul 25 16:50:46 node-2 kernel: [    0.493347] ACPI: \_SB_.PCI1: notify handler is installed
Jul 25 16:50:46 node-2 kernel: [    0.493426] Found 4 acpi root devices
Jul 25 16:50:46 node-2 kernel: [    0.493545] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 25 16:50:46 node-2 kernel: [    0.493547] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 25 16:50:46 node-2 kernel: [    0.493549] vgaarb: loaded
Jul 25 16:50:46 node-2 kernel: [    0.493550] vgaarb: bridge control possible 0000:0c:00.0
Jul 25 16:50:46 node-2 kernel: [    0.493671] SCSI subsystem initialized
Jul 25 16:50:46 node-2 kernel: [    0.493732] libata version 3.00 loaded.
Jul 25 16:50:46 node-2 kernel: [    0.493747] ACPI: bus type USB registered
Jul 25 16:50:46 node-2 kernel: [    0.493757] usbcore: registered new interface driver usbfs
Jul 25 16:50:46 node-2 kernel: [    0.493763] usbcore: registered new interface driver hub
Jul 25 16:50:46 node-2 kernel: [    0.493785] usbcore: registered new device driver usb
Jul 25 16:50:46 node-2 kernel: [    0.493944] PCI: Using ACPI for IRQ routing
Jul 25 16:50:46 node-2 kernel: [    0.497553] PCI: pci_cache_line_size set to 64 bytes
Jul 25 16:50:46 node-2 kernel: [    0.497754] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 25 16:50:46 node-2 kernel: [    0.497755] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 25 16:50:46 node-2 kernel: [    0.497756] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 25 16:50:46 node-2 kernel: [    0.497821] NetLabel: Initializing
Jul 25 16:50:46 node-2 kernel: [    0.497823] NetLabel:  domain hash size = 128
Jul 25 16:50:46 node-2 kernel: [    0.497823] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 25 16:50:46 node-2 kernel: [    0.497833] NetLabel:  unlabeled traffic allowed by default
Jul 25 16:50:46 node-2 kernel: [    0.497889] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 25 16:50:46 node-2 kernel: [    0.497893] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 25 16:50:46 node-2 kernel: [    0.499949] Switched to clocksource hpet
Jul 25 16:50:46 node-2 kernel: [    0.503878] AppArmor: AppArmor Filesystem Enabled
Jul 25 16:50:46 node-2 kernel: [    0.503892] pnp: PnP ACPI init
Jul 25 16:50:46 node-2 kernel: [    0.503906] ACPI: bus type PNP registered
Jul 25 16:50:46 node-2 kernel: [    0.504021] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 25 16:50:46 node-2 kernel: [    0.504029] pnp 00:01: [dma 4]
Jul 25 16:50:46 node-2 kernel: [    0.504040] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 25 16:50:46 node-2 kernel: [    0.504066] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 25 16:50:46 node-2 kernel: [    0.504086] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 25 16:50:46 node-2 kernel: [    0.504103] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 25 16:50:46 node-2 kernel: [    0.504135] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 25 16:50:46 node-2 kernel: [    0.504185] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504188] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 25 16:50:46 node-2 kernel: [    0.504189] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504191] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504192] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504196] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504199] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 25 16:50:46 node-2 kernel: [    0.504200] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504202] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504203] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504205] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504206] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504208] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 25 16:50:46 node-2 kernel: [    0.504210] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 25 16:50:46 node-2 kernel: [    0.504294] pnp 00:07: [dma 0 disabled]
Jul 25 16:50:46 node-2 kernel: [    0.504322] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 25 16:50:46 node-2 kernel: [    0.504396] pnp 00:08: [dma 0 disabled]
Jul 25 16:50:46 node-2 kernel: [    0.504427] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 25 16:50:46 node-2 kernel: [    0.504477] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 25 16:50:46 node-2 kernel: [    0.504824] pnp: PnP ACPI: found 10 devices
Jul 25 16:50:46 node-2 kernel: [    0.504825] ACPI: bus type PNP unregistered
Jul 25 16:50:46 node-2 kernel: [    0.511186] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 25 16:50:46 node-2 kernel: [    0.511189] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 25 16:50:46 node-2 kernel: [    0.511191] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 25 16:50:46 node-2 kernel: [    0.511196] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 25 16:50:46 node-2 kernel: [    0.511197] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.511212] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511241] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 25 16:50:46 node-2 kernel: [    0.511255] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511284] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 25 16:50:46 node-2 kernel: [    0.511298] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 25 16:50:46 node-2 kernel: [    0.511327] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 25 16:50:46 node-2 kernel: [    0.511341] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 25 16:50:46 node-2 kernel: [    0.511370] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 25 16:50:46 node-2 kernel: [    0.511372] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.511386] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511415] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 25 16:50:46 node-2 kernel: [    0.511417] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.511432] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511461] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 25 16:50:46 node-2 kernel: [    0.511463] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.511466] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511470] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 25 16:50:46 node-2 kernel: [    0.511471] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.511474] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511478] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 25 16:50:46 node-2 kernel: [    0.511482] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 25 16:50:46 node-2 kernel: [    0.511490] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 25 16:50:46 node-2 kernel: [    0.511494] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 25 16:50:46 node-2 kernel: [    0.511500] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 25 16:50:46 node-2 kernel: [    0.511501] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 25 16:50:46 node-2 kernel: [    0.511502] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 25 16:50:46 node-2 kernel: [    0.511503] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 25 16:50:46 node-2 kernel: [    0.511504] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 25 16:50:46 node-2 kernel: [    0.511504] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 25 16:50:46 node-2 kernel: [    0.511505] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 25 16:50:46 node-2 kernel: [    0.511506] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 25 16:50:46 node-2 kernel: [    0.511507] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.511508] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511509] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.511510] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511511] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.511511] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511512] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.511513] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511514] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 25 16:50:46 node-2 kernel: [    0.511515] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511516] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 25 16:50:46 node-2 kernel: [    0.511517] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 25 16:50:46 node-2 kernel: [    0.511518] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 25 16:50:46 node-2 kernel: [    0.511519] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 25 16:50:46 node-2 kernel: [    0.511521] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 25 16:50:46 node-2 kernel: [    0.511522] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 25 16:50:46 node-2 kernel: [    0.511556] NET: Registered protocol family 2
Jul 25 16:50:46 node-2 kernel: [    0.511819] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.512155] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.512300] TCP: Hash tables configured (established 262144 bind 65536)
Jul 25 16:50:46 node-2 kernel: [    0.512336] TCP: reno registered
Jul 25 16:50:46 node-2 kernel: [    0.512365] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.512458] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.512604] NET: Registered protocol family 1
Jul 25 16:50:46 node-2 kernel: [    0.552044] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 25 16:50:46 node-2 kernel: [    0.552058] PCI: CLS 64 bytes, default 64
Jul 25 16:50:46 node-2 kernel: [    0.552133] Trying to unpack rootfs image as initramfs...
Jul 25 16:50:46 node-2 kernel: [    0.771112] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 25 16:50:46 node-2 kernel: [    0.771156] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 25 16:50:46 node-2 kernel: [    0.771159] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 25 16:50:46 node-2 kernel: [    0.771569] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771575] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771580] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771586] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771598] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771615] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771630] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771646] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771667] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771676] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771682] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771689] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771695] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771703] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771710] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771727] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 25 16:50:46 node-2 kernel: [    0.771809] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 25 16:50:46 node-2 kernel: [    0.771812] Scanning for low memory corruption every 60 seconds
Jul 25 16:50:46 node-2 kernel: [    0.772191] Initialise system trusted keyring
Jul 25 16:50:46 node-2 kernel: [    0.772246] audit: initializing netlink socket (disabled)
Jul 25 16:50:46 node-2 kernel: [    0.772262] type=2000 audit(1469465410.728:1): initialized
Jul 25 16:50:46 node-2 kernel: [    0.790127] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 25 16:50:46 node-2 kernel: [    0.791653] zbud: loaded
Jul 25 16:50:46 node-2 kernel: [    0.791785] VFS: Disk quotas dquot_6.5.2
Jul 25 16:50:46 node-2 kernel: [    0.791825] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 25 16:50:46 node-2 kernel: [    0.792197] fuse init (API version 7.22)
Jul 25 16:50:46 node-2 kernel: [    0.792257] msgmni has been set to 32768
Jul 25 16:50:46 node-2 kernel: [    0.792306] Key type big_key registered
Jul 25 16:50:46 node-2 kernel: [    0.792799] Key type asymmetric registered
Jul 25 16:50:46 node-2 kernel: [    0.792801] Asymmetric key parser 'x509' registered
Jul 25 16:50:46 node-2 kernel: [    0.792823] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 25 16:50:46 node-2 kernel: [    0.792894] io scheduler noop registered
Jul 25 16:50:46 node-2 kernel: [    0.792896] io scheduler deadline registered (default)
Jul 25 16:50:46 node-2 kernel: [    0.792915] io scheduler cfq registered
Jul 25 16:50:46 node-2 kernel: [    0.793439] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    0.793608] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    0.793725] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    0.793837] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    0.793951] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    0.794049] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    0.794451] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 25 16:50:46 node-2 kernel: [    0.794477] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 25 16:50:46 node-2 kernel: [    0.794494] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 25 16:50:46 node-2 kernel: [    0.794502] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794504] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794507] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 25 16:50:46 node-2 kernel: [    0.794512] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794514] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794515] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794516] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794518] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794519] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794521] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794522] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794523] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794525] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794526] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794527] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794530] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 25 16:50:46 node-2 kernel: [    0.794535] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794537] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 25 16:50:46 node-2 kernel: [    0.794552] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794555] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 25 16:50:46 node-2 kernel: [    0.794565] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794567] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 25 16:50:46 node-2 kernel: [    0.794570] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 25 16:50:46 node-2 kernel: [    0.794609] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 25 16:50:46 node-2 kernel: [    0.794615] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 25 16:50:46 node-2 kernel: [    0.794620] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 25 16:50:46 node-2 kernel: [    0.794629] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 25 16:50:46 node-2 kernel: [    0.794670] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 25 16:50:46 node-2 kernel: [    0.794671] vesafb: scrolling: redraw
Jul 25 16:50:46 node-2 kernel: [    0.794673] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 25 16:50:46 node-2 kernel: [    0.815228] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 25 16:50:46 node-2 kernel: [    0.823730] Console: switching to colour frame buffer device 80x30
Jul 25 16:50:46 node-2 kernel: [    0.832404] fb0: VESA VGA frame buffer device
Jul 25 16:50:46 node-2 kernel: [    0.832600] intel_idle: MWAIT substates: 0x2120
Jul 25 16:50:46 node-2 kernel: [    0.832601] intel_idle: v0.4 model 0x3F
Jul 25 16:50:46 node-2 kernel: [    0.832602] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 25 16:50:46 node-2 kernel: [    0.832834] ipmi message handler version 39.2
Jul 25 16:50:46 node-2 kernel: [    0.833104] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 25 16:50:46 node-2 kernel: [    0.833538] ACPI: AC Adapter [P111] (on-line)
Jul 25 16:50:46 node-2 kernel: [    0.838761] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 25 16:50:46 node-2 kernel: [    0.849761] ACPI: Power Button [PWRB]
Jul 25 16:50:46 node-2 kernel: [    0.855513] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 25 16:50:46 node-2 kernel: [    0.867126] ACPI: Power Button [PWRF]
Jul 25 16:50:46 node-2 kernel: [    0.893502] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 25 16:50:46 node-2 kernel: [    0.905313] pstore: Registered erst as persistent store backend
Jul 25 16:50:46 node-2 kernel: [    0.911643] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 25 16:50:46 node-2 kernel: [    0.923744] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 25 16:50:46 node-2 kernel: [    0.950571] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 25 16:50:46 node-2 kernel: [    0.983823] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 25 16:50:46 node-2 kernel: [    0.997900] Linux agpgart interface v0.103
Jul 25 16:50:46 node-2 kernel: [    1.005535] brd: module loaded
Jul 25 16:50:46 node-2 kernel: [    1.012589] loop: module loaded
Jul 25 16:50:46 node-2 kernel: [    1.019312] libphy: Fixed MDIO Bus: probed
Jul 25 16:50:46 node-2 kernel: [    1.025780] tun: Universal TUN/TAP device driver, 1.6
Jul 25 16:50:46 node-2 kernel: [    1.032293] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 25 16:50:46 node-2 kernel: [    1.038843] PPP generic driver version 2.4.2
Jul 25 16:50:46 node-2 kernel: [    1.045284] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 25 16:50:46 node-2 kernel: [    1.051712] ehci-pci: EHCI PCI platform driver
Jul 25 16:50:46 node-2 kernel: [    1.058229] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 25 16:50:46 node-2 kernel: [    1.064642] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 25 16:50:46 node-2 kernel: [    1.077167] ehci-pci 0000:00:1a.0: debug port 2
Jul 25 16:50:46 node-2 kernel: [    1.087370] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 25 16:50:46 node-2 kernel: [    1.087388] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 25 16:50:46 node-2 kernel: [    1.103442] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 25 16:50:46 node-2 kernel: [    1.109599] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 25 16:50:46 node-2 kernel: [    1.115809] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 25 16:50:46 node-2 kernel: [    1.127697] usb usb1: Product: EHCI Host Controller
Jul 25 16:50:46 node-2 kernel: [    1.133803] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 25 16:50:46 node-2 kernel: [    1.139860] usb usb1: SerialNumber: 0000:00:1a.0
Jul 25 16:50:46 node-2 kernel: [    1.145809] hub 1-0:1.0: USB hub found
Jul 25 16:50:46 node-2 kernel: [    1.151574] hub 1-0:1.0: 2 ports detected
Jul 25 16:50:46 node-2 kernel: [    1.157366] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 25 16:50:46 node-2 kernel: [    1.162952] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 25 16:50:46 node-2 kernel: [    1.173861] ehci-pci 0000:00:1d.0: debug port 2
Jul 25 16:50:46 node-2 kernel: [    1.183172] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 25 16:50:46 node-2 kernel: [    1.183175] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 25 16:50:46 node-2 kernel: [    1.199360] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 25 16:50:46 node-2 kernel: [    1.204607] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 25 16:50:46 node-2 kernel: [    1.209936] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 25 16:50:46 node-2 kernel: [    1.220515] usb usb2: Product: EHCI Host Controller
Jul 25 16:50:46 node-2 kernel: [    1.225988] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 25 16:50:46 node-2 kernel: [    1.231534] usb usb2: SerialNumber: 0000:00:1d.0
Jul 25 16:50:46 node-2 kernel: [    1.237049] hub 2-0:1.0: USB hub found
Jul 25 16:50:46 node-2 kernel: [    1.242399] hub 2-0:1.0: 2 ports detected
Jul 25 16:50:46 node-2 kernel: [    1.247732] ehci-platform: EHCI generic platform driver
Jul 25 16:50:46 node-2 kernel: [    1.252991] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 25 16:50:46 node-2 kernel: [    1.258335] ohci-pci: OHCI PCI platform driver
Jul 25 16:50:46 node-2 kernel: [    1.263645] ohci-platform: OHCI generic platform driver
Jul 25 16:50:46 node-2 kernel: [    1.268863] uhci_hcd: USB Universal Host Controller Interface driver
Jul 25 16:50:46 node-2 kernel: [    1.274223] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 25 16:50:46 node-2 kernel: [    1.467138] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 25 16:50:46 node-2 kernel: [    1.766890] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 25 16:50:46 node-2 kernel: [    1.783182] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 25 16:50:46 node-2 kernel: [    1.788787] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 25 16:50:46 node-2 kernel: [    1.794449] hub 1-1:1.0: USB hub found
Jul 25 16:50:46 node-2 kernel: [    1.800044] hub 1-1:1.0: 6 ports detected
Jul 25 16:50:46 node-2 kernel: [    1.914778] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 25 16:50:46 node-2 kernel: [    2.312869] i8042: No controller found
Jul 25 16:50:46 node-2 kernel: [    2.318395] mousedev: PS/2 mouse device common for all mice
Jul 25 16:50:46 node-2 kernel: [    2.324128] rtc_cmos 00:02: RTC can wake from S4
Jul 25 16:50:46 node-2 kernel: [    2.327293] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 25 16:50:46 node-2 kernel: [    2.327294] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 25 16:50:46 node-2 kernel: [    2.328050] hub 2-1:1.0: USB hub found
Jul 25 16:50:46 node-2 kernel: [    2.328285] hub 2-1:1.0: 8 ports detected
Jul 25 16:50:46 node-2 kernel: [    2.352448] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 25 16:50:46 node-2 kernel: [    2.358293] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 25 16:50:46 node-2 kernel: [    2.369764] device-mapper: uevent: version 1.0.3
Jul 25 16:50:46 node-2 kernel: [    2.375571] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 25 16:50:46 node-2 kernel: [    2.387003] ledtrig-cpu: registered to indicate activity on CPUs
Jul 25 16:50:46 node-2 kernel: [    2.393005] TCP: cubic registered
Jul 25 16:50:46 node-2 kernel: [    2.398922] NET: Registered protocol family 10
Jul 25 16:50:46 node-2 kernel: [    2.404985] NET: Registered protocol family 17
Jul 25 16:50:46 node-2 kernel: [    2.410755] Key type dns_resolver registered
Jul 25 16:50:46 node-2 kernel: [    2.416838] Loading compiled-in X.509 certificates
Jul 25 16:50:46 node-2 kernel: [    2.423054] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 25 16:50:46 node-2 kernel: [    2.434712] registered taskstats version 1
Jul 25 16:50:46 node-2 kernel: [    2.442854] Key type trusted registered
Jul 25 16:50:46 node-2 kernel: [    2.450545] Key type encrypted registered
Jul 25 16:50:46 node-2 kernel: [    2.456143] AppArmor: AppArmor sha1 policy hashing enabled
Jul 25 16:50:46 node-2 kernel: [    2.461747] IMA: No TPM chip found, activating TPM-bypass!
Jul 25 16:50:46 node-2 kernel: [    2.467863] regulator-dummy: disabling
Jul 25 16:50:46 node-2 kernel: [    2.473400]   Magic number: 8:370:844
Jul 25 16:50:46 node-2 kernel: [    2.478870] hub 1-1:1.0: hash matches
Jul 25 16:50:46 node-2 kernel: [    2.484295] acpi device:c5: hash matches
Jul 25 16:50:46 node-2 kernel: [    2.489757] rtc_cmos 00:02: setting system clock to 2016-07-25 16:50:13 UTC (1469465413)
Jul 25 16:50:46 node-2 kernel: [    2.502025] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 25 16:50:46 node-2 kernel: [    2.507523] EDD information not available.
Jul 25 16:50:46 node-2 kernel: [    2.512993] PM: Hibernation image not present or could not be loaded.
Jul 25 16:50:46 node-2 kernel: [    2.513860] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 25 16:50:46 node-2 kernel: [    2.524993] Write protecting the kernel read-only data: 12288k
Jul 25 16:50:46 node-2 kernel: [    2.531253] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 25 16:50:46 node-2 kernel: [    2.543795] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 25 16:50:46 node-2 kernel: [    2.575271] device-mapper: multipath: version 1.6.0 loaded
Jul 25 16:50:46 node-2 kernel: [    2.583113] systemd-udevd[216]: starting version 204
Jul 25 16:50:46 node-2 kernel: [    2.604768] md: linear personality registered for level -1
Jul 25 16:50:46 node-2 kernel: [    2.606504] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 25 16:50:46 node-2 kernel: [    2.625606] md: multipath personality registered for level -4
Jul 25 16:50:46 node-2 kernel: [    2.633748] md: raid0 personality registered for level 0
Jul 25 16:50:46 node-2 kernel: [    2.641452] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 25 16:50:46 node-2 kernel: [    2.647874] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 25 16:50:46 node-2 kernel: [    2.660033] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 25 16:50:46 node-2 kernel: [    2.660034] 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 25 16:50:46 node-2 kernel: [    2.660035] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 16:50:46 node-2 kernel: [    2.660393] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.660501] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.660617] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.660715] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.660874] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.677641] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 25 16:50:46 node-2 kernel: [    2.677653] 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 25 16:50:46 node-2 kernel: [    2.677654] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 16:50:46 node-2 kernel: [    2.677834] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.678003] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.678192] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.678306] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.678519] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.694364] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 25 16:50:46 node-2 kernel: [    2.694370] 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 25 16:50:46 node-2 kernel: [    2.694377] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 16:50:46 node-2 kernel: [    2.694583] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.694734] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.694874] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.695014] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.695221] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.712127] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 25 16:50:46 node-2 kernel: [    2.712128] 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 25 16:50:46 node-2 kernel: [    2.712129] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 25 16:50:46 node-2 kernel: [    2.712326] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.712376] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.712473] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.712608] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.712770] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.856737] md: raid1 personality registered for level 1
Jul 25 16:50:46 node-2 kernel: [    2.647783] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 25 16:50:46 node-2 kernel: [    2.857668] megasas: FW now in Ready state
Jul 25 16:50:46 node-2 kernel: [    2.857844] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.857883] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.857937] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858161] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858202] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858245] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858279] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858313] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858357] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858404] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858441] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858481] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858518] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858544] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858598] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858626] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 25 16:50:46 node-2 kernel: [    2.858812] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 25 16:50:46 node-2 kernel: [    2.884587] Switched to clocksource tsc
Jul 25 16:50:46 node-2 kernel: [    2.914227] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 25 16:50:46 node-2 kernel: [    2.921181] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 25 16:50:46 node-2 kernel: [    2.934623] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 25 16:50:46 node-2 kernel: [    2.941364] usb 2-1.4: Manufacturer: Avocent
Jul 25 16:50:46 node-2 kernel: [    2.947918] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 25 16:50:46 node-2 kernel: [    2.957352] hidraw: raw HID events driver (C) Jiri Kosina
Jul 25 16:50:46 node-2 kernel: [    2.963740] raid6: sse2x1   10952 MB/s
Jul 25 16:50:46 node-2 kernel: [    2.973304] usbcore: registered new interface driver usbhid
Jul 25 16:50:46 node-2 kernel: [    2.979759] usbhid: USB HID core driver
Jul 25 16:50:46 node-2 kernel: [    2.986952] 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 25 16:50:46 node-2 kernel: [    2.999752] 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 25 16:50:46 node-2 kernel: [    3.012662] 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 25 16:50:46 node-2 kernel: [    3.025999] 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 25 16:50:46 node-2 kernel: [    3.039412] raid6: sse2x2    3651 MB/s
Jul 25 16:50:46 node-2 kernel: [    3.040512] 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 25 16:50:46 node-2 kernel: [    3.041386] 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 25 16:50:46 node-2 kernel: [    3.137725] raid6: sse2x4   17172 MB/s
Jul 25 16:50:46 node-2 kernel: [    3.201673] megasas:IOC Init cmd success
Jul 25 16:50:46 node-2 kernel: [    3.209666] raid6: avx2x1   22808 MB/s
Jul 25 16:50:46 node-2 kernel: [    3.229654] megasas: INIT adapter done
Jul 25 16:50:46 node-2 kernel: [    3.281600] raid6: avx2x2   26265 MB/s
Jul 25 16:50:46 node-2 kernel: [    3.305585] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 25 16:50:46 node-2 kernel: [    3.312283] scsi0 : LSI SAS based MegaRAID driver
Jul 25 16:50:46 node-2 kernel: [    3.319478] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 25 16:50:46 node-2 kernel: [    3.337008] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 25 16:50:46 node-2 kernel: [    3.352597] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 25 16:50:46 node-2 kernel: [    3.353535] raid6: avx2x4   30462 MB/s
Jul 25 16:50:46 node-2 kernel: [    3.353536] raid6: using algorithm avx2x4 (30462 MB/s)
Jul 25 16:50:46 node-2 kernel: [    3.353536] raid6: using avx2x2 recovery algorithm
Jul 25 16:50:46 node-2 kernel: [    3.379275] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 25 16:50:46 node-2 kernel: [    3.392560] xor: automatically using best checksumming function:
Jul 25 16:50:46 node-2 kernel: [    3.392816] sd 0:2:0:0: [sda] Write Protect is off
Jul 25 16:50:46 node-2 kernel: [    3.392817] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 25 16:50:46 node-2 kernel: [    3.392893] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 25 16:50:46 node-2 kernel: [    3.423460]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 25 16:50:46 node-2 kernel: [    3.430268] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 25 16:50:46 node-2 kernel: [    3.457432]    avx       : 36730.000 MB/sec
Jul 25 16:50:46 node-2 kernel: [    3.464238] async_tx: api initialized (async)
Jul 25 16:50:46 node-2 kernel: [    3.473940] md: raid6 personality registered for level 6
Jul 25 16:50:46 node-2 kernel: [    3.479887] md: raid5 personality registered for level 5
Jul 25 16:50:46 node-2 kernel: [    3.485648] md: raid4 personality registered for level 4
Jul 25 16:50:46 node-2 kernel: [    3.494150] md: raid10 personality registered for level 10
Jul 25 16:50:46 node-2 kernel: [    3.540997] multipathd (362): /proc/362/oom_adj is deprecated, please use /proc/362/oom_score_adj instead.
Jul 25 16:50:46 node-2 kernel: [    3.562646] random: lvm urandom read with 29 bits of entropy available
Jul 25 16:50:46 node-2 kernel: [    3.687310] bio: create slab <bio-1> at 1
Jul 25 16:50:46 node-2 kernel: [    4.454990] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 16:50:46 node-2 kernel: [    5.138135] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 25 16:50:46 node-2 kernel: [    5.160187] random: nonblocking pool is initialized
Jul 25 16:50:46 node-2 kernel: [    5.187709] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 25 16:50:46 node-2 kernel: [    5.279942] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 25 16:50:46 node-2 kernel: [    5.357734] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 25 16:50:46 node-2 kernel: [    5.457802] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 16:50:46 node-2 kernel: [    5.665530] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 25 16:50:46 node-2 kernel: [    5.706760] XFS (dm-0): Mounting Filesystem
Jul 25 16:50:46 node-2 kernel: [    6.022961] XFS (dm-0): Ending clean mount
Jul 25 16:50:46 node-2 kernel: [    6.096184] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 25 16:50:46 node-2 kernel: [    6.134541] XFS (dm-1): Mounting Filesystem
Jul 25 16:50:46 node-2 kernel: [    6.219150] XFS (dm-1): Ending clean mount
Jul 25 16:50:46 node-2 kernel: [    7.875640] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 25 16:50:46 node-2 kernel: [    7.889178] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 25 16:50:46 node-2 kernel: [    8.046176] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 25 16:50:46 node-2 kernel: [    8.046181] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 25 16:50:46 node-2 kernel: [    8.046186] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 25 16:50:46 node-2 kernel: [    8.046190] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 25 16:50:46 node-2 kernel: [    8.064726] systemd-udevd[775]: starting version 204
Jul 25 16:50:46 node-2 kernel: [    8.236274] wmi: Mapper loaded
Jul 25 16:50:46 node-2 kernel: [    8.256009] IPMI System Interface driver.
Jul 25 16:50:46 node-2 kernel: [    8.256046] ipmi_si: probing via ACPI
Jul 25 16:50:46 node-2 kernel: [    8.256064] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 25 16:50:46 node-2 kernel: [    8.256065] ipmi_si: Adding ACPI-specified kcs state machine
Jul 25 16:50:46 node-2 kernel: [    8.256073] ipmi_si: probing via SMBIOS
Jul 25 16:50:46 node-2 kernel: [    8.256074] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 25 16:50:46 node-2 kernel: [    8.256075] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 25 16:50:46 node-2 kernel: [    8.256076] ipmi_si: probing via SPMI
Jul 25 16:50:46 node-2 kernel: [    8.256077] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 25 16:50:46 node-2 kernel: [    8.256078] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 25 16:50:46 node-2 kernel: [    8.256079] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 25 16:50:46 node-2 kernel: [    8.257966] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 25 16:50:46 node-2 kernel: [    8.257970] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 25 16:50:46 node-2 kernel: [    8.257973] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 25 16:50:46 node-2 kernel: [    8.257974] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 25 16:50:46 node-2 kernel: [    8.257987] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 25 16:50:46 node-2 kernel: [    8.266027] power_meter ACPI000D:00: Found ACPI power meter.
Jul 25 16:50:46 node-2 kernel: [    8.266034] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 25 16:50:46 node-2 kernel: [    8.274224] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 25 16:50:46 node-2 kernel: [    8.321726] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 25 16:50:46 node-2 kernel: [    8.321730] ipmi_si 00:09: IPMI kcs interface initialized
Jul 25 16:50:46 node-2 kernel: [    8.333799] systemd-udevd[804]: renamed network interface eth1 to enp7s0
Jul 25 16:50:46 node-2 kernel: [    8.357739] systemd-udevd[794]: renamed network interface eth0 to enp6s0
Jul 25 16:50:46 node-2 kernel: [    8.393753] systemd-udevd[797]: renamed network interface eth2 to enp8s0
Jul 25 16:50:46 node-2 kernel: [    8.421963] systemd-udevd[807]: renamed network interface eth3 to enp9s0
Jul 25 16:50:46 node-2 kernel: [    8.745041] type=1400 audit(1469465419.757:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1062 comm="apparmor_parser"
Jul 25 16:50:46 node-2 kernel: [    8.745204] type=1400 audit(1469465419.757:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1062 comm="apparmor_parser"
Jul 25 16:50:46 node-2 kernel: [    8.745333] type=1400 audit(1469465419.757:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1062 comm="apparmor_parser"
Jul 25 16:50:46 node-2 kernel: [    8.746386] type=1400 audit(1469465419.757:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Jul 25 16:50:46 node-2 kernel: [    8.746533] type=1400 audit(1469465419.757:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1060 comm="apparmor_parser"
Jul 25 16:50:46 node-2 kernel: [    8.746659] type=1400 audit(1469465419.757:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1060 comm="apparmor_parser"
Jul 25 16:50:46 node-2 kernel: [    8.777803] type=1400 audit(1469465419.789:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1063 comm="apparmor_parser"
Jul 25 16:50:46 node-2 kernel: [    8.777950] type=1400 audit(1469465419.789:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1063 comm="apparmor_parser"
Jul 25 16:50:46 node-2 kernel: [    8.778075] type=1400 audit(1469465419.789:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1063 comm="apparmor_parser"
Jul 25 16:50:46 node-2 kernel: [    8.778634] type=1400 audit(1469465419.789:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1064 comm="apparmor_parser"
Jul 25 16:50:46 node-2 kernel: [    9.285323] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 25 16:50:46 node-2 kernel: [    9.285961] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 25 16:50:46 node-2 kernel: [    9.470190] enic 0000:06:00.0 enp6s0: Link UP
Jul 25 16:50:46 node-2 kernel: [    9.471508] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 25 16:50:46 node-2 kernel: [    9.471517] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 25 16:50:46 node-2 kernel: [   18.446887] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 25 16:50:46 node-2 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 25 16:50:47 node-2 failsafe: Failsafe of 120 seconds reached.
Jul 25 16:50:47 node-2 kernel: [   37.049811] init: failsafe main process (8399) killed by TERM signal
Jul 25 16:50:47 node-2 dbus[8427]: [system] AppArmor D-Bus mediation is enabled
Jul 25 16:50:48 node-2 kernel: [   37.279242] audit_printk_skb: 30 callbacks suppressed
Jul 25 16:50:48 node-2 kernel: [   37.279244] type=1400 audit(1469465448.086:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8527 comm="apparmor_parser"
Jul 25 16:50:48 node-2 kernel: [   37.279517] type=1400 audit(1469465448.086:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8526 comm="apparmor_parser"
Jul 25 16:50:48 node-2 kernel: [   37.279521] type=1400 audit(1469465448.086:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8526 comm="apparmor_parser"
Jul 25 16:50:48 node-2 kernel: [   37.279524] type=1400 audit(1469465448.086:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8526 comm="apparmor_parser"
Jul 25 16:50:48 node-2 kernel: [   37.279758] type=1400 audit(1469465448.086:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8526 comm="apparmor_parser"
Jul 25 16:50:48 node-2 kernel: [   37.279759] type=1400 audit(1469465448.086:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8526 comm="apparmor_parser"
Jul 25 16:50:48 node-2 kernel: [   37.279872] type=1400 audit(1469465448.086:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8526 comm="apparmor_parser"
Jul 25 16:50:48 node-2 kernel: [   37.349173] type=1400 audit(1469465448.158:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8529 comm="apparmor_parser"
Jul 25 16:50:48 node-2 anacron[8592]: Anacron 2.3 started on 2016-07-25
Jul 25 16:50:48 node-2 cron[8557]: (CRON) INFO (pidfile fd = 3)
Jul 25 16:50:48 node-2 cron[8599]: (CRON) STARTUP (fork ok)
Jul 25 16:50:48 node-2 anacron[8592]: Will run job `cron.daily' in 5 min.
Jul 25 16:50:48 node-2 anacron[8592]: Will run job `cron.weekly' in 10 min.
Jul 25 16:50:48 node-2 anacron[8592]: Will run job `cron.monthly' in 15 min.
Jul 25 16:50:48 node-2 anacron[8592]: Jobs will be executed sequentially
Jul 25 16:50:48 node-2 cron[8599]: (CRON) INFO (Running @reboot jobs)
Jul 25 16:50:48 node-2 multipathd: path checkers start up
Jul 25 16:50:48 node-2 postfix/master[8736]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 25 16:50:52 node-2 puppet-agent[8920]: Reopening log files
Jul 25 16:50:52 node-2 puppet-agent[8920]: Could not request certificate: Connection refused - connect(2)
Jul 25 16:51:01 node-2 CRON[8951]: (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 25 16:51:08 node-2 puppet-user[9010]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 25 16:51:08 node-2 puppet-user[9010]: Compiled catalog for node-2.domain.tld in environment production in 0.03 seconds
Jul 25 16:51:09 node-2 puppet-user[9010]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 25 16:51:09 node-2 puppet-user[9010]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 25 16:51:09 node-2 puppet-user[9010]: Finished catalog run in 0.49 seconds
Jul 25 16:51:10 node-2 multipathd: uevent trigger error
Jul 25 16:51:10 node-2 puppet-user[9545]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 25 16:51:10 node-2 puppet-user[9545]: Compiled catalog for node-2.domain.tld in environment production in 0.08 seconds
Jul 25 16:51:10 node-2 puppet-user[9545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 25 16:51:10 node-2 puppet-user[9545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 25 16:51:10 node-2 puppet-user[9545]: (/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 25 16:51:10 node-2 puppet-user[9545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 25 16:51:10 node-2 puppet-user[9545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 25 16:51:10 node-2 puppet-user[9545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 25 16:51:10 node-2 puppet-user[9545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 25 16:51:10 node-2 puppet-user[9545]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 25 16:51:10 node-2 puppet-user[9545]: Finished catalog run in 0.06 seconds
Jul 25 16:51:12 node-2 puppet-user[10020]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 25 16:51:12 node-2 puppet-user[10020]: Compiled catalog for node-2.domain.tld in environment production in 0.07 seconds
Jul 25 16:51:12 node-2 puppet-user[10020]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 25 16:51:12 node-2 puppet-user[10020]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 25 16:51:12 node-2 puppet-user[10020]: Finished catalog run in 0.03 seconds
Jul 25 16:51:13 node-2 puppet-user[10474]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 25 16:51:13 node-2 puppet-user[10474]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 25 16:51:14 node-2 puppet-user[10474]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 25 16:51:14 node-2 puppet-user[10474]: Finished catalog run in 0.03 seconds
Jul 25 16:51:15 node-2 puppet-user[10917]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 25 16:51:15 node-2 puppet-user[10917]: Compiled catalog for node-2.domain.tld in environment production in 0.17 seconds
Jul 25 16:51:15 node-2 puppet-user[10917]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 25 16:51:15 node-2 puppet-user[10917]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 25 16:51:16 node-2 puppet-user[10917]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 25 16:51:16 node-2 puppet-user[10917]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Jul 25 16:51:16 node-2 puppet-user[10917]: Finished catalog run in 1.18 seconds
Jul 25 16:51:17 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 16:51:17 node-2 nailgun-agent: D, [2016-07-25T16:51:01.536544 #8954] DEBUG -- : Sleep for 16 seconds before sending request
Jul 25 16:51:17 node-2 nailgun-agent: I, [2016-07-25T16:51:17.550936 #8954]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 25 16:51:17 node-2 nailgun-agent: D, [2016-07-25T16:51:17.942276 #8954] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 25 16:51:17 node-2 puppet-user[11442]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 25 16:51:18 node-2 puppet-user[11442]: Compiled catalog for node-2.domain.tld in environment production in 0.24 seconds
Jul 25 16:51:18 node-2 puppet-user[11442]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 25 16:51:18 node-2 puppet-user[11442]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Jul 25 16:51:18 node-2 puppet-user[11442]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 25 16:51:18 node-2 puppet-user[11442]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 25 16:51:18 node-2 puppet-user[11442]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 25 16:51:18 node-2 puppet-user[11442]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 25 16:51:18 node-2 puppet-user[11442]: Finished catalog run in 0.36 seconds
Jul 25 16:51:20 node-2 puppet-user[12049]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 25 16:51:20 node-2 puppet-user[12049]: Compiled catalog for node-2.domain.tld in environment production in 0.18 seconds
Jul 25 16:51:20 node-2 puppet-user[12049]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 25 16:51:20 node-2 kernel: [   69.725956] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 25 16:51:20 node-2 kernel: [   69.726008] 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 25 16:51:20 node-2 puppet-user[12049]: (/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 25 16:51:20 node-2 puppet-user[12049]: Finished catalog run in 0.06 seconds
Jul 25 16:51:22 node-2 puppet-user[12514]: (Scope(Class[main])) MODULAR: sync_time
Jul 25 16:51:22 node-2 puppet-user[12514]: Compiled catalog for node-2.domain.tld in environment production in 0.02 seconds
Jul 25 16:51:22 node-2 ntpdate[13110]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 25 16:51:28 node-2 ntpdate[13110]: adjust time server 10.20.0.2 offset 0.001685 sec
Jul 25 16:51:28 node-2 puppet-user[12514]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 25 16:51:28 node-2 puppet-user[12514]: Finished catalog run in 6.17 seconds
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.830841 #8954] DEBUG -- : Trying to find block devices
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.830931 #8954] DEBUG -- : Found block device: sda
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.830992 #8954] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.831015 #8954] DEBUG -- : Trying to get list of physical devices
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.831200 #8954] DEBUG -- : Getting udev properties for device: sda
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.832918 #8954] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc7880
Jul 25 16:51:29 node-2 nailgun-agent: a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"88636", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.832944 #8954] DEBUG -- : Trying to find out if device sda is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.832988 #8954] DEBUG -- : Device sda removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.833031 #8954] DEBUG -- : Device sda seems to be appropriate
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.833407 #8954] DEBUG -- : Getting udev properties for device: dm-0
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.834956 #8954] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-8EQfLCHP9TdCkycbKBxgUQwydDMo481kT40UNuobwvxqNA5BuNgfwGKbsFukMsV9 /dev/disk/by-uuid/379b937b-e061-4d4c-918b-313e8b20bc7b /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-8EQfLCHP9TdCkycbKBxgUQwydDMo481kT40UNuobwvxqNA5BuNgfwGKbsFukMsV9", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"379b937b-e061-4d4c-918b-313e8b20bc7b", "ID_FS_UUID_ENC"=>"379b937b-e061-4d4c-918b-313e8b20bc7b", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45993", "nomdmonddf"=>"1", "nomd
Jul 25 16:51:29 node-2 nailgun-agent: monisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.834993 #8954] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.835023 #8954] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.835037 #8954] DEBUG -- : Device dm-0 seems to be appropriate
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.835050 #8954] DEBUG -- : Getting udev properties for device: dm-1
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.836600 #8954] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-C1EKddf5yBK13Q0Lh75G2fgpLl5bx2PMD5FErRWZngEhgovZX1XrKtskoBJcYBWf /dev/disk/by-uuid/ec0e40a5-6524-462f-b4a3-df9621652519 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-C1EKddf5yBK13Q0Lh75G2fgpLl5bx2PMD5FErRWZngEhgovZX1XrKtskoBJcYBWf", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ec0e40a5-6524-462f-b4a3-df9621652519", "ID_FS_UUID_ENC"=>"ec0e40a5-6524-462f-b4a3-df9621652519", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"68
Jul 25 16:51:29 node-2 nailgun-agent: 524", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.836626 #8954] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.836657 #8954] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.836682 #8954] DEBUG -- : Device dm-1 seems to be appropriate
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.836696 #8954] DEBUG -- : Getting udev properties for device: dm-2
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.838225 #8954] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-bpxf5ey3ZjLLWLk48dhPaUki2oGC4XPjF1Mi3pMTpWCGnFDxB97ame4bvTKDaksS /dev/disk/by-uuid/6a229231-53bf-4d2d-98b3-5439bb9d703c /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-bpxf5ey3ZjLLWLk48dhPaUki2oGC4XPjF1Mi3pMTpWCGnFDxB97ame4bvTKDaksS", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"6a229231-53bf-4d2d-98b3-5439bb9d703c", "ID_FS_UUID_ENC"=>"6a229231-53bf-4d2d-98b3-5439bb9d703c", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"74945", "nomdmond
Jul 25 16:51:29 node-2 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.838252 #8954] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.838293 #8954] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.838307 #8954] DEBUG -- : Device dm-2 seems to be appropriate
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.838321 #8954] DEBUG -- : Getting udev properties for device: dm-3
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.839817 #8954] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-gTXPnhyDteARUeGSi3Xd4zkoALnVWt9ckBNd1REqOXtcovIZyrE6XfIF6IYGSYur /dev/disk/by-uuid/a199d0d4-96cb-4eff-bbbc-057eabc159d0 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-gTXPnhyDteARUeGSi3Xd4zkoALnVWt9ckBNd1REqOXtcovIZyrE6XfIF6IYGSYur", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a199d0d4-96cb-4eff-bbbc-057eabc159d0", "ID_FS_UUID_ENC"=>"a199d0d4-96cb-4eff-bbbc-057eabc159d0", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84536", "nomdmonddf"=>"1", 
Jul 25 16:51:29 node-2 nailgun-agent: "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.839877 #8954] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.839906 #8954] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.839920 #8954] DEBUG -- : Device dm-3 seems to be appropriate
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.839934 #8954] DEBUG -- : Getting udev properties for device: dm-4
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.841505 #8954] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-5sQwTzwQl9OsLYtZ9N1RnBeHXk3WzxaGn3eNpddLhA6EtGfXDOoP7K1Jh5jeDeWw /dev/disk/by-uuid/1681dc78-cc21-4aa3-9b24-23d745c98720 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-5sQwTzwQl9OsLYtZ9N1RnBeHXk3WzxaGn3eNpddLhA6EtGfXDOoP7K1Jh5jeDeWw", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"1681dc78-cc21-4aa3-9b24-23d745c98720", "ID_FS_UUID_ENC"=>"1681dc78-cc21-4aa3-9b24-23d745c98720", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"89882", "nomdmonddf"=>"1", "nomd
Jul 25 16:51:29 node-2 nailgun-agent: monisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.841541 #8954] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.841571 #8954] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.841585 #8954] DEBUG -- : Device dm-4 seems to be appropriate
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.841599 #8954] DEBUG -- : Getting udev properties for device: dm-5
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.843128 #8954] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-5sQwTzwQl9OsLYtZ9N1RnBeHXk3WzxaG48JZUZVGeb8ZlZdHgwJ91N2RYg6Ff3G8 /dev/disk/by-uuid/8d701280-b072-447e-8a64-8c819c32eac5 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-5sQwTzwQl9OsLYtZ9N1RnBeHXk3WzxaG48JZUZVGeb8ZlZdHgwJ91N2RYg6Ff3G8", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"8d701280-b072-447e-8a64-8c819c32eac5", "ID_FS_UUID_ENC"=>"8d701280-b072-447e-8a64-8c819c32eac5", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90454", "nomdmonddf"=>"1", "nomdmonisw"
Jul 25 16:51:29 node-2 nailgun-agent: =>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.843156 #8954] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.843198 #8954] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.843211 #8954] DEBUG -- : Device dm-5 seems to be appropriate
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.843225 #8954] DEBUG -- : Getting udev properties for device: ram0
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.844677 #8954] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60095", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.844724 #8954] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.844770 #8954] DEBUG -- : Device ram0 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.844789 #8954] DEBUG -- : Getting udev properties for device: ram1
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.846187 #8954] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60107", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.846211 #8954] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.846250 #8954] DEBUG -- : Device ram1 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.846269 #8954] DEBUG -- : Getting udev properties for device: ram2
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.847648 #8954] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60200", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.847672 #8954] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.847709 #8954] DEBUG -- : Device ram2 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.847727 #8954] DEBUG -- : Getting udev properties for device: ram3
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.849093 #8954] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60214", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.849118 #8954] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.849154 #8954] DEBUG -- : Device ram3 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.849190 #8954] DEBUG -- : Getting udev properties for device: ram4
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.850534 #8954] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60229", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.850578 #8954] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.850612 #8954] DEBUG -- : Device ram4 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.850632 #8954] DEBUG -- : Getting udev properties for device: ram5
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.852018 #8954] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60244", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.852042 #8954] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.852076 #8954] DEBUG -- : Device ram5 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.852123 #8954] DEBUG -- : Getting udev properties for device: ram6
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.853465 #8954] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60262", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.853489 #8954] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.853522 #8954] DEBUG -- : Device ram6 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.853541 #8954] DEBUG -- : Getting udev properties for device: ram7
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.854916 #8954] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60277", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.854941 #8954] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.854975 #8954] DEBUG -- : Device ram7 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.855005 #8954] DEBUG -- : Getting udev properties for device: ram8
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.856362 #8954] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60291", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.856387 #8954] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.856429 #8954] DEBUG -- : Device ram8 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.856449 #8954] DEBUG -- : Getting udev properties for device: ram9
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.857835 #8954] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60304", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.857860 #8954] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.857909 #8954] DEBUG -- : Device ram9 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.857927 #8954] DEBUG -- : Getting udev properties for device: loop0
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.859328 #8954] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59992", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.859352 #8954] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.859393 #8954] DEBUG -- : Device loop0 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.859424 #8954] DEBUG -- : Getting udev properties for device: loop1
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.860995 #8954] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60010", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.861035 #8954] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.861071 #8954] DEBUG -- : Device loop1 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.861092 #8954] DEBUG -- : Getting udev properties for device: loop2
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.862504 #8954] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60027", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.862543 #8954] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.862575 #8954] DEBUG -- : Device loop2 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.862603 #8954] DEBUG -- : Getting udev properties for device: loop3
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.864034 #8954] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60038", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.864060 #8954] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.864139 #8954] DEBUG -- : Device loop3 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.864159 #8954] DEBUG -- : Getting udev properties for device: loop4
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.865583 #8954] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60051", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.865619 #8954] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.865651 #8954] DEBUG -- : Device loop4 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.865681 #8954] DEBUG -- : Getting udev properties for device: loop5
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.867088 #8954] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60061", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.867113 #8954] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.867146 #8954] DEBUG -- : Device loop5 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.867165 #8954] DEBUG -- : Getting udev properties for device: loop6
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.868556 #8954] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60073", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.868581 #8954] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.868614 #8954] DEBUG -- : Device loop6 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.868645 #8954] DEBUG -- : Getting udev properties for device: loop7
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.870025 #8954] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60084", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.870049 #8954] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.870099 #8954] DEBUG -- : Device loop7 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.870118 #8954] DEBUG -- : Getting udev properties for device: ram10
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.876686 #8954] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60118", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.876717 #8954] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.876757 #8954] DEBUG -- : Device ram10 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.876775 #8954] DEBUG -- : Getting udev properties for device: ram11
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.878366 #8954] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60130", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.878391 #8954] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.878434 #8954] DEBUG -- : Device ram11 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.878453 #8954] DEBUG -- : Getting udev properties for device: ram12
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.879832 #8954] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60147", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.879892 #8954] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.879932 #8954] DEBUG -- : Device ram12 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.879950 #8954] DEBUG -- : Getting udev properties for device: ram13
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.881317 #8954] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60160", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.881344 #8954] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.881413 #8954] DEBUG -- : Device ram13 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.881432 #8954] DEBUG -- : Getting udev properties for device: ram14
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.882797 #8954] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60173", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.882823 #8954] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.882855 #8954] DEBUG -- : Device ram14 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.882922 #8954] DEBUG -- : Getting udev properties for device: ram15
Jul 25 16:51:29 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884268 #8954] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60186", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884293 #8954] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884324 #8954] DEBUG -- : Device ram15 removable parameter: "0"
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884359 #8954] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884422 #8954] DEBUG -- : Block device seems to be physical data storage: sda
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884461 #8954] DEBUG -- : Found block device: dm-0
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884487 #8954] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884500 #8954] DEBUG -- : Found block device: dm-1
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884510 #8954] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884518 #8954] DEBUG -- : Found block device: dm-2
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884528 #8954] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884536 #8954] DEBUG -- : Found block device: dm-3
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884589 #8954] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884598 #8954] DEBUG -- : Found block device: dm-4
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884608 #8954] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884616 #8954] DEBUG -- : Found block device: dm-5
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884627 #8954] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884635 #8954] DEBUG -- : Found block device: ram0
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884644 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884652 #8954] DEBUG -- : Found block device: ram1
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884700 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884710 #8954] DEBUG -- : Found block device: ram2
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884718 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884727 #8954] DEBUG -- : Found block device: ram3
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884736 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884744 #8954] DEBUG -- : Found block device: ram4
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884753 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884761 #8954] DEBUG -- : Found block device: ram5
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884770 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884815 #8954] DEBUG -- : Found block device: ram6
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884825 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884834 #8954] DEBUG -- : Found block device: ram7
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884843 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884851 #8954] DEBUG -- : Found block device: ram8
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884860 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884867 #8954] DEBUG -- : Found block device: ram9
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884876 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884884 #8954] DEBUG -- : Found block device: loop0
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884929 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884939 #8954] DEBUG -- : Found block device: loop1
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884949 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884957 #8954] DEBUG -- : Found block device: loop2
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884967 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884975 #8954] DEBUG -- : Found block device: loop3
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884984 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.884992 #8954] DEBUG -- : Found block device: loop4
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885002 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885041 #8954] DEBUG -- : Found block device: loop5
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885050 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885058 #8954] DEBUG -- : Found block device: loop6
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885067 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885075 #8954] DEBUG -- : Found block device: loop7
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885084 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885091 #8954] DEBUG -- : Found block device: ram10
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885100 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885109 #8954] DEBUG -- : Found block device: ram11
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885151 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885161 #8954] DEBUG -- : Found block device: ram12
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885172 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885181 #8954] DEBUG -- : Found block device: ram13
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885189 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885197 #8954] DEBUG -- : Found block device: ram14
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885205 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885213 #8954] DEBUG -- : Found block device: ram15
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885222 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.885282 #8954] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.961637 #8954] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 25 16:51:29 node-2 nailgun-agent: D, [2016-07-25T16:51:29.961682 #8954] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 25 16:51:33 node-2 kernel: [   82.935801] init: plymouth-upstart-bridge main process ended, respawning
Jul 25 16:51:33 node-2 puppet-agent[8920]: Could not run: SIGTERM
Jul 25 16:51:34 node-2 kernel: [   83.186983] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 25 16:51:34 node-2 ec2: 
Jul 25 16:51:34 node-2 ec2: #############################################################
Jul 25 16:51:34 node-2 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 25 16:51:34 node-2 ec2: 1024 58:40:81:ad:9c:13:f6:b1:0f:ea:e5:30:e3:f8:54:71  root@node-2.domain.tld (DSA)
Jul 25 16:51:34 node-2 ec2: 256 9a:0a:67:8c:0f:ec:ce:4f:93:eb:16:cf:6a:84:fd:aa  root@node-2.domain.tld (ECDSA)
Jul 25 16:51:34 node-2 ec2: 256 44:87:c5:ae:dc:1a:8e:6e:67:ed:31:6d:fe:1f:65:0c  root@node-2.domain.tld (ED25519)
Jul 25 16:51:34 node-2 ec2: 2048 2b:e9:0d:b1:0e:84:37:97:27:09:b7:26:02:5e:f6:ae  root@node-2.domain.tld (RSA)
Jul 25 16:51:34 node-2 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 25 16:51:34 node-2 ec2: #############################################################
Jul 25 16:51:42 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303264 #8954] DEBUG -- : Trying to find block devices
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303451 #8954] DEBUG -- : Found block device: sda
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303479 #8954] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303499 #8954] DEBUG -- : Block device seems to be physical data storage: sda
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303521 #8954] DEBUG -- : Found block device: dm-0
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303533 #8954] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303544 #8954] DEBUG -- : Found block device: dm-1
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303554 #8954] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303563 #8954] DEBUG -- : Found block device: dm-2
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303572 #8954] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303581 #8954] DEBUG -- : Found block device: dm-3
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303618 #8954] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303627 #8954] DEBUG -- : Found block device: dm-4
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303637 #8954] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303645 #8954] DEBUG -- : Found block device: dm-5
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303654 #8954] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303662 #8954] DEBUG -- : Found block device: ram0
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303671 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303680 #8954] DEBUG -- : Found block device: ram1
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303690 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303698 #8954] DEBUG -- : Found block device: ram2
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303707 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303750 #8954] DEBUG -- : Found block device: ram3
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303760 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303768 #8954] DEBUG -- : Found block device: ram4
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303777 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303786 #8954] DEBUG -- : Found block device: ram5
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303796 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303804 #8954] DEBUG -- : Found block device: ram6
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303813 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303821 #8954] DEBUG -- : Found block device: ram7
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303831 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303839 #8954] DEBUG -- : Found block device: ram8
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303882 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303891 #8954] DEBUG -- : Found block device: ram9
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303901 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303909 #8954] DEBUG -- : Found block device: loop0
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303918 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303927 #8954] DEBUG -- : Found block device: loop1
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303936 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303944 #8954] DEBUG -- : Found block device: loop2
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303953 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.303962 #8954] DEBUG -- : Found block device: loop3
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304001 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304010 #8954] DEBUG -- : Found block device: loop4
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304019 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304027 #8954] DEBUG -- : Found block device: loop5
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304036 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304044 #8954] DEBUG -- : Found block device: loop6
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304053 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304062 #8954] DEBUG -- : Found block device: loop7
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304071 #8954] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304079 #8954] DEBUG -- : Found block device: ram10
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304087 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304131 #8954] DEBUG -- : Found block device: ram11
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304140 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304149 #8954] DEBUG -- : Found block device: ram12
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304159 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304167 #8954] DEBUG -- : Found block device: ram13
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304176 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304185 #8954] DEBUG -- : Found block device: ram14
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304194 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304202 #8954] DEBUG -- : Found block device: ram15
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304211 #8954] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.304285 #8954] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 25 16:51:42 node-2 nailgun-agent: D, [2016-07-25T16:51:42.477635 #8954] DEBUG -- : Response: status: 200 body: {"id": 2}
Jul 25 16:51:42 node-2 nailgun-agent: I, [2016-07-25T16:51:42.477797 #8954]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 25 16:52:01 node-2 CRON[13756]: (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 25 16:52:03 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 16:52:03 node-2 nailgun-agent: I, [2016-07-25T16:52:03.662600 #13759]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 25 16:52:16 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 16:52:16 node-2 nailgun-agent: I, [2016-07-25T16:52:16.722097 #13759]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 2
Jul 25 16:52:17 node-2 puppet-user[13925]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 25 16:52:17 node-2 puppet-user[13925]: Compiled catalog for node-2.domain.tld in environment production in 0.10 seconds
Jul 25 16:52:17 node-2 puppet-user[13925]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 25 16:52:17 node-2 puppet-user[13925]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 25 16:52:17 node-2 puppet-user[13925]: Finished catalog run in 0.07 seconds
Jul 25 16:52:19 node-2 puppet-user[14537]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 25 16:52:21 node-2 puppet-user[14537]: Compiled catalog for node-2.domain.tld in environment production in 1.50 seconds
Jul 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:21 node-2 puppet-user[14537]: (/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 25 16:52:31 node-2 puppet-user[14537]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 25 16:52:31 node-2 puppet-user[14537]: Finished catalog run in 10.11 seconds
Jul 25 16:52:33 node-2 puppet-user[15279]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 25 16:52:33 node-2 puppet-user[15279]: Compiled catalog for node-2.domain.tld in environment production in 0.13 seconds
Jul 25 16:52:38 node-2 puppet-user[15279]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 25 16:53:01 node-2 CRON[17018]: (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 25 16:53:06 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 16:53:06 node-2 nailgun-agent: I, [2016-07-25T16:53:06.918014 #17021]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 25 16:53:10 node-2 puppet-user[15279]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 25 16:53:10 node-2 puppet-user[15279]: Finished catalog run in 36.24 seconds
Jul 25 16:53:12 node-2 puppet-user[17917]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 25 16:53:12 node-2 puppet-user[17917]: Compiled catalog for node-2.domain.tld in environment production in 0.54 seconds
Jul 25 16:53:12 node-2 puppet-user[17917]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 25 16:53:12 node-2 puppet-user[17917]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 25 16:53:12 node-2 puppet-user[17917]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 25 16:53:12 node-2 puppet-user[17917]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 25 16:53:12 node-2 puppet-user[17917]: Finished catalog run in 0.10 seconds
Jul 25 16:53:14 node-2 puppet-user[18371]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 25 16:53:15 node-2 puppet-user[18371]: Compiled catalog for node-2.domain.tld in environment production in 0.82 seconds
Jul 25 16:53:15 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 25 16:53:15 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 25 16:53:15 node-2 crontab[18807]: (root) LIST (root)
Jul 25 16:53:15 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 25 16:53:15 node-2 crontab[18808]: (root) REPLACE (root)
Jul 25 16:53:17 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/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 25 16:53:19 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 25 16:53:20 node-2 puppet-user[18371]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 25 16:53:20 node-2 puppet-user[18371]: (/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 25 16:53:20 node-2 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8372" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 25 16:53:20 node-2 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 25 16:53:21 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:21 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:21 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:21 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:21 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:40 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:40 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:40 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:40 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:43 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:43 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:43 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:43 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:43 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:45 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:45 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:45 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:45 node-2 multipathd: uevent trigger error
<27>Jul 25 16:53:45 node-2 multipathd: uevent trigger error
<27>Jul 25 16:54:45 node-2 ntpdate[29408]: no servers can be used, exiting
<27>Jul 25 16:55:16 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:16 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:16 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:16 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:19 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:19 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:19 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:19 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:34 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:34 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:34 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:34 node-2 multipathd: uevent trigger error
<27>Jul 25 16:55:34 node-2 multipathd: uevent trigger error
<27>Jul 25 16:56:35 node-2 multipathd: uevent trigger error
<27>Jul 25 16:56:35 node-2 multipathd: uevent trigger error
<27>Jul 25 16:56:35 node-2 multipathd: uevent trigger error
<27>Jul 25 16:56:35 node-2 multipathd: uevent trigger error
<27>Jul 25 16:56:43 node-2 multipathd: uevent trigger error
<27>Jul 25 16:56:43 node-2 multipathd: uevent trigger error
<27>Jul 25 16:56:43 node-2 multipathd: uevent trigger error
<27>Jul 25 16:56:43 node-2 multipathd: uevent trigger error
<27>Jul 25 16:56:46 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 16:56:46 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 16:56:52 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 16:56:52 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 16:56:57 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 16:57:03 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 16:57:03 node-2 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 25 16:57:10 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:10 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:10 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:10 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:10 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:23 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:23 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:23 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:23 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:56 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:56 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:56 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:56 node-2 multipathd: uevent trigger error
<27>Jul 25 16:57:56 node-2 multipathd: uevent trigger error
<129>Jul 25 16:57:59 node-2 haproxy[22195]: Server odl-neutron-endpoint/node-2 is DOWN, reason: Layer4 connection 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 25 16:57:59 node-2 haproxy[22195]: proxy odl-neutron-endpoint has no server available!
<129>Jul 25 16:58:00 node-2 haproxy[22202]: Server odl-jetty/node-2 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 56ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 25 16:58:00 node-2 haproxy[22202]: proxy odl-jetty has no server available!
<27>Jul 25 16:58:22 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:22 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:22 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:22 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:22 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:22 node-2 multipathd: uevent trigger error
<129>Jul 25 16:58:24 node-2 haproxy[24855]: 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 25 16:58:25 node-2 haproxy[24864]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:25 node-2 haproxy[24864]: 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 25 16:58:25 node-2 haproxy[24864]: proxy mysqld has no server available!
<27>Jul 25 16:58:28 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:28 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:28 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:28 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:28 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:28 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:31 node-2 multipathd: uevent trigger error
<129>Jul 25 16:58:33 node-2 haproxy[27266]: 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 25 16:58:34 node-2 haproxy[27270]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:34 node-2 haproxy[27270]: 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 25 16:58:34 node-2 haproxy[27270]: proxy mysqld has no server available!
<129>Jul 25 16:58:34 node-2 haproxy[27270]: 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 25 16:58:34 node-2 haproxy[27270]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:35 node-2 haproxy[27270]: 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 25 16:58:35 node-2 haproxy[27270]: proxy object-storage has no server available!
<27>Jul 25 16:58:36 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:36 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:36 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:36 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:36 node-2 multipathd: uevent trigger error
<129>Jul 25 16:58:39 node-2 haproxy[28708]: 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 25 16:58:39 node-2 haproxy[28708]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:39 node-2 haproxy[28708]: 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 25 16:58:39 node-2 haproxy[28708]: proxy neutron has no server available!
<129>Jul 25 16:58:39 node-2 haproxy[28708]: 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 25 16:58:39 node-2 haproxy[28708]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:39 node-2 haproxy[28708]: 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 25 16:58:39 node-2 haproxy[28708]: proxy mysqld has no server available!
<129>Jul 25 16:58:40 node-2 haproxy[28712]: 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 25 16:58:40 node-2 haproxy[28712]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:40 node-2 haproxy[28712]: 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 25 16:58:40 node-2 haproxy[28712]: proxy object-storage has no server available!
<27>Jul 25 16:58:41 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:41 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:41 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:41 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:41 node-2 multipathd: uevent trigger error
<129>Jul 25 16:58:44 node-2 haproxy[30009]: 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 25 16:58:44 node-2 haproxy[30009]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:44 node-2 haproxy[30009]: 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 25 16:58:44 node-2 haproxy[30009]: proxy keystone-1 has no server available!
<129>Jul 25 16:58:44 node-2 haproxy[30009]: 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 25 16:58:45 node-2 haproxy[30018]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:45 node-2 haproxy[30018]: 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 25 16:58:45 node-2 haproxy[30018]: proxy keystone-2 has no server available!
<129>Jul 25 16:58:45 node-2 haproxy[30018]: 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 25 16:58:45 node-2 haproxy[30018]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:45 node-2 haproxy[30018]: 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 25 16:58:45 node-2 haproxy[30018]: proxy neutron has no server available!
<129>Jul 25 16:58:45 node-2 haproxy[30018]: 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 25 16:58:45 node-2 haproxy[30018]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:45 node-2 haproxy[30018]: 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 25 16:58:45 node-2 haproxy[30018]: proxy mysqld has no server available!
<129>Jul 25 16:58:45 node-2 haproxy[30018]: 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 25 16:58:46 node-2 haproxy[30018]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:46 node-2 haproxy[30018]: 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 25 16:58:46 node-2 haproxy[30018]: proxy object-storage has no server available!
<27>Jul 25 16:58:47 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:47 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:47 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:47 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:47 node-2 multipathd: uevent trigger error
<129>Jul 25 16:58:49 node-2 haproxy[31289]: 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 25 16:58:49 node-2 haproxy[31289]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:49 node-2 haproxy[31289]: 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 25 16:58:49 node-2 haproxy[31289]: proxy keystone-1 has no server available!
<129>Jul 25 16:58:50 node-2 haproxy[31294]: 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 25 16:58:50 node-2 haproxy[31294]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:50 node-2 haproxy[31294]: 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 25 16:58:50 node-2 haproxy[31294]: proxy keystone-2 has no server available!
<129>Jul 25 16:58:50 node-2 haproxy[31294]: 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 25 16:58:50 node-2 haproxy[31294]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:50 node-2 haproxy[31294]: 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 25 16:58:50 node-2 haproxy[31294]: proxy neutron has no server available!
<129>Jul 25 16:58:50 node-2 haproxy[31294]: 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 25 16:58:50 node-2 haproxy[31294]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:50 node-2 haproxy[31294]: 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 25 16:58:50 node-2 haproxy[31294]: proxy mysqld has no server available!
<129>Jul 25 16:58:50 node-2 haproxy[31294]: 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 25 16:58:51 node-2 haproxy[31294]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:51 node-2 haproxy[31294]: 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 25 16:58:51 node-2 haproxy[31294]: proxy object-storage has no server available!
<129>Jul 25 16:58:51 node-2 haproxy[31294]: 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 25 16:58:51 node-2 haproxy[31294]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:51 node-2 haproxy[31294]: 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 25 16:58:51 node-2 haproxy[31294]: proxy aodh has no server available!
<27>Jul 25 16:58:52 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:52 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:52 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:52 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:52 node-2 multipathd: uevent trigger error
<129>Jul 25 16:58:55 node-2 haproxy[32548]: 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 25 16:58:55 node-2 haproxy[32548]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:55 node-2 haproxy[32548]: 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 25 16:58:55 node-2 haproxy[32548]: proxy keystone-1 has no server available!
<129>Jul 25 16:58:55 node-2 haproxy[32548]: 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 25 16:58:55 node-2 haproxy[32548]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:55 node-2 haproxy[32548]: 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 25 16:58:55 node-2 haproxy[32548]: proxy keystone-2 has no server available!
<129>Jul 25 16:58:55 node-2 haproxy[32548]: 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 25 16:58:55 node-2 haproxy[32548]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:55 node-2 haproxy[32548]: 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 25 16:58:55 node-2 haproxy[32548]: proxy neutron has no server available!
<129>Jul 25 16:58:55 node-2 haproxy[32548]: 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 25 16:58:55 node-2 haproxy[32548]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:56 node-2 haproxy[32553]: 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 25 16:58:56 node-2 haproxy[32553]: proxy mysqld has no server available!
<129>Jul 25 16:58:56 node-2 haproxy[32553]: 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 25 16:58:56 node-2 haproxy[32553]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:56 node-2 haproxy[32553]: 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 25 16:58:56 node-2 haproxy[32553]: proxy object-storage has no server available!
<129>Jul 25 16:58:56 node-2 haproxy[32553]: 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 25 16:58:56 node-2 haproxy[32553]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:56 node-2 haproxy[32553]: 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 25 16:58:56 node-2 haproxy[32553]: proxy aodh has no server available!
<129>Jul 25 16:58:56 node-2 haproxy[32553]: 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 25 16:58:56 node-2 haproxy[32553]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:58:56 node-2 haproxy[32553]: 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 25 16:58:56 node-2 haproxy[32553]: proxy ceilometer has no server available!
<27>Jul 25 16:58:58 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:58 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:58 node-2 multipathd: uevent trigger error
<27>Jul 25 16:58:58 node-2 multipathd: uevent trigger error
<129>Jul 25 16:59:00 node-2 haproxy[1425]: 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 25 16:59:00 node-2 haproxy[1425]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:00 node-2 haproxy[1425]: 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 25 16:59:00 node-2 haproxy[1425]: proxy keystone-1 has no server available!
<129>Jul 25 16:59:00 node-2 haproxy[1425]: 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 25 16:59:00 node-2 haproxy[1425]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:00 node-2 haproxy[1425]: 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 25 16:59:00 node-2 haproxy[1425]: proxy keystone-2 has no server available!
<129>Jul 25 16:59:00 node-2 haproxy[1425]: 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 25 16:59:00 node-2 haproxy[1425]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:01 node-2 haproxy[1429]: 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 25 16:59:01 node-2 haproxy[1429]: proxy neutron has no server available!
<129>Jul 25 16:59:01 node-2 haproxy[1429]: 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 25 16:59:01 node-2 haproxy[1429]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:01 node-2 haproxy[1429]: 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 25 16:59:01 node-2 haproxy[1429]: proxy mysqld has no server available!
<129>Jul 25 16:59:01 node-2 haproxy[1429]: 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 25 16:59:01 node-2 haproxy[1429]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:01 node-2 haproxy[1429]: 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 25 16:59:01 node-2 haproxy[1429]: proxy object-storage has no server available!
<129>Jul 25 16:59:01 node-2 haproxy[1429]: 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 25 16:59:01 node-2 haproxy[1429]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:01 node-2 haproxy[1429]: 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 25 16:59:01 node-2 haproxy[1429]: proxy aodh has no server available!
<129>Jul 25 16:59:01 node-2 haproxy[1429]: 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 25 16:59:02 node-2 haproxy[1429]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:02 node-2 haproxy[1429]: 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 25 16:59:02 node-2 haproxy[1429]: proxy ceilometer has no server available!
<27>Jul 25 16:59:03 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:03 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:03 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:03 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:03 node-2 multipathd: uevent trigger error
<129>Jul 25 16:59:05 node-2 haproxy[2717]: 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 25 16:59:05 node-2 haproxy[2717]: 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 25 16:59:05 node-2 haproxy[2717]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:06 node-2 haproxy[2724]: 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 25 16:59:06 node-2 haproxy[2724]: proxy keystone-1 has no server available!
<129>Jul 25 16:59:06 node-2 haproxy[2724]: 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 25 16:59:06 node-2 haproxy[2724]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:06 node-2 haproxy[2724]: 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 25 16:59:06 node-2 haproxy[2724]: proxy keystone-2 has no server available!
<129>Jul 25 16:59:06 node-2 haproxy[2724]: 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 25 16:59:06 node-2 haproxy[2724]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:06 node-2 haproxy[2724]: 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 25 16:59:06 node-2 haproxy[2724]: proxy neutron has no server available!
<129>Jul 25 16:59:06 node-2 haproxy[2724]: 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 25 16:59:06 node-2 haproxy[2724]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:06 node-2 haproxy[2724]: 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 25 16:59:06 node-2 haproxy[2724]: proxy mysqld has no server available!
<129>Jul 25 16:59:06 node-2 haproxy[2724]: 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 25 16:59:06 node-2 haproxy[2724]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:06 node-2 haproxy[2724]: 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 25 16:59:06 node-2 haproxy[2724]: proxy object-storage has no server available!
<129>Jul 25 16:59:07 node-2 haproxy[2724]: 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 25 16:59:07 node-2 haproxy[2724]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:07 node-2 haproxy[2724]: 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 25 16:59:07 node-2 haproxy[2724]: proxy aodh has no server available!
<129>Jul 25 16:59:07 node-2 haproxy[2724]: 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 25 16:59:07 node-2 haproxy[2724]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:07 node-2 haproxy[2724]: 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 25 16:59:07 node-2 haproxy[2724]: proxy ceilometer has no server available!
<27>Jul 25 16:59:08 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:08 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:08 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:08 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:08 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:08 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:08 node-2 multipathd: uevent trigger error
<129>Jul 25 16:59:11 node-2 haproxy[4089]: 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 25 16:59:11 node-2 haproxy[4089]: 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 25 16:59:11 node-2 haproxy[4089]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:11 node-2 haproxy[4089]: 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 25 16:59:11 node-2 haproxy[4089]: proxy keystone-1 has no server available!
<129>Jul 25 16:59:11 node-2 haproxy[4089]: 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 25 16:59:12 node-2 haproxy[4093]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: proxy keystone-2 has no server available!
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: proxy glance-api has no server available!
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: proxy glance-glare has no server available!
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: proxy neutron has no server available!
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: proxy glance-registry has no server available!
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:12 node-2 haproxy[4093]: proxy mysqld has no server available!
<129>Jul 25 16:59:12 node-2 haproxy[4093]: 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 25 16:59:13 node-2 haproxy[4093]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:13 node-2 haproxy[4093]: 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 25 16:59:13 node-2 haproxy[4093]: proxy object-storage has no server available!
<129>Jul 25 16:59:13 node-2 haproxy[4093]: 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 25 16:59:13 node-2 haproxy[4093]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:13 node-2 haproxy[4093]: 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 25 16:59:13 node-2 haproxy[4093]: proxy aodh has no server available!
<129>Jul 25 16:59:13 node-2 haproxy[4093]: 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 25 16:59:13 node-2 haproxy[4093]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:13 node-2 haproxy[4093]: 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 25 16:59:13 node-2 haproxy[4093]: proxy ceilometer has no server available!
<27>Jul 25 16:59:14 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:14 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:14 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:14 node-2 multipathd: uevent trigger error
<129>Jul 25 16:59:17 node-2 haproxy[5532]: 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 25 16:59:17 node-2 haproxy[5532]: 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 25 16:59:17 node-2 haproxy[5532]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:17 node-2 haproxy[5532]: 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 25 16:59:17 node-2 haproxy[5532]: proxy keystone-1 has no server available!
<129>Jul 25 16:59:17 node-2 haproxy[5532]: 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 25 16:59:17 node-2 haproxy[5532]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:17 node-2 haproxy[5532]: 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 25 16:59:17 node-2 haproxy[5532]: proxy keystone-2 has no server available!
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: proxy nova-api has no server available!
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: proxy nova-metadata-api has no server available!
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: proxy glance-api has no server available!
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: proxy glance-glare has no server available!
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: proxy neutron has no server available!
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: proxy glance-registry has no server available!
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:18 node-2 haproxy[5554]: proxy mysqld has no server available!
<129>Jul 25 16:59:18 node-2 haproxy[5554]: 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 25 16:59:19 node-2 haproxy[5554]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:19 node-2 haproxy[5554]: 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 25 16:59:19 node-2 haproxy[5554]: proxy object-storage has no server available!
<129>Jul 25 16:59:19 node-2 haproxy[5554]: 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 25 16:59:19 node-2 haproxy[5554]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:19 node-2 haproxy[5554]: 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 25 16:59:19 node-2 haproxy[5554]: proxy aodh has no server available!
<129>Jul 25 16:59:19 node-2 haproxy[5554]: 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 25 16:59:19 node-2 haproxy[5554]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:19 node-2 haproxy[5554]: 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 25 16:59:19 node-2 haproxy[5554]: proxy ceilometer has no server available!
<129>Jul 25 16:59:19 node-2 haproxy[5554]: 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 25 16:59:19 node-2 haproxy[5554]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:19 node-2 haproxy[5554]: 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 25 16:59:19 node-2 haproxy[5554]: proxy nova-novncproxy has no server available!
<27>Jul 25 16:59:20 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:20 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:20 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:20 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:20 node-2 multipathd: uevent trigger error
<129>Jul 25 16:59:22 node-2 haproxy[6921]: 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 25 16:59:22 node-2 haproxy[6921]: 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 25 16:59:23 node-2 haproxy[6928]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: proxy keystone-1 has no server available!
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: proxy keystone-2 has no server available!
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: proxy nova-api has no server available!
<27>Jul 25 16:59:23 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: proxy nova-metadata-api has no server available!
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: proxy cinder-api has no server available!
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: proxy glance-api has no server available!
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: proxy glance-glare has no server available!
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:23 node-2 haproxy[6928]: 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 25 16:59:23 node-2 haproxy[6928]: proxy neutron has no server available!
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: proxy glance-registry has no server available!
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: proxy mysqld has no server available!
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: proxy object-storage has no server available!
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: proxy aodh has no server available!
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: proxy ceilometer has no server available!
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:24 node-2 haproxy[6928]: 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 25 16:59:24 node-2 haproxy[6928]: proxy nova-novncproxy has no server available!
<27>Jul 25 16:59:25 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:25 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:25 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:25 node-2 multipathd: uevent trigger error
<129>Jul 25 16:59:28 node-2 haproxy[8312]: 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 25 16:59:28 node-2 haproxy[8312]: 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 25 16:59:28 node-2 haproxy[8312]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:28 node-2 haproxy[8312]: 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 25 16:59:28 node-2 haproxy[8312]: proxy keystone-1 has no server available!
<129>Jul 25 16:59:28 node-2 haproxy[8312]: 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 25 16:59:28 node-2 haproxy[8312]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:28 node-2 haproxy[8312]: 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 25 16:59:28 node-2 haproxy[8312]: proxy keystone-2 has no server available!
<129>Jul 25 16:59:28 node-2 haproxy[8312]: 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 25 16:59:28 node-2 haproxy[8312]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:28 node-2 haproxy[8312]: 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 25 16:59:28 node-2 haproxy[8312]: proxy nova-api has no server available!
<129>Jul 25 16:59:28 node-2 haproxy[8312]: 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 25 16:59:28 node-2 haproxy[8312]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:28 node-2 haproxy[8312]: 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 25 16:59:28 node-2 haproxy[8312]: proxy nova-metadata-api has no server available!
<129>Jul 25 16:59:28 node-2 haproxy[8312]: 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 25 16:59:28 node-2 haproxy[8312]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: proxy cinder-api has no server available!
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: proxy glance-api has no server available!
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: proxy glance-glare has no server available!
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: proxy neutron has no server available!
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: proxy glance-registry has no server available!
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: proxy mysqld has no server available!
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: proxy object-storage has no server available!
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: proxy aodh has no server available!
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: proxy ceilometer has no server available!
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:29 node-2 haproxy[8316]: 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 25 16:59:29 node-2 haproxy[8316]: proxy heat-api has no server available!
<129>Jul 25 16:59:30 node-2 haproxy[8316]: 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 25 16:59:30 node-2 haproxy[8316]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:30 node-2 haproxy[8316]: 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 25 16:59:30 node-2 haproxy[8316]: proxy heat-api-cfn has no server available!
<129>Jul 25 16:59:30 node-2 haproxy[8316]: 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 25 16:59:30 node-2 haproxy[8316]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:30 node-2 haproxy[8316]: 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 25 16:59:30 node-2 haproxy[8316]: proxy heat-api-cloudwatch has no server available!
<129>Jul 25 16:59:30 node-2 haproxy[8316]: 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 25 16:59:30 node-2 haproxy[8316]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 25 16:59:30 node-2 haproxy[8316]: 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 25 16:59:30 node-2 haproxy[8316]: proxy nova-novncproxy has no server available!
<27>Jul 25 16:59:30 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 16:59:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:31 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:34 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:34 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:34 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:34 node-2 multipathd: uevent trigger error
<27>Jul 25 16:59:45 node-2 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 25 17:00:10 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 25 17:00:13 node-2 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 25 17:01:05 node-2 multipathd: uevent trigger error
<27>Jul 25 17:01:05 node-2 multipathd: uevent trigger error
<27>Jul 25 17:01:05 node-2 multipathd: uevent trigger error
<27>Jul 25 17:01:05 node-2 multipathd: uevent trigger error
<27>Jul 25 17:01:05 node-2 multipathd: uevent trigger error
<27>Jul 25 17:02:42 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 17:03:26 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:26 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:26 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:26 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:26 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:37 node-2 multipathd: uevent trigger error
<43>Jul 25 17:03:50 node-2 apache2_error [Mon Jul 25 17:03:50.425916 2016] [mpm_event:notice] [pid 21096:tid 139796657788800] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 17:03:50 node-2 apache2_error [Mon Jul 25 17:03:50.426052 2016] [core:notice] [pid 21096:tid 139796657788800] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 17:03:59 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:59 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:59 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:59 node-2 multipathd: uevent trigger error
<27>Jul 25 17:03:59 node-2 multipathd: uevent trigger error
<43>Jul 25 17:04:00 node-2 apache2_error [Mon Jul 25 17:03:53.622806 2016] [mpm_event:notice] [pid 21096:tid 139796657788800] AH00491: caught SIGTERM, shutting down
<43>Jul 25 17:04:00 node-2 apache2_error [Mon Jul 25 17:03:54.710506 2016] [mpm_worker:notice] [pid 21457:tid 140439394088832] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 25 17:04:00 node-2 apache2_error [Mon Jul 25 17:03:54.710570 2016] [core:notice] [pid 21457:tid 140439394088832] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 17:04:02 node-2 multipathd: uevent trigger error
<27>Jul 25 17:04:02 node-2 multipathd: uevent trigger error
<27>Jul 25 17:04:02 node-2 multipathd: uevent trigger error
<27>Jul 25 17:04:02 node-2 multipathd: uevent trigger error
<43>Jul 25 17:05:11 node-2 apache2_error [Mon Jul 25 17:05:10.511515 2016] [mpm_worker:notice] [pid 21457:tid 140439394088832] AH00295: caught SIGTERM, shutting down
<43>Jul 25 17:05:21 node-2 apache2_error [Mon Jul 25 17:05:11.270005 2016] [mpm_worker:notice] [pid 3011:tid 139889147918208] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 17:05:21 node-2 apache2_error [Mon Jul 25 17:05:11.270032 2016] [core:notice] [pid 3011:tid 139889147918208] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 17:05:43 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 25 17:06:01 node-2 apache2_error [Mon Jul 25 17:05:55.504013 2016] [mpm_worker:notice] [pid 3011:tid 139889147918208] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 17:06:01 node-2 apache2_error [Mon Jul 25 17:05:55.700510 2016] [mpm_worker:warn] [pid 3011:tid 139889147918208] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 17:06:01 node-2 apache2_error [Mon Jul 25 17:05:55.703492 2016] [mpm_worker:notice] [pid 3011:tid 139889147918208] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 17:06:01 node-2 apache2_error [Mon Jul 25 17:05:55.703506 2016] [core:notice] [pid 3011:tid 139889147918208] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 17:06:40 node-2 multipathd: uevent trigger error
<27>Jul 25 17:06:40 node-2 multipathd: uevent trigger error
<27>Jul 25 17:06:40 node-2 multipathd: uevent trigger error
<27>Jul 25 17:06:40 node-2 multipathd: uevent trigger error
<27>Jul 25 17:06:40 node-2 multipathd: uevent trigger error
<27>Jul 25 17:06:40 node-2 multipathd: uevent trigger error
<27>Jul 25 17:06:44 node-2 multipathd: uevent trigger error
<27>Jul 25 17:06:44 node-2 multipathd: uevent trigger error
<27>Jul 25 17:06:44 node-2 multipathd: uevent trigger error
<27>Jul 25 17:06:44 node-2 multipathd: uevent trigger error
<27>Jul 25 17:06:44 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:00 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:00 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:00 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:00 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:00 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:21 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:21 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:21 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:21 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:21 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:26 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:26 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:26 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:26 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:26 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:39 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:39 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:39 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:39 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:39 node-2 multipathd: uevent trigger error
<27>Jul 25 17:07:39 node-2 multipathd: uevent trigger error
<27>Jul 25 17:08:38 node-2 multipathd: uevent trigger error
<27>Jul 25 17:08:38 node-2 multipathd: uevent trigger error
<27>Jul 25 17:08:38 node-2 multipathd: uevent trigger error
<27>Jul 25 17:08:38 node-2 multipathd: uevent trigger error
<27>Jul 25 17:08:38 node-2 multipathd: uevent trigger error
<27>Jul 25 17:08:47 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 17:09:50 node-2 multipathd: uevent trigger error
<27>Jul 25 17:09:50 node-2 multipathd: uevent trigger error
<27>Jul 25 17:09:50 node-2 multipathd: uevent trigger error
<27>Jul 25 17:09:50 node-2 multipathd: uevent trigger error
<27>Jul 25 17:09:50 node-2 multipathd: uevent trigger error
<27>Jul 25 17:09:50 node-2 multipathd: uevent trigger error
<27>Jul 25 17:10:49 node-2 multipathd: uevent trigger error
<27>Jul 25 17:10:49 node-2 multipathd: uevent trigger error
<27>Jul 25 17:10:49 node-2 multipathd: uevent trigger error
<27>Jul 25 17:10:49 node-2 multipathd: uevent trigger error
<27>Jul 25 17:10:49 node-2 multipathd: uevent trigger error
<27>Jul 25 17:10:54 node-2 multipathd: uevent trigger error
<27>Jul 25 17:10:54 node-2 multipathd: uevent trigger error
<27>Jul 25 17:10:54 node-2 multipathd: uevent trigger error
<27>Jul 25 17:10:54 node-2 multipathd: uevent trigger error
<27>Jul 25 17:11:18 node-2 multipathd: uevent trigger error
<27>Jul 25 17:11:18 node-2 multipathd: uevent trigger error
<27>Jul 25 17:11:18 node-2 multipathd: uevent trigger error
<27>Jul 25 17:11:18 node-2 multipathd: uevent trigger error
<27>Jul 25 17:11:18 node-2 multipathd: uevent trigger error
<27>Jul 25 17:11:49 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 17:13:46 node-2 multipathd: uevent trigger error
<27>Jul 25 17:13:46 node-2 multipathd: uevent trigger error
<27>Jul 25 17:13:46 node-2 multipathd: uevent trigger error
<27>Jul 25 17:13:46 node-2 multipathd: uevent trigger error
<27>Jul 25 17:13:46 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:01 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:01 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:01 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:01 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:01 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:06 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:06 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:06 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:06 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:06 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:11 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:11 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:11 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:11 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:11 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:31 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:31 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:31 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:31 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:31 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:35 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:35 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:35 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:35 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:35 node-2 multipathd: uevent trigger error
<27>Jul 25 17:14:50 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 17:15:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:15:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:15:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:15:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:15:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:15:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:19 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:19 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:19 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:19 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:16:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:17:52 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 17:19:01 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:01 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:01 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:01 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:01 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:33 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:33 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:33 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:33 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:33 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:38 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:38 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:38 node-2 multipathd: uevent trigger error
<27>Jul 25 17:19:38 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:28 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:28 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:28 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:28 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:36 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:36 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:36 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:36 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:36 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:49 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:49 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:49 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:49 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:49 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:53 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 17:20:55 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:55 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:55 node-2 multipathd: uevent trigger error
<27>Jul 25 17:20:55 node-2 multipathd: uevent trigger error
<27>Jul 25 17:21:27 node-2 multipathd: uevent trigger error
<27>Jul 25 17:21:27 node-2 multipathd: uevent trigger error
<27>Jul 25 17:21:27 node-2 multipathd: uevent trigger error
<27>Jul 25 17:21:27 node-2 multipathd: uevent trigger error
<27>Jul 25 17:22:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:22:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:22:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:22:37 node-2 multipathd: uevent trigger error
<27>Jul 25 17:22:56 node-2 multipathd: uevent trigger error
<27>Jul 25 17:22:56 node-2 multipathd: uevent trigger error
<27>Jul 25 17:22:56 node-2 multipathd: uevent trigger error
<27>Jul 25 17:22:56 node-2 multipathd: uevent trigger error
<11>Jul 25 17:23:10 node-2 liberasurecode[16758]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:10 node-2 liberasurecode[16758]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:10 node-2 liberasurecode[16758]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:10 node-2 liberasurecode[16758]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:10 node-2 liberasurecode[16785]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:10 node-2 liberasurecode[16785]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:10 node-2 liberasurecode[16785]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:10 node-2 liberasurecode[16785]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:12 node-2 liberasurecode[18086]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:12 node-2 liberasurecode[18086]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:12 node-2 liberasurecode[18086]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:12 node-2 liberasurecode[18086]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:17 node-2 liberasurecode[19460]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:17 node-2 liberasurecode[19460]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:17 node-2 liberasurecode[19460]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:17 node-2 liberasurecode[19460]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:17 node-2 liberasurecode[19505]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:17 node-2 liberasurecode[19505]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:17 node-2 liberasurecode[19505]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:17 node-2 liberasurecode[19505]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19551]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19551]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19551]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19551]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19704]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19704]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19704]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19704]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19724]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19724]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19724]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19724]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19748]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19748]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19772]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19772]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19772]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:18 node-2 liberasurecode[19772]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:35 node-2 liberasurecode[20651]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:35 node-2 liberasurecode[20651]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:35 node-2 liberasurecode[20651]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:23:35 node-2 liberasurecode[20651]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 17:23:43 node-2 multipathd: uevent trigger error
<27>Jul 25 17:23:43 node-2 multipathd: uevent trigger error
<27>Jul 25 17:23:43 node-2 multipathd: uevent trigger error
<27>Jul 25 17:23:43 node-2 multipathd: uevent trigger error
<27>Jul 25 17:23:43 node-2 multipathd: uevent trigger error
<27>Jul 25 17:23:55 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<43>Jul 25 17:24:32 node-2 apache2_error [Mon Jul 25 17:24:31.169381 2016] [mpm_worker:notice] [pid 3011:tid 139889147918208] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 17:24:32 node-2 apache2_error [Mon Jul 25 17:24:31.554536 2016] [mpm_worker:warn] [pid 3011:tid 139889147918208] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 17:24:32 node-2 apache2_error [Mon Jul 25 17:24:31.562902 2016] [mpm_worker:notice] [pid 3011:tid 139889147918208] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 17:24:32 node-2 apache2_error [Mon Jul 25 17:24:31.562954 2016] [core:notice] [pid 3011:tid 139889147918208] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 25 17:25:02 node-2 liberasurecode[740]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:25:02 node-2 liberasurecode[740]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:25:02 node-2 liberasurecode[740]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:25:02 node-2 liberasurecode[740]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 25 17:25:12 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:12 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:12 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:12 node-2 multipathd: uevent trigger error
<43>Jul 25 17:25:12 node-2 apache2_error [Mon Jul 25 17:25:08.613033 2016] [mpm_worker:notice] [pid 3011:tid 139889147918208] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 17:25:12 node-2 apache2_error [Mon Jul 25 17:25:08.810487 2016] [mpm_worker:warn] [pid 3011:tid 139889147918208] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 17:25:12 node-2 apache2_error [Mon Jul 25 17:25:08.818909 2016] [mpm_worker:notice] [pid 3011:tid 139889147918208] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 17:25:12 node-2 apache2_error [Mon Jul 25 17:25:08.818937 2016] [core:notice] [pid 3011:tid 139889147918208] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 17:25:19 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:19 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:19 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:19 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:19 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:57 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:57 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:57 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:57 node-2 multipathd: uevent trigger error
<27>Jul 25 17:25:57 node-2 multipathd: uevent trigger error
<43>Jul 25 17:26:02 node-2 apache2_error [Mon Jul 25 17:25:53.981471 2016] [mpm_worker:notice] [pid 3011:tid 139889147918208] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 25 17:26:02 node-2 apache2_error [Mon Jul 25 17:25:54.178142 2016] [mpm_worker:warn] [pid 3011:tid 139889147918208] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 25 17:26:02 node-2 apache2_error [Mon Jul 25 17:25:54.186588 2016] [mpm_worker:notice] [pid 3011:tid 139889147918208] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 25 17:26:02 node-2 apache2_error [Mon Jul 25 17:25:54.186620 2016] [core:notice] [pid 3011:tid 139889147918208] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 25 17:26:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:10 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:10 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:10 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:10 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:10 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:10 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:10 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:20 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:34 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:34 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:34 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:34 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:55 node-2 multipathd: uevent trigger error
<27>Jul 25 17:26:56 node-2 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 25 17:27:02 node-2 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 25 17:27:11 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:11 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:11 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:11 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:11 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:16 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:16 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:16 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:16 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:22 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:22 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:22 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:22 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:22 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:34 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:34 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:34 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:34 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:34 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:38 node-2 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 25 17:27:48 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:48 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:48 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:48 node-2 multipathd: uevent trigger error
<27>Jul 25 17:27:48 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:04 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:09 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:09 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:09 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:09 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:16 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:16 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:16 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:16 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:16 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:21 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:21 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:21 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:21 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:32 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:46 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:46 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:46 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:46 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:46 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:51 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:51 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:51 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:51 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:56 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:56 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:56 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:56 node-2 multipathd: uevent trigger error
<27>Jul 25 17:28:56 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:05 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:05 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:05 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:05 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:05 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:09 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:09 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:09 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:09 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:09 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:14 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:14 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:14 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:14 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:14 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:18 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:18 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:18 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:18 node-2 multipathd: uevent trigger error
<27>Jul 25 17:29:18 node-2 multipathd: uevent trigger error
<11>Jul 25 17:30:01 node-2 liberasurecode[9140]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:30:01 node-2 liberasurecode[9140]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:30:01 node-2 liberasurecode[9140]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 25 17:30:01 node-2 liberasurecode[9140]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
