Jul 29 04:08:25 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8382" x-info="http://www.rsyslog.com"] start
Jul 29 04:08:25 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 29 04:08:25 node-5 rsyslogd: rsyslogd's groupid changed to 104
Jul 29 04:08:25 node-5 rsyslogd: rsyslogd's userid changed to 101
Jul 29 04:08:25 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 29 04:08:25 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 29 04:08:25 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 29 04:08:25 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 29 04:08:25 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=2412558c-77ba-4a40-8577-74ac4cd89780 nomdmonddf nomdmonisw
Jul 29 04:08:25 node-5 kernel: [    0.000000] KERNEL supported cpus:
Jul 29 04:08:25 node-5 kernel: [    0.000000]   Intel GenuineIntel
Jul 29 04:08:25 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Jul 29 04:08:25 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Jul 29 04:08:25 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 29 04:08:25 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 29 04:08:25 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 29 04:08:25 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 29 04:08:25 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 29 04:08:25 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 29 04:08:25 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 29 04:08:25 node-5 kernel: [    0.000000] No AGP bridge found
Jul 29 04:08:25 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 29 04:08:25 node-5 kernel: [    0.000000] MTRR default type: write-back
Jul 29 04:08:25 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 29 04:08:25 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Jul 29 04:08:25 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 29 04:08:25 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 29 04:08:25 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 29 04:08:25 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 29 04:08:25 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 29 04:08:25 node-5 kernel: [    0.000000]   2 disabled
Jul 29 04:08:25 node-5 kernel: [    0.000000]   3 disabled
Jul 29 04:08:25 node-5 kernel: [    0.000000]   4 disabled
Jul 29 04:08:25 node-5 kernel: [    0.000000]   5 disabled
Jul 29 04:08:25 node-5 kernel: [    0.000000]   6 disabled
Jul 29 04:08:25 node-5 kernel: [    0.000000]   7 disabled
Jul 29 04:08:25 node-5 kernel: [    0.000000]   8 disabled
Jul 29 04:08:25 node-5 kernel: [    0.000000]   9 disabled
Jul 29 04:08:25 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 29 04:08:25 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 29 04:08:25 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 29 04:08:25 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 29 04:08:25 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 29 04:08:25 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Jul 29 04:08:25 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 29 04:08:25 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 29 04:08:25 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 29 04:08:25 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 29 04:08:25 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 29 04:08:25 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 29 04:08:25 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 29 04:08:25 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 29 04:08:25 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 29 04:08:25 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 29 04:08:25 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 29 04:08:25 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 29 04:08:25 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 29 04:08:25 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 29 04:08:25 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 29 04:08:25 node-5 kernel: [    0.000000] Zone ranges:
Jul 29 04:08:25 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] Movable zone start for each node
Jul 29 04:08:25 node-5 kernel: [    0.000000] Early memory node ranges
Jul 29 04:08:25 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 29 04:08:25 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 29 04:08:25 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 29 04:08:25 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 29 04:08:25 node-5 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 29 04:08:25 node-5 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 29 04:08:25 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 29 04:08:25 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 29 04:08:25 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 29 04:08:25 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 29 04:08:25 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 29 04:08:25 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 29 04:08:25 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 29 04:08:25 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 29 04:08:25 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 29 04:08:25 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 29 04:08:25 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 29 04:08:25 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 29 04:08:25 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 29 04:08:25 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 29 04:08:25 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 29 04:08:25 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 29 04:08:25 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 29 04:08:25 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 29 04:08:25 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 29 04:08:25 node-5 kernel: [    0.000000] Policy zone: Normal
Jul 29 04:08:25 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=2412558c-77ba-4a40-8577-74ac4cd89780 nomdmonddf nomdmonisw
Jul 29 04:08:25 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 29 04:08:25 node-5 kernel: [    0.000000] Checking aperture...
Jul 29 04:08:25 node-5 kernel: [    0.000000] No AGP bridge found
Jul 29 04:08:25 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 29 04:08:25 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 29 04:08:25 node-5 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 29 04:08:25 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 29 04:08:25 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 29 04:08:25 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 29 04:08:25 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 29 04:08:25 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 29 04:08:25 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 29 04:08:25 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 29 04:08:25 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 29 04:08:25 node-5 kernel: [    0.000000] console [tty0] enabled
Jul 29 04:08:25 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 29 04:08:25 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 29 04:08:25 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 29 04:08:25 node-5 kernel: [    0.000000] hpet clockevent registered
Jul 29 04:08:25 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 29 04:08:25 node-5 kernel: [    0.004000] tsc: Detected 3492.208 MHz processor
Jul 29 04:08:25 node-5 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.41 BogoMIPS (lpj=13968832)
Jul 29 04:08:25 node-5 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 29 04:08:25 node-5 kernel: [    0.000046] Security Framework initialized
Jul 29 04:08:25 node-5 kernel: [    0.000064] AppArmor: AppArmor initialized
Jul 29 04:08:25 node-5 kernel: [    0.000065] Yama: becoming mindful.
Jul 29 04:08:25 node-5 kernel: [    0.001451] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.006349] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.008276] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.008304] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.008584] Initializing cgroup subsys memory
Jul 29 04:08:25 node-5 kernel: [    0.008591] Initializing cgroup subsys devices
Jul 29 04:08:25 node-5 kernel: [    0.008593] Initializing cgroup subsys freezer
Jul 29 04:08:25 node-5 kernel: [    0.008595] Initializing cgroup subsys blkio
Jul 29 04:08:25 node-5 kernel: [    0.008596] Initializing cgroup subsys perf_event
Jul 29 04:08:25 node-5 kernel: [    0.008599] Initializing cgroup subsys hugetlb
Jul 29 04:08:25 node-5 kernel: [    0.008617] CPU: Physical Processor ID: 0
Jul 29 04:08:25 node-5 kernel: [    0.008619] CPU: Processor Core ID: 0
Jul 29 04:08:25 node-5 kernel: [    0.008622] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 29 04:08:25 node-5 kernel: [    0.008622] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 29 04:08:25 node-5 kernel: [    0.009316] mce: CPU supports 22 MCE banks
Jul 29 04:08:25 node-5 kernel: [    0.009343] CPU0: Thermal monitoring enabled (TM1)
Jul 29 04:08:25 node-5 kernel: [    0.009364] process: using mwait in idle threads
Jul 29 04:08:25 node-5 kernel: [    0.009367] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 29 04:08:25 node-5 kernel: [    0.009367] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 29 04:08:25 node-5 kernel: [    0.009367] tlb_flushall_shift: 6
Jul 29 04:08:25 node-5 kernel: [    0.009457] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 29 04:08:25 node-5 kernel: [    0.010182] ACPI: Core revision 20131115
Jul 29 04:08:25 node-5 kernel: [    0.022838] ACPI: All ACPI Tables successfully acquired
Jul 29 04:08:25 node-5 kernel: [    0.022999] ftrace: allocating 28617 entries in 112 pages
Jul 29 04:08:25 node-5 kernel: [    0.031821] dmar: Host address width 46
Jul 29 04:08:25 node-5 kernel: [    0.031823] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 29 04:08:25 node-5 kernel: [    0.031829] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 04:08:25 node-5 kernel: [    0.031831] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 29 04:08:25 node-5 kernel: [    0.031835] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 04:08:25 node-5 kernel: [    0.031836] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 29 04:08:25 node-5 kernel: [    0.031838] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 29 04:08:25 node-5 kernel: [    0.031839] dmar: ATSR flags: 0x0
Jul 29 04:08:25 node-5 kernel: [    0.031840] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 29 04:08:25 node-5 kernel: [    0.031841] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 29 04:08:25 node-5 kernel: [    0.031956] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 29 04:08:25 node-5 kernel: [    0.031958] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 04:08:25 node-5 kernel: [    0.031959] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 04:08:25 node-5 kernel: [    0.031960] HPET id 0 under DRHD base 0xc7ffc000
Jul 29 04:08:25 node-5 kernel: [    0.031961] Your BIOS is broken and requested that x2apic be disabled.
Jul 29 04:08:25 node-5 kernel: [    0.031961] This will slightly decrease performance.
Jul 29 04:08:25 node-5 kernel: [    0.031961] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 29 04:08:25 node-5 kernel: [    0.032395] Enabled IRQ remapping in xapic mode
Jul 29 04:08:25 node-5 kernel: [    0.032396] x2apic not enabled, IRQ remapping is in xapic mode
Jul 29 04:08:25 node-5 kernel: [    0.032400] Switched APIC routing to physical flat.
Jul 29 04:08:25 node-5 kernel: [    0.033021] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 29 04:08:25 node-5 kernel: [    0.072674] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 29 04:08:25 node-5 kernel: [    0.072679] TSC deadline timer enabled
Jul 29 04:08:25 node-5 kernel: [    0.072687] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 29 04:08:25 node-5 kernel: [    0.072693] ... version:                3
Jul 29 04:08:25 node-5 kernel: [    0.072694] ... bit width:              48
Jul 29 04:08:25 node-5 kernel: [    0.072695] ... generic registers:      4
Jul 29 04:08:25 node-5 kernel: [    0.072696] ... value mask:             0000ffffffffffff
Jul 29 04:08:25 node-5 kernel: [    0.072697] ... max period:             0000ffffffffffff
Jul 29 04:08:25 node-5 kernel: [    0.072698] ... fixed-purpose events:   3
Jul 29 04:08:25 node-5 kernel: [    0.072699] ... event mask:             000000070000000f
Jul 29 04:08:25 node-5 kernel: [    0.074117] x86: Booting SMP configuration:
Jul 29 04:08:25 node-5 kernel: [    0.088222] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 29 04:08:25 node-5 kernel: [    0.074119] .... node  #0, CPUs:        #1  #2  #3
Jul 29 04:08:25 node-5 kernel: [    0.116146] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 29 04:08:25 node-5 kernel: [    0.270306] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 29 04:08:25 node-5 kernel: [    0.325922] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 29 04:08:25 node-5 kernel: [    0.382980] x86: Booted up 2 nodes, 16 CPUs
Jul 29 04:08:25 node-5 kernel: [    0.382983] smpboot: Total of 16 processors activated (111763.19 BogoMIPS)
Jul 29 04:08:25 node-5 kernel: [    0.407900] devtmpfs: initialized
Jul 29 04:08:25 node-5 kernel: [    0.411014] EVM: security.selinux
Jul 29 04:08:25 node-5 kernel: [    0.411015] EVM: security.SMACK64
Jul 29 04:08:25 node-5 kernel: [    0.411016] EVM: security.ima
Jul 29 04:08:25 node-5 kernel: [    0.411017] EVM: security.capability
Jul 29 04:08:25 node-5 kernel: [    0.411079] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.411750] pinctrl core: initialized pinctrl subsystem
Jul 29 04:08:25 node-5 kernel: [    0.411813] regulator-dummy: no parameters
Jul 29 04:08:25 node-5 kernel: [    0.411844] RTC time:  4:07:45, date: 07/29/16
Jul 29 04:08:25 node-5 kernel: [    0.411876] NET: Registered protocol family 16
Jul 29 04:08:25 node-5 kernel: [    0.411960] cpuidle: using governor ladder
Jul 29 04:08:25 node-5 kernel: [    0.411961] cpuidle: using governor menu
Jul 29 04:08:25 node-5 kernel: [    0.411994] ACPI: bus type PCI registered
Jul 29 04:08:25 node-5 kernel: [    0.411996] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 29 04:08:25 node-5 kernel: [    0.412043] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 29 04:08:25 node-5 kernel: [    0.412046] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 29 04:08:25 node-5 kernel: [    0.425782] PCI: Using configuration type 1 for base access
Jul 29 04:08:25 node-5 kernel: [    0.426788] bio: create slab <bio-0> at 0
Jul 29 04:08:25 node-5 kernel: [    0.427065] ACPI: Added _OSI(Module Device)
Jul 29 04:08:25 node-5 kernel: [    0.427066] ACPI: Added _OSI(Processor Device)
Jul 29 04:08:25 node-5 kernel: [    0.427067] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 29 04:08:25 node-5 kernel: [    0.427069] ACPI: Added _OSI(Processor Aggregator Device)
Jul 29 04:08:25 node-5 kernel: [    0.439716] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 29 04:08:25 node-5 kernel: [    0.450354] ACPI: Interpreter enabled
Jul 29 04:08:25 node-5 kernel: [    0.450360] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 29 04:08:25 node-5 kernel: [    0.450364] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 29 04:08:25 node-5 kernel: [    0.450366] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 29 04:08:25 node-5 kernel: [    0.450373] ACPI: (supports S0 S4 S5)
Jul 29 04:08:25 node-5 kernel: [    0.450374] ACPI: Using IOAPIC for interrupt routing
Jul 29 04:08:25 node-5 kernel: [    0.450414] HEST: Table parsing has been initialized.
Jul 29 04:08:25 node-5 kernel: [    0.450417] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 29 04:08:25 node-5 kernel: [    0.450968] ACPI: No dock devices found.
Jul 29 04:08:25 node-5 kernel: [    0.462552] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 29 04:08:25 node-5 kernel: [    0.462557] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:25 node-5 kernel: [    0.462561] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 04:08:25 node-5 kernel: [    0.462590] PCI host bridge to bus 0000:ff
Jul 29 04:08:25 node-5 kernel: [    0.462592] pci_bus 0000:ff: root bus resource [bus ff]
Jul 29 04:08:25 node-5 kernel: [    0.462600] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.462639] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.462670] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.462706] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.462736] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.462766] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.462798] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.462827] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.462859] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.462888] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.462915] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.462943] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.462971] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.462997] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463024] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463051] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463080] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463108] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463135] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.463163] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463189] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.463215] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463241] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463271] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.463307] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463338] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463368] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463399] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463431] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463462] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463493] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463524] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463555] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463586] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463617] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463650] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463685] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463716] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463744] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463775] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463809] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463847] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463883] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463917] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463950] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.463979] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464009] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464040] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464074] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464105] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464136] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464166] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464195] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464224] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464254] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464285] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464316] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464373] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 29 04:08:25 node-5 kernel: [    0.464376] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:25 node-5 kernel: [    0.464378] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 04:08:25 node-5 kernel: [    0.464397] PCI host bridge to bus 0000:7f
Jul 29 04:08:25 node-5 kernel: [    0.464399] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 29 04:08:25 node-5 kernel: [    0.464404] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464431] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.464459] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464488] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464514] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.464538] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.464563] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464588] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464610] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464632] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464654] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464676] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464700] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464722] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464745] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464770] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464791] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464814] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464836] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.464860] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464881] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.464903] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464925] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.464951] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 04:08:25 node-5 kernel: [    0.464983] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465009] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465037] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465066] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465091] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465118] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465144] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465172] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465196] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465225] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465253] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465281] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465310] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465336] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465361] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465389] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465415] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465441] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465469] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465495] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465521] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465548] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465574] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465601] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465627] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465653] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465682] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 04:08:25 node-5 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 29 04:08:25 node-5 kernel: [    0.465705] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465728] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465752] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465778] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465807] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.465833] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.467074] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 29 04:08:25 node-5 kernel: [    0.467077] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:25 node-5 kernel: [    0.468203] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 04:08:25 node-5 kernel: [    0.468712] PCI host bridge to bus 0000:00
Jul 29 04:08:25 node-5 kernel: [    0.468714] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 29 04:08:25 node-5 kernel: [    0.468716] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 29 04:08:25 node-5 kernel: [    0.468717] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 29 04:08:25 node-5 kernel: [    0.468718] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 29 04:08:25 node-5 kernel: [    0.468720] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 29 04:08:25 node-5 kernel: [    0.468721] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 29 04:08:25 node-5 kernel: [    0.468723] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 29 04:08:25 node-5 kernel: [    0.468728] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 29 04:08:25 node-5 kernel: [    0.468810] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.468840] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.468882] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 29 04:08:25 node-5 kernel: [    0.468901] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.468930] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.468970] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 29 04:08:25 node-5 kernel: [    0.468988] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.469018] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.469060] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 29 04:08:25 node-5 kernel: [    0.469077] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.469147] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.469224] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.469298] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 04:08:25 node-5 kernel: [    0.469302] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 29 04:08:25 node-5 kernel: [    0.469387] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 29 04:08:25 node-5 kernel: [    0.469533] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 29 04:08:25 node-5 kernel: [    0.469551] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 29 04:08:25 node-5 kernel: [    0.469628] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.469681] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 29 04:08:25 node-5 kernel: [    0.469702] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.469758] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.469801] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 29 04:08:25 node-5 kernel: [    0.469827] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.469883] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.469926] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 29 04:08:25 node-5 kernel: [    0.469950] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 29 04:08:25 node-5 kernel: [    0.469968] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 29 04:08:25 node-5 kernel: [    0.470045] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.470094] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 29 04:08:25 node-5 kernel: [    0.470121] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 29 04:08:25 node-5 kernel: [    0.470369] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 29 04:08:25 node-5 kernel: [    0.470375] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 29 04:08:25 node-5 kernel: [    0.470381] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.470387] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.470394] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 29 04:08:25 node-5 kernel: [    0.470424] pci 0000:01:00.0: supports D1 D2
Jul 29 04:08:25 node-5 kernel: [    0.480511] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 04:08:25 node-5 kernel: [    0.480517] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 04:08:25 node-5 kernel: [    0.480521] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 04:08:25 node-5 kernel: [    0.480787] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.480835] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 29 04:08:25 node-5 kernel: [    0.488518] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 04:08:25 node-5 kernel: [    0.488524] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.488528] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:25 node-5 kernel: [    0.488612] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.488694] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.488770] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.488815] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 04:08:25 node-5 kernel: [    0.488819] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.488820] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:25 node-5 kernel: [    0.488877] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.489015] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.489070] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 04:08:25 node-5 kernel: [    0.489073] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.489075] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:25 node-5 kernel: [    0.489123] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.489243] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.489281] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.489404] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.489442] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.489562] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.489599] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 29 04:08:25 node-5 kernel: [    0.489718] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 29 04:08:25 node-5 kernel: [    0.489758] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 04:08:25 node-5 kernel: [    0.489761] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.489763] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:25 node-5 kernel: [    0.489823] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:25 node-5 kernel: [    0.489885] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.489937] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.489979] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 29 04:08:25 node-5 kernel: [    0.490086] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 29 04:08:25 node-5 kernel: [    0.490193] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 04:08:25 node-5 kernel: [    0.490195] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.490197] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 04:08:25 node-5 kernel: [    0.490253] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:25 node-5 kernel: [    0.490307] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.490358] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.490569] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 04:08:25 node-5 kernel: [    0.490572] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 04:08:25 node-5 kernel: [    0.490637] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:25 node-5 kernel: [    0.490690] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.490738] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.490949] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 04:08:25 node-5 kernel: [    0.490953] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 04:08:25 node-5 kernel: [    0.491020] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 29 04:08:25 node-5 kernel: [    0.491085] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.491137] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 29 04:08:25 node-5 kernel: [    0.491362] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 04:08:25 node-5 kernel: [    0.491366] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 04:08:25 node-5 kernel: [    0.491539] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 04:08:25 node-5 kernel: [    0.491578] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 04:08:25 node-5 kernel: [    0.491653] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 29 04:08:25 node-5 kernel: [    0.491672] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 29 04:08:25 node-5 kernel: [    0.491685] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 29 04:08:25 node-5 kernel: [    0.491698] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 29 04:08:25 node-5 kernel: [    0.491748] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 29 04:08:25 node-5 kernel: [    0.496526] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 04:08:25 node-5 kernel: [    0.496535] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 04:08:25 node-5 kernel: [    0.496587] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 29 04:08:25 node-5 kernel: [    0.497306] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 29 04:08:25 node-5 kernel: [    0.497309] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 04:08:25 node-5 kernel: [    0.497433] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 04:08:25 node-5 kernel: [    0.497541] PCI host bridge to bus 0000:80
Jul 29 04:08:25 node-5 kernel: [    0.497543] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 29 04:08:25 node-5 kernel: [    0.497544] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 29 04:08:25 node-5 kernel: [    0.497546] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 29 04:08:25 node-5 kernel: [    0.497554] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.497617] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.497685] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 04:08:25 node-5 kernel: [    0.497746] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 04:08:25 node-5 kernel: [    0.497751] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 29 04:08:25 node-5 kernel: [    0.497822] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 29 04:08:25 node-5 kernel: [    0.498122] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 29 04:08:25 node-5 kernel: [    0.498153] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 29 04:08:25 node-5 kernel: [    0.498182] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 29 04:08:25 node-5 kernel: [    0.498211] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 29 04:08:25 node-5 kernel: [    0.498240] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:25 node-5 kernel: [    0.498270] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:25 node-5 kernel: [    0.498300] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:25 node-5 kernel: [    0.498329] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 04:08:25 node-5 kernel: [    0.498415] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 29 04:08:25 node-5 kernel: [    0.498419] ACPI: \_SB_.UNC1: notify handler is installed
Jul 29 04:08:25 node-5 kernel: [    0.498420] ACPI: \_SB_.UNC0: notify handler is installed
Jul 29 04:08:25 node-5 kernel: [    0.498435] ACPI: \_SB_.PCI0: notify handler is installed
Jul 29 04:08:25 node-5 kernel: [    0.498488] ACPI: \_SB_.PCI1: notify handler is installed
Jul 29 04:08:25 node-5 kernel: [    0.498568] Found 4 acpi root devices
Jul 29 04:08:25 node-5 kernel: [    0.498678] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 29 04:08:25 node-5 kernel: [    0.498680] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 29 04:08:25 node-5 kernel: [    0.498681] vgaarb: loaded
Jul 29 04:08:25 node-5 kernel: [    0.498682] vgaarb: bridge control possible 0000:0c:00.0
Jul 29 04:08:25 node-5 kernel: [    0.498803] SCSI subsystem initialized
Jul 29 04:08:25 node-5 kernel: [    0.498866] libata version 3.00 loaded.
Jul 29 04:08:25 node-5 kernel: [    0.498882] ACPI: bus type USB registered
Jul 29 04:08:25 node-5 kernel: [    0.498892] usbcore: registered new interface driver usbfs
Jul 29 04:08:25 node-5 kernel: [    0.498897] usbcore: registered new interface driver hub
Jul 29 04:08:25 node-5 kernel: [    0.498920] usbcore: registered new device driver usb
Jul 29 04:08:25 node-5 kernel: [    0.499095] PCI: Using ACPI for IRQ routing
Jul 29 04:08:25 node-5 kernel: [    0.502699] PCI: pci_cache_line_size set to 64 bytes
Jul 29 04:08:25 node-5 kernel: [    0.502906] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 29 04:08:25 node-5 kernel: [    0.502907] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 29 04:08:25 node-5 kernel: [    0.502908] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 29 04:08:25 node-5 kernel: [    0.502974] NetLabel: Initializing
Jul 29 04:08:25 node-5 kernel: [    0.502976] NetLabel:  domain hash size = 128
Jul 29 04:08:25 node-5 kernel: [    0.502976] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 29 04:08:25 node-5 kernel: [    0.502986] NetLabel:  unlabeled traffic allowed by default
Jul 29 04:08:25 node-5 kernel: [    0.503042] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 29 04:08:25 node-5 kernel: [    0.503046] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 29 04:08:25 node-5 kernel: [    0.505104] Switched to clocksource hpet
Jul 29 04:08:25 node-5 kernel: [    0.509118] AppArmor: AppArmor Filesystem Enabled
Jul 29 04:08:25 node-5 kernel: [    0.509132] pnp: PnP ACPI init
Jul 29 04:08:25 node-5 kernel: [    0.509139] ACPI: bus type PNP registered
Jul 29 04:08:25 node-5 kernel: [    0.509248] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 29 04:08:25 node-5 kernel: [    0.509257] pnp 00:01: [dma 4]
Jul 29 04:08:25 node-5 kernel: [    0.509268] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 29 04:08:25 node-5 kernel: [    0.509295] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 29 04:08:25 node-5 kernel: [    0.509314] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 29 04:08:25 node-5 kernel: [    0.509331] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 29 04:08:25 node-5 kernel: [    0.509364] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 29 04:08:25 node-5 kernel: [    0.509415] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509417] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 29 04:08:25 node-5 kernel: [    0.509418] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509420] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509422] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509426] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509428] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 29 04:08:25 node-5 kernel: [    0.509429] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509431] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509432] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509434] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509435] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509437] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 29 04:08:25 node-5 kernel: [    0.509439] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 29 04:08:25 node-5 kernel: [    0.509522] pnp 00:07: [dma 0 disabled]
Jul 29 04:08:25 node-5 kernel: [    0.509550] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 04:08:25 node-5 kernel: [    0.509625] pnp 00:08: [dma 0 disabled]
Jul 29 04:08:25 node-5 kernel: [    0.509656] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 04:08:25 node-5 kernel: [    0.509706] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 29 04:08:25 node-5 kernel: [    0.510051] pnp: PnP ACPI: found 10 devices
Jul 29 04:08:25 node-5 kernel: [    0.510053] ACPI: bus type PNP unregistered
Jul 29 04:08:25 node-5 kernel: [    0.516379] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 04:08:25 node-5 kernel: [    0.516382] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 04:08:25 node-5 kernel: [    0.516385] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 04:08:25 node-5 kernel: [    0.516389] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 04:08:25 node-5 kernel: [    0.516391] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.516406] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516435] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 04:08:25 node-5 kernel: [    0.516449] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516478] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 04:08:25 node-5 kernel: [    0.516492] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 04:08:25 node-5 kernel: [    0.516521] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 04:08:25 node-5 kernel: [    0.516535] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 04:08:25 node-5 kernel: [    0.516564] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 04:08:25 node-5 kernel: [    0.516566] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.516580] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516609] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 04:08:25 node-5 kernel: [    0.516611] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.516625] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516654] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 04:08:25 node-5 kernel: [    0.516655] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.516658] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516662] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 04:08:25 node-5 kernel: [    0.516664] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.516666] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516670] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 04:08:25 node-5 kernel: [    0.516675] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 04:08:25 node-5 kernel: [    0.516683] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 04:08:25 node-5 kernel: [    0.516686] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 04:08:25 node-5 kernel: [    0.516693] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 29 04:08:25 node-5 kernel: [    0.516693] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 29 04:08:25 node-5 kernel: [    0.516694] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 29 04:08:25 node-5 kernel: [    0.516695] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 29 04:08:25 node-5 kernel: [    0.516696] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 29 04:08:25 node-5 kernel: [    0.516697] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 29 04:08:25 node-5 kernel: [    0.516698] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 29 04:08:25 node-5 kernel: [    0.516699] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 29 04:08:25 node-5 kernel: [    0.516700] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.516701] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516702] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.516702] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516703] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.516704] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516705] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.516706] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516707] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 29 04:08:25 node-5 kernel: [    0.516708] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516709] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 29 04:08:25 node-5 kernel: [    0.516710] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 29 04:08:25 node-5 kernel: [    0.516711] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 29 04:08:25 node-5 kernel: [    0.516712] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 29 04:08:25 node-5 kernel: [    0.516714] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 29 04:08:25 node-5 kernel: [    0.516715] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 29 04:08:25 node-5 kernel: [    0.516753] NET: Registered protocol family 2
Jul 29 04:08:25 node-5 kernel: [    0.517022] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.517367] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.517510] TCP: Hash tables configured (established 262144 bind 65536)
Jul 29 04:08:25 node-5 kernel: [    0.517553] TCP: reno registered
Jul 29 04:08:25 node-5 kernel: [    0.517583] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.517679] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.517829] NET: Registered protocol family 1
Jul 29 04:08:25 node-5 kernel: [    0.557199] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 29 04:08:25 node-5 kernel: [    0.557213] PCI: CLS 64 bytes, default 64
Jul 29 04:08:25 node-5 kernel: [    0.557274] Trying to unpack rootfs image as initramfs...
Jul 29 04:08:25 node-5 kernel: [    0.776207] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 29 04:08:25 node-5 kernel: [    0.776243] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 29 04:08:25 node-5 kernel: [    0.776245] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 29 04:08:25 node-5 kernel: [    0.776646] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776653] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776657] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776663] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776675] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776692] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776707] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776723] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776734] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776744] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776750] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776757] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776766] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776778] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776791] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776803] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 04:08:25 node-5 kernel: [    0.776921] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 29 04:08:25 node-5 kernel: [    0.776924] Scanning for low memory corruption every 60 seconds
Jul 29 04:08:25 node-5 kernel: [    0.777300] Initialise system trusted keyring
Jul 29 04:08:25 node-5 kernel: [    0.777355] audit: initializing netlink socket (disabled)
Jul 29 04:08:25 node-5 kernel: [    0.777371] type=2000 audit(1469765265.732:1): initialized
Jul 29 04:08:25 node-5 kernel: [    0.795287] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 29 04:08:25 node-5 kernel: [    0.796795] zbud: loaded
Jul 29 04:08:25 node-5 kernel: [    0.796929] VFS: Disk quotas dquot_6.5.2
Jul 29 04:08:25 node-5 kernel: [    0.796963] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 29 04:08:25 node-5 kernel: [    0.797341] fuse init (API version 7.22)
Jul 29 04:08:25 node-5 kernel: [    0.797400] msgmni has been set to 32768
Jul 29 04:08:25 node-5 kernel: [    0.797449] Key type big_key registered
Jul 29 04:08:25 node-5 kernel: [    0.797986] Key type asymmetric registered
Jul 29 04:08:25 node-5 kernel: [    0.797989] Asymmetric key parser 'x509' registered
Jul 29 04:08:25 node-5 kernel: [    0.798011] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 29 04:08:25 node-5 kernel: [    0.798078] io scheduler noop registered
Jul 29 04:08:25 node-5 kernel: [    0.798079] io scheduler deadline registered (default)
Jul 29 04:08:25 node-5 kernel: [    0.798097] io scheduler cfq registered
Jul 29 04:08:25 node-5 kernel: [    0.798493] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    0.798636] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    0.798749] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    0.798884] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    0.798994] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    0.799112] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    0.799494] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 29 04:08:25 node-5 kernel: [    0.799519] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 29 04:08:25 node-5 kernel: [    0.799536] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 29 04:08:25 node-5 kernel: [    0.799545] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799548] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799550] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:25 node-5 kernel: [    0.799556] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799557] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799559] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799560] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799562] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799563] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799565] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799566] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799567] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799569] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799570] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799571] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799574] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:25 node-5 kernel: [    0.799579] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799581] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:25 node-5 kernel: [    0.799596] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799599] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 29 04:08:25 node-5 kernel: [    0.799611] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799612] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 29 04:08:25 node-5 kernel: [    0.799615] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 29 04:08:25 node-5 kernel: [    0.799652] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 29 04:08:25 node-5 kernel: [    0.799658] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 29 04:08:25 node-5 kernel: [    0.799662] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 29 04:08:25 node-5 kernel: [    0.799672] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 29 04:08:25 node-5 kernel: [    0.799713] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 29 04:08:25 node-5 kernel: [    0.799714] vesafb: scrolling: redraw
Jul 29 04:08:25 node-5 kernel: [    0.799716] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 29 04:08:25 node-5 kernel: [    0.820411] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 29 04:08:25 node-5 kernel: [    0.828925] Console: switching to colour frame buffer device 80x30
Jul 29 04:08:25 node-5 kernel: [    0.837592] fb0: VESA VGA frame buffer device
Jul 29 04:08:25 node-5 kernel: [    0.837787] intel_idle: MWAIT substates: 0x2120
Jul 29 04:08:25 node-5 kernel: [    0.837789] intel_idle: v0.4 model 0x3F
Jul 29 04:08:25 node-5 kernel: [    0.837789] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 29 04:08:25 node-5 kernel: [    0.838012] ipmi message handler version 39.2
Jul 29 04:08:25 node-5 kernel: [    0.838295] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 29 04:08:25 node-5 kernel: [    0.838729] ACPI: AC Adapter [P111] (on-line)
Jul 29 04:08:25 node-5 kernel: [    0.844035] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 29 04:08:25 node-5 kernel: [    0.855158] ACPI: Power Button [PWRB]
Jul 29 04:08:25 node-5 kernel: [    0.860902] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 29 04:08:25 node-5 kernel: [    0.872521] ACPI: Power Button [PWRF]
Jul 29 04:08:25 node-5 kernel: [    0.890597] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 29 04:08:25 node-5 kernel: [    0.902270] pstore: Registered erst as persistent store backend
Jul 29 04:08:25 node-5 kernel: [    0.908443] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 29 04:08:25 node-5 kernel: [    0.920409] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 29 04:08:25 node-5 kernel: [    0.947138] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 29 04:08:25 node-5 kernel: [    0.980397] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 29 04:08:25 node-5 kernel: [    0.994509] Linux agpgart interface v0.103
Jul 29 04:08:25 node-5 kernel: [    1.002133] brd: module loaded
Jul 29 04:08:25 node-5 kernel: [    1.009163] loop: module loaded
Jul 29 04:08:25 node-5 kernel: [    1.015863] libphy: Fixed MDIO Bus: probed
Jul 29 04:08:25 node-5 kernel: [    1.022326] tun: Universal TUN/TAP device driver, 1.6
Jul 29 04:08:25 node-5 kernel: [    1.028833] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 29 04:08:25 node-5 kernel: [    1.035352] PPP generic driver version 2.4.2
Jul 29 04:08:25 node-5 kernel: [    1.041733] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 29 04:08:25 node-5 kernel: [    1.048186] ehci-pci: EHCI PCI platform driver
Jul 29 04:08:25 node-5 kernel: [    1.054704] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 29 04:08:25 node-5 kernel: [    1.061109] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 29 04:08:25 node-5 kernel: [    1.073624] ehci-pci 0000:00:1a.0: debug port 2
Jul 29 04:08:25 node-5 kernel: [    1.083836] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 29 04:08:25 node-5 kernel: [    1.083855] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 29 04:08:25 node-5 kernel: [    1.100602] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 29 04:08:25 node-5 kernel: [    1.106666] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 04:08:25 node-5 kernel: [    1.112817] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 04:08:25 node-5 kernel: [    1.124693] usb usb1: Product: EHCI Host Controller
Jul 29 04:08:25 node-5 kernel: [    1.130709] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 04:08:25 node-5 kernel: [    1.136746] usb usb1: SerialNumber: 0000:00:1a.0
Jul 29 04:08:25 node-5 kernel: [    1.142718] hub 1-0:1.0: USB hub found
Jul 29 04:08:25 node-5 kernel: [    1.148475] hub 1-0:1.0: 2 ports detected
Jul 29 04:08:25 node-5 kernel: [    1.154259] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 29 04:08:25 node-5 kernel: [    1.159839] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 29 04:08:25 node-5 kernel: [    1.170705] ehci-pci 0000:00:1d.0: debug port 2
Jul 29 04:08:25 node-5 kernel: [    1.180004] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 29 04:08:25 node-5 kernel: [    1.180007] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 29 04:08:25 node-5 kernel: [    1.196521] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 29 04:08:25 node-5 kernel: [    1.201710] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 04:08:25 node-5 kernel: [    1.207012] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 04:08:25 node-5 kernel: [    1.217630] usb usb2: Product: EHCI Host Controller
Jul 29 04:08:25 node-5 kernel: [    1.223133] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 04:08:25 node-5 kernel: [    1.228676] usb usb2: SerialNumber: 0000:00:1d.0
Jul 29 04:08:25 node-5 kernel: [    1.234206] hub 2-0:1.0: USB hub found
Jul 29 04:08:25 node-5 kernel: [    1.239563] hub 2-0:1.0: 2 ports detected
Jul 29 04:08:25 node-5 kernel: [    1.244849] ehci-platform: EHCI generic platform driver
Jul 29 04:08:25 node-5 kernel: [    1.250123] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 29 04:08:25 node-5 kernel: [    1.255504] ohci-pci: OHCI PCI platform driver
Jul 29 04:08:25 node-5 kernel: [    1.260858] ohci-platform: OHCI generic platform driver
Jul 29 04:08:25 node-5 kernel: [    1.266038] uhci_hcd: USB Universal Host Controller Interface driver
Jul 29 04:08:25 node-5 kernel: [    1.271369] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 29 04:08:25 node-5 kernel: [    1.464301] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 29 04:08:25 node-5 kernel: [    1.772099] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 29 04:08:25 node-5 kernel: [    1.788369] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 29 04:08:25 node-5 kernel: [    1.793969] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 04:08:25 node-5 kernel: [    1.799636] hub 1-1:1.0: USB hub found
Jul 29 04:08:25 node-5 kernel: [    1.805105] hub 1-1:1.0: 6 ports detected
Jul 29 04:08:25 node-5 kernel: [    1.919934] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 29 04:08:25 node-5 kernel: [    2.310004] i8042: No controller found
Jul 29 04:08:25 node-5 kernel: [    2.315527] mousedev: PS/2 mouse device common for all mice
Jul 29 04:08:25 node-5 kernel: [    2.321235] rtc_cmos 00:02: RTC can wake from S4
Jul 29 04:08:25 node-5 kernel: [    2.324360] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 29 04:08:25 node-5 kernel: [    2.324361] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 04:08:25 node-5 kernel: [    2.325120] hub 2-1:1.0: USB hub found
Jul 29 04:08:25 node-5 kernel: [    2.325355] hub 2-1:1.0: 8 ports detected
Jul 29 04:08:25 node-5 kernel: [    2.349453] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 29 04:08:25 node-5 kernel: [    2.355190] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 29 04:08:25 node-5 kernel: [    2.366486] device-mapper: uevent: version 1.0.3
Jul 29 04:08:25 node-5 kernel: [    2.372195] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 29 04:08:25 node-5 kernel: [    2.383561] ledtrig-cpu: registered to indicate activity on CPUs
Jul 29 04:08:25 node-5 kernel: [    2.389518] TCP: cubic registered
Jul 29 04:08:25 node-5 kernel: [    2.395391] NET: Registered protocol family 10
Jul 29 04:08:25 node-5 kernel: [    2.401486] NET: Registered protocol family 17
Jul 29 04:08:25 node-5 kernel: [    2.407259] Key type dns_resolver registered
Jul 29 04:08:25 node-5 kernel: [    2.413314] Loading compiled-in X.509 certificates
Jul 29 04:08:25 node-5 kernel: [    2.419520] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 29 04:08:25 node-5 kernel: [    2.431145] registered taskstats version 1
Jul 29 04:08:25 node-5 kernel: [    2.439210] Key type trusted registered
Jul 29 04:08:25 node-5 kernel: [    2.446823] Key type encrypted registered
Jul 29 04:08:25 node-5 kernel: [    2.452321] AppArmor: AppArmor sha1 policy hashing enabled
Jul 29 04:08:25 node-5 kernel: [    2.457830] IMA: No TPM chip found, activating TPM-bypass!
Jul 29 04:08:25 node-5 kernel: [    2.463926] regulator-dummy: disabling
Jul 29 04:08:25 node-5 kernel: [    2.469416]   Magic number: 8:671:111
Jul 29 04:08:25 node-5 kernel: [    2.475161] rtc_cmos 00:02: setting system clock to 2016-07-29 04:07:47 UTC (1469765267)
Jul 29 04:08:25 node-5 kernel: [    2.487689] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 29 04:08:25 node-5 kernel: [    2.493363] EDD information not available.
Jul 29 04:08:25 node-5 kernel: [    2.499001] PM: Hibernation image not present or could not be loaded.
Jul 29 04:08:25 node-5 kernel: [    2.499873] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 29 04:08:25 node-5 kernel: [    2.511213] Write protecting the kernel read-only data: 12288k
Jul 29 04:08:25 node-5 kernel: [    2.517509] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 29 04:08:25 node-5 kernel: [    2.530463] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 29 04:08:25 node-5 kernel: [    2.563216] device-mapper: multipath: version 1.6.0 loaded
Jul 29 04:08:25 node-5 kernel: [    2.571155] systemd-udevd[215]: starting version 204
Jul 29 04:08:25 node-5 kernel: [    2.590489] md: linear personality registered for level -1
Jul 29 04:08:25 node-5 kernel: [    2.599947] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 29 04:08:25 node-5 kernel: [    2.610394] md: multipath personality registered for level -4
Jul 29 04:08:25 node-5 kernel: [    2.618570] md: raid0 personality registered for level 0
Jul 29 04:08:25 node-5 kernel: [    2.626874] md: raid1 personality registered for level 1
Jul 29 04:08:25 node-5 kernel: [    2.637785] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 29 04:08:25 node-5 kernel: [    2.644162] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 29 04:08:25 node-5 kernel: [    2.653610] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 29 04:08:25 node-5 kernel: [    2.666198] 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 29 04:08:25 node-5 kernel: [    2.679518] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:25 node-5 kernel: [    2.686374] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.686380] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.686388] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.686393] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.686441] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.699583] raid6: sse2x1    2677 MB/s
Jul 29 04:08:25 node-5 kernel: [    2.706748] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 29 04:08:25 node-5 kernel: [    2.721495] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 29 04:08:25 node-5 kernel: [    2.734684] 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 29 04:08:25 node-5 kernel: [    2.748160] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:25 node-5 kernel: [    2.755021] megasas: FW now in Ready state
Jul 29 04:08:25 node-5 kernel: [    2.761715] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761721] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761724] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761728] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761732] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761739] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761743] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761747] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761751] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761754] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761758] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761762] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761765] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761769] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761772] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761776] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    2.761807] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 29 04:08:25 node-5 kernel: [    2.767499] raid6: sse2x2    2450 MB/s
Jul 29 04:08:25 node-5 kernel: [    2.835139] raid6: sse2x4    8721 MB/s
Jul 29 04:08:25 node-5 kernel: [    2.907077] raid6: avx2x1   14943 MB/s
Jul 29 04:08:25 node-5 kernel: [    2.979023] raid6: avx2x2   18889 MB/s
Jul 29 04:08:25 node-5 kernel: [    3.050954] raid6: avx2x4   21357 MB/s
Jul 29 04:08:25 node-5 kernel: [    3.056901] raid6: using algorithm avx2x4 (21357 MB/s)
Jul 29 04:08:25 node-5 kernel: [    3.062770] raid6: using avx2x2 recovery algorithm
Jul 29 04:08:25 node-5 kernel: [    3.068517] Switched to clocksource tsc
Jul 29 04:08:25 node-5 kernel: [    3.068525] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.068565] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.068605] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.068650] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.068728] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.077491] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 29 04:08:25 node-5 kernel: [    3.077492] 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 29 04:08:25 node-5 kernel: [    3.077493] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:25 node-5 kernel: [    3.077552] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.077588] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.077626] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.077664] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.077750] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.089016] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 29 04:08:25 node-5 kernel: [    3.089017] 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 29 04:08:25 node-5 kernel: [    3.089018] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 04:08:25 node-5 kernel: [    3.089077] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.089112] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.089151] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.089184] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.089269] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 04:08:25 node-5 kernel: [    3.095796] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 29 04:08:25 node-5 kernel: [    3.095797] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 29 04:08:25 node-5 kernel: [    3.095798] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 29 04:08:25 node-5 kernel: [    3.095799] usb 2-1.4: Manufacturer: Avocent
Jul 29 04:08:25 node-5 kernel: [    3.095799] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 29 04:08:25 node-5 kernel: [    3.152337] xor: automatically using best checksumming function:
Jul 29 04:08:25 node-5 kernel: [    3.188732] hidraw: raw HID events driver (C) Jiri Kosina
Jul 29 04:08:25 node-5 kernel: [    3.190834]    avx       : 36700.000 MB/sec
Jul 29 04:08:25 node-5 kernel: [    3.224165] async_tx: api initialized (async)
Jul 29 04:08:25 node-5 kernel: [    3.232063] usbcore: registered new interface driver usbhid
Jul 29 04:08:25 node-5 kernel: [    3.238382] usbhid: USB HID core driver
Jul 29 04:08:25 node-5 kernel: [    3.245688] 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 29 04:08:25 node-5 kernel: [    3.258827] 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 29 04:08:25 node-5 kernel: [    3.258829] md: raid6 personality registered for level 6
Jul 29 04:08:25 node-5 kernel: [    3.258829] md: raid5 personality registered for level 5
Jul 29 04:08:25 node-5 kernel: [    3.258829] md: raid4 personality registered for level 4
Jul 29 04:08:25 node-5 kernel: [    3.291060] 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 29 04:08:25 node-5 kernel: [    3.303532] 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 29 04:08:25 node-5 kernel: [    3.316560] md: raid10 personality registered for level 10
Jul 29 04:08:25 node-5 kernel: [    3.316568] 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 29 04:08:25 node-5 kernel: [    3.316619] 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 29 04:08:25 node-5 kernel: [    3.396173] multipathd (357): /proc/357/oom_adj is deprecated, please use /proc/357/oom_score_adj instead.
Jul 29 04:08:25 node-5 kernel: [    3.414671] megasas:IOC Init cmd success
Jul 29 04:08:25 node-5 kernel: [    3.466643] megasas: INIT adapter done
Jul 29 04:08:25 node-5 kernel: [    3.542573] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 29 04:08:25 node-5 kernel: [    3.549468] scsi0 : LSI SAS based MegaRAID driver
Jul 29 04:08:25 node-5 kernel: [    3.556894] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 04:08:25 node-5 kernel: [    3.581734] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 04:08:25 node-5 kernel: [    3.596877] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 29 04:08:25 node-5 kernel: [    3.603381] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 29 04:08:25 node-5 kernel: [    3.616939] sd 0:2:0:0: [sda] Write Protect is off
Jul 29 04:08:25 node-5 kernel: [    3.623676] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 29 04:08:25 node-5 kernel: [    3.623695] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 29 04:08:25 node-5 kernel: [    3.664965]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 29 04:08:25 node-5 kernel: [    3.671922] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 29 04:08:25 node-5 kernel: [    3.801875] random: lvm urandom read with 26 bits of entropy available
Jul 29 04:08:25 node-5 kernel: [    3.920526] bio: create slab <bio-1> at 1
Jul 29 04:08:25 node-5 kernel: [    4.681586] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 04:08:25 node-5 kernel: [    5.179832] init: plymouth-upstart-bridge main process (554) terminated with status 1
Jul 29 04:08:25 node-5 kernel: [    5.192044] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 04:08:25 node-5 kernel: [    5.336874] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 29 04:08:25 node-5 kernel: [    5.363271] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 29 04:08:25 node-5 kernel: [    5.496625] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 29 04:08:25 node-5 kernel: [    5.562471] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 29 04:08:25 node-5 kernel: [    5.674636] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 04:08:25 node-5 kernel: [    5.810067] random: nonblocking pool is initialized
Jul 29 04:08:25 node-5 kernel: [    5.877099] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 29 04:08:25 node-5 kernel: [    5.918309] XFS (dm-0): Mounting Filesystem
Jul 29 04:08:25 node-5 kernel: [    6.150033] XFS (dm-0): Ending clean mount
Jul 29 04:08:25 node-5 kernel: [    6.211455] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 04:08:25 node-5 kernel: [    6.244388] XFS (dm-1): Mounting Filesystem
Jul 29 04:08:25 node-5 kernel: [    6.352183] XFS (dm-1): Ending clean mount
Jul 29 04:08:25 node-5 kernel: [    8.351935] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 29 04:08:25 node-5 kernel: [    8.375613] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 29 04:08:25 node-5 kernel: [    8.506016] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 29 04:08:25 node-5 kernel: [    8.506021] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 29 04:08:25 node-5 kernel: [    8.506025] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 29 04:08:25 node-5 kernel: [    8.506028] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 29 04:08:25 node-5 kernel: [    8.539669] systemd-udevd[781]: starting version 204
Jul 29 04:08:25 node-5 kernel: [    8.740162] power_meter ACPI000D:00: Found ACPI power meter.
Jul 29 04:08:25 node-5 kernel: [    8.740178] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 29 04:08:25 node-5 kernel: [    8.771388] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 29 04:08:25 node-5 kernel: [    8.774193] wmi: Mapper loaded
Jul 29 04:08:25 node-5 kernel: [    8.780824] IPMI System Interface driver.
Jul 29 04:08:25 node-5 kernel: [    8.780857] ipmi_si: probing via ACPI
Jul 29 04:08:25 node-5 kernel: [    8.780875] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 29 04:08:25 node-5 kernel: [    8.780876] ipmi_si: Adding ACPI-specified kcs state machine
Jul 29 04:08:25 node-5 kernel: [    8.780884] ipmi_si: probing via SMBIOS
Jul 29 04:08:25 node-5 kernel: [    8.780885] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 04:08:25 node-5 kernel: [    8.780886] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 29 04:08:25 node-5 kernel: [    8.780888] ipmi_si: probing via SPMI
Jul 29 04:08:25 node-5 kernel: [    8.780888] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 04:08:25 node-5 kernel: [    8.780889] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 29 04:08:25 node-5 kernel: [    8.780890] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 29 04:08:25 node-5 kernel: [    8.786975] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 29 04:08:25 node-5 kernel: [    8.786980] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 04:08:25 node-5 kernel: [    8.786982] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 29 04:08:25 node-5 kernel: [    8.786984] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 04:08:25 node-5 kernel: [    8.786996] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 29 04:08:25 node-5 kernel: [    8.834542] systemd-udevd[802]: renamed network interface eth0 to enp6s0
Jul 29 04:08:25 node-5 kernel: [    8.858416] systemd-udevd[812]: renamed network interface eth1 to enp7s0
Jul 29 04:08:25 node-5 kernel: [    8.890364] systemd-udevd[801]: renamed network interface eth2 to enp8s0
Jul 29 04:08:25 node-5 kernel: [    8.930396] systemd-udevd[798]: renamed network interface eth3 to enp9s0
Jul 29 04:08:25 node-5 kernel: [    8.935895] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 29 04:08:25 node-5 kernel: [    8.935900] ipmi_si 00:09: IPMI kcs interface initialized
Jul 29 04:08:25 node-5 kernel: [    9.226178] type=1400 audit(1469765274.255:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1021 comm="apparmor_parser"
Jul 29 04:08:25 node-5 kernel: [    9.226335] type=1400 audit(1469765274.255:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1021 comm="apparmor_parser"
Jul 29 04:08:25 node-5 kernel: [    9.226465] type=1400 audit(1469765274.255:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1021 comm="apparmor_parser"
Jul 29 04:08:25 node-5 kernel: [    9.237232] type=1400 audit(1469765274.263:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1069 comm="apparmor_parser"
Jul 29 04:08:25 node-5 kernel: [    9.237372] type=1400 audit(1469765274.263:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1069 comm="apparmor_parser"
Jul 29 04:08:25 node-5 kernel: [    9.237493] type=1400 audit(1469765274.263:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1069 comm="apparmor_parser"
Jul 29 04:08:25 node-5 kernel: [    9.247366] type=1400 audit(1469765274.275:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1022 comm="apparmor_parser"
Jul 29 04:08:25 node-5 kernel: [    9.247504] type=1400 audit(1469765274.275:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1022 comm="apparmor_parser"
Jul 29 04:08:25 node-5 kernel: [    9.247628] type=1400 audit(1469765274.275:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1022 comm="apparmor_parser"
Jul 29 04:08:25 node-5 kernel: [    9.248927] type=1400 audit(1469765274.275:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1020 comm="apparmor_parser"
Jul 29 04:08:25 node-5 kernel: [    9.725214] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 29 04:08:25 node-5 kernel: [    9.726175] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 29 04:08:25 node-5 kernel: [    9.920627] enic 0000:06:00.0 enp6s0: Link UP
Jul 29 04:08:25 node-5 kernel: [    9.921051] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 29 04:08:25 node-5 kernel: [    9.921056] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 29 04:08:25 node-5 kernel: [   18.599453] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 29 04:08:26 node-5 failsafe: Failsafe of 120 seconds reached.
Jul 29 04:08:26 node-5 kernel: [   41.611220] init: failsafe main process (8409) killed by TERM signal
Jul 29 04:08:26 node-5 dbus[8447]: [system] AppArmor D-Bus mediation is enabled
Jul 29 04:08:27 node-5 kernel: [   41.847477] audit_printk_skb: 30 callbacks suppressed
Jul 29 04:08:27 node-5 kernel: [   41.847478] type=1400 audit(1469765307.094:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8537 comm="apparmor_parser"
Jul 29 04:08:27 node-5 kernel: [   41.850756] type=1400 audit(1469765307.098:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8536 comm="apparmor_parser"
Jul 29 04:08:27 node-5 kernel: [   41.850761] type=1400 audit(1469765307.098:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8536 comm="apparmor_parser"
Jul 29 04:08:27 node-5 kernel: [   41.850765] type=1400 audit(1469765307.098:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8536 comm="apparmor_parser"
Jul 29 04:08:27 node-5 kernel: [   41.850984] type=1400 audit(1469765307.098:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8536 comm="apparmor_parser"
Jul 29 04:08:27 node-5 kernel: [   41.850986] type=1400 audit(1469765307.098:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8536 comm="apparmor_parser"
Jul 29 04:08:27 node-5 kernel: [   41.851101] type=1400 audit(1469765307.098:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8536 comm="apparmor_parser"
Jul 29 04:08:27 node-5 kernel: [   41.913208] type=1400 audit(1469765307.158:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8539 comm="apparmor_parser"
Jul 29 04:08:27 node-5 anacron[8602]: Anacron 2.3 started on 2016-07-29
Jul 29 04:08:27 node-5 cron[8566]: (CRON) INFO (pidfile fd = 3)
Jul 29 04:08:27 node-5 anacron[8602]: Will run job `cron.daily' in 5 min.
Jul 29 04:08:27 node-5 anacron[8602]: Will run job `cron.weekly' in 10 min.
Jul 29 04:08:27 node-5 anacron[8602]: Will run job `cron.monthly' in 15 min.
Jul 29 04:08:27 node-5 anacron[8602]: Jobs will be executed sequentially
Jul 29 04:08:27 node-5 cron[8616]: (CRON) STARTUP (fork ok)
Jul 29 04:08:27 node-5 multipathd: path checkers start up
Jul 29 04:08:27 node-5 cron[8616]: (CRON) INFO (Running @reboot jobs)
Jul 29 04:08:27 node-5 postfix/master[8746]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 29 04:08:30 node-5 puppet-agent[8930]: Reopening log files
Jul 29 04:08:31 node-5 puppet-agent[8930]: Could not request certificate: Connection refused - connect(2)
Jul 29 04:08:42 node-5 puppet-user[9009]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 29 04:08:42 node-5 puppet-user[9009]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 29 04:08:42 node-5 puppet-user[9009]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 29 04:08:42 node-5 puppet-user[9009]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 29 04:08:42 node-5 puppet-user[9009]: Finished catalog run in 0.41 seconds
Jul 29 04:08:44 node-5 multipathd: uevent trigger error
Jul 29 04:08:44 node-5 puppet-user[9434]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 04:08:44 node-5 puppet-user[9434]: Compiled catalog for node-5.domain.tld in environment production in 0.09 seconds
Jul 29 04:08:44 node-5 puppet-user[9434]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 29 04:08:44 node-5 puppet-user[9434]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 29 04:08:44 node-5 puppet-user[9434]: (/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 29 04:08:44 node-5 puppet-user[9434]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 29 04:08:44 node-5 puppet-user[9434]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 29 04:08:44 node-5 puppet-user[9434]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 29 04:08:44 node-5 puppet-user[9434]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 29 04:08:44 node-5 puppet-user[9434]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 29 04:08:44 node-5 puppet-user[9434]: Finished catalog run in 0.07 seconds
Jul 29 04:08:45 node-5 puppet-user[9891]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 29 04:08:45 node-5 puppet-user[9891]: Compiled catalog for node-5.domain.tld in environment production in 0.08 seconds
Jul 29 04:08:45 node-5 puppet-user[9891]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 29 04:08:45 node-5 puppet-user[9891]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 29 04:08:45 node-5 puppet-user[9891]: Finished catalog run in 0.03 seconds
Jul 29 04:08:47 node-5 puppet-user[10349]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 29 04:08:47 node-5 puppet-user[10349]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 29 04:08:47 node-5 puppet-user[10349]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 29 04:08:47 node-5 puppet-user[10349]: Finished catalog run in 0.03 seconds
Jul 29 04:08:48 node-5 puppet-user[10800]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 29 04:08:49 node-5 puppet-user[10800]: Compiled catalog for node-5.domain.tld in environment production in 0.18 seconds
Jul 29 04:08:49 node-5 puppet-user[10800]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 29 04:08:49 node-5 puppet-user[10800]: (/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 29 04:08:49 node-5 puppet-user[10800]: Finished catalog run in 0.42 seconds
Jul 29 04:08:50 node-5 puppet-user[11305]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 29 04:08:51 node-5 puppet-user[11305]: Compiled catalog for node-5.domain.tld in environment production in 0.20 seconds
Jul 29 04:08:51 node-5 puppet-user[11305]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 29 04:08:51 node-5 puppet-user[11305]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 29 04:08:51 node-5 puppet-user[11305]: (/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 29 04:08:51 node-5 puppet-user[11305]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 29 04:08:51 node-5 puppet-user[11305]: Finished catalog run in 0.22 seconds
Jul 29 04:08:52 node-5 puppet-user[11872]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 29 04:08:52 node-5 puppet-user[11872]: Compiled catalog for node-5.domain.tld in environment production in 0.16 seconds
Jul 29 04:08:53 node-5 puppet-user[11872]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 29 04:08:53 node-5 kernel: [   67.783334] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 29 04:08:53 node-5 kernel: [   67.783382] 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 29 04:08:53 node-5 puppet-user[11872]: (/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 29 04:08:53 node-5 puppet-user[11872]: Finished catalog run in 0.05 seconds
Jul 29 04:08:54 node-5 puppet-user[12334]: (Scope(Class[main])) MODULAR: sync_time
Jul 29 04:08:54 node-5 puppet-user[12334]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 29 04:08:54 node-5 ntpdate[12745]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 29 04:09:01 node-5 ntpdate[12745]: adjust time server 10.20.0.2 offset 0.000508 sec
Jul 29 04:09:01 node-5 puppet-user[12334]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 29 04:09:01 node-5 puppet-user[12334]: Finished catalog run in 6.16 seconds
Jul 29 04:09:01 node-5 CRON[12901]: (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 29 04:09:07 node-5 puppet-user[13138]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 04:09:07 node-5 puppet-user[13138]: Compiled catalog for node-5.domain.tld in environment production in 0.07 seconds
Jul 29 04:09:08 node-5 puppet-user[13138]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 29 04:09:08 node-5 puppet-user[13138]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/opendaylight"]'
Jul 29 04:09:08 node-5 puppet-user[13138]: Finished catalog run in 0.06 seconds
Jul 29 04:09:09 node-5 puppet-user[13591]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 29 04:09:09 node-5 puppet-user[13591]: Compiled catalog for node-5.domain.tld in environment production in 0.67 seconds
Jul 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 puppet-user[13591]: (/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 29 04:09:10 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 04:09:10 node-5 nailgun-agent: D, [2016-07-29T04:09:01.559351 #12904] DEBUG -- : Sleep for 9 seconds before sending request
Jul 29 04:09:10 node-5 nailgun-agent: I, [2016-07-29T04:09:10.572000 #12904]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 04:09:10 node-5 nailgun-agent: D, [2016-07-29T04:09:10.949356 #12904] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 29 04:09:14 node-5 kernel: [   89.630472] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 04:09:15 node-5 puppet-agent[8930]: Could not run: SIGTERM
Jul 29 04:09:15 node-5 kernel: [   89.893202] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 29 04:09:15 node-5 ec2: 
Jul 29 04:09:15 node-5 ec2: #############################################################
Jul 29 04:09:15 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 29 04:09:15 node-5 ec2: 1024 8c:b8:6c:74:23:4c:4b:30:88:e7:52:c3:1c:52:93:45  root@node-5.domain.tld (DSA)
Jul 29 04:09:15 node-5 ec2: 256 be:59:40:a2:a5:7d:5f:b9:6a:40:18:9e:52:13:04:55  root@node-5.domain.tld (ECDSA)
Jul 29 04:09:15 node-5 ec2: 256 39:09:a6:8a:bd:e4:d9:db:5f:f0:24:b7:41:9b:bd:08  root@node-5.domain.tld (ED25519)
Jul 29 04:09:15 node-5 ec2: 2048 54:0b:9d:79:0a:30:78:fa:e7:35:e1:eb:8d:5a:b3:aa  root@node-5.domain.tld (RSA)
Jul 29 04:09:15 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 29 04:09:15 node-5 ec2: #############################################################
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.898307 #12904] DEBUG -- : Trying to find block devices
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.898439 #12904] DEBUG -- : Found block device: sda
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.898528 #12904] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.898555 #12904] DEBUG -- : Trying to get list of physical devices
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.898743 #12904] DEBUG -- : Getting udev properties for device: sda
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.900790 #12904] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc788
Jul 29 04:09:22 node-5 nailgun-agent: 0a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29396", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.900823 #12904] DEBUG -- : Trying to find out if device sda is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.900875 #12904] DEBUG -- : Device sda removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.900894 #12904] DEBUG -- : Device sda seems to be appropriate
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.901362 #12904] DEBUG -- : Getting udev properties for device: dm-0
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.903143 #12904] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-Elj4jg3mzyU3aBJOWZLLzMtesb0uDsZyXxm8J21RGK7zchsBenLUednfpLDF085D /dev/disk/by-uuid/53e82f38-a695-4ff4-8d7a-aac37b49e561 /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-Elj4jg3mzyU3aBJOWZLLzMtesb0uDsZyXxm8J21RGK7zchsBenLUednfpLDF085D", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"53e82f38-a695-4ff4-8d7a-aac37b49e561", "ID_FS_UUID_ENC"=>"53e82f38-a695-4ff4-8d7a-aac37b49e561", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"78227", "nomdmonddf"=>"1", "nom
Jul 29 04:09:22 node-5 nailgun-agent: dmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.903188 #12904] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.903246 #12904] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.903264 #12904] DEBUG -- : Device dm-0 seems to be appropriate
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.903280 #12904] DEBUG -- : Getting udev properties for device: dm-1
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.905239 #12904] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-F2ls6ZlhlpFwOhd3jkgnWvJCdsR4C4v0O4MhJJww51EHYeRcRbkqZU9X7gQKAmdV /dev/disk/by-uuid/4589669f-599a-4e8a-8b27-af1caa38177e /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-F2ls6ZlhlpFwOhd3jkgnWvJCdsR4C4v0O4MhJJww51EHYeRcRbkqZU9X7gQKAmdV", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4589669f-599a-4e8a-8b27-af1caa38177e", "ID_FS_UUID_ENC"=>"4589669f-599a-4e8a-8b27-af1caa38177e", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2
Jul 29 04:09:22 node-5 nailgun-agent: 4202", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.905323 #12904] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.905359 #12904] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.905375 #12904] DEBUG -- : Device dm-1 seems to be appropriate
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.905391 #12904] DEBUG -- : Getting udev properties for device: dm-2
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.907186 #12904] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-usGwuUBnL9wYDWvA1yRuDh3ELdtQTsapciIysEYbk0yejAX51EVycwnFqkhsseel /dev/disk/by-uuid/75d82cdb-f6ef-4f71-8fb6-7b5e4ad31c3f /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-usGwuUBnL9wYDWvA1yRuDh3ELdtQTsapciIysEYbk0yejAX51EVycwnFqkhsseel", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"75d82cdb-f6ef-4f71-8fb6-7b5e4ad31c3f", "ID_FS_UUID_ENC"=>"75d82cdb-f6ef-4f71-8fb6-7b5e4ad31c3f", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"21619", "nomdmon
Jul 29 04:09:22 node-5 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.907231 #12904] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.907265 #12904] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.907282 #12904] DEBUG -- : Device dm-2 seems to be appropriate
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.907298 #12904] DEBUG -- : Getting udev properties for device: dm-3
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.909104 #12904] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-9cR3VTd32q9HJ1TnJTo3jfVAFdMpNtEIacZSOEUSkNZM7Plnu2APaEjlfsus60MM /dev/disk/by-uuid/f752f036-2ba7-4f1f-9f74-ccf3b835343d /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-9cR3VTd32q9HJ1TnJTo3jfVAFdMpNtEIacZSOEUSkNZM7Plnu2APaEjlfsus60MM", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f752f036-2ba7-4f1f-9f74-ccf3b835343d", "ID_FS_UUID_ENC"=>"f752f036-2ba7-4f1f-9f74-ccf3b835343d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"28804", "nomdmonddf"=>"1",
Jul 29 04:09:22 node-5 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.909147 #12904] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.909188 #12904] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.909224 #12904] DEBUG -- : Device dm-3 seems to be appropriate
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.909239 #12904] DEBUG -- : Getting udev properties for device: dm-4
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.911032 #12904] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-xdfM2gnYdvRqfZBk1grPsdKxyJt0YLuGGtfOcudDCLxAkFBQbkMfbq0RdwkcgyII /dev/disk/by-uuid/2412558c-77ba-4a40-8577-74ac4cd89780 /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-xdfM2gnYdvRqfZBk1grPsdKxyJt0YLuGGtfOcudDCLxAkFBQbkMfbq0RdwkcgyII", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"2412558c-77ba-4a40-8577-74ac4cd89780", "ID_FS_UUID_ENC"=>"2412558c-77ba-4a40-8577-74ac4cd89780", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33263", "nomdmonddf"=>"1", "nom
Jul 29 04:09:22 node-5 nailgun-agent: dmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.911077 #12904] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.911111 #12904] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.911126 #12904] DEBUG -- : Device dm-4 seems to be appropriate
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.911141 #12904] DEBUG -- : Getting udev properties for device: dm-5
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.912981 #12904] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-xdfM2gnYdvRqfZBk1grPsdKxyJt0YLuGJqhOof1n4jwthRWepf2orlonoSnKqGMe /dev/disk/by-uuid/d8146945-17bc-4d09-b293-e63fd60369ae /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-xdfM2gnYdvRqfZBk1grPsdKxyJt0YLuGJqhOof1n4jwthRWepf2orlonoSnKqGMe", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"d8146945-17bc-4d09-b293-e63fd60369ae", "ID_FS_UUID_ENC"=>"d8146945-17bc-4d09-b293-e63fd60369ae", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"33635", "nomdmonddf"=>"1", "nomdmonisw
Jul 29 04:09:22 node-5 nailgun-agent: "=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.913012 #12904] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.913059 #12904] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.913111 #12904] DEBUG -- : Device dm-5 seems to be appropriate
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.913127 #12904] DEBUG -- : Getting udev properties for device: ram0
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.914742 #12904] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75843", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.914770 #12904] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.914808 #12904] DEBUG -- : Device ram0 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.914831 #12904] DEBUG -- : Getting udev properties for device: ram1
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.916445 #12904] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75858", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.916473 #12904] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.916515 #12904] DEBUG -- : Device ram1 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.916538 #12904] DEBUG -- : Getting udev properties for device: ram2
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.918370 #12904] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"76026", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.918409 #12904] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.918459 #12904] DEBUG -- : Device ram2 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.918511 #12904] DEBUG -- : Getting udev properties for device: ram3
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.920641 #12904] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"76048", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.920671 #12904] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.920712 #12904] DEBUG -- : Device ram3 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.920753 #12904] DEBUG -- : Getting udev properties for device: ram4
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.922353 #12904] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"76061", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.922383 #12904] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.922439 #12904] DEBUG -- : Device ram4 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.922461 #12904] DEBUG -- : Getting udev properties for device: ram5
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.924417 #12904] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"76090", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.924446 #12904] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.924535 #12904] DEBUG -- : Device ram5 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.924558 #12904] DEBUG -- : Getting udev properties for device: ram6
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.926222 #12904] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"76105", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.926251 #12904] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.926296 #12904] DEBUG -- : Device ram6 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.926336 #12904] DEBUG -- : Getting udev properties for device: ram7
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.927969 #12904] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"76117", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.928017 #12904] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.928059 #12904] DEBUG -- : Device ram7 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.928081 #12904] DEBUG -- : Getting udev properties for device: ram8
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.929847 #12904] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"76131", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.929876 #12904] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.929915 #12904] DEBUG -- : Device ram8 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.929963 #12904] DEBUG -- : Getting udev properties for device: ram9
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.931575 #12904] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"76144", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.931603 #12904] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.931653 #12904] DEBUG -- : Device ram9 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.931693 #12904] DEBUG -- : Getting udev properties for device: loop0
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.933292 #12904] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75701", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.933321 #12904] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.933359 #12904] DEBUG -- : Device loop0 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.933396 #12904] DEBUG -- : Getting udev properties for device: loop1
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.935165 #12904] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75718", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.935193 #12904] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.935241 #12904] DEBUG -- : Device loop1 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.935264 #12904] DEBUG -- : Getting udev properties for device: loop2
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.937050 #12904] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75735", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.937079 #12904] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.937115 #12904] DEBUG -- : Device loop2 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.937138 #12904] DEBUG -- : Getting udev properties for device: loop3
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.938802 #12904] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75751", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.938830 #12904] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.938888 #12904] DEBUG -- : Device loop3 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.938910 #12904] DEBUG -- : Getting udev properties for device: loop4
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.940481 #12904] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75782", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.940510 #12904] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.940550 #12904] DEBUG -- : Device loop4 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.940584 #12904] DEBUG -- : Getting udev properties for device: loop5
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.942571 #12904] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75796", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.942612 #12904] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.942647 #12904] DEBUG -- : Device loop5 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.942669 #12904] DEBUG -- : Getting udev properties for device: loop6
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.944285 #12904] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75813", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.944325 #12904] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.944375 #12904] DEBUG -- : Device loop6 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.944408 #12904] DEBUG -- : Getting udev properties for device: loop7
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.946217 #12904] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75829", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.946279 #12904] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.946334 #12904] DEBUG -- : Device loop7 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.946356 #12904] DEBUG -- : Getting udev properties for device: ram10
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.947987 #12904] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75878", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.948015 #12904] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.948077 #12904] DEBUG -- : Device ram10 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.948099 #12904] DEBUG -- : Getting udev properties for device: ram11
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.949832 #12904] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75899", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.949859 #12904] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.949912 #12904] DEBUG -- : Device ram11 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.949948 #12904] DEBUG -- : Getting udev properties for device: ram12
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.951552 #12904] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75919", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.951588 #12904] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.951636 #12904] DEBUG -- : Device ram12 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.951668 #12904] DEBUG -- : Getting udev properties for device: ram13
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.958179 #12904] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75940", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.958206 #12904] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.958247 #12904] DEBUG -- : Device ram13 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.958268 #12904] DEBUG -- : Getting udev properties for device: ram14
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.960072 #12904] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75956", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.960099 #12904] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.960143 #12904] DEBUG -- : Device ram14 removable parameter: "0"
Jul 29 04:09:22 node-5 nailgun-agent: D, [2016-07-29T04:09:22.960164 #12904] DEBUG -- : Getting udev properties for device: ram15
Jul 29 04:09:22 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.961873 #12904] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"75975", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.961900 #12904] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.961987 #12904] DEBUG -- : Device ram15 removable parameter: "0"
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962023 #12904] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962039 #12904] DEBUG -- : Block device seems to be physical data storage: sda
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962083 #12904] DEBUG -- : Found block device: dm-0
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962097 #12904] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962110 #12904] DEBUG -- : Found block device: dm-1
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962121 #12904] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962131 #12904] DEBUG -- : Found block device: dm-2
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962143 #12904] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962152 #12904] DEBUG -- : Found block device: dm-3
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962209 #12904] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962220 #12904] DEBUG -- : Found block device: dm-4
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962231 #12904] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962239 #12904] DEBUG -- : Found block device: dm-5
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962249 #12904] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962258 #12904] DEBUG -- : Found block device: ram0
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962268 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962276 #12904] DEBUG -- : Found block device: ram1
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962285 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962293 #12904] DEBUG -- : Found block device: ram2
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962354 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962363 #12904] DEBUG -- : Found block device: ram3
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962373 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962382 #12904] DEBUG -- : Found block device: ram4
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962392 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962400 #12904] DEBUG -- : Found block device: ram5
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962411 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962420 #12904] DEBUG -- : Found block device: ram6
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962430 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962479 #12904] DEBUG -- : Found block device: ram7
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962490 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962499 #12904] DEBUG -- : Found block device: ram8
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962509 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962517 #12904] DEBUG -- : Found block device: ram9
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962528 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962537 #12904] DEBUG -- : Found block device: loop0
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962548 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962556 #12904] DEBUG -- : Found block device: loop1
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962615 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962626 #12904] DEBUG -- : Found block device: loop2
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962636 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962644 #12904] DEBUG -- : Found block device: loop3
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962654 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962663 #12904] DEBUG -- : Found block device: loop4
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962673 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962681 #12904] DEBUG -- : Found block device: loop5
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962691 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962699 #12904] DEBUG -- : Found block device: loop6
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962756 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962766 #12904] DEBUG -- : Found block device: loop7
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962776 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962786 #12904] DEBUG -- : Found block device: ram10
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962796 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962805 #12904] DEBUG -- : Found block device: ram11
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962818 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962827 #12904] DEBUG -- : Found block device: ram12
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962836 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962882 #12904] DEBUG -- : Found block device: ram13
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962893 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962901 #12904] DEBUG -- : Found block device: ram14
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962910 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962918 #12904] DEBUG -- : Found block device: ram15
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962929 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:22.962958 #12904] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:23.034104 #12904] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 29 04:09:23 node-5 nailgun-agent: D, [2016-07-29T04:09:23.034156 #12904] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 29 04:09:28 node-5 puppet-user[13591]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 29 04:09:28 node-5 puppet-user[13591]: Finished catalog run in 18.20 seconds
Jul 29 04:09:30 node-5 puppet-user[15159]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 29 04:09:30 node-5 puppet-user[15159]: Compiled catalog for node-5.domain.tld in environment production in 0.13 seconds
Jul 29 04:09:35 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 04:09:35 node-5 puppet-user[15159]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.180978 #12904] DEBUG -- : Trying to find block devices
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181114 #12904] DEBUG -- : Found block device: sda
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181154 #12904] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181207 #12904] DEBUG -- : Block device seems to be physical data storage: sda
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181263 #12904] DEBUG -- : Found block device: dm-0
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181280 #12904] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181294 #12904] DEBUG -- : Found block device: dm-1
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181307 #12904] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181319 #12904] DEBUG -- : Found block device: dm-2
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181331 #12904] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181341 #12904] DEBUG -- : Found block device: dm-3
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181352 #12904] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181363 #12904] DEBUG -- : Found block device: dm-4
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181375 #12904] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181405 #12904] DEBUG -- : Found block device: dm-5
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181418 #12904] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181428 #12904] DEBUG -- : Found block device: ram0
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181439 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181449 #12904] DEBUG -- : Found block device: ram1
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181460 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181470 #12904] DEBUG -- : Found block device: ram2
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181481 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181490 #12904] DEBUG -- : Found block device: ram3
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181501 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181532 #12904] DEBUG -- : Found block device: ram4
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181544 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181554 #12904] DEBUG -- : Found block device: ram5
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181564 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181574 #12904] DEBUG -- : Found block device: ram6
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181585 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181594 #12904] DEBUG -- : Found block device: ram7
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181605 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181614 #12904] DEBUG -- : Found block device: ram8
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181625 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181667 #12904] DEBUG -- : Found block device: ram9
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181680 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181690 #12904] DEBUG -- : Found block device: loop0
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181701 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181710 #12904] DEBUG -- : Found block device: loop1
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181720 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181730 #12904] DEBUG -- : Found block device: loop2
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181741 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181750 #12904] DEBUG -- : Found block device: loop3
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181760 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181808 #12904] DEBUG -- : Found block device: loop4
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181820 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181830 #12904] DEBUG -- : Found block device: loop5
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181863 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181877 #12904] DEBUG -- : Found block device: loop6
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181888 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181899 #12904] DEBUG -- : Found block device: loop7
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181910 #12904] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181919 #12904] DEBUG -- : Found block device: ram10
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181929 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181970 #12904] DEBUG -- : Found block device: ram11
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181983 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.181992 #12904] DEBUG -- : Found block device: ram12
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.182002 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.182012 #12904] DEBUG -- : Found block device: ram13
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.182022 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.182032 #12904] DEBUG -- : Found block device: ram14
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.182042 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.182051 #12904] DEBUG -- : Found block device: ram15
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.182087 #12904] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.182123 #12904] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 29 04:09:35 node-5 nailgun-agent: D, [2016-07-29T04:09:35.394106 #12904] DEBUG -- : Response: status: 200 body: {"id": 5}
Jul 29 04:09:35 node-5 nailgun-agent: I, [2016-07-29T04:09:35.394503 #12904]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 29 04:10:01 node-5 CRON[17386]: (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 29 04:10:08 node-5 puppet-user[15159]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 29 04:10:08 node-5 puppet-user[15159]: Finished catalog run in 37.60 seconds
Jul 29 04:10:08 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 04:10:08 node-5 nailgun-agent: I, [2016-07-29T04:10:08.565943 #17389]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 04:10:10 node-5 puppet-user[17816]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 29 04:10:10 node-5 puppet-user[17816]: Compiled catalog for node-5.domain.tld in environment production in 0.57 seconds
Jul 29 04:10:10 node-5 puppet-user[17816]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 29 04:10:10 node-5 puppet-user[17816]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 29 04:10:10 node-5 puppet-user[17816]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 29 04:10:10 node-5 puppet-user[17816]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 29 04:10:10 node-5 puppet-user[17816]: Finished catalog run in 0.09 seconds
Jul 29 04:10:12 node-5 puppet-user[18355]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 29 04:10:13 node-5 puppet-user[18355]: Compiled catalog for node-5.domain.tld in environment production in 0.76 seconds
Jul 29 04:10:13 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 29 04:10:13 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 29 04:10:13 node-5 crontab[18796]: (root) LIST (root)
Jul 29 04:10:13 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 29 04:10:13 node-5 crontab[18797]: (root) REPLACE (root)
Jul 29 04:10:16 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/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 29 04:10:17 node-5 puppet-user[18355]: (/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 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/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 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 29 04:10:17 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/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 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/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 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/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 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/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 29 04:10:18 node-5 puppet-user[18355]: (/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 29 04:10:18 node-5 puppet-user[18355]: (/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 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/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 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/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 29 04:10:18 node-5 puppet-user[18355]: (/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 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 29 04:10:18 node-5 puppet-user[18355]: (/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 29 04:10:18 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8382" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 04:10:18 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 29 04:10:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:40 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:40 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:40 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:40 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:40 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:43 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:45 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:45 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:45 node-5 multipathd: uevent trigger error
<27>Jul 29 04:10:45 node-5 multipathd: uevent trigger error
<27>Jul 29 04:11:45 node-5 ntpdate[30191]: no servers can be used, exiting
<27>Jul 29 04:11:45 node-5 ntpdate[30310]: no servers can be used, exiting
<27>Jul 29 04:12:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:31 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:31 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:31 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:31 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-5 multipathd: uevent trigger error
<27>Jul 29 04:12:34 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:07 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:07 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:07 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:07 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:07 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:14 node-5 multipathd: uevent trigger error
<43>Jul 29 04:13:28 node-5 apache2_error [Fri Jul 29 04:13:26.589027 2016] [mpm_event:notice] [pid 12669:tid 139975452886912] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 04:13:28 node-5 apache2_error [Fri Jul 29 04:13:26.589198 2016] [core:notice] [pid 12669:tid 139975452886912] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:13:33 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:33 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:33 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:33 node-5 multipathd: uevent trigger error
<27>Jul 29 04:13:33 node-5 multipathd: uevent trigger error
<43>Jul 29 04:13:38 node-5 apache2_error [Fri Jul 29 04:13:29.821095 2016] [mpm_event:notice] [pid 12669:tid 139975452886912] AH00491: caught SIGTERM, shutting down
<43>Jul 29 04:13:38 node-5 apache2_error [Fri Jul 29 04:13:30.886766 2016] [mpm_worker:notice] [pid 13336:tid 139688580654976] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 04:13:38 node-5 apache2_error [Fri Jul 29 04:13:30.886797 2016] [core:notice] [pid 13336:tid 139688580654976] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 29 04:14:08 node-5 apache2_error [Fri Jul 29 04:14:07.019365 2016] [mpm_worker:notice] [pid 13336:tid 139688580654976] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:14:08 node-5 apache2_error [Fri Jul 29 04:14:07.026678 2016] [mpm_worker:warn] [pid 13336:tid 139688580654976] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:14:08 node-5 apache2_error [Fri Jul 29 04:14:07.027630 2016] [mpm_worker:notice] [pid 13336:tid 139688580654976] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 04:14:08 node-5 apache2_error [Fri Jul 29 04:14:07.027648 2016] [core:notice] [pid 13336:tid 139688580654976] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:14:10 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:10 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:10 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:10 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:10 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:44 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 29 04:14:48 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:48 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:48 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:48 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:48 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:59 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:59 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:59 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:59 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:59 node-5 multipathd: uevent trigger error
<27>Jul 29 04:14:59 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:07 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:07 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:07 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:07 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:07 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:12 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:12 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:12 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:12 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:12 node-5 multipathd: uevent trigger error
<129>Jul 29 04:15:15 node-5 haproxy[27832]: 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 29 04:15:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:17 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:20 node-5 multipathd: uevent trigger error
<129>Jul 29 04:15:23 node-5 haproxy[30261]: 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 29 04:15:24 node-5 haproxy[30265]: 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 29 04:15:26 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:26 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:26 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:26 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:26 node-5 multipathd: uevent trigger error
<129>Jul 29 04:15:28 node-5 haproxy[31437]: 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 29 04:15:29 node-5 haproxy[31441]: 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 29 04:15:29 node-5 haproxy[31441]: 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 29 04:15:31 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:31 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:31 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:31 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:31 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:31 node-5 multipathd: uevent trigger error
<129>Jul 29 04:15:33 node-5 haproxy[32644]: 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 29 04:15:34 node-5 haproxy[32651]: 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 29 04:15:34 node-5 haproxy[32651]: 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 29 04:15:34 node-5 haproxy[32651]: 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 29 04:15:35 node-5 haproxy[32651]: 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 29 04:15:36 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:36 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:36 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:36 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:36 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:36 node-5 multipathd: uevent trigger error
<129>Jul 29 04:15:39 node-5 haproxy[1428]: 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 29 04:15:39 node-5 haproxy[1428]: 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 29 04:15:39 node-5 haproxy[1428]: 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 29 04:15:39 node-5 haproxy[1428]: 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 29 04:15:40 node-5 haproxy[1428]: 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 29 04:15:40 node-5 haproxy[1428]: 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 29 04:15:42 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:42 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:42 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:42 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:42 node-5 multipathd: uevent trigger error
<129>Jul 29 04:15:42 node-5 haproxy[1428]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:42 node-5 haproxy[1428]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:42 node-5 haproxy[1428]: proxy aodh has no server available!
<129>Jul 29 04:15:44 node-5 haproxy[2619]: 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 29 04:15:44 node-5 haproxy[2619]: 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 29 04:15:44 node-5 haproxy[2619]: 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 29 04:15:45 node-5 haproxy[2623]: 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 29 04:15:45 node-5 haproxy[2623]: 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 29 04:15:45 node-5 haproxy[2623]: 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 29 04:15:46 node-5 haproxy[2623]: 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 29 04:15:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:47 node-5 multipathd: uevent trigger error
<129>Jul 29 04:15:47 node-5 haproxy[2623]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:47 node-5 haproxy[2623]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:47 node-5 haproxy[2623]: proxy aodh has no server available!
<129>Jul 29 04:15:47 node-5 haproxy[2623]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:47 node-5 haproxy[2623]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:47 node-5 haproxy[2623]: proxy ceilometer has no server available!
<129>Jul 29 04:15:49 node-5 haproxy[3793]: 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 29 04:15:49 node-5 haproxy[3793]: 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 29 04:15:50 node-5 haproxy[3798]: 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 29 04:15:50 node-5 haproxy[3798]: 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 29 04:15:50 node-5 haproxy[3798]: 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 29 04:15:50 node-5 haproxy[3798]: 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 29 04:15:51 node-5 haproxy[3798]: 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 29 04:15:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:52 node-5 multipathd: uevent trigger error
<129>Jul 29 04:15:52 node-5 haproxy[3798]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:52 node-5 haproxy[3798]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:52 node-5 haproxy[3798]: proxy aodh has no server available!
<129>Jul 29 04:15:52 node-5 haproxy[3798]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:53 node-5 haproxy[3798]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:53 node-5 haproxy[3798]: proxy ceilometer has no server available!
<129>Jul 29 04:15:55 node-5 haproxy[5010]: 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 29 04:15:55 node-5 haproxy[5010]: 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 29 04:15:55 node-5 haproxy[5010]: 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 29 04:15:55 node-5 haproxy[5010]: 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 29 04:15:55 node-5 haproxy[5010]: 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 29 04:15:56 node-5 haproxy[5010]: 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 29 04:15:56 node-5 haproxy[5010]: 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 29 04:15:56 node-5 haproxy[5010]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:56 node-5 haproxy[5010]: Server horizon/node-4 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 29 04:15:57 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:57 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:57 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:57 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:57 node-5 multipathd: uevent trigger error
<27>Jul 29 04:15:57 node-5 multipathd: uevent trigger error
<129>Jul 29 04:15:58 node-5 haproxy[5010]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:58 node-5 haproxy[5010]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:58 node-5 haproxy[5010]: proxy aodh has no server available!
<129>Jul 29 04:15:58 node-5 haproxy[5010]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:15:58 node-5 haproxy[5010]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:15:58 node-5 haproxy[5010]: proxy ceilometer has no server available!
<129>Jul 29 04:16:00 node-5 haproxy[6253]: 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 29 04:16:00 node-5 haproxy[6253]: 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 29 04:16:01 node-5 haproxy[6257]: 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 29 04:16:01 node-5 haproxy[6257]: 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 29 04:16:01 node-5 haproxy[6257]: 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 29 04:16:01 node-5 haproxy[6257]: 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 29 04:16:01 node-5 haproxy[6257]: 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 29 04:16:01 node-5 haproxy[6257]: 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 29 04:16:02 node-5 haproxy[6257]: 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 29 04:16:02 node-5 haproxy[6257]: 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 29 04:16:02 node-5 haproxy[6257]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:02 node-5 haproxy[6257]: Server horizon/node-4 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 29 04:16:03 node-5 haproxy[6257]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:16:03 node-5 multipathd: uevent trigger error
<129>Jul 29 04:16:03 node-5 haproxy[6257]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:03 node-5 haproxy[6257]: proxy glance-registry has no server available!
<27>Jul 29 04:16:03 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:03 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:03 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:03 node-5 multipathd: uevent trigger error
<129>Jul 29 04:16:03 node-5 haproxy[6257]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:04 node-5 haproxy[6257]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:04 node-5 haproxy[6257]: proxy aodh has no server available!
<129>Jul 29 04:16:04 node-5 haproxy[6257]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:04 node-5 haproxy[6257]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:04 node-5 haproxy[6257]: proxy ceilometer has no server available!
<27>Jul 29 04:16:04 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 29 04:16:06 node-5 haproxy[7706]: 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 29 04:16:06 node-5 haproxy[7706]: 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 29 04:16:06 node-5 haproxy[7706]: 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 29 04:16:06 node-5 haproxy[7706]: 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 29 04:16:07 node-5 haproxy[7710]: 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 29 04:16:07 node-5 haproxy[7710]: 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 29 04:16:07 node-5 haproxy[7710]: 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 29 04:16:07 node-5 haproxy[7710]: 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 29 04:16:07 node-5 haproxy[7710]: 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 29 04:16:07 node-5 haproxy[7710]: 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 29 04:16:07 node-5 haproxy[7710]: 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 29 04:16:07 node-5 haproxy[7710]: 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 29 04:16:08 node-5 haproxy[7710]: 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 29 04:16:08 node-5 haproxy[7710]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:08 node-5 haproxy[7710]: Server horizon/node-4 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 29 04:16:09 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:09 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:09 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:09 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:09 node-5 multipathd: uevent trigger error
<129>Jul 29 04:16:09 node-5 haproxy[7710]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:09 node-5 haproxy[7710]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:09 node-5 haproxy[7710]: proxy glance-registry has no server available!
<129>Jul 29 04:16:09 node-5 haproxy[7710]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:09 node-5 haproxy[7710]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:09 node-5 haproxy[7710]: proxy aodh has no server available!
<129>Jul 29 04:16:09 node-5 haproxy[7710]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:09 node-5 haproxy[7710]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:09 node-5 haproxy[7710]: proxy ceilometer has no server available!
<129>Jul 29 04:16:10 node-5 haproxy[7710]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:10 node-5 haproxy[7710]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:10 node-5 haproxy[7710]: proxy nova-novncproxy has no server available!
<129>Jul 29 04:16:11 node-5 haproxy[8956]: 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 29 04:16:11 node-5 haproxy[8956]: 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 29 04:16:11 node-5 haproxy[8956]: 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 29 04:16:12 node-5 haproxy[8962]: 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 29 04:16:12 node-5 haproxy[8962]: 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 29 04:16:12 node-5 haproxy[8962]: 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 29 04:16:12 node-5 haproxy[8962]: 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 29 04:16:12 node-5 haproxy[8962]: 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 29 04:16:12 node-5 haproxy[8962]: 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 29 04:16:12 node-5 haproxy[8962]: 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 29 04:16:12 node-5 haproxy[8962]: 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 29 04:16:13 node-5 haproxy[8962]: 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 29 04:16:13 node-5 haproxy[8962]: 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 29 04:16:13 node-5 haproxy[8962]: 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 29 04:16:13 node-5 haproxy[8962]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:13 node-5 haproxy[8962]: Server horizon/node-4 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 29 04:16:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:14 node-5 multipathd: uevent trigger error
<129>Jul 29 04:16:14 node-5 haproxy[8962]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:14 node-5 haproxy[8962]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:14 node-5 haproxy[8962]: proxy glance-registry has no server available!
<129>Jul 29 04:16:14 node-5 haproxy[8962]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:15 node-5 haproxy[8962]: Server aodh/node-4 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 29 04:16:15 node-5 haproxy[8962]: proxy aodh has no server available!
<129>Jul 29 04:16:15 node-5 haproxy[8962]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:15 node-5 haproxy[8962]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:15 node-5 haproxy[8962]: proxy ceilometer has no server available!
<129>Jul 29 04:16:15 node-5 haproxy[8962]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:15 node-5 haproxy[8962]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:15 node-5 haproxy[8962]: proxy nova-novncproxy has no server available!
<129>Jul 29 04:16:17 node-5 haproxy[10450]: 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 29 04:16:17 node-5 haproxy[10450]: 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 29 04:16:17 node-5 haproxy[10450]: 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 29 04:16:17 node-5 haproxy[10450]: 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 29 04:16:17 node-5 haproxy[10450]: 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 29 04:16:17 node-5 haproxy[10450]: 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 29 04:16:17 node-5 haproxy[10450]: 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 29 04:16:17 node-5 haproxy[10450]: 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 29 04:16:17 node-5 haproxy[10450]: 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 29 04:16:17 node-5 haproxy[10450]: 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 29 04:16:18 node-5 haproxy[10450]: 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 29 04:16:18 node-5 haproxy[10450]: 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 29 04:16:18 node-5 haproxy[10450]: 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 29 04:16:18 node-5 haproxy[10450]: 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 29 04:16:18 node-5 haproxy[10450]: 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 29 04:16:18 node-5 haproxy[10450]: 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 29 04:16:18 node-5 haproxy[10450]: 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 29 04:16:18 node-5 haproxy[10450]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:18 node-5 haproxy[10450]: Server horizon/node-4 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 29 04:16:19 node-5 multipathd: uevent trigger error
<129>Jul 29 04:16:19 node-5 haproxy[10450]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 04:16:19 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:19 node-5 multipathd: uevent trigger error
<129>Jul 29 04:16:19 node-5 haproxy[10450]: Server glance-registry/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:19 node-5 haproxy[10450]: proxy glance-registry has no server available!
<27>Jul 29 04:16:19 node-5 multipathd: uevent trigger error
<129>Jul 29 04:16:20 node-5 haproxy[10450]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:20 node-5 haproxy[10450]: Server aodh/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:20 node-5 haproxy[10450]: proxy aodh has no server available!
<129>Jul 29 04:16:20 node-5 haproxy[10450]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:20 node-5 haproxy[10450]: Server ceilometer/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:20 node-5 haproxy[10450]: proxy ceilometer has no server available!
<129>Jul 29 04:16:20 node-5 haproxy[10450]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:20 node-5 haproxy[10450]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:20 node-5 haproxy[10450]: proxy nova-novncproxy has no server available!
<27>Jul 29 04:16:23 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:23 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:23 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:23 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:25 node-5 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 29 04:16:26 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:26 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:26 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:26 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:26 node-5 multipathd: uevent trigger error
<129>Jul 29 04:16:26 node-5 haproxy[10450]: Server keystone-1/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:26 node-5 haproxy[10450]: Server keystone-1/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:26 node-5 haproxy[10450]: proxy keystone-1 has no server available!
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server keystone-2/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server keystone-2/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:27 node-5 haproxy[10450]: proxy keystone-2 has no server available!
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server nova-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server nova-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:27 node-5 haproxy[10450]: proxy nova-api has no server available!
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:27 node-5 haproxy[10450]: proxy nova-metadata-api has no server available!
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server cinder-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:27 node-5 haproxy[10450]: proxy cinder-api has no server available!
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server glance-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server glance-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:27 node-5 haproxy[10450]: proxy glance-api has no server available!
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server glance-glare/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server glance-glare/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:27 node-5 haproxy[10450]: proxy glance-glare has no server available!
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server neutron/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server neutron/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:27 node-5 haproxy[10450]: proxy neutron has no server available!
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:27 node-5 haproxy[10450]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:27 node-5 haproxy[10450]: proxy mysqld has no server available!
<129>Jul 29 04:16:28 node-5 haproxy[10450]: Server object-storage/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:28 node-5 haproxy[10450]: Server object-storage/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:28 node-5 haproxy[10450]: proxy object-storage has no server available!
<129>Jul 29 04:16:28 node-5 haproxy[10450]: Server heat-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:28 node-5 haproxy[10450]: Server heat-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:28 node-5 haproxy[10450]: proxy heat-api has no server available!
<129>Jul 29 04:16:28 node-5 haproxy[10450]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:28 node-5 haproxy[10450]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:28 node-5 haproxy[10450]: proxy heat-api-cfn has no server available!
<129>Jul 29 04:16:28 node-5 haproxy[10450]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 04:16:28 node-5 haproxy[10450]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 04:16:28 node-5 haproxy[10450]: proxy heat-api-cloudwatch has no server available!
<27>Jul 29 04:16:30 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:30 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:30 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:30 node-5 multipathd: uevent trigger error
<27>Jul 29 04:16:49 node-5 multipathd: uevent trigger error
<27>Jul 29 04:17:02 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 04:17:02 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 29 04:17:30 node-5 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-5 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-5 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-5 multipathd: uevent trigger error
<27>Jul 29 04:17:30 node-5 multipathd: uevent trigger error
<27>Jul 29 04:17:41 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 04:18:38 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 29 04:18:40 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 29 04:19:55 node-5 multipathd: uevent trigger error
<27>Jul 29 04:19:55 node-5 multipathd: uevent trigger error
<27>Jul 29 04:19:55 node-5 multipathd: uevent trigger error
<27>Jul 29 04:19:55 node-5 multipathd: uevent trigger error
<27>Jul 29 04:19:55 node-5 multipathd: uevent trigger error
<27>Jul 29 04:23:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:23:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:23:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:23:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:23:14 node-5 multipathd: uevent trigger error
<27>Jul 29 04:23:14 node-5 multipathd: uevent trigger error
<43>Jul 29 04:24:29 node-5 apache2_error [Fri Jul 29 04:24:22.653232 2016] [mpm_worker:notice] [pid 13336:tid 139688580654976] AH00295: caught SIGTERM, shutting down
<43>Jul 29 04:24:29 node-5 apache2_error [Fri Jul 29 04:24:23.402629 2016] [mpm_worker:notice] [pid 14444:tid 140237207820160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:24:29 node-5 apache2_error [Fri Jul 29 04:24:23.402663 2016] [core:notice] [pid 14444:tid 140237207820160] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 29 04:24:30 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<11>Jul 29 04:24:31 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<43>Jul 29 04:24:59 node-5 apache2_error [Fri Jul 29 04:24:55.376264 2016] [mpm_worker:notice] [pid 14444:tid 140237207820160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:24:59 node-5 apache2_error [Fri Jul 29 04:24:55.385332 2016] [mpm_worker:warn] [pid 14444:tid 140237207820160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:24:59 node-5 apache2_error [Fri Jul 29 04:24:55.391841 2016] [mpm_worker:notice] [pid 14444:tid 140237207820160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:24:59 node-5 apache2_error [Fri Jul 29 04:24:55.391873 2016] [core:notice] [pid 14444:tid 140237207820160] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:25:00 node-5 multipathd: uevent trigger error
<27>Jul 29 04:25:00 node-5 multipathd: uevent trigger error
<27>Jul 29 04:25:00 node-5 multipathd: uevent trigger error
<27>Jul 29 04:25:01 node-5 multipathd: uevent trigger error
<27>Jul 29 04:25:01 node-5 multipathd: uevent trigger error
<27>Jul 29 04:25:01 node-5 multipathd: uevent trigger error
<27>Jul 29 04:26:01 node-5 multipathd: uevent trigger error
<27>Jul 29 04:26:01 node-5 multipathd: uevent trigger error
<27>Jul 29 04:26:01 node-5 multipathd: uevent trigger error
<27>Jul 29 04:26:01 node-5 multipathd: uevent trigger error
<27>Jul 29 04:26:01 node-5 multipathd: uevent trigger error
<27>Jul 29 04:26:01 node-5 multipathd: uevent trigger error
<11>Jul 29 04:27:12 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<27>Jul 29 04:27:13 node-5 multipathd: uevent trigger error
<27>Jul 29 04:27:13 node-5 multipathd: uevent trigger error
<27>Jul 29 04:27:13 node-5 multipathd: uevent trigger error
<27>Jul 29 04:27:13 node-5 multipathd: uevent trigger error
<27>Jul 29 04:27:13 node-5 multipathd: uevent trigger error
<27>Jul 29 04:27:13 node-5 multipathd: uevent trigger error
<11>Jul 29 04:29:27 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<11>Jul 29 04:29:52 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<11>Jul 29 04:30:29 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<11>Jul 29 04:31:07 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<27>Jul 29 04:32:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:32:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:34:28 node-5 multipathd: uevent trigger error
<27>Jul 29 04:34:28 node-5 multipathd: uevent trigger error
<27>Jul 29 04:34:28 node-5 multipathd: uevent trigger error
<27>Jul 29 04:34:28 node-5 multipathd: uevent trigger error
<27>Jul 29 04:34:28 node-5 multipathd: uevent trigger error
<27>Jul 29 04:35:36 node-5 multipathd: uevent trigger error
<27>Jul 29 04:35:36 node-5 multipathd: uevent trigger error
<27>Jul 29 04:35:36 node-5 multipathd: uevent trigger error
<27>Jul 29 04:35:36 node-5 multipathd: uevent trigger error
<27>Jul 29 04:35:36 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:13 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:13 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:13 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:13 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:13 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:22 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:27 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:27 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:27 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:27 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:27 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:27 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:27 node-5 multipathd: uevent trigger error
<27>Jul 29 04:36:27 node-5 multipathd: uevent trigger error
<43>Jul 29 04:37:20 node-5 apache2_error [Fri Jul 29 04:37:14.555973 2016] [mpm_worker:notice] [pid 14444:tid 140237207820160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:37:20 node-5 apache2_error [Fri Jul 29 04:37:14.936812 2016] [mpm_worker:warn] [pid 14444:tid 140237207820160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:37:20 node-5 apache2_error [Fri Jul 29 04:37:14.939727 2016] [mpm_worker:notice] [pid 14444:tid 140237207820160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:37:20 node-5 apache2_error [Fri Jul 29 04:37:14.939738 2016] [core:notice] [pid 14444:tid 140237207820160] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 04:37:56 node-5 multipathd: uevent trigger error
<27>Jul 29 04:37:56 node-5 multipathd: uevent trigger error
<27>Jul 29 04:37:56 node-5 multipathd: uevent trigger error
<27>Jul 29 04:37:56 node-5 multipathd: uevent trigger error
<27>Jul 29 04:37:56 node-5 multipathd: uevent trigger error
<43>Jul 29 04:38:00 node-5 apache2_error [Fri Jul 29 04:37:51.897091 2016] [mpm_worker:notice] [pid 14444:tid 140237207820160] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 04:38:00 node-5 apache2_error [Fri Jul 29 04:37:52.284824 2016] [mpm_worker:warn] [pid 14444:tid 140237207820160] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 04:38:00 node-5 apache2_error [Fri Jul 29 04:37:52.293819 2016] [mpm_worker:notice] [pid 14444:tid 140237207820160] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 04:38:00 node-5 apache2_error [Fri Jul 29 04:37:52.293852 2016] [core:notice] [pid 14444:tid 140237207820160] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 29 04:38:28 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<27>Jul 29 04:38:37 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:37 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:37 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:37 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:42 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:42 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:42 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:42 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:38:47 node-5 multipathd: uevent trigger error
<11>Jul 29 04:39:51 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<27>Jul 29 04:40:15 node-5 multipathd: uevent trigger error
<27>Jul 29 04:40:15 node-5 multipathd: uevent trigger error
<27>Jul 29 04:40:15 node-5 multipathd: uevent trigger error
<27>Jul 29 04:40:15 node-5 multipathd: uevent trigger error
<27>Jul 29 04:40:15 node-5 multipathd: uevent trigger error
<11>Jul 29 04:40:23 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<11>Jul 29 04:40:56 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<27>Jul 29 04:41:03 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:03 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:03 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:03 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:03 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:15 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:15 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:15 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:15 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:15 node-5 multipathd: uevent trigger error
<11>Jul 29 04:41:25 node-5 liberasurecode[6748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-5 liberasurecode[6748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-5 liberasurecode[6748]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-5 liberasurecode[6748]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-5 liberasurecode[6772]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-5 liberasurecode[6772]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-5 liberasurecode[6772]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:25 node-5 liberasurecode[6772]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:27 node-5 liberasurecode[7488]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:27 node-5 liberasurecode[7488]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:27 node-5 liberasurecode[7488]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:27 node-5 liberasurecode[7488]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9654]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9654]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9654]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9654]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9690]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9690]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9690]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9690]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9758]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9758]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9758]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[9758]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10000]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10000]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10012]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10012]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10012]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10012]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10030]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10030]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10030]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10030]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10042]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10042]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10042]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:41:33 node-5 liberasurecode[10042]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 29 04:41:39 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:39 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:39 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:39 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:40 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:44 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:44 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:44 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:44 node-5 multipathd: uevent trigger error
<27>Jul 29 04:41:44 node-5 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-5 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-5 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-5 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-5 multipathd: uevent trigger error
<27>Jul 29 04:42:48 node-5 multipathd: uevent trigger error
<27>Jul 29 04:44:50 node-5 multipathd: uevent trigger error
<27>Jul 29 04:44:50 node-5 multipathd: uevent trigger error
<27>Jul 29 04:44:50 node-5 multipathd: uevent trigger error
<27>Jul 29 04:44:50 node-5 multipathd: uevent trigger error
<27>Jul 29 04:44:55 node-5 multipathd: uevent trigger error
<27>Jul 29 04:44:55 node-5 multipathd: uevent trigger error
<27>Jul 29 04:44:55 node-5 multipathd: uevent trigger error
<27>Jul 29 04:44:55 node-5 multipathd: uevent trigger error
<27>Jul 29 04:44:55 node-5 multipathd: uevent trigger error
<11>Jul 29 04:45:01 node-5 liberasurecode[7748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:45:01 node-5 liberasurecode[7748]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:45:01 node-5 liberasurecode[7748]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 04:45:01 node-5 liberasurecode[7748]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 29 04:45:08 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:08 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:08 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:08 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:21 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:21 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:21 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:21 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:21 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:25 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:25 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:25 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:25 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:25 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:38 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:38 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:38 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:38 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:43 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:43 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:43 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:43 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:43 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:47 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:45:52 node-5 multipathd: uevent trigger error
<27>Jul 29 04:46:33 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 29 04:46:33 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Jul 29 04:46:37 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
<11>Jul 29 04:47:39 node-5 epmd: epmd: node name already occupied rabbitmq-cli-14
