Jul 26 02:58:54 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8400" x-info="http://www.rsyslog.com"] start
Jul 26 02:58:54 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 26 02:58:54 node-5 rsyslogd: rsyslogd's groupid changed to 104
Jul 26 02:58:54 node-5 rsyslogd: rsyslogd's userid changed to 101
Jul 26 02:58:54 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 26 02:58:54 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 26 02:58:54 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 26 02:58:54 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 26 02:58:54 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=b5c2d4c3-9cd8-4679-a00f-a8c701d1fa62 nomdmonddf nomdmonisw
Jul 26 02:58:54 node-5 kernel: [    0.000000] KERNEL supported cpus:
Jul 26 02:58:54 node-5 kernel: [    0.000000]   Intel GenuineIntel
Jul 26 02:58:54 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Jul 26 02:58:54 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Jul 26 02:58:54 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 26 02:58:54 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 26 02:58:54 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 26 02:58:54 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 26 02:58:54 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 26 02:58:54 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 26 02:58:54 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 26 02:58:54 node-5 kernel: [    0.000000] No AGP bridge found
Jul 26 02:58:54 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 26 02:58:54 node-5 kernel: [    0.000000] MTRR default type: write-back
Jul 26 02:58:54 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 26 02:58:54 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Jul 26 02:58:54 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 26 02:58:54 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 26 02:58:54 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 26 02:58:54 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 26 02:58:54 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 26 02:58:54 node-5 kernel: [    0.000000]   2 disabled
Jul 26 02:58:54 node-5 kernel: [    0.000000]   3 disabled
Jul 26 02:58:54 node-5 kernel: [    0.000000]   4 disabled
Jul 26 02:58:54 node-5 kernel: [    0.000000]   5 disabled
Jul 26 02:58:54 node-5 kernel: [    0.000000]   6 disabled
Jul 26 02:58:54 node-5 kernel: [    0.000000]   7 disabled
Jul 26 02:58:54 node-5 kernel: [    0.000000]   8 disabled
Jul 26 02:58:54 node-5 kernel: [    0.000000]   9 disabled
Jul 26 02:58:54 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 26 02:58:54 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 26 02:58:54 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 26 02:58:54 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 26 02:58:54 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 26 02:58:54 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Jul 26 02:58:54 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 26 02:58:54 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 26 02:58:54 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 26 02:58:54 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 26 02:58:54 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 26 02:58:54 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 26 02:58:54 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 26 02:58:54 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 26 02:58:54 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 26 02:58:54 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 26 02:58:54 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 26 02:58:54 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 26 02:58:54 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35826000-0x36c0afff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 26 02:58:54 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 26 02:58:54 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 26 02:58:54 node-5 kernel: [    0.000000] Zone ranges:
Jul 26 02:58:54 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] Movable zone start for each node
Jul 26 02:58:54 node-5 kernel: [    0.000000] Early memory node ranges
Jul 26 02:58:54 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 26 02:58:54 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 26 02:58:54 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 26 02:58:54 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 26 02:58:54 node-5 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 26 02:58:54 node-5 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 26 02:58:54 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 26 02:58:54 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 26 02:58:54 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 26 02:58:54 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 26 02:58:54 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 26 02:58:54 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 26 02:58:54 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 26 02:58:54 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 26 02:58:54 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 26 02:58:54 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 26 02:58:54 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 26 02:58:54 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 26 02:58:54 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 26 02:58:54 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 26 02:58:54 node-5 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 26 02:58:54 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 26 02:58:54 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 26 02:58:54 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 26 02:58:54 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 26 02:58:54 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 26 02:58:54 node-5 kernel: [    0.000000] Policy zone: Normal
Jul 26 02:58:54 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=b5c2d4c3-9cd8-4679-a00f-a8c701d1fa62 nomdmonddf nomdmonisw
Jul 26 02:58:54 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 26 02:58:54 node-5 kernel: [    0.000000] Checking aperture...
Jul 26 02:58:54 node-5 kernel: [    0.000000] No AGP bridge found
Jul 26 02:58:54 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 26 02:58:54 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 26 02:58:54 node-5 kernel: [    0.000000] Memory: 32653324K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627172K reserved)
Jul 26 02:58:54 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 26 02:58:54 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 26 02:58:54 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 26 02:58:54 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 26 02:58:54 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 26 02:58:54 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 26 02:58:54 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 26 02:58:54 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 26 02:58:54 node-5 kernel: [    0.000000] console [tty0] enabled
Jul 26 02:58:54 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 26 02:58:54 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 26 02:58:54 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 26 02:58:54 node-5 kernel: [    0.000000] hpet clockevent registered
Jul 26 02:58:54 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 26 02:58:54 node-5 kernel: [    0.004000] tsc: Detected 3491.512 MHz processor
Jul 26 02:58:54 node-5 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.02 BogoMIPS (lpj=13966048)
Jul 26 02:58:54 node-5 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 26 02:58:54 node-5 kernel: [    0.000048] Security Framework initialized
Jul 26 02:58:54 node-5 kernel: [    0.000066] AppArmor: AppArmor initialized
Jul 26 02:58:54 node-5 kernel: [    0.000067] Yama: becoming mindful.
Jul 26 02:58:54 node-5 kernel: [    0.001459] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.006325] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.008255] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.008283] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.008576] Initializing cgroup subsys memory
Jul 26 02:58:54 node-5 kernel: [    0.008584] Initializing cgroup subsys devices
Jul 26 02:58:54 node-5 kernel: [    0.008586] Initializing cgroup subsys freezer
Jul 26 02:58:54 node-5 kernel: [    0.008588] Initializing cgroup subsys blkio
Jul 26 02:58:54 node-5 kernel: [    0.008589] Initializing cgroup subsys perf_event
Jul 26 02:58:54 node-5 kernel: [    0.008592] Initializing cgroup subsys hugetlb
Jul 26 02:58:54 node-5 kernel: [    0.008611] CPU: Physical Processor ID: 0
Jul 26 02:58:54 node-5 kernel: [    0.008613] CPU: Processor Core ID: 0
Jul 26 02:58:54 node-5 kernel: [    0.008617] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 26 02:58:54 node-5 kernel: [    0.008617] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 26 02:58:54 node-5 kernel: [    0.009310] mce: CPU supports 22 MCE banks
Jul 26 02:58:54 node-5 kernel: [    0.009338] CPU0: Thermal monitoring enabled (TM1)
Jul 26 02:58:54 node-5 kernel: [    0.009358] process: using mwait in idle threads
Jul 26 02:58:54 node-5 kernel: [    0.009362] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 26 02:58:54 node-5 kernel: [    0.009362] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 26 02:58:54 node-5 kernel: [    0.009362] tlb_flushall_shift: 6
Jul 26 02:58:54 node-5 kernel: [    0.009450] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 26 02:58:54 node-5 kernel: [    0.010173] ACPI: Core revision 20131115
Jul 26 02:58:54 node-5 kernel: [    0.022831] ACPI: All ACPI Tables successfully acquired
Jul 26 02:58:54 node-5 kernel: [    0.022994] ftrace: allocating 28617 entries in 112 pages
Jul 26 02:58:54 node-5 kernel: [    0.031798] dmar: Host address width 46
Jul 26 02:58:54 node-5 kernel: [    0.031800] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 26 02:58:54 node-5 kernel: [    0.031806] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 26 02:58:54 node-5 kernel: [    0.031807] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 26 02:58:54 node-5 kernel: [    0.031811] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 26 02:58:54 node-5 kernel: [    0.031813] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 26 02:58:54 node-5 kernel: [    0.031814] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 26 02:58:54 node-5 kernel: [    0.031815] dmar: ATSR flags: 0x0
Jul 26 02:58:54 node-5 kernel: [    0.031816] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 26 02:58:54 node-5 kernel: [    0.031817] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 26 02:58:54 node-5 kernel: [    0.031933] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 26 02:58:54 node-5 kernel: [    0.031935] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 26 02:58:54 node-5 kernel: [    0.031936] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 26 02:58:54 node-5 kernel: [    0.031937] HPET id 0 under DRHD base 0xc7ffc000
Jul 26 02:58:54 node-5 kernel: [    0.031938] Your BIOS is broken and requested that x2apic be disabled.
Jul 26 02:58:54 node-5 kernel: [    0.031938] This will slightly decrease performance.
Jul 26 02:58:54 node-5 kernel: [    0.031938] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 26 02:58:54 node-5 kernel: [    0.032370] Enabled IRQ remapping in xapic mode
Jul 26 02:58:54 node-5 kernel: [    0.032371] x2apic not enabled, IRQ remapping is in xapic mode
Jul 26 02:58:54 node-5 kernel: [    0.032375] Switched APIC routing to physical flat.
Jul 26 02:58:54 node-5 kernel: [    0.033010] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 26 02:58:54 node-5 kernel: [    0.072656] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 26 02:58:54 node-5 kernel: [    0.072661] TSC deadline timer enabled
Jul 26 02:58:54 node-5 kernel: [    0.072669] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 26 02:58:54 node-5 kernel: [    0.072675] ... version:                3
Jul 26 02:58:54 node-5 kernel: [    0.072676] ... bit width:              48
Jul 26 02:58:54 node-5 kernel: [    0.072676] ... generic registers:      4
Jul 26 02:58:54 node-5 kernel: [    0.072677] ... value mask:             0000ffffffffffff
Jul 26 02:58:54 node-5 kernel: [    0.072678] ... max period:             0000ffffffffffff
Jul 26 02:58:54 node-5 kernel: [    0.072679] ... fixed-purpose events:   3
Jul 26 02:58:54 node-5 kernel: [    0.072680] ... event mask:             000000070000000f
Jul 26 02:58:54 node-5 kernel: [    0.074120] x86: Booting SMP configuration:
Jul 26 02:58:54 node-5 kernel: [    0.088223] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 26 02:58:54 node-5 kernel: [    0.074122] .... node  #0, CPUs:        #1  #2  #3
Jul 26 02:58:54 node-5 kernel: [    0.116134] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 26 02:58:54 node-5 kernel: [    0.270272] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 26 02:58:54 node-5 kernel: [    0.325884] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 26 02:58:54 node-5 kernel: [    0.382936] x86: Booted up 2 nodes, 16 CPUs
Jul 26 02:58:54 node-5 kernel: [    0.382939] smpboot: Total of 16 processors activated (111740.37 BogoMIPS)
Jul 26 02:58:54 node-5 kernel: [    0.407077] devtmpfs: initialized
Jul 26 02:58:54 node-5 kernel: [    0.410166] EVM: security.selinux
Jul 26 02:58:54 node-5 kernel: [    0.410168] EVM: security.SMACK64
Jul 26 02:58:54 node-5 kernel: [    0.410169] EVM: security.ima
Jul 26 02:58:54 node-5 kernel: [    0.410170] EVM: security.capability
Jul 26 02:58:54 node-5 kernel: [    0.410219] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.410902] pinctrl core: initialized pinctrl subsystem
Jul 26 02:58:54 node-5 kernel: [    0.410966] regulator-dummy: no parameters
Jul 26 02:58:54 node-5 kernel: [    0.410998] RTC time:  2:58:18, date: 07/26/16
Jul 26 02:58:54 node-5 kernel: [    0.411033] NET: Registered protocol family 16
Jul 26 02:58:54 node-5 kernel: [    0.411118] cpuidle: using governor ladder
Jul 26 02:58:54 node-5 kernel: [    0.411120] cpuidle: using governor menu
Jul 26 02:58:54 node-5 kernel: [    0.411155] ACPI: bus type PCI registered
Jul 26 02:58:54 node-5 kernel: [    0.411157] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 26 02:58:54 node-5 kernel: [    0.411204] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 26 02:58:54 node-5 kernel: [    0.411207] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 26 02:58:54 node-5 kernel: [    0.424938] PCI: Using configuration type 1 for base access
Jul 26 02:58:54 node-5 kernel: [    0.425939] bio: create slab <bio-0> at 0
Jul 26 02:58:54 node-5 kernel: [    0.426210] ACPI: Added _OSI(Module Device)
Jul 26 02:58:54 node-5 kernel: [    0.426212] ACPI: Added _OSI(Processor Device)
Jul 26 02:58:54 node-5 kernel: [    0.426213] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 26 02:58:54 node-5 kernel: [    0.426214] ACPI: Added _OSI(Processor Aggregator Device)
Jul 26 02:58:54 node-5 kernel: [    0.438862] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 26 02:58:54 node-5 kernel: [    0.449536] ACPI: Interpreter enabled
Jul 26 02:58:54 node-5 kernel: [    0.449542] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 26 02:58:54 node-5 kernel: [    0.449546] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 26 02:58:54 node-5 kernel: [    0.449548] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 26 02:58:54 node-5 kernel: [    0.449555] ACPI: (supports S0 S4 S5)
Jul 26 02:58:54 node-5 kernel: [    0.449556] ACPI: Using IOAPIC for interrupt routing
Jul 26 02:58:54 node-5 kernel: [    0.449596] HEST: Table parsing has been initialized.
Jul 26 02:58:54 node-5 kernel: [    0.449599] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 26 02:58:54 node-5 kernel: [    0.450149] ACPI: No dock devices found.
Jul 26 02:58:54 node-5 kernel: [    0.461688] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 26 02:58:54 node-5 kernel: [    0.461693] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 02:58:54 node-5 kernel: [    0.461696] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 26 02:58:54 node-5 kernel: [    0.461723] PCI host bridge to bus 0000:ff
Jul 26 02:58:54 node-5 kernel: [    0.461725] pci_bus 0000:ff: root bus resource [bus ff]
Jul 26 02:58:54 node-5 kernel: [    0.461733] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.461771] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.461802] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.461837] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.461866] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.461895] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.461926] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.461955] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.461983] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462011] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462038] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462064] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462092] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462119] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462146] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462174] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462204] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462231] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462258] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.462288] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462314] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.462339] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462365] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462395] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.462430] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462462] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462492] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462522] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462554] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462585] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462615] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462646] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462676] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462707] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462738] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462770] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462803] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462833] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462861] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462892] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462924] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462961] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.462996] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463029] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463059] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463088] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463118] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463146] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463178] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463209] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463240] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463272] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463303] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463332] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463362] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463394] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463427] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463485] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 26 02:58:54 node-5 kernel: [    0.463487] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 02:58:54 node-5 kernel: [    0.463491] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 26 02:58:54 node-5 kernel: [    0.463511] PCI host bridge to bus 0000:7f
Jul 26 02:58:54 node-5 kernel: [    0.463512] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 26 02:58:54 node-5 kernel: [    0.463518] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463548] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.463579] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463610] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463634] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.463664] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.463690] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463717] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463740] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463763] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463788] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463813] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463840] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463864] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463889] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463915] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463936] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463959] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.463982] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.464005] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464028] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.464050] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464072] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464099] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 26 02:58:54 node-5 kernel: [    0.464133] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464161] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464189] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464217] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464242] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464270] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464296] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464324] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464348] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464375] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464403] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464431] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464460] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464484] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464509] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464537] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464562] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464588] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464618] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464647] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464672] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464698] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464726] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464753] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464780] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464807] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464837] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464862] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464885] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464911] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464938] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464967] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.464993] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.466252] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 26 02:58:54 node-5 kernel: [    0.466256] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 02:58:54 node-5 kernel: [    0.467383] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 26 02:58:54 node-5 kernel: [    0.467896] PCI host bridge to bus 0000:00
Jul 26 02:58:54 node-5 kernel: [    0.467899] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 26 02:58:54 node-5 kernel: [    0.467901] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 26 02:58:54 node-5 kernel: [    0.467902] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 26 02:58:54 node-5 kernel: [    0.467903] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 26 02:58:54 node-5 kernel: [    0.467905] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 26 02:58:54 node-5 kernel: [    0.467906] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 26 02:58:54 node-5 kernel: [    0.467908] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 26 02:58:54 node-5 kernel: [    0.467913] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 26 02:58:54 node-5 kernel: [    0.467996] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.468027] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.468068] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 26 02:58:54 node-5 kernel: [    0.468089] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.468119] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.468159] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 26 02:58:54 node-5 kernel: [    0.468177] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.468207] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.468250] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 26 02:58:54 node-5 kernel: [    0.468268] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.468338] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.468417] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.468493] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 26 02:58:54 node-5 kernel: [    0.468498] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 26 02:58:54 node-5 kernel: [    0.468582] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 26 02:58:54 node-5 kernel: [    0.468729] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 26 02:58:54 node-5 kernel: [    0.468747] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 26 02:58:54 node-5 kernel: [    0.468825] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.468879] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 26 02:58:54 node-5 kernel: [    0.468901] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.468956] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.468999] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 26 02:58:54 node-5 kernel: [    0.469026] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.469082] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.469125] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 26 02:58:54 node-5 kernel: [    0.469149] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 26 02:58:54 node-5 kernel: [    0.469167] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 26 02:58:54 node-5 kernel: [    0.469244] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.469294] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 26 02:58:54 node-5 kernel: [    0.469320] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 26 02:58:54 node-5 kernel: [    0.469565] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 26 02:58:54 node-5 kernel: [    0.469571] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 26 02:58:54 node-5 kernel: [    0.469577] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.469583] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.469590] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 26 02:58:54 node-5 kernel: [    0.469620] pci 0000:01:00.0: supports D1 D2
Jul 26 02:58:54 node-5 kernel: [    0.475657] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 26 02:58:54 node-5 kernel: [    0.475659] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 26 02:58:54 node-5 kernel: [    0.475661] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 26 02:58:54 node-5 kernel: [    0.475767] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.475800] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 26 02:58:54 node-5 kernel: [    0.483661] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 26 02:58:54 node-5 kernel: [    0.483667] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.483671] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:54 node-5 kernel: [    0.483755] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.483837] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.483914] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.483958] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 26 02:58:54 node-5 kernel: [    0.483961] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.483963] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:54 node-5 kernel: [    0.484015] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.484138] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.484194] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 26 02:58:54 node-5 kernel: [    0.484197] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.484199] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:54 node-5 kernel: [    0.484248] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.484387] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.484428] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.484547] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.484583] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.484705] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.484743] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 26 02:58:54 node-5 kernel: [    0.484862] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 26 02:58:54 node-5 kernel: [    0.484904] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 26 02:58:54 node-5 kernel: [    0.484907] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.484909] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:54 node-5 kernel: [    0.484969] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 26 02:58:54 node-5 kernel: [    0.485032] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.485084] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.485125] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 26 02:58:54 node-5 kernel: [    0.485210] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 26 02:58:54 node-5 kernel: [    0.485316] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 26 02:58:54 node-5 kernel: [    0.485318] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.485320] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 26 02:58:54 node-5 kernel: [    0.485386] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 26 02:58:54 node-5 kernel: [    0.485444] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.485492] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.485706] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 26 02:58:54 node-5 kernel: [    0.485709] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 26 02:58:54 node-5 kernel: [    0.485773] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 26 02:58:54 node-5 kernel: [    0.485826] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.485874] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.486083] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 26 02:58:54 node-5 kernel: [    0.486087] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 26 02:58:54 node-5 kernel: [    0.486146] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 26 02:58:54 node-5 kernel: [    0.486206] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.486261] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 26 02:58:54 node-5 kernel: [    0.486511] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 26 02:58:54 node-5 kernel: [    0.486514] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 26 02:58:54 node-5 kernel: [    0.486688] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 26 02:58:54 node-5 kernel: [    0.486726] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 26 02:58:54 node-5 kernel: [    0.486802] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 26 02:58:54 node-5 kernel: [    0.486820] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 26 02:58:54 node-5 kernel: [    0.486834] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 26 02:58:54 node-5 kernel: [    0.486847] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 26 02:58:54 node-5 kernel: [    0.486897] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 26 02:58:54 node-5 kernel: [    0.491674] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 26 02:58:54 node-5 kernel: [    0.491679] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 26 02:58:54 node-5 kernel: [    0.491710] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 26 02:58:54 node-5 kernel: [    0.492199] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 26 02:58:54 node-5 kernel: [    0.492202] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 26 02:58:54 node-5 kernel: [    0.492327] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 26 02:58:54 node-5 kernel: [    0.492434] PCI host bridge to bus 0000:80
Jul 26 02:58:54 node-5 kernel: [    0.492436] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 26 02:58:54 node-5 kernel: [    0.492438] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 26 02:58:54 node-5 kernel: [    0.492439] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 26 02:58:54 node-5 kernel: [    0.492447] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.492510] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.492578] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 26 02:58:54 node-5 kernel: [    0.492641] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 26 02:58:54 node-5 kernel: [    0.492646] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 26 02:58:54 node-5 kernel: [    0.492718] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 26 02:58:54 node-5 kernel: [    0.493018] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 26 02:58:54 node-5 kernel: [    0.493050] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 26 02:58:54 node-5 kernel: [    0.493079] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 26 02:58:54 node-5 kernel: [    0.493108] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 26 02:58:54 node-5 kernel: [    0.493137] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 02:58:54 node-5 kernel: [    0.493167] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 02:58:54 node-5 kernel: [    0.493197] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 02:58:54 node-5 kernel: [    0.493226] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 26 02:58:54 node-5 kernel: [    0.493311] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 26 02:58:54 node-5 kernel: [    0.493316] ACPI: \_SB_.UNC1: notify handler is installed
Jul 26 02:58:54 node-5 kernel: [    0.493317] ACPI: \_SB_.UNC0: notify handler is installed
Jul 26 02:58:54 node-5 kernel: [    0.493332] ACPI: \_SB_.PCI0: notify handler is installed
Jul 26 02:58:54 node-5 kernel: [    0.493385] ACPI: \_SB_.PCI1: notify handler is installed
Jul 26 02:58:54 node-5 kernel: [    0.493464] Found 4 acpi root devices
Jul 26 02:58:54 node-5 kernel: [    0.493574] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 26 02:58:54 node-5 kernel: [    0.493576] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 26 02:58:54 node-5 kernel: [    0.493578] vgaarb: loaded
Jul 26 02:58:54 node-5 kernel: [    0.493579] vgaarb: bridge control possible 0000:0c:00.0
Jul 26 02:58:54 node-5 kernel: [    0.493702] SCSI subsystem initialized
Jul 26 02:58:54 node-5 kernel: [    0.493766] libata version 3.00 loaded.
Jul 26 02:58:54 node-5 kernel: [    0.493782] ACPI: bus type USB registered
Jul 26 02:58:54 node-5 kernel: [    0.493792] usbcore: registered new interface driver usbfs
Jul 26 02:58:54 node-5 kernel: [    0.493797] usbcore: registered new interface driver hub
Jul 26 02:58:54 node-5 kernel: [    0.493821] usbcore: registered new device driver usb
Jul 26 02:58:54 node-5 kernel: [    0.493992] PCI: Using ACPI for IRQ routing
Jul 26 02:58:54 node-5 kernel: [    0.497585] PCI: pci_cache_line_size set to 64 bytes
Jul 26 02:58:54 node-5 kernel: [    0.497795] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 26 02:58:54 node-5 kernel: [    0.497796] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 26 02:58:54 node-5 kernel: [    0.497797] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 26 02:58:54 node-5 kernel: [    0.497862] NetLabel: Initializing
Jul 26 02:58:54 node-5 kernel: [    0.497864] NetLabel:  domain hash size = 128
Jul 26 02:58:54 node-5 kernel: [    0.497865] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 26 02:58:54 node-5 kernel: [    0.497874] NetLabel:  unlabeled traffic allowed by default
Jul 26 02:58:54 node-5 kernel: [    0.497943] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 26 02:58:54 node-5 kernel: [    0.497947] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 26 02:58:54 node-5 kernel: [    0.500003] Switched to clocksource hpet
Jul 26 02:58:54 node-5 kernel: [    0.503797] AppArmor: AppArmor Filesystem Enabled
Jul 26 02:58:54 node-5 kernel: [    0.503811] pnp: PnP ACPI init
Jul 26 02:58:54 node-5 kernel: [    0.503817] ACPI: bus type PNP registered
Jul 26 02:58:54 node-5 kernel: [    0.503925] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 26 02:58:54 node-5 kernel: [    0.503933] pnp 00:01: [dma 4]
Jul 26 02:58:54 node-5 kernel: [    0.503944] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 26 02:58:54 node-5 kernel: [    0.503978] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 26 02:58:54 node-5 kernel: [    0.504003] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 26 02:58:54 node-5 kernel: [    0.504021] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 26 02:58:54 node-5 kernel: [    0.504054] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 26 02:58:54 node-5 kernel: [    0.504105] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504107] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 26 02:58:54 node-5 kernel: [    0.504108] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504110] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504111] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504116] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504118] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 26 02:58:54 node-5 kernel: [    0.504120] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504121] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504123] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504124] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504126] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504127] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 26 02:58:54 node-5 kernel: [    0.504129] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 26 02:58:54 node-5 kernel: [    0.504213] pnp 00:07: [dma 0 disabled]
Jul 26 02:58:54 node-5 kernel: [    0.504241] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 26 02:58:54 node-5 kernel: [    0.504315] pnp 00:08: [dma 0 disabled]
Jul 26 02:58:54 node-5 kernel: [    0.504346] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 26 02:58:54 node-5 kernel: [    0.504396] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 26 02:58:54 node-5 kernel: [    0.504742] pnp: PnP ACPI: found 10 devices
Jul 26 02:58:54 node-5 kernel: [    0.504744] ACPI: bus type PNP unregistered
Jul 26 02:58:54 node-5 kernel: [    0.511021] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 26 02:58:54 node-5 kernel: [    0.511024] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 26 02:58:54 node-5 kernel: [    0.511027] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 26 02:58:54 node-5 kernel: [    0.511031] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 26 02:58:54 node-5 kernel: [    0.511033] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.511048] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511077] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 26 02:58:54 node-5 kernel: [    0.511092] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511120] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 26 02:58:54 node-5 kernel: [    0.511135] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 26 02:58:54 node-5 kernel: [    0.511167] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 26 02:58:54 node-5 kernel: [    0.511181] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 26 02:58:54 node-5 kernel: [    0.511210] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 26 02:58:54 node-5 kernel: [    0.511212] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.511226] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511255] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 26 02:58:54 node-5 kernel: [    0.511257] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.511271] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511300] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 26 02:58:54 node-5 kernel: [    0.511302] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.511305] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511309] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 26 02:58:54 node-5 kernel: [    0.511310] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.511313] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511316] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 26 02:58:54 node-5 kernel: [    0.511321] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 26 02:58:54 node-5 kernel: [    0.511329] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 26 02:58:54 node-5 kernel: [    0.511333] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 26 02:58:54 node-5 kernel: [    0.511339] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 26 02:58:54 node-5 kernel: [    0.511340] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 26 02:58:54 node-5 kernel: [    0.511341] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 26 02:58:54 node-5 kernel: [    0.511342] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 26 02:58:54 node-5 kernel: [    0.511342] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 26 02:58:54 node-5 kernel: [    0.511343] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 26 02:58:54 node-5 kernel: [    0.511344] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 26 02:58:54 node-5 kernel: [    0.511345] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 26 02:58:54 node-5 kernel: [    0.511346] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.511347] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511348] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.511349] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511350] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.511351] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511351] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.511352] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511353] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 26 02:58:54 node-5 kernel: [    0.511354] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511355] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 26 02:58:54 node-5 kernel: [    0.511356] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 26 02:58:54 node-5 kernel: [    0.511357] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 26 02:58:54 node-5 kernel: [    0.511358] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 26 02:58:54 node-5 kernel: [    0.511360] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 26 02:58:54 node-5 kernel: [    0.511361] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 26 02:58:54 node-5 kernel: [    0.511402] NET: Registered protocol family 2
Jul 26 02:58:54 node-5 kernel: [    0.511654] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.511984] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.512134] TCP: Hash tables configured (established 262144 bind 65536)
Jul 26 02:58:54 node-5 kernel: [    0.512177] TCP: reno registered
Jul 26 02:58:54 node-5 kernel: [    0.512205] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.512303] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.512452] NET: Registered protocol family 1
Jul 26 02:58:54 node-5 kernel: [    0.548034] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 26 02:58:54 node-5 kernel: [    0.548041] PCI: CLS 64 bytes, default 64
Jul 26 02:58:54 node-5 kernel: [    0.548083] Trying to unpack rootfs image as initramfs...
Jul 26 02:58:54 node-5 kernel: [    0.767365] Freeing initrd memory: 20372K (ffff880035826000 - ffff880036c0b000)
Jul 26 02:58:54 node-5 kernel: [    0.767408] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 26 02:58:54 node-5 kernel: [    0.767411] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 26 02:58:54 node-5 kernel: [    0.767828] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767834] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767839] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767845] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767857] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767874] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767889] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767905] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767917] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767926] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767932] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767938] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767947] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767960] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767973] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.767986] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 26 02:58:54 node-5 kernel: [    0.768085] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 26 02:58:54 node-5 kernel: [    0.768088] Scanning for low memory corruption every 60 seconds
Jul 26 02:58:54 node-5 kernel: [    0.768508] Initialise system trusted keyring
Jul 26 02:58:54 node-5 kernel: [    0.768563] audit: initializing netlink socket (disabled)
Jul 26 02:58:54 node-5 kernel: [    0.768580] type=2000 audit(1469501898.724:1): initialized
Jul 26 02:58:54 node-5 kernel: [    0.786429] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 26 02:58:54 node-5 kernel: [    0.787944] zbud: loaded
Jul 26 02:58:54 node-5 kernel: [    0.788073] VFS: Disk quotas dquot_6.5.2
Jul 26 02:58:54 node-5 kernel: [    0.788110] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 26 02:58:54 node-5 kernel: [    0.788484] fuse init (API version 7.22)
Jul 26 02:58:54 node-5 kernel: [    0.788539] msgmni has been set to 32768
Jul 26 02:58:54 node-5 kernel: [    0.788591] Key type big_key registered
Jul 26 02:58:54 node-5 kernel: [    0.789081] Key type asymmetric registered
Jul 26 02:58:54 node-5 kernel: [    0.789083] Asymmetric key parser 'x509' registered
Jul 26 02:58:54 node-5 kernel: [    0.789105] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 26 02:58:54 node-5 kernel: [    0.789193] io scheduler noop registered
Jul 26 02:58:54 node-5 kernel: [    0.789195] io scheduler deadline registered (default)
Jul 26 02:58:54 node-5 kernel: [    0.789213] io scheduler cfq registered
Jul 26 02:58:54 node-5 kernel: [    0.789613] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    0.789743] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    0.789860] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    0.789971] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    0.790086] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    0.790190] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    0.790592] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 26 02:58:54 node-5 kernel: [    0.790617] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 26 02:58:54 node-5 kernel: [    0.790634] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 26 02:58:54 node-5 kernel: [    0.790646] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790648] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790651] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 26 02:58:54 node-5 kernel: [    0.790656] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790658] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790659] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790661] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790662] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790664] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790665] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790666] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790668] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790669] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790671] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790672] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790675] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 26 02:58:54 node-5 kernel: [    0.790682] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790685] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 26 02:58:54 node-5 kernel: [    0.790696] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790699] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 26 02:58:54 node-5 kernel: [    0.790710] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790712] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 26 02:58:54 node-5 kernel: [    0.790715] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 26 02:58:54 node-5 kernel: [    0.790745] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 26 02:58:54 node-5 kernel: [    0.790751] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 26 02:58:54 node-5 kernel: [    0.790755] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 26 02:58:54 node-5 kernel: [    0.790772] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 26 02:58:54 node-5 kernel: [    0.790812] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 26 02:58:54 node-5 kernel: [    0.790813] vesafb: scrolling: redraw
Jul 26 02:58:54 node-5 kernel: [    0.790815] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 26 02:58:54 node-5 kernel: [    0.811387] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 26 02:58:54 node-5 kernel: [    0.819908] Console: switching to colour frame buffer device 80x30
Jul 26 02:58:54 node-5 kernel: [    0.828576] fb0: VESA VGA frame buffer device
Jul 26 02:58:54 node-5 kernel: [    0.828772] intel_idle: MWAIT substates: 0x2120
Jul 26 02:58:54 node-5 kernel: [    0.828773] intel_idle: v0.4 model 0x3F
Jul 26 02:58:54 node-5 kernel: [    0.828773] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 26 02:58:54 node-5 kernel: [    0.829002] ipmi message handler version 39.2
Jul 26 02:58:54 node-5 kernel: [    0.829284] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 26 02:58:54 node-5 kernel: [    0.829718] ACPI: AC Adapter [P111] (on-line)
Jul 26 02:58:54 node-5 kernel: [    0.834965] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 26 02:58:54 node-5 kernel: [    0.845955] ACPI: Power Button [PWRB]
Jul 26 02:58:54 node-5 kernel: [    0.851711] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 26 02:58:54 node-5 kernel: [    0.863430] ACPI: Power Button [PWRF]
Jul 26 02:58:54 node-5 kernel: [    0.881489] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 26 02:58:54 node-5 kernel: [    0.893211] pstore: Registered erst as persistent store backend
Jul 26 02:58:54 node-5 kernel: [    0.899423] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 26 02:58:54 node-5 kernel: [    0.911459] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 26 02:58:54 node-5 kernel: [    0.938204] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 26 02:58:54 node-5 kernel: [    0.971606] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 26 02:58:54 node-5 kernel: [    0.985666] Linux agpgart interface v0.103
Jul 26 02:58:54 node-5 kernel: [    0.993283] brd: module loaded
Jul 26 02:58:54 node-5 kernel: [    1.000331] loop: module loaded
Jul 26 02:58:54 node-5 kernel: [    1.007057] libphy: Fixed MDIO Bus: probed
Jul 26 02:58:54 node-5 kernel: [    1.013531] tun: Universal TUN/TAP device driver, 1.6
Jul 26 02:58:54 node-5 kernel: [    1.020009] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 26 02:58:54 node-5 kernel: [    1.026543] PPP generic driver version 2.4.2
Jul 26 02:58:54 node-5 kernel: [    1.032939] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 26 02:58:54 node-5 kernel: [    1.039386] ehci-pci: EHCI PCI platform driver
Jul 26 02:58:54 node-5 kernel: [    1.045909] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 26 02:58:54 node-5 kernel: [    1.052333] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 26 02:58:54 node-5 kernel: [    1.064879] ehci-pci 0000:00:1a.0: debug port 2
Jul 26 02:58:54 node-5 kernel: [    1.075092] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 26 02:58:54 node-5 kernel: [    1.075122] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 26 02:58:54 node-5 kernel: [    1.091505] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 26 02:58:54 node-5 kernel: [    1.097677] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 26 02:58:54 node-5 kernel: [    1.103947] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 26 02:58:54 node-5 kernel: [    1.115863] usb usb1: Product: EHCI Host Controller
Jul 26 02:58:54 node-5 kernel: [    1.121896] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 26 02:58:54 node-5 kernel: [    1.127956] usb usb1: SerialNumber: 0000:00:1a.0
Jul 26 02:58:54 node-5 kernel: [    1.133909] hub 1-0:1.0: USB hub found
Jul 26 02:58:54 node-5 kernel: [    1.139683] hub 1-0:1.0: 2 ports detected
Jul 26 02:58:54 node-5 kernel: [    1.145492] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 26 02:58:54 node-5 kernel: [    1.151158] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 26 02:58:54 node-5 kernel: [    1.162165] ehci-pci 0000:00:1d.0: debug port 2
Jul 26 02:58:54 node-5 kernel: [    1.171501] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 26 02:58:54 node-5 kernel: [    1.171504] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 26 02:58:54 node-5 kernel: [    1.187423] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 26 02:58:54 node-5 kernel: [    1.192751] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 26 02:58:54 node-5 kernel: [    1.198215] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 26 02:58:54 node-5 kernel: [    1.209053] usb usb2: Product: EHCI Host Controller
Jul 26 02:58:54 node-5 kernel: [    1.214661] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 26 02:58:54 node-5 kernel: [    1.220358] usb usb2: SerialNumber: 0000:00:1d.0
Jul 26 02:58:54 node-5 kernel: [    1.226017] hub 2-0:1.0: USB hub found
Jul 26 02:58:54 node-5 kernel: [    1.231514] hub 2-0:1.0: 2 ports detected
Jul 26 02:58:54 node-5 kernel: [    1.236958] ehci-platform: EHCI generic platform driver
Jul 26 02:58:54 node-5 kernel: [    1.242315] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 26 02:58:54 node-5 kernel: [    1.247765] ohci-pci: OHCI PCI platform driver
Jul 26 02:58:54 node-5 kernel: [    1.253175] ohci-platform: OHCI generic platform driver
Jul 26 02:58:54 node-5 kernel: [    1.258480] uhci_hcd: USB Universal Host Controller Interface driver
Jul 26 02:58:54 node-5 kernel: [    1.263931] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 26 02:58:54 node-5 kernel: [    1.455203] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 26 02:58:54 node-5 kernel: [    1.631405] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 26 02:58:54 node-5 kernel: [    1.636915] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 26 02:58:54 node-5 kernel: [    1.642671] hub 1-1:1.0: USB hub found
Jul 26 02:58:54 node-5 kernel: [    1.648140] hub 1-1:1.0: 6 ports detected
Jul 26 02:58:54 node-5 kernel: [    1.762934] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 26 02:58:54 node-5 kernel: [    1.763172] tsc: Refined TSC clocksource calibration: 3491.885 MHz
Jul 26 02:58:54 node-5 kernel: [    2.031065] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 26 02:58:54 node-5 kernel: [    2.036608] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 26 02:58:54 node-5 kernel: [    2.042458] hub 2-1:1.0: USB hub found
Jul 26 02:58:54 node-5 kernel: [    2.048176] hub 2-1:1.0: 8 ports detected
Jul 26 02:58:54 node-5 kernel: [    2.305512] i8042: No controller found
Jul 26 02:58:54 node-5 kernel: [    2.310923] mousedev: PS/2 mouse device common for all mice
Jul 26 02:58:54 node-5 kernel: [    2.316428] rtc_cmos 00:02: RTC can wake from S4
Jul 26 02:58:54 node-5 kernel: [    2.322002] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 26 02:58:54 node-5 kernel: [    2.326523] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 26 02:58:54 node-5 kernel: [    2.333125] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 26 02:58:54 node-5 kernel: [    2.344206] device-mapper: uevent: version 1.0.3
Jul 26 02:58:54 node-5 kernel: [    2.349850] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 26 02:58:54 node-5 kernel: [    2.361041] ledtrig-cpu: registered to indicate activity on CPUs
Jul 26 02:58:54 node-5 kernel: [    2.366951] TCP: cubic registered
Jul 26 02:58:54 node-5 kernel: [    2.372868] NET: Registered protocol family 10
Jul 26 02:58:54 node-5 kernel: [    2.378894] NET: Registered protocol family 17
Jul 26 02:58:54 node-5 kernel: [    2.384562] Key type dns_resolver registered
Jul 26 02:58:54 node-5 kernel: [    2.390508] Loading compiled-in X.509 certificates
Jul 26 02:58:54 node-5 kernel: [    2.396663] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 26 02:58:54 node-5 kernel: [    2.408035] registered taskstats version 1
Jul 26 02:58:54 node-5 kernel: [    2.415957] Key type trusted registered
Jul 26 02:58:54 node-5 kernel: [    2.423532] Key type encrypted registered
Jul 26 02:58:54 node-5 kernel: [    2.428996] AppArmor: AppArmor sha1 policy hashing enabled
Jul 26 02:58:54 node-5 kernel: [    2.434476] IMA: No TPM chip found, activating TPM-bypass!
Jul 26 02:58:54 node-5 kernel: [    2.440624] regulator-dummy: disabling
Jul 26 02:58:54 node-5 kernel: [    2.446199]   Magic number: 8:611:966
Jul 26 02:58:54 node-5 kernel: [    2.451882] rtc_cmos 00:02: setting system clock to 2016-07-26 02:58:20 UTC (1469501900)
Jul 26 02:58:54 node-5 kernel: [    2.464230] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 26 02:58:54 node-5 kernel: [    2.469834] EDD information not available.
Jul 26 02:58:54 node-5 kernel: [    2.475509] PM: Hibernation image not present or could not be loaded.
Jul 26 02:58:54 node-5 kernel: [    2.476366] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 26 02:58:54 node-5 kernel: [    2.478884] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 26 02:58:54 node-5 kernel: [    2.478887] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 26 02:58:54 node-5 kernel: [    2.478888] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 26 02:58:54 node-5 kernel: [    2.478890] usb 2-1.4: Manufacturer: Avocent
Jul 26 02:58:54 node-5 kernel: [    2.478892] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 26 02:58:54 node-5 kernel: [    2.523528] Write protecting the kernel read-only data: 12288k
Jul 26 02:58:54 node-5 kernel: [    2.529834] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 26 02:58:54 node-5 kernel: [    2.542374] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 26 02:58:54 node-5 kernel: [    2.574801] device-mapper: multipath: version 1.6.0 loaded
Jul 26 02:58:54 node-5 kernel: [    2.582814] systemd-udevd[215]: starting version 204
Jul 26 02:58:54 node-5 kernel: [    2.607761] md: linear personality registered for level -1
Jul 26 02:58:54 node-5 kernel: [    2.622454] md: multipath personality registered for level -4
Jul 26 02:58:54 node-5 kernel: [    2.630536] md: raid0 personality registered for level 0
Jul 26 02:58:54 node-5 kernel: [    2.638697] md: raid1 personality registered for level 1
Jul 26 02:58:54 node-5 kernel: [    2.648849] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 26 02:58:54 node-5 kernel: [    2.655352] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 26 02:58:54 node-5 kernel: [    2.655237] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 26 02:58:54 node-5 kernel: [    2.674463] hidraw: raw HID events driver (C) Jiri Kosina
Jul 26 02:58:54 node-5 kernel: [    2.674638] megasas: FW now in Ready state
Jul 26 02:58:54 node-5 kernel: [    2.674707] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.674748] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.674785] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.674821] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.674856] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.674896] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.674933] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.674972] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.675004] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.675043] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.675080] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.675115] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.675142] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.675175] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.675210] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.675248] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.675405] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 26 02:58:54 node-5 kernel: [    2.684729] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 26 02:58:54 node-5 kernel: [    2.684731] 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 26 02:58:54 node-5 kernel: [    2.684732] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 02:58:54 node-5 kernel: [    2.684793] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.684833] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.684871] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.684908] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.684982] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.697249] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 26 02:58:54 node-5 kernel: [    2.697250] 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 26 02:58:54 node-5 kernel: [    2.697251] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 02:58:54 node-5 kernel: [    2.697319] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.697359] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.697397] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.697433] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.697501] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.708240] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 26 02:58:54 node-5 kernel: [    2.708242] 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 26 02:58:54 node-5 kernel: [    2.708243] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 02:58:54 node-5 kernel: [    2.708304] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.708336] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.708373] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.708409] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.708494] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.714231] raid6: sse2x1    1423 MB/s
Jul 26 02:58:54 node-5 kernel: [    2.717838] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 26 02:58:54 node-5 kernel: [    2.717840] 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 26 02:58:54 node-5 kernel: [    2.717841] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 26 02:58:54 node-5 kernel: [    2.717897] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.717932] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.717967] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.718004] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.718082] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 26 02:58:54 node-5 kernel: [    2.782170] raid6: sse2x2     743 MB/s
Jul 26 02:58:54 node-5 kernel: [    2.850299] raid6: sse2x4    1171 MB/s
Jul 26 02:58:54 node-5 kernel: [    2.917968] raid6: avx2x1    4165 MB/s
Jul 26 02:58:54 node-5 kernel: [    2.989908] raid6: avx2x2   18875 MB/s
Jul 26 02:58:54 node-5 kernel: [    3.061841] raid6: avx2x4   21365 MB/s
Jul 26 02:58:54 node-5 kernel: [    3.067665] raid6: using algorithm avx2x4 (21365 MB/s)
Jul 26 02:58:54 node-5 kernel: [    3.073643] raid6: using avx2x2 recovery algorithm
Jul 26 02:58:54 node-5 kernel: [    3.079493] megasas:IOC Init cmd success
Jul 26 02:58:54 node-5 kernel: [    3.079494] Switched to clocksource tsc
Jul 26 02:58:54 node-5 kernel: [    3.091449] xor: automatically using best checksumming function:
Jul 26 02:58:54 node-5 kernel: [    3.093247] usbcore: registered new interface driver usbhid
Jul 26 02:58:54 node-5 kernel: [    3.093248] usbhid: USB HID core driver
Jul 26 02:58:54 node-5 kernel: [    3.107831] megasas: INIT adapter done
Jul 26 02:58:54 node-5 kernel: [    3.113394] 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 26 02:58:54 node-5 kernel: [    3.124458] 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 26 02:58:54 node-5 kernel: [    3.135594] 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 26 02:58:54 node-5 kernel: [    3.145794]    avx       : 36560.000 MB/sec
Jul 26 02:58:54 node-5 kernel: [    3.152393] 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 26 02:58:54 node-5 kernel: [    3.164180] 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 26 02:58:54 node-5 kernel: [    3.164181] async_tx: api initialized (async)
Jul 26 02:58:54 node-5 kernel: [    3.181698] 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 26 02:58:54 node-5 kernel: [    3.185782] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 26 02:58:54 node-5 kernel: [    3.186195] scsi0 : LSI SAS based MegaRAID driver
Jul 26 02:58:54 node-5 kernel: [    3.193352] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 26 02:58:54 node-5 kernel: [    3.204493] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 26 02:58:54 node-5 kernel: [    3.208700] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 26 02:58:54 node-5 kernel: [    3.208732] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 26 02:58:54 node-5 kernel: [    3.209043] sd 0:2:0:0: [sda] Write Protect is off
Jul 26 02:58:54 node-5 kernel: [    3.209044] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 26 02:58:54 node-5 kernel: [    3.209116] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 26 02:58:54 node-5 kernel: [    3.239632]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 26 02:58:54 node-5 kernel: [    3.241879] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 26 02:58:54 node-5 kernel: [    3.288549] md: raid6 personality registered for level 6
Jul 26 02:58:54 node-5 kernel: [    3.295681] md: raid5 personality registered for level 5
Jul 26 02:58:54 node-5 kernel: [    3.302607] md: raid4 personality registered for level 4
Jul 26 02:58:54 node-5 kernel: [    3.312590] md: raid10 personality registered for level 10
Jul 26 02:58:54 node-5 kernel: [    3.365611] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Jul 26 02:58:54 node-5 kernel: [    3.411449] random: lvm urandom read with 29 bits of entropy available
Jul 26 02:58:54 node-5 kernel: [    3.542174] bio: create slab <bio-1> at 1
Jul 26 02:58:54 node-5 kernel: [    4.477763] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 02:58:54 node-5 kernel: [    5.186217] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 26 02:58:54 node-5 kernel: [    5.192342] random: nonblocking pool is initialized
Jul 26 02:58:54 node-5 kernel: [    5.225438] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 26 02:58:54 node-5 kernel: [    5.367931] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 26 02:58:54 node-5 kernel: [    5.403938] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 26 02:58:54 node-5 kernel: [    5.485606] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 02:58:54 node-5 kernel: [    5.684205] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 26 02:58:54 node-5 kernel: [    5.737976] XFS (dm-1): Mounting Filesystem
Jul 26 02:58:54 node-5 kernel: [    5.977857] XFS (dm-1): Ending clean mount
Jul 26 02:58:54 node-5 kernel: [    6.120138] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 02:58:54 node-5 kernel: [    6.155203] XFS (dm-2): Mounting Filesystem
Jul 26 02:58:54 node-5 kernel: [    6.248896] XFS (dm-2): Ending clean mount
Jul 26 02:58:54 node-5 kernel: [    6.351099] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 26 02:58:54 node-5 kernel: [    8.234567] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 26 02:58:54 node-5 kernel: [    8.248553] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 26 02:58:54 node-5 kernel: [    8.375386] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 26 02:58:54 node-5 kernel: [    8.375390] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 26 02:58:54 node-5 kernel: [    8.375393] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 26 02:58:54 node-5 kernel: [    8.375397] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 26 02:58:54 node-5 kernel: [    8.411618] systemd-udevd[802]: starting version 204
Jul 26 02:58:54 node-5 kernel: [    8.600054] power_meter ACPI000D:00: Found ACPI power meter.
Jul 26 02:58:54 node-5 kernel: [    8.600067] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 26 02:58:54 node-5 kernel: [    8.617492] wmi: Mapper loaded
Jul 26 02:58:54 node-5 kernel: [    8.619843] IPMI System Interface driver.
Jul 26 02:58:54 node-5 kernel: [    8.619915] ipmi_si: probing via ACPI
Jul 26 02:58:54 node-5 kernel: [    8.619934] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 26 02:58:54 node-5 kernel: [    8.619935] ipmi_si: Adding ACPI-specified kcs state machine
Jul 26 02:58:54 node-5 kernel: [    8.619957] ipmi_si: probing via SMBIOS
Jul 26 02:58:54 node-5 kernel: [    8.619958] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 26 02:58:54 node-5 kernel: [    8.619959] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 26 02:58:54 node-5 kernel: [    8.619961] ipmi_si: probing via SPMI
Jul 26 02:58:54 node-5 kernel: [    8.619962] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 26 02:58:54 node-5 kernel: [    8.619963] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 26 02:58:54 node-5 kernel: [    8.619965] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 26 02:58:54 node-5 kernel: [    8.632811] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 26 02:58:54 node-5 kernel: [    8.632815] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 26 02:58:54 node-5 kernel: [    8.632818] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 26 02:58:54 node-5 kernel: [    8.632819] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 26 02:58:54 node-5 kernel: [    8.632858] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 26 02:58:54 node-5 kernel: [    8.633990] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 26 02:58:54 node-5 kernel: [    8.697532] systemd-udevd[820]: renamed network interface eth0 to enp6s0
Jul 26 02:58:54 node-5 kernel: [    8.717377] systemd-udevd[822]: renamed network interface eth2 to enp8s0
Jul 26 02:58:54 node-5 kernel: [    8.741351] systemd-udevd[831]: renamed network interface eth1 to enp7s0
Jul 26 02:58:54 node-5 kernel: [    8.765828] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 26 02:58:54 node-5 kernel: [    8.765838] ipmi_si 00:09: IPMI kcs interface initialized
Jul 26 02:58:54 node-5 kernel: [    8.765995] systemd-udevd[819]: renamed network interface eth3 to enp9s0
Jul 26 02:58:54 node-5 kernel: [    9.023686] type=1400 audit(1469501907.072:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1087 comm="apparmor_parser"
Jul 26 02:58:54 node-5 kernel: [    9.023737] type=1400 audit(1469501907.072:3): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1088 comm="apparmor_parser"
Jul 26 02:58:54 node-5 kernel: [    9.023920] type=1400 audit(1469501907.072:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1088 comm="apparmor_parser"
Jul 26 02:58:54 node-5 kernel: [    9.023963] type=1400 audit(1469501907.072:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1087 comm="apparmor_parser"
Jul 26 02:58:54 node-5 kernel: [    9.024051] type=1400 audit(1469501907.072:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1088 comm="apparmor_parser"
Jul 26 02:58:54 node-5 kernel: [    9.024167] type=1400 audit(1469501907.072:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1087 comm="apparmor_parser"
Jul 26 02:58:54 node-5 kernel: [    9.031943] type=1400 audit(1469501907.080:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1080 comm="apparmor_parser"
Jul 26 02:58:54 node-5 kernel: [    9.032084] type=1400 audit(1469501907.080:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1080 comm="apparmor_parser"
Jul 26 02:58:54 node-5 kernel: [    9.032203] type=1400 audit(1469501907.080:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1080 comm="apparmor_parser"
Jul 26 02:58:54 node-5 kernel: [    9.043800] type=1400 audit(1469501907.092:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1086 comm="apparmor_parser"
Jul 26 02:58:54 node-5 kernel: [    9.575289] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 26 02:58:54 node-5 kernel: [    9.576365] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 26 02:58:54 node-5 kernel: [    9.760062] enic 0000:06:00.0 enp6s0: Link UP
Jul 26 02:58:54 node-5 kernel: [    9.761080] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 26 02:58:54 node-5 kernel: [    9.761089] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 26 02:58:54 node-5 kernel: [   19.489942] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 26 02:58:56 node-5 failsafe: Failsafe of 120 seconds reached.
Jul 26 02:58:56 node-5 kernel: [   37.879994] init: failsafe main process (8427) killed by TERM signal
Jul 26 02:58:56 node-5 dbus[8467]: [system] AppArmor D-Bus mediation is enabled
Jul 26 02:58:56 node-5 kernel: [   38.047393] audit_printk_skb: 30 callbacks suppressed
Jul 26 02:58:56 node-5 kernel: [   38.047395] type=1400 audit(1469501936.221:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8550 comm="apparmor_parser"
Jul 26 02:58:56 node-5 kernel: [   38.047571] type=1400 audit(1469501936.221:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8548 comm="apparmor_parser"
Jul 26 02:58:56 node-5 kernel: [   38.047577] type=1400 audit(1469501936.221:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8548 comm="apparmor_parser"
Jul 26 02:58:56 node-5 kernel: [   38.047580] type=1400 audit(1469501936.221:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8548 comm="apparmor_parser"
Jul 26 02:58:56 node-5 kernel: [   38.047966] type=1400 audit(1469501936.225:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8548 comm="apparmor_parser"
Jul 26 02:58:56 node-5 kernel: [   38.047969] type=1400 audit(1469501936.225:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8548 comm="apparmor_parser"
Jul 26 02:58:56 node-5 kernel: [   38.048189] type=1400 audit(1469501936.225:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8548 comm="apparmor_parser"
Jul 26 02:58:56 node-5 kernel: [   38.141480] type=1400 audit(1469501936.317:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8552 comm="apparmor_parser"
Jul 26 02:58:56 node-5 anacron[8621]: Anacron 2.3 started on 2016-07-26
Jul 26 02:58:56 node-5 cron[8586]: (CRON) INFO (pidfile fd = 3)
Jul 26 02:58:56 node-5 cron[8627]: (CRON) STARTUP (fork ok)
Jul 26 02:58:56 node-5 anacron[8621]: Will run job `cron.daily' in 5 min.
Jul 26 02:58:56 node-5 anacron[8621]: Will run job `cron.weekly' in 10 min.
Jul 26 02:58:56 node-5 anacron[8621]: Will run job `cron.monthly' in 15 min.
Jul 26 02:58:56 node-5 anacron[8621]: Jobs will be executed sequentially
Jul 26 02:58:56 node-5 multipathd: path checkers start up
Jul 26 02:58:56 node-5 cron[8627]: (CRON) INFO (Running @reboot jobs)
Jul 26 02:58:57 node-5 postfix/master[8765]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 26 02:59:00 node-5 puppet-agent[8949]: Reopening log files
Jul 26 02:59:01 node-5 puppet-agent[8949]: Could not request certificate: Connection refused - connect(2)
Jul 26 02:59:01 node-5 CRON[8980]: (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 26 02:59:12 node-5 puppet-user[9039]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 26 02:59:12 node-5 puppet-user[9039]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 26 02:59:13 node-5 puppet-user[9039]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 26 02:59:13 node-5 puppet-user[9039]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 26 02:59:13 node-5 puppet-user[9039]: Finished catalog run in 0.45 seconds
Jul 26 02:59:14 node-5 multipathd: uevent trigger error
Jul 26 02:59:14 node-5 puppet-user[9464]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 26 02:59:14 node-5 puppet-user[9464]: Compiled catalog for node-5.domain.tld in environment production in 0.10 seconds
Jul 26 02:59:15 node-5 puppet-user[9464]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 26 02:59:15 node-5 puppet-user[9464]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 26 02:59:15 node-5 puppet-user[9464]: (/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 26 02:59:15 node-5 puppet-user[9464]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 26 02:59:15 node-5 puppet-user[9464]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 26 02:59:15 node-5 puppet-user[9464]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 26 02:59:15 node-5 puppet-user[9464]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 26 02:59:15 node-5 puppet-user[9464]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 26 02:59:15 node-5 puppet-user[9464]: Finished catalog run in 0.08 seconds
Jul 26 02:59:16 node-5 puppet-user[9932]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 26 02:59:16 node-5 puppet-user[9932]: Compiled catalog for node-5.domain.tld in environment production in 0.09 seconds
Jul 26 02:59:16 node-5 puppet-user[9932]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 26 02:59:16 node-5 puppet-user[9932]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 26 02:59:16 node-5 puppet-user[9932]: Finished catalog run in 0.04 seconds
Jul 26 02:59:18 node-5 puppet-user[10392]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 26 02:59:18 node-5 puppet-user[10392]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 26 02:59:18 node-5 puppet-user[10392]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 26 02:59:18 node-5 puppet-user[10392]: Finished catalog run in 0.04 seconds
Jul 26 02:59:19 node-5 puppet-user[10841]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 26 02:59:19 node-5 puppet-user[10841]: Compiled catalog for node-5.domain.tld in environment production in 0.32 seconds
Jul 26 02:59:20 node-5 puppet-user[10841]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 26 02:59:20 node-5 puppet-user[10841]: (/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 26 02:59:20 node-5 puppet-user[10841]: Finished catalog run in 0.48 seconds
Jul 26 02:59:21 node-5 puppet-user[11322]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 26 02:59:22 node-5 puppet-user[11322]: Compiled catalog for node-5.domain.tld in environment production in 0.21 seconds
Jul 26 02:59:22 node-5 puppet-user[11322]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 26 02:59:22 node-5 puppet-user[11322]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 26 02:59:22 node-5 puppet-user[11322]: (/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 26 02:59:22 node-5 puppet-user[11322]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 26 02:59:22 node-5 puppet-user[11322]: Finished catalog run in 0.26 seconds
Jul 26 02:59:23 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 02:59:23 node-5 nailgun-agent: D, [2016-07-26T02:59:01.683091 #8983] DEBUG -- : Sleep for 22 seconds before sending request
Jul 26 02:59:23 node-5 nailgun-agent: I, [2016-07-26T02:59:23.713187 #8983]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 26 02:59:23 node-5 puppet-user[11797]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 26 02:59:24 node-5 puppet-user[11797]: Compiled catalog for node-5.domain.tld in environment production in 0.14 seconds
Jul 26 02:59:24 node-5 puppet-user[11797]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 26 02:59:24 node-5 kernel: [   65.975211] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 26 02:59:24 node-5 kernel: [   65.975266] 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 26 02:59:24 node-5 puppet-user[11797]: (/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 26 02:59:24 node-5 puppet-user[11797]: Finished catalog run in 0.07 seconds
Jul 26 02:59:24 node-5 nailgun-agent: D, [2016-07-26T02:59:24.634216 #8983] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 26 02:59:25 node-5 puppet-user[12389]: (Scope(Class[main])) MODULAR: sync_time
Jul 26 02:59:25 node-5 puppet-user[12389]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 26 02:59:26 node-5 ntpdate[12802]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 26 02:59:32 node-5 ntpdate[12802]: adjust time server 10.20.0.2 offset -0.042204 sec
Jul 26 02:59:32 node-5 puppet-user[12389]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 26 02:59:32 node-5 puppet-user[12389]: Finished catalog run in 6.17 seconds
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.596342 #8983] DEBUG -- : Trying to find block devices
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.596417 #8983] DEBUG -- : Found block device: sda
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.596473 #8983] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.596496 #8983] DEBUG -- : Trying to get list of physical devices
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.596644 #8983] DEBUG -- : Getting udev properties for device: sda
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.598413 #8983] 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 26 02:59:36 node-5 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"371", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.598460 #8983] DEBUG -- : Trying to find out if device sda is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.598504 #8983] DEBUG -- : Device sda removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.598518 #8983] DEBUG -- : Device sda seems to be appropriate
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.598954 #8983] DEBUG -- : Getting udev properties for device: dm-0
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.600488 #8983] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-S5Mxfvm0Sx80QrIuwPJeP2NBkH1qy0qze6qzBX303TI5IBppkpWB2mVLG3VJLguR /dev/disk/by-uuid/d9392992-a7ad-4b29-ba4f-ad11ec7c88eb /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-S5Mxfvm0Sx80QrIuwPJeP2NBkH1qy0qze6qzBX303TI5IBppkpWB2mVLG3VJLguR", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d9392992-a7ad-4b29-ba4f-ad11ec7c88eb", "ID_FS_UUID_ENC"=>"d9392992-a7ad-4b29-ba4f-ad11ec7c88eb", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48
Jul 26 02:59:36 node-5 nailgun-agent: 7", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.600515 #8983] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.600546 #8983] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.600581 #8983] DEBUG -- : Device dm-0 seems to be appropriate
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.600594 #8983] DEBUG -- : Getting udev properties for device: dm-1
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.602159 #8983] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-0gjAuA0hyMQDtydU9JQtQoiYYrIrgaJPzhv1h3fbzD52NfI3DBTKmXOjELwA2Uve /dev/disk/by-uuid/e2799871-24bb-4d5c-a26b-5f2e7e4a60f7 /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-0gjAuA0hyMQDtydU9JQtQoiYYrIrgaJPzhv1h3fbzD52NfI3DBTKmXOjELwA2Uve", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e2799871-24bb-4d5c-a26b-5f2e7e4a60f7", "ID_FS_UUID_ENC"=>"e2799871-24bb-4d5c-a26b-5f2e7e4a60f7", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"20505", "nomdmonddf"=>"1", "nomd
Jul 26 02:59:36 node-5 nailgun-agent: monisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.602198 #8983] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.602262 #8983] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.602275 #8983] DEBUG -- : Device dm-1 seems to be appropriate
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.602300 #8983] DEBUG -- : Getting udev properties for device: dm-2
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.603813 #8983] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-dIGRaaRmz5mAPe0qXlf9SOOvjavP9mzkrHY47ODJh0rCmWYUEPthU47UrRIf8YIR /dev/disk/by-uuid/95e4735f-1494-4798-98d4-4bf771d2023b /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-dIGRaaRmz5mAPe0qXlf9SOOvjavP9mzkrHY47ODJh0rCmWYUEPthU47UrRIf8YIR", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"95e4735f-1494-4798-98d4-4bf771d2023b", "ID_FS_UUID_ENC"=>"95e4735f-1494-4798-98d4-4bf771d2023b", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"34
Jul 26 02:59:36 node-5 nailgun-agent: 572", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.603848 #8983] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.603888 #8983] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.603901 #8983] DEBUG -- : Device dm-2 seems to be appropriate
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.603924 #8983] DEBUG -- : Getting udev properties for device: dm-3
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.605495 #8983] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-uCg3GmUkS4zjekeQ4NfMwO2aD2ZwGeKHNK9V9UT8pgTPcB2g7TCXszKIl266Pdl3 /dev/disk/by-uuid/7db1035e-e662-467d-aa0e-506115b9c189 /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-uCg3GmUkS4zjekeQ4NfMwO2aD2ZwGeKHNK9V9UT8pgTPcB2g7TCXszKIl266Pdl3", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"7db1035e-e662-467d-aa0e-506115b9c189", "ID_FS_UUID_ENC"=>"7db1035e-e662-467d-aa0e-506115b9c189", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37582", "nomdmond
Jul 26 02:59:36 node-5 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.605518 #8983] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.605550 #8983] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.605572 #8983] DEBUG -- : Device dm-3 seems to be appropriate
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.605586 #8983] DEBUG -- : Getting udev properties for device: dm-4
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.607173 #8983] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-QJBFzdaItgmUX2M0r3PfycQErAYyGsj51bLEPKIzQjxSZTGmGAGakG01N0LEjncI /dev/disk/by-uuid/21af716b-30ea-43f0-9f14-1f4f49dfa095 /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-QJBFzdaItgmUX2M0r3PfycQErAYyGsj51bLEPKIzQjxSZTGmGAGakG01N0LEjncI", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"21af716b-30ea-43f0-9f14-1f4f49dfa095", "ID_FS_UUID_ENC"=>"21af716b-30ea-43f0-9f14-1f4f49dfa095", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"41324", "nomdmonddf"=>"1", 
Jul 26 02:59:36 node-5 nailgun-agent: "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.607215 #8983] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.607242 #8983] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.607262 #8983] DEBUG -- : Device dm-4 seems to be appropriate
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.607275 #8983] DEBUG -- : Getting udev properties for device: dm-5
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.608820 #8983] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-Pews1Uz8kycDSEqjbsFgwc3GcWL2QwMXc0rkz722nAr5tRMUTEoLweIFIIeGHg0y /dev/disk/by-uuid/b5c2d4c3-9cd8-4679-a00f-a8c701d1fa62 /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-Pews1Uz8kycDSEqjbsFgwc3GcWL2QwMXc0rkz722nAr5tRMUTEoLweIFIIeGHg0y", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b5c2d4c3-9cd8-4679-a00f-a8c701d1fa62", "ID_FS_UUID_ENC"=>"b5c2d4c3-9cd8-4679-a00f-a8c701d1fa62", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48762", "nomdmonddf"=>"1", "nomd
Jul 26 02:59:36 node-5 nailgun-agent: monisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.608855 #8983] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.608903 #8983] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.608929 #8983] DEBUG -- : Device dm-5 seems to be appropriate
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.608941 #8983] DEBUG -- : Getting udev properties for device: dm-6
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.610442 #8983] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-Pews1Uz8kycDSEqjbsFgwc3GcWL2QwMXbOmWiLZNXciEtsbNW5HWdoj2J9cPfNEx /dev/disk/by-uuid/65e53f56-5515-4e8b-92fb-802f338cf72c /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-Pews1Uz8kycDSEqjbsFgwc3GcWL2QwMXbOmWiLZNXciEtsbNW5HWdoj2J9cPfNEx", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"65e53f56-5515-4e8b-92fb-802f338cf72c", "ID_FS_UUID_ENC"=>"65e53f56-5515-4e8b-92fb-802f338cf72c", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49183", "nomdmonddf"=>"1", "nomdmonisw"
Jul 26 02:59:36 node-5 nailgun-agent: =>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.610466 #8983] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.610493 #8983] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.610504 #8983] DEBUG -- : Device dm-6 seems to be appropriate
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.610542 #8983] DEBUG -- : Getting udev properties for device: ram0
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.611912 #8983] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96353", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.611932 #8983] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.611967 #8983] DEBUG -- : Device ram0 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.611991 #8983] DEBUG -- : Getting udev properties for device: ram1
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.617050 #8983] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96533", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.617073 #8983] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.617110 #8983] DEBUG -- : Device ram1 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.617127 #8983] DEBUG -- : Getting udev properties for device: ram2
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.618672 #8983] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98604", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.618693 #8983] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.618726 #8983] DEBUG -- : Device ram2 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.618743 #8983] DEBUG -- : Getting udev properties for device: ram3
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.620096 #8983] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98922", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.620116 #8983] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.620147 #8983] DEBUG -- : Device ram3 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.620165 #8983] DEBUG -- : Getting udev properties for device: ram4
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.621515 #8983] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99209", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.621574 #8983] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.621615 #8983] DEBUG -- : Device ram4 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.621632 #8983] DEBUG -- : Getting udev properties for device: ram5
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.622972 #8983] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99574", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.622991 #8983] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.623052 #8983] DEBUG -- : Device ram5 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.623068 #8983] DEBUG -- : Getting udev properties for device: ram6
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.624392 #8983] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99926", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.624413 #8983] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.624441 #8983] DEBUG -- : Device ram6 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.624480 #8983] DEBUG -- : Getting udev properties for device: ram7
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.625836 #8983] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"542", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.625856 #8983] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.625883 #8983] DEBUG -- : Device ram7 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.625900 #8983] DEBUG -- : Getting udev properties for device: ram8
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.628037 #8983] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"821", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.628057 #8983] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.628088 #8983] DEBUG -- : Device ram8 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.628105 #8983] DEBUG -- : Getting udev properties for device: ram9
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.629454 #8983] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1045", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.629474 #8983] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.629507 #8983] DEBUG -- : Device ram9 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.629524 #8983] DEBUG -- : Getting udev properties for device: loop0
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.630888 #8983] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"94605", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.630908 #8983] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.630942 #8983] DEBUG -- : Device loop0 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.630960 #8983] DEBUG -- : Getting udev properties for device: loop1
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.632288 #8983] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"94824", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.632347 #8983] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.632385 #8983] DEBUG -- : Device loop1 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.632403 #8983] DEBUG -- : Getting udev properties for device: loop2
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.633754 #8983] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"94964", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.633775 #8983] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.633836 #8983] DEBUG -- : Device loop2 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.633854 #8983] DEBUG -- : Getting udev properties for device: loop3
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.635174 #8983] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95092", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.635194 #8983] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.635221 #8983] DEBUG -- : Device loop3 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.635260 #8983] DEBUG -- : Getting udev properties for device: loop4
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.636584 #8983] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95276", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.636604 #8983] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.636629 #8983] DEBUG -- : Device loop4 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.636646 #8983] DEBUG -- : Getting udev properties for device: loop5
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.637991 #8983] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95525", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.638010 #8983] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.638042 #8983] DEBUG -- : Device loop5 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.638059 #8983] DEBUG -- : Getting udev properties for device: loop6
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.639412 #8983] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95788", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.639432 #8983] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.639463 #8983] DEBUG -- : Device loop6 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.639480 #8983] DEBUG -- : Getting udev properties for device: loop7
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.640846 #8983] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95935", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.640867 #8983] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.640903 #8983] DEBUG -- : Device loop7 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.640919 #8983] DEBUG -- : Getting udev properties for device: ram10
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.642291 #8983] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96683", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.642312 #8983] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.642345 #8983] DEBUG -- : Device ram10 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.642361 #8983] DEBUG -- : Getting udev properties for device: ram11
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.643688 #8983] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96906", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.643708 #8983] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.643786 #8983] DEBUG -- : Device ram11 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.643804 #8983] DEBUG -- : Getting udev properties for device: ram12
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.645135 #8983] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97070", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.645155 #8983] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.645181 #8983] DEBUG -- : Device ram12 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.645222 #8983] DEBUG -- : Getting udev properties for device: ram13
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.646545 #8983] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97385", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.646565 #8983] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.646593 #8983] DEBUG -- : Device ram13 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.646611 #8983] DEBUG -- : Getting udev properties for device: ram14
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.647959 #8983] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97810", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.647978 #8983] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.648005 #8983] DEBUG -- : Device ram14 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.648022 #8983] DEBUG -- : Getting udev properties for device: ram15
Jul 26 02:59:36 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649358 #8983] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98262", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649378 #8983] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649404 #8983] DEBUG -- : Device ram15 removable parameter: "0"
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649435 #8983] 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 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649455 #8983] DEBUG -- : Block device seems to be physical data storage: sda
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649491 #8983] DEBUG -- : Found block device: dm-0
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649540 #8983] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649553 #8983] DEBUG -- : Found block device: dm-1
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649563 #8983] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649573 #8983] DEBUG -- : Found block device: dm-2
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649584 #8983] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649592 #8983] DEBUG -- : Found block device: dm-3
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649602 #8983] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649610 #8983] DEBUG -- : Found block device: dm-4
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649620 #8983] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649628 #8983] DEBUG -- : Found block device: dm-5
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649658 #8983] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649667 #8983] DEBUG -- : Found block device: dm-6
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649677 #8983] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649685 #8983] DEBUG -- : Found block device: ram0
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649694 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649703 #8983] DEBUG -- : Found block device: ram1
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649712 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649730 #8983] DEBUG -- : Found block device: ram2
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649741 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649749 #8983] DEBUG -- : Found block device: ram3
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649788 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649796 #8983] DEBUG -- : Found block device: ram4
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649805 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649814 #8983] DEBUG -- : Found block device: ram5
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649823 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649831 #8983] DEBUG -- : Found block device: ram6
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649840 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649848 #8983] DEBUG -- : Found block device: ram7
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649857 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649886 #8983] DEBUG -- : Found block device: ram8
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649896 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649904 #8983] DEBUG -- : Found block device: ram9
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649913 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649921 #8983] DEBUG -- : Found block device: loop0
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649930 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649938 #8983] DEBUG -- : Found block device: loop1
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649948 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649957 #8983] DEBUG -- : Found block device: loop2
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649966 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.649973 #8983] DEBUG -- : Found block device: loop3
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650011 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650020 #8983] DEBUG -- : Found block device: loop4
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650028 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650036 #8983] DEBUG -- : Found block device: loop5
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650045 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650053 #8983] DEBUG -- : Found block device: loop6
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650062 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650069 #8983] DEBUG -- : Found block device: loop7
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650078 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650087 #8983] DEBUG -- : Found block device: ram10
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650118 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650126 #8983] DEBUG -- : Found block device: ram11
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650136 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650144 #8983] DEBUG -- : Found block device: ram12
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650153 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650161 #8983] DEBUG -- : Found block device: ram13
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650169 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650177 #8983] DEBUG -- : Found block device: ram14
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650186 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650193 #8983] DEBUG -- : Found block device: ram15
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650223 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.650251 #8983] 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 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.741536 #8983] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 26 02:59:36 node-5 nailgun-agent: D, [2016-07-26T02:59:36.741607 #8983] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 26 02:59:38 node-5 puppet-user[13315]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 26 02:59:38 node-5 puppet-user[13315]: Compiled catalog for node-5.domain.tld in environment production in 0.09 seconds
Jul 26 02:59:38 node-5 puppet-user[13315]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 26 02:59:38 node-5 puppet-user[13315]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 26 02:59:38 node-5 puppet-user[13315]: Finished catalog run in 0.08 seconds
Jul 26 02:59:40 node-5 puppet-user[13779]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 26 02:59:41 node-5 puppet-user[13779]: Compiled catalog for node-5.domain.tld in environment production in 1.03 seconds
Jul 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:41 node-5 puppet-user[13779]: (/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 26 02:59:48 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630052 #8983] DEBUG -- : Trying to find block devices
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630126 #8983] DEBUG -- : Found block device: sda
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630151 #8983] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630167 #8983] DEBUG -- : Block device seems to be physical data storage: sda
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630186 #8983] DEBUG -- : Found block device: dm-0
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630196 #8983] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630206 #8983] DEBUG -- : Found block device: dm-1
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630216 #8983] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630242 #8983] DEBUG -- : Found block device: dm-2
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630251 #8983] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630260 #8983] DEBUG -- : Found block device: dm-3
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630269 #8983] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630277 #8983] DEBUG -- : Found block device: dm-4
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630286 #8983] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630294 #8983] DEBUG -- : Found block device: dm-5
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630321 #8983] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630331 #8983] DEBUG -- : Found block device: dm-6
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630340 #8983] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630359 #8983] DEBUG -- : Found block device: ram0
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630367 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630375 #8983] DEBUG -- : Found block device: ram1
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630384 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630392 #8983] DEBUG -- : Found block device: ram2
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630400 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630408 #8983] DEBUG -- : Found block device: ram3
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630417 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630443 #8983] DEBUG -- : Found block device: ram4
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630452 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630461 #8983] DEBUG -- : Found block device: ram5
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630470 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630478 #8983] DEBUG -- : Found block device: ram6
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630486 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630494 #8983] DEBUG -- : Found block device: ram7
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630503 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630511 #8983] DEBUG -- : Found block device: ram8
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630529 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630538 #8983] DEBUG -- : Found block device: ram9
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630547 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630565 #8983] DEBUG -- : Found block device: loop0
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630575 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630583 #8983] DEBUG -- : Found block device: loop1
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630591 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630600 #8983] DEBUG -- : Found block device: loop2
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630623 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630631 #8983] DEBUG -- : Found block device: loop3
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630641 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630649 #8983] DEBUG -- : Found block device: loop4
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630668 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630676 #8983] DEBUG -- : Found block device: loop5
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630684 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630692 #8983] DEBUG -- : Found block device: loop6
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630709 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630717 #8983] DEBUG -- : Found block device: loop7
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630726 #8983] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.630744 #8983] DEBUG -- : Found block device: ram10
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638087 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638144 #8983] DEBUG -- : Found block device: ram11
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638160 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638172 #8983] DEBUG -- : Found block device: ram12
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638181 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638189 #8983] DEBUG -- : Found block device: ram13
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638203 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638212 #8983] DEBUG -- : Found block device: ram14
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638220 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638227 #8983] DEBUG -- : Found block device: ram15
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638236 #8983] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.638270 #8983] 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 26 02:59:48 node-5 nailgun-agent: D, [2016-07-26T02:59:48.831135 #8983] DEBUG -- : Response: status: 200 body: {"id": 5}
Jul 26 02:59:48 node-5 nailgun-agent: I, [2016-07-26T02:59:48.831302 #8983]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 26 02:59:51 node-5 kernel: [   93.694905] init: plymouth-upstart-bridge main process ended, respawning
Jul 26 02:59:52 node-5 puppet-agent[8949]: Could not run: SIGTERM
Jul 26 02:59:52 node-5 kernel: [   93.962939] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 26 02:59:52 node-5 ec2: 
Jul 26 02:59:52 node-5 ec2: #############################################################
Jul 26 02:59:52 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 26 02:59:52 node-5 ec2: 1024 4e:34:a6:bf:65:38:0b:81:0f:dc:18:cd:fd:ed:41:a1  root@node-5.domain.tld (DSA)
Jul 26 02:59:52 node-5 ec2: 256 33:22:14:7a:de:44:5b:1e:69:c2:bc:b9:35:2f:6a:22  root@node-5.domain.tld (ECDSA)
Jul 26 02:59:52 node-5 ec2: 256 37:88:fe:9d:26:33:9e:2e:aa:bd:82:94:72:6b:cc:86  root@node-5.domain.tld (ED25519)
Jul 26 02:59:52 node-5 ec2: 2048 11:36:fc:b0:95:0f:7b:d8:fb:4c:63:a2:7e:25:0a:20  root@node-5.domain.tld (RSA)
Jul 26 02:59:52 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 26 02:59:52 node-5 ec2: #############################################################
Jul 26 02:59:57 node-5 puppet-user[13779]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 26 02:59:57 node-5 puppet-user[13779]: Finished catalog run in 16.76 seconds
Jul 26 03:00:00 node-5 puppet-user[15257]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 26 03:00:00 node-5 puppet-user[15257]: Compiled catalog for node-5.domain.tld in environment production in 0.13 seconds
Jul 26 03:00:01 node-5 CRON[15732]: (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 26 03:00:05 node-5 puppet-user[15257]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 26 03:00:28 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 03:00:29 node-5 nailgun-agent: I, [2016-07-26T03:00:29.004399 #15735]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 26 03:00:39 node-5 puppet-user[15257]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 26 03:00:39 node-5 puppet-user[15257]: Finished catalog run in 38.64 seconds
Jul 26 03:00:41 node-5 puppet-user[17924]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 26 03:00:41 node-5 puppet-user[17924]: Compiled catalog for node-5.domain.tld in environment production in 0.62 seconds
Jul 26 03:00:41 node-5 puppet-user[17924]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 26 03:00:41 node-5 puppet-user[17924]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 26 03:00:41 node-5 puppet-user[17924]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 26 03:00:41 node-5 puppet-user[17924]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 26 03:00:41 node-5 puppet-user[17924]: Finished catalog run in 0.09 seconds
Jul 26 03:00:41 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 26 03:00:42 node-5 nailgun-agent: I, [2016-07-26T03:00:42.119929 #15735]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 26 03:00:43 node-5 puppet-user[18563]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 26 03:00:44 node-5 puppet-user[18563]: Compiled catalog for node-5.domain.tld in environment production in 0.91 seconds
Jul 26 03:00:45 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 26 03:00:45 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 26 03:00:45 node-5 crontab[18996]: (root) LIST (root)
Jul 26 03:00:45 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 26 03:00:45 node-5 crontab[18997]: (root) REPLACE (root)
Jul 26 03:00:47 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 26 03:00:48 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 26 03:00:48 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 26 03:00:48 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:48 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 26 03:00:48 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 26 03:00:48 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 26 03:00:48 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:48 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/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 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 26 03:00:49 node-5 puppet-user[18563]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 26 03:00:50 node-5 puppet-user[18563]: (/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 26 03:00:50 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8400" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 26 03:00:50 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 26 03:00:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:00:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:00:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:00:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:00:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:00:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:01:11 node-5 multipathd: uevent trigger error
<27>Jul 26 03:01:11 node-5 multipathd: uevent trigger error
<27>Jul 26 03:01:11 node-5 multipathd: uevent trigger error
<27>Jul 26 03:01:11 node-5 multipathd: uevent trigger error
<27>Jul 26 03:01:11 node-5 multipathd: uevent trigger error
<27>Jul 26 03:01:14 node-5 multipathd: uevent trigger error
<27>Jul 26 03:01:14 node-5 multipathd: uevent trigger error
<27>Jul 26 03:01:14 node-5 multipathd: uevent trigger error
<27>Jul 26 03:01:14 node-5 multipathd: uevent trigger error
<27>Jul 26 03:01:14 node-5 multipathd: uevent trigger error
<27>Jul 26 03:02:15 node-5 ntpdate[30022]: no servers can be used, exiting
<27>Jul 26 03:02:16 node-5 ntpdate[30268]: no servers can be used, exiting
<27>Jul 26 03:02:47 node-5 multipathd: uevent trigger error
<27>Jul 26 03:02:47 node-5 multipathd: uevent trigger error
<27>Jul 26 03:02:47 node-5 multipathd: uevent trigger error
<27>Jul 26 03:02:47 node-5 multipathd: uevent trigger error
<27>Jul 26 03:02:47 node-5 multipathd: uevent trigger error
<27>Jul 26 03:02:50 node-5 multipathd: uevent trigger error
<27>Jul 26 03:02:50 node-5 multipathd: uevent trigger error
<27>Jul 26 03:02:50 node-5 multipathd: uevent trigger error
<27>Jul 26 03:02:50 node-5 multipathd: uevent trigger error
<27>Jul 26 03:02:50 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:06 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:56 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:56 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:56 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:56 node-5 multipathd: uevent trigger error
<27>Jul 26 03:03:56 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:34 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 26 03:04:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:42 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:42 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:42 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:42 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:42 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:48 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:48 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:48 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:48 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:48 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:48 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:56 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:56 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:56 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:56 node-5 multipathd: uevent trigger error
<27>Jul 26 03:04:56 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:02 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:02 node-5 haproxy[18647]: 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 26 03:05:02 node-5 haproxy[18647]: proxy odl-jetty has no server available!
<27>Jul 26 03:05:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:02 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:04 node-5 haproxy[18647]: 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 26 03:05:04 node-5 haproxy[18647]: proxy odl-neutron-endpoint has no server available!
<129>Jul 26 03:05:05 node-5 haproxy[19836]: 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 26 03:05:07 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:07 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:07 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:07 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:07 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:07 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:07 node-5 haproxy[19836]: 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 26 03:05:07 node-5 haproxy[19836]: proxy odl-jetty has no server available!
<27>Jul 26 03:05:10 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:10 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:10 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:10 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:10 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:12 node-5 haproxy[19836]: 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 26 03:05:12 node-5 haproxy[19836]: proxy odl-neutron-endpoint has no server available!
<129>Jul 26 03:05:13 node-5 haproxy[22069]: 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 26 03:05:14 node-5 haproxy[22073]: 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 26 03:05:16 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:16 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:16 node-5 haproxy[22073]: 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 26 03:05:16 node-5 haproxy[22073]: proxy odl-jetty has no server available!
<129>Jul 26 03:05:18 node-5 haproxy[23301]: 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 26 03:05:19 node-5 haproxy[23305]: 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 26 03:05:19 node-5 haproxy[23305]: 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 26 03:05:21 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:21 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:21 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:21 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:21 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:22 node-5 haproxy[23305]: 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 26 03:05:22 node-5 haproxy[23305]: proxy odl-jetty has no server available!
<129>Jul 26 03:05:23 node-5 haproxy[24556]: Server keystone-1/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 26 03:05:24 node-5 haproxy[24560]: Server keystone-2/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 26 03:05:24 node-5 haproxy[24560]: 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 26 03:05:24 node-5 haproxy[24560]: 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 26 03:05:25 node-5 haproxy[24560]: 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 26 03:05:26 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:26 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:26 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:26 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:26 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:27 node-5 haproxy[24560]: 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 26 03:05:27 node-5 haproxy[24560]: proxy odl-jetty has no server available!
<129>Jul 26 03:05:29 node-5 haproxy[25894]: Server keystone-1/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 26 03:05:29 node-5 haproxy[25894]: Server keystone-2/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 26 03:05:29 node-5 haproxy[25894]: 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 26 03:05:29 node-5 haproxy[25894]: 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 26 03:05:30 node-5 haproxy[25894]: 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 26 03:05:30 node-5 haproxy[25894]: 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 26 03:05:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:31 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:32 node-5 haproxy[25894]: 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 26 03:05:32 node-5 haproxy[25894]: Server aodh/node-4 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 26 03:05:32 node-5 haproxy[25894]: proxy aodh has no server available!
<129>Jul 26 03:05:32 node-5 haproxy[25894]: 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 26 03:05:32 node-5 haproxy[25894]: proxy odl-jetty has no server available!
<129>Jul 26 03:05:33 node-5 haproxy[27076]: Server keystone-1/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 26 03:05:34 node-5 haproxy[27080]: Server keystone-2/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 26 03:05:34 node-5 haproxy[27080]: 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 26 03:05:34 node-5 haproxy[27080]: 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 26 03:05:35 node-5 haproxy[27080]: 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 26 03:05:35 node-5 haproxy[27080]: 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 26 03:05:35 node-5 haproxy[27080]: 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 26 03:05:36 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:36 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:36 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:36 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:36 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:37 node-5 haproxy[27080]: Server aodh/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 26 03:05:37 node-5 haproxy[27080]: Server aodh/node-4 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 26 03:05:37 node-5 haproxy[27080]: proxy aodh has no server available!
<129>Jul 26 03:05:37 node-5 haproxy[27080]: 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 26 03:05:37 node-5 haproxy[27080]: Server ceilometer/node-4 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 26 03:05:37 node-5 haproxy[27080]: proxy ceilometer has no server available!
<129>Jul 26 03:05:37 node-5 haproxy[27080]: 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 26 03:05:37 node-5 haproxy[27080]: proxy odl-jetty has no server available!
<129>Jul 26 03:05:39 node-5 haproxy[28275]: Server keystone-1/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 26 03:05:39 node-5 haproxy[28275]: Server keystone-2/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 26 03:05:39 node-5 haproxy[28275]: 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 26 03:05:39 node-5 haproxy[28275]: 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 26 03:05:40 node-5 haproxy[28275]: 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 26 03:05:40 node-5 haproxy[28275]: 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 26 03:05:40 node-5 haproxy[28275]: 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 26 03:05:41 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:41 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:41 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:41 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:41 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:41 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:41 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:42 node-5 haproxy[28275]: 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 26 03:05:42 node-5 haproxy[28275]: Server aodh/node-4 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 26 03:05:42 node-5 haproxy[28275]: proxy aodh has no server available!
<129>Jul 26 03:05:42 node-5 haproxy[28275]: 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 26 03:05:42 node-5 haproxy[28275]: Server ceilometer/node-4 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 26 03:05:42 node-5 haproxy[28275]: proxy ceilometer has no server available!
<129>Jul 26 03:05:42 node-5 haproxy[28275]: 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 26 03:05:42 node-5 haproxy[28275]: proxy odl-jetty has no server available!
<129>Jul 26 03:05:44 node-5 haproxy[29645]: Server horizon/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 26 03:05:44 node-5 haproxy[29645]: Server keystone-1/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 26 03:05:44 node-5 haproxy[29645]: Server keystone-2/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 26 03:05:44 node-5 haproxy[29645]: 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 26 03:05:44 node-5 haproxy[29645]: 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 26 03:05:45 node-5 haproxy[29645]: 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 26 03:05:45 node-5 haproxy[29645]: 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 26 03:05:45 node-5 haproxy[29645]: 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 26 03:05:45 node-5 haproxy[29645]: Server horizon/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 26 03:05:45 node-5 haproxy[29645]: Server horizon/node-4 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 26 03:05:45 node-5 haproxy[29645]: proxy horizon has no server available!
<27>Jul 26 03:05:46 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:46 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:46 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:46 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:46 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:47 node-5 haproxy[29645]: 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 26 03:05:47 node-5 haproxy[29645]: Server aodh/node-4 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 26 03:05:47 node-5 haproxy[29645]: proxy aodh has no server available!
<129>Jul 26 03:05:47 node-5 haproxy[29645]: 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 26 03:05:47 node-5 haproxy[29645]: Server ceilometer/node-4 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 26 03:05:47 node-5 haproxy[29645]: proxy ceilometer has no server available!
<129>Jul 26 03:05:47 node-5 haproxy[29645]: 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 26 03:05:47 node-5 haproxy[29645]: proxy odl-jetty has no server available!
<129>Jul 26 03:05:49 node-5 haproxy[30877]: Server horizon/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 26 03:05:50 node-5 haproxy[30883]: Server keystone-1/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 26 03:05:50 node-5 haproxy[30883]: Server keystone-2/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 26 03:05:50 node-5 haproxy[30883]: 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 26 03:05:50 node-5 haproxy[30883]: 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 26 03:05:50 node-5 haproxy[30883]: 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 26 03:05:50 node-5 haproxy[30883]: 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 26 03:05:51 node-5 haproxy[30883]: 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 26 03:05:51 node-5 haproxy[30883]: 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 26 03:05:51 node-5 haproxy[30883]: 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 26 03:05:51 node-5 haproxy[30883]: 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 26 03:05:51 node-5 haproxy[30883]: Server horizon/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 26 03:05:51 node-5 haproxy[30883]: Server horizon/node-4 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 26 03:05:51 node-5 haproxy[30883]: proxy horizon has no server available!
<27>Jul 26 03:05:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:52 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:52 node-5 haproxy[30883]: 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 26 03:05:52 node-5 haproxy[30883]: Server glance-registry/node-4 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 26 03:05:52 node-5 haproxy[30883]: proxy glance-registry has no server available!
<129>Jul 26 03:05:53 node-5 haproxy[30883]: 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 26 03:05:53 node-5 haproxy[30883]: Server aodh/node-4 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 26 03:05:53 node-5 haproxy[30883]: proxy aodh has no server available!
<129>Jul 26 03:05:53 node-5 haproxy[30883]: 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 26 03:05:53 node-5 haproxy[30883]: Server ceilometer/node-4 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 26 03:05:53 node-5 haproxy[30883]: proxy ceilometer has no server available!
<129>Jul 26 03:05:53 node-5 haproxy[30883]: 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 26 03:05:53 node-5 haproxy[30883]: proxy odl-jetty has no server available!
<129>Jul 26 03:05:55 node-5 haproxy[32133]: Server horizon/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 26 03:05:55 node-5 haproxy[32133]: Server keystone-1/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 26 03:05:55 node-5 haproxy[32133]: Server keystone-2/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 26 03:05:55 node-5 haproxy[32133]: 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 26 03:05:56 node-5 haproxy[32137]: 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 26 03:05:56 node-5 haproxy[32137]: 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 26 03:05:56 node-5 haproxy[32137]: 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 26 03:05:56 node-5 haproxy[32137]: 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 26 03:05:56 node-5 haproxy[32137]: 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 26 03:05:56 node-5 haproxy[32137]: 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 26 03:05:56 node-5 haproxy[32137]: 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 26 03:05:57 node-5 haproxy[32137]: 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 26 03:05:57 node-5 haproxy[32137]: 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 26 03:05:57 node-5 haproxy[32137]: 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 26 03:05:57 node-5 haproxy[32137]: Server horizon/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 26 03:05:57 node-5 haproxy[32137]: Server horizon/node-4 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 26 03:05:57 node-5 haproxy[32137]: proxy horizon has no server available!
<27>Jul 26 03:05:58 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:58 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:58 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:58 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:58 node-5 multipathd: uevent trigger error
<27>Jul 26 03:05:58 node-5 multipathd: uevent trigger error
<129>Jul 26 03:05:58 node-5 haproxy[32137]: 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 26 03:05:58 node-5 haproxy[32137]: Server glance-registry/node-4 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 26 03:05:58 node-5 haproxy[32137]: proxy glance-registry has no server available!
<129>Jul 26 03:05:58 node-5 haproxy[32137]: 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 26 03:05:58 node-5 haproxy[32137]: Server aodh/node-4 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 26 03:05:58 node-5 haproxy[32137]: proxy aodh has no server available!
<129>Jul 26 03:05:59 node-5 haproxy[32137]: 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 26 03:05:59 node-5 haproxy[32137]: Server ceilometer/node-4 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 26 03:05:59 node-5 haproxy[32137]: proxy ceilometer has no server available!
<129>Jul 26 03:05:59 node-5 haproxy[32137]: 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 26 03:05:59 node-5 haproxy[32137]: Server nova-novncproxy/node-4 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 26 03:05:59 node-5 haproxy[32137]: proxy nova-novncproxy has no server available!
<129>Jul 26 03:05:59 node-5 haproxy[32137]: 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 26 03:05:59 node-5 haproxy[32137]: proxy odl-jetty has no server available!
<129>Jul 26 03:06:00 node-5 haproxy[888]: Server horizon/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 26 03:06:00 node-5 haproxy[888]: Server keystone-1/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 26 03:06:00 node-5 haproxy[888]: Server keystone-2/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 26 03:06:01 node-5 haproxy[892]: 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 26 03:06:01 node-5 haproxy[892]: 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 26 03:06:01 node-5 haproxy[892]: 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 26 03:06:01 node-5 haproxy[892]: 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 26 03:06:01 node-5 haproxy[892]: 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 26 03:06:01 node-5 haproxy[892]: 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 26 03:06:01 node-5 haproxy[892]: 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 26 03:06:01 node-5 haproxy[892]: 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 26 03:06:02 node-5 haproxy[892]: 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 26 03:06:02 node-5 haproxy[892]: 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 26 03:06:02 node-5 haproxy[892]: 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 26 03:06:02 node-5 haproxy[892]: 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 26 03:06:02 node-5 haproxy[892]: Server horizon/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 26 03:06:02 node-5 haproxy[892]: Server horizon/node-4 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 26 03:06:02 node-5 haproxy[892]: proxy horizon has no server available!
<27>Jul 26 03:06:03 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:03 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:03 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:03 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:03 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:03 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:03 node-5 multipathd: uevent trigger error
<129>Jul 26 03:06:03 node-5 haproxy[892]: 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 26 03:06:03 node-5 haproxy[892]: Server glance-registry/node-4 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 26 03:06:03 node-5 haproxy[892]: proxy glance-registry has no server available!
<129>Jul 26 03:06:04 node-5 haproxy[892]: 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 26 03:06:04 node-5 haproxy[892]: Server aodh/node-4 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 26 03:06:04 node-5 haproxy[892]: proxy aodh has no server available!
<129>Jul 26 03:06:04 node-5 haproxy[892]: 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 26 03:06:04 node-5 haproxy[892]: Server ceilometer/node-4 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 26 03:06:04 node-5 haproxy[892]: proxy ceilometer has no server available!
<129>Jul 26 03:06:04 node-5 haproxy[892]: 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 26 03:06:04 node-5 haproxy[892]: Server nova-novncproxy/node-4 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 26 03:06:04 node-5 haproxy[892]: proxy nova-novncproxy has no server available!
<129>Jul 26 03:06:04 node-5 haproxy[892]: 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 26 03:06:04 node-5 haproxy[892]: proxy odl-jetty has no server available!
<129>Jul 26 03:06:06 node-5 haproxy[2133]: Server horizon/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 26 03:06:06 node-5 haproxy[2133]: Server keystone-1/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 26 03:06:06 node-5 haproxy[2133]: Server keystone-2/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 26 03:06:06 node-5 haproxy[2133]: 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 26 03:06:06 node-5 haproxy[2133]: 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 26 03:06:06 node-5 haproxy[2133]: 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 26 03:06:07 node-5 haproxy[2137]: 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 26 03:06:07 node-5 haproxy[2137]: 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 26 03:06:07 node-5 haproxy[2137]: 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 26 03:06:07 node-5 haproxy[2137]: 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 26 03:06:07 node-5 haproxy[2137]: 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 26 03:06:07 node-5 haproxy[2137]: 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 26 03:06:07 node-5 haproxy[2137]: 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 26 03:06:07 node-5 haproxy[2137]: 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 26 03:06:07 node-5 haproxy[2137]: 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 26 03:06:08 node-5 haproxy[2137]: 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 26 03:06:08 node-5 haproxy[2137]: 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 26 03:06:08 node-5 haproxy[2137]: 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 26 03:06:08 node-5 haproxy[2137]: Server horizon/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 26 03:06:08 node-5 haproxy[2137]: Server horizon/node-4 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 26 03:06:08 node-5 haproxy[2137]: proxy horizon has no server available!
<27>Jul 26 03:06:09 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:09 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:09 node-5 multipathd: uevent trigger error
<129>Jul 26 03:06:09 node-5 haproxy[2137]: 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.
<27>Jul 26 03:06:09 node-5 multipathd: uevent trigger error
<129>Jul 26 03:06:09 node-5 haproxy[2137]: Server glance-registry/node-4 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 26 03:06:09 node-5 haproxy[2137]: proxy glance-registry has no server available!
<129>Jul 26 03:06:09 node-5 haproxy[2137]: 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 26 03:06:09 node-5 haproxy[2137]: Server aodh/node-4 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 26 03:06:09 node-5 haproxy[2137]: proxy aodh has no server available!
<129>Jul 26 03:06:09 node-5 haproxy[2137]: 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 26 03:06:09 node-5 haproxy[2137]: Server ceilometer/node-4 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 26 03:06:09 node-5 haproxy[2137]: proxy ceilometer has no server available!
<129>Jul 26 03:06:10 node-5 haproxy[2137]: 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 26 03:06:10 node-5 haproxy[2137]: Server nova-novncproxy/node-4 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 26 03:06:10 node-5 haproxy[2137]: proxy nova-novncproxy has no server available!
<129>Jul 26 03:06:10 node-5 haproxy[2137]: 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 26 03:06:10 node-5 haproxy[2137]: proxy odl-jetty has no server available!
<27>Jul 26 03:06:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:12 node-5 multipathd: uevent trigger error
<129>Jul 26 03:06:16 node-5 haproxy[2137]: 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 26 03:06:16 node-5 haproxy[2137]: proxy odl-neutron-endpoint has no server available!
<129>Jul 26 03:06:16 node-5 haproxy[2137]: Server keystone-1/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 26 03:06:16 node-5 haproxy[2137]: Server keystone-1/node-4 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 26 03:06:16 node-5 haproxy[2137]: proxy keystone-1 has no server available!
<129>Jul 26 03:06:16 node-5 haproxy[2137]: 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 26 03:06:16 node-5 haproxy[2137]: Server keystone-2/node-4 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 26 03:06:16 node-5 haproxy[2137]: proxy keystone-2 has no server available!
<129>Jul 26 03:06:16 node-5 haproxy[2137]: 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 26 03:06:16 node-5 haproxy[2137]: Server nova-api/node-4 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 26 03:06:16 node-5 haproxy[2137]: proxy nova-api has no server available!
<129>Jul 26 03:06:16 node-5 haproxy[2137]: Server nova-metadata-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 26 03:06:16 node-5 haproxy[2137]: Server nova-metadata-api/node-4 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 26 03:06:16 node-5 haproxy[2137]: proxy nova-metadata-api has no server available!
<129>Jul 26 03:06:16 node-5 haproxy[2137]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:16 node-5 haproxy[2137]: Backup Server cinder-api/node-4 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 26 03:06:16 node-5 haproxy[2137]: proxy cinder-api has no server available!
<129>Jul 26 03:06:16 node-5 haproxy[2137]: Server glance-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 26 03:06:17 node-5 haproxy[2137]: Server glance-api/node-4 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 26 03:06:17 node-5 haproxy[2137]: proxy glance-api has no server available!
<129>Jul 26 03:06:17 node-5 haproxy[2137]: 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 26 03:06:17 node-5 haproxy[2137]: Server glance-glare/node-4 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 26 03:06:17 node-5 haproxy[2137]: proxy glance-glare has no server available!
<129>Jul 26 03:06:17 node-5 haproxy[2137]: 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 26 03:06:17 node-5 haproxy[2137]: Server neutron/node-4 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 26 03:06:17 node-5 haproxy[2137]: proxy neutron has no server available!
<129>Jul 26 03:06:17 node-5 haproxy[2137]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 26 03:06:17 node-5 haproxy[2137]: Backup Server mysqld/node-4 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 26 03:06:17 node-5 haproxy[2137]: proxy mysqld has no server available!
<129>Jul 26 03:06:17 node-5 haproxy[2137]: 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 26 03:06:17 node-5 haproxy[2137]: Server object-storage/node-4 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 26 03:06:17 node-5 haproxy[2137]: proxy object-storage has no server available!
<129>Jul 26 03:06:17 node-5 haproxy[2137]: 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 26 03:06:17 node-5 haproxy[2137]: Server heat-api/node-4 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 26 03:06:17 node-5 haproxy[2137]: proxy heat-api has no server available!
<129>Jul 26 03:06:17 node-5 haproxy[2137]: 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 26 03:06:17 node-5 haproxy[2137]: Server heat-api-cfn/node-4 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 26 03:06:17 node-5 haproxy[2137]: proxy heat-api-cfn has no server available!
<129>Jul 26 03:06:18 node-5 haproxy[2137]: 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 26 03:06:18 node-5 haproxy[2137]: Server heat-api-cloudwatch/node-4 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 26 03:06:18 node-5 haproxy[2137]: proxy heat-api-cloudwatch has no server available!
<43>Jul 26 03:06:30 node-5 apache2_error [Tue Jul 26 03:06:26.441248 2016] [mpm_event:notice] [pid 5666:tid 140668164839296] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 03:06:30 node-5 apache2_error [Tue Jul 26 03:06:26.441457 2016] [core:notice] [pid 5666:tid 140668164839296] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 26 03:06:30 node-5 apache2_error [Tue Jul 26 03:06:29.742373 2016] [mpm_event:notice] [pid 5666:tid 140668164839296] AH00491: caught SIGTERM, shutting down
<27>Jul 26 03:06:35 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:35 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:35 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:35 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:35 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:38 node-5 multipathd: uevent trigger error
<27>Jul 26 03:06:38 node-5 multipathd: uevent trigger error
<43>Jul 26 03:06:40 node-5 apache2_error [Tue Jul 26 03:06:30.833487 2016] [mpm_worker:notice] [pid 6031:tid 140398092040064] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 03:06:40 node-5 apache2_error [Tue Jul 26 03:06:30.833543 2016] [core:notice] [pid 6031:tid 140398092040064] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:06:52 node-5 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 26 03:07:08 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 26 03:07:15 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:15 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:15 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:15 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:15 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:15 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:15 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:19 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:19 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:19 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:19 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:19 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:19 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:19 node-5 multipathd: uevent trigger error
<27>Jul 26 03:07:19 node-5 multipathd: uevent trigger error
<43>Jul 26 03:07:20 node-5 apache2_error [Tue Jul 26 03:07:11.801184 2016] [mpm_worker:notice] [pid 6031:tid 140398092040064] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 03:07:20 node-5 apache2_error [Tue Jul 26 03:07:11.808816 2016] [mpm_worker:warn] [pid 6031:tid 140398092040064] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 03:07:20 node-5 apache2_error [Tue Jul 26 03:07:11.809570 2016] [mpm_worker:notice] [pid 6031:tid 140398092040064] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 26 03:07:20 node-5 apache2_error [Tue Jul 26 03:07:11.809583 2016] [core:notice] [pid 6031:tid 140398092040064] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:07:40 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:02 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 26 03:08:02 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 26 03:08:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:06 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:06 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:06 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:06 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:27 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:27 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:27 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:27 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:27 node-5 multipathd: uevent trigger error
<27>Jul 26 03:08:41 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 26 03:09:39 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 26 03:09:41 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 26 03:10:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:10:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:10:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:10:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:14:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:14:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:14:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:14:02 node-5 multipathd: uevent trigger error
<27>Jul 26 03:14:02 node-5 multipathd: uevent trigger error
<43>Jul 26 03:15:21 node-5 apache2_error [Tue Jul 26 03:15:19.129239 2016] [mpm_worker:notice] [pid 6031:tid 140398092040064] AH00295: caught SIGTERM, shutting down
<43>Jul 26 03:15:21 node-5 apache2_error [Tue Jul 26 03:15:19.882421 2016] [mpm_worker:notice] [pid 15258:tid 140307290892160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 03:15:21 node-5 apache2_error [Tue Jul 26 03:15:19.882463 2016] [core:notice] [pid 15258:tid 140307290892160] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:15:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:15:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:15:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:15:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:15:57 node-5 multipathd: uevent trigger error
<43>Jul 26 03:16:01 node-5 apache2_error [Tue Jul 26 03:15:51.857714 2016] [mpm_worker:notice] [pid 15258:tid 140307290892160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 03:16:01 node-5 apache2_error [Tue Jul 26 03:15:51.872290 2016] [mpm_worker:warn] [pid 15258:tid 140307290892160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 03:16:01 node-5 apache2_error [Tue Jul 26 03:15:51.878258 2016] [mpm_worker:notice] [pid 15258:tid 140307290892160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 03:16:01 node-5 apache2_error [Tue Jul 26 03:15:51.878287 2016] [core:notice] [pid 15258:tid 140307290892160] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:16:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:16:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:16:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:16:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:16:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:16:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:18:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:21:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:21:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:21:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:21:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:21:57 node-5 multipathd: uevent trigger error
<27>Jul 26 03:24:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:24:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:24:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:24:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:24:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:24:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:24:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:13 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:49 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:49 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:49 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:49 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:49 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:49 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:49 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:25:59 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:10 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:10 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:10 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:10 node-5 multipathd: uevent trigger error
<27>Jul 26 03:26:10 node-5 multipathd: uevent trigger error
<43>Jul 26 03:27:02 node-5 apache2_error [Tue Jul 26 03:26:55.973350 2016] [mpm_worker:notice] [pid 15258:tid 140307290892160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 03:27:02 node-5 apache2_error [Tue Jul 26 03:26:56.354958 2016] [mpm_worker:warn] [pid 15258:tid 140307290892160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 03:27:02 node-5 apache2_error [Tue Jul 26 03:26:56.358915 2016] [mpm_worker:notice] [pid 15258:tid 140307290892160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 03:27:02 node-5 apache2_error [Tue Jul 26 03:26:56.358932 2016] [core:notice] [pid 15258:tid 140307290892160] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:27:37 node-5 multipathd: uevent trigger error
<27>Jul 26 03:27:37 node-5 multipathd: uevent trigger error
<27>Jul 26 03:27:37 node-5 multipathd: uevent trigger error
<27>Jul 26 03:27:37 node-5 multipathd: uevent trigger error
<27>Jul 26 03:27:37 node-5 multipathd: uevent trigger error
<27>Jul 26 03:27:37 node-5 multipathd: uevent trigger error
<43>Jul 26 03:27:42 node-5 apache2_error [Tue Jul 26 03:27:33.288143 2016] [mpm_worker:notice] [pid 15258:tid 140307290892160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 26 03:27:42 node-5 apache2_error [Tue Jul 26 03:27:33.674087 2016] [mpm_worker:warn] [pid 15258:tid 140307290892160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 26 03:27:42 node-5 apache2_error [Tue Jul 26 03:27:33.683060 2016] [mpm_worker:notice] [pid 15258:tid 140307290892160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 26 03:27:42 node-5 apache2_error [Tue Jul 26 03:27:33.683086 2016] [core:notice] [pid 15258:tid 140307290892160] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 26 03:28:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:28:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:28:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:28:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:28:12 node-5 multipathd: uevent trigger error
<27>Jul 26 03:28:16 node-5 multipathd: uevent trigger error
<27>Jul 26 03:28:16 node-5 multipathd: uevent trigger error
<27>Jul 26 03:28:16 node-5 multipathd: uevent trigger error
<27>Jul 26 03:28:16 node-5 multipathd: uevent trigger error
<27>Jul 26 03:28:16 node-5 multipathd: uevent trigger error
<27>Jul 26 03:29:50 node-5 multipathd: uevent trigger error
<27>Jul 26 03:29:50 node-5 multipathd: uevent trigger error
<27>Jul 26 03:29:50 node-5 multipathd: uevent trigger error
<27>Jul 26 03:29:50 node-5 multipathd: uevent trigger error
<27>Jul 26 03:29:50 node-5 multipathd: uevent trigger error
<27>Jul 26 03:30:39 node-5 multipathd: uevent trigger error
<27>Jul 26 03:30:39 node-5 multipathd: uevent trigger error
<27>Jul 26 03:30:39 node-5 multipathd: uevent trigger error
<27>Jul 26 03:30:39 node-5 multipathd: uevent trigger error
<27>Jul 26 03:30:39 node-5 multipathd: uevent trigger error
<27>Jul 26 03:30:55 node-5 multipathd: uevent trigger error
<27>Jul 26 03:30:55 node-5 multipathd: uevent trigger error
<27>Jul 26 03:30:55 node-5 multipathd: uevent trigger error
<27>Jul 26 03:30:55 node-5 multipathd: uevent trigger error
<27>Jul 26 03:30:55 node-5 multipathd: uevent trigger error
<11>Jul 26 03:31:04 node-5 liberasurecode[30683]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:04 node-5 liberasurecode[30683]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:04 node-5 liberasurecode[30683]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:04 node-5 liberasurecode[30683]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:04 node-5 liberasurecode[30707]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:04 node-5 liberasurecode[30707]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:04 node-5 liberasurecode[30707]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:04 node-5 liberasurecode[30707]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:07 node-5 liberasurecode[31103]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:07 node-5 liberasurecode[31103]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:07 node-5 liberasurecode[31103]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:07 node-5 liberasurecode[31103]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31667]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31667]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31667]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31667]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31703]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31703]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31703]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31703]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31744]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31744]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31744]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31744]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31806]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31806]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31806]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31806]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31818]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31818]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31818]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31818]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31830]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31830]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31830]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31830]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31842]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31842]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31842]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:31:12 node-5 liberasurecode[31842]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 26 03:31:18 node-5 multipathd: uevent trigger error
<27>Jul 26 03:31:18 node-5 multipathd: uevent trigger error
<27>Jul 26 03:31:18 node-5 multipathd: uevent trigger error
<27>Jul 26 03:31:18 node-5 multipathd: uevent trigger error
<27>Jul 26 03:31:18 node-5 multipathd: uevent trigger error
<27>Jul 26 03:31:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:31:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:31:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:31:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:31:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:32:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:32:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:32:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:32:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:32:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:32:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:32:31 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:28 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:28 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:28 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:28 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:28 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:34 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:34 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:34 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:34 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:34 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:47 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:47 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:47 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:47 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:47 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:52 node-5 multipathd: uevent trigger error
<27>Jul 26 03:34:52 node-5 multipathd: uevent trigger error
<11>Jul 26 03:35:01 node-5 liberasurecode[5650]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:35:01 node-5 liberasurecode[5650]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:35:01 node-5 liberasurecode[5650]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 26 03:35:01 node-5 liberasurecode[5650]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 26 03:35:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:05 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:18 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:18 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:18 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:18 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:18 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:23 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:27 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:27 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:27 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:27 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:27 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:32 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:36 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:36 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:36 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:36 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:36 node-5 multipathd: uevent trigger error
<27>Jul 26 03:35:36 node-5 multipathd: uevent trigger error
<27>Jul 26 03:36:09 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 26 03:36:09 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
