Jul 28 00:29:31 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8400" x-info="http://www.rsyslog.com"] start
Jul 28 00:29:31 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 28 00:29:31 node-5 rsyslogd: rsyslogd's groupid changed to 104
Jul 28 00:29:31 node-5 rsyslogd: rsyslogd's userid changed to 101
Jul 28 00:29:31 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 28 00:29:31 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 28 00:29:31 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 28 00:29:31 node-5 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 28 00:29:31 node-5 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=41e3acd0-3f1e-4ee9-b750-24d053a307c1 nomdmonddf nomdmonisw
Jul 28 00:29:31 node-5 kernel: [    0.000000] KERNEL supported cpus:
Jul 28 00:29:31 node-5 kernel: [    0.000000]   Intel GenuineIntel
Jul 28 00:29:31 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Jul 28 00:29:31 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Jul 28 00:29:31 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 28 00:29:31 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 28 00:29:31 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 28 00:29:31 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 28 00:29:31 node-5 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 28 00:29:31 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 28 00:29:31 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 28 00:29:31 node-5 kernel: [    0.000000] No AGP bridge found
Jul 28 00:29:31 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 28 00:29:31 node-5 kernel: [    0.000000] MTRR default type: write-back
Jul 28 00:29:31 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 28 00:29:31 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Jul 28 00:29:31 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 28 00:29:31 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 28 00:29:31 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 28 00:29:31 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 28 00:29:31 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 28 00:29:31 node-5 kernel: [    0.000000]   2 disabled
Jul 28 00:29:31 node-5 kernel: [    0.000000]   3 disabled
Jul 28 00:29:31 node-5 kernel: [    0.000000]   4 disabled
Jul 28 00:29:31 node-5 kernel: [    0.000000]   5 disabled
Jul 28 00:29:31 node-5 kernel: [    0.000000]   6 disabled
Jul 28 00:29:31 node-5 kernel: [    0.000000]   7 disabled
Jul 28 00:29:31 node-5 kernel: [    0.000000]   8 disabled
Jul 28 00:29:31 node-5 kernel: [    0.000000]   9 disabled
Jul 28 00:29:31 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 28 00:29:31 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 28 00:29:31 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 28 00:29:31 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 28 00:29:31 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 28 00:29:31 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Jul 28 00:29:31 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 28 00:29:31 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 28 00:29:31 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 28 00:29:31 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 28 00:29:31 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 28 00:29:31 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 28 00:29:31 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 28 00:29:31 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 28 00:29:31 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 28 00:29:31 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 28 00:29:31 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 28 00:29:31 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 28 00:29:31 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35820000-0x36c07fff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 28 00:29:31 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 28 00:29:31 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 28 00:29:31 node-5 kernel: [    0.000000] Zone ranges:
Jul 28 00:29:31 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] Movable zone start for each node
Jul 28 00:29:31 node-5 kernel: [    0.000000] Early memory node ranges
Jul 28 00:29:31 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 28 00:29:31 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 28 00:29:31 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 28 00:29:31 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 28 00:29:31 node-5 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 28 00:29:31 node-5 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 28 00:29:31 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 28 00:29:31 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 28 00:29:31 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 28 00:29:31 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 28 00:29:31 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 28 00:29:31 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 28 00:29:31 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 28 00:29:31 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 28 00:29:31 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 28 00:29:31 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 28 00:29:31 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 28 00:29:31 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 28 00:29:31 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 28 00:29:31 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 28 00:29:31 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 28 00:29:31 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 28 00:29:31 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 28 00:29:31 node-5 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 28 00:29:31 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 28 00:29:31 node-5 kernel: [    0.000000] Policy zone: Normal
Jul 28 00:29:31 node-5 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=41e3acd0-3f1e-4ee9-b750-24d053a307c1 nomdmonddf nomdmonisw
Jul 28 00:29:31 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 28 00:29:31 node-5 kernel: [    0.000000] Checking aperture...
Jul 28 00:29:31 node-5 kernel: [    0.000000] No AGP bridge found
Jul 28 00:29:31 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 28 00:29:31 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 28 00:29:31 node-5 kernel: [    0.000000] Memory: 32653312K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627184K reserved)
Jul 28 00:29:31 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 28 00:29:31 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 28 00:29:31 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 28 00:29:31 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 28 00:29:31 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 28 00:29:31 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 28 00:29:31 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 28 00:29:31 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 28 00:29:31 node-5 kernel: [    0.000000] console [tty0] enabled
Jul 28 00:29:31 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 28 00:29:31 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 28 00:29:31 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 28 00:29:31 node-5 kernel: [    0.000000] hpet clockevent registered
Jul 28 00:29:31 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 28 00:29:31 node-5 kernel: [    0.004000] tsc: Detected 3491.723 MHz processor
Jul 28 00:29:31 node-5 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.44 BogoMIPS (lpj=13966892)
Jul 28 00:29:31 node-5 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 28 00:29:31 node-5 kernel: [    0.000050] Security Framework initialized
Jul 28 00:29:31 node-5 kernel: [    0.000069] AppArmor: AppArmor initialized
Jul 28 00:29:31 node-5 kernel: [    0.000070] Yama: becoming mindful.
Jul 28 00:29:31 node-5 kernel: [    0.001460] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.006258] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.008186] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.008214] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.008504] Initializing cgroup subsys memory
Jul 28 00:29:31 node-5 kernel: [    0.008512] Initializing cgroup subsys devices
Jul 28 00:29:31 node-5 kernel: [    0.008514] Initializing cgroup subsys freezer
Jul 28 00:29:31 node-5 kernel: [    0.008516] Initializing cgroup subsys blkio
Jul 28 00:29:31 node-5 kernel: [    0.008517] Initializing cgroup subsys perf_event
Jul 28 00:29:31 node-5 kernel: [    0.008519] Initializing cgroup subsys hugetlb
Jul 28 00:29:31 node-5 kernel: [    0.008538] CPU: Physical Processor ID: 0
Jul 28 00:29:31 node-5 kernel: [    0.008540] CPU: Processor Core ID: 0
Jul 28 00:29:31 node-5 kernel: [    0.008543] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 28 00:29:31 node-5 kernel: [    0.008543] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 28 00:29:31 node-5 kernel: [    0.009237] mce: CPU supports 22 MCE banks
Jul 28 00:29:31 node-5 kernel: [    0.009264] CPU0: Thermal monitoring enabled (TM1)
Jul 28 00:29:31 node-5 kernel: [    0.009285] process: using mwait in idle threads
Jul 28 00:29:31 node-5 kernel: [    0.009288] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 28 00:29:31 node-5 kernel: [    0.009288] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 28 00:29:31 node-5 kernel: [    0.009288] tlb_flushall_shift: 6
Jul 28 00:29:31 node-5 kernel: [    0.009376] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 28 00:29:31 node-5 kernel: [    0.010102] ACPI: Core revision 20131115
Jul 28 00:29:31 node-5 kernel: [    0.022786] ACPI: All ACPI Tables successfully acquired
Jul 28 00:29:31 node-5 kernel: [    0.022950] ftrace: allocating 28617 entries in 112 pages
Jul 28 00:29:31 node-5 kernel: [    0.031779] dmar: Host address width 46
Jul 28 00:29:31 node-5 kernel: [    0.031782] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 28 00:29:31 node-5 kernel: [    0.031788] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 00:29:31 node-5 kernel: [    0.031789] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 28 00:29:31 node-5 kernel: [    0.031793] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 00:29:31 node-5 kernel: [    0.031795] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 28 00:29:31 node-5 kernel: [    0.031796] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 28 00:29:31 node-5 kernel: [    0.031797] dmar: ATSR flags: 0x0
Jul 28 00:29:31 node-5 kernel: [    0.031798] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 28 00:29:31 node-5 kernel: [    0.031800] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 28 00:29:31 node-5 kernel: [    0.031916] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 28 00:29:31 node-5 kernel: [    0.031917] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 00:29:31 node-5 kernel: [    0.031918] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 00:29:31 node-5 kernel: [    0.031919] HPET id 0 under DRHD base 0xc7ffc000
Jul 28 00:29:31 node-5 kernel: [    0.031920] Your BIOS is broken and requested that x2apic be disabled.
Jul 28 00:29:31 node-5 kernel: [    0.031920] This will slightly decrease performance.
Jul 28 00:29:31 node-5 kernel: [    0.031920] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 28 00:29:31 node-5 kernel: [    0.032351] Enabled IRQ remapping in xapic mode
Jul 28 00:29:31 node-5 kernel: [    0.032352] x2apic not enabled, IRQ remapping is in xapic mode
Jul 28 00:29:31 node-5 kernel: [    0.032356] Switched APIC routing to physical flat.
Jul 28 00:29:31 node-5 kernel: [    0.032991] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 28 00:29:31 node-5 kernel: [    0.072639] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 28 00:29:31 node-5 kernel: [    0.072644] TSC deadline timer enabled
Jul 28 00:29:31 node-5 kernel: [    0.072652] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 28 00:29:31 node-5 kernel: [    0.072658] ... version:                3
Jul 28 00:29:31 node-5 kernel: [    0.072659] ... bit width:              48
Jul 28 00:29:31 node-5 kernel: [    0.072660] ... generic registers:      4
Jul 28 00:29:31 node-5 kernel: [    0.072661] ... value mask:             0000ffffffffffff
Jul 28 00:29:31 node-5 kernel: [    0.072662] ... max period:             0000ffffffffffff
Jul 28 00:29:31 node-5 kernel: [    0.072663] ... fixed-purpose events:   3
Jul 28 00:29:31 node-5 kernel: [    0.072663] ... event mask:             000000070000000f
Jul 28 00:29:31 node-5 kernel: [    0.074109] x86: Booting SMP configuration:
Jul 28 00:29:31 node-5 kernel: [    0.088313] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 28 00:29:31 node-5 kernel: [    0.074111] .... node  #0, CPUs:        #1  #2  #3
Jul 28 00:29:31 node-5 kernel: [    0.116219] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 28 00:29:31 node-5 kernel: [    0.270165] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 28 00:29:31 node-5 kernel: [    0.325776] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 28 00:29:31 node-5 kernel: [    0.382438] x86: Booted up 2 nodes, 16 CPUs
Jul 28 00:29:31 node-5 kernel: [    0.382441] smpboot: Total of 16 processors activated (111747.25 BogoMIPS)
Jul 28 00:29:31 node-5 kernel: [    0.405393] devtmpfs: initialized
Jul 28 00:29:31 node-5 kernel: [    0.408523] EVM: security.selinux
Jul 28 00:29:31 node-5 kernel: [    0.408525] EVM: security.SMACK64
Jul 28 00:29:31 node-5 kernel: [    0.408526] EVM: security.ima
Jul 28 00:29:31 node-5 kernel: [    0.408527] EVM: security.capability
Jul 28 00:29:31 node-5 kernel: [    0.408576] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.409265] pinctrl core: initialized pinctrl subsystem
Jul 28 00:29:31 node-5 kernel: [    0.409326] regulator-dummy: no parameters
Jul 28 00:29:31 node-5 kernel: [    0.409358] RTC time:  0:28:52, date: 07/28/16
Jul 28 00:29:31 node-5 kernel: [    0.409392] NET: Registered protocol family 16
Jul 28 00:29:31 node-5 kernel: [    0.409475] cpuidle: using governor ladder
Jul 28 00:29:31 node-5 kernel: [    0.409476] cpuidle: using governor menu
Jul 28 00:29:31 node-5 kernel: [    0.409511] ACPI: bus type PCI registered
Jul 28 00:29:31 node-5 kernel: [    0.409512] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 28 00:29:31 node-5 kernel: [    0.409557] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 28 00:29:31 node-5 kernel: [    0.409560] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 28 00:29:31 node-5 kernel: [    0.423290] PCI: Using configuration type 1 for base access
Jul 28 00:29:31 node-5 kernel: [    0.424288] bio: create slab <bio-0> at 0
Jul 28 00:29:31 node-5 kernel: [    0.424568] ACPI: Added _OSI(Module Device)
Jul 28 00:29:31 node-5 kernel: [    0.424569] ACPI: Added _OSI(Processor Device)
Jul 28 00:29:31 node-5 kernel: [    0.424570] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 28 00:29:31 node-5 kernel: [    0.424571] ACPI: Added _OSI(Processor Aggregator Device)
Jul 28 00:29:31 node-5 kernel: [    0.437204] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 28 00:29:31 node-5 kernel: [    0.447721] ACPI: Interpreter enabled
Jul 28 00:29:31 node-5 kernel: [    0.447727] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 28 00:29:31 node-5 kernel: [    0.447731] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 28 00:29:31 node-5 kernel: [    0.447733] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 28 00:29:31 node-5 kernel: [    0.447740] ACPI: (supports S0 S4 S5)
Jul 28 00:29:31 node-5 kernel: [    0.447741] ACPI: Using IOAPIC for interrupt routing
Jul 28 00:29:31 node-5 kernel: [    0.447781] HEST: Table parsing has been initialized.
Jul 28 00:29:31 node-5 kernel: [    0.447784] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 28 00:29:31 node-5 kernel: [    0.448336] ACPI: No dock devices found.
Jul 28 00:29:31 node-5 kernel: [    0.459881] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 28 00:29:31 node-5 kernel: [    0.459886] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 00:29:31 node-5 kernel: [    0.459890] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 00:29:31 node-5 kernel: [    0.459916] PCI host bridge to bus 0000:ff
Jul 28 00:29:31 node-5 kernel: [    0.459918] pci_bus 0000:ff: root bus resource [bus ff]
Jul 28 00:29:31 node-5 kernel: [    0.459926] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.459964] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.459994] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460028] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460056] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.460084] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.460115] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460143] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460172] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460199] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460225] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460251] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460278] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460304] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460330] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460356] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460383] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460410] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460436] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.460464] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460489] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.460514] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460540] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460569] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.460602] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460633] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460662] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460692] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460722] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460752] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460782] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460812] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460843] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460875] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460907] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460939] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.460972] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461001] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461028] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461059] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461090] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461126] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461158] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461190] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461219] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461247] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461278] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461307] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461339] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461369] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461400] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461428] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461457] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461485] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461514] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461544] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461575] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461632] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 28 00:29:31 node-5 kernel: [    0.461634] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 00:29:31 node-5 kernel: [    0.461637] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 00:29:31 node-5 kernel: [    0.461654] PCI host bridge to bus 0000:7f
Jul 28 00:29:31 node-5 kernel: [    0.461656] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 28 00:29:31 node-5 kernel: [    0.461661] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461688] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.461715] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461744] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461766] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.461790] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.461815] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461840] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461866] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461889] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461911] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461933] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461956] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.461978] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462006] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462034] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462056] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462079] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462102] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.462125] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462147] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.462169] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462191] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462217] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 00:29:31 node-5 kernel: [    0.462250] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462276] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462303] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462330] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462355] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462381] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462407] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462434] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462458] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462484] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462509] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462535] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462563] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462589] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462613] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462640] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462665] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462694] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462724] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462752] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462779] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462804] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462829] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462856] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462883] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462910] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462938] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462964] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.462987] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.463013] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.463039] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.463068] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.463095] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.464351] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 28 00:29:31 node-5 kernel: [    0.464354] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 00:29:31 node-5 kernel: [    0.465470] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 00:29:31 node-5 kernel: [    0.465981] PCI host bridge to bus 0000:00
Jul 28 00:29:31 node-5 kernel: [    0.465986] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 28 00:29:31 node-5 kernel: [    0.465988] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 28 00:29:31 node-5 kernel: [    0.465989] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 28 00:29:31 node-5 kernel: [    0.465991] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 28 00:29:31 node-5 kernel: [    0.465992] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 28 00:29:31 node-5 kernel: [    0.465994] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 28 00:29:31 node-5 kernel: [    0.465995] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 28 00:29:31 node-5 kernel: [    0.466001] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 28 00:29:31 node-5 kernel: [    0.466084] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.466115] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.466156] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 28 00:29:31 node-5 kernel: [    0.466176] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.466206] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.466246] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 28 00:29:31 node-5 kernel: [    0.466265] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.466294] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.466337] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 28 00:29:31 node-5 kernel: [    0.466355] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.466425] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.466502] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.466577] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 00:29:31 node-5 kernel: [    0.466581] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 28 00:29:31 node-5 kernel: [    0.466666] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 28 00:29:31 node-5 kernel: [    0.466813] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 28 00:29:31 node-5 kernel: [    0.466830] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 28 00:29:31 node-5 kernel: [    0.466908] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.466963] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 28 00:29:31 node-5 kernel: [    0.466984] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.467040] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.467083] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 28 00:29:31 node-5 kernel: [    0.467110] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.467166] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.467209] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 28 00:29:31 node-5 kernel: [    0.467232] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 28 00:29:31 node-5 kernel: [    0.467249] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 28 00:29:31 node-5 kernel: [    0.467327] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.467376] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 28 00:29:31 node-5 kernel: [    0.467403] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 28 00:29:31 node-5 kernel: [    0.467653] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 28 00:29:31 node-5 kernel: [    0.467659] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 28 00:29:31 node-5 kernel: [    0.467665] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.467671] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.467678] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 28 00:29:31 node-5 kernel: [    0.467708] pci 0000:01:00.0: supports D1 D2
Jul 28 00:29:31 node-5 kernel: [    0.477998] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 00:29:31 node-5 kernel: [    0.478005] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 00:29:31 node-5 kernel: [    0.478009] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 00:29:31 node-5 kernel: [    0.478143] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.478176] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 28 00:29:31 node-5 kernel: [    0.485996] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 00:29:31 node-5 kernel: [    0.486002] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.486006] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 00:29:31 node-5 kernel: [    0.486091] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.486172] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.486248] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.486292] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 00:29:31 node-5 kernel: [    0.486295] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.486297] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 00:29:31 node-5 kernel: [    0.486349] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.486475] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.486528] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 00:29:31 node-5 kernel: [    0.486530] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.486532] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 00:29:31 node-5 kernel: [    0.486581] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.486700] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.486760] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.486885] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.486927] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.487046] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.487087] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 28 00:29:31 node-5 kernel: [    0.487229] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 28 00:29:31 node-5 kernel: [    0.487272] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 00:29:31 node-5 kernel: [    0.487275] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.487277] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 00:29:31 node-5 kernel: [    0.487345] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 28 00:29:31 node-5 kernel: [    0.487409] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.487465] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.487506] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 28 00:29:31 node-5 kernel: [    0.487588] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 28 00:29:31 node-5 kernel: [    0.487693] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 00:29:31 node-5 kernel: [    0.487696] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.487698] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 00:29:31 node-5 kernel: [    0.487780] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 28 00:29:31 node-5 kernel: [    0.487839] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.487887] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.488107] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 00:29:31 node-5 kernel: [    0.488111] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 00:29:31 node-5 kernel: [    0.488177] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 28 00:29:31 node-5 kernel: [    0.488234] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.488282] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.488491] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 00:29:31 node-5 kernel: [    0.488495] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 00:29:31 node-5 kernel: [    0.488556] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 28 00:29:31 node-5 kernel: [    0.488616] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.488668] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 28 00:29:31 node-5 kernel: [    0.488920] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 00:29:31 node-5 kernel: [    0.488923] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 00:29:31 node-5 kernel: [    0.489098] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 00:29:31 node-5 kernel: [    0.489137] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 00:29:31 node-5 kernel: [    0.489212] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 28 00:29:31 node-5 kernel: [    0.489231] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 28 00:29:31 node-5 kernel: [    0.489244] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 28 00:29:31 node-5 kernel: [    0.489258] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 28 00:29:31 node-5 kernel: [    0.489308] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 28 00:29:31 node-5 kernel: [    0.494002] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 00:29:31 node-5 kernel: [    0.494011] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 00:29:31 node-5 kernel: [    0.494063] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 28 00:29:31 node-5 kernel: [    0.494584] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 28 00:29:31 node-5 kernel: [    0.494587] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 00:29:31 node-5 kernel: [    0.494711] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 00:29:31 node-5 kernel: [    0.494818] PCI host bridge to bus 0000:80
Jul 28 00:29:31 node-5 kernel: [    0.494820] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 28 00:29:31 node-5 kernel: [    0.494822] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 28 00:29:31 node-5 kernel: [    0.494823] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 28 00:29:31 node-5 kernel: [    0.494831] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.494894] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.494963] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 00:29:31 node-5 kernel: [    0.495025] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 00:29:31 node-5 kernel: [    0.495030] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 28 00:29:31 node-5 kernel: [    0.495101] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 28 00:29:31 node-5 kernel: [    0.495401] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 28 00:29:31 node-5 kernel: [    0.495432] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 28 00:29:31 node-5 kernel: [    0.495462] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 28 00:29:31 node-5 kernel: [    0.495491] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 28 00:29:31 node-5 kernel: [    0.495520] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 00:29:31 node-5 kernel: [    0.495550] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 00:29:31 node-5 kernel: [    0.495579] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 00:29:31 node-5 kernel: [    0.495609] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 00:29:31 node-5 kernel: [    0.495695] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 28 00:29:31 node-5 kernel: [    0.495699] ACPI: \_SB_.UNC1: notify handler is installed
Jul 28 00:29:31 node-5 kernel: [    0.495700] ACPI: \_SB_.UNC0: notify handler is installed
Jul 28 00:29:31 node-5 kernel: [    0.495715] ACPI: \_SB_.PCI0: notify handler is installed
Jul 28 00:29:31 node-5 kernel: [    0.495768] ACPI: \_SB_.PCI1: notify handler is installed
Jul 28 00:29:31 node-5 kernel: [    0.495849] Found 4 acpi root devices
Jul 28 00:29:31 node-5 kernel: [    0.495967] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 28 00:29:31 node-5 kernel: [    0.495969] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 28 00:29:31 node-5 kernel: [    0.495971] vgaarb: loaded
Jul 28 00:29:31 node-5 kernel: [    0.495972] vgaarb: bridge control possible 0000:0c:00.0
Jul 28 00:29:31 node-5 kernel: [    0.496089] SCSI subsystem initialized
Jul 28 00:29:31 node-5 kernel: [    0.496152] libata version 3.00 loaded.
Jul 28 00:29:31 node-5 kernel: [    0.496167] ACPI: bus type USB registered
Jul 28 00:29:31 node-5 kernel: [    0.496176] usbcore: registered new interface driver usbfs
Jul 28 00:29:31 node-5 kernel: [    0.496181] usbcore: registered new interface driver hub
Jul 28 00:29:31 node-5 kernel: [    0.496203] usbcore: registered new device driver usb
Jul 28 00:29:31 node-5 kernel: [    0.496363] PCI: Using ACPI for IRQ routing
Jul 28 00:29:31 node-5 kernel: [    0.499976] PCI: pci_cache_line_size set to 64 bytes
Jul 28 00:29:31 node-5 kernel: [    0.500178] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 28 00:29:31 node-5 kernel: [    0.500179] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 28 00:29:31 node-5 kernel: [    0.500180] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 28 00:29:31 node-5 kernel: [    0.500245] NetLabel: Initializing
Jul 28 00:29:31 node-5 kernel: [    0.500246] NetLabel:  domain hash size = 128
Jul 28 00:29:31 node-5 kernel: [    0.500247] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 28 00:29:31 node-5 kernel: [    0.500257] NetLabel:  unlabeled traffic allowed by default
Jul 28 00:29:31 node-5 kernel: [    0.500312] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 28 00:29:31 node-5 kernel: [    0.500316] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 28 00:29:31 node-5 kernel: [    0.502370] Switched to clocksource hpet
Jul 28 00:29:31 node-5 kernel: [    0.506308] AppArmor: AppArmor Filesystem Enabled
Jul 28 00:29:31 node-5 kernel: [    0.506331] pnp: PnP ACPI init
Jul 28 00:29:31 node-5 kernel: [    0.506338] ACPI: bus type PNP registered
Jul 28 00:29:31 node-5 kernel: [    0.506452] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 28 00:29:31 node-5 kernel: [    0.506460] pnp 00:01: [dma 4]
Jul 28 00:29:31 node-5 kernel: [    0.506472] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 28 00:29:31 node-5 kernel: [    0.506498] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 28 00:29:31 node-5 kernel: [    0.506518] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 28 00:29:31 node-5 kernel: [    0.506535] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 28 00:29:31 node-5 kernel: [    0.506569] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 28 00:29:31 node-5 kernel: [    0.506623] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506625] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 28 00:29:31 node-5 kernel: [    0.506626] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506628] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506630] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506634] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506637] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 28 00:29:31 node-5 kernel: [    0.506638] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506640] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506641] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506643] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506644] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506646] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 28 00:29:31 node-5 kernel: [    0.506648] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 28 00:29:31 node-5 kernel: [    0.506731] pnp 00:07: [dma 0 disabled]
Jul 28 00:29:31 node-5 kernel: [    0.506759] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 00:29:31 node-5 kernel: [    0.506834] pnp 00:08: [dma 0 disabled]
Jul 28 00:29:31 node-5 kernel: [    0.506867] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 00:29:31 node-5 kernel: [    0.506917] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 28 00:29:31 node-5 kernel: [    0.507262] pnp: PnP ACPI: found 10 devices
Jul 28 00:29:31 node-5 kernel: [    0.507264] ACPI: bus type PNP unregistered
Jul 28 00:29:31 node-5 kernel: [    0.513523] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 00:29:31 node-5 kernel: [    0.513526] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 00:29:31 node-5 kernel: [    0.513528] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 00:29:31 node-5 kernel: [    0.513533] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 00:29:31 node-5 kernel: [    0.513535] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.513549] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513578] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 00:29:31 node-5 kernel: [    0.513595] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513624] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 00:29:31 node-5 kernel: [    0.513639] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 00:29:31 node-5 kernel: [    0.513667] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 00:29:31 node-5 kernel: [    0.513682] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 00:29:31 node-5 kernel: [    0.513710] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 00:29:31 node-5 kernel: [    0.513712] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.513742] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513770] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 00:29:31 node-5 kernel: [    0.513772] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.513786] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513815] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 00:29:31 node-5 kernel: [    0.513817] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.513819] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513824] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 00:29:31 node-5 kernel: [    0.513825] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.513828] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513831] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 00:29:31 node-5 kernel: [    0.513836] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 00:29:31 node-5 kernel: [    0.513844] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 00:29:31 node-5 kernel: [    0.513847] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 00:29:31 node-5 kernel: [    0.513854] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 28 00:29:31 node-5 kernel: [    0.513855] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 28 00:29:31 node-5 kernel: [    0.513856] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 28 00:29:31 node-5 kernel: [    0.513856] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 28 00:29:31 node-5 kernel: [    0.513857] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 28 00:29:31 node-5 kernel: [    0.513858] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 28 00:29:31 node-5 kernel: [    0.513859] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 28 00:29:31 node-5 kernel: [    0.513860] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 28 00:29:31 node-5 kernel: [    0.513861] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.513862] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513863] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.513864] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513865] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.513865] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513866] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.513867] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513868] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 28 00:29:31 node-5 kernel: [    0.513869] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513870] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 28 00:29:31 node-5 kernel: [    0.513871] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 28 00:29:31 node-5 kernel: [    0.513872] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 28 00:29:31 node-5 kernel: [    0.513873] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 28 00:29:31 node-5 kernel: [    0.513875] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 28 00:29:31 node-5 kernel: [    0.513876] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 28 00:29:31 node-5 kernel: [    0.513914] NET: Registered protocol family 2
Jul 28 00:29:31 node-5 kernel: [    0.514175] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.514515] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.514660] TCP: Hash tables configured (established 262144 bind 65536)
Jul 28 00:29:31 node-5 kernel: [    0.514697] TCP: reno registered
Jul 28 00:29:31 node-5 kernel: [    0.514726] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.514819] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.514964] NET: Registered protocol family 1
Jul 28 00:29:31 node-5 kernel: [    0.554465] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 28 00:29:31 node-5 kernel: [    0.554479] PCI: CLS 64 bytes, default 64
Jul 28 00:29:31 node-5 kernel: [    0.554550] Trying to unpack rootfs image as initramfs...
Jul 28 00:29:31 node-5 kernel: [    0.773621] Freeing initrd memory: 20384K (ffff880035820000 - ffff880036c08000)
Jul 28 00:29:31 node-5 kernel: [    0.773653] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 28 00:29:31 node-5 kernel: [    0.773655] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 28 00:29:31 node-5 kernel: [    0.774055] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774061] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774066] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774072] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774096] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774107] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774116] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774125] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774132] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774151] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774157] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774163] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774170] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774178] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774185] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774193] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 00:29:31 node-5 kernel: [    0.774270] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 28 00:29:31 node-5 kernel: [    0.774273] Scanning for low memory corruption every 60 seconds
Jul 28 00:29:31 node-5 kernel: [    0.774645] Initialise system trusted keyring
Jul 28 00:29:31 node-5 kernel: [    0.774698] audit: initializing netlink socket (disabled)
Jul 28 00:29:31 node-5 kernel: [    0.774714] type=2000 audit(1469665732.728:1): initialized
Jul 28 00:29:31 node-5 kernel: [    0.792588] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 28 00:29:31 node-5 kernel: [    0.794096] zbud: loaded
Jul 28 00:29:31 node-5 kernel: [    0.794236] VFS: Disk quotas dquot_6.5.2
Jul 28 00:29:31 node-5 kernel: [    0.794270] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 28 00:29:31 node-5 kernel: [    0.794644] fuse init (API version 7.22)
Jul 28 00:29:31 node-5 kernel: [    0.794706] msgmni has been set to 32768
Jul 28 00:29:31 node-5 kernel: [    0.794758] Key type big_key registered
Jul 28 00:29:31 node-5 kernel: [    0.795232] Key type asymmetric registered
Jul 28 00:29:31 node-5 kernel: [    0.795234] Asymmetric key parser 'x509' registered
Jul 28 00:29:31 node-5 kernel: [    0.795256] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 28 00:29:31 node-5 kernel: [    0.795336] io scheduler noop registered
Jul 28 00:29:31 node-5 kernel: [    0.795337] io scheduler deadline registered (default)
Jul 28 00:29:31 node-5 kernel: [    0.795358] io scheduler cfq registered
Jul 28 00:29:31 node-5 kernel: [    0.795767] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    0.795901] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    0.796019] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    0.796129] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    0.796243] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    0.796340] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    0.796730] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 28 00:29:31 node-5 kernel: [    0.796755] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 28 00:29:31 node-5 kernel: [    0.796771] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 28 00:29:31 node-5 kernel: [    0.796780] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796782] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796785] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 28 00:29:31 node-5 kernel: [    0.796790] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796792] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796793] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796795] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796796] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796798] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796799] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796801] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796802] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796804] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796805] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796807] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796810] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 28 00:29:31 node-5 kernel: [    0.796815] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796818] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 28 00:29:31 node-5 kernel: [    0.796833] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796836] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 28 00:29:31 node-5 kernel: [    0.796846] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796848] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 28 00:29:31 node-5 kernel: [    0.796851] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 28 00:29:31 node-5 kernel: [    0.796889] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 28 00:29:31 node-5 kernel: [    0.796895] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 28 00:29:31 node-5 kernel: [    0.796899] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 28 00:29:31 node-5 kernel: [    0.796909] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 28 00:29:31 node-5 kernel: [    0.796950] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 28 00:29:31 node-5 kernel: [    0.796951] vesafb: scrolling: redraw
Jul 28 00:29:31 node-5 kernel: [    0.796953] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 28 00:29:31 node-5 kernel: [    0.817602] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 28 00:29:31 node-5 kernel: [    0.826111] Console: switching to colour frame buffer device 80x30
Jul 28 00:29:31 node-5 kernel: [    0.834794] fb0: VESA VGA frame buffer device
Jul 28 00:29:31 node-5 kernel: [    0.835010] intel_idle: MWAIT substates: 0x2120
Jul 28 00:29:31 node-5 kernel: [    0.835011] intel_idle: v0.4 model 0x3F
Jul 28 00:29:31 node-5 kernel: [    0.835012] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 28 00:29:31 node-5 kernel: [    0.835240] ipmi message handler version 39.2
Jul 28 00:29:31 node-5 kernel: [    0.835527] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 28 00:29:31 node-5 kernel: [    0.835962] ACPI: AC Adapter [P111] (on-line)
Jul 28 00:29:31 node-5 kernel: [    0.841206] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 28 00:29:31 node-5 kernel: [    0.852213] ACPI: Power Button [PWRB]
Jul 28 00:29:31 node-5 kernel: [    0.858010] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 28 00:29:31 node-5 kernel: [    0.869643] ACPI: Power Button [PWRF]
Jul 28 00:29:31 node-5 kernel: [    0.895886] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 28 00:29:31 node-5 kernel: [    0.907532] pstore: Registered erst as persistent store backend
Jul 28 00:29:31 node-5 kernel: [    0.913712] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 28 00:29:31 node-5 kernel: [    0.925654] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 28 00:29:31 node-5 kernel: [    0.952387] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 28 00:29:31 node-5 kernel: [    0.985797] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 28 00:29:31 node-5 kernel: [    0.999884] Linux agpgart interface v0.103
Jul 28 00:29:31 node-5 kernel: [    1.007532] brd: module loaded
Jul 28 00:29:31 node-5 kernel: [    1.014562] loop: module loaded
Jul 28 00:29:31 node-5 kernel: [    1.021259] libphy: Fixed MDIO Bus: probed
Jul 28 00:29:31 node-5 kernel: [    1.027721] tun: Universal TUN/TAP device driver, 1.6
Jul 28 00:29:31 node-5 kernel: [    1.034188] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 28 00:29:31 node-5 kernel: [    1.040707] PPP generic driver version 2.4.2
Jul 28 00:29:31 node-5 kernel: [    1.047092] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 28 00:29:31 node-5 kernel: [    1.053523] ehci-pci: EHCI PCI platform driver
Jul 28 00:29:31 node-5 kernel: [    1.060037] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 28 00:29:31 node-5 kernel: [    1.066446] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 28 00:29:31 node-5 kernel: [    1.078960] ehci-pci 0000:00:1a.0: debug port 2
Jul 28 00:29:31 node-5 kernel: [    1.089160] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 28 00:29:31 node-5 kernel: [    1.089179] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 28 00:29:31 node-5 kernel: [    1.105863] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 28 00:29:31 node-5 kernel: [    1.111935] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 00:29:31 node-5 kernel: [    1.118113] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 00:29:31 node-5 kernel: [    1.130017] usb usb1: Product: EHCI Host Controller
Jul 28 00:29:31 node-5 kernel: [    1.136039] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 00:29:31 node-5 kernel: [    1.142155] usb usb1: SerialNumber: 0000:00:1a.0
Jul 28 00:29:31 node-5 kernel: [    1.148189] hub 1-0:1.0: USB hub found
Jul 28 00:29:31 node-5 kernel: [    1.153974] hub 1-0:1.0: 2 ports detected
Jul 28 00:29:31 node-5 kernel: [    1.159778] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 28 00:29:31 node-5 kernel: [    1.165364] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 28 00:29:31 node-5 kernel: [    1.176292] ehci-pci 0000:00:1d.0: debug port 2
Jul 28 00:29:31 node-5 kernel: [    1.185600] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 28 00:29:31 node-5 kernel: [    1.185603] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 28 00:29:31 node-5 kernel: [    1.201782] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 28 00:29:31 node-5 kernel: [    1.206993] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 00:29:31 node-5 kernel: [    1.212334] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 00:29:31 node-5 kernel: [    1.223088] usb usb2: Product: EHCI Host Controller
Jul 28 00:29:31 node-5 kernel: [    1.228604] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 00:29:31 node-5 kernel: [    1.234211] usb usb2: SerialNumber: 0000:00:1d.0
Jul 28 00:29:31 node-5 kernel: [    1.239804] hub 2-0:1.0: USB hub found
Jul 28 00:29:31 node-5 kernel: [    1.245178] hub 2-0:1.0: 2 ports detected
Jul 28 00:29:31 node-5 kernel: [    1.250493] ehci-platform: EHCI generic platform driver
Jul 28 00:29:31 node-5 kernel: [    1.255732] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 28 00:29:31 node-5 kernel: [    1.261066] ohci-pci: OHCI PCI platform driver
Jul 28 00:29:31 node-5 kernel: [    1.266370] ohci-platform: OHCI generic platform driver
Jul 28 00:29:31 node-5 kernel: [    1.271589] uhci_hcd: USB Universal Host Controller Interface driver
Jul 28 00:29:31 node-5 kernel: [    1.276946] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 28 00:29:31 node-5 kernel: [    1.473548] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 28 00:29:31 node-5 kernel: [    1.629713] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 28 00:29:31 node-5 kernel: [    1.635275] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 00:29:31 node-5 kernel: [    1.641106] hub 1-1:1.0: USB hub found
Jul 28 00:29:31 node-5 kernel: [    1.646698] hub 1-1:1.0: 6 ports detected
Jul 28 00:29:31 node-5 kernel: [    1.761305] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 28 00:29:31 node-5 kernel: [    1.769304] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 28 00:29:31 node-5 kernel: [    2.029374] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 28 00:29:31 node-5 kernel: [    2.034913] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 00:29:31 node-5 kernel: [    2.040767] hub 2-1:1.0: USB hub found
Jul 28 00:29:31 node-5 kernel: [    2.046485] hub 2-1:1.0: 8 ports detected
Jul 28 00:29:31 node-5 kernel: [    2.318472] i8042: No controller found
Jul 28 00:29:31 node-5 kernel: [    2.323897] mousedev: PS/2 mouse device common for all mice
Jul 28 00:29:31 node-5 kernel: [    2.324891] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 28 00:29:31 node-5 kernel: [    2.335005] rtc_cmos 00:02: RTC can wake from S4
Jul 28 00:29:31 node-5 kernel: [    2.340754] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 28 00:29:31 node-5 kernel: [    2.346369] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 28 00:29:31 node-5 kernel: [    2.357437] device-mapper: uevent: version 1.0.3
Jul 28 00:29:31 node-5 kernel: [    2.363062] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 28 00:29:31 node-5 kernel: [    2.374272] ledtrig-cpu: registered to indicate activity on CPUs
Jul 28 00:29:31 node-5 kernel: [    2.380187] TCP: cubic registered
Jul 28 00:29:31 node-5 kernel: [    2.386067] NET: Registered protocol family 10
Jul 28 00:29:31 node-5 kernel: [    2.392046] NET: Registered protocol family 17
Jul 28 00:29:31 node-5 kernel: [    2.397702] Key type dns_resolver registered
Jul 28 00:29:31 node-5 kernel: [    2.403658] Loading compiled-in X.509 certificates
Jul 28 00:29:31 node-5 kernel: [    2.409813] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 28 00:29:31 node-5 kernel: [    2.421163] registered taskstats version 1
Jul 28 00:29:31 node-5 kernel: [    2.429113] Key type trusted registered
Jul 28 00:29:31 node-5 kernel: [    2.436651] Key type encrypted registered
Jul 28 00:29:31 node-5 kernel: [    2.442102] AppArmor: AppArmor sha1 policy hashing enabled
Jul 28 00:29:31 node-5 kernel: [    2.447586] IMA: No TPM chip found, activating TPM-bypass!
Jul 28 00:29:31 node-5 kernel: [    2.453728] regulator-dummy: disabling
Jul 28 00:29:31 node-5 kernel: [    2.459291]   Magic number: 8:34:457
Jul 28 00:29:31 node-5 kernel: [    2.461447] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 28 00:29:31 node-5 kernel: [    2.461448] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 28 00:29:31 node-5 kernel: [    2.461449] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 28 00:29:31 node-5 kernel: [    2.461450] usb 2-1.4: Manufacturer: Avocent
Jul 28 00:29:31 node-5 kernel: [    2.461450] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 28 00:29:31 node-5 kernel: [    2.498107] rtc_cmos 00:02: setting system clock to 2016-07-28 00:28:54 UTC (1469665734)
Jul 28 00:29:31 node-5 kernel: [    2.510676] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 28 00:29:31 node-5 kernel: [    2.516416] EDD information not available.
Jul 28 00:29:31 node-5 kernel: [    2.522110] PM: Hibernation image not present or could not be loaded.
Jul 28 00:29:31 node-5 kernel: [    2.522973] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 28 00:29:31 node-5 kernel: [    2.534339] Write protecting the kernel read-only data: 12288k
Jul 28 00:29:31 node-5 kernel: [    2.540661] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 28 00:29:31 node-5 kernel: [    2.553218] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 28 00:29:31 node-5 kernel: [    2.585949] device-mapper: multipath: version 1.6.0 loaded
Jul 28 00:29:31 node-5 kernel: [    2.593988] systemd-udevd[215]: starting version 204
Jul 28 00:29:31 node-5 kernel: [    2.615183] md: linear personality registered for level -1
Jul 28 00:29:31 node-5 kernel: [    2.629228] md: multipath personality registered for level -4
Jul 28 00:29:31 node-5 kernel: [    2.637319] md: raid0 personality registered for level 0
Jul 28 00:29:31 node-5 kernel: [    2.645468] md: raid1 personality registered for level 1
Jul 28 00:29:31 node-5 kernel: [    2.656365] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 28 00:29:31 node-5 kernel: [    2.662800] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 28 00:29:31 node-5 kernel: [    2.669240] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 28 00:29:31 node-5 kernel: [    2.672341] megasas: FW now in Ready state
Jul 28 00:29:31 node-5 kernel: [    2.673191] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.673376] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.673476] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.673576] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.673674] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.673789] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.673956] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.674049] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.674172] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.674330] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.674482] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.674554] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.674696] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.674810] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.674938] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.675107] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.675844] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 28 00:29:31 node-5 kernel: [    2.695063] hidraw: raw HID events driver (C) Jiri Kosina
Jul 28 00:29:31 node-5 kernel: [    2.703614] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 28 00:29:31 node-5 kernel: [    2.709689] usbcore: registered new interface driver usbhid
Jul 28 00:29:31 node-5 kernel: [    2.709690] usbhid: USB HID core driver
Jul 28 00:29:31 node-5 kernel: [    2.720682] raid6: sse2x1     875 MB/s
Jul 28 00:29:31 node-5 kernel: [    2.736806] 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 28 00:29:31 node-5 kernel: [    2.750014] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 00:29:31 node-5 kernel: [    2.756810] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.756815] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.756819] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.756823] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.756869] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 00:29:31 node-5 kernel: [    2.788458] raid6: sse2x2    3502 MB/s
Jul 28 00:29:31 node-5 kernel: [    2.860383] raid6: sse2x4   10118 MB/s
Jul 28 00:29:31 node-5 kernel: [    2.932317] raid6: avx2x1   14943 MB/s
Jul 28 00:29:31 node-5 kernel: [    3.004270] raid6: avx2x2   18872 MB/s
Jul 28 00:29:31 node-5 kernel: [    3.076202] raid6: avx2x4   21371 MB/s
Jul 28 00:29:31 node-5 kernel: [    3.081741] raid6: using algorithm avx2x4 (21371 MB/s)
Jul 28 00:29:31 node-5 kernel: [    3.087339] raid6: using avx2x2 recovery algorithm
Jul 28 00:29:31 node-5 kernel: [    3.092868] Switched to clocksource tsc
Jul 28 00:29:31 node-5 kernel: [    3.098882] xor: automatically using best checksumming function:
Jul 28 00:29:31 node-5 kernel: [    3.104589] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 28 00:29:31 node-5 kernel: [    3.115322] 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 28 00:29:31 node-5 kernel: [    3.126860] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 00:29:31 node-5 kernel: [    3.132782] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.132789] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.132795] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.132799] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.132843] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.132950] 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 28 00:29:31 node-5 kernel: [    3.133010] 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 28 00:29:31 node-5 kernel: [    3.133078] 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 28 00:29:31 node-5 kernel: [    3.133125] 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 28 00:29:31 node-5 kernel: [    3.133180] 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 28 00:29:31 node-5 kernel: [    3.133223] 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 28 00:29:31 node-5 kernel: [    3.144163]    avx       : 35182.000 MB/sec
Jul 28 00:29:31 node-5 kernel: [    3.224850] async_tx: api initialized (async)
Jul 28 00:29:31 node-5 kernel: [    3.232566] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 28 00:29:31 node-5 kernel: [    3.246035] 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 28 00:29:31 node-5 kernel: [    3.260565] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 00:29:31 node-5 kernel: [    3.268109] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.268114] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.268119] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.268124] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.268162] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.285142] md: raid6 personality registered for level 6
Jul 28 00:29:31 node-5 kernel: [    3.292619] md: raid5 personality registered for level 5
Jul 28 00:29:31 node-5 kernel: [    3.292974] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 28 00:29:31 node-5 kernel: [    3.292977] 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 28 00:29:31 node-5 kernel: [    3.292978] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 00:29:31 node-5 kernel: [    3.293342] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.293476] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.293613] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.293729] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.293873] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 00:29:31 node-5 kernel: [    3.350622] md: raid4 personality registered for level 4
Jul 28 00:29:31 node-5 kernel: [    3.361060] md: raid10 personality registered for level 10
Jul 28 00:29:31 node-5 kernel: [    3.417189] multipathd (355): /proc/355/oom_adj is deprecated, please use /proc/355/oom_score_adj instead.
Jul 28 00:29:31 node-5 kernel: [    3.691714] megasas:IOC Init cmd success
Jul 28 00:29:31 node-5 kernel: [    3.743716] megasas: INIT adapter done
Jul 28 00:29:31 node-5 kernel: [    3.819629] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 28 00:29:31 node-5 kernel: [    3.826216] scsi0 : LSI SAS based MegaRAID driver
Jul 28 00:29:31 node-5 kernel: [    3.833739] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 00:29:31 node-5 kernel: [    3.852057] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 00:29:31 node-5 kernel: [    3.866866] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 28 00:29:31 node-5 kernel: [    3.873347] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 28 00:29:31 node-5 kernel: [    3.886253] sd 0:2:0:0: [sda] Write Protect is off
Jul 28 00:29:31 node-5 kernel: [    3.892778] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 28 00:29:31 node-5 kernel: [    3.892798] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 28 00:29:31 node-5 kernel: [    3.936650]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 28 00:29:31 node-5 kernel: [    3.943534] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 28 00:29:31 node-5 kernel: [    4.080705] random: lvm urandom read with 30 bits of entropy available
Jul 28 00:29:31 node-5 kernel: [    4.208889] bio: create slab <bio-1> at 1
Jul 28 00:29:31 node-5 kernel: [    5.103341] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 00:29:31 node-5 kernel: [    5.860525] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 28 00:29:31 node-5 kernel: [    5.866768] random: nonblocking pool is initialized
Jul 28 00:29:31 node-5 kernel: [    5.912689] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 28 00:29:31 node-5 kernel: [    6.066208] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 28 00:29:31 node-5 kernel: [    6.120053] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 28 00:29:31 node-5 kernel: [    6.195656] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 00:29:31 node-5 kernel: [    6.435381] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 28 00:29:31 node-5 kernel: [    6.464957] XFS (dm-1): Mounting Filesystem
Jul 28 00:29:31 node-5 kernel: [    6.610274] XFS (dm-1): Ending clean mount
Jul 28 00:29:31 node-5 kernel: [    6.657082] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 00:29:31 node-5 kernel: [    6.684762] XFS (dm-2): Mounting Filesystem
Jul 28 00:29:31 node-5 kernel: [    6.802897] XFS (dm-2): Ending clean mount
Jul 28 00:29:31 node-5 kernel: [    7.049121] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 00:29:31 node-5 kernel: [    8.862970] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 28 00:29:31 node-5 kernel: [    8.877732] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 28 00:29:31 node-5 kernel: [    9.045180] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 28 00:29:31 node-5 kernel: [    9.045185] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 28 00:29:31 node-5 kernel: [    9.045190] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 28 00:29:31 node-5 kernel: [    9.045194] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 28 00:29:31 node-5 kernel: [    9.084086] systemd-udevd[801]: starting version 204
Jul 28 00:29:31 node-5 kernel: [    9.354693] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 28 00:29:31 node-5 kernel: [    9.354699] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 00:29:31 node-5 kernel: [    9.354702] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 28 00:29:31 node-5 kernel: [    9.354703] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 00:29:31 node-5 kernel: [    9.354719] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 28 00:29:31 node-5 kernel: [    9.368254] power_meter ACPI000D:00: Found ACPI power meter.
Jul 28 00:29:31 node-5 kernel: [    9.368262] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 28 00:29:31 node-5 kernel: [    9.377853] wmi: Mapper loaded
Jul 28 00:29:31 node-5 kernel: [    9.395129] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 28 00:29:31 node-5 kernel: [    9.449015] IPMI System Interface driver.
Jul 28 00:29:31 node-5 kernel: [    9.449047] ipmi_si: probing via ACPI
Jul 28 00:29:31 node-5 kernel: [    9.449062] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 28 00:29:31 node-5 kernel: [    9.449063] ipmi_si: Adding ACPI-specified kcs state machine
Jul 28 00:29:31 node-5 kernel: [    9.449070] ipmi_si: probing via SMBIOS
Jul 28 00:29:31 node-5 kernel: [    9.449071] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 00:29:31 node-5 kernel: [    9.449071] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 28 00:29:31 node-5 kernel: [    9.449073] ipmi_si: probing via SPMI
Jul 28 00:29:31 node-5 kernel: [    9.449074] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 00:29:31 node-5 kernel: [    9.449074] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 28 00:29:31 node-5 kernel: [    9.449075] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 28 00:29:31 node-5 kernel: [    9.487457] systemd-udevd[841]: renamed network interface eth1 to enp7s0
Jul 28 00:29:31 node-5 kernel: [    9.511157] systemd-udevd[842]: renamed network interface eth0 to enp6s0
Jul 28 00:29:31 node-5 kernel: [    9.559089] systemd-udevd[830]: renamed network interface eth2 to enp8s0
Jul 28 00:29:31 node-5 kernel: [    9.587088] systemd-udevd[829]: renamed network interface eth3 to enp9s0
Jul 28 00:29:31 node-5 kernel: [    9.610934] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 28 00:29:31 node-5 kernel: [    9.610941] ipmi_si 00:09: IPMI kcs interface initialized
Jul 28 00:29:31 node-5 kernel: [   10.017800] type=1400 audit(1469665742.018:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1094 comm="apparmor_parser"
Jul 28 00:29:31 node-5 kernel: [   10.017959] type=1400 audit(1469665742.018:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1094 comm="apparmor_parser"
Jul 28 00:29:31 node-5 kernel: [   10.018088] type=1400 audit(1469665742.018:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1094 comm="apparmor_parser"
Jul 28 00:29:31 node-5 kernel: [   10.036480] type=1400 audit(1469665742.038:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1096 comm="apparmor_parser"
Jul 28 00:29:31 node-5 kernel: [   10.036620] type=1400 audit(1469665742.038:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1096 comm="apparmor_parser"
Jul 28 00:29:31 node-5 kernel: [   10.036743] type=1400 audit(1469665742.038:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1096 comm="apparmor_parser"
Jul 28 00:29:31 node-5 kernel: [   10.040385] type=1400 audit(1469665742.042:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1095 comm="apparmor_parser"
Jul 28 00:29:31 node-5 kernel: [   10.040552] type=1400 audit(1469665742.042:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1095 comm="apparmor_parser"
Jul 28 00:29:31 node-5 kernel: [   10.040677] type=1400 audit(1469665742.042:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1095 comm="apparmor_parser"
Jul 28 00:29:31 node-5 kernel: [   10.050983] type=1400 audit(1469665742.054:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1093 comm="apparmor_parser"
Jul 28 00:29:31 node-5 kernel: [   10.576369] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 28 00:29:31 node-5 kernel: [   10.577216] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 28 00:29:31 node-5 kernel: [   10.760996] enic 0000:06:00.0 enp6s0: Link UP
Jul 28 00:29:31 node-5 kernel: [   10.761545] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 28 00:29:31 node-5 kernel: [   10.761555] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 28 00:29:31 node-5 kernel: [   21.545976] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 28 00:29:31 node-5 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 28 00:29:32 node-5 failsafe: Failsafe of 120 seconds reached.
Jul 28 00:29:33 node-5 kernel: [   40.406007] init: failsafe main process (8427) killed by TERM signal
Jul 28 00:29:33 node-5 dbus[8471]: [system] AppArmor D-Bus mediation is enabled
Jul 28 00:29:33 node-5 kernel: [   40.667345] audit_printk_skb: 30 callbacks suppressed
Jul 28 00:29:33 node-5 kernel: [   40.667347] type=1400 audit(1469665773.282:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8544 comm="apparmor_parser"
Jul 28 00:29:33 node-5 kernel: [   40.667351] type=1400 audit(1469665773.282:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8544 comm="apparmor_parser"
Jul 28 00:29:33 node-5 kernel: [   40.667354] type=1400 audit(1469665773.282:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Jul 28 00:29:33 node-5 kernel: [   40.667694] type=1400 audit(1469665773.282:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8544 comm="apparmor_parser"
Jul 28 00:29:33 node-5 kernel: [   40.667696] type=1400 audit(1469665773.282:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Jul 28 00:29:33 node-5 kernel: [   40.667915] type=1400 audit(1469665773.282:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8544 comm="apparmor_parser"
Jul 28 00:29:33 node-5 kernel: [   40.669329] type=1400 audit(1469665773.286:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8545 comm="apparmor_parser"
Jul 28 00:29:33 node-5 kernel: [   40.739679] type=1400 audit(1469665773.354:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8547 comm="apparmor_parser"
Jul 28 00:29:33 node-5 anacron[8620]: Anacron 2.3 started on 2016-07-28
Jul 28 00:29:33 node-5 anacron[8620]: Will run job `cron.daily' in 5 min.
Jul 28 00:29:33 node-5 anacron[8620]: Will run job `cron.weekly' in 10 min.
Jul 28 00:29:33 node-5 anacron[8620]: Will run job `cron.monthly' in 15 min.
Jul 28 00:29:33 node-5 anacron[8620]: Jobs will be executed sequentially
Jul 28 00:29:33 node-5 cron[8585]: (CRON) INFO (pidfile fd = 3)
Jul 28 00:29:33 node-5 cron[8643]: (CRON) STARTUP (fork ok)
Jul 28 00:29:33 node-5 multipathd: path checkers start up
Jul 28 00:29:33 node-5 cron[8643]: (CRON) INFO (Running @reboot jobs)
Jul 28 00:29:34 node-5 postfix/master[8764]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 28 00:29:37 node-5 puppet-agent[8948]: Reopening log files
Jul 28 00:29:38 node-5 puppet-agent[8948]: Could not request certificate: Connection refused - connect(2)
Jul 28 00:29:47 node-5 puppet-user[9027]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 28 00:29:47 node-5 puppet-user[9027]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 28 00:29:47 node-5 puppet-user[9027]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 28 00:29:47 node-5 puppet-user[9027]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 28 00:29:48 node-5 puppet-user[9027]: Finished catalog run in 0.37 seconds
Jul 28 00:29:49 node-5 multipathd: uevent trigger error
Jul 28 00:29:49 node-5 puppet-user[9462]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 00:29:49 node-5 puppet-user[9462]: Compiled catalog for node-5.domain.tld in environment production in 0.10 seconds
Jul 28 00:29:49 node-5 puppet-user[9462]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 28 00:29:50 node-5 puppet-user[9462]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 28 00:29:50 node-5 puppet-user[9462]: (/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 28 00:29:50 node-5 puppet-user[9462]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 28 00:29:50 node-5 puppet-user[9462]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 28 00:29:50 node-5 puppet-user[9462]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 28 00:29:50 node-5 puppet-user[9462]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 28 00:29:50 node-5 puppet-user[9462]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 28 00:29:50 node-5 puppet-user[9462]: Finished catalog run in 0.06 seconds
Jul 28 00:29:51 node-5 puppet-user[9944]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 28 00:29:51 node-5 puppet-user[9944]: Compiled catalog for node-5.domain.tld in environment production in 0.07 seconds
Jul 28 00:29:51 node-5 puppet-user[9944]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 28 00:29:51 node-5 puppet-user[9944]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 28 00:29:51 node-5 puppet-user[9944]: Finished catalog run in 0.05 seconds
Jul 28 00:29:53 node-5 puppet-user[10515]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 28 00:29:53 node-5 puppet-user[10515]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 28 00:29:53 node-5 puppet-user[10515]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 28 00:29:53 node-5 puppet-user[10515]: Finished catalog run in 0.04 seconds
Jul 28 00:29:54 node-5 puppet-user[10969]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 28 00:29:54 node-5 puppet-user[10969]: Compiled catalog for node-5.domain.tld in environment production in 0.18 seconds
Jul 28 00:29:54 node-5 puppet-user[10969]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 28 00:29:55 node-5 puppet-user[10969]: (/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 28 00:29:55 node-5 puppet-user[10969]: Finished catalog run in 0.47 seconds
Jul 28 00:29:56 node-5 puppet-user[11450]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 28 00:29:56 node-5 puppet-user[11450]: Compiled catalog for node-5.domain.tld in environment production in 0.21 seconds
Jul 28 00:29:56 node-5 puppet-user[11450]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 28 00:29:56 node-5 puppet-user[11450]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 28 00:29:56 node-5 puppet-user[11450]: (/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 28 00:29:56 node-5 puppet-user[11450]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 28 00:29:56 node-5 puppet-user[11450]: Finished catalog run in 0.29 seconds
Jul 28 00:29:58 node-5 puppet-user[11934]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 28 00:29:58 node-5 puppet-user[11934]: Compiled catalog for node-5.domain.tld in environment production in 0.15 seconds
Jul 28 00:29:58 node-5 puppet-user[11934]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 28 00:29:58 node-5 kernel: [   66.366880] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 28 00:29:58 node-5 kernel: [   66.366929] 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 28 00:29:58 node-5 puppet-user[11934]: (/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 28 00:29:58 node-5 puppet-user[11934]: Finished catalog run in 0.06 seconds
Jul 28 00:30:00 node-5 puppet-user[12396]: (Scope(Class[main])) MODULAR: sync_time
Jul 28 00:30:00 node-5 puppet-user[12396]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 28 00:30:00 node-5 ntpdate[12823]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 28 00:30:01 node-5 CRON[12845]: (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 28 00:30:06 node-5 ntpdate[12823]: adjust time server 10.20.0.2 offset 0.001249 sec
Jul 28 00:30:06 node-5 puppet-user[12396]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 28 00:30:06 node-5 puppet-user[12396]: Finished catalog run in 6.18 seconds
Jul 28 00:30:10 node-5 puppet-user[13218]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 00:30:10 node-5 puppet-user[13218]: Compiled catalog for node-5.domain.tld in environment production in 0.07 seconds
Jul 28 00:30:10 node-5 puppet-user[13218]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 28 00:30:10 node-5 puppet-user[13218]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 28 00:30:10 node-5 puppet-user[13218]: Finished catalog run in 0.06 seconds
Jul 28 00:30:12 node-5 puppet-user[13678]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 28 00:30:13 node-5 puppet-user[13678]: Compiled catalog for node-5.domain.tld in environment production in 1.00 seconds
Jul 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:13 node-5 puppet-user[13678]: (/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 28 00:30:15 node-5 kernel: [   83.396198] init: plymouth-upstart-bridge main process ended, respawning
Jul 28 00:30:15 node-5 puppet-agent[8948]: Could not run: SIGTERM
Jul 28 00:30:16 node-5 kernel: [   83.662557] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 28 00:30:16 node-5 ec2: 
Jul 28 00:30:16 node-5 ec2: #############################################################
Jul 28 00:30:16 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 28 00:30:16 node-5 ec2: 1024 bc:15:4b:05:6a:35:67:16:44:fe:52:5c:b0:eb:af:11  root@node-5.domain.tld (DSA)
Jul 28 00:30:16 node-5 ec2: 256 bc:67:16:5f:c8:de:df:fd:51:8b:00:3e:79:05:8d:c2  root@node-5.domain.tld (ECDSA)
Jul 28 00:30:16 node-5 ec2: 256 34:f4:9e:64:ea:27:23:68:65:6a:91:b5:a3:e0:01:21  root@node-5.domain.tld (ED25519)
Jul 28 00:30:16 node-5 ec2: 2048 4e:8b:38:0f:ed:1e:ed:c5:37:07:57:46:bd:0c:d9:39  root@node-5.domain.tld (RSA)
Jul 28 00:30:16 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 28 00:30:16 node-5 ec2: #############################################################
Jul 28 00:30:24 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 00:30:24 node-5 nailgun-agent: D, [2016-07-28T00:30:01.594858 #12848] DEBUG -- : Sleep for 23 seconds before sending request
Jul 28 00:30:24 node-5 nailgun-agent: I, [2016-07-28T00:30:24.609625 #12848]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 00:30:25 node-5 nailgun-agent: D, [2016-07-28T00:30:25.037751 #12848] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 28 00:30:28 node-5 puppet-user[13678]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 28 00:30:28 node-5 puppet-user[13678]: Finished catalog run in 15.01 seconds
Jul 28 00:30:29 node-5 puppet-user[15007]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 28 00:30:30 node-5 puppet-user[15007]: Compiled catalog for node-5.domain.tld in environment production in 0.12 seconds
Jul 28 00:30:34 node-5 puppet-user[15007]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.232766 #12848] DEBUG -- : Trying to find block devices
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.232974 #12848] DEBUG -- : Found block device: sda
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.233046 #12848] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.233084 #12848] DEBUG -- : Trying to get list of physical devices
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.233339 #12848] DEBUG -- : Getting udev properties for device: sda
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.236614 #12848] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /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"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc788
Jul 28 00:30:37 node-5 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99934", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.236666 #12848] DEBUG -- : Trying to find out if device sda is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.236777 #12848] DEBUG -- : Device sda removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.236804 #12848] DEBUG -- : Device sda seems to be appropriate
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.237550 #12848] DEBUG -- : Getting udev properties for device: dm-0
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.240604 #12848] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-72jND81BOaxb4hjuK1Os9lDXkKPL4KjWxxeRNCefaIrlZiq0nwWPmBo4EDSxzYU5 /dev/disk/by-uuid/995ba5f5-ce40-4b00-a02e-01b144f7da19 /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "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-72jND81BOaxb4hjuK1Os9lDXkKPL4KjWxxeRNCefaIrlZiq0nwWPmBo4EDSxzYU5", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"995ba5f5-ce40-4b00-a02e-01b144f7da19", "ID_FS_UUID_ENC"=>"995ba5f5-ce40-4b00-a02e-01b144f7da19", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6
Jul 28 00:30:37 node-5 nailgun-agent: 5660", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.240651 #12848] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.240704 #12848] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.240730 #12848] DEBUG -- : Device dm-0 seems to be appropriate
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.240785 #12848] DEBUG -- : Getting udev properties for device: dm-1
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.243783 #12848] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-qFtTjv7H865m5TW7UNkh2SwumIZp0nZMq2cT3FsXtZudfLmfDqyjV0pEeNcXe364 /dev/disk/by-uuid/28ad82e1-25db-4634-96c3-20dd4fb8e6f5 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "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-qFtTjv7H865m5TW7UNkh2SwumIZp0nZMq2cT3FsXtZudfLmfDqyjV0pEeNcXe364", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"28ad82e1-25db-4634-96c3-20dd4fb8e6f5", "ID_FS_UUID_ENC"=>"28ad82e1-25db-4634-96c3-20dd4fb8e6f5", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"86638", "nomdmonddf"=>"1", "nom
Jul 28 00:30:37 node-5 nailgun-agent: dmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.243828 #12848] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.243964 #12848] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.243990 #12848] DEBUG -- : Device dm-1 seems to be appropriate
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.244031 #12848] DEBUG -- : Getting udev properties for device: dm-2
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.247380 #12848] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-eovMGFyMsdTc1D0uRvqSdBJtnmT2WcmURbgmwcxLTiGtz0UyXFngPtEtw8X35IeL /dev/disk/by-uuid/3eb860e5-72c5-42ce-b36b-4792bada7390 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "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-eovMGFyMsdTc1D0uRvqSdBJtnmT2WcmURbgmwcxLTiGtz0UyXFngPtEtw8X35IeL", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"3eb860e5-72c5-42ce-b36b-4792bada7390", "ID_FS_UUID_ENC"=>"3eb860e5-72c5-42ce-b36b-4792bada7390", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6
Jul 28 00:30:37 node-5 nailgun-agent: 446", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.247453 #12848] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.247540 #12848] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.247577 #12848] DEBUG -- : Device dm-2 seems to be appropriate
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.247657 #12848] DEBUG -- : Getting udev properties for device: dm-3
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.251044 #12848] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-8bhH7LFv2kFsgzFq7v6y70f30nYK6dALD0jjCiJUqNGiOGNP10AjGPln0RvdxqiB /dev/disk/by-uuid/23479241-bd6c-44d4-a455-3a7d5095ad73 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "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-8bhH7LFv2kFsgzFq7v6y70f30nYK6dALD0jjCiJUqNGiOGNP10AjGPln0RvdxqiB", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"23479241-bd6c-44d4-a455-3a7d5095ad73", "ID_FS_UUID_ENC"=>"23479241-bd6c-44d4-a455-3a7d5095ad73", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"18442", "nomdmon
Jul 28 00:30:37 node-5 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.251123 #12848] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.251280 #12848] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.251320 #12848] DEBUG -- : Device dm-3 seems to be appropriate
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.251362 #12848] DEBUG -- : Getting udev properties for device: dm-4
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.254682 #12848] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-EuBDq4GIrmZek0LyDRMvvMVJ18BRd1lKFogrYor2r7vp8evjAGXzhas8u27r9xie /dev/disk/by-uuid/4a34c6c0-83ad-4222-b24f-43055f5eecdc /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "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-EuBDq4GIrmZek0LyDRMvvMVJ18BRd1lKFogrYor2r7vp8evjAGXzhas8u27r9xie", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4a34c6c0-83ad-4222-b24f-43055f5eecdc", "ID_FS_UUID_ENC"=>"4a34c6c0-83ad-4222-b24f-43055f5eecdc", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33221", "nomdmonddf"=>"1",
Jul 28 00:30:37 node-5 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.254733 #12848] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.254819 #12848] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.254846 #12848] DEBUG -- : Device dm-4 seems to be appropriate
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.254874 #12848] DEBUG -- : Getting udev properties for device: dm-5
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.257940 #12848] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-5CUejDIpWaqRd4LqaK0Fv4Vxq9JqdjyrlSlrqDw9W5TQPckFgCyxPrrNjxFNdfDy /dev/disk/by-uuid/41e3acd0-3f1e-4ee9-b750-24d053a307c1 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "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-5CUejDIpWaqRd4LqaK0Fv4Vxq9JqdjyrlSlrqDw9W5TQPckFgCyxPrrNjxFNdfDy", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"41e3acd0-3f1e-4ee9-b750-24d053a307c1", "ID_FS_UUID_ENC"=>"41e3acd0-3f1e-4ee9-b750-24d053a307c1", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"40372", "nomdmonddf"=>"1", "nom
Jul 28 00:30:37 node-5 nailgun-agent: dmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.257984 #12848] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.258061 #12848] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.258128 #12848] DEBUG -- : Device dm-5 seems to be appropriate
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.258156 #12848] DEBUG -- : Getting udev properties for device: dm-6
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.261387 #12848] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-5CUejDIpWaqRd4LqaK0Fv4Vxq9JqdjyrqLO4cEwsn5u6cboFeNDF557qpCyNNmNS /dev/disk/by-uuid/2176e4f5-58cd-4f6f-be12-eb8131be0431 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "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-5CUejDIpWaqRd4LqaK0Fv4Vxq9JqdjyrqLO4cEwsn5u6cboFeNDF557qpCyNNmNS", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"2176e4f5-58cd-4f6f-be12-eb8131be0431", "ID_FS_UUID_ENC"=>"2176e4f5-58cd-4f6f-be12-eb8131be0431", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"40827", "nomdmonddf"=>"1", "nomdmonisw
Jul 28 00:30:37 node-5 nailgun-agent: "=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.261460 #12848] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.261524 #12848] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.261552 #12848] DEBUG -- : Device dm-6 seems to be appropriate
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.261582 #12848] DEBUG -- : Getting udev properties for device: ram0
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.264825 #12848] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52412", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.264873 #12848] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.264942 #12848] DEBUG -- : Device ram0 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.265011 #12848] DEBUG -- : Getting udev properties for device: ram1
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.267944 #12848] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52627", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.267997 #12848] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.268061 #12848] DEBUG -- : Device ram1 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.268109 #12848] DEBUG -- : Getting udev properties for device: ram2
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.271460 #12848] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53290", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.271530 #12848] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.271628 #12848] DEBUG -- : Device ram2 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.271736 #12848] DEBUG -- : Getting udev properties for device: ram3
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.274973 #12848] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53325", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.275007 #12848] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.275059 #12848] DEBUG -- : Device ram3 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.275087 #12848] DEBUG -- : Getting udev properties for device: ram4
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.278196 #12848] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53455", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.278245 #12848] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.278324 #12848] DEBUG -- : Device ram4 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.278379 #12848] DEBUG -- : Getting udev properties for device: ram5
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.281530 #12848] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53569", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.281582 #12848] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.281676 #12848] DEBUG -- : Device ram5 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.281752 #12848] DEBUG -- : Getting udev properties for device: ram6
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.284767 #12848] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53660", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.284854 #12848] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.284949 #12848] DEBUG -- : Device ram6 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.285032 #12848] DEBUG -- : Getting udev properties for device: ram7
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.287932 #12848] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53825", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.287978 #12848] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.288097 #12848] DEBUG -- : Device ram7 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.288178 #12848] DEBUG -- : Getting udev properties for device: ram8
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.291170 #12848] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53991", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.291207 #12848] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.291281 #12848] DEBUG -- : Device ram8 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.291307 #12848] DEBUG -- : Getting udev properties for device: ram9
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.294145 #12848] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"54034", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.294189 #12848] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.294263 #12848] DEBUG -- : Device ram9 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.294356 #12848] DEBUG -- : Getting udev properties for device: loop0
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.297260 #12848] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51527", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.297344 #12848] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.297421 #12848] DEBUG -- : Device loop0 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.297480 #12848] DEBUG -- : Getting udev properties for device: loop1
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.300467 #12848] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51619", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.300539 #12848] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.300608 #12848] DEBUG -- : Device loop1 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.300696 #12848] DEBUG -- : Getting udev properties for device: loop2
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.303600 #12848] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51680", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.303636 #12848] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.303682 #12848] DEBUG -- : Device loop2 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.303729 #12848] DEBUG -- : Getting udev properties for device: loop3
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.306623 #12848] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51762", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.306683 #12848] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.306739 #12848] DEBUG -- : Device loop3 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.306767 #12848] DEBUG -- : Getting udev properties for device: loop4
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.309730 #12848] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51876", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.309805 #12848] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.309898 #12848] DEBUG -- : Device loop4 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.309989 #12848] DEBUG -- : Getting udev properties for device: loop5
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.313144 #12848] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"51981", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.313214 #12848] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.313314 #12848] DEBUG -- : Device loop5 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.313388 #12848] DEBUG -- : Getting udev properties for device: loop6
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.316505 #12848] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52292", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.316563 #12848] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.316664 #12848] DEBUG -- : Device loop6 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.316714 #12848] DEBUG -- : Getting udev properties for device: loop7
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.326818 #12848] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52401", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.326858 #12848] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.326912 #12848] DEBUG -- : Device loop7 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.326938 #12848] DEBUG -- : Getting udev properties for device: ram10
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.330797 #12848] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52854", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.330826 #12848] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.330875 #12848] DEBUG -- : Device ram10 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.330900 #12848] DEBUG -- : Getting udev properties for device: ram11
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.334764 #12848] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52974", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.334793 #12848] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.334884 #12848] DEBUG -- : Device ram11 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.334933 #12848] DEBUG -- : Getting udev properties for device: ram12
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.338882 #12848] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53026", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.338928 #12848] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.338991 #12848] DEBUG -- : Device ram12 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.339025 #12848] DEBUG -- : Getting udev properties for device: ram13
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.341644 #12848] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53159", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.341679 #12848] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.341781 #12848] DEBUG -- : Device ram13 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.341809 #12848] DEBUG -- : Getting udev properties for device: ram14
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.344462 #12848] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53188", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.344503 #12848] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.344555 #12848] DEBUG -- : Device ram14 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.344641 #12848] DEBUG -- : Getting udev properties for device: ram15
Jul 28 00:30:37 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347221 #12848] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"53239", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347256 #12848] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347298 #12848] DEBUG -- : Device ram15 removable parameter: "0"
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347348 #12848] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347368 #12848] DEBUG -- : Block device seems to be physical data storage: sda
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347474 #12848] DEBUG -- : Found block device: dm-0
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347509 #12848] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347531 #12848] DEBUG -- : Found block device: dm-1
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347548 #12848] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347569 #12848] DEBUG -- : Found block device: dm-2
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347587 #12848] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347601 #12848] DEBUG -- : Found block device: dm-3
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347617 #12848] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347631 #12848] DEBUG -- : Found block device: dm-4
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347723 #12848] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347739 #12848] DEBUG -- : Found block device: dm-5
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347757 #12848] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347771 #12848] DEBUG -- : Found block device: dm-6
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347787 #12848] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347802 #12848] DEBUG -- : Found block device: ram0
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347819 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347833 #12848] DEBUG -- : Found block device: ram1
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347849 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347863 #12848] DEBUG -- : Found block device: ram2
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347937 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347953 #12848] DEBUG -- : Found block device: ram3
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347972 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.347985 #12848] DEBUG -- : Found block device: ram4
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348001 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348025 #12848] DEBUG -- : Found block device: ram5
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348044 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348058 #12848] DEBUG -- : Found block device: ram6
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348073 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348152 #12848] DEBUG -- : Found block device: ram7
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348170 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348184 #12848] DEBUG -- : Found block device: ram8
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348201 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348215 #12848] DEBUG -- : Found block device: ram9
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348231 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348245 #12848] DEBUG -- : Found block device: loop0
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348264 #12848] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348278 #12848] DEBUG -- : Found block device: loop1
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348366 #12848] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348382 #12848] DEBUG -- : Found block device: loop2
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348400 #12848] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348413 #12848] DEBUG -- : Found block device: loop3
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348429 #12848] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348444 #12848] DEBUG -- : Found block device: loop4
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348460 #12848] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348474 #12848] DEBUG -- : Found block device: loop5
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348490 #12848] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348582 #12848] DEBUG -- : Found block device: loop6
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348601 #12848] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348615 #12848] DEBUG -- : Found block device: loop7
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348631 #12848] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348645 #12848] DEBUG -- : Found block device: ram10
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348660 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348673 #12848] DEBUG -- : Found block device: ram11
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348691 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348705 #12848] DEBUG -- : Found block device: ram12
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348790 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348805 #12848] DEBUG -- : Found block device: ram13
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348822 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348836 #12848] DEBUG -- : Found block device: ram14
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348852 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348865 #12848] DEBUG -- : Found block device: ram15
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348879 #12848] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.348926 #12848] 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-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 28 00:30:37 node-5 nailgun-agent: D, [2016-07-28T00:30:37.631229 #12848] DEBUG -- : Response: status: 200 body: {"id": 5}
Jul 28 00:30:37 node-5 nailgun-agent: I, [2016-07-28T00:30:37.631662 #12848]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 28 00:31:01 node-5 CRON[16990]: (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 28 00:31:07 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 00:31:07 node-5 nailgun-agent: I, [2016-07-28T00:31:07.817362 #16993]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 00:31:10 node-5 puppet-user[15007]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 28 00:31:10 node-5 puppet-user[15007]: Finished catalog run in 40.47 seconds
Jul 28 00:31:12 node-5 puppet-user[17907]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 28 00:31:13 node-5 puppet-user[17907]: Compiled catalog for node-5.domain.tld in environment production in 0.58 seconds
Jul 28 00:31:13 node-5 puppet-user[17907]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 28 00:31:13 node-5 puppet-user[17907]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 28 00:31:13 node-5 puppet-user[17907]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 28 00:31:13 node-5 puppet-user[17907]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 28 00:31:13 node-5 puppet-user[17907]: Finished catalog run in 0.09 seconds
Jul 28 00:31:15 node-5 puppet-user[18377]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 28 00:31:16 node-5 puppet-user[18377]: Compiled catalog for node-5.domain.tld in environment production in 1.00 seconds
Jul 28 00:31:16 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 28 00:31:16 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 28 00:31:16 node-5 crontab[18834]: (root) LIST (root)
Jul 28 00:31:16 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 28 00:31:16 node-5 crontab[18835]: (root) REPLACE (root)
Jul 28 00:31:18 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 28 00:31:20 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/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 28 00:31:20 node-5 puppet-user[18377]: (/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 28 00:31:20 node-5 nailgun-agent: I, [2016-07-28T00:31:20.823456 #16993]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/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 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 28 00:31:20 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/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 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/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 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/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 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/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 28 00:31:21 node-5 puppet-user[18377]: (/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 28 00:31:21 node-5 puppet-user[18377]: (/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 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/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 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/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 28 00:31:21 node-5 puppet-user[18377]: (/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 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 28 00:31:21 node-5 puppet-user[18377]: (/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 28 00:31:21 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8400" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 00:31:21 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 28 00:31:23 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:23 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:23 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:23 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:23 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:23 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:44 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:44 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:44 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:44 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:44 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:31:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:32:49 node-5 ntpdate[29975]: no servers can be used, exiting
<27>Jul 28 00:32:49 node-5 ntpdate[30067]: no servers can be used, exiting
<27>Jul 28 00:33:21 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:21 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:21 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:21 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:21 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:24 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:24 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:24 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:24 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:24 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:24 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:36 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:36 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:36 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:36 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:36 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:46 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:46 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:46 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:46 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:46 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:46 node-5 multipathd: uevent trigger error
<27>Jul 28 00:33:46 node-5 multipathd: uevent trigger error
<27>Jul 28 00:34:30 node-5 multipathd: uevent trigger error
<27>Jul 28 00:34:30 node-5 multipathd: uevent trigger error
<27>Jul 28 00:34:30 node-5 multipathd: uevent trigger error
<27>Jul 28 00:34:30 node-5 multipathd: uevent trigger error
<27>Jul 28 00:34:30 node-5 multipathd: uevent trigger error
<43>Jul 28 00:34:52 node-5 apache2_error [Thu Jul 28 00:34:44.544594 2016] [mpm_event:notice] [pid 10592:tid 140464970033024] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 00:34:52 node-5 apache2_error [Thu Jul 28 00:34:44.544732 2016] [core:notice] [pid 10592:tid 140464970033024] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 00:34:52 node-5 apache2_error [Thu Jul 28 00:34:47.867378 2016] [mpm_event:notice] [pid 10592:tid 140464970033024] AH00491: caught SIGTERM, shutting down
<43>Jul 28 00:34:52 node-5 apache2_error [Thu Jul 28 00:34:48.955881 2016] [mpm_worker:notice] [pid 10907:tid 139998118139776] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 00:34:52 node-5 apache2_error [Thu Jul 28 00:34:48.955919 2016] [core:notice] [pid 10907:tid 139998118139776] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 00:34:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:34:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:34:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:34:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:34:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:33 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 28 00:35:37 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:37 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:37 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:37 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:37 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:48 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:48 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:48 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:49 node-5 ntpdate[19671]: the NTP socket is in use, exiting
<27>Jul 28 00:35:56 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:56 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:56 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:56 node-5 multipathd: uevent trigger error
<27>Jul 28 00:35:56 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:01 node-5 haproxy[21776]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:01 node-5 haproxy[21776]: proxy odl-jetty has no server available!
<27>Jul 28 00:36:01 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:01 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:01 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:01 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:01 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:01 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:03 node-5 haproxy[21776]: Server odl-neutron-endpoint/node-2 is DOWN, reason: Layer4 timeout, check duration: 5002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:03 node-5 haproxy[21776]: proxy odl-neutron-endpoint has no server available!
<129>Jul 28 00:36:04 node-5 haproxy[22989]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:36:07 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:07 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:07 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:07 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:07 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:07 node-5 haproxy[22993]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:07 node-5 haproxy[22993]: proxy odl-jetty has no server available!
<27>Jul 28 00:36:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:10 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:12 node-5 haproxy[22993]: Server odl-neutron-endpoint/node-2 is DOWN, reason: Layer4 timeout, check duration: 5002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:12 node-5 haproxy[22993]: proxy odl-neutron-endpoint has no server available!
<129>Jul 28 00:36:13 node-5 haproxy[25269]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:14 node-5 haproxy[25269]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:36:15 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:15 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:15 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:15 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:16 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:16 node-5 haproxy[25269]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:16 node-5 haproxy[25269]: proxy odl-jetty has no server available!
<129>Jul 28 00:36:18 node-5 haproxy[26481]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:19 node-5 haproxy[26485]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:19 node-5 haproxy[26485]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:36:21 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:21 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:21 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:21 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:21 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:21 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:22 node-5 haproxy[26485]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:22 node-5 haproxy[26485]: proxy odl-jetty has no server available!
<129>Jul 28 00:36:23 node-5 haproxy[27843]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:24 node-5 haproxy[27847]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:24 node-5 haproxy[27847]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:24 node-5 haproxy[27847]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:25 node-5 haproxy[27847]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:36:26 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:26 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:26 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:26 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:26 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:26 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:26 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:27 node-5 haproxy[27847]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:27 node-5 haproxy[27847]: proxy odl-jetty has no server available!
<129>Jul 28 00:36:29 node-5 haproxy[29065]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:29 node-5 haproxy[29065]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:29 node-5 haproxy[29065]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:30 node-5 haproxy[29065]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:30 node-5 haproxy[29065]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:30 node-5 haproxy[29065]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:36:31 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:31 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:31 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:31 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:31 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:32 node-5 haproxy[29065]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:32 node-5 haproxy[29065]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:32 node-5 haproxy[29065]: proxy aodh has no server available!
<129>Jul 28 00:36:32 node-5 haproxy[29065]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:32 node-5 haproxy[29065]: proxy odl-jetty has no server available!
<129>Jul 28 00:36:34 node-5 haproxy[30272]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:34 node-5 haproxy[30272]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:34 node-5 haproxy[30272]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:35 node-5 haproxy[30276]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:35 node-5 haproxy[30276]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:35 node-5 haproxy[30276]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:35 node-5 haproxy[30276]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:36:37 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:37 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:37 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:37 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:37 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:37 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:37 node-5 haproxy[30276]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:37 node-5 haproxy[30276]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:37 node-5 haproxy[30276]: proxy aodh has no server available!
<129>Jul 28 00:36:37 node-5 haproxy[30276]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:37 node-5 haproxy[30276]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:37 node-5 haproxy[30276]: proxy ceilometer has no server available!
<129>Jul 28 00:36:38 node-5 haproxy[30276]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:38 node-5 haproxy[30276]: proxy odl-jetty has no server available!
<129>Jul 28 00:36:39 node-5 haproxy[31644]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:39 node-5 haproxy[31644]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:40 node-5 haproxy[31648]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:40 node-5 haproxy[31648]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:40 node-5 haproxy[31648]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:40 node-5 haproxy[31648]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:41 node-5 haproxy[31648]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:36:42 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:42 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:42 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:42 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:42 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:42 node-5 haproxy[31648]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:42 node-5 haproxy[31648]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:42 node-5 haproxy[31648]: proxy aodh has no server available!
<129>Jul 28 00:36:42 node-5 haproxy[31648]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:43 node-5 haproxy[31648]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:43 node-5 haproxy[31648]: proxy ceilometer has no server available!
<129>Jul 28 00:36:43 node-5 haproxy[31648]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:43 node-5 haproxy[31648]: proxy odl-jetty has no server available!
<129>Jul 28 00:36:45 node-5 haproxy[379]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:45 node-5 haproxy[379]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:45 node-5 haproxy[379]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:45 node-5 haproxy[379]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:46 node-5 haproxy[379]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:46 node-5 haproxy[379]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:46 node-5 haproxy[379]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:46 node-5 haproxy[379]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:46 node-5 haproxy[379]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:36:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:47 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:48 node-5 haproxy[379]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:48 node-5 haproxy[379]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:48 node-5 haproxy[379]: proxy aodh has no server available!
<129>Jul 28 00:36:48 node-5 haproxy[379]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:48 node-5 haproxy[379]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:48 node-5 haproxy[379]: proxy ceilometer has no server available!
<129>Jul 28 00:36:48 node-5 haproxy[379]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:48 node-5 haproxy[379]: proxy odl-jetty has no server available!
<129>Jul 28 00:36:50 node-5 haproxy[1664]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:50 node-5 haproxy[1664]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:51 node-5 haproxy[1670]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:51 node-5 haproxy[1670]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:51 node-5 haproxy[1670]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:51 node-5 haproxy[1670]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:51 node-5 haproxy[1670]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:51 node-5 haproxy[1670]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:52 node-5 haproxy[1670]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:52 node-5 haproxy[1670]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:52 node-5 haproxy[1670]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:52 node-5 haproxy[1670]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:53 node-5 haproxy[1670]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:36:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:53 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:53 node-5 haproxy[1670]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:53 node-5 haproxy[1670]: proxy glance-registry has no server available!
<129>Jul 28 00:36:54 node-5 haproxy[1670]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:54 node-5 haproxy[1670]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:54 node-5 haproxy[1670]: proxy aodh has no server available!
<129>Jul 28 00:36:54 node-5 haproxy[1670]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:54 node-5 haproxy[1670]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:54 node-5 haproxy[1670]: proxy ceilometer has no server available!
<129>Jul 28 00:36:54 node-5 haproxy[1670]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:54 node-5 haproxy[1670]: proxy odl-jetty has no server available!
<129>Jul 28 00:36:56 node-5 haproxy[2922]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:56 node-5 haproxy[2922]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:56 node-5 haproxy[2922]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:57 node-5 haproxy[2926]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:57 node-5 haproxy[2926]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:57 node-5 haproxy[2926]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:57 node-5 haproxy[2926]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:57 node-5 haproxy[2926]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:57 node-5 haproxy[2926]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:57 node-5 haproxy[2926]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:57 node-5 haproxy[2926]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:58 node-5 haproxy[2926]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:58 node-5 haproxy[2926]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:58 node-5 haproxy[2926]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:58 node-5 haproxy[2926]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:36:59 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:59 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:59 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:59 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:59 node-5 multipathd: uevent trigger error
<27>Jul 28 00:36:59 node-5 multipathd: uevent trigger error
<129>Jul 28 00:36:59 node-5 haproxy[2926]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:59 node-5 haproxy[2926]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:59 node-5 haproxy[2926]: proxy glance-registry has no server available!
<129>Jul 28 00:36:59 node-5 haproxy[2926]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:36:59 node-5 haproxy[2926]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:36:59 node-5 haproxy[2926]: proxy aodh has no server available!
<129>Jul 28 00:37:00 node-5 haproxy[2926]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:00 node-5 haproxy[2926]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:00 node-5 haproxy[2926]: proxy ceilometer has no server available!
<129>Jul 28 00:37:00 node-5 haproxy[2926]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:00 node-5 haproxy[2926]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:00 node-5 haproxy[2926]: proxy nova-novncproxy has no server available!
<129>Jul 28 00:37:00 node-5 haproxy[2926]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:00 node-5 haproxy[2926]: proxy odl-jetty has no server available!
<129>Jul 28 00:37:02 node-5 haproxy[4150]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:02 node-5 haproxy[4150]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:02 node-5 haproxy[4150]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:02 node-5 haproxy[4150]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:02 node-5 haproxy[4150]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:02 node-5 haproxy[4150]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:02 node-5 haproxy[4150]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:02 node-5 haproxy[4150]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:03 node-5 haproxy[4150]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:03 node-5 haproxy[4150]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:03 node-5 haproxy[4150]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:03 node-5 haproxy[4150]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:03 node-5 haproxy[4150]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:03 node-5 haproxy[4150]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:03 node-5 haproxy[4150]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:03 node-5 haproxy[4150]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 28 00:37:04 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:04 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:04 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:04 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:04 node-5 multipathd: uevent trigger error
<129>Jul 28 00:37:04 node-5 haproxy[4150]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:04 node-5 haproxy[4150]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:04 node-5 haproxy[4150]: proxy glance-registry has no server available!
<129>Jul 28 00:37:05 node-5 haproxy[4150]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:05 node-5 haproxy[4150]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:05 node-5 haproxy[4150]: proxy aodh has no server available!
<129>Jul 28 00:37:05 node-5 haproxy[4150]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:05 node-5 haproxy[4150]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:05 node-5 haproxy[4150]: proxy ceilometer has no server available!
<129>Jul 28 00:37:05 node-5 haproxy[4150]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:05 node-5 haproxy[4150]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:05 node-5 haproxy[4150]: proxy nova-novncproxy has no server available!
<129>Jul 28 00:37:05 node-5 haproxy[4150]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:05 node-5 haproxy[4150]: proxy odl-jetty has no server available!
<129>Jul 28 00:37:07 node-5 haproxy[5432]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:07 node-5 haproxy[5432]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:08 node-5 haproxy[5436]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:08 node-5 haproxy[5436]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:08 node-5 haproxy[5436]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:08 node-5 haproxy[5436]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:08 node-5 haproxy[5436]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:08 node-5 haproxy[5436]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:08 node-5 haproxy[5436]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:08 node-5 haproxy[5436]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:08 node-5 haproxy[5436]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:09 node-5 haproxy[5436]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:09 node-5 haproxy[5436]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:09 node-5 haproxy[5436]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:09 node-5 haproxy[5436]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:09 node-5 haproxy[5436]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:09 node-5 haproxy[5436]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:09 node-5 haproxy[5436]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:09 node-5 haproxy[5436]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:10 node-5 haproxy[5436]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:10 node-5 haproxy[5436]: Server glance-registry/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:10 node-5 haproxy[5436]: proxy glance-registry has no server available!
<27>Jul 28 00:37:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:10 node-5 multipathd: uevent trigger error
<129>Jul 28 00:37:10 node-5 haproxy[5436]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:10 node-5 haproxy[5436]: Server aodh/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:10 node-5 haproxy[5436]: proxy aodh has no server available!
<129>Jul 28 00:37:11 node-5 haproxy[5436]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:11 node-5 haproxy[5436]: Server ceilometer/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:11 node-5 haproxy[5436]: proxy ceilometer has no server available!
<129>Jul 28 00:37:11 node-5 haproxy[5436]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:11 node-5 haproxy[5436]: Server nova-novncproxy/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:11 node-5 haproxy[5436]: proxy nova-novncproxy has no server available!
<129>Jul 28 00:37:11 node-5 haproxy[5436]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:11 node-5 haproxy[5436]: proxy odl-jetty has no server available!
<27>Jul 28 00:37:13 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:13 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:13 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:13 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:14 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:14 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:14 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:17 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:17 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:17 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:17 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:17 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:17 node-5 multipathd: uevent trigger error
<129>Jul 28 00:37:17 node-5 haproxy[5436]: Server odl-neutron-endpoint/node-2 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:17 node-5 haproxy[5436]: proxy odl-neutron-endpoint has no server available!
<129>Jul 28 00:37:17 node-5 haproxy[5436]: Server keystone-1/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:17 node-5 haproxy[5436]: Server keystone-1/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:17 node-5 haproxy[5436]: proxy keystone-1 has no server available!
<129>Jul 28 00:37:17 node-5 haproxy[5436]: Server keystone-2/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:17 node-5 haproxy[5436]: Server keystone-2/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:17 node-5 haproxy[5436]: proxy keystone-2 has no server available!
<129>Jul 28 00:37:17 node-5 haproxy[5436]: Server nova-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server nova-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:18 node-5 haproxy[5436]: proxy nova-api has no server available!
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server nova-metadata-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:18 node-5 haproxy[5436]: proxy nova-metadata-api has no server available!
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server cinder-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Backup Server cinder-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:18 node-5 haproxy[5436]: proxy cinder-api has no server available!
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server glance-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server glance-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:18 node-5 haproxy[5436]: proxy glance-api has no server available!
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server glance-glare/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server glance-glare/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:18 node-5 haproxy[5436]: proxy glance-glare has no server available!
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server neutron/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server neutron/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:18 node-5 haproxy[5436]: proxy neutron has no server available!
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:18 node-5 haproxy[5436]: proxy mysqld has no server available!
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server object-storage/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:18 node-5 haproxy[5436]: Server object-storage/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:18 node-5 haproxy[5436]: proxy object-storage has no server available!
<129>Jul 28 00:37:19 node-5 haproxy[5436]: Server heat-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:19 node-5 haproxy[5436]: Server heat-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:19 node-5 haproxy[5436]: proxy heat-api has no server available!
<129>Jul 28 00:37:19 node-5 haproxy[5436]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:19 node-5 haproxy[5436]: Server heat-api-cfn/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:19 node-5 haproxy[5436]: proxy heat-api-cfn has no server available!
<129>Jul 28 00:37:19 node-5 haproxy[5436]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 00:37:19 node-5 haproxy[5436]: Server heat-api-cloudwatch/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 00:37:19 node-5 haproxy[5436]: proxy heat-api-cloudwatch has no server available!
<27>Jul 28 00:37:26 node-5 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 00:37:49 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<43>Jul 28 00:37:52 node-5 apache2_error [Thu Jul 28 00:37:50.997651 2016] [mpm_worker:notice] [pid 10907:tid 139998118139776] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 00:37:52 node-5 apache2_error [Thu Jul 28 00:37:51.003505 2016] [mpm_worker:warn] [pid 10907:tid 139998118139776] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 00:37:52 node-5 apache2_error [Thu Jul 28 00:37:51.003844 2016] [mpm_worker:notice] [pid 10907:tid 139998118139776] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 00:37:52 node-5 apache2_error [Thu Jul 28 00:37:51.003850 2016] [core:notice] [pid 10907:tid 139998118139776] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 00:37:54 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:54 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:54 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:54 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:54 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:37:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:02 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:02 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:02 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:02 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:02 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:02 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:24 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:38 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 28 00:38:38 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 28 00:38:44 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:44 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:44 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:44 node-5 multipathd: uevent trigger error
<27>Jul 28 00:38:44 node-5 multipathd: uevent trigger error
<27>Jul 28 00:39:04 node-5 multipathd: uevent trigger error
<27>Jul 28 00:39:04 node-5 multipathd: uevent trigger error
<27>Jul 28 00:39:04 node-5 multipathd: uevent trigger error
<27>Jul 28 00:39:04 node-5 multipathd: uevent trigger error
<27>Jul 28 00:39:04 node-5 multipathd: uevent trigger error
<27>Jul 28 00:39:11 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 28 00:40:14 node-5 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 28 00:40:16 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 28 00:41:32 node-5 multipathd: uevent trigger error
<27>Jul 28 00:41:32 node-5 multipathd: uevent trigger error
<27>Jul 28 00:41:32 node-5 multipathd: uevent trigger error
<27>Jul 28 00:41:32 node-5 multipathd: uevent trigger error
<27>Jul 28 00:41:32 node-5 multipathd: uevent trigger error
<27>Jul 28 00:44:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:44:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:44:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:44:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:44:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:44:40 node-5 multipathd: uevent trigger error
<43>Jul 28 00:46:02 node-5 apache2_error [Thu Jul 28 00:46:02.154659 2016] [mpm_worker:notice] [pid 10907:tid 139998118139776] AH00295: caught SIGTERM, shutting down
<43>Jul 28 00:46:02 node-5 apache2_error [Thu Jul 28 00:46:02.902360 2016] [mpm_worker:notice] [pid 18244:tid 139815836641152] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 00:46:02 node-5 apache2_error [Thu Jul 28 00:46:02.902386 2016] [core:notice] [pid 18244:tid 139815836641152] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 00:46:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:46:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:46:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:46:40 node-5 multipathd: uevent trigger error
<27>Jul 28 00:46:40 node-5 multipathd: uevent trigger error
<43>Jul 28 00:46:42 node-5 apache2_error [Thu Jul 28 00:46:34.802648 2016] [mpm_worker:notice] [pid 18244:tid 139815836641152] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 00:46:42 node-5 apache2_error [Thu Jul 28 00:46:34.812680 2016] [mpm_worker:warn] [pid 18244:tid 139815836641152] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 00:46:42 node-5 apache2_error [Thu Jul 28 00:46:34.821010 2016] [mpm_worker:notice] [pid 18244:tid 139815836641152] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 00:46:42 node-5 apache2_error [Thu Jul 28 00:46:34.821038 2016] [core:notice] [pid 18244:tid 139815836641152] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 00:47:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:47:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:47:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:47:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:47:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:47:41 node-5 multipathd: uevent trigger error
<27>Jul 28 00:48:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:48:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:48:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:48:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:48:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:48:58 node-5 multipathd: uevent trigger error
<27>Jul 28 00:52:48 node-5 multipathd: uevent trigger error
<27>Jul 28 00:52:48 node-5 multipathd: uevent trigger error
<27>Jul 28 00:52:48 node-5 multipathd: uevent trigger error
<27>Jul 28 00:52:48 node-5 multipathd: uevent trigger error
<27>Jul 28 00:52:48 node-5 multipathd: uevent trigger error
<27>Jul 28 00:52:48 node-5 multipathd: uevent trigger error
<27>Jul 28 00:54:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:54:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:54:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:54:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:54:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:54:53 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:00 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:00 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:00 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:00 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:00 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:38 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:38 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:38 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:38 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:38 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:38 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:38 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:47 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:52 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:52 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:52 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:52 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:52 node-5 multipathd: uevent trigger error
<27>Jul 28 00:56:52 node-5 multipathd: uevent trigger error
<43>Jul 28 00:57:43 node-5 apache2_error [Thu Jul 28 00:57:43.473770 2016] [mpm_worker:notice] [pid 18244:tid 139815836641152] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 00:57:53 node-5 apache2_error [Thu Jul 28 00:57:43.859109 2016] [mpm_worker:warn] [pid 18244:tid 139815836641152] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 00:57:53 node-5 apache2_error [Thu Jul 28 00:57:43.865003 2016] [mpm_worker:notice] [pid 18244:tid 139815836641152] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 00:57:53 node-5 apache2_error [Thu Jul 28 00:57:43.865042 2016] [core:notice] [pid 18244:tid 139815836641152] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 00:58:23 node-5 apache2_error [Thu Jul 28 00:58:20.872111 2016] [mpm_worker:notice] [pid 18244:tid 139815836641152] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 00:58:23 node-5 apache2_error [Thu Jul 28 00:58:21.254084 2016] [mpm_worker:warn] [pid 18244:tid 139815836641152] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 00:58:23 node-5 apache2_error [Thu Jul 28 00:58:21.262413 2016] [mpm_worker:notice] [pid 18244:tid 139815836641152] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 00:58:23 node-5 apache2_error [Thu Jul 28 00:58:21.262444 2016] [core:notice] [pid 18244:tid 139815836641152] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 00:58:25 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:25 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:25 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:25 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:25 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:25 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:43 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:43 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:43 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:43 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:43 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:43 node-5 multipathd: uevent trigger error
<27>Jul 28 00:58:43 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:10 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:20 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:20 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:20 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:20 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:20 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:25 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:25 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:25 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:25 node-5 multipathd: uevent trigger error
<27>Jul 28 00:59:25 node-5 multipathd: uevent trigger error
<27>Jul 28 01:00:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:00:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:00:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:00:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:00:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:00:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:01:36 node-5 multipathd: uevent trigger error
<27>Jul 28 01:01:36 node-5 multipathd: uevent trigger error
<27>Jul 28 01:01:36 node-5 multipathd: uevent trigger error
<27>Jul 28 01:01:36 node-5 multipathd: uevent trigger error
<27>Jul 28 01:01:36 node-5 multipathd: uevent trigger error
<27>Jul 28 01:01:52 node-5 multipathd: uevent trigger error
<27>Jul 28 01:01:52 node-5 multipathd: uevent trigger error
<27>Jul 28 01:01:52 node-5 multipathd: uevent trigger error
<27>Jul 28 01:01:52 node-5 multipathd: uevent trigger error
<27>Jul 28 01:01:52 node-5 multipathd: uevent trigger error
<11>Jul 28 01:02:02 node-5 liberasurecode[7173]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:02 node-5 liberasurecode[7173]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:02 node-5 liberasurecode[7173]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:02 node-5 liberasurecode[7173]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:02 node-5 liberasurecode[7202]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:02 node-5 liberasurecode[7202]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:02 node-5 liberasurecode[7202]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:02 node-5 liberasurecode[7202]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:04 node-5 liberasurecode[7601]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:04 node-5 liberasurecode[7601]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:04 node-5 liberasurecode[7601]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:04 node-5 liberasurecode[7601]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:09 node-5 liberasurecode[8746]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:09 node-5 liberasurecode[8746]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:09 node-5 liberasurecode[8746]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:09 node-5 liberasurecode[8746]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:09 node-5 liberasurecode[8872]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:09 node-5 liberasurecode[8872]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:09 node-5 liberasurecode[8872]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:09 node-5 liberasurecode[8872]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9035]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9035]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9035]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9035]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9306]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9306]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9306]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9306]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9318]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9318]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9318]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9318]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9349]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9349]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9349]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9349]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9333]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9333]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9333]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:02:10 node-5 liberasurecode[9333]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 01:02:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:02:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:02:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:02:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:02:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:02:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:02:21 node-5 multipathd: uevent trigger error
<27>Jul 28 01:02:21 node-5 multipathd: uevent trigger error
<27>Jul 28 01:02:21 node-5 multipathd: uevent trigger error
<27>Jul 28 01:02:21 node-5 multipathd: uevent trigger error
<27>Jul 28 01:02:21 node-5 multipathd: uevent trigger error
<27>Jul 28 01:03:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:03:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:03:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:03:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:03:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:03:30 node-5 multipathd: uevent trigger error
<11>Jul 28 01:05:02 node-5 liberasurecode[2553]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:05:02 node-5 liberasurecode[2553]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:05:02 node-5 liberasurecode[2553]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 01:05:02 node-5 liberasurecode[2553]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 01:05:29 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:29 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:34 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:34 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:34 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:34 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:34 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:47 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:52 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:52 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:52 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:52 node-5 multipathd: uevent trigger error
<27>Jul 28 01:05:52 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:05 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:05 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:05 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:05 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:05 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:12 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:12 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:12 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:12 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:12 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:12 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:12 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:16 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:20 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:20 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:20 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:20 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:20 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:20 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:24 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:25 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:25 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:25 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:25 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:29 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:29 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:30 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:34 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:34 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:34 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:34 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:34 node-5 multipathd: uevent trigger error
<27>Jul 28 01:06:45 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 01:06:45 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
