Jul 24 12:30:45 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8375" x-info="http://www.rsyslog.com"] start
Jul 24 12:30:45 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 24 12:30:45 node-5 rsyslogd: rsyslogd's groupid changed to 104
Jul 24 12:30:45 node-5 rsyslogd: rsyslogd's userid changed to 101
Jul 24 12:30:45 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 24 12:30:45 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 24 12:30:45 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 24 12:30:45 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 24 12:30:45 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=f4aec397-b60b-4655-acae-f351d2ea28bc nomdmonddf nomdmonisw
Jul 24 12:30:45 node-5 kernel: [    0.000000] KERNEL supported cpus:
Jul 24 12:30:45 node-5 kernel: [    0.000000]   Intel GenuineIntel
Jul 24 12:30:45 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Jul 24 12:30:45 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Jul 24 12:30:45 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 24 12:30:45 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 24 12:30:45 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 24 12:30:45 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 24 12:30:45 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 24 12:30:45 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 24 12:30:45 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 24 12:30:45 node-5 kernel: [    0.000000] No AGP bridge found
Jul 24 12:30:45 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 24 12:30:45 node-5 kernel: [    0.000000] MTRR default type: write-back
Jul 24 12:30:45 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 24 12:30:45 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Jul 24 12:30:45 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 24 12:30:45 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 24 12:30:45 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 24 12:30:45 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 24 12:30:45 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 24 12:30:45 node-5 kernel: [    0.000000]   2 disabled
Jul 24 12:30:45 node-5 kernel: [    0.000000]   3 disabled
Jul 24 12:30:45 node-5 kernel: [    0.000000]   4 disabled
Jul 24 12:30:45 node-5 kernel: [    0.000000]   5 disabled
Jul 24 12:30:45 node-5 kernel: [    0.000000]   6 disabled
Jul 24 12:30:45 node-5 kernel: [    0.000000]   7 disabled
Jul 24 12:30:45 node-5 kernel: [    0.000000]   8 disabled
Jul 24 12:30:45 node-5 kernel: [    0.000000]   9 disabled
Jul 24 12:30:45 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 24 12:30:45 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 24 12:30:45 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 24 12:30:45 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 24 12:30:45 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 24 12:30:45 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Jul 24 12:30:45 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 24 12:30:45 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 24 12:30:45 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 24 12:30:45 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 24 12:30:45 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 24 12:30:45 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 24 12:30:45 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 24 12:30:45 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 24 12:30:45 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 24 12:30:45 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 24 12:30:45 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 24 12:30:45 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 24 12:30:45 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 24 12:30:45 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 24 12:30:45 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 24 12:30:45 node-5 kernel: [    0.000000] Zone ranges:
Jul 24 12:30:45 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] Movable zone start for each node
Jul 24 12:30:45 node-5 kernel: [    0.000000] Early memory node ranges
Jul 24 12:30:45 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 24 12:30:45 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 24 12:30:45 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 24 12:30:45 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 24 12:30:45 node-5 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 24 12:30:45 node-5 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 24 12:30:45 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 24 12:30:45 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 24 12:30:45 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 24 12:30:45 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 24 12:30:45 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 24 12:30:45 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 24 12:30:45 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 24 12:30:45 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 24 12:30:45 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 24 12:30:45 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 24 12:30:45 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 24 12:30:45 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 24 12:30:45 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 24 12:30:45 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 24 12:30:45 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 24 12:30:45 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 24 12:30:45 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 24 12:30:45 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 24 12:30:45 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 24 12:30:45 node-5 kernel: [    0.000000] Policy zone: Normal
Jul 24 12:30:45 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=f4aec397-b60b-4655-acae-f351d2ea28bc nomdmonddf nomdmonisw
Jul 24 12:30:45 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 24 12:30:45 node-5 kernel: [    0.000000] Checking aperture...
Jul 24 12:30:45 node-5 kernel: [    0.000000] No AGP bridge found
Jul 24 12:30:45 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 24 12:30:45 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 24 12:30:45 node-5 kernel: [    0.000000] Memory: 32653460K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 24 12:30:45 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 24 12:30:45 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 24 12:30:45 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 24 12:30:45 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 24 12:30:45 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 24 12:30:45 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 24 12:30:45 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 24 12:30:45 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 24 12:30:45 node-5 kernel: [    0.000000] console [tty0] enabled
Jul 24 12:30:45 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 24 12:30:45 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 24 12:30:45 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 24 12:30:45 node-5 kernel: [    0.000000] hpet clockevent registered
Jul 24 12:30:45 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 24 12:30:45 node-5 kernel: [    0.004000] tsc: Detected 3492.001 MHz processor
Jul 24 12:30:45 node-5 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.00 BogoMIPS (lpj=13968004)
Jul 24 12:30:45 node-5 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 24 12:30:45 node-5 kernel: [    0.000047] Security Framework initialized
Jul 24 12:30:45 node-5 kernel: [    0.000065] AppArmor: AppArmor initialized
Jul 24 12:30:45 node-5 kernel: [    0.000066] Yama: becoming mindful.
Jul 24 12:30:45 node-5 kernel: [    0.001450] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.006379] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.008311] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.008339] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.008630] Initializing cgroup subsys memory
Jul 24 12:30:45 node-5 kernel: [    0.008638] Initializing cgroup subsys devices
Jul 24 12:30:45 node-5 kernel: [    0.008640] Initializing cgroup subsys freezer
Jul 24 12:30:45 node-5 kernel: [    0.008642] Initializing cgroup subsys blkio
Jul 24 12:30:45 node-5 kernel: [    0.008643] Initializing cgroup subsys perf_event
Jul 24 12:30:45 node-5 kernel: [    0.008645] Initializing cgroup subsys hugetlb
Jul 24 12:30:45 node-5 kernel: [    0.008665] CPU: Physical Processor ID: 0
Jul 24 12:30:45 node-5 kernel: [    0.008666] CPU: Processor Core ID: 0
Jul 24 12:30:45 node-5 kernel: [    0.008669] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 24 12:30:45 node-5 kernel: [    0.008669] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 24 12:30:45 node-5 kernel: [    0.009363] mce: CPU supports 22 MCE banks
Jul 24 12:30:45 node-5 kernel: [    0.009391] CPU0: Thermal monitoring enabled (TM1)
Jul 24 12:30:45 node-5 kernel: [    0.009411] process: using mwait in idle threads
Jul 24 12:30:45 node-5 kernel: [    0.009414] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 24 12:30:45 node-5 kernel: [    0.009414] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 24 12:30:45 node-5 kernel: [    0.009414] tlb_flushall_shift: 6
Jul 24 12:30:45 node-5 kernel: [    0.009504] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 24 12:30:45 node-5 kernel: [    0.010229] ACPI: Core revision 20131115
Jul 24 12:30:45 node-5 kernel: [    0.022905] ACPI: All ACPI Tables successfully acquired
Jul 24 12:30:45 node-5 kernel: [    0.023065] ftrace: allocating 28617 entries in 112 pages
Jul 24 12:30:45 node-5 kernel: [    0.031890] dmar: Host address width 46
Jul 24 12:30:45 node-5 kernel: [    0.031892] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 24 12:30:45 node-5 kernel: [    0.031898] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 12:30:45 node-5 kernel: [    0.031900] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 24 12:30:45 node-5 kernel: [    0.031903] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 12:30:45 node-5 kernel: [    0.031905] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 24 12:30:45 node-5 kernel: [    0.031906] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 24 12:30:45 node-5 kernel: [    0.031907] dmar: ATSR flags: 0x0
Jul 24 12:30:45 node-5 kernel: [    0.031908] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 24 12:30:45 node-5 kernel: [    0.031910] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 24 12:30:45 node-5 kernel: [    0.032025] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 24 12:30:45 node-5 kernel: [    0.032026] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 12:30:45 node-5 kernel: [    0.032027] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 12:30:45 node-5 kernel: [    0.032028] HPET id 0 under DRHD base 0xc7ffc000
Jul 24 12:30:45 node-5 kernel: [    0.032029] Your BIOS is broken and requested that x2apic be disabled.
Jul 24 12:30:45 node-5 kernel: [    0.032029] This will slightly decrease performance.
Jul 24 12:30:45 node-5 kernel: [    0.032029] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 24 12:30:45 node-5 kernel: [    0.032461] Enabled IRQ remapping in xapic mode
Jul 24 12:30:45 node-5 kernel: [    0.032462] x2apic not enabled, IRQ remapping is in xapic mode
Jul 24 12:30:45 node-5 kernel: [    0.032466] Switched APIC routing to physical flat.
Jul 24 12:30:45 node-5 kernel: [    0.033088] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 24 12:30:45 node-5 kernel: [    0.072739] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 24 12:30:45 node-5 kernel: [    0.072744] TSC deadline timer enabled
Jul 24 12:30:45 node-5 kernel: [    0.072752] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 24 12:30:45 node-5 kernel: [    0.072758] ... version:                3
Jul 24 12:30:45 node-5 kernel: [    0.072759] ... bit width:              48
Jul 24 12:30:45 node-5 kernel: [    0.072760] ... generic registers:      4
Jul 24 12:30:45 node-5 kernel: [    0.072761] ... value mask:             0000ffffffffffff
Jul 24 12:30:45 node-5 kernel: [    0.072762] ... max period:             0000ffffffffffff
Jul 24 12:30:45 node-5 kernel: [    0.072763] ... fixed-purpose events:   3
Jul 24 12:30:45 node-5 kernel: [    0.072764] ... event mask:             000000070000000f
Jul 24 12:30:45 node-5 kernel: [    0.074216] x86: Booting SMP configuration:
Jul 24 12:30:45 node-5 kernel: [    0.088420] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 24 12:30:45 node-5 kernel: [    0.074218] .... node  #0, CPUs:        #1  #2  #3
Jul 24 12:30:45 node-5 kernel: [    0.116329] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 24 12:30:45 node-5 kernel: [    0.270480] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 24 12:30:45 node-5 kernel: [    0.326096] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 24 12:30:45 node-5 kernel: [    0.383156] x86: Booted up 2 nodes, 16 CPUs
Jul 24 12:30:45 node-5 kernel: [    0.383160] smpboot: Total of 16 processors activated (111756.92 BogoMIPS)
Jul 24 12:30:45 node-5 kernel: [    0.407769] devtmpfs: initialized
Jul 24 12:30:45 node-5 kernel: [    0.410884] EVM: security.selinux
Jul 24 12:30:45 node-5 kernel: [    0.410886] EVM: security.SMACK64
Jul 24 12:30:45 node-5 kernel: [    0.410887] EVM: security.ima
Jul 24 12:30:45 node-5 kernel: [    0.410888] EVM: security.capability
Jul 24 12:30:45 node-5 kernel: [    0.410937] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.411631] pinctrl core: initialized pinctrl subsystem
Jul 24 12:30:45 node-5 kernel: [    0.411692] regulator-dummy: no parameters
Jul 24 12:30:45 node-5 kernel: [    0.411724] RTC time: 12:30:09, date: 07/24/16
Jul 24 12:30:45 node-5 kernel: [    0.411758] NET: Registered protocol family 16
Jul 24 12:30:45 node-5 kernel: [    0.411843] cpuidle: using governor ladder
Jul 24 12:30:45 node-5 kernel: [    0.411845] cpuidle: using governor menu
Jul 24 12:30:45 node-5 kernel: [    0.411878] ACPI: bus type PCI registered
Jul 24 12:30:45 node-5 kernel: [    0.411880] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 24 12:30:45 node-5 kernel: [    0.411925] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 24 12:30:45 node-5 kernel: [    0.411928] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 24 12:30:45 node-5 kernel: [    0.425662] PCI: Using configuration type 1 for base access
Jul 24 12:30:45 node-5 kernel: [    0.426665] bio: create slab <bio-0> at 0
Jul 24 12:30:45 node-5 kernel: [    0.426943] ACPI: Added _OSI(Module Device)
Jul 24 12:30:45 node-5 kernel: [    0.426944] ACPI: Added _OSI(Processor Device)
Jul 24 12:30:45 node-5 kernel: [    0.426946] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 24 12:30:45 node-5 kernel: [    0.426947] ACPI: Added _OSI(Processor Aggregator Device)
Jul 24 12:30:45 node-5 kernel: [    0.439596] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 24 12:30:45 node-5 kernel: [    0.450060] ACPI: Interpreter enabled
Jul 24 12:30:45 node-5 kernel: [    0.450066] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 24 12:30:45 node-5 kernel: [    0.450070] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 24 12:30:45 node-5 kernel: [    0.450073] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 24 12:30:45 node-5 kernel: [    0.450079] ACPI: (supports S0 S4 S5)
Jul 24 12:30:45 node-5 kernel: [    0.450081] ACPI: Using IOAPIC for interrupt routing
Jul 24 12:30:45 node-5 kernel: [    0.450123] HEST: Table parsing has been initialized.
Jul 24 12:30:45 node-5 kernel: [    0.450126] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 24 12:30:45 node-5 kernel: [    0.450676] ACPI: No dock devices found.
Jul 24 12:30:45 node-5 kernel: [    0.462201] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 24 12:30:45 node-5 kernel: [    0.462206] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 12:30:45 node-5 kernel: [    0.462210] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 12:30:45 node-5 kernel: [    0.462239] PCI host bridge to bus 0000:ff
Jul 24 12:30:45 node-5 kernel: [    0.462241] pci_bus 0000:ff: root bus resource [bus ff]
Jul 24 12:30:45 node-5 kernel: [    0.462249] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462290] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.462320] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462356] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462386] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.462415] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.462447] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462477] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462508] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462536] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462563] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462589] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462618] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462644] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462671] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462698] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462726] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462754] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462781] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.462809] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462835] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.462861] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462888] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462918] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.462954] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.462986] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463016] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463047] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463079] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463110] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463141] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463173] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463204] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463236] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463270] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463304] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463338] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463368] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463396] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463429] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463464] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463502] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463536] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463569] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463600] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463631] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463661] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463690] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463720] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463751] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463782] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463811] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463838] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463867] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463896] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463927] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.463958] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464014] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 24 12:30:45 node-5 kernel: [    0.464017] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 12:30:45 node-5 kernel: [    0.464020] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 12:30:45 node-5 kernel: [    0.464037] PCI host bridge to bus 0000:7f
Jul 24 12:30:45 node-5 kernel: [    0.464039] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 24 12:30:45 node-5 kernel: [    0.464044] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464071] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.464099] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464128] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464150] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.464174] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.464201] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464225] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464247] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464269] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464291] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464313] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464336] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464358] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464387] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464416] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464437] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464462] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464486] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.464510] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464533] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.464557] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464582] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464611] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 12:30:45 node-5 kernel: [    0.464644] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464670] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464696] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464722] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464747] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464774] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464802] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464830] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464855] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464882] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464910] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464937] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464965] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.464991] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465017] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465047] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465072] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465100] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465129] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465157] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465185] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465210] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465235] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465261] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465287] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465314] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465343] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465366] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465388] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465413] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465438] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465466] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.465492] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.466732] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 24 12:30:45 node-5 kernel: [    0.466735] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 12:30:45 node-5 kernel: [    0.467864] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 12:30:45 node-5 kernel: [    0.468371] PCI host bridge to bus 0000:00
Jul 24 12:30:45 node-5 kernel: [    0.468374] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 24 12:30:45 node-5 kernel: [    0.468378] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 24 12:30:45 node-5 kernel: [    0.468380] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 24 12:30:45 node-5 kernel: [    0.468381] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 24 12:30:45 node-5 kernel: [    0.468382] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 24 12:30:45 node-5 kernel: [    0.468384] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 24 12:30:45 node-5 kernel: [    0.468385] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 24 12:30:45 node-5 kernel: [    0.468391] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 24 12:30:45 node-5 kernel: [    0.468475] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.468506] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.468547] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 24 12:30:45 node-5 kernel: [    0.468567] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.468596] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.468636] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 24 12:30:45 node-5 kernel: [    0.468655] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.468684] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.468724] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 24 12:30:45 node-5 kernel: [    0.468741] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.468812] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.468891] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.468969] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 12:30:45 node-5 kernel: [    0.468974] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 24 12:30:45 node-5 kernel: [    0.469059] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 24 12:30:45 node-5 kernel: [    0.469207] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 24 12:30:45 node-5 kernel: [    0.469225] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 24 12:30:45 node-5 kernel: [    0.469302] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.469356] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 24 12:30:45 node-5 kernel: [    0.469378] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.469434] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.469477] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 24 12:30:45 node-5 kernel: [    0.469506] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.469562] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.469604] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 24 12:30:45 node-5 kernel: [    0.469632] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 24 12:30:45 node-5 kernel: [    0.469649] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 24 12:30:45 node-5 kernel: [    0.469727] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.469776] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 24 12:30:45 node-5 kernel: [    0.469803] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 24 12:30:45 node-5 kernel: [    0.470051] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 24 12:30:45 node-5 kernel: [    0.470057] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 24 12:30:45 node-5 kernel: [    0.470063] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.470069] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.470076] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 24 12:30:45 node-5 kernel: [    0.470106] pci 0000:01:00.0: supports D1 D2
Jul 24 12:30:45 node-5 kernel: [    0.476394] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 12:30:45 node-5 kernel: [    0.476400] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 12:30:45 node-5 kernel: [    0.476404] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 12:30:45 node-5 kernel: [    0.476666] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.476725] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 24 12:30:45 node-5 kernel: [    0.484390] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 12:30:45 node-5 kernel: [    0.484397] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.484401] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 12:30:45 node-5 kernel: [    0.484493] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.484561] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.484637] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.484686] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 12:30:45 node-5 kernel: [    0.484690] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.484691] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 12:30:45 node-5 kernel: [    0.484749] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.484872] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.484926] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 12:30:45 node-5 kernel: [    0.484928] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.484930] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 12:30:45 node-5 kernel: [    0.484979] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.485098] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.485138] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.485260] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.485296] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.485415] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.485450] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 24 12:30:45 node-5 kernel: [    0.485569] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 24 12:30:45 node-5 kernel: [    0.485610] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 12:30:45 node-5 kernel: [    0.485613] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.485615] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 12:30:45 node-5 kernel: [    0.485673] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 24 12:30:45 node-5 kernel: [    0.485749] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.485800] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.485841] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 24 12:30:45 node-5 kernel: [    0.485920] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 24 12:30:45 node-5 kernel: [    0.486027] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 12:30:45 node-5 kernel: [    0.486030] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.486032] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 12:30:45 node-5 kernel: [    0.486088] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 24 12:30:45 node-5 kernel: [    0.486145] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.486193] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.486406] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 12:30:45 node-5 kernel: [    0.486410] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 12:30:45 node-5 kernel: [    0.486471] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 24 12:30:45 node-5 kernel: [    0.486524] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.486572] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.486809] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 12:30:45 node-5 kernel: [    0.486813] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 12:30:45 node-5 kernel: [    0.486872] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 24 12:30:45 node-5 kernel: [    0.486934] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.486986] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 24 12:30:45 node-5 kernel: [    0.487205] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 12:30:45 node-5 kernel: [    0.487209] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 12:30:45 node-5 kernel: [    0.487383] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 12:30:45 node-5 kernel: [    0.487421] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 12:30:45 node-5 kernel: [    0.487500] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 24 12:30:45 node-5 kernel: [    0.487518] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 24 12:30:45 node-5 kernel: [    0.487532] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 24 12:30:45 node-5 kernel: [    0.487545] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 24 12:30:45 node-5 kernel: [    0.487595] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 24 12:30:45 node-5 kernel: [    0.492397] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 12:30:45 node-5 kernel: [    0.492406] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 12:30:45 node-5 kernel: [    0.492458] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 24 12:30:45 node-5 kernel: [    0.493121] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 24 12:30:45 node-5 kernel: [    0.493124] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 12:30:45 node-5 kernel: [    0.493244] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 12:30:45 node-5 kernel: [    0.493352] PCI host bridge to bus 0000:80
Jul 24 12:30:45 node-5 kernel: [    0.493354] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 24 12:30:45 node-5 kernel: [    0.493355] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 24 12:30:45 node-5 kernel: [    0.493357] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 24 12:30:45 node-5 kernel: [    0.493365] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.493430] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.493499] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 12:30:45 node-5 kernel: [    0.493561] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 12:30:45 node-5 kernel: [    0.493566] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 24 12:30:45 node-5 kernel: [    0.493639] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 24 12:30:45 node-5 kernel: [    0.493935] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 24 12:30:45 node-5 kernel: [    0.493966] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 24 12:30:45 node-5 kernel: [    0.493996] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 24 12:30:45 node-5 kernel: [    0.494025] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 24 12:30:45 node-5 kernel: [    0.494054] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 12:30:45 node-5 kernel: [    0.494084] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 12:30:45 node-5 kernel: [    0.494113] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 12:30:45 node-5 kernel: [    0.494143] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 12:30:45 node-5 kernel: [    0.494228] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 24 12:30:45 node-5 kernel: [    0.494232] ACPI: \_SB_.UNC1: notify handler is installed
Jul 24 12:30:45 node-5 kernel: [    0.494233] ACPI: \_SB_.UNC0: notify handler is installed
Jul 24 12:30:45 node-5 kernel: [    0.494248] ACPI: \_SB_.PCI0: notify handler is installed
Jul 24 12:30:45 node-5 kernel: [    0.494301] ACPI: \_SB_.PCI1: notify handler is installed
Jul 24 12:30:45 node-5 kernel: [    0.494380] Found 4 acpi root devices
Jul 24 12:30:45 node-5 kernel: [    0.494489] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 24 12:30:45 node-5 kernel: [    0.494491] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 24 12:30:45 node-5 kernel: [    0.494493] vgaarb: loaded
Jul 24 12:30:45 node-5 kernel: [    0.494494] vgaarb: bridge control possible 0000:0c:00.0
Jul 24 12:30:45 node-5 kernel: [    0.494615] SCSI subsystem initialized
Jul 24 12:30:45 node-5 kernel: [    0.494679] libata version 3.00 loaded.
Jul 24 12:30:45 node-5 kernel: [    0.494694] ACPI: bus type USB registered
Jul 24 12:30:45 node-5 kernel: [    0.494705] usbcore: registered new interface driver usbfs
Jul 24 12:30:45 node-5 kernel: [    0.494710] usbcore: registered new interface driver hub
Jul 24 12:30:45 node-5 kernel: [    0.494733] usbcore: registered new device driver usb
Jul 24 12:30:45 node-5 kernel: [    0.494900] PCI: Using ACPI for IRQ routing
Jul 24 12:30:45 node-5 kernel: [    0.498508] PCI: pci_cache_line_size set to 64 bytes
Jul 24 12:30:45 node-5 kernel: [    0.498741] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 24 12:30:45 node-5 kernel: [    0.498742] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 24 12:30:45 node-5 kernel: [    0.498743] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 24 12:30:45 node-5 kernel: [    0.498809] NetLabel: Initializing
Jul 24 12:30:45 node-5 kernel: [    0.498811] NetLabel:  domain hash size = 128
Jul 24 12:30:45 node-5 kernel: [    0.498811] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 24 12:30:45 node-5 kernel: [    0.498821] NetLabel:  unlabeled traffic allowed by default
Jul 24 12:30:45 node-5 kernel: [    0.498889] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 24 12:30:45 node-5 kernel: [    0.498894] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 24 12:30:45 node-5 kernel: [    0.500962] Switched to clocksource hpet
Jul 24 12:30:45 node-5 kernel: [    0.505460] AppArmor: AppArmor Filesystem Enabled
Jul 24 12:30:45 node-5 kernel: [    0.505498] pnp: PnP ACPI init
Jul 24 12:30:45 node-5 kernel: [    0.505511] ACPI: bus type PNP registered
Jul 24 12:30:45 node-5 kernel: [    0.505688] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 24 12:30:45 node-5 kernel: [    0.505699] pnp 00:01: [dma 4]
Jul 24 12:30:45 node-5 kernel: [    0.505717] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 24 12:30:45 node-5 kernel: [    0.505752] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 24 12:30:45 node-5 kernel: [    0.505777] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 24 12:30:45 node-5 kernel: [    0.505798] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 24 12:30:45 node-5 kernel: [    0.505844] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 24 12:30:45 node-5 kernel: [    0.505956] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505959] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 24 12:30:45 node-5 kernel: [    0.505960] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505962] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505963] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505965] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505968] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 24 12:30:45 node-5 kernel: [    0.505970] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505971] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505973] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505974] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505976] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505977] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 24 12:30:45 node-5 kernel: [    0.505980] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 24 12:30:45 node-5 kernel: [    0.506081] pnp 00:07: [dma 0 disabled]
Jul 24 12:30:45 node-5 kernel: [    0.506114] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 12:30:45 node-5 kernel: [    0.506196] pnp 00:08: [dma 0 disabled]
Jul 24 12:30:45 node-5 kernel: [    0.506231] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 12:30:45 node-5 kernel: [    0.506290] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 24 12:30:45 node-5 kernel: [    0.506733] pnp: PnP ACPI: found 10 devices
Jul 24 12:30:45 node-5 kernel: [    0.506735] ACPI: bus type PNP unregistered
Jul 24 12:30:45 node-5 kernel: [    0.512741] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 12:30:45 node-5 kernel: [    0.512745] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 12:30:45 node-5 kernel: [    0.512748] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 12:30:45 node-5 kernel: [    0.512753] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 12:30:45 node-5 kernel: [    0.512755] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.512770] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 12:30:45 node-5 kernel: [    0.512799] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 12:30:45 node-5 kernel: [    0.512814] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 12:30:45 node-5 kernel: [    0.512843] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 12:30:45 node-5 kernel: [    0.512858] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 12:30:45 node-5 kernel: [    0.512887] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 12:30:45 node-5 kernel: [    0.512901] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 12:30:45 node-5 kernel: [    0.512930] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 12:30:45 node-5 kernel: [    0.512937] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.512952] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 12:30:45 node-5 kernel: [    0.512981] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 12:30:45 node-5 kernel: [    0.512983] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.512998] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 12:30:45 node-5 kernel: [    0.513030] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 12:30:45 node-5 kernel: [    0.513032] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.513035] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 12:30:45 node-5 kernel: [    0.513039] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 12:30:45 node-5 kernel: [    0.513041] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.513044] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 12:30:45 node-5 kernel: [    0.513048] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 12:30:45 node-5 kernel: [    0.513054] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 12:30:45 node-5 kernel: [    0.513063] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 12:30:45 node-5 kernel: [    0.513067] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 12:30:45 node-5 kernel: [    0.513074] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 24 12:30:45 node-5 kernel: [    0.513075] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 24 12:30:45 node-5 kernel: [    0.513076] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 24 12:30:45 node-5 kernel: [    0.513077] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 24 12:30:45 node-5 kernel: [    0.513078] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 24 12:30:45 node-5 kernel: [    0.513079] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 24 12:30:45 node-5 kernel: [    0.513080] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 24 12:30:45 node-5 kernel: [    0.513081] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 24 12:30:45 node-5 kernel: [    0.513082] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.513083] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 12:30:45 node-5 kernel: [    0.513084] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.513085] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 12:30:45 node-5 kernel: [    0.513086] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.513087] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 12:30:45 node-5 kernel: [    0.513088] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.513089] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 12:30:45 node-5 kernel: [    0.513090] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 24 12:30:45 node-5 kernel: [    0.513090] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 24 12:30:45 node-5 kernel: [    0.513092] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 24 12:30:45 node-5 kernel: [    0.513093] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 24 12:30:45 node-5 kernel: [    0.513094] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 24 12:30:45 node-5 kernel: [    0.513095] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 24 12:30:45 node-5 kernel: [    0.513098] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 24 12:30:45 node-5 kernel: [    0.513099] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 24 12:30:45 node-5 kernel: [    0.513141] NET: Registered protocol family 2
Jul 24 12:30:45 node-5 kernel: [    0.513439] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.513810] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.513977] TCP: Hash tables configured (established 262144 bind 65536)
Jul 24 12:30:45 node-5 kernel: [    0.514019] TCP: reno registered
Jul 24 12:30:45 node-5 kernel: [    0.514050] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.514157] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.514333] NET: Registered protocol family 1
Jul 24 12:30:45 node-5 kernel: [    0.553049] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 24 12:30:45 node-5 kernel: [    0.553063] PCI: CLS 64 bytes, default 64
Jul 24 12:30:45 node-5 kernel: [    0.553149] Trying to unpack rootfs image as initramfs...
Jul 24 12:30:45 node-5 kernel: [    0.774301] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 24 12:30:45 node-5 kernel: [    0.774345] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 24 12:30:45 node-5 kernel: [    0.774348] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 24 12:30:45 node-5 kernel: [    0.774755] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774763] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774771] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774777] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774785] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774793] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774800] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774804] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774810] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774818] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774827] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774833] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774840] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774846] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774852] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774858] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 12:30:45 node-5 kernel: [    0.774903] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 24 12:30:45 node-5 kernel: [    0.774905] Scanning for low memory corruption every 60 seconds
Jul 24 12:30:45 node-5 kernel: [    0.775207] Initialise system trusted keyring
Jul 24 12:30:45 node-5 kernel: [    0.775254] audit: initializing netlink socket (disabled)
Jul 24 12:30:45 node-5 kernel: [    0.775266] type=2000 audit(1469363409.728:1): initialized
Jul 24 12:30:45 node-5 kernel: [    0.793181] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 24 12:30:45 node-5 kernel: [    0.794638] zbud: loaded
Jul 24 12:30:45 node-5 kernel: [    0.794759] VFS: Disk quotas dquot_6.5.2
Jul 24 12:30:45 node-5 kernel: [    0.794800] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 24 12:30:45 node-5 kernel: [    0.795165] fuse init (API version 7.22)
Jul 24 12:30:45 node-5 kernel: [    0.795219] msgmni has been set to 32768
Jul 24 12:30:45 node-5 kernel: [    0.795264] Key type big_key registered
Jul 24 12:30:45 node-5 kernel: [    0.795820] Key type asymmetric registered
Jul 24 12:30:45 node-5 kernel: [    0.795822] Asymmetric key parser 'x509' registered
Jul 24 12:30:45 node-5 kernel: [    0.795844] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 24 12:30:45 node-5 kernel: [    0.795909] io scheduler noop registered
Jul 24 12:30:45 node-5 kernel: [    0.795911] io scheduler deadline registered (default)
Jul 24 12:30:45 node-5 kernel: [    0.795930] io scheduler cfq registered
Jul 24 12:30:45 node-5 kernel: [    0.796436] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    0.796646] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    0.796775] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    0.796890] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    0.797009] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    0.797103] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    0.797487] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 24 12:30:45 node-5 kernel: [    0.797512] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 24 12:30:45 node-5 kernel: [    0.797528] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 24 12:30:45 node-5 kernel: [    0.797540] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797543] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797545] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 24 12:30:45 node-5 kernel: [    0.797550] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797552] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797553] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797555] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797556] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797558] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797559] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797560] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797562] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797563] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797565] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797566] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797568] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 24 12:30:45 node-5 kernel: [    0.797579] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797581] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 24 12:30:45 node-5 kernel: [    0.797593] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797596] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 24 12:30:45 node-5 kernel: [    0.797607] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797609] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 24 12:30:45 node-5 kernel: [    0.797612] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 24 12:30:45 node-5 kernel: [    0.797638] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 24 12:30:45 node-5 kernel: [    0.797644] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 24 12:30:45 node-5 kernel: [    0.797648] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 24 12:30:45 node-5 kernel: [    0.797656] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 24 12:30:45 node-5 kernel: [    0.797691] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 24 12:30:45 node-5 kernel: [    0.797692] vesafb: scrolling: redraw
Jul 24 12:30:45 node-5 kernel: [    0.797694] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 24 12:30:45 node-5 kernel: [    0.818185] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 24 12:30:45 node-5 kernel: [    0.826684] Console: switching to colour frame buffer device 80x30
Jul 24 12:30:45 node-5 kernel: [    0.835349] fb0: VESA VGA frame buffer device
Jul 24 12:30:45 node-5 kernel: [    0.835547] intel_idle: MWAIT substates: 0x2120
Jul 24 12:30:45 node-5 kernel: [    0.835548] intel_idle: v0.4 model 0x3F
Jul 24 12:30:45 node-5 kernel: [    0.835549] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 24 12:30:45 node-5 kernel: [    0.835789] ipmi message handler version 39.2
Jul 24 12:30:45 node-5 kernel: [    0.836068] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 24 12:30:45 node-5 kernel: [    0.836501] ACPI: AC Adapter [P111] (on-line)
Jul 24 12:30:45 node-5 kernel: [    0.841740] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 24 12:30:45 node-5 kernel: [    0.852735] ACPI: Power Button [PWRB]
Jul 24 12:30:45 node-5 kernel: [    0.858542] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 24 12:30:45 node-5 kernel: [    0.870181] ACPI: Power Button [PWRF]
Jul 24 12:30:45 node-5 kernel: [    0.886505] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 24 12:30:45 node-5 kernel: [    0.898153] pstore: Registered erst as persistent store backend
Jul 24 12:30:45 node-5 kernel: [    0.904341] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 24 12:30:45 node-5 kernel: [    0.916303] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 24 12:30:45 node-5 kernel: [    0.943042] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 24 12:30:45 node-5 kernel: [    0.976335] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 24 12:30:45 node-5 kernel: [    0.990465] Linux agpgart interface v0.103
Jul 24 12:30:45 node-5 kernel: [    0.998162] brd: module loaded
Jul 24 12:30:45 node-5 kernel: [    1.005290] loop: module loaded
Jul 24 12:30:45 node-5 kernel: [    1.012100] libphy: Fixed MDIO Bus: probed
Jul 24 12:30:45 node-5 kernel: [    1.018587] tun: Universal TUN/TAP device driver, 1.6
Jul 24 12:30:45 node-5 kernel: [    1.025053] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 24 12:30:45 node-5 kernel: [    1.031578] PPP generic driver version 2.4.2
Jul 24 12:30:45 node-5 kernel: [    1.037972] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 24 12:30:45 node-5 kernel: [    1.044415] ehci-pci: EHCI PCI platform driver
Jul 24 12:30:45 node-5 kernel: [    1.050934] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 24 12:30:45 node-5 kernel: [    1.057343] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 24 12:30:45 node-5 kernel: [    1.069895] ehci-pci 0000:00:1a.0: debug port 2
Jul 24 12:30:45 node-5 kernel: [    1.080111] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 24 12:30:45 node-5 kernel: [    1.080129] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 24 12:30:45 node-5 kernel: [    1.096447] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 24 12:30:45 node-5 kernel: [    1.102522] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 12:30:45 node-5 kernel: [    1.108704] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 12:30:45 node-5 kernel: [    1.120623] usb usb1: Product: EHCI Host Controller
Jul 24 12:30:45 node-5 kernel: [    1.126652] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 12:30:45 node-5 kernel: [    1.132703] usb usb1: SerialNumber: 0000:00:1a.0
Jul 24 12:30:45 node-5 kernel: [    1.138674] hub 1-0:1.0: USB hub found
Jul 24 12:30:45 node-5 kernel: [    1.144451] hub 1-0:1.0: 2 ports detected
Jul 24 12:30:45 node-5 kernel: [    1.150256] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 24 12:30:45 node-5 kernel: [    1.155865] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 24 12:30:45 node-5 kernel: [    1.166792] ehci-pci 0000:00:1d.0: debug port 2
Jul 24 12:30:45 node-5 kernel: [    1.176128] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 24 12:30:45 node-5 kernel: [    1.176131] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 24 12:30:45 node-5 kernel: [    1.192366] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 24 12:30:45 node-5 kernel: [    1.197593] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 12:30:45 node-5 kernel: [    1.202909] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 12:30:45 node-5 kernel: [    1.213545] usb usb2: Product: EHCI Host Controller
Jul 24 12:30:45 node-5 kernel: [    1.219049] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 12:30:45 node-5 kernel: [    1.224621] usb usb2: SerialNumber: 0000:00:1d.0
Jul 24 12:30:45 node-5 kernel: [    1.230173] hub 2-0:1.0: USB hub found
Jul 24 12:30:45 node-5 kernel: [    1.235566] hub 2-0:1.0: 2 ports detected
Jul 24 12:30:45 node-5 kernel: [    1.240923] ehci-platform: EHCI generic platform driver
Jul 24 12:30:45 node-5 kernel: [    1.246195] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 24 12:30:45 node-5 kernel: [    1.251553] ohci-pci: OHCI PCI platform driver
Jul 24 12:30:45 node-5 kernel: [    1.256888] ohci-platform: OHCI generic platform driver
Jul 24 12:30:45 node-5 kernel: [    1.262142] uhci_hcd: USB Universal Host Controller Interface driver
Jul 24 12:30:45 node-5 kernel: [    1.267563] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 24 12:30:45 node-5 kernel: [    1.460146] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 24 12:30:45 node-5 kernel: [    1.771905] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 24 12:30:45 node-5 kernel: [    1.788272] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 24 12:30:45 node-5 kernel: [    1.793887] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 12:30:45 node-5 kernel: [    1.799664] hub 1-1:1.0: USB hub found
Jul 24 12:30:45 node-5 kernel: [    1.805259] hub 1-1:1.0: 6 ports detected
Jul 24 12:30:45 node-5 kernel: [    1.919776] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 24 12:30:45 node-5 kernel: [    2.306890] i8042: No controller found
Jul 24 12:30:45 node-5 kernel: [    2.312471] mousedev: PS/2 mouse device common for all mice
Jul 24 12:30:45 node-5 kernel: [    2.318221] rtc_cmos 00:02: RTC can wake from S4
Jul 24 12:30:45 node-5 kernel: [    2.320259] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 24 12:30:45 node-5 kernel: [    2.320260] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 12:30:45 node-5 kernel: [    2.320775] hub 2-1:1.0: USB hub found
Jul 24 12:30:45 node-5 kernel: [    2.321008] hub 2-1:1.0: 8 ports detected
Jul 24 12:30:45 node-5 kernel: [    2.346936] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 24 12:30:45 node-5 kernel: [    2.352748] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 24 12:30:45 node-5 kernel: [    2.364143] device-mapper: uevent: version 1.0.3
Jul 24 12:30:45 node-5 kernel: [    2.369870] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 24 12:30:45 node-5 kernel: [    2.381298] ledtrig-cpu: registered to indicate activity on CPUs
Jul 24 12:30:45 node-5 kernel: [    2.387311] TCP: cubic registered
Jul 24 12:30:45 node-5 kernel: [    2.393214] NET: Registered protocol family 10
Jul 24 12:30:45 node-5 kernel: [    2.399301] NET: Registered protocol family 17
Jul 24 12:30:45 node-5 kernel: [    2.405101] Key type dns_resolver registered
Jul 24 12:30:45 node-5 kernel: [    2.411191] Loading compiled-in X.509 certificates
Jul 24 12:30:45 node-5 kernel: [    2.417412] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 24 12:30:45 node-5 kernel: [    2.429070] registered taskstats version 1
Jul 24 12:30:45 node-5 kernel: [    2.437145] Key type trusted registered
Jul 24 12:30:45 node-5 kernel: [    2.444872] Key type encrypted registered
Jul 24 12:30:45 node-5 kernel: [    2.450372] AppArmor: AppArmor sha1 policy hashing enabled
Jul 24 12:30:45 node-5 kernel: [    2.455890] IMA: No TPM chip found, activating TPM-bypass!
Jul 24 12:30:45 node-5 kernel: [    2.461968] regulator-dummy: disabling
Jul 24 12:30:45 node-5 kernel: [    2.467459]   Magic number: 8:559:532
Jul 24 12:30:45 node-5 kernel: [    2.472934] bdi 1:10: hash matches
Jul 24 12:30:45 node-5 kernel: [    2.478298] tty ttyS12: hash matches
Jul 24 12:30:45 node-5 kernel: [    2.483584] acpi device:122: hash matches
Jul 24 12:30:45 node-5 kernel: [    2.489007] rtc_cmos 00:02: setting system clock to 2016-07-24 12:30:11 UTC (1469363411)
Jul 24 12:30:45 node-5 kernel: [    2.500993] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 24 12:30:45 node-5 kernel: [    2.506451] EDD information not available.
Jul 24 12:30:45 node-5 kernel: [    2.511858] PM: Hibernation image not present or could not be loaded.
Jul 24 12:30:45 node-5 kernel: [    2.512689] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 24 12:30:45 node-5 kernel: [    2.523868] Write protecting the kernel read-only data: 12288k
Jul 24 12:30:45 node-5 kernel: [    2.530020] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 24 12:30:45 node-5 kernel: [    2.542354] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 24 12:30:45 node-5 kernel: [    2.573372] device-mapper: multipath: version 1.6.0 loaded
Jul 24 12:30:45 node-5 kernel: [    2.580892] systemd-udevd[219]: starting version 204
Jul 24 12:30:45 node-5 kernel: [    2.601896] md: linear personality registered for level -1
Jul 24 12:30:45 node-5 kernel: [    2.607293] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 24 12:30:45 node-5 kernel: [    2.621724] md: multipath personality registered for level -4
Jul 24 12:30:45 node-5 kernel: [    2.629606] md: raid0 personality registered for level 0
Jul 24 12:30:45 node-5 kernel: [    2.637577] md: raid1 personality registered for level 1
Jul 24 12:30:45 node-5 kernel: [    2.648804] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 24 12:30:45 node-5 kernel: [    2.654963] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 24 12:30:45 node-5 kernel: [    2.655267] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 24 12:30:45 node-5 kernel: [    2.655565] megasas: FW now in Ready state
Jul 24 12:30:45 node-5 kernel: [    2.655630] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.655671] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.655709] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.655743] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.655780] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.655811] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.655845] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.655882] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.655920] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.655954] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.655987] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.656024] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.656041] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.656077] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.656113] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.656150] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.656310] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 24 12:30:45 node-5 kernel: [    2.693565] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 24 12:30:45 node-5 kernel: [    2.706810] 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 24 12:30:45 node-5 kernel: [    2.711196] raid6: sse2x1    3324 MB/s
Jul 24 12:30:45 node-5 kernel: [    2.727481] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 12:30:45 node-5 kernel: [    2.734451] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.734455] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.734463] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.734467] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.734508] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 12:30:45 node-5 kernel: [    2.756646] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 24 12:30:45 node-5 kernel: [    2.770024] 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 24 12:30:45 node-5 kernel: [    2.779218] raid6: sse2x2   10651 MB/s
Jul 24 12:30:45 node-5 kernel: [    2.790270] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 12:30:45 node-5 kernel: [    2.846971] raid6: sse2x4    9985 MB/s
Jul 24 12:30:45 node-5 kernel: [    2.918911] raid6: avx2x1   14941 MB/s
Jul 24 12:30:45 node-5 kernel: [    2.990855] raid6: avx2x2   18852 MB/s
Jul 24 12:30:45 node-5 kernel: [    3.062787] raid6: avx2x4   21292 MB/s
Jul 24 12:30:45 node-5 kernel: [    3.068997] raid6: using algorithm avx2x4 (21292 MB/s)
Jul 24 12:30:45 node-5 kernel: [    3.075164] raid6: using avx2x2 recovery algorithm
Jul 24 12:30:45 node-5 kernel: [    3.081193] megasas:IOC Init cmd success
Jul 24 12:30:45 node-5 kernel: [    3.081196] Switched to clocksource tsc
Jul 24 12:30:45 node-5 kernel: [    3.093082] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.093086] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.093090] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.093094] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.093146] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.105321] xor: automatically using best checksumming function:
Jul 24 12:30:45 node-5 kernel: [    3.107586] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 24 12:30:45 node-5 kernel: [    3.107586] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 12:30:45 node-5 kernel: [    3.107587] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 24 12:30:45 node-5 kernel: [    3.107588] usb 2-1.4: Manufacturer: Avocent
Jul 24 12:30:45 node-5 kernel: [    3.107588] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 24 12:30:45 node-5 kernel: [    3.116426] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 24 12:30:45 node-5 kernel: [    3.116427] 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 24 12:30:45 node-5 kernel: [    3.116428] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 12:30:45 node-5 kernel: [    3.116473] megasas: INIT adapter done
Jul 24 12:30:45 node-5 kernel: [    3.116532] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.116566] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.116605] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.116642] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.116703] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.128378] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 24 12:30:45 node-5 kernel: [    3.128380] 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 24 12:30:45 node-5 kernel: [    3.128380] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 12:30:45 node-5 kernel: [    3.128434] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.128464] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.128500] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.128530] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.128594] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 12:30:45 node-5 kernel: [    3.186686] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 24 12:30:45 node-5 kernel: [    3.187049] scsi0 : LSI SAS based MegaRAID driver
Jul 24 12:30:45 node-5 kernel: [    3.193977] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 12:30:45 node-5 kernel: [    3.204952] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 12:30:45 node-5 kernel: [    3.209082] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 24 12:30:45 node-5 kernel: [    3.209257] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 24 12:30:45 node-5 kernel: [    3.209385] sd 0:2:0:0: [sda] Write Protect is off
Jul 24 12:30:45 node-5 kernel: [    3.209386] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 24 12:30:45 node-5 kernel: [    3.209485] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 24 12:30:45 node-5 kernel: [    3.240819]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 24 12:30:45 node-5 kernel: [    3.242161] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 24 12:30:45 node-5 kernel: [    3.330548] hidraw: raw HID events driver (C) Jiri Kosina
Jul 24 12:30:45 node-5 kernel: [    3.340380] usbcore: registered new interface driver usbhid
Jul 24 12:30:45 node-5 kernel: [    3.347262] usbhid: USB HID core driver
Jul 24 12:30:45 node-5 kernel: [    3.354901] 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 24 12:30:45 node-5 kernel: [    3.366510]    avx       : 35596.000 MB/sec
Jul 24 12:30:45 node-5 kernel: [    3.375368] 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 24 12:30:45 node-5 kernel: [    3.389206] async_tx: api initialized (async)
Jul 24 12:30:45 node-5 kernel: [    3.389256] 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 24 12:30:45 node-5 kernel: [    3.389629] 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 24 12:30:45 node-5 kernel: [    3.389692] 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 24 12:30:45 node-5 kernel: [    3.389912] 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 24 12:30:45 node-5 kernel: [    3.456034] md: raid6 personality registered for level 6
Jul 24 12:30:45 node-5 kernel: [    3.463344] md: raid5 personality registered for level 5
Jul 24 12:30:45 node-5 kernel: [    3.470496] md: raid4 personality registered for level 4
Jul 24 12:30:45 node-5 kernel: [    3.479616] random: lvm urandom read with 32 bits of entropy available
Jul 24 12:30:45 node-5 kernel: [    3.486658] md: raid10 personality registered for level 10
Jul 24 12:30:45 node-5 kernel: [    3.543540] multipathd (370): /proc/370/oom_adj is deprecated, please use /proc/370/oom_score_adj instead.
Jul 24 12:30:45 node-5 kernel: [    3.600975] bio: create slab <bio-1> at 1
Jul 24 12:30:45 node-5 kernel: [    4.419702] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 12:30:45 node-5 kernel: [    5.099577] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 24 12:30:45 node-5 kernel: [    5.144932] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 24 12:30:45 node-5 kernel: [    5.342271] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 24 12:30:45 node-5 kernel: [    5.370453] random: nonblocking pool is initialized
Jul 24 12:30:45 node-5 kernel: [    5.378298] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 24 12:30:45 node-5 kernel: [    5.441581] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 12:30:45 node-5 kernel: [    5.604444] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 24 12:30:45 node-5 kernel: [    5.642155] XFS (dm-0): Mounting Filesystem
Jul 24 12:30:45 node-5 kernel: [    5.888887] XFS (dm-0): Ending clean mount
Jul 24 12:30:45 node-5 kernel: [    5.932386] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 12:30:45 node-5 kernel: [    5.959325] XFS (dm-1): Mounting Filesystem
Jul 24 12:30:45 node-5 kernel: [    6.108726] XFS (dm-1): Ending clean mount
Jul 24 12:30:45 node-5 kernel: [    7.853398] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 12:30:45 node-5 kernel: [    7.876110] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 12:30:45 node-5 kernel: [    8.047926] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 24 12:30:45 node-5 kernel: [    8.047937] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 24 12:30:45 node-5 kernel: [    8.047944] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 24 12:30:45 node-5 kernel: [    8.047952] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 24 12:30:45 node-5 kernel: [    8.096042] systemd-udevd[779]: starting version 204
Jul 24 12:30:45 node-5 kernel: [    8.297137] wmi: Mapper loaded
Jul 24 12:30:45 node-5 kernel: [    8.299809] power_meter ACPI000D:00: Found ACPI power meter.
Jul 24 12:30:45 node-5 kernel: [    8.299821] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 24 12:30:45 node-5 kernel: [    8.322086] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 24 12:30:45 node-5 kernel: [    8.322090] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 12:30:45 node-5 kernel: [    8.322093] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 24 12:30:45 node-5 kernel: [    8.322094] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 12:30:45 node-5 kernel: [    8.322116] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 24 12:30:45 node-5 kernel: [    8.328628] IPMI System Interface driver.
Jul 24 12:30:45 node-5 kernel: [    8.328669] ipmi_si: probing via ACPI
Jul 24 12:30:45 node-5 kernel: [    8.328682] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 24 12:30:45 node-5 kernel: [    8.328683] ipmi_si: Adding ACPI-specified kcs state machine
Jul 24 12:30:45 node-5 kernel: [    8.328690] ipmi_si: probing via SMBIOS
Jul 24 12:30:45 node-5 kernel: [    8.328691] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 12:30:45 node-5 kernel: [    8.328691] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 24 12:30:45 node-5 kernel: [    8.328693] ipmi_si: probing via SPMI
Jul 24 12:30:45 node-5 kernel: [    8.328694] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 12:30:45 node-5 kernel: [    8.328694] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 24 12:30:45 node-5 kernel: [    8.328695] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 24 12:30:45 node-5 kernel: [    8.359451] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 24 12:30:45 node-5 kernel: [    8.447406] systemd-udevd[807]: renamed network interface eth1 to enp7s0
Jul 24 12:30:45 node-5 kernel: [    8.463001] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 24 12:30:45 node-5 kernel: [    8.463012] ipmi_si 00:09: IPMI kcs interface initialized
Jul 24 12:30:45 node-5 kernel: [    8.478634] systemd-udevd[798]: renamed network interface eth0 to enp6s0
Jul 24 12:30:45 node-5 kernel: [    8.498559] systemd-udevd[797]: renamed network interface eth2 to enp8s0
Jul 24 12:30:45 node-5 kernel: [    8.534507] systemd-udevd[799]: renamed network interface eth3 to enp9s0
Jul 24 12:30:45 node-5 kernel: [    8.728112] type=1400 audit(1469363417.741:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1037 comm="apparmor_parser"
Jul 24 12:30:45 node-5 kernel: [    8.728265] type=1400 audit(1469363417.741:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1037 comm="apparmor_parser"
Jul 24 12:30:45 node-5 kernel: [    8.728393] type=1400 audit(1469363417.741:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1037 comm="apparmor_parser"
Jul 24 12:30:45 node-5 kernel: [    8.731515] type=1400 audit(1469363417.745:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1068 comm="apparmor_parser"
Jul 24 12:30:45 node-5 kernel: [    8.731657] type=1400 audit(1469363417.745:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1068 comm="apparmor_parser"
Jul 24 12:30:45 node-5 kernel: [    8.731777] type=1400 audit(1469363417.745:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1068 comm="apparmor_parser"
Jul 24 12:30:45 node-5 kernel: [    8.739674] type=1400 audit(1469363417.753:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1036 comm="apparmor_parser"
Jul 24 12:30:45 node-5 kernel: [    8.739815] type=1400 audit(1469363417.753:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1036 comm="apparmor_parser"
Jul 24 12:30:45 node-5 kernel: [    8.739932] type=1400 audit(1469363417.753:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1036 comm="apparmor_parser"
Jul 24 12:30:45 node-5 kernel: [    8.745983] type=1400 audit(1469363417.761:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1038 comm="apparmor_parser"
Jul 24 12:30:45 node-5 kernel: [    9.289228] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 12:30:45 node-5 kernel: [    9.300029] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 12:30:45 node-5 kernel: [    9.517190] enic 0000:06:00.0 enp6s0: Link UP
Jul 24 12:30:45 node-5 kernel: [    9.518706] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 24 12:30:45 node-5 kernel: [    9.518730] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 24 12:30:45 node-5 kernel: [   18.963334] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 24 12:30:45 node-5 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 24 12:30:46 node-5 failsafe: Failsafe of 120 seconds reached.
Jul 24 12:30:46 node-5 kernel: [   37.710345] init: failsafe main process (8402) killed by TERM signal
Jul 24 12:30:46 node-5 dbus[8442]: [system] AppArmor D-Bus mediation is enabled
Jul 24 12:30:47 node-5 kernel: [   37.851289] audit_printk_skb: 30 callbacks suppressed
Jul 24 12:30:47 node-5 kernel: [   37.851291] type=1400 audit(1469363447.072:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8528 comm="apparmor_parser"
Jul 24 12:30:47 node-5 kernel: [   37.851389] type=1400 audit(1469363447.072:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8527 comm="apparmor_parser"
Jul 24 12:30:47 node-5 kernel: [   37.851394] type=1400 audit(1469363447.072:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8527 comm="apparmor_parser"
Jul 24 12:30:47 node-5 kernel: [   37.851397] type=1400 audit(1469363447.072:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8527 comm="apparmor_parser"
Jul 24 12:30:47 node-5 kernel: [   37.851629] type=1400 audit(1469363447.072:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8527 comm="apparmor_parser"
Jul 24 12:30:47 node-5 kernel: [   37.851631] type=1400 audit(1469363447.072:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8527 comm="apparmor_parser"
Jul 24 12:30:47 node-5 kernel: [   37.851747] type=1400 audit(1469363447.072:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8527 comm="apparmor_parser"
Jul 24 12:30:47 node-5 kernel: [   37.918758] type=1400 audit(1469363447.140:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8530 comm="apparmor_parser"
Jul 24 12:30:47 node-5 cron[8559]: (CRON) INFO (pidfile fd = 3)
Jul 24 12:30:47 node-5 anacron[8575]: Anacron 2.3 started on 2016-07-24
Jul 24 12:30:47 node-5 cron[8593]: (CRON) STARTUP (fork ok)
Jul 24 12:30:47 node-5 anacron[8575]: Will run job `cron.daily' in 5 min.
Jul 24 12:30:47 node-5 anacron[8575]: Will run job `cron.weekly' in 10 min.
Jul 24 12:30:47 node-5 anacron[8575]: Will run job `cron.monthly' in 15 min.
Jul 24 12:30:47 node-5 anacron[8575]: Jobs will be executed sequentially
Jul 24 12:30:47 node-5 cron[8593]: (CRON) INFO (Running @reboot jobs)
Jul 24 12:30:47 node-5 multipathd: path checkers start up
Jul 24 12:30:47 node-5 postfix/master[8738]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 24 12:30:51 node-5 puppet-agent[9053]: Reopening log files
Jul 24 12:30:52 node-5 puppet-agent[9053]: Could not request certificate: Connection refused - connect(2)
Jul 24 12:31:01 node-5 CRON[9084]: (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 24 12:31:06 node-5 puppet-user[9323]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 24 12:31:06 node-5 puppet-user[9323]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 24 12:31:07 node-5 puppet-user[9323]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 24 12:31:07 node-5 puppet-user[9323]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 24 12:31:07 node-5 puppet-user[9323]: Finished catalog run in 0.66 seconds
Jul 24 12:31:09 node-5 multipathd: uevent trigger error
Jul 24 12:31:09 node-5 puppet-user[9748]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 12:31:09 node-5 puppet-user[9748]: Compiled catalog for node-5.domain.tld in environment production in 0.09 seconds
Jul 24 12:31:09 node-5 puppet-user[9748]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 24 12:31:09 node-5 puppet-user[9748]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 24 12:31:09 node-5 puppet-user[9748]: (/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 24 12:31:09 node-5 puppet-user[9748]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 24 12:31:09 node-5 puppet-user[9748]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 24 12:31:09 node-5 puppet-user[9748]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 24 12:31:09 node-5 puppet-user[9748]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 24 12:31:09 node-5 puppet-user[9748]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 24 12:31:09 node-5 puppet-user[9748]: Finished catalog run in 0.05 seconds
Jul 24 12:31:10 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 12:31:10 node-5 nailgun-agent: D, [2016-07-24T12:31:01.506155 #9087] DEBUG -- : Sleep for 9 seconds before sending request
Jul 24 12:31:10 node-5 nailgun-agent: I, [2016-07-24T12:31:10.522430 #9087]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 12:31:10 node-5 puppet-user[10213]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 24 12:31:10 node-5 puppet-user[10213]: Compiled catalog for node-5.domain.tld in environment production in 0.08 seconds
Jul 24 12:31:11 node-5 nailgun-agent: D, [2016-07-24T12:31:11.001026 #9087] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 24 12:31:11 node-5 puppet-user[10213]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 24 12:31:11 node-5 puppet-user[10213]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 24 12:31:11 node-5 puppet-user[10213]: Finished catalog run in 0.02 seconds
Jul 24 12:31:12 node-5 puppet-user[10808]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 24 12:31:12 node-5 puppet-user[10808]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 24 12:31:12 node-5 puppet-user[10808]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 24 12:31:12 node-5 puppet-user[10808]: Finished catalog run in 0.03 seconds
Jul 24 12:31:14 node-5 puppet-user[11264]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 24 12:31:14 node-5 puppet-user[11264]: Compiled catalog for node-5.domain.tld in environment production in 0.22 seconds
Jul 24 12:31:14 node-5 puppet-user[11264]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 24 12:31:14 node-5 puppet-user[11264]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 24 12:31:15 node-5 puppet-user[11264]: (/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 24 12:31:15 node-5 kernel: [   66.111437] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 12:31:15 node-5 puppet-user[11264]: Finished catalog run in 0.80 seconds
Jul 24 12:31:15 node-5 puppet-agent[9053]: Could not run: SIGTERM
Jul 24 12:31:15 node-5 kernel: [   66.377147] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 24 12:31:15 node-5 ec2: 
Jul 24 12:31:15 node-5 ec2: #############################################################
Jul 24 12:31:15 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 24 12:31:15 node-5 ec2: 1024 09:01:62:34:44:9c:1b:ab:b5:d8:92:ca:c9:ac:54:9b  root@node-5.domain.tld (DSA)
Jul 24 12:31:15 node-5 ec2: 256 36:e2:ae:b7:9e:4e:56:40:39:d8:8f:77:22:3d:f0:60  root@node-5.domain.tld (ECDSA)
Jul 24 12:31:15 node-5 ec2: 256 d7:1b:25:08:ad:c2:3d:35:db:53:00:81:ce:31:65:1c  root@node-5.domain.tld (ED25519)
Jul 24 12:31:15 node-5 ec2: 2048 c8:8d:2d:78:79:69:7d:6e:32:21:17:e4:ae:c7:44:86  root@node-5.domain.tld (RSA)
Jul 24 12:31:15 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 24 12:31:15 node-5 ec2: #############################################################
Jul 24 12:31:16 node-5 puppet-user[11936]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 24 12:31:17 node-5 puppet-user[11936]: Compiled catalog for node-5.domain.tld in environment production in 0.23 seconds
Jul 24 12:31:17 node-5 puppet-user[11936]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 24 12:31:17 node-5 puppet-user[11936]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 24 12:31:17 node-5 puppet-user[11936]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 24 12:31:17 node-5 puppet-user[11936]: (/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 24 12:31:17 node-5 puppet-user[11936]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 24 12:31:17 node-5 puppet-user[11936]: Finished catalog run in 0.29 seconds
Jul 24 12:31:18 node-5 puppet-user[12432]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 24 12:31:18 node-5 puppet-user[12432]: Compiled catalog for node-5.domain.tld in environment production in 0.15 seconds
Jul 24 12:31:19 node-5 puppet-user[12432]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 24 12:31:19 node-5 kernel: [   69.834220] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 24 12:31:19 node-5 kernel: [   69.834270] 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 24 12:31:19 node-5 puppet-user[12432]: (/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 24 12:31:19 node-5 puppet-user[12432]: Finished catalog run in 0.05 seconds
Jul 24 12:31:20 node-5 puppet-user[12888]: (Scope(Class[main])) MODULAR: sync_time
Jul 24 12:31:20 node-5 puppet-user[12888]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 24 12:31:20 node-5 ntpdate[13312]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.221239 #9087] DEBUG -- : Trying to find block devices
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.221358 #9087] DEBUG -- : Found block device: sda
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.221415 #9087] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.221442 #9087] DEBUG -- : Trying to get list of physical devices
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.221608 #9087] DEBUG -- : Getting udev properties for device: sda
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.223569 #9087] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /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"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Jul 24 12:31:23 node-5 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"99617", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.223641 #9087] DEBUG -- : Trying to find out if device sda is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.223689 #9087] DEBUG -- : Device sda removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.223707 #9087] DEBUG -- : Device sda seems to be appropriate
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.224182 #9087] DEBUG -- : Getting udev properties for device: dm-0
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.226264 #9087] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-F86arCMy7ArmlPke4WSM99Ct6lrIE0tjHqt9SkBt7Oys2U3w0ji0wggkfJXCTF8j /dev/disk/by-uuid/b3403f25-c0ba-40b3-a60d-df60b2a9635f /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-F86arCMy7ArmlPke4WSM99Ct6lrIE0tjHqt9SkBt7Oys2U3w0ji0wggkfJXCTF8j", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b3403f25-c0ba-40b3-a60d-df60b2a9635f", "ID_FS_UUID_ENC"=>"b3403f25-c0ba-40b3-a60d-df60b2a9635f", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58600", "nomdmonddf"=>"1", "nomd
Jul 24 12:31:23 node-5 nailgun-agent: monisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.226292 #9087] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.226335 #9087] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.226348 #9087] DEBUG -- : Device dm-0 seems to be appropriate
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.226363 #9087] DEBUG -- : Getting udev properties for device: dm-1
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.228737 #9087] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-WNQzmDPSU4Ae13UsMOLNvn8HjZXJydC2YNW5O3sdPPftZCpQDCjg78GxBysiC6kr /dev/disk/by-uuid/36ba585e-d45b-49f2-8ccb-9ff3beb4aedb /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-WNQzmDPSU4Ae13UsMOLNvn8HjZXJydC2YNW5O3sdPPftZCpQDCjg78GxBysiC6kr", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"36ba585e-d45b-49f2-8ccb-9ff3beb4aedb", "ID_FS_UUID_ENC"=>"36ba585e-d45b-49f2-8ccb-9ff3beb4aedb", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31
Jul 24 12:31:23 node-5 nailgun-agent: 585", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.228766 #9087] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.228798 #9087] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.228814 #9087] DEBUG -- : Device dm-1 seems to be appropriate
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.228845 #9087] DEBUG -- : Getting udev properties for device: dm-2
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.230769 #9087] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-dly7XdAfsSgUzjtGHK5cQ4MTBzN5b13B12xtJpj6MljZA9tZhFjbr0ozQ1hPgrsY /dev/disk/by-uuid/5ee1dff4-9d75-40eb-bd4c-73bc1081e53a /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-dly7XdAfsSgUzjtGHK5cQ4MTBzN5b13B12xtJpj6MljZA9tZhFjbr0ozQ1hPgrsY", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"5ee1dff4-9d75-40eb-bd4c-73bc1081e53a", "ID_FS_UUID_ENC"=>"5ee1dff4-9d75-40eb-bd4c-73bc1081e53a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37563", "nomdmond
Jul 24 12:31:23 node-5 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.230796 #9087] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.230827 #9087] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.230841 #9087] DEBUG -- : Device dm-2 seems to be appropriate
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.230873 #9087] DEBUG -- : Getting udev properties for device: dm-3
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.232503 #9087] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-XvietOZzFIn3iKmrKFDy0k9Zoi2BqRhW4sBK8Owm3VWUy3dizmQZozmDGfbFtBEm /dev/disk/by-uuid/ed45649e-172e-45ad-883f-95dfb4e1334a /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-XvietOZzFIn3iKmrKFDy0k9Zoi2BqRhW4sBK8Owm3VWUy3dizmQZozmDGfbFtBEm", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ed45649e-172e-45ad-883f-95dfb4e1334a", "ID_FS_UUID_ENC"=>"ed45649e-172e-45ad-883f-95dfb4e1334a", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"45814", "nomdmonddf"=>"1", 
Jul 24 12:31:23 node-5 nailgun-agent: "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.232546 #9087] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.232578 #9087] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.232592 #9087] DEBUG -- : Device dm-3 seems to be appropriate
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.232624 #9087] DEBUG -- : Getting udev properties for device: dm-4
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.234456 #9087] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-rsLRghvOpOjMopJgASAJpjdXEdmja2HyhCLihWUBzQc5xMXnP7L0CX7DvPMcbzNh /dev/disk/by-uuid/f4aec397-b60b-4655-acae-f351d2ea28bc /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-rsLRghvOpOjMopJgASAJpjdXEdmja2HyhCLihWUBzQc5xMXnP7L0CX7DvPMcbzNh", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f4aec397-b60b-4655-acae-f351d2ea28bc", "ID_FS_UUID_ENC"=>"f4aec397-b60b-4655-acae-f351d2ea28bc", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"48434", "nomdmonddf"=>"1", "nomd
Jul 24 12:31:23 node-5 nailgun-agent: monisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.234518 #9087] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.234551 #9087] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.234565 #9087] DEBUG -- : Device dm-4 seems to be appropriate
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.234581 #9087] DEBUG -- : Getting udev properties for device: dm-5
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.236514 #9087] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-rsLRghvOpOjMopJgASAJpjdXEdmja2HydtX9eRkATDp6gG134DNKH15qYp2OO74I /dev/disk/by-uuid/20f20a25-bbef-460a-ba13-f09c82ae47f6 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-rsLRghvOpOjMopJgASAJpjdXEdmja2HydtX9eRkATDp6gG134DNKH15qYp2OO74I", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"20f20a25-bbef-460a-ba13-f09c82ae47f6", "ID_FS_UUID_ENC"=>"20f20a25-bbef-460a-ba13-f09c82ae47f6", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49079", "nomdmonddf"=>"1", "nomdmonisw"
Jul 24 12:31:23 node-5 nailgun-agent: =>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.236556 #9087] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.236618 #9087] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.236633 #9087] DEBUG -- : Device dm-5 seems to be appropriate
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.236649 #9087] DEBUG -- : Getting udev properties for device: ram0
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.238219 #9087] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72363", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.238246 #9087] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.238301 #9087] DEBUG -- : Device ram0 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.238323 #9087] DEBUG -- : Getting udev properties for device: ram1
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.239837 #9087] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72447", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.239859 #9087] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.239889 #9087] DEBUG -- : Device ram1 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.239909 #9087] DEBUG -- : Getting udev properties for device: ram2
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.241487 #9087] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73115", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.241508 #9087] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.241573 #9087] DEBUG -- : Device ram2 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.241592 #9087] DEBUG -- : Getting udev properties for device: ram3
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.243177 #9087] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73174", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.243200 #9087] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.243229 #9087] DEBUG -- : Device ram3 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.243249 #9087] DEBUG -- : Getting udev properties for device: ram4
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.244958 #9087] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73233", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.244987 #9087] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.245017 #9087] DEBUG -- : Device ram4 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.245044 #9087] DEBUG -- : Getting udev properties for device: ram5
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.246687 #9087] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73368", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.246709 #9087] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.246772 #9087] DEBUG -- : Device ram5 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.246791 #9087] DEBUG -- : Getting udev properties for device: ram6
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.248341 #9087] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73470", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.248372 #9087] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.248403 #9087] DEBUG -- : Device ram6 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.248430 #9087] DEBUG -- : Getting udev properties for device: ram7
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.250293 #9087] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73581", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.250316 #9087] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.250347 #9087] DEBUG -- : Device ram7 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.250366 #9087] DEBUG -- : Getting udev properties for device: ram8
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.251823 #9087] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73642", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.251843 #9087] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.251885 #9087] DEBUG -- : Device ram8 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.251906 #9087] DEBUG -- : Getting udev properties for device: ram9
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.253421 #9087] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"73709", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.253442 #9087] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.253482 #9087] DEBUG -- : Device ram9 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.253510 #9087] DEBUG -- : Getting udev properties for device: loop0
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.255082 #9087] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71089", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.255110 #9087] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.255139 #9087] DEBUG -- : Device loop0 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.259885 #9087] DEBUG -- : Getting udev properties for device: loop1
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.261902 #9087] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71188", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.261925 #9087] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.261955 #9087] DEBUG -- : Device loop1 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.261974 #9087] DEBUG -- : Getting udev properties for device: loop2
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.263419 #9087] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71262", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.263440 #9087] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.263472 #9087] DEBUG -- : Device loop2 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.263491 #9087] DEBUG -- : Getting udev properties for device: loop3
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.265394 #9087] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71345", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.265414 #9087] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.265448 #9087] DEBUG -- : Device loop3 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.265466 #9087] DEBUG -- : Getting udev properties for device: loop4
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.267028 #9087] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71415", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.267048 #9087] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.267083 #9087] DEBUG -- : Device loop4 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.267101 #9087] DEBUG -- : Getting udev properties for device: loop5
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.268614 #9087] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71515", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.268660 #9087] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.268693 #9087] DEBUG -- : Device loop5 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.268710 #9087] DEBUG -- : Getting udev properties for device: loop6
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.270241 #9087] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"71922", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.270273 #9087] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.270343 #9087] DEBUG -- : Device loop6 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.270361 #9087] DEBUG -- : Getting udev properties for device: loop7
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.271820 #9087] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72284", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.271840 #9087] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.271867 #9087] DEBUG -- : Device loop7 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.271912 #9087] DEBUG -- : Getting udev properties for device: ram10
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.273705 #9087] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72522", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.273725 #9087] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.273752 #9087] DEBUG -- : Device ram10 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.273770 #9087] DEBUG -- : Getting udev properties for device: ram11
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.275207 #9087] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72633", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.275227 #9087] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.275258 #9087] DEBUG -- : Device ram11 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.275275 #9087] DEBUG -- : Getting udev properties for device: ram12
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.276874 #9087] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72710", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.276893 #9087] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.276929 #9087] DEBUG -- : Device ram12 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.276947 #9087] DEBUG -- : Getting udev properties for device: ram13
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.278414 #9087] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72770", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.278433 #9087] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.278463 #9087] DEBUG -- : Device ram13 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.278480 #9087] DEBUG -- : Getting udev properties for device: ram14
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.279987 #9087] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72862", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.280007 #9087] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.280039 #9087] DEBUG -- : Device ram14 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.280057 #9087] DEBUG -- : Getting udev properties for device: ram15
Jul 24 12:31:23 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281587 #9087] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72987", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281607 #9087] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281687 #9087] DEBUG -- : Device ram15 removable parameter: "0"
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281721 #9087] 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-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281735 #9087] DEBUG -- : Block device seems to be physical data storage: sda
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281769 #9087] DEBUG -- : Found block device: dm-0
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281793 #9087] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281806 #9087] DEBUG -- : Found block device: dm-1
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281823 #9087] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281847 #9087] DEBUG -- : Found block device: dm-2
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281856 #9087] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281893 #9087] DEBUG -- : Found block device: dm-3
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281904 #9087] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281913 #9087] DEBUG -- : Found block device: dm-4
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281922 #9087] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281931 #9087] DEBUG -- : Found block device: dm-5
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281941 #9087] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281949 #9087] DEBUG -- : Found block device: ram0
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281959 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281967 #9087] DEBUG -- : Found block device: ram1
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.281977 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282016 #9087] DEBUG -- : Found block device: ram2
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282027 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282036 #9087] DEBUG -- : Found block device: ram3
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282046 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282054 #9087] DEBUG -- : Found block device: ram4
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282063 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282071 #9087] DEBUG -- : Found block device: ram5
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282083 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282091 #9087] DEBUG -- : Found block device: ram6
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282101 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282133 #9087] DEBUG -- : Found block device: ram7
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282142 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282151 #9087] DEBUG -- : Found block device: ram8
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282160 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282168 #9087] DEBUG -- : Found block device: ram9
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282177 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282186 #9087] DEBUG -- : Found block device: loop0
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282195 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282203 #9087] DEBUG -- : Found block device: loop1
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282212 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282242 #9087] DEBUG -- : Found block device: loop2
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282252 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282260 #9087] DEBUG -- : Found block device: loop3
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282270 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282278 #9087] DEBUG -- : Found block device: loop4
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282288 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282296 #9087] DEBUG -- : Found block device: loop5
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282304 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282313 #9087] DEBUG -- : Found block device: loop6
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282325 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282361 #9087] DEBUG -- : Found block device: loop7
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282371 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282379 #9087] DEBUG -- : Found block device: ram10
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282389 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282397 #9087] DEBUG -- : Found block device: ram11
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282405 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282414 #9087] DEBUG -- : Found block device: ram12
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282423 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282431 #9087] DEBUG -- : Found block device: ram13
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282440 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282485 #9087] DEBUG -- : Found block device: ram14
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282495 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282503 #9087] DEBUG -- : Found block device: ram15
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282512 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.282540 #9087] 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-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.340642 #9087] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 24 12:31:23 node-5 nailgun-agent: D, [2016-07-24T12:31:23.340693 #9087] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 24 12:31:26 node-5 ntpdate[13312]: adjust time server 10.20.0.2 offset -0.091220 sec
Jul 24 12:31:26 node-5 puppet-user[12888]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 24 12:31:26 node-5 puppet-user[12888]: Finished catalog run in 6.16 seconds
Jul 24 12:31:35 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375448 #9087] DEBUG -- : Trying to find block devices
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375556 #9087] DEBUG -- : Found block device: sda
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375585 #9087] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375603 #9087] DEBUG -- : Block device seems to be physical data storage: sda
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375634 #9087] DEBUG -- : Found block device: dm-0
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375684 #9087] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375696 #9087] DEBUG -- : Found block device: dm-1
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375707 #9087] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375716 #9087] DEBUG -- : Found block device: dm-2
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375725 #9087] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375734 #9087] DEBUG -- : Found block device: dm-3
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375744 #9087] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375752 #9087] DEBUG -- : Found block device: dm-4
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375762 #9087] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375770 #9087] DEBUG -- : Found block device: dm-5
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375809 #9087] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375817 #9087] DEBUG -- : Found block device: ram0
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375826 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375834 #9087] DEBUG -- : Found block device: ram1
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375843 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375851 #9087] DEBUG -- : Found block device: ram2
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375860 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375868 #9087] DEBUG -- : Found block device: ram3
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375876 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375913 #9087] DEBUG -- : Found block device: ram4
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375922 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375931 #9087] DEBUG -- : Found block device: ram5
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375940 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375947 #9087] DEBUG -- : Found block device: ram6
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375957 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375965 #9087] DEBUG -- : Found block device: ram7
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375973 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.375981 #9087] DEBUG -- : Found block device: ram8
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376018 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376027 #9087] DEBUG -- : Found block device: ram9
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376037 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376045 #9087] DEBUG -- : Found block device: loop0
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376055 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376062 #9087] DEBUG -- : Found block device: loop1
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376070 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376078 #9087] DEBUG -- : Found block device: loop2
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376086 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376094 #9087] DEBUG -- : Found block device: loop3
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376134 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376144 #9087] DEBUG -- : Found block device: loop4
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376153 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376161 #9087] DEBUG -- : Found block device: loop5
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376169 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376177 #9087] DEBUG -- : Found block device: loop6
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376186 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376194 #9087] DEBUG -- : Found block device: loop7
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376203 #9087] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376236 #9087] DEBUG -- : Found block device: ram10
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376245 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376253 #9087] DEBUG -- : Found block device: ram11
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376262 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376269 #9087] DEBUG -- : Found block device: ram12
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376278 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376286 #9087] DEBUG -- : Found block device: ram13
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376322 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376331 #9087] DEBUG -- : Found block device: ram14
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376340 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376347 #9087] DEBUG -- : Found block device: ram15
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376356 #9087] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.376384 #9087] 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-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Jul 24 12:31:35 node-5 nailgun-agent: D, [2016-07-24T12:31:35.548909 #9087] DEBUG -- : Response: status: 200 body: {"id": 5}
Jul 24 12:31:35 node-5 nailgun-agent: I, [2016-07-24T12:31:35.549090 #9087]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 24 12:32:01 node-5 CRON[13782]: (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 24 12:32:02 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 12:32:02 node-5 nailgun-agent: I, [2016-07-24T12:32:02.731268 #13785]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 12:32:15 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 12:32:15 node-5 nailgun-agent: I, [2016-07-24T12:32:15.818382 #13785]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 24 12:32:17 node-5 puppet-user[14113]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 12:32:17 node-5 puppet-user[14113]: Compiled catalog for node-5.domain.tld in environment production in 0.12 seconds
Jul 24 12:32:17 node-5 puppet-user[14113]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 24 12:32:17 node-5 puppet-user[14113]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 24 12:32:17 node-5 puppet-user[14113]: Finished catalog run in 0.09 seconds
Jul 24 12:32:19 node-5 puppet-user[14571]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 24 12:32:20 node-5 puppet-user[14571]: Compiled catalog for node-5.domain.tld in environment production in 1.11 seconds
Jul 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:20 node-5 puppet-user[14571]: (/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 24 12:32:37 node-5 puppet-user[14571]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 24 12:32:37 node-5 puppet-user[14571]: Finished catalog run in 16.75 seconds
Jul 24 12:32:39 node-5 puppet-user[15461]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 24 12:32:39 node-5 puppet-user[15461]: Compiled catalog for node-5.domain.tld in environment production in 0.14 seconds
Jul 24 12:32:44 node-5 puppet-user[15461]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 24 12:33:01 node-5 CRON[17095]: (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 24 12:33:03 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 12:33:04 node-5 nailgun-agent: I, [2016-07-24T12:33:03.998804 #17098]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 12:33:14 node-5 puppet-user[15461]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 24 12:33:14 node-5 puppet-user[15461]: Finished catalog run in 35.23 seconds
Jul 24 12:33:16 node-5 puppet-user[18075]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 24 12:33:17 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 12:33:17 node-5 nailgun-agent: I, [2016-07-24T12:33:17.189465 #17098]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 24 12:33:17 node-5 puppet-user[18075]: Compiled catalog for node-5.domain.tld in environment production in 0.56 seconds
Jul 24 12:33:17 node-5 puppet-user[18075]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 24 12:33:17 node-5 puppet-user[18075]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 24 12:33:17 node-5 puppet-user[18075]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 24 12:33:17 node-5 puppet-user[18075]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 24 12:33:17 node-5 puppet-user[18075]: Finished catalog run in 0.18 seconds
Jul 24 12:33:19 node-5 puppet-user[18724]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 24 12:33:20 node-5 puppet-user[18724]: Compiled catalog for node-5.domain.tld in environment production in 1.00 seconds
Jul 24 12:33:20 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 24 12:33:20 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 24 12:33:20 node-5 crontab[19169]: (root) LIST (root)
Jul 24 12:33:20 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 24 12:33:20 node-5 crontab[19170]: (root) REPLACE (root)
Jul 24 12:33:23 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/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 24 12:33:24 node-5 puppet-user[18724]: (/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 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/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 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 24 12:33:24 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/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 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/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 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/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 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/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 24 12:33:25 node-5 puppet-user[18724]: (/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 24 12:33:25 node-5 puppet-user[18724]: (/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 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/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 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/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 24 12:33:25 node-5 puppet-user[18724]: (/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 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 24 12:33:25 node-5 puppet-user[18724]: (/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 24 12:33:25 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8375" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 12:33:25 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 24 12:33:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:45 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:45 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:45 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:45 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:49 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:49 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:49 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:49 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:49 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:51 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:51 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:51 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:51 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:51 node-5 multipathd: uevent trigger error
<27>Jul 24 12:33:51 node-5 multipathd: uevent trigger error
<27>Jul 24 12:34:51 node-5 ntpdate[30457]: no servers can be used, exiting
<27>Jul 24 12:34:51 node-5 ntpdate[30547]: no servers can be used, exiting
<27>Jul 24 12:34:51 node-5 ntpdate[30793]: no servers can be used, exiting
<27>Jul 24 12:35:23 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:23 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:23 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:23 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:23 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:38 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:38 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:38 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:38 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:38 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:47 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:47 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:47 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:47 node-5 multipathd: uevent trigger error
<27>Jul 24 12:35:47 node-5 multipathd: uevent trigger error
<43>Jul 24 12:36:05 node-5 apache2_error [Sun Jul 24 12:35:59.923612 2016] [mpm_event:notice] [pid 7955:tid 140121676359552] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 12:36:05 node-5 apache2_error [Sun Jul 24 12:35:59.923747 2016] [core:notice] [pid 7955:tid 140121676359552] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 12:36:05 node-5 apache2_error [Sun Jul 24 12:36:03.102768 2016] [mpm_event:notice] [pid 7955:tid 140121676359552] AH00491: caught SIGTERM, shutting down
<43>Jul 24 12:36:05 node-5 apache2_error [Sun Jul 24 12:36:04.195430 2016] [mpm_worker:notice] [pid 8459:tid 140570091972480] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 12:36:05 node-5 apache2_error [Sun Jul 24 12:36:04.195483 2016] [core:notice] [pid 8459:tid 140570091972480] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 12:36:08 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:08 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:08 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:08 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:08 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:08 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:44 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:44 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:44 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:44 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:44 node-5 multipathd: uevent trigger error
<27>Jul 24 12:36:44 node-5 multipathd: uevent trigger error
<43>Jul 24 12:36:45 node-5 apache2_error [Sun Jul 24 12:36:41.205598 2016] [mpm_worker:notice] [pid 8459:tid 140570091972480] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 12:36:45 node-5 apache2_error [Sun Jul 24 12:36:41.214798 2016] [mpm_worker:warn] [pid 8459:tid 140570091972480] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 12:36:45 node-5 apache2_error [Sun Jul 24 12:36:41.215528 2016] [mpm_worker:notice] [pid 8459:tid 140570091972480] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 12:36:45 node-5 apache2_error [Sun Jul 24 12:36:41.215539 2016] [core:notice] [pid 8459:tid 140570091972480] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 12:37:03 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:37 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 24 12:37:42 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:42 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:42 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:42 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:42 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:58 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:58 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:58 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:58 node-5 multipathd: uevent trigger error
<27>Jul 24 12:37:58 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:05 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:05 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:05 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:05 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:05 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:11 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:11 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:11 node-5 haproxy[26048]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:11 node-5 haproxy[26048]: proxy odl-jetty has no server available!
<27>Jul 24 12:38:11 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:11 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:11 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:13 node-5 haproxy[26048]: Server odl-neutron-endpoint/node-2 is DOWN, reason: Layer4 timeout, check duration: 5002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:13 node-5 haproxy[26048]: proxy odl-neutron-endpoint has no server available!
<129>Jul 24 12:38:13 node-5 haproxy[27221]: 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 24 12:38:16 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:16 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:16 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:16 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:16 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:16 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:16 node-5 haproxy[27232]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:16 node-5 haproxy[27232]: proxy odl-jetty has no server available!
<27>Jul 24 12:38:19 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:19 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:19 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:19 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:19 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:19 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:21 node-5 haproxy[27232]: Server odl-neutron-endpoint/node-2 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 24 12:38:21 node-5 haproxy[27232]: proxy odl-neutron-endpoint has no server available!
<129>Jul 24 12:38:22 node-5 haproxy[29666]: 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 24 12:38:23 node-5 haproxy[29675]: 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 24 12:38:24 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:24 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:24 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:24 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:24 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:25 node-5 haproxy[29675]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:25 node-5 haproxy[29675]: proxy odl-jetty has no server available!
<129>Jul 24 12:38:27 node-5 haproxy[30864]: 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 24 12:38:28 node-5 haproxy[30878]: 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 24 12:38:28 node-5 haproxy[30878]: 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 24 12:38:29 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:29 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:29 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:29 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:30 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:31 node-5 haproxy[30878]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:31 node-5 haproxy[30878]: proxy odl-jetty has no server available!
<129>Jul 24 12:38:32 node-5 haproxy[32081]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:33 node-5 haproxy[32090]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:33 node-5 haproxy[32090]: 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 24 12:38:33 node-5 haproxy[32090]: 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 24 12:38:34 node-5 haproxy[32090]: 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 24 12:38:35 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:35 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:35 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:35 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:35 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:35 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:36 node-5 haproxy[32090]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:36 node-5 haproxy[32090]: proxy odl-jetty has no server available!
<129>Jul 24 12:38:37 node-5 haproxy[859]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:38 node-5 haproxy[868]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:38 node-5 haproxy[868]: 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 24 12:38:38 node-5 haproxy[868]: 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 24 12:38:38 node-5 haproxy[868]: 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 24 12:38:39 node-5 haproxy[868]: 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 24 12:38:40 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:40 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:40 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:40 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:40 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:41 node-5 haproxy[868]: 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 24 12:38:41 node-5 haproxy[868]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:41 node-5 haproxy[868]: proxy aodh has no server available!
<129>Jul 24 12:38:41 node-5 haproxy[868]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:41 node-5 haproxy[868]: proxy odl-jetty has no server available!
<129>Jul 24 12:38:43 node-5 haproxy[2050]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:43 node-5 haproxy[2050]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:43 node-5 haproxy[2050]: 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 24 12:38:43 node-5 haproxy[2050]: 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 24 12:38:44 node-5 haproxy[2050]: 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 24 12:38:44 node-5 haproxy[2050]: 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 24 12:38:44 node-5 haproxy[2050]: 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 24 12:38:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:46 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:46 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:46 node-5 haproxy[2050]: 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 24 12:38:46 node-5 haproxy[2050]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:46 node-5 haproxy[2050]: proxy aodh has no server available!
<129>Jul 24 12:38:46 node-5 haproxy[2050]: 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 24 12:38:46 node-5 haproxy[2050]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:46 node-5 haproxy[2050]: proxy ceilometer has no server available!
<129>Jul 24 12:38:46 node-5 haproxy[2050]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:46 node-5 haproxy[2050]: proxy odl-jetty has no server available!
<129>Jul 24 12:38:48 node-5 haproxy[3248]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:48 node-5 haproxy[3248]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:48 node-5 haproxy[3248]: 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 24 12:38:49 node-5 haproxy[3257]: 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 24 12:38:49 node-5 haproxy[3257]: 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 24 12:38:49 node-5 haproxy[3257]: 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 24 12:38:50 node-5 haproxy[3257]: 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 24 12:38:51 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:51 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:51 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:51 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:51 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:51 node-5 haproxy[3257]: 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 24 12:38:51 node-5 haproxy[3257]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:51 node-5 haproxy[3257]: proxy aodh has no server available!
<129>Jul 24 12:38:51 node-5 haproxy[3257]: 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 24 12:38:51 node-5 haproxy[3257]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:51 node-5 haproxy[3257]: proxy ceilometer has no server available!
<129>Jul 24 12:38:52 node-5 haproxy[3257]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:52 node-5 haproxy[3257]: proxy odl-jetty has no server available!
<129>Jul 24 12:38:53 node-5 haproxy[4441]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:54 node-5 haproxy[4450]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:54 node-5 haproxy[4450]: 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 24 12:38:54 node-5 haproxy[4450]: 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 24 12:38:54 node-5 haproxy[4450]: 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 24 12:38:55 node-5 haproxy[4450]: 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 24 12:38:55 node-5 haproxy[4450]: 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 24 12:38:55 node-5 haproxy[4450]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:55 node-5 haproxy[4450]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 12:38:56 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:56 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:56 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:56 node-5 multipathd: uevent trigger error
<27>Jul 24 12:38:56 node-5 multipathd: uevent trigger error
<129>Jul 24 12:38:56 node-5 haproxy[4450]: 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 24 12:38:56 node-5 haproxy[4450]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:56 node-5 haproxy[4450]: proxy aodh has no server available!
<129>Jul 24 12:38:57 node-5 haproxy[4450]: 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 24 12:38:57 node-5 haproxy[4450]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:57 node-5 haproxy[4450]: proxy ceilometer has no server available!
<129>Jul 24 12:38:57 node-5 haproxy[4450]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:38:57 node-5 haproxy[4450]: proxy odl-jetty has no server available!
<129>Jul 24 12:38:59 node-5 haproxy[5694]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:59 node-5 haproxy[5694]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:38:59 node-5 haproxy[5694]: 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 24 12:38:59 node-5 haproxy[5694]: 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 24 12:39:00 node-5 haproxy[5703]: 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 24 12:39:00 node-5 haproxy[5703]: 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 24 12:39:00 node-5 haproxy[5703]: 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 24 12:39:00 node-5 haproxy[5703]: 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 24 12:39:00 node-5 haproxy[5703]: 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 24 12:39:00 node-5 haproxy[5703]: 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 24 12:39:01 node-5 haproxy[5703]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:01 node-5 haproxy[5703]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:02 node-5 haproxy[5703]: 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.
<27>Jul 24 12:39:02 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:02 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:02 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:02 node-5 multipathd: uevent trigger error
<129>Jul 24 12:39:02 node-5 haproxy[5703]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:02 node-5 haproxy[5703]: proxy glance-registry has no server available!
<27>Jul 24 12:39:02 node-5 multipathd: uevent trigger error
<129>Jul 24 12:39:02 node-5 haproxy[5703]: 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 24 12:39:02 node-5 haproxy[5703]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:02 node-5 haproxy[5703]: proxy aodh has no server available!
<129>Jul 24 12:39:02 node-5 haproxy[5703]: 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 24 12:39:02 node-5 haproxy[5703]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:02 node-5 haproxy[5703]: proxy ceilometer has no server available!
<129>Jul 24 12:39:02 node-5 haproxy[5703]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:02 node-5 haproxy[5703]: proxy odl-jetty has no server available!
<129>Jul 24 12:39:05 node-5 haproxy[6987]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:05 node-5 haproxy[6987]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:05 node-5 haproxy[6987]: 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 24 12:39:05 node-5 haproxy[6987]: 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 24 12:39:05 node-5 haproxy[6987]: 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 24 12:39:05 node-5 haproxy[6987]: 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 24 12:39:05 node-5 haproxy[6987]: 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 24 12:39:06 node-5 haproxy[6987]: 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 24 12:39:06 node-5 haproxy[6987]: 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 24 12:39:06 node-5 haproxy[6987]: 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 24 12:39:06 node-5 haproxy[6987]: 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 24 12:39:06 node-5 haproxy[6987]: 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 24 12:39:06 node-5 haproxy[6987]: 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 24 12:39:06 node-5 haproxy[6987]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:06 node-5 haproxy[6987]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 12:39:07 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:07 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:07 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:07 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:07 node-5 multipathd: uevent trigger error
<129>Jul 24 12:39:07 node-5 haproxy[6987]: 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 24 12:39:08 node-5 haproxy[6987]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:08 node-5 haproxy[6987]: proxy glance-registry has no server available!
<129>Jul 24 12:39:08 node-5 haproxy[6987]: 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 24 12:39:08 node-5 haproxy[6987]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:08 node-5 haproxy[6987]: proxy aodh has no server available!
<129>Jul 24 12:39:08 node-5 haproxy[6987]: 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 24 12:39:08 node-5 haproxy[6987]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:08 node-5 haproxy[6987]: proxy ceilometer has no server available!
<129>Jul 24 12:39:08 node-5 haproxy[6987]: 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 24 12:39:08 node-5 haproxy[6987]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:08 node-5 haproxy[6987]: proxy nova-novncproxy has no server available!
<129>Jul 24 12:39:08 node-5 haproxy[6987]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:08 node-5 haproxy[6987]: proxy odl-jetty has no server available!
<27>Jul 24 12:39:09 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 24 12:39:10 node-5 haproxy[8197]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:10 node-5 haproxy[8197]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:10 node-5 haproxy[8197]: 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 24 12:39:10 node-5 haproxy[8197]: 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 24 12:39:10 node-5 haproxy[8197]: 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 24 12:39:11 node-5 haproxy[8211]: 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 24 12:39:11 node-5 haproxy[8211]: 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 24 12:39:11 node-5 haproxy[8211]: 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 24 12:39:11 node-5 haproxy[8211]: 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 24 12:39:11 node-5 haproxy[8211]: 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 24 12:39:11 node-5 haproxy[8211]: 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 24 12:39:11 node-5 haproxy[8211]: 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 24 12:39:12 node-5 haproxy[8211]: 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 24 12:39:12 node-5 haproxy[8211]: 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 24 12:39:12 node-5 haproxy[8211]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:12 node-5 haproxy[8211]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 12:39:13 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:13 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:13 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:13 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:13 node-5 multipathd: uevent trigger error
<129>Jul 24 12:39:13 node-5 haproxy[8211]: 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 24 12:39:13 node-5 haproxy[8211]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:13 node-5 haproxy[8211]: proxy glance-registry has no server available!
<129>Jul 24 12:39:13 node-5 haproxy[8211]: 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 24 12:39:13 node-5 haproxy[8211]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:13 node-5 haproxy[8211]: proxy aodh has no server available!
<129>Jul 24 12:39:13 node-5 haproxy[8211]: 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 24 12:39:13 node-5 haproxy[8211]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:13 node-5 haproxy[8211]: proxy ceilometer has no server available!
<129>Jul 24 12:39:14 node-5 haproxy[8211]: 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 24 12:39:14 node-5 haproxy[8211]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:14 node-5 haproxy[8211]: proxy nova-novncproxy has no server available!
<129>Jul 24 12:39:14 node-5 haproxy[8211]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:14 node-5 haproxy[8211]: proxy odl-jetty has no server available!
<129>Jul 24 12:39:16 node-5 haproxy[9513]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:16 node-5 haproxy[9513]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:16 node-5 haproxy[9513]: 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 24 12:39:16 node-5 haproxy[9513]: 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 24 12:39:16 node-5 haproxy[9513]: 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 24 12:39:16 node-5 haproxy[9513]: 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 24 12:39:16 node-5 haproxy[9513]: 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 24 12:39:16 node-5 haproxy[9513]: 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 24 12:39:16 node-5 haproxy[9513]: 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 24 12:39:17 node-5 haproxy[9513]: 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 24 12:39:17 node-5 haproxy[9513]: 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 24 12:39:17 node-5 haproxy[9513]: 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 24 12:39:17 node-5 haproxy[9513]: 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 24 12:39:17 node-5 haproxy[9513]: 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 24 12:39:17 node-5 haproxy[9513]: 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 24 12:39:17 node-5 haproxy[9513]: 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 24 12:39:17 node-5 haproxy[9513]: 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 24 12:39:17 node-5 haproxy[9513]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:17 node-5 haproxy[9513]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 12:39:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:18 node-5 multipathd: uevent trigger error
<129>Jul 24 12:39:18 node-5 haproxy[9513]: 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 24 12:39:18 node-5 haproxy[9513]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:18 node-5 haproxy[9513]: proxy glance-registry has no server available!
<129>Jul 24 12:39:19 node-5 haproxy[9513]: 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 24 12:39:19 node-5 haproxy[9513]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:19 node-5 haproxy[9513]: proxy aodh has no server available!
<129>Jul 24 12:39:19 node-5 haproxy[9513]: 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 24 12:39:19 node-5 haproxy[9513]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:19 node-5 haproxy[9513]: proxy ceilometer has no server available!
<129>Jul 24 12:39:19 node-5 haproxy[9513]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:19 node-5 haproxy[9513]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:19 node-5 haproxy[9513]: proxy nova-novncproxy has no server available!
<129>Jul 24 12:39:19 node-5 haproxy[9513]: Server odl-jetty/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:19 node-5 haproxy[9513]: proxy odl-jetty has no server available!
<27>Jul 24 12:39:22 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:22 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:22 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:22 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:22 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:25 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:25 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:25 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:25 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:25 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:25 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:25 node-5 multipathd: uevent trigger error
<129>Jul 24 12:39:25 node-5 haproxy[9513]: Server odl-neutron-endpoint/node-2 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:25 node-5 haproxy[9513]: proxy odl-neutron-endpoint has no server available!
<129>Jul 24 12:39:26 node-5 haproxy[9513]: 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 24 12:39:26 node-5 haproxy[9513]: Server keystone-1/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:26 node-5 haproxy[9513]: proxy keystone-1 has no server available!
<129>Jul 24 12:39:26 node-5 haproxy[9513]: 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 24 12:39:26 node-5 haproxy[9513]: Server keystone-2/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:26 node-5 haproxy[9513]: proxy keystone-2 has no server available!
<129>Jul 24 12:39:26 node-5 haproxy[9513]: 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 24 12:39:26 node-5 haproxy[9513]: Server nova-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:26 node-5 haproxy[9513]: proxy nova-api has no server available!
<129>Jul 24 12:39:26 node-5 haproxy[9513]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:26 node-5 haproxy[9513]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:26 node-5 haproxy[9513]: proxy nova-metadata-api has no server available!
<129>Jul 24 12:39:26 node-5 haproxy[9513]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 12:39:26 node-5 haproxy[9513]: Backup Server cinder-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:26 node-5 haproxy[9513]: proxy cinder-api has no server available!
<129>Jul 24 12:39:26 node-5 haproxy[9513]: 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 24 12:39:26 node-5 haproxy[9513]: Server glance-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:26 node-5 haproxy[9513]: proxy glance-api has no server available!
<129>Jul 24 12:39:26 node-5 haproxy[9513]: Server glance-glare/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 24 12:39:26 node-5 haproxy[9513]: Server glance-glare/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:26 node-5 haproxy[9513]: proxy glance-glare has no server available!
<129>Jul 24 12:39:26 node-5 haproxy[9513]: Server neutron/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 24 12:39:26 node-5 haproxy[9513]: Server neutron/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:26 node-5 haproxy[9513]: proxy neutron has no server available!
<129>Jul 24 12:39:27 node-5 haproxy[9513]: 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 24 12:39:27 node-5 haproxy[9513]: Backup Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:27 node-5 haproxy[9513]: proxy mysqld has no server available!
<129>Jul 24 12:39:27 node-5 haproxy[9513]: 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 24 12:39:27 node-5 haproxy[9513]: Server object-storage/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:27 node-5 haproxy[9513]: proxy object-storage has no server available!
<129>Jul 24 12:39:27 node-5 haproxy[9513]: Server heat-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 24 12:39:27 node-5 haproxy[9513]: Server heat-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:27 node-5 haproxy[9513]: proxy heat-api has no server available!
<129>Jul 24 12:39:27 node-5 haproxy[9513]: 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 24 12:39:27 node-5 haproxy[9513]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:27 node-5 haproxy[9513]: proxy heat-api-cfn has no server available!
<129>Jul 24 12:39:27 node-5 haproxy[9513]: Server heat-api-cloudwatch/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 24 12:39:27 node-5 haproxy[9513]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 12:39:27 node-5 haproxy[9513]: proxy heat-api-cloudwatch has no server available!
<27>Jul 24 12:39:29 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:29 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:29 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:29 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:29 node-5 multipathd: uevent trigger error
<27>Jul 24 12:39:29 node-5 multipathd: uevent trigger error
<27>Jul 24 12:40:06 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 12:40:06 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 24 12:40:35 node-5 multipathd: uevent trigger error
<27>Jul 24 12:40:35 node-5 multipathd: uevent trigger error
<27>Jul 24 12:40:35 node-5 multipathd: uevent trigger error
<27>Jul 24 12:40:35 node-5 multipathd: uevent trigger error
<27>Jul 24 12:40:35 node-5 multipathd: uevent trigger error
<27>Jul 24 12:40:37 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 12:41:15 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 24 12:41:17 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 24 12:42:53 node-5 multipathd: uevent trigger error
<27>Jul 24 12:42:53 node-5 multipathd: uevent trigger error
<27>Jul 24 12:42:53 node-5 multipathd: uevent trigger error
<27>Jul 24 12:42:53 node-5 multipathd: uevent trigger error
<27>Jul 24 12:42:53 node-5 multipathd: uevent trigger error
<27>Jul 24 12:42:53 node-5 multipathd: uevent trigger error
<27>Jul 24 12:46:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:46:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:46:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:46:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:46:18 node-5 multipathd: uevent trigger error
<43>Jul 24 12:47:36 node-5 apache2_error [Sun Jul 24 12:47:26.933953 2016] [mpm_worker:notice] [pid 8459:tid 140570091972480] AH00295: caught SIGTERM, shutting down
<43>Jul 24 12:47:36 node-5 apache2_error [Sun Jul 24 12:47:27.702270 2016] [mpm_worker:notice] [pid 7118:tid 140373448570752] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 12:47:36 node-5 apache2_error [Sun Jul 24 12:47:27.702318 2016] [core:notice] [pid 7118:tid 140373448570752] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 12:48:04 node-5 multipathd: uevent trigger error
<27>Jul 24 12:48:04 node-5 multipathd: uevent trigger error
<27>Jul 24 12:48:04 node-5 multipathd: uevent trigger error
<27>Jul 24 12:48:04 node-5 multipathd: uevent trigger error
<27>Jul 24 12:48:05 node-5 multipathd: uevent trigger error
<27>Jul 24 12:48:05 node-5 multipathd: uevent trigger error
<43>Jul 24 12:48:06 node-5 apache2_error [Sun Jul 24 12:47:59.625005 2016] [mpm_worker:notice] [pid 7118:tid 140373448570752] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 12:48:06 node-5 apache2_error [Sun Jul 24 12:47:59.634405 2016] [mpm_worker:warn] [pid 7118:tid 140373448570752] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 12:48:06 node-5 apache2_error [Sun Jul 24 12:47:59.638947 2016] [mpm_worker:notice] [pid 7118:tid 140373448570752] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 12:48:06 node-5 apache2_error [Sun Jul 24 12:47:59.638972 2016] [core:notice] [pid 7118:tid 140373448570752] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 12:49:02 node-5 multipathd: uevent trigger error
<27>Jul 24 12:49:02 node-5 multipathd: uevent trigger error
<27>Jul 24 12:49:02 node-5 multipathd: uevent trigger error
<27>Jul 24 12:49:02 node-5 multipathd: uevent trigger error
<27>Jul 24 12:49:02 node-5 multipathd: uevent trigger error
<27>Jul 24 12:50:13 node-5 multipathd: uevent trigger error
<27>Jul 24 12:50:13 node-5 multipathd: uevent trigger error
<27>Jul 24 12:50:13 node-5 multipathd: uevent trigger error
<27>Jul 24 12:50:13 node-5 multipathd: uevent trigger error
<27>Jul 24 12:50:13 node-5 multipathd: uevent trigger error
<27>Jul 24 12:55:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:55:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:55:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:55:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:55:26 node-5 multipathd: uevent trigger error
<27>Jul 24 12:57:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:57:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:57:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:57:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:57:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:57:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:58:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:58:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:58:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:58:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:58:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:58:41 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:18 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:27 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:32 node-5 multipathd: uevent trigger error
<27>Jul 24 12:59:32 node-5 multipathd: uevent trigger error
<43>Jul 24 13:00:27 node-5 apache2_error [Sun Jul 24 13:00:22.590925 2016] [mpm_worker:notice] [pid 7118:tid 140373448570752] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 13:00:27 node-5 apache2_error [Sun Jul 24 13:00:22.975755 2016] [mpm_worker:warn] [pid 7118:tid 140373448570752] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 13:00:27 node-5 apache2_error [Sun Jul 24 13:00:22.981553 2016] [mpm_worker:notice] [pid 7118:tid 140373448570752] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 13:00:27 node-5 apache2_error [Sun Jul 24 13:00:22.981727 2016] [core:notice] [pid 7118:tid 140373448570752] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 13:01:03 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:03 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:03 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:03 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:03 node-5 multipathd: uevent trigger error
<43>Jul 24 13:01:07 node-5 apache2_error [Sun Jul 24 13:00:59.642460 2016] [mpm_worker:notice] [pid 7118:tid 140373448570752] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 13:01:07 node-5 apache2_error [Sun Jul 24 13:01:00.027526 2016] [mpm_worker:warn] [pid 7118:tid 140373448570752] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 13:01:07 node-5 apache2_error [Sun Jul 24 13:01:00.035670 2016] [mpm_worker:notice] [pid 7118:tid 140373448570752] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 13:01:07 node-5 apache2_error [Sun Jul 24 13:01:00.035707 2016] [core:notice] [pid 7118:tid 140373448570752] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 13:01:21 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:21 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:21 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:21 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:21 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:37 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:37 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:37 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:59 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:59 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:59 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:59 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:59 node-5 multipathd: uevent trigger error
<27>Jul 24 13:01:59 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:00 node-5 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 24 13:02:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:53 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:53 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:53 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:53 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:53 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:57 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:57 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:57 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:57 node-5 multipathd: uevent trigger error
<27>Jul 24 13:02:57 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:09 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:09 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:09 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:10 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:10 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:10 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:26 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:26 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:26 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:26 node-5 multipathd: uevent trigger error
<27>Jul 24 13:03:26 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:16 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:16 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:16 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:16 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:16 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:16 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:30 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:30 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:30 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:30 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:30 node-5 multipathd: uevent trigger error
<11>Jul 24 13:04:40 node-5 liberasurecode[66346]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:40 node-5 liberasurecode[66346]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:40 node-5 liberasurecode[66346]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:40 node-5 liberasurecode[66346]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:40 node-5 liberasurecode[66370]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:40 node-5 liberasurecode[66370]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:40 node-5 liberasurecode[66370]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:40 node-5 liberasurecode[66370]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:42 node-5 liberasurecode[66760]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:42 node-5 liberasurecode[66760]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:42 node-5 liberasurecode[66760]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:42 node-5 liberasurecode[66760]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:47 node-5 liberasurecode[67840]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:47 node-5 liberasurecode[67840]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:47 node-5 liberasurecode[67840]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:47 node-5 liberasurecode[67840]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[67991]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[67991]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[67991]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[67991]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68101]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68101]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68101]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68101]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68327]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68327]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68327]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68327]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68341]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68341]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68341]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68341]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68374]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68374]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68374]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68403]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68403]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68403]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:04:48 node-5 liberasurecode[68403]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 13:04:55 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:55 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:55 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:55 node-5 multipathd: uevent trigger error
<27>Jul 24 13:04:55 node-5 multipathd: uevent trigger error
<27>Jul 24 13:05:00 node-5 multipathd: uevent trigger error
<27>Jul 24 13:05:00 node-5 multipathd: uevent trigger error
<27>Jul 24 13:05:00 node-5 multipathd: uevent trigger error
<27>Jul 24 13:05:00 node-5 multipathd: uevent trigger error
<27>Jul 24 13:05:00 node-5 multipathd: uevent trigger error
<11>Jul 24 13:05:01 node-5 liberasurecode[72954]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:05:01 node-5 liberasurecode[72954]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:05:01 node-5 liberasurecode[72954]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:05:01 node-5 liberasurecode[72954]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 13:06:06 node-5 multipathd: uevent trigger error
<27>Jul 24 13:06:06 node-5 multipathd: uevent trigger error
<27>Jul 24 13:06:06 node-5 multipathd: uevent trigger error
<27>Jul 24 13:06:06 node-5 multipathd: uevent trigger error
<27>Jul 24 13:06:06 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:10 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:10 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:10 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:10 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:10 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:28 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:28 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:28 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:28 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:28 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:33 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:33 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:33 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:33 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:33 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:48 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:55 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:55 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:55 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:55 node-5 multipathd: uevent trigger error
<27>Jul 24 13:08:55 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:00 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:00 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:00 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:00 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:00 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:04 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:04 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:04 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:04 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:04 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:09 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:09 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:09 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:09 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:09 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:14 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:18 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:18 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:18 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:18 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:18 node-5 multipathd: uevent trigger error
<27>Jul 24 13:09:52 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 13:09:52 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Jul 24 13:10:01 node-5 liberasurecode[121543]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:10:01 node-5 liberasurecode[121543]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:10:01 node-5 liberasurecode[121543]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 13:10:01 node-5 liberasurecode[121543]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
