Jul 23 16:38:47 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8408" x-info="http://www.rsyslog.com"] start
Jul 23 16:38:47 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 23 16:38:47 node-5 rsyslogd: rsyslogd's groupid changed to 104
Jul 23 16:38:47 node-5 rsyslogd: rsyslogd's userid changed to 101
Jul 23 16:38:47 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 23 16:38:47 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 23 16:38:47 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 23 16:38:47 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 23 16:38:47 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=3ede14ae-128c-44eb-9b83-0af5a649e292 nomdmonddf nomdmonisw
Jul 23 16:38:47 node-5 kernel: [    0.000000] KERNEL supported cpus:
Jul 23 16:38:47 node-5 kernel: [    0.000000]   Intel GenuineIntel
Jul 23 16:38:47 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Jul 23 16:38:47 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Jul 23 16:38:47 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 23 16:38:47 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 23 16:38:47 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 23 16:38:47 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 23 16:38:47 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 23 16:38:47 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 23 16:38:47 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 23 16:38:47 node-5 kernel: [    0.000000] No AGP bridge found
Jul 23 16:38:47 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 23 16:38:47 node-5 kernel: [    0.000000] MTRR default type: write-back
Jul 23 16:38:47 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 23 16:38:47 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Jul 23 16:38:47 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 23 16:38:47 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 23 16:38:47 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 23 16:38:47 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 23 16:38:47 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 23 16:38:47 node-5 kernel: [    0.000000]   2 disabled
Jul 23 16:38:47 node-5 kernel: [    0.000000]   3 disabled
Jul 23 16:38:47 node-5 kernel: [    0.000000]   4 disabled
Jul 23 16:38:47 node-5 kernel: [    0.000000]   5 disabled
Jul 23 16:38:47 node-5 kernel: [    0.000000]   6 disabled
Jul 23 16:38:47 node-5 kernel: [    0.000000]   7 disabled
Jul 23 16:38:47 node-5 kernel: [    0.000000]   8 disabled
Jul 23 16:38:47 node-5 kernel: [    0.000000]   9 disabled
Jul 23 16:38:47 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 23 16:38:47 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 23 16:38:47 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 23 16:38:47 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 23 16:38:47 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 23 16:38:47 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Jul 23 16:38:47 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 23 16:38:47 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 23 16:38:47 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 23 16:38:47 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 23 16:38:47 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 23 16:38:47 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 23 16:38:47 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 23 16:38:47 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 23 16:38:47 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 23 16:38:47 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 23 16:38:47 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 23 16:38:47 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 23 16:38:47 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 23 16:38:47 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 23 16:38:47 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 23 16:38:47 node-5 kernel: [    0.000000] Zone ranges:
Jul 23 16:38:47 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] Movable zone start for each node
Jul 23 16:38:47 node-5 kernel: [    0.000000] Early memory node ranges
Jul 23 16:38:47 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 23 16:38:47 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 23 16:38:47 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 23 16:38:47 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 23 16:38:47 node-5 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 23 16:38:47 node-5 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 23 16:38:47 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 23 16:38:47 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 23 16:38:47 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 23 16:38:47 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 23 16:38:47 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 23 16:38:47 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 23 16:38:47 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 23 16:38:47 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 23 16:38:47 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 23 16:38:47 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 23 16:38:47 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 23 16:38:47 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 23 16:38:47 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 23 16:38:47 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 23 16:38:47 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 23 16:38:47 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 23 16:38:47 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 23 16:38:47 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 23 16:38:47 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 23 16:38:47 node-5 kernel: [    0.000000] Policy zone: Normal
Jul 23 16:38:47 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=3ede14ae-128c-44eb-9b83-0af5a649e292 nomdmonddf nomdmonisw
Jul 23 16:38:47 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 23 16:38:47 node-5 kernel: [    0.000000] Checking aperture...
Jul 23 16:38:47 node-5 kernel: [    0.000000] No AGP bridge found
Jul 23 16:38:47 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 23 16:38:47 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 23 16:38:47 node-5 kernel: [    0.000000] Memory: 32653320K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 23 16:38:47 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 23 16:38:47 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 23 16:38:47 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 23 16:38:47 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 23 16:38:47 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 23 16:38:47 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 23 16:38:47 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 23 16:38:47 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 23 16:38:47 node-5 kernel: [    0.000000] console [tty0] enabled
Jul 23 16:38:47 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 23 16:38:47 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 23 16:38:47 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 23 16:38:47 node-5 kernel: [    0.000000] hpet clockevent registered
Jul 23 16:38:47 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 23 16:38:47 node-5 kernel: [    0.004000] tsc: Detected 3491.833 MHz processor
Jul 23 16:38:47 node-5 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.66 BogoMIPS (lpj=13967332)
Jul 23 16:38:47 node-5 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 23 16:38:47 node-5 kernel: [    0.000047] Security Framework initialized
Jul 23 16:38:47 node-5 kernel: [    0.000065] AppArmor: AppArmor initialized
Jul 23 16:38:47 node-5 kernel: [    0.000067] Yama: becoming mindful.
Jul 23 16:38:47 node-5 kernel: [    0.001456] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.006293] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.008223] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.008249] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.008538] Initializing cgroup subsys memory
Jul 23 16:38:47 node-5 kernel: [    0.008547] Initializing cgroup subsys devices
Jul 23 16:38:47 node-5 kernel: [    0.008549] Initializing cgroup subsys freezer
Jul 23 16:38:47 node-5 kernel: [    0.008550] Initializing cgroup subsys blkio
Jul 23 16:38:47 node-5 kernel: [    0.008552] Initializing cgroup subsys perf_event
Jul 23 16:38:47 node-5 kernel: [    0.008554] Initializing cgroup subsys hugetlb
Jul 23 16:38:47 node-5 kernel: [    0.008574] CPU: Physical Processor ID: 0
Jul 23 16:38:47 node-5 kernel: [    0.008575] CPU: Processor Core ID: 0
Jul 23 16:38:47 node-5 kernel: [    0.008579] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 23 16:38:47 node-5 kernel: [    0.008579] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 23 16:38:47 node-5 kernel: [    0.009273] mce: CPU supports 22 MCE banks
Jul 23 16:38:47 node-5 kernel: [    0.009300] CPU0: Thermal monitoring enabled (TM1)
Jul 23 16:38:47 node-5 kernel: [    0.009321] process: using mwait in idle threads
Jul 23 16:38:47 node-5 kernel: [    0.009324] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 23 16:38:47 node-5 kernel: [    0.009324] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 23 16:38:47 node-5 kernel: [    0.009324] tlb_flushall_shift: 6
Jul 23 16:38:47 node-5 kernel: [    0.009413] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 23 16:38:47 node-5 kernel: [    0.010137] ACPI: Core revision 20131115
Jul 23 16:38:47 node-5 kernel: [    0.022801] ACPI: All ACPI Tables successfully acquired
Jul 23 16:38:47 node-5 kernel: [    0.022963] ftrace: allocating 28617 entries in 112 pages
Jul 23 16:38:47 node-5 kernel: [    0.031775] dmar: Host address width 46
Jul 23 16:38:47 node-5 kernel: [    0.031777] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 23 16:38:47 node-5 kernel: [    0.031783] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 23 16:38:47 node-5 kernel: [    0.031784] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 23 16:38:47 node-5 kernel: [    0.031788] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 23 16:38:47 node-5 kernel: [    0.031790] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 23 16:38:47 node-5 kernel: [    0.031791] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 23 16:38:47 node-5 kernel: [    0.031792] dmar: ATSR flags: 0x0
Jul 23 16:38:47 node-5 kernel: [    0.031793] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 23 16:38:47 node-5 kernel: [    0.031795] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 23 16:38:47 node-5 kernel: [    0.031911] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 23 16:38:47 node-5 kernel: [    0.031912] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 23 16:38:47 node-5 kernel: [    0.031913] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 23 16:38:47 node-5 kernel: [    0.031914] HPET id 0 under DRHD base 0xc7ffc000
Jul 23 16:38:47 node-5 kernel: [    0.031915] Your BIOS is broken and requested that x2apic be disabled.
Jul 23 16:38:47 node-5 kernel: [    0.031915] This will slightly decrease performance.
Jul 23 16:38:47 node-5 kernel: [    0.031915] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 23 16:38:47 node-5 kernel: [    0.032347] Enabled IRQ remapping in xapic mode
Jul 23 16:38:47 node-5 kernel: [    0.032348] x2apic not enabled, IRQ remapping is in xapic mode
Jul 23 16:38:47 node-5 kernel: [    0.032352] Switched APIC routing to physical flat.
Jul 23 16:38:47 node-5 kernel: [    0.032978] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 23 16:38:47 node-5 kernel: [    0.072627] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 23 16:38:47 node-5 kernel: [    0.072633] TSC deadline timer enabled
Jul 23 16:38:47 node-5 kernel: [    0.072640] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 23 16:38:47 node-5 kernel: [    0.072646] ... version:                3
Jul 23 16:38:47 node-5 kernel: [    0.072647] ... bit width:              48
Jul 23 16:38:47 node-5 kernel: [    0.072648] ... generic registers:      4
Jul 23 16:38:47 node-5 kernel: [    0.072649] ... value mask:             0000ffffffffffff
Jul 23 16:38:47 node-5 kernel: [    0.072650] ... max period:             0000ffffffffffff
Jul 23 16:38:47 node-5 kernel: [    0.072651] ... fixed-purpose events:   3
Jul 23 16:38:47 node-5 kernel: [    0.072652] ... event mask:             000000070000000f
Jul 23 16:38:47 node-5 kernel: [    0.074080] x86: Booting SMP configuration:
Jul 23 16:38:47 node-5 kernel: [    0.088205] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 23 16:38:47 node-5 kernel: [    0.074082] .... node  #0, CPUs:        #1  #2  #3
Jul 23 16:38:47 node-5 kernel: [    0.116122] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 23 16:38:47 node-5 kernel: [    0.270265] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 23 16:38:47 node-5 kernel: [    0.325882] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 23 16:38:47 node-5 kernel: [    0.382728] x86: Booted up 2 nodes, 16 CPUs
Jul 23 16:38:47 node-5 kernel: [    0.382731] smpboot: Total of 16 processors activated (111750.97 BogoMIPS)
Jul 23 16:38:47 node-5 kernel: [    0.406777] devtmpfs: initialized
Jul 23 16:38:47 node-5 kernel: [    0.409876] EVM: security.selinux
Jul 23 16:38:47 node-5 kernel: [    0.409878] EVM: security.SMACK64
Jul 23 16:38:47 node-5 kernel: [    0.409879] EVM: security.ima
Jul 23 16:38:47 node-5 kernel: [    0.409880] EVM: security.capability
Jul 23 16:38:47 node-5 kernel: [    0.409930] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.410588] pinctrl core: initialized pinctrl subsystem
Jul 23 16:38:47 node-5 kernel: [    0.410651] regulator-dummy: no parameters
Jul 23 16:38:47 node-5 kernel: [    0.410683] RTC time: 16:38:08, date: 07/23/16
Jul 23 16:38:47 node-5 kernel: [    0.410718] NET: Registered protocol family 16
Jul 23 16:38:47 node-5 kernel: [    0.410802] cpuidle: using governor ladder
Jul 23 16:38:47 node-5 kernel: [    0.410804] cpuidle: using governor menu
Jul 23 16:38:47 node-5 kernel: [    0.410837] ACPI: bus type PCI registered
Jul 23 16:38:47 node-5 kernel: [    0.410839] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 23 16:38:47 node-5 kernel: [    0.410886] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 23 16:38:47 node-5 kernel: [    0.410888] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 23 16:38:47 node-5 kernel: [    0.424617] PCI: Using configuration type 1 for base access
Jul 23 16:38:47 node-5 kernel: [    0.425619] bio: create slab <bio-0> at 0
Jul 23 16:38:47 node-5 kernel: [    0.425891] ACPI: Added _OSI(Module Device)
Jul 23 16:38:47 node-5 kernel: [    0.425892] ACPI: Added _OSI(Processor Device)
Jul 23 16:38:47 node-5 kernel: [    0.425893] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 23 16:38:47 node-5 kernel: [    0.425895] ACPI: Added _OSI(Processor Aggregator Device)
Jul 23 16:38:47 node-5 kernel: [    0.438562] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 23 16:38:47 node-5 kernel: [    0.449135] ACPI: Interpreter enabled
Jul 23 16:38:47 node-5 kernel: [    0.449140] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 23 16:38:47 node-5 kernel: [    0.449144] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 23 16:38:47 node-5 kernel: [    0.449147] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 23 16:38:47 node-5 kernel: [    0.449154] ACPI: (supports S0 S4 S5)
Jul 23 16:38:47 node-5 kernel: [    0.449155] ACPI: Using IOAPIC for interrupt routing
Jul 23 16:38:47 node-5 kernel: [    0.449200] HEST: Table parsing has been initialized.
Jul 23 16:38:47 node-5 kernel: [    0.449203] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 23 16:38:47 node-5 kernel: [    0.449757] ACPI: No dock devices found.
Jul 23 16:38:47 node-5 kernel: [    0.461268] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 23 16:38:47 node-5 kernel: [    0.461272] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 23 16:38:47 node-5 kernel: [    0.461276] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 23 16:38:47 node-5 kernel: [    0.461302] PCI host bridge to bus 0000:ff
Jul 23 16:38:47 node-5 kernel: [    0.461304] pci_bus 0000:ff: root bus resource [bus ff]
Jul 23 16:38:47 node-5 kernel: [    0.461312] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461350] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.461380] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461415] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461444] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.461472] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.461503] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461531] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461561] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461589] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461615] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461641] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461669] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461695] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461721] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461747] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461775] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461802] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461828] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.461856] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461882] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.461907] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461933] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.461963] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.461998] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462028] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462058] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462088] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462120] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462152] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462184] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462216] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462246] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462276] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462308] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462340] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462373] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462403] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462430] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462461] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462493] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462529] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462564] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462596] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462626] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462655] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462684] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462713] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462745] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462775] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462806] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462834] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462863] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462891] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462920] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462950] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.462982] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463038] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 23 16:38:47 node-5 kernel: [    0.463040] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 23 16:38:47 node-5 kernel: [    0.463043] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 23 16:38:47 node-5 kernel: [    0.463061] PCI host bridge to bus 0000:7f
Jul 23 16:38:47 node-5 kernel: [    0.463062] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 23 16:38:47 node-5 kernel: [    0.463067] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463094] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.463122] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463151] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463172] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.463196] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.463221] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463247] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463270] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463292] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463315] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463337] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463368] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463392] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463418] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463445] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463466] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463489] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463512] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.463537] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463559] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.463581] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463605] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463633] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 23 16:38:47 node-5 kernel: [    0.463665] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463691] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463717] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463743] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463767] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463795] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463820] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463848] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463872] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463900] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463927] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463954] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.463982] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464008] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464032] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464060] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464085] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464110] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464139] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464166] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464192] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464216] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464242] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464268] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464294] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464320] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464349] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464374] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464397] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464422] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464446] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464475] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.464500] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.465740] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 23 16:38:47 node-5 kernel: [    0.465743] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 23 16:38:47 node-5 kernel: [    0.466870] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 23 16:38:47 node-5 kernel: [    0.467383] PCI host bridge to bus 0000:00
Jul 23 16:38:47 node-5 kernel: [    0.467386] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 23 16:38:47 node-5 kernel: [    0.467387] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 23 16:38:47 node-5 kernel: [    0.467388] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 23 16:38:47 node-5 kernel: [    0.467390] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 23 16:38:47 node-5 kernel: [    0.467391] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 23 16:38:47 node-5 kernel: [    0.467393] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 23 16:38:47 node-5 kernel: [    0.467394] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 23 16:38:47 node-5 kernel: [    0.467400] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 23 16:38:47 node-5 kernel: [    0.467482] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.467513] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.467554] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 23 16:38:47 node-5 kernel: [    0.467573] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.467602] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.467642] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 23 16:38:47 node-5 kernel: [    0.467660] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.467690] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.467730] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 23 16:38:47 node-5 kernel: [    0.467746] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.467816] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.467892] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.467968] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 23 16:38:47 node-5 kernel: [    0.467972] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 23 16:38:47 node-5 kernel: [    0.468056] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 23 16:38:47 node-5 kernel: [    0.468204] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 23 16:38:47 node-5 kernel: [    0.468221] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 23 16:38:47 node-5 kernel: [    0.468300] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.468354] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 23 16:38:47 node-5 kernel: [    0.468375] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.468431] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.468474] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 23 16:38:47 node-5 kernel: [    0.468501] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.468557] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.468600] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 23 16:38:47 node-5 kernel: [    0.468625] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 23 16:38:47 node-5 kernel: [    0.468643] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 23 16:38:47 node-5 kernel: [    0.468721] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.468771] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 23 16:38:47 node-5 kernel: [    0.468798] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 23 16:38:47 node-5 kernel: [    0.469046] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 23 16:38:47 node-5 kernel: [    0.469052] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 23 16:38:47 node-5 kernel: [    0.469058] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.469064] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.469071] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 23 16:38:47 node-5 kernel: [    0.469101] pci 0000:01:00.0: supports D1 D2
Jul 23 16:38:47 node-5 kernel: [    0.479354] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 23 16:38:47 node-5 kernel: [    0.479361] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 23 16:38:47 node-5 kernel: [    0.479365] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 23 16:38:47 node-5 kernel: [    0.479622] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.479656] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 23 16:38:47 node-5 kernel: [    0.487351] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 23 16:38:47 node-5 kernel: [    0.487358] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.487362] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 23 16:38:47 node-5 kernel: [    0.487445] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.487518] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.487613] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.487695] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 23 16:38:47 node-5 kernel: [    0.487702] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.487706] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 23 16:38:47 node-5 kernel: [    0.487800] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.487923] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.487977] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 23 16:38:47 node-5 kernel: [    0.487979] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.487981] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 23 16:38:47 node-5 kernel: [    0.488031] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.488151] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.488193] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.488312] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.488349] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.488468] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.488504] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 23 16:38:47 node-5 kernel: [    0.488625] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 23 16:38:47 node-5 kernel: [    0.488666] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 23 16:38:47 node-5 kernel: [    0.488669] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.488671] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 23 16:38:47 node-5 kernel: [    0.488730] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 23 16:38:47 node-5 kernel: [    0.488813] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.488866] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.488922] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 23 16:38:47 node-5 kernel: [    0.489005] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 23 16:38:47 node-5 kernel: [    0.489111] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 23 16:38:47 node-5 kernel: [    0.489113] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.489115] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 23 16:38:47 node-5 kernel: [    0.489171] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 23 16:38:47 node-5 kernel: [    0.489225] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.489273] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.489486] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 23 16:38:47 node-5 kernel: [    0.489490] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 23 16:38:47 node-5 kernel: [    0.489553] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 23 16:38:47 node-5 kernel: [    0.489605] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.489654] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.489887] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 23 16:38:47 node-5 kernel: [    0.489890] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 23 16:38:47 node-5 kernel: [    0.489950] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 23 16:38:47 node-5 kernel: [    0.490013] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.490065] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 23 16:38:47 node-5 kernel: [    0.490288] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 23 16:38:47 node-5 kernel: [    0.490292] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 23 16:38:47 node-5 kernel: [    0.490466] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 23 16:38:47 node-5 kernel: [    0.490504] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 23 16:38:47 node-5 kernel: [    0.490583] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 23 16:38:47 node-5 kernel: [    0.490602] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 23 16:38:47 node-5 kernel: [    0.490615] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 23 16:38:47 node-5 kernel: [    0.490629] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 23 16:38:47 node-5 kernel: [    0.490679] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 23 16:38:47 node-5 kernel: [    0.495358] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 23 16:38:47 node-5 kernel: [    0.495367] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 23 16:38:47 node-5 kernel: [    0.495420] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 23 16:38:47 node-5 kernel: [    0.495993] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 23 16:38:47 node-5 kernel: [    0.495996] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 23 16:38:47 node-5 kernel: [    0.496116] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 23 16:38:47 node-5 kernel: [    0.496225] PCI host bridge to bus 0000:80
Jul 23 16:38:47 node-5 kernel: [    0.496227] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 23 16:38:47 node-5 kernel: [    0.496228] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 23 16:38:47 node-5 kernel: [    0.496230] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 23 16:38:47 node-5 kernel: [    0.496238] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.496301] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.496369] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 23 16:38:47 node-5 kernel: [    0.496431] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 23 16:38:47 node-5 kernel: [    0.496437] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 23 16:38:47 node-5 kernel: [    0.496507] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 23 16:38:47 node-5 kernel: [    0.496804] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 23 16:38:47 node-5 kernel: [    0.496835] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 23 16:38:47 node-5 kernel: [    0.496865] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 23 16:38:47 node-5 kernel: [    0.496894] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 23 16:38:47 node-5 kernel: [    0.496923] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 23 16:38:47 node-5 kernel: [    0.496953] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 23 16:38:47 node-5 kernel: [    0.496983] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 23 16:38:47 node-5 kernel: [    0.497012] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 23 16:38:47 node-5 kernel: [    0.497098] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 23 16:38:47 node-5 kernel: [    0.497102] ACPI: \_SB_.UNC1: notify handler is installed
Jul 23 16:38:47 node-5 kernel: [    0.497103] ACPI: \_SB_.UNC0: notify handler is installed
Jul 23 16:38:47 node-5 kernel: [    0.497118] ACPI: \_SB_.PCI0: notify handler is installed
Jul 23 16:38:47 node-5 kernel: [    0.497171] ACPI: \_SB_.PCI1: notify handler is installed
Jul 23 16:38:47 node-5 kernel: [    0.497251] Found 4 acpi root devices
Jul 23 16:38:47 node-5 kernel: [    0.497371] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 23 16:38:47 node-5 kernel: [    0.497373] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 23 16:38:47 node-5 kernel: [    0.497375] vgaarb: loaded
Jul 23 16:38:47 node-5 kernel: [    0.497376] vgaarb: bridge control possible 0000:0c:00.0
Jul 23 16:38:47 node-5 kernel: [    0.497495] SCSI subsystem initialized
Jul 23 16:38:47 node-5 kernel: [    0.497556] libata version 3.00 loaded.
Jul 23 16:38:47 node-5 kernel: [    0.497572] ACPI: bus type USB registered
Jul 23 16:38:47 node-5 kernel: [    0.497583] usbcore: registered new interface driver usbfs
Jul 23 16:38:47 node-5 kernel: [    0.497588] usbcore: registered new interface driver hub
Jul 23 16:38:47 node-5 kernel: [    0.497609] usbcore: registered new device driver usb
Jul 23 16:38:47 node-5 kernel: [    0.497771] PCI: Using ACPI for IRQ routing
Jul 23 16:38:47 node-5 kernel: [    0.501383] PCI: pci_cache_line_size set to 64 bytes
Jul 23 16:38:47 node-5 kernel: [    0.501591] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 23 16:38:47 node-5 kernel: [    0.501592] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 23 16:38:47 node-5 kernel: [    0.501593] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 23 16:38:47 node-5 kernel: [    0.501659] NetLabel: Initializing
Jul 23 16:38:47 node-5 kernel: [    0.501660] NetLabel:  domain hash size = 128
Jul 23 16:38:47 node-5 kernel: [    0.501661] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 23 16:38:47 node-5 kernel: [    0.501671] NetLabel:  unlabeled traffic allowed by default
Jul 23 16:38:47 node-5 kernel: [    0.501727] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 23 16:38:47 node-5 kernel: [    0.501732] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 23 16:38:47 node-5 kernel: [    0.503796] Switched to clocksource hpet
Jul 23 16:38:47 node-5 kernel: [    0.507911] AppArmor: AppArmor Filesystem Enabled
Jul 23 16:38:47 node-5 kernel: [    0.507924] pnp: PnP ACPI init
Jul 23 16:38:47 node-5 kernel: [    0.507932] ACPI: bus type PNP registered
Jul 23 16:38:47 node-5 kernel: [    0.508041] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 23 16:38:47 node-5 kernel: [    0.508049] pnp 00:01: [dma 4]
Jul 23 16:38:47 node-5 kernel: [    0.508060] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 23 16:38:47 node-5 kernel: [    0.508087] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 23 16:38:47 node-5 kernel: [    0.508106] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 23 16:38:47 node-5 kernel: [    0.508123] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 23 16:38:47 node-5 kernel: [    0.508156] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 23 16:38:47 node-5 kernel: [    0.508207] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508209] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 23 16:38:47 node-5 kernel: [    0.508211] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508212] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508214] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508218] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508220] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 23 16:38:47 node-5 kernel: [    0.508221] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508223] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508224] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508226] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508227] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508229] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 23 16:38:47 node-5 kernel: [    0.508231] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 23 16:38:47 node-5 kernel: [    0.508314] pnp 00:07: [dma 0 disabled]
Jul 23 16:38:47 node-5 kernel: [    0.508343] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 23 16:38:47 node-5 kernel: [    0.508418] pnp 00:08: [dma 0 disabled]
Jul 23 16:38:47 node-5 kernel: [    0.508450] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 23 16:38:47 node-5 kernel: [    0.508501] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 23 16:38:47 node-5 kernel: [    0.508846] pnp: PnP ACPI: found 10 devices
Jul 23 16:38:47 node-5 kernel: [    0.508848] ACPI: bus type PNP unregistered
Jul 23 16:38:47 node-5 kernel: [    0.515163] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 23 16:38:47 node-5 kernel: [    0.515166] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 23 16:38:47 node-5 kernel: [    0.515169] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 23 16:38:47 node-5 kernel: [    0.515173] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 23 16:38:47 node-5 kernel: [    0.515175] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.515189] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515218] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 23 16:38:47 node-5 kernel: [    0.515233] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515262] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 23 16:38:47 node-5 kernel: [    0.515276] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 23 16:38:47 node-5 kernel: [    0.515305] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 23 16:38:47 node-5 kernel: [    0.515319] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 23 16:38:47 node-5 kernel: [    0.515348] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 23 16:38:47 node-5 kernel: [    0.515350] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.515364] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515393] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 23 16:38:47 node-5 kernel: [    0.515395] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.515412] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515441] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 23 16:38:47 node-5 kernel: [    0.515443] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.515446] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515450] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 23 16:38:47 node-5 kernel: [    0.515451] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.515454] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515458] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 23 16:38:47 node-5 kernel: [    0.515462] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 23 16:38:47 node-5 kernel: [    0.515470] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 23 16:38:47 node-5 kernel: [    0.515474] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 23 16:38:47 node-5 kernel: [    0.515480] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 23 16:38:47 node-5 kernel: [    0.515481] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 23 16:38:47 node-5 kernel: [    0.515482] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 23 16:38:47 node-5 kernel: [    0.515483] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 23 16:38:47 node-5 kernel: [    0.515484] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 23 16:38:47 node-5 kernel: [    0.515485] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 23 16:38:47 node-5 kernel: [    0.515486] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 23 16:38:47 node-5 kernel: [    0.515486] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 23 16:38:47 node-5 kernel: [    0.515487] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.515488] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515489] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.515490] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515491] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.515492] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515493] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.515493] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515494] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 23 16:38:47 node-5 kernel: [    0.515495] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515496] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 23 16:38:47 node-5 kernel: [    0.515497] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 23 16:38:47 node-5 kernel: [    0.515498] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 23 16:38:47 node-5 kernel: [    0.515499] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 23 16:38:47 node-5 kernel: [    0.515501] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 23 16:38:47 node-5 kernel: [    0.515502] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 23 16:38:47 node-5 kernel: [    0.515542] NET: Registered protocol family 2
Jul 23 16:38:47 node-5 kernel: [    0.515814] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.516146] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.516293] TCP: Hash tables configured (established 262144 bind 65536)
Jul 23 16:38:47 node-5 kernel: [    0.516330] TCP: reno registered
Jul 23 16:38:47 node-5 kernel: [    0.516359] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.516456] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.516606] NET: Registered protocol family 1
Jul 23 16:38:47 node-5 kernel: [    0.555844] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 23 16:38:47 node-5 kernel: [    0.555851] PCI: CLS 64 bytes, default 64
Jul 23 16:38:47 node-5 kernel: [    0.555893] Trying to unpack rootfs image as initramfs...
Jul 23 16:38:47 node-5 kernel: [    0.775412] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 23 16:38:47 node-5 kernel: [    0.775448] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 23 16:38:47 node-5 kernel: [    0.775450] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 23 16:38:47 node-5 kernel: [    0.775881] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775887] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775892] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775897] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775909] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775926] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775942] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775957] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775968] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775978] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775984] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775990] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.775999] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.776011] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.776024] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.776037] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 23 16:38:47 node-5 kernel: [    0.776149] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 23 16:38:47 node-5 kernel: [    0.776156] Scanning for low memory corruption every 60 seconds
Jul 23 16:38:47 node-5 kernel: [    0.776589] Initialise system trusted keyring
Jul 23 16:38:47 node-5 kernel: [    0.776642] audit: initializing netlink socket (disabled)
Jul 23 16:38:47 node-5 kernel: [    0.776658] type=2000 audit(1469291888.732:1): initialized
Jul 23 16:38:47 node-5 kernel: [    0.794606] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 23 16:38:47 node-5 kernel: [    0.796151] zbud: loaded
Jul 23 16:38:47 node-5 kernel: [    0.796278] VFS: Disk quotas dquot_6.5.2
Jul 23 16:38:47 node-5 kernel: [    0.796315] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 23 16:38:47 node-5 kernel: [    0.796682] fuse init (API version 7.22)
Jul 23 16:38:47 node-5 kernel: [    0.796743] msgmni has been set to 32768
Jul 23 16:38:47 node-5 kernel: [    0.796791] Key type big_key registered
Jul 23 16:38:47 node-5 kernel: [    0.797307] Key type asymmetric registered
Jul 23 16:38:47 node-5 kernel: [    0.797309] Asymmetric key parser 'x509' registered
Jul 23 16:38:47 node-5 kernel: [    0.797335] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 23 16:38:47 node-5 kernel: [    0.797416] io scheduler noop registered
Jul 23 16:38:47 node-5 kernel: [    0.797418] io scheduler deadline registered (default)
Jul 23 16:38:47 node-5 kernel: [    0.797437] io scheduler cfq registered
Jul 23 16:38:47 node-5 kernel: [    0.797836] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    0.797956] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    0.798068] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    0.798190] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    0.798305] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    0.798403] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    0.798798] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 23 16:38:47 node-5 kernel: [    0.798824] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 23 16:38:47 node-5 kernel: [    0.798840] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 23 16:38:47 node-5 kernel: [    0.798849] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798851] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798854] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 23 16:38:47 node-5 kernel: [    0.798859] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798860] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798862] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798863] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798865] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798866] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798868] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798869] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798871] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798872] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798873] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798875] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798877] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 23 16:38:47 node-5 kernel: [    0.798882] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798884] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 23 16:38:47 node-5 kernel: [    0.798901] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798905] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 23 16:38:47 node-5 kernel: [    0.798915] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798917] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 23 16:38:47 node-5 kernel: [    0.798920] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 23 16:38:47 node-5 kernel: [    0.798969] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 23 16:38:47 node-5 kernel: [    0.798975] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 23 16:38:47 node-5 kernel: [    0.798980] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 23 16:38:47 node-5 kernel: [    0.798989] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 23 16:38:47 node-5 kernel: [    0.799029] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 23 16:38:47 node-5 kernel: [    0.799031] vesafb: scrolling: redraw
Jul 23 16:38:47 node-5 kernel: [    0.799032] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 23 16:38:47 node-5 kernel: [    0.819515] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 23 16:38:47 node-5 kernel: [    0.828101] Console: switching to colour frame buffer device 80x30
Jul 23 16:38:47 node-5 kernel: [    0.836916] fb0: VESA VGA frame buffer device
Jul 23 16:38:47 node-5 kernel: [    0.837112] intel_idle: MWAIT substates: 0x2120
Jul 23 16:38:47 node-5 kernel: [    0.837113] intel_idle: v0.4 model 0x3F
Jul 23 16:38:47 node-5 kernel: [    0.837114] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 23 16:38:47 node-5 kernel: [    0.837348] ipmi message handler version 39.2
Jul 23 16:38:47 node-5 kernel: [    0.837626] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 23 16:38:47 node-5 kernel: [    0.838059] ACPI: AC Adapter [P111] (on-line)
Jul 23 16:38:47 node-5 kernel: [    0.843289] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 23 16:38:47 node-5 kernel: [    0.854326] ACPI: Power Button [PWRB]
Jul 23 16:38:47 node-5 kernel: [    0.860083] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 23 16:38:47 node-5 kernel: [    0.871725] ACPI: Power Button [PWRF]
Jul 23 16:38:47 node-5 kernel: [    0.897331] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 23 16:38:47 node-5 kernel: [    0.908990] pstore: Registered erst as persistent store backend
Jul 23 16:38:47 node-5 kernel: [    0.915190] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 23 16:38:47 node-5 kernel: [    0.927136] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 23 16:38:47 node-5 kernel: [    0.953891] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 23 16:38:47 node-5 kernel: [    0.987159] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 23 16:38:47 node-5 kernel: [    1.001254] Linux agpgart interface v0.103
Jul 23 16:38:47 node-5 kernel: [    1.008875] brd: module loaded
Jul 23 16:38:47 node-5 kernel: [    1.015932] loop: module loaded
Jul 23 16:38:47 node-5 kernel: [    1.022645] libphy: Fixed MDIO Bus: probed
Jul 23 16:38:47 node-5 kernel: [    1.029098] tun: Universal TUN/TAP device driver, 1.6
Jul 23 16:38:47 node-5 kernel: [    1.035565] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 23 16:38:47 node-5 kernel: [    1.042111] PPP generic driver version 2.4.2
Jul 23 16:38:47 node-5 kernel: [    1.048490] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 23 16:38:47 node-5 kernel: [    1.054916] ehci-pci: EHCI PCI platform driver
Jul 23 16:38:47 node-5 kernel: [    1.061429] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 23 16:38:47 node-5 kernel: [    1.067827] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 23 16:38:47 node-5 kernel: [    1.080333] ehci-pci 0000:00:1a.0: debug port 2
Jul 23 16:38:47 node-5 kernel: [    1.090536] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 23 16:38:47 node-5 kernel: [    1.090555] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 23 16:38:47 node-5 kernel: [    1.107289] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 23 16:38:47 node-5 kernel: [    1.113358] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 23 16:38:47 node-5 kernel: [    1.119526] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 23 16:38:47 node-5 kernel: [    1.131404] usb usb1: Product: EHCI Host Controller
Jul 23 16:38:47 node-5 kernel: [    1.137421] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 23 16:38:47 node-5 kernel: [    1.143448] usb usb1: SerialNumber: 0000:00:1a.0
Jul 23 16:38:47 node-5 kernel: [    1.149383] hub 1-0:1.0: USB hub found
Jul 23 16:38:47 node-5 kernel: [    1.155149] hub 1-0:1.0: 2 ports detected
Jul 23 16:38:47 node-5 kernel: [    1.160927] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 23 16:38:47 node-5 kernel: [    1.166506] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 23 16:38:47 node-5 kernel: [    1.177400] ehci-pci 0000:00:1d.0: debug port 2
Jul 23 16:38:47 node-5 kernel: [    1.186701] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 23 16:38:47 node-5 kernel: [    1.186704] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 23 16:38:47 node-5 kernel: [    1.203207] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 23 16:38:47 node-5 kernel: [    1.208402] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 23 16:38:47 node-5 kernel: [    1.213699] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 23 16:38:47 node-5 kernel: [    1.224279] usb usb2: Product: EHCI Host Controller
Jul 23 16:38:47 node-5 kernel: [    1.229742] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 23 16:38:47 node-5 kernel: [    1.235294] usb usb2: SerialNumber: 0000:00:1d.0
Jul 23 16:38:47 node-5 kernel: [    1.240829] hub 2-0:1.0: USB hub found
Jul 23 16:38:47 node-5 kernel: [    1.246185] hub 2-0:1.0: 2 ports detected
Jul 23 16:38:47 node-5 kernel: [    1.251492] ehci-platform: EHCI generic platform driver
Jul 23 16:38:47 node-5 kernel: [    1.256730] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 23 16:38:47 node-5 kernel: [    1.262052] ohci-pci: OHCI PCI platform driver
Jul 23 16:38:47 node-5 kernel: [    1.267360] ohci-platform: OHCI generic platform driver
Jul 23 16:38:47 node-5 kernel: [    1.272565] uhci_hcd: USB Universal Host Controller Interface driver
Jul 23 16:38:47 node-5 kernel: [    1.277906] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 23 16:38:47 node-5 kernel: [    1.478970] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 23 16:38:47 node-5 kernel: [    1.770737] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 23 16:38:47 node-5 kernel: [    1.787076] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 23 16:38:47 node-5 kernel: [    1.792769] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 23 16:38:47 node-5 kernel: [    1.798593] hub 1-1:1.0: USB hub found
Jul 23 16:38:47 node-5 kernel: [    1.804187] hub 1-1:1.0: 6 ports detected
Jul 23 16:38:47 node-5 kernel: [    1.918598] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 23 16:38:47 node-5 kernel: [    2.316602] i8042: No controller found
Jul 23 16:38:47 node-5 kernel: [    2.322215] mousedev: PS/2 mouse device common for all mice
Jul 23 16:38:47 node-5 kernel: [    2.327942] rtc_cmos 00:02: RTC can wake from S4
Jul 23 16:38:47 node-5 kernel: [    2.333676] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 23 16:38:47 node-5 kernel: [    2.335047] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 23 16:38:47 node-5 kernel: [    2.335048] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 23 16:38:47 node-5 kernel: [    2.335564] hub 2-1:1.0: USB hub found
Jul 23 16:38:47 node-5 kernel: [    2.335804] hub 2-1:1.0: 8 ports detected
Jul 23 16:38:47 node-5 kernel: [    2.361832] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 23 16:38:47 node-5 kernel: [    2.373110] device-mapper: uevent: version 1.0.3
Jul 23 16:38:47 node-5 kernel: [    2.378815] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 23 16:38:47 node-5 kernel: [    2.390154] ledtrig-cpu: registered to indicate activity on CPUs
Jul 23 16:38:47 node-5 kernel: [    2.396097] TCP: cubic registered
Jul 23 16:38:47 node-5 kernel: [    2.401938] NET: Registered protocol family 10
Jul 23 16:38:47 node-5 kernel: [    2.407992] NET: Registered protocol family 17
Jul 23 16:38:47 node-5 kernel: [    2.413749] Key type dns_resolver registered
Jul 23 16:38:47 node-5 kernel: [    2.419754] Loading compiled-in X.509 certificates
Jul 23 16:38:47 node-5 kernel: [    2.425951] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 23 16:38:47 node-5 kernel: [    2.437532] registered taskstats version 1
Jul 23 16:38:47 node-5 kernel: [    2.445557] Key type trusted registered
Jul 23 16:38:47 node-5 kernel: [    2.453130] Key type encrypted registered
Jul 23 16:38:47 node-5 kernel: [    2.458614] AppArmor: AppArmor sha1 policy hashing enabled
Jul 23 16:38:47 node-5 kernel: [    2.464111] IMA: No TPM chip found, activating TPM-bypass!
Jul 23 16:38:47 node-5 kernel: [    2.470202] regulator-dummy: disabling
Jul 23 16:38:47 node-5 kernel: [    2.475640]   Magic number: 8:14:642
Jul 23 16:38:47 node-5 kernel: [    2.481369] rtc_cmos 00:02: setting system clock to 2016-07-23 16:38:11 UTC (1469291891)
Jul 23 16:38:47 node-5 kernel: [    2.493913] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 23 16:38:47 node-5 kernel: [    2.499604] EDD information not available.
Jul 23 16:38:47 node-5 kernel: [    2.505223] PM: Hibernation image not present or could not be loaded.
Jul 23 16:38:47 node-5 kernel: [    2.506086] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 23 16:38:47 node-5 kernel: [    2.517535] Write protecting the kernel read-only data: 12288k
Jul 23 16:38:47 node-5 kernel: [    2.523897] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 23 16:38:47 node-5 kernel: [    2.536884] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 23 16:38:47 node-5 kernel: [    2.568895] device-mapper: multipath: version 1.6.0 loaded
Jul 23 16:38:47 node-5 kernel: [    2.576873] systemd-udevd[215]: starting version 204
Jul 23 16:38:47 node-5 kernel: [    2.597792] md: linear personality registered for level -1
Jul 23 16:38:47 node-5 kernel: [    2.612111] md: multipath personality registered for level -4
Jul 23 16:38:47 node-5 kernel: [    2.614339] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 23 16:38:47 node-5 kernel: [    2.626588] md: raid0 personality registered for level 0
Jul 23 16:38:47 node-5 kernel: [    2.635255] md: raid1 personality registered for level 1
Jul 23 16:38:47 node-5 kernel: [    2.644111] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 23 16:38:47 node-5 kernel: [    2.650505] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 23 16:38:47 node-5 kernel: [    2.656809] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 23 16:38:47 node-5 kernel: [    2.662232] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 23 16:38:47 node-5 kernel: [    2.662239] 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 23 16:38:47 node-5 kernel: [    2.662247] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 23 16:38:47 node-5 kernel: [    2.662650] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.662739] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.662862] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.663083] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.663165] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.678137] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 23 16:38:47 node-5 kernel: [    2.678158] 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 23 16:38:47 node-5 kernel: [    2.678167] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 23 16:38:47 node-5 kernel: [    2.678330] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.678445] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.678596] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.678680] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.678844] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.695216] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 23 16:38:47 node-5 kernel: [    2.695220] 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 23 16:38:47 node-5 kernel: [    2.695221] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 23 16:38:47 node-5 kernel: [    2.695423] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.695594] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.695772] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.695903] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.696149] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.709992] raid6: sse2x1   11304 MB/s
Jul 23 16:38:47 node-5 kernel: [    2.711179] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 23 16:38:47 node-5 kernel: [    2.711191] 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 23 16:38:47 node-5 kernel: [    2.711206] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 23 16:38:47 node-5 kernel: [    2.711328] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.711461] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.711564] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.711672] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.711869] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 23 16:38:47 node-5 kernel: [    2.750406] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 23 16:38:47 node-5 kernel: [    2.750407] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 23 16:38:47 node-5 kernel: [    2.750409] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 23 16:38:47 node-5 kernel: [    2.750411] usb 2-1.4: Manufacturer: Avocent
Jul 23 16:38:47 node-5 kernel: [    2.750411] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 23 16:38:47 node-5 kernel: [    2.777948] raid6: sse2x2   14616 MB/s
Jul 23 16:38:47 node-5 kernel: [    2.845878] raid6: sse2x4   17021 MB/s
Jul 23 16:38:47 node-5 kernel: [    2.913767] raid6: avx2x1   22211 MB/s
Jul 23 16:38:47 node-5 kernel: [    2.985706] raid6: avx2x2   18870 MB/s
Jul 23 16:38:47 node-5 kernel: [    3.057643] raid6: avx2x4   21333 MB/s
Jul 23 16:38:47 node-5 kernel: [    3.063308] raid6: using algorithm avx2x1 (22211 MB/s)
Jul 23 16:38:47 node-5 kernel: [    3.068910] raid6: using avx2x2 recovery algorithm
Jul 23 16:38:47 node-5 kernel: [    3.074605] Switched to clocksource tsc
Jul 23 16:38:47 node-5 kernel: [    3.074606] megasas: FW now in Ready state
Jul 23 16:38:47 node-5 kernel: [    3.075138] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.075222] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.075358] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.075508] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.075605] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.075766] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.075956] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.076030] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.076107] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.076258] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.076365] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.076467] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.076587] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.076690] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.076832] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.076936] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 23 16:38:47 node-5 kernel: [    3.077811] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 23 16:38:47 node-5 kernel: [    3.097014] xor: automatically using best checksumming function:
Jul 23 16:38:47 node-5 kernel: [    3.109627] hidraw: raw HID events driver (C) Jiri Kosina
Jul 23 16:38:47 node-5 kernel: [    3.117743] usbcore: registered new interface driver usbhid
Jul 23 16:38:47 node-5 kernel: [    3.123233] usbhid: USB HID core driver
Jul 23 16:38:47 node-5 kernel: [    3.129485] 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 23 16:38:47 node-5 kernel: [    3.140705] 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 23 16:38:47 node-5 kernel: [    3.141552]    avx       : 35708.000 MB/sec
Jul 23 16:38:47 node-5 kernel: [    3.157543] 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 23 16:38:47 node-5 kernel: [    3.168988] async_tx: api initialized (async)
Jul 23 16:38:47 node-5 kernel: [    3.169013] 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 23 16:38:47 node-5 kernel: [    3.169066] 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 23 16:38:47 node-5 kernel: [    3.169108] 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 23 16:38:47 node-5 kernel: [    3.214327] md: raid6 personality registered for level 6
Jul 23 16:38:47 node-5 kernel: [    3.220655] md: raid5 personality registered for level 5
Jul 23 16:38:47 node-5 kernel: [    3.226973] md: raid4 personality registered for level 4
Jul 23 16:38:47 node-5 kernel: [    3.236400] md: raid10 personality registered for level 10
Jul 23 16:38:47 node-5 kernel: [    3.291392] multipathd (355): /proc/355/oom_adj is deprecated, please use /proc/355/oom_score_adj instead.
Jul 23 16:38:47 node-5 kernel: [    3.465299] megasas:IOC Init cmd success
Jul 23 16:38:47 node-5 kernel: [    3.493281] megasas: INIT adapter done
Jul 23 16:38:47 node-5 kernel: [    3.737072] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 23 16:38:47 node-5 kernel: [    3.744055] scsi0 : LSI SAS based MegaRAID driver
Jul 23 16:38:47 node-5 kernel: [    3.751547] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 23 16:38:47 node-5 kernel: [    3.769995] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 23 16:38:47 node-5 kernel: [    3.785601] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 23 16:38:47 node-5 kernel: [    3.792141] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 23 16:38:47 node-5 kernel: [    3.805078] sd 0:2:0:0: [sda] Write Protect is off
Jul 23 16:38:47 node-5 kernel: [    3.811452] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 23 16:38:47 node-5 kernel: [    3.811470] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 23 16:38:47 node-5 kernel: [    3.855341]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 23 16:38:47 node-5 kernel: [    3.861969] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 23 16:38:47 node-5 kernel: [    3.987097] random: lvm urandom read with 27 bits of entropy available
Jul 23 16:38:47 node-5 kernel: [    4.136247] bio: create slab <bio-1> at 1
Jul 23 16:38:47 node-5 kernel: [    4.989919] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 23 16:38:47 node-5 kernel: [    5.694517] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 23 16:38:47 node-5 kernel: [    5.745035] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 23 16:38:47 node-5 kernel: [    5.808734] random: nonblocking pool is initialized
Jul 23 16:38:47 node-5 kernel: [    5.906236] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 23 16:38:47 node-5 kernel: [    5.942132] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 23 16:38:47 node-5 kernel: [    6.023824] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 23 16:38:47 node-5 kernel: [    6.255060] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 23 16:38:47 node-5 kernel: [    6.299963] XFS (dm-1): Mounting Filesystem
Jul 23 16:38:47 node-5 kernel: [    6.611870] XFS (dm-1): Ending clean mount
Jul 23 16:38:47 node-5 kernel: [    6.682304] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 23 16:38:47 node-5 kernel: [    6.723090] XFS (dm-2): Mounting Filesystem
Jul 23 16:38:47 node-5 kernel: [    6.822575] XFS (dm-2): Ending clean mount
Jul 23 16:38:47 node-5 kernel: [    6.990832] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 23 16:38:47 node-5 kernel: [    8.969407] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 23 16:38:47 node-5 kernel: [    8.983039] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 23 16:38:47 node-5 kernel: [    9.128015] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 23 16:38:47 node-5 kernel: [    9.128021] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 23 16:38:47 node-5 kernel: [    9.128025] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 23 16:38:47 node-5 kernel: [    9.128030] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 23 16:38:47 node-5 kernel: [    9.158734] systemd-udevd[801]: starting version 204
Jul 23 16:38:47 node-5 kernel: [    9.427550] power_meter ACPI000D:00: Found ACPI power meter.
Jul 23 16:38:47 node-5 kernel: [    9.427559] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 23 16:38:47 node-5 kernel: [    9.450814] IPMI System Interface driver.
Jul 23 16:38:47 node-5 kernel: [    9.450859] ipmi_si: probing via ACPI
Jul 23 16:38:47 node-5 kernel: [    9.450877] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 23 16:38:47 node-5 kernel: [    9.450878] ipmi_si: Adding ACPI-specified kcs state machine
Jul 23 16:38:47 node-5 kernel: [    9.450886] ipmi_si: probing via SMBIOS
Jul 23 16:38:47 node-5 kernel: [    9.450887] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 23 16:38:47 node-5 kernel: [    9.450887] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 23 16:38:47 node-5 kernel: [    9.450889] ipmi_si: probing via SPMI
Jul 23 16:38:47 node-5 kernel: [    9.450890] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 23 16:38:47 node-5 kernel: [    9.450890] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 23 16:38:47 node-5 kernel: [    9.450892] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 23 16:38:47 node-5 kernel: [    9.482816] wmi: Mapper loaded
Jul 23 16:38:47 node-5 kernel: [    9.485619] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 23 16:38:47 node-5 kernel: [    9.494094] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 23 16:38:47 node-5 kernel: [    9.494100] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 23 16:38:47 node-5 kernel: [    9.494103] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 23 16:38:47 node-5 kernel: [    9.494106] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 23 16:38:47 node-5 kernel: [    9.494124] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 23 16:38:47 node-5 kernel: [    9.540620] systemd-udevd[826]: renamed network interface eth0 to enp6s0
Jul 23 16:38:47 node-5 kernel: [    9.560505] systemd-udevd[843]: renamed network interface eth1 to enp7s0
Jul 23 16:38:47 node-5 kernel: [    9.588472] systemd-udevd[845]: renamed network interface eth2 to enp8s0
Jul 23 16:38:47 node-5 kernel: [    9.594299] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 23 16:38:47 node-5 kernel: [    9.594304] ipmi_si 00:09: IPMI kcs interface initialized
Jul 23 16:38:47 node-5 kernel: [    9.620462] systemd-udevd[819]: renamed network interface eth3 to enp9s0
Jul 23 16:38:47 node-5 kernel: [    9.889448] type=1400 audit(1469291898.909:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1085 comm="apparmor_parser"
Jul 23 16:38:47 node-5 kernel: [    9.889596] type=1400 audit(1469291898.909:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1085 comm="apparmor_parser"
Jul 23 16:38:47 node-5 kernel: [    9.889722] type=1400 audit(1469291898.909:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1085 comm="apparmor_parser"
Jul 23 16:38:47 node-5 kernel: [    9.908755] type=1400 audit(1469291898.929:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1084 comm="apparmor_parser"
Jul 23 16:38:47 node-5 kernel: [    9.908889] type=1400 audit(1469291898.929:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1084 comm="apparmor_parser"
Jul 23 16:38:47 node-5 kernel: [    9.909015] type=1400 audit(1469291898.929:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1084 comm="apparmor_parser"
Jul 23 16:38:47 node-5 kernel: [    9.910853] type=1400 audit(1469291898.929:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1083 comm="apparmor_parser"
Jul 23 16:38:47 node-5 kernel: [    9.910994] type=1400 audit(1469291898.929:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1083 comm="apparmor_parser"
Jul 23 16:38:47 node-5 kernel: [    9.911115] type=1400 audit(1469291898.929:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1083 comm="apparmor_parser"
Jul 23 16:38:47 node-5 kernel: [    9.926967] type=1400 audit(1469291898.945:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1086 comm="apparmor_parser"
Jul 23 16:38:47 node-5 kernel: [   10.455881] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 23 16:38:47 node-5 kernel: [   10.456628] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 23 16:38:47 node-5 kernel: [   10.715297] enic 0000:06:00.0 enp6s0: Link UP
Jul 23 16:38:47 node-5 kernel: [   10.715723] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 23 16:38:47 node-5 kernel: [   10.715732] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 23 16:38:47 node-5 kernel: [   21.290646] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 23 16:38:47 node-5 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 23 16:38:48 node-5 failsafe: Failsafe of 120 seconds reached.
Jul 23 16:38:48 node-5 kernel: [   40.326236] init: failsafe main process (8435) killed by TERM signal
Jul 23 16:38:49 node-5 dbus[8480]: [system] AppArmor D-Bus mediation is enabled
Jul 23 16:38:49 node-5 kernel: [   40.612801] audit_printk_skb: 30 callbacks suppressed
Jul 23 16:38:49 node-5 kernel: [   40.612804] type=1400 audit(1469291929.257:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8561 comm="apparmor_parser"
Jul 23 16:38:49 node-5 kernel: [   40.612808] type=1400 audit(1469291929.257:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8561 comm="apparmor_parser"
Jul 23 16:38:49 node-5 kernel: [   40.612811] type=1400 audit(1469291929.257:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8561 comm="apparmor_parser"
Jul 23 16:38:49 node-5 kernel: [   40.613038] type=1400 audit(1469291929.257:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8561 comm="apparmor_parser"
Jul 23 16:38:49 node-5 kernel: [   40.613040] type=1400 audit(1469291929.257:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8561 comm="apparmor_parser"
Jul 23 16:38:49 node-5 kernel: [   40.613157] type=1400 audit(1469291929.257:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8561 comm="apparmor_parser"
Jul 23 16:38:49 node-5 kernel: [   40.613945] type=1400 audit(1469291929.261:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8562 comm="apparmor_parser"
Jul 23 16:38:49 node-5 kernel: [   40.695159] type=1400 audit(1469291929.341:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8564 comm="apparmor_parser"
Jul 23 16:38:49 node-5 cron[8594]: (CRON) INFO (pidfile fd = 3)
Jul 23 16:38:49 node-5 cron[8631]: (CRON) STARTUP (fork ok)
Jul 23 16:38:49 node-5 anacron[8612]: Anacron 2.3 started on 2016-07-23
Jul 23 16:38:49 node-5 cron[8631]: (CRON) INFO (Running @reboot jobs)
Jul 23 16:38:49 node-5 multipathd: path checkers start up
Jul 23 16:38:49 node-5 anacron[8612]: Will run job `cron.daily' in 5 min.
Jul 23 16:38:49 node-5 anacron[8612]: Will run job `cron.weekly' in 10 min.
Jul 23 16:38:49 node-5 anacron[8612]: Will run job `cron.monthly' in 15 min.
Jul 23 16:38:49 node-5 anacron[8612]: Jobs will be executed sequentially
Jul 23 16:38:50 node-5 postfix/master[8772]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 23 16:38:53 node-5 puppet-agent[8957]: Reopening log files
Jul 23 16:38:53 node-5 puppet-agent[8957]: Could not request certificate: Connection refused - connect(2)
Jul 23 16:39:01 node-5 CRON[9003]: (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 23 16:39:02 node-5 puppet-user[9047]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 23 16:39:02 node-5 puppet-user[9047]: Compiled catalog for node-5.domain.tld in environment production in 0.04 seconds
Jul 23 16:39:03 node-5 puppet-user[9047]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 23 16:39:03 node-5 puppet-user[9047]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 23 16:39:03 node-5 puppet-user[9047]: Finished catalog run in 0.46 seconds
Jul 23 16:39:05 node-5 multipathd: uevent trigger error
Jul 23 16:39:05 node-5 puppet-user[9477]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 23 16:39:05 node-5 puppet-user[9477]: Compiled catalog for node-5.domain.tld in environment production in 0.09 seconds
Jul 23 16:39:05 node-5 puppet-user[9477]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 23 16:39:05 node-5 puppet-user[9477]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 23 16:39:05 node-5 puppet-user[9477]: (/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 23 16:39:05 node-5 puppet-user[9477]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 23 16:39:05 node-5 puppet-user[9477]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 23 16:39:05 node-5 puppet-user[9477]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 23 16:39:05 node-5 puppet-user[9477]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 23 16:39:05 node-5 puppet-user[9477]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 23 16:39:05 node-5 puppet-user[9477]: Finished catalog run in 0.05 seconds
Jul 23 16:39:06 node-5 puppet-user[10060]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 23 16:39:06 node-5 puppet-user[10060]: Compiled catalog for node-5.domain.tld in environment production in 0.07 seconds
Jul 23 16:39:06 node-5 puppet-user[10060]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 23 16:39:06 node-5 puppet-user[10060]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 23 16:39:06 node-5 puppet-user[10060]: Finished catalog run in 0.03 seconds
Jul 23 16:39:08 node-5 puppet-user[10538]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 23 16:39:08 node-5 puppet-user[10538]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 23 16:39:08 node-5 puppet-user[10538]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 23 16:39:08 node-5 puppet-user[10538]: Finished catalog run in 0.03 seconds
Jul 23 16:39:09 node-5 puppet-user[10997]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 23 16:39:10 node-5 puppet-user[10997]: Compiled catalog for node-5.domain.tld in environment production in 0.18 seconds
Jul 23 16:39:10 node-5 puppet-user[10997]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 23 16:39:10 node-5 puppet-user[10997]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 23 16:39:10 node-5 puppet-user[10997]: (/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 23 16:39:11 node-5 puppet-user[10997]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Jul 23 16:39:11 node-5 puppet-user[10997]: Finished catalog run in 1.17 seconds
Jul 23 16:39:11 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 16:39:11 node-5 nailgun-agent: D, [2016-07-23T16:39:01.730779 #9006] DEBUG -- : Sleep for 10 seconds before sending request
Jul 23 16:39:11 node-5 nailgun-agent: I, [2016-07-23T16:39:11.745347 #9006]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 23 16:39:12 node-5 nailgun-agent: D, [2016-07-23T16:39:12.291328 #9006] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 23 16:39:12 node-5 puppet-user[11650]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 23 16:39:13 node-5 puppet-user[11650]: Compiled catalog for node-5.domain.tld in environment production in 0.35 seconds
Jul 23 16:39:13 node-5 puppet-user[11650]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 23 16:39:13 node-5 puppet-user[11650]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Jul 23 16:39:13 node-5 puppet-user[11650]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 23 16:39:13 node-5 puppet-user[11650]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 23 16:39:13 node-5 puppet-user[11650]: (/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 23 16:39:13 node-5 puppet-user[11650]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 23 16:39:13 node-5 puppet-user[11650]: Finished catalog run in 0.45 seconds
Jul 23 16:39:15 node-5 puppet-user[12161]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 23 16:39:15 node-5 puppet-user[12161]: Compiled catalog for node-5.domain.tld in environment production in 0.19 seconds
Jul 23 16:39:15 node-5 puppet-user[12161]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 23 16:39:15 node-5 kernel: [   67.014544] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 23 16:39:15 node-5 kernel: [   67.014593] 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 23 16:39:15 node-5 puppet-user[12161]: (/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 23 16:39:15 node-5 puppet-user[12161]: Finished catalog run in 0.08 seconds
Jul 23 16:39:17 node-5 puppet-user[12619]: (Scope(Class[main])) MODULAR: sync_time
Jul 23 16:39:17 node-5 puppet-user[12619]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 23 16:39:17 node-5 ntpdate[13042]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 23 16:39:23 node-5 ntpdate[13042]: adjust time server 10.20.0.2 offset 0.001998 sec
Jul 23 16:39:23 node-5 puppet-user[12619]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 23 16:39:23 node-5 puppet-user[12619]: Finished catalog run in 6.20 seconds
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.221191 #9006] DEBUG -- : Trying to find block devices
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.221303 #9006] DEBUG -- : Found block device: sda
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.221341 #9006] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.221363 #9006] DEBUG -- : Trying to get list of physical devices
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.221513 #9006] DEBUG -- : Getting udev properties for device: sda
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.223462 #9006] 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"=>"0x618e72837273a8901cc7884
Jul 23 16:39:24 node-5 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"20880", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.223491 #9006] DEBUG -- : Trying to find out if device sda is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.223554 #9006] DEBUG -- : Device sda removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.223570 #9006] DEBUG -- : Device sda seems to be appropriate
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.224008 #9006] DEBUG -- : Getting udev properties for device: dm-0
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.225595 #9006] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-nbsPcbppeR0UCeZJJIk29uq20URvjr4Fcc7iESd8vGpkQwA3z3xaNRr7R22cqLOp /dev/disk/by-uuid/28baf5d7-03a4-4ad0-92d1-0ab435835261 /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-nbsPcbppeR0UCeZJJIk29uq20URvjr4Fcc7iESd8vGpkQwA3z3xaNRr7R22cqLOp", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"28baf5d7-03a4-4ad0-92d1-0ab435835261", "ID_FS_UUID_ENC"=>"28baf5d7-03a4-4ad0-92d1-0ab435835261", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95
Jul 23 16:39:24 node-5 nailgun-agent: 486", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.225623 #9006] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.225655 #9006] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.225682 #9006] DEBUG -- : Device dm-0 seems to be appropriate
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.225698 #9006] DEBUG -- : Getting udev properties for device: dm-1
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.227303 #9006] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-4VSMCxzIWPIDKNwbdqFIltegFS0NfBLQ8JGeivte4BrCg4TBj69eL4K7Kv0MRvNx /dev/disk/by-uuid/d895a0df-c6f8-4493-b12c-f20beb55b350 /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-4VSMCxzIWPIDKNwbdqFIltegFS0NfBLQ8JGeivte4BrCg4TBj69eL4K7Kv0MRvNx", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d895a0df-c6f8-4493-b12c-f20beb55b350", "ID_FS_UUID_ENC"=>"d895a0df-c6f8-4493-b12c-f20beb55b350", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"19627", "nomdmonddf"=>"1", "nomd
Jul 23 16:39:24 node-5 nailgun-agent: monisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.227330 #9006] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.227363 #9006] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.227379 #9006] DEBUG -- : Device dm-1 seems to be appropriate
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.227420 #9006] DEBUG -- : Getting udev properties for device: dm-2
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.228936 #9006] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-tB8R85zT0Wl6sQms3Q59XvSeYUbLxl5FNLkiF30dpPicoXQfFLM6014f0JgBw7k2 /dev/disk/by-uuid/573b60a8-72a4-463d-aba3-d1baa8362b80 /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-tB8R85zT0Wl6sQms3Q59XvSeYUbLxl5FNLkiF30dpPicoXQfFLM6014f0JgBw7k2", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"573b60a8-72a4-463d-aba3-d1baa8362b80", "ID_FS_UUID_ENC"=>"573b60a8-72a4-463d-aba3-d1baa8362b80", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"26
Jul 23 16:39:24 node-5 nailgun-agent: 685", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.228963 #9006] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.228997 #9006] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.229058 #9006] DEBUG -- : Device dm-2 seems to be appropriate
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.229074 #9006] DEBUG -- : Getting udev properties for device: dm-3
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.230608 #9006] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-BpNXfRQKLBluLsczsg3XeeoeEKIBl0kGvlNemlFNMD080fipKkdfqFSSuHefoBpN /dev/disk/by-uuid/3aa9d591-dff2-4fa1-9dc9-0c8b718d2cdd /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-BpNXfRQKLBluLsczsg3XeeoeEKIBl0kGvlNemlFNMD080fipKkdfqFSSuHefoBpN", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"3aa9d591-dff2-4fa1-9dc9-0c8b718d2cdd", "ID_FS_UUID_ENC"=>"3aa9d591-dff2-4fa1-9dc9-0c8b718d2cdd", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37051", "nomdmond
Jul 23 16:39:24 node-5 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.230662 #9006] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.230709 #9006] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.230724 #9006] DEBUG -- : Device dm-3 seems to be appropriate
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.230739 #9006] DEBUG -- : Getting udev properties for device: dm-4
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.232285 #9006] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-wIkEPotECFqu7Vq3kkSBvycFJcPRluWU3nF6OUmrM5fgd2iaxdzennAAEK0oflHy /dev/disk/by-uuid/862eb905-0ca3-4c86-ba46-eb74ea3db5f3 /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-wIkEPotECFqu7Vq3kkSBvycFJcPRluWU3nF6OUmrM5fgd2iaxdzennAAEK0oflHy", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"862eb905-0ca3-4c86-ba46-eb74ea3db5f3", "ID_FS_UUID_ENC"=>"862eb905-0ca3-4c86-ba46-eb74ea3db5f3", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"47238", "nomdmonddf"=>"1", 
Jul 23 16:39:24 node-5 nailgun-agent: "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.232312 #9006] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.232357 #9006] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.232387 #9006] DEBUG -- : Device dm-4 seems to be appropriate
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.232403 #9006] DEBUG -- : Getting udev properties for device: dm-5
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.233962 #9006] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-6dQjW7Pm7Klbef7aBqifwYCXAlRX6kxmg5LlfWvjXmGcuQGWSQ1P8sjibIHLBGYy /dev/disk/by-uuid/3ede14ae-128c-44eb-9b83-0af5a649e292 /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-6dQjW7Pm7Klbef7aBqifwYCXAlRX6kxmg5LlfWvjXmGcuQGWSQ1P8sjibIHLBGYy", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"3ede14ae-128c-44eb-9b83-0af5a649e292", "ID_FS_UUID_ENC"=>"3ede14ae-128c-44eb-9b83-0af5a649e292", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52170", "nomdmonddf"=>"1", "nomd
Jul 23 16:39:24 node-5 nailgun-agent: monisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.234032 #9006] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.234080 #9006] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.234095 #9006] DEBUG -- : Device dm-5 seems to be appropriate
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.234110 #9006] DEBUG -- : Getting udev properties for device: dm-6
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.235609 #9006] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-6dQjW7Pm7Klbef7aBqifwYCXAlRX6kxm76pqYD4QmUjElNdiQ2rwEQUBSjCOP3MH /dev/disk/by-uuid/5b4b99e5-b896-4ce4-af85-617afca2c955 /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-6dQjW7Pm7Klbef7aBqifwYCXAlRX6kxm76pqYD4QmUjElNdiQ2rwEQUBSjCOP3MH", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"5b4b99e5-b896-4ce4-af85-617afca2c955", "ID_FS_UUID_ENC"=>"5b4b99e5-b896-4ce4-af85-617afca2c955", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52523", "nomdmonddf"=>"1", "nomdmonisw"
Jul 23 16:39:24 node-5 nailgun-agent: =>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.235633 #9006] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.235682 #9006] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.235709 #9006] DEBUG -- : Device dm-6 seems to be appropriate
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.235723 #9006] DEBUG -- : Getting udev properties for device: ram0
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.237144 #9006] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55184", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.237203 #9006] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.237250 #9006] DEBUG -- : Device ram0 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.237271 #9006] DEBUG -- : Getting udev properties for device: ram1
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.238814 #9006] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55191", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.238840 #9006] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.238879 #9006] DEBUG -- : Device ram1 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.238910 #9006] DEBUG -- : Getting udev properties for device: ram2
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.240302 #9006] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55251", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.240329 #9006] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.240362 #9006] DEBUG -- : Device ram2 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.240399 #9006] DEBUG -- : Getting udev properties for device: ram3
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.241834 #9006] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55266", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.241859 #9006] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.241903 #9006] DEBUG -- : Device ram3 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.241934 #9006] DEBUG -- : Getting udev properties for device: ram4
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.243318 #9006] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55282", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.243345 #9006] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.243392 #9006] DEBUG -- : Device ram4 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.243413 #9006] DEBUG -- : Getting udev properties for device: ram5
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.244824 #9006] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55299", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.244850 #9006] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.244908 #9006] DEBUG -- : Device ram5 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.244929 #9006] DEBUG -- : Getting udev properties for device: ram6
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.246314 #9006] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55315", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.246341 #9006] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.246381 #9006] DEBUG -- : Device ram6 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.246402 #9006] DEBUG -- : Getting udev properties for device: ram7
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.247810 #9006] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55354", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.247852 #9006] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.247893 #9006] DEBUG -- : Device ram7 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.247914 #9006] DEBUG -- : Getting udev properties for device: ram8
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.249300 #9006] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55386", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.249325 #9006] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.249360 #9006] DEBUG -- : Device ram8 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.249404 #9006] DEBUG -- : Getting udev properties for device: ram9
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.250800 #9006] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55410", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.250826 #9006] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.250887 #9006] DEBUG -- : Device ram9 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.250907 #9006] DEBUG -- : Getting udev properties for device: loop0
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.252286 #9006] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55120", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.252322 #9006] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.252370 #9006] DEBUG -- : Device loop0 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.252400 #9006] DEBUG -- : Getting udev properties for device: loop1
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.253816 #9006] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55132", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.253841 #9006] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.253908 #9006] DEBUG -- : Device loop1 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.253929 #9006] DEBUG -- : Getting udev properties for device: loop2
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.255297 #9006] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55141", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.255332 #9006] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.255368 #9006] DEBUG -- : Device loop2 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.255400 #9006] DEBUG -- : Getting udev properties for device: loop3
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.256765 #9006] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55148", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.256791 #9006] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.256829 #9006] DEBUG -- : Device loop3 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.256861 #9006] DEBUG -- : Getting udev properties for device: loop4
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.258285 #9006] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55156", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.258307 #9006] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.258340 #9006] DEBUG -- : Device loop4 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.258359 #9006] DEBUG -- : Getting udev properties for device: loop5
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.259729 #9006] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55163", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.259761 #9006] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.259800 #9006] DEBUG -- : Device loop5 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.259823 #9006] DEBUG -- : Getting udev properties for device: loop6
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.261173 #9006] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55170", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.261194 #9006] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.261240 #9006] DEBUG -- : Device loop6 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.261259 #9006] DEBUG -- : Getting udev properties for device: loop7
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.262638 #9006] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55177", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.262660 #9006] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.262703 #9006] DEBUG -- : Device loop7 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.262734 #9006] DEBUG -- : Getting udev properties for device: ram10
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.264095 #9006] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55198", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.264116 #9006] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.264147 #9006] DEBUG -- : Device ram10 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.264165 #9006] DEBUG -- : Getting udev properties for device: ram11
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.265524 #9006] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55206", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.265548 #9006] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.265596 #9006] DEBUG -- : Device ram11 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.265616 #9006] DEBUG -- : Getting udev properties for device: ram12
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.266991 #9006] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55213", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.267012 #9006] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.267062 #9006] DEBUG -- : Device ram12 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.267080 #9006] DEBUG -- : Getting udev properties for device: ram13
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.268435 #9006] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55221", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.268455 #9006] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.268507 #9006] DEBUG -- : Device ram13 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.268526 #9006] DEBUG -- : Getting udev properties for device: ram14
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.273490 #9006] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55228", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.273518 #9006] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.273560 #9006] DEBUG -- : Device ram14 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.273580 #9006] DEBUG -- : Getting udev properties for device: ram15
Jul 23 16:39:24 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275123 #9006] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"55237", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275144 #9006] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275186 #9006] DEBUG -- : Device ram15 removable parameter: "0"
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275218 #9006] 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 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275232 #9006] DEBUG -- : Block device seems to be physical data storage: sda
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275265 #9006] DEBUG -- : Found block device: dm-0
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275335 #9006] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275348 #9006] DEBUG -- : Found block device: dm-1
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275359 #9006] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275368 #9006] DEBUG -- : Found block device: dm-2
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275379 #9006] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275388 #9006] DEBUG -- : Found block device: dm-3
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275398 #9006] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275407 #9006] DEBUG -- : Found block device: dm-4
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275417 #9006] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275463 #9006] DEBUG -- : Found block device: dm-5
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275473 #9006] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275482 #9006] DEBUG -- : Found block device: dm-6
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275492 #9006] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275501 #9006] DEBUG -- : Found block device: ram0
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275511 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275520 #9006] DEBUG -- : Found block device: ram1
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275529 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275538 #9006] DEBUG -- : Found block device: ram2
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275578 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275587 #9006] DEBUG -- : Found block device: ram3
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275597 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275606 #9006] DEBUG -- : Found block device: ram4
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275617 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275626 #9006] DEBUG -- : Found block device: ram5
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275635 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275645 #9006] DEBUG -- : Found block device: ram6
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275655 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275695 #9006] DEBUG -- : Found block device: ram7
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275706 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275716 #9006] DEBUG -- : Found block device: ram8
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275726 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275735 #9006] DEBUG -- : Found block device: ram9
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275744 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275753 #9006] DEBUG -- : Found block device: loop0
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275763 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275771 #9006] DEBUG -- : Found block device: loop1
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275780 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275820 #9006] DEBUG -- : Found block device: loop2
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275832 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275841 #9006] DEBUG -- : Found block device: loop3
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275851 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275860 #9006] DEBUG -- : Found block device: loop4
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275870 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275879 #9006] DEBUG -- : Found block device: loop5
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275889 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275898 #9006] DEBUG -- : Found block device: loop6
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275945 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275954 #9006] DEBUG -- : Found block device: loop7
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275965 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275974 #9006] DEBUG -- : Found block device: ram10
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275983 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.275992 #9006] DEBUG -- : Found block device: ram11
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.276001 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.276011 #9006] DEBUG -- : Found block device: ram12
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.276022 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.276061 #9006] DEBUG -- : Found block device: ram13
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.276072 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.276081 #9006] DEBUG -- : Found block device: ram14
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.276091 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.276100 #9006] DEBUG -- : Found block device: ram15
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.276110 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.276137 #9006] 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 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.333782 #9006] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 23 16:39:24 node-5 nailgun-agent: D, [2016-07-23T16:39:24.333861 #9006] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 23 16:39:30 node-5 kernel: [   81.705292] init: plymouth-upstart-bridge main process ended, respawning
Jul 23 16:39:30 node-5 puppet-agent[8957]: Could not run: SIGTERM
Jul 23 16:39:30 node-5 kernel: [   81.982471] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 23 16:39:30 node-5 ec2: 
Jul 23 16:39:30 node-5 ec2: #############################################################
Jul 23 16:39:30 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 23 16:39:30 node-5 ec2: 1024 f5:8c:19:85:e0:73:cb:84:f5:32:c8:9d:20:f6:65:72  root@node-5.domain.tld (DSA)
Jul 23 16:39:30 node-5 ec2: 256 e7:6c:be:53:03:d1:a3:bf:d0:b9:d3:c2:4d:eb:3d:65  root@node-5.domain.tld (ECDSA)
Jul 23 16:39:30 node-5 ec2: 256 e3:41:8c:5e:e0:c7:43:e2:d6:3e:22:a4:9b:18:32:ec  root@node-5.domain.tld (ED25519)
Jul 23 16:39:30 node-5 ec2: 2048 7c:cc:ee:eb:54:7b:9b:05:15:7f:2d:a2:6f:fc:a7:99  root@node-5.domain.tld (RSA)
Jul 23 16:39:30 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 23 16:39:30 node-5 ec2: #############################################################
Jul 23 16:39:36 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371483 #9006] DEBUG -- : Trying to find block devices
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371570 #9006] DEBUG -- : Found block device: sda
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371615 #9006] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371634 #9006] DEBUG -- : Block device seems to be physical data storage: sda
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371659 #9006] DEBUG -- : Found block device: dm-0
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371675 #9006] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371700 #9006] DEBUG -- : Found block device: dm-1
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371712 #9006] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371723 #9006] DEBUG -- : Found block device: dm-2
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371744 #9006] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371755 #9006] DEBUG -- : Found block device: dm-3
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371766 #9006] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371777 #9006] DEBUG -- : Found block device: dm-4
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371801 #9006] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371810 #9006] DEBUG -- : Found block device: dm-5
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371821 #9006] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371830 #9006] DEBUG -- : Found block device: dm-6
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371859 #9006] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371869 #9006] DEBUG -- : Found block device: ram0
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371880 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371889 #9006] DEBUG -- : Found block device: ram1
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371900 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371910 #9006] DEBUG -- : Found block device: ram2
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371920 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371952 #9006] DEBUG -- : Found block device: ram3
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371963 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371973 #9006] DEBUG -- : Found block device: ram4
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371983 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.371993 #9006] DEBUG -- : Found block device: ram5
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372004 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372012 #9006] DEBUG -- : Found block device: ram6
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372022 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372030 #9006] DEBUG -- : Found block device: ram7
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372040 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372077 #9006] DEBUG -- : Found block device: ram8
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372088 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372098 #9006] DEBUG -- : Found block device: ram9
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372108 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372117 #9006] DEBUG -- : Found block device: loop0
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372128 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372136 #9006] DEBUG -- : Found block device: loop1
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372145 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372155 #9006] DEBUG -- : Found block device: loop2
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372164 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372193 #9006] DEBUG -- : Found block device: loop3
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372203 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372213 #9006] DEBUG -- : Found block device: loop4
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372222 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372231 #9006] DEBUG -- : Found block device: loop5
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372241 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372249 #9006] DEBUG -- : Found block device: loop6
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372258 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372266 #9006] DEBUG -- : Found block device: loop7
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372291 #9006] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372300 #9006] DEBUG -- : Found block device: ram10
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372310 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372318 #9006] DEBUG -- : Found block device: ram11
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372327 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372336 #9006] DEBUG -- : Found block device: ram12
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372346 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372354 #9006] DEBUG -- : Found block device: ram13
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372363 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372372 #9006] DEBUG -- : Found block device: ram14
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372400 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372410 #9006] DEBUG -- : Found block device: ram15
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372420 #9006] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.372447 #9006] 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 23 16:39:36 node-5 nailgun-agent: D, [2016-07-23T16:39:36.557324 #9006] DEBUG -- : Response: status: 200 body: {"id": 5}
Jul 23 16:39:36 node-5 nailgun-agent: I, [2016-07-23T16:39:36.557544 #9006]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 23 16:40:01 node-5 CRON[13877]: (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 23 16:40:12 node-5 puppet-user[13907]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 23 16:40:12 node-5 puppet-user[13907]: Compiled catalog for node-5.domain.tld in environment production in 0.11 seconds
Jul 23 16:40:12 node-5 puppet-user[13907]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 23 16:40:12 node-5 puppet-user[13907]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 23 16:40:12 node-5 puppet-user[13907]: Finished catalog run in 0.08 seconds
Jul 23 16:40:14 node-5 puppet-user[14362]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 23 16:40:15 node-5 puppet-user[14362]: Compiled catalog for node-5.domain.tld in environment production in 1.01 seconds
Jul 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:16 node-5 puppet-user[14362]: (/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 23 16:40:29 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 16:40:29 node-5 nailgun-agent: I, [2016-07-23T16:40:29.737509 #13880]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 23 16:40:33 node-5 puppet-user[14362]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 23 16:40:33 node-5 puppet-user[14362]: Finished catalog run in 17.51 seconds
Jul 23 16:40:35 node-5 puppet-user[15420]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 23 16:40:35 node-5 puppet-user[15420]: Compiled catalog for node-5.domain.tld in environment production in 0.12 seconds
Jul 23 16:40:40 node-5 puppet-user[15420]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 23 16:40:42 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 16:40:42 node-5 nailgun-agent: I, [2016-07-23T16:40:42.977507 #13880]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 23 16:41:01 node-5 CRON[17300]: (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 23 16:41:08 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 16:41:08 node-5 nailgun-agent: I, [2016-07-23T16:41:08.163661 #17303]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 23 16:41:14 node-5 puppet-user[15420]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 23 16:41:14 node-5 puppet-user[15420]: Finished catalog run in 38.61 seconds
Jul 23 16:41:16 node-5 puppet-user[18280]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 23 16:41:17 node-5 puppet-user[18280]: Compiled catalog for node-5.domain.tld in environment production in 0.56 seconds
Jul 23 16:41:17 node-5 puppet-user[18280]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 23 16:41:17 node-5 puppet-user[18280]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 23 16:41:17 node-5 puppet-user[18280]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 23 16:41:17 node-5 puppet-user[18280]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 23 16:41:17 node-5 puppet-user[18280]: Finished catalog run in 0.12 seconds
Jul 23 16:41:19 node-5 puppet-user[18754]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 23 16:41:19 node-5 puppet-user[18754]: Compiled catalog for node-5.domain.tld in environment production in 0.83 seconds
Jul 23 16:41:20 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 23 16:41:20 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 23 16:41:20 node-5 crontab[19199]: (root) LIST (root)
Jul 23 16:41:20 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 23 16:41:20 node-5 crontab[19202]: (root) REPLACE (root)
Jul 23 16:41:21 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 23 16:41:21 node-5 nailgun-agent: I, [2016-07-23T16:41:21.244886 #17303]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 23 16:41:22 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 23 16:41:23 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/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 23 16:41:24 node-5 puppet-user[18754]: (/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 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/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 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/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 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/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 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/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 23 16:41:24 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 23 16:41:24 node-5 puppet-user[18754]: (/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 23 16:41:24 node-5 puppet-user[18754]: (/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 23 16:41:25 node-5 puppet-user[18754]: (/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 23 16:41:25 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 23 16:41:25 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 23 16:41:25 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 23 16:41:25 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 23 16:41:25 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 23 16:41:25 node-5 puppet-user[18754]: (/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 23 16:41:25 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 23 16:41:25 node-5 puppet-user[18754]: (/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 23 16:41:25 node-5 puppet-user[18754]: (/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 23 16:41:25 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 23 16:41:25 node-5 puppet-user[18754]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 23 16:41:25 node-5 puppet-user[18754]: (/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 23 16:41:25 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8408" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 23 16:41:25 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 23 16:41:27 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:27 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:27 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:27 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:27 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:27 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:47 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:47 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:47 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:47 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:47 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:47 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:47 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:50 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:50 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:50 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:50 node-5 multipathd: uevent trigger error
<27>Jul 23 16:41:50 node-5 multipathd: uevent trigger error
<27>Jul 23 16:42:50 node-5 ntpdate[29521]: no servers can be used, exiting
<27>Jul 23 16:43:22 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:22 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:22 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:22 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:22 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:25 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:25 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:25 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:25 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:25 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:37 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:37 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:37 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:37 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:37 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:37 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:40 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:40 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:40 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:40 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:40 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:43:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:30 node-5 multipathd: uevent trigger error
<43>Jul 23 16:44:45 node-5 apache2_error [Sat Jul 23 16:44:43.471839 2016] [mpm_event:notice] [pid 9251:tid 140449196169088] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 23 16:44:45 node-5 apache2_error [Sat Jul 23 16:44:43.472032 2016] [core:notice] [pid 9251:tid 140449196169088] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 16:44:51 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:51 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:51 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:51 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:51 node-5 multipathd: uevent trigger error
<27>Jul 23 16:44:51 node-5 multipathd: uevent trigger error
<43>Jul 23 16:44:55 node-5 apache2_error [Sat Jul 23 16:44:46.746551 2016] [mpm_event:notice] [pid 9251:tid 140449196169088] AH00491: caught SIGTERM, shutting down
<43>Jul 23 16:44:55 node-5 apache2_error [Sat Jul 23 16:44:47.839718 2016] [mpm_worker:notice] [pid 9561:tid 139925059008384] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 23 16:44:55 node-5 apache2_error [Sat Jul 23 16:44:47.839762 2016] [core:notice] [pid 9561:tid 139925059008384] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 16:45:31 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 23 16:45:34 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:34 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:34 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:34 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:34 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:34 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:38 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:38 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:38 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:38 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:38 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:38 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:52 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:52 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:52 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:52 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:52 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:58 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:58 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:58 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:58 node-5 multipathd: uevent trigger error
<27>Jul 23 16:45:58 node-5 multipathd: uevent trigger error
<129>Jul 23 16:45:58 node-5 haproxy[19602]: Server odl-jetty/node-1 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 23 16:45:58 node-5 haproxy[19602]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:01 node-5 haproxy[20664]: 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 23 16:46:02 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:02 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:02 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:02 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:02 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:02 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:03 node-5 haproxy[20664]: Server odl-jetty/node-1 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 23 16:46:03 node-5 haproxy[20664]: proxy odl-jetty has no server available!
<27>Jul 23 16:46:05 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:05 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:05 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:05 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:05 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:05 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:08 node-5 haproxy[20664]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer4 timeout, check duration: 5000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 23 16:46:08 node-5 haproxy[20664]: proxy odl-neutron-endpoint has no server available!
<129>Jul 23 16:46:08 node-5 haproxy[22686]: 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 23 16:46:09 node-5 haproxy[22690]: 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 23 16:46:11 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:11 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:11 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:11 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:11 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:12 node-5 haproxy[22690]: Server odl-jetty/node-1 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 23 16:46:12 node-5 haproxy[22690]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:13 node-5 haproxy[23757]: 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 23 16:46:14 node-5 haproxy[23764]: 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 23 16:46:14 node-5 haproxy[23764]: 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 23 16:46:15 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:15 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:15 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:15 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:15 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:15 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:17 node-5 haproxy[23764]: Server odl-jetty/node-1 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 23 16:46:17 node-5 haproxy[23764]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:18 node-5 haproxy[24979]: 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 23 16:46:18 node-5 haproxy[24979]: 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 23 16:46:19 node-5 haproxy[24983]: 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 23 16:46:19 node-5 haproxy[24983]: 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 23 16:46:20 node-5 haproxy[24983]: 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 23 16:46:20 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:20 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:20 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:20 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:21 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:22 node-5 haproxy[24983]: Server odl-jetty/node-1 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 23 16:46:22 node-5 haproxy[24983]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:23 node-5 haproxy[26049]: 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 23 16:46:23 node-5 haproxy[26049]: 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 23 16:46:23 node-5 haproxy[26049]: 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 23 16:46:24 node-5 haproxy[26053]: 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 23 16:46:24 node-5 haproxy[26053]: 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 23 16:46:24 node-5 haproxy[26053]: 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 23 16:46:25 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:25 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:25 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:25 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:25 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:25 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:26 node-5 haproxy[26053]: Server aodh/node-1 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 23 16:46:26 node-5 haproxy[26053]: Server aodh/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 23 16:46:26 node-5 haproxy[26053]: proxy aodh has no server available!
<129>Jul 23 16:46:27 node-5 haproxy[26053]: Server odl-jetty/node-1 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 23 16:46:27 node-5 haproxy[26053]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:28 node-5 haproxy[27114]: 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 23 16:46:28 node-5 haproxy[27114]: 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 23 16:46:28 node-5 haproxy[27114]: 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 23 16:46:29 node-5 haproxy[27118]: 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 23 16:46:29 node-5 haproxy[27118]: 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 23 16:46:29 node-5 haproxy[27118]: 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 23 16:46:29 node-5 haproxy[27118]: 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 23 16:46:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:30 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:31 node-5 haproxy[27118]: Server aodh/node-1 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 23 16:46:31 node-5 haproxy[27118]: Server aodh/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 23 16:46:31 node-5 haproxy[27118]: proxy aodh has no server available!
<129>Jul 23 16:46:31 node-5 haproxy[27118]: Server ceilometer/node-1 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 23 16:46:31 node-5 haproxy[27118]: Server ceilometer/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 23 16:46:31 node-5 haproxy[27118]: proxy ceilometer has no server available!
<129>Jul 23 16:46:32 node-5 haproxy[27118]: Server odl-jetty/node-1 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 23 16:46:32 node-5 haproxy[27118]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:33 node-5 haproxy[28341]: 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 23 16:46:33 node-5 haproxy[28341]: 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 23 16:46:33 node-5 haproxy[28341]: 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 23 16:46:33 node-5 haproxy[28341]: 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 23 16:46:34 node-5 haproxy[28345]: 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 23 16:46:34 node-5 haproxy[28345]: 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 23 16:46:34 node-5 haproxy[28345]: 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 23 16:46:35 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:35 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:35 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:35 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:35 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:36 node-5 haproxy[28345]: Server aodh/node-1 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 23 16:46:36 node-5 haproxy[28345]: Server aodh/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 23 16:46:36 node-5 haproxy[28345]: proxy aodh has no server available!
<129>Jul 23 16:46:36 node-5 haproxy[28345]: Server ceilometer/node-1 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 23 16:46:36 node-5 haproxy[28345]: Server ceilometer/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 23 16:46:36 node-5 haproxy[28345]: proxy ceilometer has no server available!
<129>Jul 23 16:46:36 node-5 haproxy[28345]: Server odl-jetty/node-1 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 23 16:46:36 node-5 haproxy[28345]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:38 node-5 haproxy[29417]: 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 23 16:46:38 node-5 haproxy[29417]: 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 23 16:46:38 node-5 haproxy[29417]: 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 23 16:46:39 node-5 haproxy[29421]: 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 23 16:46:39 node-5 haproxy[29421]: 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 23 16:46:39 node-5 haproxy[29421]: 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 23 16:46:39 node-5 haproxy[29421]: 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 23 16:46:40 node-5 haproxy[29421]: Server horizon/node-1 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 23 16:46:40 node-5 haproxy[29421]: Server horizon/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 23 16:46:40 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:40 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:40 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:40 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:40 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:41 node-5 haproxy[29421]: Server aodh/node-1 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 23 16:46:41 node-5 haproxy[29421]: Server aodh/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 23 16:46:41 node-5 haproxy[29421]: proxy aodh has no server available!
<129>Jul 23 16:46:41 node-5 haproxy[29421]: Server ceilometer/node-1 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 23 16:46:41 node-5 haproxy[29421]: Server ceilometer/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 23 16:46:41 node-5 haproxy[29421]: proxy ceilometer has no server available!
<129>Jul 23 16:46:41 node-5 haproxy[29421]: Server odl-jetty/node-1 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 23 16:46:41 node-5 haproxy[29421]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:43 node-5 haproxy[30530]: 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 23 16:46:43 node-5 haproxy[30530]: 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 23 16:46:44 node-5 haproxy[30539]: 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 23 16:46:44 node-5 haproxy[30539]: 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 23 16:46:44 node-5 haproxy[30539]: 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 23 16:46:44 node-5 haproxy[30539]: 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 23 16:46:44 node-5 haproxy[30539]: 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 23 16:46:44 node-5 haproxy[30539]: 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 23 16:46:45 node-5 haproxy[30539]: 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 23 16:46:45 node-5 haproxy[30539]: 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 23 16:46:45 node-5 haproxy[30539]: Server horizon/node-1 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 23 16:46:45 node-5 haproxy[30539]: Server horizon/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.
<27>Jul 23 16:46:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:46 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:46 node-5 haproxy[30539]: Server glance-registry/node-1 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 23 16:46:46 node-5 haproxy[30539]: Server glance-registry/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 23 16:46:46 node-5 haproxy[30539]: proxy glance-registry has no server available!
<129>Jul 23 16:46:46 node-5 haproxy[30539]: Server aodh/node-1 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 23 16:46:47 node-5 haproxy[30539]: Server aodh/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 23 16:46:47 node-5 haproxy[30539]: proxy aodh has no server available!
<129>Jul 23 16:46:47 node-5 haproxy[30539]: Server ceilometer/node-1 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 23 16:46:47 node-5 haproxy[30539]: Server ceilometer/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 23 16:46:47 node-5 haproxy[30539]: proxy ceilometer has no server available!
<129>Jul 23 16:46:47 node-5 haproxy[30539]: Server odl-jetty/node-1 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 23 16:46:47 node-5 haproxy[30539]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:49 node-5 haproxy[31636]: 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 23 16:46:49 node-5 haproxy[31636]: 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 23 16:46:49 node-5 haproxy[31636]: 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 23 16:46:49 node-5 haproxy[31636]: 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 23 16:46:49 node-5 haproxy[31636]: 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 23 16:46:49 node-5 haproxy[31636]: 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 23 16:46:49 node-5 haproxy[31636]: 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 23 16:46:50 node-5 haproxy[31636]: 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 23 16:46:50 node-5 haproxy[31636]: 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 23 16:46:50 node-5 haproxy[31636]: 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 23 16:46:50 node-5 haproxy[31636]: 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 23 16:46:50 node-5 haproxy[31636]: 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 23 16:46:50 node-5 haproxy[31636]: 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 23 16:46:50 node-5 haproxy[31636]: Server horizon/node-1 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 23 16:46:50 node-5 haproxy[31636]: Server horizon/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 23 16:46:51 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:51 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:51 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:51 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:51 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:51 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:51 node-5 haproxy[31636]: Server glance-registry/node-1 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 23 16:46:51 node-5 haproxy[31636]: Server glance-registry/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 23 16:46:51 node-5 haproxy[31636]: proxy glance-registry has no server available!
<129>Jul 23 16:46:52 node-5 haproxy[31636]: Server aodh/node-1 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 23 16:46:52 node-5 haproxy[31636]: Server aodh/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 23 16:46:52 node-5 haproxy[31636]: proxy aodh has no server available!
<129>Jul 23 16:46:52 node-5 haproxy[31636]: Server ceilometer/node-1 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 23 16:46:52 node-5 haproxy[31636]: Server ceilometer/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 23 16:46:52 node-5 haproxy[31636]: proxy ceilometer has no server available!
<129>Jul 23 16:46:52 node-5 haproxy[31636]: Server nova-novncproxy/node-1 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 23 16:46:52 node-5 haproxy[31636]: Server nova-novncproxy/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 23 16:46:52 node-5 haproxy[31636]: proxy nova-novncproxy has no server available!
<129>Jul 23 16:46:52 node-5 haproxy[31636]: Server odl-jetty/node-1 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 23 16:46:52 node-5 haproxy[31636]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:54 node-5 haproxy[32728]: 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 23 16:46:54 node-5 haproxy[32728]: 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 23 16:46:54 node-5 haproxy[32728]: 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 23 16:46:54 node-5 haproxy[32728]: 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 23 16:46:54 node-5 haproxy[32728]: 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 23 16:46:54 node-5 haproxy[32728]: 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 23 16:46:54 node-5 haproxy[32728]: 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 23 16:46:54 node-5 haproxy[32728]: 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 23 16:46:55 node-5 haproxy[32728]: 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 23 16:46:55 node-5 haproxy[32728]: 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 23 16:46:55 node-5 haproxy[32728]: 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 23 16:46:55 node-5 haproxy[32728]: 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 23 16:46:55 node-5 haproxy[32728]: 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 23 16:46:55 node-5 haproxy[32728]: 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 23 16:46:55 node-5 haproxy[32728]: Server horizon/node-1 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 23 16:46:55 node-5 haproxy[32728]: Server horizon/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.
<27>Jul 23 16:46:56 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:56 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:56 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:56 node-5 multipathd: uevent trigger error
<27>Jul 23 16:46:56 node-5 multipathd: uevent trigger error
<129>Jul 23 16:46:57 node-5 haproxy[32728]: Server glance-registry/node-1 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 23 16:46:57 node-5 haproxy[32728]: Server glance-registry/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 23 16:46:57 node-5 haproxy[32728]: proxy glance-registry has no server available!
<129>Jul 23 16:46:57 node-5 haproxy[32728]: Server aodh/node-1 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 23 16:46:57 node-5 haproxy[32728]: Server aodh/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 23 16:46:57 node-5 haproxy[32728]: proxy aodh has no server available!
<129>Jul 23 16:46:57 node-5 haproxy[32728]: Server ceilometer/node-1 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 23 16:46:57 node-5 haproxy[32728]: Server ceilometer/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 23 16:46:57 node-5 haproxy[32728]: proxy ceilometer has no server available!
<129>Jul 23 16:46:57 node-5 haproxy[32728]: Server nova-novncproxy/node-1 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 23 16:46:57 node-5 haproxy[32728]: Server nova-novncproxy/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 23 16:46:57 node-5 haproxy[32728]: proxy nova-novncproxy has no server available!
<129>Jul 23 16:46:57 node-5 haproxy[32728]: Server odl-jetty/node-1 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 23 16:46:57 node-5 haproxy[32728]: proxy odl-jetty has no server available!
<129>Jul 23 16:46:59 node-5 haproxy[1440]: 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 23 16:46:59 node-5 haproxy[1440]: 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 23 16:46:59 node-5 haproxy[1440]: 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 23 16:46:59 node-5 haproxy[1440]: 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 23 16:47:00 node-5 haproxy[1444]: 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 23 16:47:00 node-5 haproxy[1444]: 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 23 16:47:00 node-5 haproxy[1444]: 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 23 16:47:00 node-5 haproxy[1444]: 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 23 16:47:00 node-5 haproxy[1444]: 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 23 16:47:00 node-5 haproxy[1444]: 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 23 16:47:00 node-5 haproxy[1444]: 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 23 16:47:00 node-5 haproxy[1444]: 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 23 16:47:00 node-5 haproxy[1444]: 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 23 16:47:00 node-5 haproxy[1444]: 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 23 16:47:01 node-5 haproxy[1444]: 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 23 16:47:01 node-5 haproxy[1444]: 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 23 16:47:01 node-5 haproxy[1444]: 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 23 16:47:01 node-5 haproxy[1444]: Server horizon/node-1 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 23 16:47:01 node-5 haproxy[1444]: Server horizon/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.
<27>Jul 23 16:47:02 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:02 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:02 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:02 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:02 node-5 multipathd: uevent trigger error
<129>Jul 23 16:47:02 node-5 haproxy[1444]: Server glance-registry/node-1 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 23 16:47:02 node-5 haproxy[1444]: Server glance-registry/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 23 16:47:02 node-5 haproxy[1444]: proxy glance-registry has no server available!
<129>Jul 23 16:47:02 node-5 haproxy[1444]: Server aodh/node-1 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 23 16:47:02 node-5 haproxy[1444]: Server aodh/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 23 16:47:02 node-5 haproxy[1444]: proxy aodh has no server available!
<129>Jul 23 16:47:02 node-5 haproxy[1444]: Server ceilometer/node-1 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 23 16:47:02 node-5 haproxy[1444]: Server ceilometer/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 23 16:47:02 node-5 haproxy[1444]: proxy ceilometer has no server available!
<129>Jul 23 16:47:03 node-5 haproxy[1444]: Server nova-novncproxy/node-1 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 23 16:47:03 node-5 haproxy[1444]: Server nova-novncproxy/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 23 16:47:03 node-5 haproxy[1444]: proxy nova-novncproxy has no server available!
<129>Jul 23 16:47:03 node-5 haproxy[1444]: Server odl-jetty/node-1 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 23 16:47:03 node-5 haproxy[1444]: proxy odl-jetty has no server available!
<27>Jul 23 16:47:05 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:05 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:05 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:05 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:05 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:08 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:08 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:08 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:08 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:08 node-5 multipathd: uevent trigger error
<129>Jul 23 16:47:09 node-5 haproxy[1444]: Server odl-neutron-endpoint/node-1 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 23 16:47:09 node-5 haproxy[1444]: proxy odl-neutron-endpoint has no server available!
<129>Jul 23 16:47:09 node-5 haproxy[1444]: Server keystone-1/node-1 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 23 16:47:09 node-5 haproxy[1444]: Server keystone-1/node-2 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 23 16:47:09 node-5 haproxy[1444]: proxy keystone-1 has no server available!
<129>Jul 23 16:47:09 node-5 haproxy[1444]: Server keystone-2/node-1 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 23 16:47:09 node-5 haproxy[1444]: Server keystone-2/node-2 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 23 16:47:09 node-5 haproxy[1444]: proxy keystone-2 has no server available!
<129>Jul 23 16:47:09 node-5 haproxy[1444]: Server nova-api/node-1 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 23 16:47:09 node-5 haproxy[1444]: Server nova-api/node-2 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 23 16:47:09 node-5 haproxy[1444]: proxy nova-api has no server available!
<129>Jul 23 16:47:09 node-5 haproxy[1444]: Server nova-metadata-api/node-1 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 23 16:47:09 node-5 haproxy[1444]: Server nova-metadata-api/node-2 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 23 16:47:09 node-5 haproxy[1444]: proxy nova-metadata-api has no server available!
<129>Jul 23 16:47:09 node-5 haproxy[1444]: Server cinder-api/node-1 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 23 16:47:09 node-5 haproxy[1444]: Backup Server cinder-api/node-2 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 23 16:47:09 node-5 haproxy[1444]: proxy cinder-api has no server available!
<129>Jul 23 16:47:10 node-5 haproxy[1444]: Server glance-api/node-1 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 23 16:47:10 node-5 haproxy[1444]: Server glance-api/node-2 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 23 16:47:10 node-5 haproxy[1444]: proxy glance-api has no server available!
<129>Jul 23 16:47:10 node-5 haproxy[1444]: Server glance-glare/node-1 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 23 16:47:10 node-5 haproxy[1444]: Server glance-glare/node-2 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 23 16:47:10 node-5 haproxy[1444]: proxy glance-glare has no server available!
<129>Jul 23 16:47:10 node-5 haproxy[1444]: Server neutron/node-1 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 23 16:47:10 node-5 haproxy[1444]: Server neutron/node-2 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 23 16:47:10 node-5 haproxy[1444]: proxy neutron has no server available!
<129>Jul 23 16:47:10 node-5 haproxy[1444]: Server mysqld/node-1 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 23 16:47:10 node-5 haproxy[1444]: Backup Server mysqld/node-2 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 23 16:47:10 node-5 haproxy[1444]: proxy mysqld has no server available!
<129>Jul 23 16:47:10 node-5 haproxy[1444]: Server object-storage/node-1 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 23 16:47:10 node-5 haproxy[1444]: Server object-storage/node-2 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 23 16:47:10 node-5 haproxy[1444]: proxy object-storage has no server available!
<129>Jul 23 16:47:10 node-5 haproxy[1444]: Server heat-api/node-1 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 23 16:47:10 node-5 haproxy[1444]: Server heat-api/node-2 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 23 16:47:10 node-5 haproxy[1444]: proxy heat-api has no server available!
<129>Jul 23 16:47:11 node-5 haproxy[1444]: Server heat-api-cfn/node-1 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 23 16:47:11 node-5 haproxy[1444]: Server heat-api-cfn/node-2 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 23 16:47:11 node-5 haproxy[1444]: proxy heat-api-cfn has no server available!
<129>Jul 23 16:47:11 node-5 haproxy[1444]: Server heat-api-cloudwatch/node-1 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 23 16:47:11 node-5 haproxy[1444]: Server heat-api-cloudwatch/node-2 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 23 16:47:11 node-5 haproxy[1444]: proxy heat-api-cloudwatch has no server available!
<27>Jul 23 16:47:19 node-5 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 23 16:47:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:44 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:45 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<43>Jul 23 16:47:45 node-5 apache2_error [Sat Jul 23 16:47:41.644794 2016] [mpm_worker:notice] [pid 9561:tid 139925059008384] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 23 16:47:45 node-5 apache2_error [Sat Jul 23 16:47:41.652982 2016] [mpm_worker:warn] [pid 9561:tid 139925059008384] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 23 16:47:45 node-5 apache2_error [Sat Jul 23 16:47:41.653741 2016] [mpm_worker:notice] [pid 9561:tid 139925059008384] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 23 16:47:45 node-5 apache2_error [Sat Jul 23 16:47:41.653754 2016] [core:notice] [pid 9561:tid 139925059008384] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 16:47:48 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:48 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:48 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:48 node-5 multipathd: uevent trigger error
<27>Jul 23 16:47:48 node-5 multipathd: uevent trigger error
<27>Jul 23 16:48:09 node-5 multipathd: uevent trigger error
<27>Jul 23 16:48:39 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 23 16:48:40 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 23 16:48:45 node-5 multipathd: uevent trigger error
<27>Jul 23 16:48:45 node-5 multipathd: uevent trigger error
<27>Jul 23 16:48:45 node-5 multipathd: uevent trigger error
<27>Jul 23 16:48:45 node-5 multipathd: uevent trigger error
<27>Jul 23 16:48:45 node-5 multipathd: uevent trigger error
<27>Jul 23 16:49:10 node-5 multipathd: uevent trigger error
<27>Jul 23 16:49:10 node-5 multipathd: uevent trigger error
<27>Jul 23 16:49:10 node-5 multipathd: uevent trigger error
<27>Jul 23 16:49:10 node-5 multipathd: uevent trigger error
<27>Jul 23 16:49:10 node-5 multipathd: uevent trigger error
<27>Jul 23 16:49:10 node-5 multipathd: uevent trigger error
<27>Jul 23 16:49:10 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 23 16:49:48 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 23 16:49:50 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 23 16:51:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:51:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:51:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:51:30 node-5 multipathd: uevent trigger error
<27>Jul 23 16:51:30 node-5 multipathd: uevent trigger error
<11>Jul 23 16:53:00 node-5 epmd: epmd: node name already occupied rabbitmq-cli-06
<11>Jul 23 16:53:38 node-5 epmd: epmd: node name already occupied rabbitmq-cli-06
<27>Jul 23 16:54:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:54:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:54:46 node-5 multipathd: uevent trigger error
<27>Jul 23 16:54:46 node-5 multipathd: uevent trigger error
<43>Jul 23 16:56:06 node-5 apache2_error [Sat Jul 23 16:56:04.033361 2016] [mpm_worker:notice] [pid 9561:tid 139925059008384] AH00295: caught SIGTERM, shutting down
<43>Jul 23 16:56:06 node-5 apache2_error [Sat Jul 23 16:56:04.785045 2016] [mpm_worker:notice] [pid 9718:tid 139817752651648] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 23 16:56:06 node-5 apache2_error [Sat Jul 23 16:56:04.785085 2016] [core:notice] [pid 9718:tid 139817752651648] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 16:56:42 node-5 multipathd: uevent trigger error
<27>Jul 23 16:56:42 node-5 multipathd: uevent trigger error
<27>Jul 23 16:56:42 node-5 multipathd: uevent trigger error
<27>Jul 23 16:56:42 node-5 multipathd: uevent trigger error
<27>Jul 23 16:56:42 node-5 multipathd: uevent trigger error
<43>Jul 23 16:56:46 node-5 apache2_error [Sat Jul 23 16:56:37.003121 2016] [mpm_worker:notice] [pid 9718:tid 139817752651648] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 23 16:56:46 node-5 apache2_error [Sat Jul 23 16:56:37.012254 2016] [mpm_worker:warn] [pid 9718:tid 139817752651648] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 23 16:56:46 node-5 apache2_error [Sat Jul 23 16:56:37.017166 2016] [mpm_worker:notice] [pid 9718:tid 139817752651648] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 23 16:56:46 node-5 apache2_error [Sat Jul 23 16:56:37.017192 2016] [core:notice] [pid 9718:tid 139817752651648] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 16:57:41 node-5 multipathd: uevent trigger error
<27>Jul 23 16:57:41 node-5 multipathd: uevent trigger error
<27>Jul 23 16:57:41 node-5 multipathd: uevent trigger error
<27>Jul 23 16:57:41 node-5 multipathd: uevent trigger error
<27>Jul 23 16:57:41 node-5 multipathd: uevent trigger error
<27>Jul 23 16:58:58 node-5 multipathd: uevent trigger error
<27>Jul 23 16:58:58 node-5 multipathd: uevent trigger error
<27>Jul 23 16:58:58 node-5 multipathd: uevent trigger error
<27>Jul 23 16:58:58 node-5 multipathd: uevent trigger error
<27>Jul 23 16:58:58 node-5 multipathd: uevent trigger error
<27>Jul 23 16:58:58 node-5 multipathd: uevent trigger error
<11>Jul 23 17:00:16 node-5 epmd: epmd: node name already occupied rabbitmq-cli-06
<27>Jul 23 17:02:42 node-5 multipathd: uevent trigger error
<27>Jul 23 17:02:42 node-5 multipathd: uevent trigger error
<27>Jul 23 17:02:42 node-5 multipathd: uevent trigger error
<27>Jul 23 17:02:42 node-5 multipathd: uevent trigger error
<27>Jul 23 17:02:42 node-5 multipathd: uevent trigger error
<27>Jul 23 17:04:51 node-5 multipathd: uevent trigger error
<27>Jul 23 17:04:51 node-5 multipathd: uevent trigger error
<27>Jul 23 17:04:51 node-5 multipathd: uevent trigger error
<27>Jul 23 17:04:51 node-5 multipathd: uevent trigger error
<27>Jul 23 17:04:51 node-5 multipathd: uevent trigger error
<27>Jul 23 17:04:51 node-5 multipathd: uevent trigger error
<27>Jul 23 17:05:58 node-5 multipathd: uevent trigger error
<27>Jul 23 17:05:58 node-5 multipathd: uevent trigger error
<27>Jul 23 17:05:58 node-5 multipathd: uevent trigger error
<27>Jul 23 17:05:58 node-5 multipathd: uevent trigger error
<27>Jul 23 17:05:58 node-5 multipathd: uevent trigger error
<27>Jul 23 17:05:58 node-5 multipathd: uevent trigger error
<27>Jul 23 17:05:58 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:34 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:34 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:34 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:34 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:34 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:34 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:34 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:43 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:43 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:43 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:43 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:43 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:43 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:43 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:48 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:48 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:48 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:48 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:48 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:48 node-5 multipathd: uevent trigger error
<27>Jul 23 17:06:48 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:10 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:10 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:10 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:10 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:10 node-5 multipathd: uevent trigger error
<27>Jul 23 17:07:10 node-5 multipathd: uevent trigger error
<43>Jul 23 17:08:07 node-5 apache2_error [Sat Jul 23 17:07:57.362221 2016] [mpm_worker:notice] [pid 9718:tid 139817752651648] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 23 17:08:07 node-5 apache2_error [Sat Jul 23 17:07:57.743158 2016] [mpm_worker:warn] [pid 9718:tid 139817752651648] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 23 17:08:07 node-5 apache2_error [Sat Jul 23 17:07:57.747827 2016] [mpm_worker:notice] [pid 9718:tid 139817752651648] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 23 17:08:07 node-5 apache2_error [Sat Jul 23 17:07:57.747858 2016] [core:notice] [pid 9718:tid 139817752651648] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 23 17:08:37 node-5 apache2_error [Sat Jul 23 17:08:34.491916 2016] [mpm_worker:notice] [pid 9718:tid 139817752651648] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 23 17:08:37 node-5 apache2_error [Sat Jul 23 17:08:34.880313 2016] [mpm_worker:warn] [pid 9718:tid 139817752651648] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 23 17:08:37 node-5 apache2_error [Sat Jul 23 17:08:34.891929 2016] [mpm_worker:notice] [pid 9718:tid 139817752651648] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 23 17:08:37 node-5 apache2_error [Sat Jul 23 17:08:34.891961 2016] [core:notice] [pid 9718:tid 139817752651648] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 23 17:08:38 node-5 multipathd: uevent trigger error
<27>Jul 23 17:08:38 node-5 multipathd: uevent trigger error
<27>Jul 23 17:08:38 node-5 multipathd: uevent trigger error
<27>Jul 23 17:08:38 node-5 multipathd: uevent trigger error
<27>Jul 23 17:08:38 node-5 multipathd: uevent trigger error
<27>Jul 23 17:08:38 node-5 multipathd: uevent trigger error
<11>Jul 23 17:09:09 node-5 epmd: epmd: node name already occupied rabbitmq-cli-06
<27>Jul 23 17:09:13 node-5 multipathd: uevent trigger error
<27>Jul 23 17:09:13 node-5 multipathd: uevent trigger error
<27>Jul 23 17:09:13 node-5 multipathd: uevent trigger error
<27>Jul 23 17:09:13 node-5 multipathd: uevent trigger error
<27>Jul 23 17:09:13 node-5 multipathd: uevent trigger error
<27>Jul 23 17:09:16 node-5 multipathd: uevent trigger error
<27>Jul 23 17:09:16 node-5 multipathd: uevent trigger error
<27>Jul 23 17:09:16 node-5 multipathd: uevent trigger error
<27>Jul 23 17:09:16 node-5 multipathd: uevent trigger error
<11>Jul 23 17:10:14 node-5 epmd: epmd: node name already occupied rabbitmq-cli-06
<27>Jul 23 17:10:39 node-5 multipathd: uevent trigger error
<27>Jul 23 17:10:39 node-5 multipathd: uevent trigger error
<27>Jul 23 17:10:39 node-5 multipathd: uevent trigger error
<27>Jul 23 17:10:39 node-5 multipathd: uevent trigger error
<27>Jul 23 17:10:39 node-5 multipathd: uevent trigger error
<27>Jul 23 17:10:39 node-5 multipathd: uevent trigger error
<27>Jul 23 17:11:28 node-5 multipathd: uevent trigger error
<27>Jul 23 17:11:28 node-5 multipathd: uevent trigger error
<27>Jul 23 17:11:28 node-5 multipathd: uevent trigger error
<27>Jul 23 17:11:28 node-5 multipathd: uevent trigger error
<27>Jul 23 17:11:41 node-5 multipathd: uevent trigger error
<27>Jul 23 17:11:41 node-5 multipathd: uevent trigger error
<27>Jul 23 17:11:41 node-5 multipathd: uevent trigger error
<27>Jul 23 17:11:41 node-5 multipathd: uevent trigger error
<27>Jul 23 17:11:41 node-5 multipathd: uevent trigger error
<11>Jul 23 17:11:50 node-5 liberasurecode[27927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:50 node-5 liberasurecode[27927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:50 node-5 liberasurecode[27927]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:50 node-5 liberasurecode[27927]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:50 node-5 liberasurecode[27954]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:50 node-5 liberasurecode[27954]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:50 node-5 liberasurecode[27954]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:50 node-5 liberasurecode[27954]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:52 node-5 liberasurecode[28356]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:52 node-5 liberasurecode[28356]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:52 node-5 liberasurecode[28356]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:52 node-5 liberasurecode[28356]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[28974]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[28974]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[28974]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[28974]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[29015]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[29015]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[29015]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[29015]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[29059]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[29059]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[29059]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:58 node-5 liberasurecode[29059]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29116]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29116]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29116]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29116]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29130]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29130]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29130]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29130]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29142]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29142]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29142]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29142]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29154]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29154]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29154]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:11:59 node-5 liberasurecode[29154]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 23 17:12:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:12:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:12:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:12:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:12:05 node-5 multipathd: uevent trigger error
<27>Jul 23 17:12:10 node-5 multipathd: uevent trigger error
<27>Jul 23 17:12:10 node-5 multipathd: uevent trigger error
<27>Jul 23 17:12:10 node-5 multipathd: uevent trigger error
<27>Jul 23 17:12:10 node-5 multipathd: uevent trigger error
<27>Jul 23 17:12:10 node-5 multipathd: uevent trigger error
<11>Jul 23 17:12:55 node-5 epmd: epmd: node name already occupied rabbitmq-cli-06
<27>Jul 23 17:13:12 node-5 multipathd: uevent trigger error
<27>Jul 23 17:13:12 node-5 multipathd: uevent trigger error
<27>Jul 23 17:13:12 node-5 multipathd: uevent trigger error
<27>Jul 23 17:13:12 node-5 multipathd: uevent trigger error
<27>Jul 23 17:13:12 node-5 multipathd: uevent trigger error
<11>Jul 23 17:15:01 node-5 liberasurecode[22970]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:15:01 node-5 liberasurecode[22970]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:15:01 node-5 liberasurecode[22970]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 23 17:15:01 node-5 liberasurecode[22970]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 23 17:15:08 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:08 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:08 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:08 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:13 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:13 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:13 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:13 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:13 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:27 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:27 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:27 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:27 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:27 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:31 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:31 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:31 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:32 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:49 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:49 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:49 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:49 node-5 multipathd: uevent trigger error
<27>Jul 23 17:15:49 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:02 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:02 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:02 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:02 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:02 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:07 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:07 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:07 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:07 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:11 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:11 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:11 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:11 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:11 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:15 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:15 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:15 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:15 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:15 node-5 multipathd: uevent trigger error
<11>Jul 23 17:16:19 node-5 epmd: epmd: node name already occupied rabbitmq-cli-06
<27>Jul 23 17:16:24 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:24 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:24 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:24 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:24 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:28 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:28 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:28 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:28 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:33 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:33 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:33 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:33 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:33 node-5 multipathd: uevent trigger error
<27>Jul 23 17:16:41 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 23 17:16:42 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
