Jul 24 20:57:35 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8411" x-info="http://www.rsyslog.com"] start
Jul 24 20:57:35 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 24 20:57:35 node-5 rsyslogd: rsyslogd's groupid changed to 104
Jul 24 20:57:35 node-5 rsyslogd: rsyslogd's userid changed to 101
Jul 24 20:57:35 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 24 20:57:35 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 24 20:57:35 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 24 20:57:35 node-5 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 24 20:57:35 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=0bb60b1d-e65f-4582-acfb-f09607b839f4 nomdmonddf nomdmonisw
Jul 24 20:57:35 node-5 kernel: [    0.000000] KERNEL supported cpus:
Jul 24 20:57:35 node-5 kernel: [    0.000000]   Intel GenuineIntel
Jul 24 20:57:35 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Jul 24 20:57:35 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Jul 24 20:57:35 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 24 20:57:35 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 24 20:57:35 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 24 20:57:35 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 24 20:57:35 node-5 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 24 20:57:35 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 24 20:57:35 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 24 20:57:35 node-5 kernel: [    0.000000] No AGP bridge found
Jul 24 20:57:35 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 24 20:57:35 node-5 kernel: [    0.000000] MTRR default type: write-back
Jul 24 20:57:35 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 24 20:57:35 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Jul 24 20:57:35 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 24 20:57:35 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 24 20:57:35 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 24 20:57:35 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 24 20:57:35 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 24 20:57:35 node-5 kernel: [    0.000000]   2 disabled
Jul 24 20:57:35 node-5 kernel: [    0.000000]   3 disabled
Jul 24 20:57:35 node-5 kernel: [    0.000000]   4 disabled
Jul 24 20:57:35 node-5 kernel: [    0.000000]   5 disabled
Jul 24 20:57:35 node-5 kernel: [    0.000000]   6 disabled
Jul 24 20:57:35 node-5 kernel: [    0.000000]   7 disabled
Jul 24 20:57:35 node-5 kernel: [    0.000000]   8 disabled
Jul 24 20:57:35 node-5 kernel: [    0.000000]   9 disabled
Jul 24 20:57:35 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 24 20:57:35 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 24 20:57:35 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 24 20:57:35 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 24 20:57:35 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 24 20:57:35 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Jul 24 20:57:35 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 24 20:57:35 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 24 20:57:35 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 24 20:57:35 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 24 20:57:35 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 24 20:57:35 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 24 20:57:35 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 24 20:57:35 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 24 20:57:35 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 24 20:57:35 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 24 20:57:35 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 24 20:57:35 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 24 20:57:35 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 24 20:57:35 node-5 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 24 20:57:35 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 24 20:57:35 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 24 20:57:35 node-5 kernel: [    0.000000] Zone ranges:
Jul 24 20:57:35 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] Movable zone start for each node
Jul 24 20:57:35 node-5 kernel: [    0.000000] Early memory node ranges
Jul 24 20:57:35 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 24 20:57:35 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 24 20:57:35 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 24 20:57:35 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 24 20:57:35 node-5 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 24 20:57:35 node-5 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 24 20:57:35 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 24 20:57:35 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 24 20:57:35 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 24 20:57:35 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 24 20:57:35 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 24 20:57:35 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 24 20:57:35 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 24 20:57:35 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 24 20:57:35 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 24 20:57:35 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 24 20:57:35 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 24 20:57:35 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 24 20:57:35 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 24 20:57:35 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 24 20:57:35 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 24 20:57:35 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 24 20:57:35 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 24 20:57:35 node-5 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 24 20:57:35 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 24 20:57:35 node-5 kernel: [    0.000000] Policy zone: Normal
Jul 24 20:57:35 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=0bb60b1d-e65f-4582-acfb-f09607b839f4 nomdmonddf nomdmonisw
Jul 24 20:57:35 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 24 20:57:35 node-5 kernel: [    0.000000] Checking aperture...
Jul 24 20:57:35 node-5 kernel: [    0.000000] No AGP bridge found
Jul 24 20:57:35 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 24 20:57:35 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 24 20:57:35 node-5 kernel: [    0.000000] Memory: 32653320K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 24 20:57:35 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 24 20:57:35 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 24 20:57:35 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 24 20:57:35 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 24 20:57:35 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 24 20:57:35 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 24 20:57:35 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 24 20:57:35 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 24 20:57:35 node-5 kernel: [    0.000000] console [tty0] enabled
Jul 24 20:57:35 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 24 20:57:35 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 24 20:57:35 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 24 20:57:35 node-5 kernel: [    0.000000] hpet clockevent registered
Jul 24 20:57:35 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 24 20:57:35 node-5 kernel: [    0.004000] tsc: Detected 3491.613 MHz processor
Jul 24 20:57:35 node-5 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.22 BogoMIPS (lpj=13966452)
Jul 24 20:57:35 node-5 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 24 20:57:35 node-5 kernel: [    0.000043] Security Framework initialized
Jul 24 20:57:35 node-5 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 24 20:57:35 node-5 kernel: [    0.000062] Yama: becoming mindful.
Jul 24 20:57:35 node-5 kernel: [    0.001451] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.006251] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.008183] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.008211] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.008503] Initializing cgroup subsys memory
Jul 24 20:57:35 node-5 kernel: [    0.008511] Initializing cgroup subsys devices
Jul 24 20:57:35 node-5 kernel: [    0.008513] Initializing cgroup subsys freezer
Jul 24 20:57:35 node-5 kernel: [    0.008515] Initializing cgroup subsys blkio
Jul 24 20:57:35 node-5 kernel: [    0.008516] Initializing cgroup subsys perf_event
Jul 24 20:57:35 node-5 kernel: [    0.008519] Initializing cgroup subsys hugetlb
Jul 24 20:57:35 node-5 kernel: [    0.008538] CPU: Physical Processor ID: 0
Jul 24 20:57:35 node-5 kernel: [    0.008539] CPU: Processor Core ID: 0
Jul 24 20:57:35 node-5 kernel: [    0.008543] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 24 20:57:35 node-5 kernel: [    0.008543] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 24 20:57:35 node-5 kernel: [    0.009236] mce: CPU supports 22 MCE banks
Jul 24 20:57:35 node-5 kernel: [    0.009264] CPU0: Thermal monitoring enabled (TM1)
Jul 24 20:57:35 node-5 kernel: [    0.009285] process: using mwait in idle threads
Jul 24 20:57:35 node-5 kernel: [    0.009288] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 24 20:57:35 node-5 kernel: [    0.009288] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 24 20:57:35 node-5 kernel: [    0.009288] tlb_flushall_shift: 6
Jul 24 20:57:35 node-5 kernel: [    0.009377] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 24 20:57:35 node-5 kernel: [    0.010101] ACPI: Core revision 20131115
Jul 24 20:57:35 node-5 kernel: [    0.022794] ACPI: All ACPI Tables successfully acquired
Jul 24 20:57:35 node-5 kernel: [    0.022957] ftrace: allocating 28617 entries in 112 pages
Jul 24 20:57:35 node-5 kernel: [    0.031755] dmar: Host address width 46
Jul 24 20:57:35 node-5 kernel: [    0.031758] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 24 20:57:35 node-5 kernel: [    0.031763] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 20:57:35 node-5 kernel: [    0.031765] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 24 20:57:35 node-5 kernel: [    0.031769] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 20:57:35 node-5 kernel: [    0.031771] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 24 20:57:35 node-5 kernel: [    0.031772] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 24 20:57:35 node-5 kernel: [    0.031773] dmar: ATSR flags: 0x0
Jul 24 20:57:35 node-5 kernel: [    0.031774] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 24 20:57:35 node-5 kernel: [    0.031775] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 24 20:57:35 node-5 kernel: [    0.031890] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 24 20:57:35 node-5 kernel: [    0.031891] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 20:57:35 node-5 kernel: [    0.031892] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 20:57:35 node-5 kernel: [    0.031894] HPET id 0 under DRHD base 0xc7ffc000
Jul 24 20:57:35 node-5 kernel: [    0.031895] Your BIOS is broken and requested that x2apic be disabled.
Jul 24 20:57:35 node-5 kernel: [    0.031895] This will slightly decrease performance.
Jul 24 20:57:35 node-5 kernel: [    0.031895] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 24 20:57:35 node-5 kernel: [    0.032329] Enabled IRQ remapping in xapic mode
Jul 24 20:57:35 node-5 kernel: [    0.032330] x2apic not enabled, IRQ remapping is in xapic mode
Jul 24 20:57:35 node-5 kernel: [    0.032334] Switched APIC routing to physical flat.
Jul 24 20:57:35 node-5 kernel: [    0.032956] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 24 20:57:35 node-5 kernel: [    0.072603] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 24 20:57:35 node-5 kernel: [    0.072608] TSC deadline timer enabled
Jul 24 20:57:35 node-5 kernel: [    0.072625] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 24 20:57:35 node-5 kernel: [    0.072632] ... version:                3
Jul 24 20:57:35 node-5 kernel: [    0.072632] ... bit width:              48
Jul 24 20:57:35 node-5 kernel: [    0.072633] ... generic registers:      4
Jul 24 20:57:35 node-5 kernel: [    0.072634] ... value mask:             0000ffffffffffff
Jul 24 20:57:35 node-5 kernel: [    0.072635] ... max period:             0000ffffffffffff
Jul 24 20:57:35 node-5 kernel: [    0.072636] ... fixed-purpose events:   3
Jul 24 20:57:35 node-5 kernel: [    0.072637] ... event mask:             000000070000000f
Jul 24 20:57:35 node-5 kernel: [    0.074070] x86: Booting SMP configuration:
Jul 24 20:57:35 node-5 kernel: [    0.088172] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 24 20:57:35 node-5 kernel: [    0.074072] .... node  #0, CPUs:        #1  #2  #3
Jul 24 20:57:35 node-5 kernel: [    0.116083] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 24 20:57:35 node-5 kernel: [    0.270219] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 24 20:57:35 node-5 kernel: [    0.325827] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 24 20:57:35 node-5 kernel: [    0.382679] x86: Booted up 2 nodes, 16 CPUs
Jul 24 20:57:35 node-5 kernel: [    0.382683] smpboot: Total of 16 processors activated (111742.88 BogoMIPS)
Jul 24 20:57:35 node-5 kernel: [    0.407381] devtmpfs: initialized
Jul 24 20:57:35 node-5 kernel: [    0.410497] EVM: security.selinux
Jul 24 20:57:35 node-5 kernel: [    0.410499] EVM: security.SMACK64
Jul 24 20:57:35 node-5 kernel: [    0.410499] EVM: security.ima
Jul 24 20:57:35 node-5 kernel: [    0.410500] EVM: security.capability
Jul 24 20:57:35 node-5 kernel: [    0.410550] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.411242] pinctrl core: initialized pinctrl subsystem
Jul 24 20:57:35 node-5 kernel: [    0.411304] regulator-dummy: no parameters
Jul 24 20:57:35 node-5 kernel: [    0.411335] RTC time: 20:56:59, date: 07/24/16
Jul 24 20:57:35 node-5 kernel: [    0.411369] NET: Registered protocol family 16
Jul 24 20:57:35 node-5 kernel: [    0.411452] cpuidle: using governor ladder
Jul 24 20:57:35 node-5 kernel: [    0.411454] cpuidle: using governor menu
Jul 24 20:57:35 node-5 kernel: [    0.411487] ACPI: bus type PCI registered
Jul 24 20:57:35 node-5 kernel: [    0.411489] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 24 20:57:35 node-5 kernel: [    0.411535] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 24 20:57:35 node-5 kernel: [    0.411537] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 24 20:57:35 node-5 kernel: [    0.425270] PCI: Using configuration type 1 for base access
Jul 24 20:57:35 node-5 kernel: [    0.426269] bio: create slab <bio-0> at 0
Jul 24 20:57:35 node-5 kernel: [    0.426548] ACPI: Added _OSI(Module Device)
Jul 24 20:57:35 node-5 kernel: [    0.426550] ACPI: Added _OSI(Processor Device)
Jul 24 20:57:35 node-5 kernel: [    0.426551] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 24 20:57:35 node-5 kernel: [    0.426552] ACPI: Added _OSI(Processor Aggregator Device)
Jul 24 20:57:35 node-5 kernel: [    0.439242] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 24 20:57:35 node-5 kernel: [    0.450940] ACPI: Interpreter enabled
Jul 24 20:57:35 node-5 kernel: [    0.450946] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 24 20:57:35 node-5 kernel: [    0.450950] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 24 20:57:35 node-5 kernel: [    0.450952] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 24 20:57:35 node-5 kernel: [    0.450959] ACPI: (supports S0 S4 S5)
Jul 24 20:57:35 node-5 kernel: [    0.450960] ACPI: Using IOAPIC for interrupt routing
Jul 24 20:57:35 node-5 kernel: [    0.451001] HEST: Table parsing has been initialized.
Jul 24 20:57:35 node-5 kernel: [    0.451004] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 24 20:57:35 node-5 kernel: [    0.451555] ACPI: No dock devices found.
Jul 24 20:57:35 node-5 kernel: [    0.463151] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 24 20:57:35 node-5 kernel: [    0.463156] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 20:57:35 node-5 kernel: [    0.463159] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 20:57:35 node-5 kernel: [    0.463188] PCI host bridge to bus 0000:ff
Jul 24 20:57:35 node-5 kernel: [    0.463190] pci_bus 0000:ff: root bus resource [bus ff]
Jul 24 20:57:35 node-5 kernel: [    0.463198] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463237] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.463267] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463302] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463332] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.463361] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.463392] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463421] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463454] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463482] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463509] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463535] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463563] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463589] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463615] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463642] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463671] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463698] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463725] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.463753] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463778] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.463804] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463830] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463860] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.463894] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463925] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463955] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.463986] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464016] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464047] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464078] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464108] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464138] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464172] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464204] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464236] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464268] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464296] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464324] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464357] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464392] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464433] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464469] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464502] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464533] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464563] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464593] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464622] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464653] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464684] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464715] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464744] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464772] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464802] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464831] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464863] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464894] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.464951] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 24 20:57:35 node-5 kernel: [    0.464953] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 20:57:35 node-5 kernel: [    0.464956] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 20:57:35 node-5 kernel: [    0.464974] PCI host bridge to bus 0000:7f
Jul 24 20:57:35 node-5 kernel: [    0.464975] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 24 20:57:35 node-5 kernel: [    0.464980] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465007] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.465035] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465068] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465090] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.465114] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.465140] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465164] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465186] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465208] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465230] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465253] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465278] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465301] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465326] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465351] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465373] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465395] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465418] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.465441] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465463] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.465485] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465507] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465533] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 20:57:35 node-5 kernel: [    0.465566] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465591] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465617] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465645] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465669] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465696] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465722] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465749] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465774] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465800] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465827] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465854] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465883] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465908] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465932] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465959] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.465984] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466010] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466038] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466066] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466094] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466118] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466143] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466170] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466196] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466221] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466251] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466276] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466298] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466323] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466347] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466376] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.466402] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.467641] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 24 20:57:35 node-5 kernel: [    0.467645] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 20:57:35 node-5 kernel: [    0.468771] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 20:57:35 node-5 kernel: [    0.469284] PCI host bridge to bus 0000:00
Jul 24 20:57:35 node-5 kernel: [    0.469286] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 24 20:57:35 node-5 kernel: [    0.469288] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 24 20:57:35 node-5 kernel: [    0.469289] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 24 20:57:35 node-5 kernel: [    0.469290] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 24 20:57:35 node-5 kernel: [    0.469292] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 24 20:57:35 node-5 kernel: [    0.469293] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 24 20:57:35 node-5 kernel: [    0.469295] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 24 20:57:35 node-5 kernel: [    0.469300] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 24 20:57:35 node-5 kernel: [    0.469382] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.469412] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.469454] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 24 20:57:35 node-5 kernel: [    0.469472] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.469502] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.469542] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 24 20:57:35 node-5 kernel: [    0.469560] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.469589] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.469629] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 24 20:57:35 node-5 kernel: [    0.469646] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.469715] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.469792] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.469867] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 20:57:35 node-5 kernel: [    0.469872] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 24 20:57:35 node-5 kernel: [    0.469957] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 24 20:57:35 node-5 kernel: [    0.470105] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 24 20:57:35 node-5 kernel: [    0.470122] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 24 20:57:35 node-5 kernel: [    0.470200] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.470253] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 24 20:57:35 node-5 kernel: [    0.470274] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.470330] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.470373] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 24 20:57:35 node-5 kernel: [    0.470403] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.470459] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.470502] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 24 20:57:35 node-5 kernel: [    0.470525] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 24 20:57:35 node-5 kernel: [    0.470543] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 24 20:57:35 node-5 kernel: [    0.470620] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.470670] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 24 20:57:35 node-5 kernel: [    0.470695] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 24 20:57:35 node-5 kernel: [    0.470942] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 24 20:57:35 node-5 kernel: [    0.470948] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 24 20:57:35 node-5 kernel: [    0.470954] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.470960] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.470967] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 24 20:57:35 node-5 kernel: [    0.470997] pci 0000:01:00.0: supports D1 D2
Jul 24 20:57:35 node-5 kernel: [    0.481065] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 20:57:35 node-5 kernel: [    0.481071] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 20:57:35 node-5 kernel: [    0.481075] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 20:57:35 node-5 kernel: [    0.481339] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.481399] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 24 20:57:35 node-5 kernel: [    0.489063] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 20:57:35 node-5 kernel: [    0.489066] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.489067] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:35 node-5 kernel: [    0.489122] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.489190] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.489289] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.489334] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 20:57:35 node-5 kernel: [    0.489337] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.489339] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:35 node-5 kernel: [    0.489392] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.489514] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.489568] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 20:57:35 node-5 kernel: [    0.489570] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.489573] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:35 node-5 kernel: [    0.489622] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.489744] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.489786] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.489905] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.489941] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.490062] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.490097] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 24 20:57:35 node-5 kernel: [    0.490231] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:35 node-5 kernel: [    0.490273] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 20:57:35 node-5 kernel: [    0.490275] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.490277] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:35 node-5 kernel: [    0.490338] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 24 20:57:35 node-5 kernel: [    0.490401] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.490453] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.490495] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 24 20:57:35 node-5 kernel: [    0.490580] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 24 20:57:35 node-5 kernel: [    0.490685] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 20:57:35 node-5 kernel: [    0.490688] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.490690] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 20:57:35 node-5 kernel: [    0.490746] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 24 20:57:35 node-5 kernel: [    0.490799] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.490848] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.491058] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 20:57:35 node-5 kernel: [    0.491062] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 20:57:35 node-5 kernel: [    0.491126] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 24 20:57:35 node-5 kernel: [    0.491179] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.491252] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.491460] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 20:57:35 node-5 kernel: [    0.491464] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 20:57:35 node-5 kernel: [    0.491523] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 24 20:57:35 node-5 kernel: [    0.491584] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.491636] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 24 20:57:35 node-5 kernel: [    0.491861] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 20:57:35 node-5 kernel: [    0.491864] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 20:57:35 node-5 kernel: [    0.492039] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 20:57:35 node-5 kernel: [    0.492077] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 20:57:35 node-5 kernel: [    0.492155] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 24 20:57:35 node-5 kernel: [    0.492174] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 24 20:57:35 node-5 kernel: [    0.492187] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 24 20:57:35 node-5 kernel: [    0.492201] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 24 20:57:35 node-5 kernel: [    0.492251] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 24 20:57:35 node-5 kernel: [    0.497076] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 20:57:35 node-5 kernel: [    0.497085] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 20:57:35 node-5 kernel: [    0.497131] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 24 20:57:35 node-5 kernel: [    0.497620] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 24 20:57:35 node-5 kernel: [    0.497623] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 20:57:35 node-5 kernel: [    0.497743] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 20:57:35 node-5 kernel: [    0.497853] PCI host bridge to bus 0000:80
Jul 24 20:57:35 node-5 kernel: [    0.497855] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 24 20:57:35 node-5 kernel: [    0.497857] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 24 20:57:35 node-5 kernel: [    0.497858] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 24 20:57:35 node-5 kernel: [    0.497866] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.497929] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.497997] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 20:57:35 node-5 kernel: [    0.498060] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 20:57:35 node-5 kernel: [    0.498065] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 24 20:57:35 node-5 kernel: [    0.498136] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 24 20:57:35 node-5 kernel: [    0.498432] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 24 20:57:35 node-5 kernel: [    0.498464] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 24 20:57:35 node-5 kernel: [    0.498493] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 24 20:57:35 node-5 kernel: [    0.498522] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 24 20:57:35 node-5 kernel: [    0.498552] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 20:57:35 node-5 kernel: [    0.498581] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 20:57:35 node-5 kernel: [    0.498611] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 20:57:35 node-5 kernel: [    0.498641] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 20:57:35 node-5 kernel: [    0.498725] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 24 20:57:35 node-5 kernel: [    0.498729] ACPI: \_SB_.UNC1: notify handler is installed
Jul 24 20:57:35 node-5 kernel: [    0.498730] ACPI: \_SB_.UNC0: notify handler is installed
Jul 24 20:57:35 node-5 kernel: [    0.498745] ACPI: \_SB_.PCI0: notify handler is installed
Jul 24 20:57:35 node-5 kernel: [    0.498798] ACPI: \_SB_.PCI1: notify handler is installed
Jul 24 20:57:35 node-5 kernel: [    0.498878] Found 4 acpi root devices
Jul 24 20:57:35 node-5 kernel: [    0.498984] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 24 20:57:35 node-5 kernel: [    0.498986] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 24 20:57:35 node-5 kernel: [    0.498988] vgaarb: loaded
Jul 24 20:57:35 node-5 kernel: [    0.498989] vgaarb: bridge control possible 0000:0c:00.0
Jul 24 20:57:35 node-5 kernel: [    0.499105] SCSI subsystem initialized
Jul 24 20:57:35 node-5 kernel: [    0.499169] libata version 3.00 loaded.
Jul 24 20:57:35 node-5 kernel: [    0.499183] ACPI: bus type USB registered
Jul 24 20:57:35 node-5 kernel: [    0.499193] usbcore: registered new interface driver usbfs
Jul 24 20:57:35 node-5 kernel: [    0.499198] usbcore: registered new interface driver hub
Jul 24 20:57:35 node-5 kernel: [    0.499234] usbcore: registered new device driver usb
Jul 24 20:57:35 node-5 kernel: [    0.499392] PCI: Using ACPI for IRQ routing
Jul 24 20:57:35 node-5 kernel: [    0.502998] PCI: pci_cache_line_size set to 64 bytes
Jul 24 20:57:35 node-5 kernel: [    0.503223] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 24 20:57:35 node-5 kernel: [    0.503224] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 24 20:57:35 node-5 kernel: [    0.503225] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 24 20:57:35 node-5 kernel: [    0.503289] NetLabel: Initializing
Jul 24 20:57:35 node-5 kernel: [    0.503290] NetLabel:  domain hash size = 128
Jul 24 20:57:35 node-5 kernel: [    0.503291] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 24 20:57:35 node-5 kernel: [    0.503301] NetLabel:  unlabeled traffic allowed by default
Jul 24 20:57:35 node-5 kernel: [    0.503356] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 24 20:57:35 node-5 kernel: [    0.503360] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 24 20:57:35 node-5 kernel: [    0.505430] Switched to clocksource hpet
Jul 24 20:57:35 node-5 kernel: [    0.509955] AppArmor: AppArmor Filesystem Enabled
Jul 24 20:57:35 node-5 kernel: [    0.509994] pnp: PnP ACPI init
Jul 24 20:57:35 node-5 kernel: [    0.510007] ACPI: bus type PNP registered
Jul 24 20:57:35 node-5 kernel: [    0.510186] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 24 20:57:35 node-5 kernel: [    0.510197] pnp 00:01: [dma 4]
Jul 24 20:57:35 node-5 kernel: [    0.510216] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 24 20:57:35 node-5 kernel: [    0.510250] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 24 20:57:35 node-5 kernel: [    0.510275] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 24 20:57:35 node-5 kernel: [    0.510296] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 24 20:57:35 node-5 kernel: [    0.510343] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 24 20:57:35 node-5 kernel: [    0.510454] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510457] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 24 20:57:35 node-5 kernel: [    0.510459] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510460] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510462] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510463] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510467] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 24 20:57:35 node-5 kernel: [    0.510468] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510470] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510471] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510473] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510474] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510476] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 24 20:57:35 node-5 kernel: [    0.510478] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 24 20:57:35 node-5 kernel: [    0.510580] pnp 00:07: [dma 0 disabled]
Jul 24 20:57:35 node-5 kernel: [    0.510613] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 20:57:35 node-5 kernel: [    0.510694] pnp 00:08: [dma 0 disabled]
Jul 24 20:57:35 node-5 kernel: [    0.510730] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 20:57:35 node-5 kernel: [    0.510787] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 24 20:57:35 node-5 kernel: [    0.511228] pnp: PnP ACPI: found 10 devices
Jul 24 20:57:35 node-5 kernel: [    0.511230] ACPI: bus type PNP unregistered
Jul 24 20:57:35 node-5 kernel: [    0.517263] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 20:57:35 node-5 kernel: [    0.517267] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 20:57:35 node-5 kernel: [    0.517270] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 20:57:35 node-5 kernel: [    0.517275] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 20:57:35 node-5 kernel: [    0.517277] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.517291] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517320] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 20:57:35 node-5 kernel: [    0.517335] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517364] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 20:57:35 node-5 kernel: [    0.517378] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 20:57:35 node-5 kernel: [    0.517411] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 20:57:35 node-5 kernel: [    0.517429] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 20:57:35 node-5 kernel: [    0.517458] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 20:57:35 node-5 kernel: [    0.517460] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.517474] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517504] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 20:57:35 node-5 kernel: [    0.517505] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.517520] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517549] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 20:57:35 node-5 kernel: [    0.517551] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.517554] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517559] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 20:57:35 node-5 kernel: [    0.517560] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.517563] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517568] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 20:57:35 node-5 kernel: [    0.517574] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 20:57:35 node-5 kernel: [    0.517583] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 20:57:35 node-5 kernel: [    0.517587] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 20:57:35 node-5 kernel: [    0.517594] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 24 20:57:35 node-5 kernel: [    0.517595] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 24 20:57:35 node-5 kernel: [    0.517596] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 24 20:57:35 node-5 kernel: [    0.517597] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 24 20:57:35 node-5 kernel: [    0.517598] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 24 20:57:35 node-5 kernel: [    0.517598] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 24 20:57:35 node-5 kernel: [    0.517600] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 24 20:57:35 node-5 kernel: [    0.517600] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 24 20:57:35 node-5 kernel: [    0.517602] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.517602] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517604] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.517604] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517605] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.517606] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517607] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.517608] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517609] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 24 20:57:35 node-5 kernel: [    0.517610] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517611] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 24 20:57:35 node-5 kernel: [    0.517613] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 24 20:57:35 node-5 kernel: [    0.517614] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 24 20:57:35 node-5 kernel: [    0.517615] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 24 20:57:35 node-5 kernel: [    0.517618] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 24 20:57:35 node-5 kernel: [    0.517619] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 24 20:57:35 node-5 kernel: [    0.517659] NET: Registered protocol family 2
Jul 24 20:57:35 node-5 kernel: [    0.517957] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.518326] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.518494] TCP: Hash tables configured (established 262144 bind 65536)
Jul 24 20:57:35 node-5 kernel: [    0.518540] TCP: reno registered
Jul 24 20:57:35 node-5 kernel: [    0.518572] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.518685] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.518852] NET: Registered protocol family 1
Jul 24 20:57:35 node-5 kernel: [    0.557454] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 24 20:57:35 node-5 kernel: [    0.557462] PCI: CLS 64 bytes, default 64
Jul 24 20:57:35 node-5 kernel: [    0.557505] Trying to unpack rootfs image as initramfs...
Jul 24 20:57:35 node-5 kernel: [    0.778782] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 24 20:57:35 node-5 kernel: [    0.778844] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 24 20:57:35 node-5 kernel: [    0.778846] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 24 20:57:35 node-5 kernel: [    0.779235] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779243] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779250] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779257] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779265] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779273] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779279] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779284] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779290] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779297] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779305] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779312] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779318] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779324] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779330] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779336] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:35 node-5 kernel: [    0.779381] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 24 20:57:35 node-5 kernel: [    0.779383] Scanning for low memory corruption every 60 seconds
Jul 24 20:57:35 node-5 kernel: [    0.779675] Initialise system trusted keyring
Jul 24 20:57:35 node-5 kernel: [    0.779722] audit: initializing netlink socket (disabled)
Jul 24 20:57:35 node-5 kernel: [    0.779733] type=2000 audit(1469393819.732:1): initialized
Jul 24 20:57:35 node-5 kernel: [    0.797622] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 24 20:57:35 node-5 kernel: [    0.799114] zbud: loaded
Jul 24 20:57:35 node-5 kernel: [    0.799235] VFS: Disk quotas dquot_6.5.2
Jul 24 20:57:35 node-5 kernel: [    0.799274] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 24 20:57:35 node-5 kernel: [    0.799639] fuse init (API version 7.22)
Jul 24 20:57:35 node-5 kernel: [    0.799691] msgmni has been set to 32768
Jul 24 20:57:35 node-5 kernel: [    0.799734] Key type big_key registered
Jul 24 20:57:35 node-5 kernel: [    0.800225] Key type asymmetric registered
Jul 24 20:57:35 node-5 kernel: [    0.800227] Asymmetric key parser 'x509' registered
Jul 24 20:57:35 node-5 kernel: [    0.800249] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 24 20:57:35 node-5 kernel: [    0.800318] io scheduler noop registered
Jul 24 20:57:35 node-5 kernel: [    0.800320] io scheduler deadline registered (default)
Jul 24 20:57:35 node-5 kernel: [    0.800339] io scheduler cfq registered
Jul 24 20:57:35 node-5 kernel: [    0.800870] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    0.801025] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    0.801143] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    0.801272] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    0.801391] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    0.801486] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    0.801927] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 24 20:57:35 node-5 kernel: [    0.801969] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 24 20:57:35 node-5 kernel: [    0.801986] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 24 20:57:35 node-5 kernel: [    0.801998] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802000] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802003] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 24 20:57:35 node-5 kernel: [    0.802008] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802009] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802011] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802012] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802014] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802015] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802017] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802018] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802019] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802021] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802022] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802024] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802026] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 24 20:57:35 node-5 kernel: [    0.802039] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802041] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 24 20:57:35 node-5 kernel: [    0.802052] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802056] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 24 20:57:35 node-5 kernel: [    0.802066] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802067] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:35 node-5 kernel: [    0.802070] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 24 20:57:35 node-5 kernel: [    0.802096] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 24 20:57:35 node-5 kernel: [    0.802102] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 24 20:57:35 node-5 kernel: [    0.802106] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 24 20:57:35 node-5 kernel: [    0.802114] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 24 20:57:35 node-5 kernel: [    0.802152] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 24 20:57:35 node-5 kernel: [    0.802154] vesafb: scrolling: redraw
Jul 24 20:57:35 node-5 kernel: [    0.802155] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 24 20:57:35 node-5 kernel: [    0.822482] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 24 20:57:35 node-5 kernel: [    0.830979] Console: switching to colour frame buffer device 80x30
Jul 24 20:57:35 node-5 kernel: [    0.839649] fb0: VESA VGA frame buffer device
Jul 24 20:57:35 node-5 kernel: [    0.839849] intel_idle: MWAIT substates: 0x2120
Jul 24 20:57:35 node-5 kernel: [    0.839850] intel_idle: v0.4 model 0x3F
Jul 24 20:57:35 node-5 kernel: [    0.839851] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 24 20:57:35 node-5 kernel: [    0.840090] ipmi message handler version 39.2
Jul 24 20:57:35 node-5 kernel: [    0.840365] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 24 20:57:35 node-5 kernel: [    0.840796] ACPI: AC Adapter [P111] (on-line)
Jul 24 20:57:35 node-5 kernel: [    0.846026] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 24 20:57:35 node-5 kernel: [    0.857015] ACPI: Power Button [PWRB]
Jul 24 20:57:35 node-5 kernel: [    0.862812] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 24 20:57:35 node-5 kernel: [    0.874442] ACPI: Power Button [PWRF]
Jul 24 20:57:35 node-5 kernel: [    0.890972] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 24 20:57:35 node-5 kernel: [    0.902606] pstore: Registered erst as persistent store backend
Jul 24 20:57:35 node-5 kernel: [    0.908784] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 24 20:57:35 node-5 kernel: [    0.920701] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 24 20:57:35 node-5 kernel: [    0.947454] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 24 20:57:35 node-5 kernel: [    0.980840] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 24 20:57:35 node-5 kernel: [    0.994980] Linux agpgart interface v0.103
Jul 24 20:57:35 node-5 kernel: [    1.002666] brd: module loaded
Jul 24 20:57:35 node-5 kernel: [    1.009704] loop: module loaded
Jul 24 20:57:35 node-5 kernel: [    1.016444] libphy: Fixed MDIO Bus: probed
Jul 24 20:57:35 node-5 kernel: [    1.022941] tun: Universal TUN/TAP device driver, 1.6
Jul 24 20:57:35 node-5 kernel: [    1.029424] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 24 20:57:35 node-5 kernel: [    1.035987] PPP generic driver version 2.4.2
Jul 24 20:57:35 node-5 kernel: [    1.042396] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 24 20:57:35 node-5 kernel: [    1.048847] ehci-pci: EHCI PCI platform driver
Jul 24 20:57:35 node-5 kernel: [    1.055394] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 24 20:57:35 node-5 kernel: [    1.061798] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 24 20:57:35 node-5 kernel: [    1.074448] ehci-pci 0000:00:1a.0: debug port 2
Jul 24 20:57:35 node-5 kernel: [    1.084713] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 24 20:57:35 node-5 kernel: [    1.084732] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 24 20:57:35 node-5 kernel: [    1.100915] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 24 20:57:35 node-5 kernel: [    1.106989] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 20:57:35 node-5 kernel: [    1.113154] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 20:57:35 node-5 kernel: [    1.125049] usb usb1: Product: EHCI Host Controller
Jul 24 20:57:35 node-5 kernel: [    1.131066] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 20:57:35 node-5 kernel: [    1.137118] usb usb1: SerialNumber: 0000:00:1a.0
Jul 24 20:57:35 node-5 kernel: [    1.143064] hub 1-0:1.0: USB hub found
Jul 24 20:57:35 node-5 kernel: [    1.148831] hub 1-0:1.0: 2 ports detected
Jul 24 20:57:35 node-5 kernel: [    1.154641] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 24 20:57:35 node-5 kernel: [    1.160224] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 24 20:57:35 node-5 kernel: [    1.171130] ehci-pci 0000:00:1d.0: debug port 2
Jul 24 20:57:35 node-5 kernel: [    1.180422] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 24 20:57:35 node-5 kernel: [    1.180425] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 24 20:57:35 node-5 kernel: [    1.196833] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 24 20:57:35 node-5 kernel: [    1.202114] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 20:57:35 node-5 kernel: [    1.207491] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 20:57:35 node-5 kernel: [    1.218203] usb usb2: Product: EHCI Host Controller
Jul 24 20:57:35 node-5 kernel: [    1.223742] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 20:57:35 node-5 kernel: [    1.229359] usb usb2: SerialNumber: 0000:00:1d.0
Jul 24 20:57:35 node-5 kernel: [    1.234965] hub 2-0:1.0: USB hub found
Jul 24 20:57:35 node-5 kernel: [    1.240383] hub 2-0:1.0: 2 ports detected
Jul 24 20:57:35 node-5 kernel: [    1.245792] ehci-platform: EHCI generic platform driver
Jul 24 20:57:35 node-5 kernel: [    1.251099] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 24 20:57:35 node-5 kernel: [    1.256484] ohci-pci: OHCI PCI platform driver
Jul 24 20:57:35 node-5 kernel: [    1.261851] ohci-platform: OHCI generic platform driver
Jul 24 20:57:35 node-5 kernel: [    1.267123] uhci_hcd: USB Universal Host Controller Interface driver
Jul 24 20:57:35 node-5 kernel: [    1.272536] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 24 20:57:35 node-5 kernel: [    1.464611] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 24 20:57:35 node-5 kernel: [    1.776357] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 24 20:57:35 node-5 kernel: [    1.792710] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 24 20:57:35 node-5 kernel: [    1.798331] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 20:57:35 node-5 kernel: [    1.804102] hub 1-1:1.0: USB hub found
Jul 24 20:57:35 node-5 kernel: [    1.809695] hub 1-1:1.0: 6 ports detected
Jul 24 20:57:35 node-5 kernel: [    1.924239] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 24 20:57:35 node-5 kernel: [    2.311785] i8042: No controller found
Jul 24 20:57:35 node-5 kernel: [    2.317341] mousedev: PS/2 mouse device common for all mice
Jul 24 20:57:35 node-5 kernel: [    2.323118] rtc_cmos 00:02: RTC can wake from S4
Jul 24 20:57:35 node-5 kernel: [    2.328703] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 24 20:57:35 node-5 kernel: [    2.328704] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 20:57:35 node-5 kernel: [    2.329080] hub 2-1:1.0: USB hub found
Jul 24 20:57:35 node-5 kernel: [    2.329316] hub 2-1:1.0: 8 ports detected
Jul 24 20:57:35 node-5 kernel: [    2.351535] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 24 20:57:35 node-5 kernel: [    2.357336] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 24 20:57:35 node-5 kernel: [    2.368705] device-mapper: uevent: version 1.0.3
Jul 24 20:57:35 node-5 kernel: [    2.374454] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 24 20:57:35 node-5 kernel: [    2.385883] ledtrig-cpu: registered to indicate activity on CPUs
Jul 24 20:57:35 node-5 kernel: [    2.391915] TCP: cubic registered
Jul 24 20:57:35 node-5 kernel: [    2.397832] NET: Registered protocol family 10
Jul 24 20:57:35 node-5 kernel: [    2.403932] NET: Registered protocol family 17
Jul 24 20:57:35 node-5 kernel: [    2.409733] Key type dns_resolver registered
Jul 24 20:57:35 node-5 kernel: [    2.415810] Loading compiled-in X.509 certificates
Jul 24 20:57:35 node-5 kernel: [    2.422045] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 24 20:57:35 node-5 kernel: [    2.433823] registered taskstats version 1
Jul 24 20:57:35 node-5 kernel: [    2.441998] Key type trusted registered
Jul 24 20:57:35 node-5 kernel: [    2.449938] Key type encrypted registered
Jul 24 20:57:35 node-5 kernel: [    2.455507] AppArmor: AppArmor sha1 policy hashing enabled
Jul 24 20:57:35 node-5 kernel: [    2.461093] IMA: No TPM chip found, activating TPM-bypass!
Jul 24 20:57:35 node-5 kernel: [    2.467302] regulator-dummy: disabling
Jul 24 20:57:35 node-5 kernel: [    2.472884]   Magic number: 8:822:953
Jul 24 20:57:35 node-5 kernel: [    2.478598] processor cpu8: hash matches
Jul 24 20:57:35 node-5 kernel: [    2.484118] memory memory6: hash matches
Jul 24 20:57:35 node-5 kernel: [    2.489497] rtc_cmos 00:02: setting system clock to 2016-07-24 20:57:01 UTC (1469393821)
Jul 24 20:57:35 node-5 kernel: [    2.501835] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 24 20:57:35 node-5 kernel: [    2.507354] EDD information not available.
Jul 24 20:57:35 node-5 kernel: [    2.512871] PM: Hibernation image not present or could not be loaded.
Jul 24 20:57:35 node-5 kernel: [    2.513680] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 24 20:57:35 node-5 kernel: [    2.524819] Write protecting the kernel read-only data: 12288k
Jul 24 20:57:35 node-5 kernel: [    2.531006] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 24 20:57:35 node-5 kernel: [    2.543477] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 24 20:57:35 node-5 kernel: [    2.575016] device-mapper: multipath: version 1.6.0 loaded
Jul 24 20:57:35 node-5 kernel: [    2.582602] systemd-udevd[217]: starting version 204
Jul 24 20:57:35 node-5 kernel: [    2.606715] md: linear personality registered for level -1
Jul 24 20:57:35 node-5 kernel: [    2.615946] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 24 20:57:35 node-5 kernel: [    2.627693] md: multipath personality registered for level -4
Jul 24 20:57:35 node-5 kernel: [    2.635801] md: raid0 personality registered for level 0
Jul 24 20:57:35 node-5 kernel: [    2.644278] md: raid1 personality registered for level 1
Jul 24 20:57:35 node-5 kernel: [    2.650456] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 24 20:57:35 node-5 kernel: [    2.656624] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 24 20:57:35 node-5 kernel: [    2.656855] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 24 20:57:35 node-5 kernel: [    2.658689] megasas: FW now in Ready state
Jul 24 20:57:35 node-5 kernel: [    2.658992] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.659095] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.659213] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.659376] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.659483] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.659778] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.659871] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.659970] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.660048] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.660217] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.660252] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.660425] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.660521] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.660605] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.660763] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.660903] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.661559] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 24 20:57:35 node-5 kernel: [    2.696115] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 24 20:57:35 node-5 kernel: [    2.709250] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 20:57:35 node-5 kernel: [    2.723154] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 20:57:35 node-5 kernel: [    2.730167] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.730173] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.730179] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.730183] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.730225] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.748523] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 24 20:57:35 node-5 kernel: [    2.755396] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 20:57:35 node-5 kernel: [    2.755599] raid6: sse2x1    9335 MB/s
Jul 24 20:57:35 node-5 kernel: [    2.756011] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 24 20:57:35 node-5 kernel: [    2.756012] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 20:57:35 node-5 kernel: [    2.756013] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 20:57:35 node-5 kernel: [    2.756463] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.756589] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.756751] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.756851] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.757082] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.774559] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 24 20:57:35 node-5 kernel: [    2.774561] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 20:57:35 node-5 kernel: [    2.774574] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 20:57:35 node-5 kernel: [    2.774787] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.774946] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.775093] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.775228] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.775760] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 20:57:35 node-5 kernel: [    2.823713] raid6: sse2x2   10594 MB/s
Jul 24 20:57:35 node-5 kernel: [    2.876067] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 24 20:57:35 node-5 kernel: [    2.882885] usb 2-1.4: Manufacturer: Avocent
Jul 24 20:57:35 node-5 kernel: [    2.889577] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 24 20:57:35 node-5 kernel: [    2.891666] raid6: sse2x4    9525 MB/s
Jul 24 20:57:35 node-5 kernel: [    2.959354] raid6: avx2x1   14858 MB/s
Jul 24 20:57:35 node-5 kernel: [    3.031290] raid6: avx2x2   18855 MB/s
Jul 24 20:57:35 node-5 kernel: [    3.103224] raid6: avx2x4   21427 MB/s
Jul 24 20:57:35 node-5 kernel: [    3.108993] raid6: using algorithm avx2x4 (21427 MB/s)
Jul 24 20:57:35 node-5 kernel: [    3.114730] raid6: using avx2x2 recovery algorithm
Jul 24 20:57:35 node-5 kernel: [    3.120512] megasas:IOC Init cmd success
Jul 24 20:57:35 node-5 kernel: [    3.120514] Switched to clocksource tsc
Jul 24 20:57:35 node-5 kernel: [    3.131290] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 24 20:57:35 node-5 kernel: [    3.131292] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 20:57:35 node-5 kernel: [    3.131307] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 20:57:35 node-5 kernel: [    3.131706] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    3.131833] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    3.131993] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    3.132087] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 24 20:57:35 node-5 kernel: [    3.132355] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 20:57:35 node-5 kernel: [    3.172310] xor: automatically using best checksumming function:
Jul 24 20:57:35 node-5 kernel: [    3.178587] hidraw: raw HID events driver (C) Jiri Kosina
Jul 24 20:57:35 node-5 kernel: [    3.186945] usbcore: registered new interface driver usbhid
Jul 24 20:57:35 node-5 kernel: [    3.192609] usbhid: USB HID core driver
Jul 24 20:57:35 node-5 kernel: [    3.198123] megasas: INIT adapter done
Jul 24 20:57:35 node-5 kernel: [    3.204335] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 24 20:57:35 node-5 kernel: [    3.215154]    avx       : 36710.000 MB/sec
Jul 24 20:57:35 node-5 kernel: [    3.220616] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 24 20:57:35 node-5 kernel: [    3.231893] async_tx: api initialized (async)
Jul 24 20:57:35 node-5 kernel: [    3.231925] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 24 20:57:35 node-5 kernel: [    3.231973] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 24 20:57:35 node-5 kernel: [    3.232028] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 24 20:57:35 node-5 kernel: [    3.232080] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 24 20:57:35 node-5 kernel: [    3.275085] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 24 20:57:35 node-5 kernel: [    3.275439] scsi0 : LSI SAS based MegaRAID driver
Jul 24 20:57:35 node-5 kernel: [    3.282506] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 20:57:35 node-5 kernel: [    3.293599] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 20:57:35 node-5 kernel: [    3.297610] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 24 20:57:35 node-5 kernel: [    3.297736] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 24 20:57:35 node-5 kernel: [    3.298050] sd 0:2:0:0: [sda] Write Protect is off
Jul 24 20:57:35 node-5 kernel: [    3.298051] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 24 20:57:35 node-5 kernel: [    3.298119] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 24 20:57:35 node-5 kernel: [    3.324508]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 24 20:57:35 node-5 kernel: [    3.326388] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 24 20:57:35 node-5 kernel: [    3.391155] md: raid6 personality registered for level 6
Jul 24 20:57:35 node-5 kernel: [    3.398348] md: raid5 personality registered for level 5
Jul 24 20:57:35 node-5 kernel: [    3.405316] md: raid4 personality registered for level 4
Jul 24 20:57:35 node-5 kernel: [    3.415117] md: raid10 personality registered for level 10
Jul 24 20:57:35 node-5 kernel: [    3.468865] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Jul 24 20:57:35 node-5 kernel: [    3.516998] random: lvm urandom read with 31 bits of entropy available
Jul 24 20:57:35 node-5 kernel: [    3.663000] bio: create slab <bio-1> at 1
Jul 24 20:57:35 node-5 kernel: [    4.523197] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 20:57:35 node-5 kernel: [    5.121905] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 24 20:57:35 node-5 kernel: [    5.150603] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 24 20:57:35 node-5 kernel: [    5.151677] random: nonblocking pool is initialized
Jul 24 20:57:35 node-5 kernel: [    5.309611] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 24 20:57:35 node-5 kernel: [    5.345547] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 24 20:57:35 node-5 kernel: [    5.415189] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 20:57:35 node-5 kernel: [    5.587888] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 24 20:57:35 node-5 kernel: [    5.625549] XFS (dm-1): Mounting Filesystem
Jul 24 20:57:35 node-5 kernel: [    5.829810] XFS (dm-1): Ending clean mount
Jul 24 20:57:35 node-5 kernel: [    5.930226] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 20:57:35 node-5 kernel: [    5.964989] XFS (dm-2): Mounting Filesystem
Jul 24 20:57:35 node-5 kernel: [    6.100840] XFS (dm-2): Ending clean mount
Jul 24 20:57:35 node-5 kernel: [    6.238701] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 20:57:35 node-5 kernel: [    8.139974] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 20:57:35 node-5 kernel: [    8.163046] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 20:57:35 node-5 kernel: [    8.310830] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 24 20:57:35 node-5 kernel: [    8.310836] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 24 20:57:35 node-5 kernel: [    8.310840] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 24 20:57:35 node-5 kernel: [    8.310844] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 24 20:57:35 node-5 kernel: [    8.344248] systemd-udevd[803]: starting version 204
Jul 24 20:57:35 node-5 kernel: [    8.526538] power_meter ACPI000D:00: Found ACPI power meter.
Jul 24 20:57:35 node-5 kernel: [    8.526551] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 24 20:57:35 node-5 kernel: [    8.543420] IPMI System Interface driver.
Jul 24 20:57:35 node-5 kernel: [    8.543524] ipmi_si: probing via ACPI
Jul 24 20:57:35 node-5 kernel: [    8.543548] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 24 20:57:35 node-5 kernel: [    8.543549] ipmi_si: Adding ACPI-specified kcs state machine
Jul 24 20:57:35 node-5 kernel: [    8.543571] ipmi_si: probing via SMBIOS
Jul 24 20:57:35 node-5 kernel: [    8.543572] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 20:57:35 node-5 kernel: [    8.543573] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 24 20:57:35 node-5 kernel: [    8.543575] ipmi_si: probing via SPMI
Jul 24 20:57:35 node-5 kernel: [    8.543576] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 20:57:35 node-5 kernel: [    8.543577] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 24 20:57:35 node-5 kernel: [    8.543579] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 24 20:57:35 node-5 kernel: [    8.547488] wmi: Mapper loaded
Jul 24 20:57:35 node-5 kernel: [    8.561650] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 24 20:57:35 node-5 kernel: [    8.561655] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 20:57:35 node-5 kernel: [    8.561657] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 24 20:57:35 node-5 kernel: [    8.561659] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 20:57:35 node-5 kernel: [    8.561695] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 24 20:57:35 node-5 kernel: [    8.563581] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 24 20:57:35 node-5 kernel: [    8.643001] systemd-udevd[825]: renamed network interface eth1 to enp7s0
Jul 24 20:57:35 node-5 kernel: [    8.666885] systemd-udevd[852]: renamed network interface eth0 to enp6s0
Jul 24 20:57:35 node-5 kernel: [    8.682957] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 24 20:57:35 node-5 kernel: [    8.682962] ipmi_si 00:09: IPMI kcs interface initialized
Jul 24 20:57:35 node-5 kernel: [    8.690862] systemd-udevd[822]: renamed network interface eth3 to enp9s0
Jul 24 20:57:35 node-5 kernel: [    8.738829] systemd-udevd[821]: renamed network interface eth2 to enp8s0
Jul 24 20:57:35 node-5 kernel: [    8.926980] type=1400 audit(1469393827.938:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1098 comm="apparmor_parser"
Jul 24 20:57:35 node-5 kernel: [    8.927134] type=1400 audit(1469393827.938:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1098 comm="apparmor_parser"
Jul 24 20:57:35 node-5 kernel: [    8.927264] type=1400 audit(1469393827.938:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1098 comm="apparmor_parser"
Jul 24 20:57:35 node-5 kernel: [    8.933151] type=1400 audit(1469393827.942:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1090 comm="apparmor_parser"
Jul 24 20:57:35 node-5 kernel: [    8.933307] type=1400 audit(1469393827.942:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1090 comm="apparmor_parser"
Jul 24 20:57:35 node-5 kernel: [    8.933441] type=1400 audit(1469393827.942:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1090 comm="apparmor_parser"
Jul 24 20:57:35 node-5 kernel: [    8.941214] type=1400 audit(1469393827.950:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1092 comm="apparmor_parser"
Jul 24 20:57:35 node-5 kernel: [    8.941357] type=1400 audit(1469393827.950:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1092 comm="apparmor_parser"
Jul 24 20:57:35 node-5 kernel: [    8.941483] type=1400 audit(1469393827.950:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1092 comm="apparmor_parser"
Jul 24 20:57:35 node-5 kernel: [    8.945620] type=1400 audit(1469393827.954:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1089 comm="apparmor_parser"
Jul 24 20:57:35 node-5 kernel: [    9.439801] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 20:57:35 node-5 kernel: [    9.461292] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 20:57:35 node-5 kernel: [    9.657088] enic 0000:06:00.0 enp6s0: Link UP
Jul 24 20:57:35 node-5 kernel: [    9.657515] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 24 20:57:35 node-5 kernel: [    9.657525] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 24 20:57:35 node-5 kernel: [   19.269878] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 24 20:57:36 node-5 failsafe: Failsafe of 120 seconds reached.
Jul 24 20:57:36 node-5 kernel: [   37.665151] init: failsafe main process (8438) killed by TERM signal
Jul 24 20:57:37 node-5 dbus[8484]: [system] AppArmor D-Bus mediation is enabled
Jul 24 20:57:37 node-5 kernel: [   37.888357] audit_printk_skb: 30 callbacks suppressed
Jul 24 20:57:37 node-5 kernel: [   37.888358] type=1400 audit(1469393857.103:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8563 comm="apparmor_parser"
Jul 24 20:57:37 node-5 kernel: [   37.888363] type=1400 audit(1469393857.103:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8563 comm="apparmor_parser"
Jul 24 20:57:37 node-5 kernel: [   37.888366] type=1400 audit(1469393857.103:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8563 comm="apparmor_parser"
Jul 24 20:57:37 node-5 kernel: [   37.888587] type=1400 audit(1469393857.103:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8563 comm="apparmor_parser"
Jul 24 20:57:37 node-5 kernel: [   37.888589] type=1400 audit(1469393857.103:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8563 comm="apparmor_parser"
Jul 24 20:57:37 node-5 kernel: [   37.888706] type=1400 audit(1469393857.103:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8563 comm="apparmor_parser"
Jul 24 20:57:37 node-5 kernel: [   37.890349] type=1400 audit(1469393857.107:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8564 comm="apparmor_parser"
Jul 24 20:57:37 node-5 kernel: [   37.992578] type=1400 audit(1469393857.207:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8566 comm="apparmor_parser"
Jul 24 20:57:37 node-5 cron[8596]: (CRON) INFO (pidfile fd = 3)
Jul 24 20:57:37 node-5 anacron[8631]: Anacron 2.3 started on 2016-07-24
Jul 24 20:57:37 node-5 cron[8635]: (CRON) STARTUP (fork ok)
Jul 24 20:57:37 node-5 anacron[8631]: Will run job `cron.daily' in 5 min.
Jul 24 20:57:37 node-5 anacron[8631]: Will run job `cron.weekly' in 10 min.
Jul 24 20:57:37 node-5 anacron[8631]: Will run job `cron.monthly' in 15 min.
Jul 24 20:57:37 node-5 anacron[8631]: Jobs will be executed sequentially
Jul 24 20:57:37 node-5 cron[8635]: (CRON) INFO (Running @reboot jobs)
Jul 24 20:57:37 node-5 multipathd: path checkers start up
Jul 24 20:57:37 node-5 postfix/master[8775]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 24 20:57:41 node-5 puppet-agent[8959]: Reopening log files
Jul 24 20:57:42 node-5 puppet-agent[8959]: Could not request certificate: Connection refused - connect(2)
Jul 24 20:57:53 node-5 puppet-user[9167]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 24 20:57:53 node-5 puppet-user[9167]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 24 20:57:54 node-5 puppet-user[9167]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 24 20:57:54 node-5 puppet-user[9167]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 24 20:57:54 node-5 puppet-user[9167]: Finished catalog run in 0.53 seconds
Jul 24 20:57:55 node-5 multipathd: uevent trigger error
Jul 24 20:57:55 node-5 puppet-user[9592]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 20:57:55 node-5 puppet-user[9592]: Compiled catalog for node-5.domain.tld in environment production in 0.09 seconds
Jul 24 20:57:55 node-5 puppet-user[9592]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 24 20:57:55 node-5 puppet-user[9592]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 24 20:57:55 node-5 puppet-user[9592]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 24 20:57:55 node-5 puppet-user[9592]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 24 20:57:55 node-5 puppet-user[9592]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 24 20:57:55 node-5 puppet-user[9592]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 24 20:57:55 node-5 puppet-user[9592]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 24 20:57:55 node-5 puppet-user[9592]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 24 20:57:56 node-5 puppet-user[9592]: Finished catalog run in 0.08 seconds
Jul 24 20:57:57 node-5 puppet-user[10055]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 24 20:57:57 node-5 puppet-user[10055]: Compiled catalog for node-5.domain.tld in environment production in 0.07 seconds
Jul 24 20:57:57 node-5 puppet-user[10055]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 24 20:57:57 node-5 puppet-user[10055]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 24 20:57:57 node-5 puppet-user[10055]: Finished catalog run in 0.03 seconds
Jul 24 20:57:59 node-5 puppet-user[10520]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 24 20:57:59 node-5 puppet-user[10520]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 24 20:57:59 node-5 puppet-user[10520]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 24 20:57:59 node-5 puppet-user[10520]: Finished catalog run in 0.05 seconds
Jul 24 20:58:01 node-5 puppet-user[11173]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 24 20:58:01 node-5 puppet-user[11173]: Compiled catalog for node-5.domain.tld in environment production in 0.21 seconds
Jul 24 20:58:01 node-5 puppet-user[11173]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 24 20:58:01 node-5 kernel: [   62.154663] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 24 20:58:01 node-5 kernel: [   62.154710] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 24 20:58:01 node-5 puppet-user[11173]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 24 20:58:01 node-5 puppet-user[11173]: Finished catalog run in 0.07 seconds
Jul 24 20:58:01 node-5 CRON[11597]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 24 20:58:02 node-5 puppet-user[11646]: (Scope(Class[main])) MODULAR: sync_time
Jul 24 20:58:02 node-5 puppet-user[11646]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 24 20:58:03 node-5 ntpdate[12063]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 24 20:58:07 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 20:58:07 node-5 nailgun-agent: D, [2016-07-24T20:58:01.630333 #11600] DEBUG -- : Sleep for 6 seconds before sending request
Jul 24 20:58:07 node-5 nailgun-agent: I, [2016-07-24T20:58:07.645554 #11600]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 20:58:08 node-5 nailgun-agent: D, [2016-07-24T20:58:08.030526 #11600] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 24 20:58:09 node-5 ntpdate[12063]: adjust time server 10.20.0.2 offset -0.089520 sec
Jul 24 20:58:09 node-5 puppet-user[11646]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 24 20:58:09 node-5 puppet-user[11646]: Finished catalog run in 6.20 seconds
Jul 24 20:58:11 node-5 kernel: [   72.337978] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 20:58:11 node-5 puppet-agent[8959]: Could not run: SIGTERM
Jul 24 20:58:11 node-5 kernel: [   72.604953] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 24 20:58:11 node-5 ec2: 
Jul 24 20:58:11 node-5 ec2: #############################################################
Jul 24 20:58:11 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 24 20:58:11 node-5 ec2: 1024 c6:52:04:89:9f:0f:2e:9d:70:b9:1b:ef:f1:fa:4e:5e  root@node-5.domain.tld (DSA)
Jul 24 20:58:11 node-5 ec2: 256 b6:db:e6:a4:b5:a6:cc:66:d9:0b:03:d7:8b:b8:d7:ed  root@node-5.domain.tld (ECDSA)
Jul 24 20:58:11 node-5 ec2: 256 1b:dc:25:ac:14:af:3b:d7:5a:dc:82:6c:cf:78:2e:2b  root@node-5.domain.tld (ED25519)
Jul 24 20:58:11 node-5 ec2: 2048 aa:61:e9:3a:3e:a3:1a:a8:91:6c:59:50:a3:b2:6a:50  root@node-5.domain.tld (RSA)
Jul 24 20:58:11 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 24 20:58:11 node-5 ec2: #############################################################
Jul 24 20:58:13 node-5 puppet-user[12565]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 20:58:13 node-5 puppet-user[12565]: Compiled catalog for node-5.domain.tld in environment production in 0.07 seconds
Jul 24 20:58:14 node-5 puppet-user[12565]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 24 20:58:14 node-5 puppet-user[12565]: Finished catalog run in 0.06 seconds
Jul 24 20:58:15 node-5 puppet-user[13018]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 24 20:58:16 node-5 puppet-user[13018]: Compiled catalog for node-5.domain.tld in environment production in 0.72 seconds
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 24 20:58:16 node-5 puppet-user[13018]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.068350 #11600] DEBUG -- : Trying to find block devices
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.068474 #11600] DEBUG -- : Found block device: sda
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.068515 #11600] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.068537 #11600] DEBUG -- : Trying to get list of physical devices
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.068675 #11600] DEBUG -- : Getting udev properties for device: sda
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.070643 #11600] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc788
Jul 24 20:58:20 node-5 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"81728", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.070669 #11600] DEBUG -- : Trying to find out if device sda is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.070725 #11600] DEBUG -- : Device sda removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.070741 #11600] DEBUG -- : Device sda seems to be appropriate
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.071206 #11600] DEBUG -- : Getting udev properties for device: dm-0
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.073015 #11600] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-tlUqd37OZmMuK3KJlxsA2yoMLtU0oCVZcYht5M2pXpNwl5KR9k6n1uMzmPt4HKy2 /dev/disk/by-uuid/9139f1a1-6180-482c-8d63-00236bae167d /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-tlUqd37OZmMuK3KJlxsA2yoMLtU0oCVZcYht5M2pXpNwl5KR9k6n1uMzmPt4HKy2", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9139f1a1-6180-482c-8d63-00236bae167d", "ID_FS_UUID_ENC"=>"9139f1a1-6180-482c-8d63-00236bae167d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2
Jul 24 20:58:20 node-5 nailgun-agent: 0171", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.073054 #11600] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.073083 #11600] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.073095 #11600] DEBUG -- : Device dm-0 seems to be appropriate
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.073110 #11600] DEBUG -- : Getting udev properties for device: dm-1
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.075004 #11600] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-nPmf9EIy8UBlrMpc9qoUZI7aETskEcvrgYFIWJLZS7N1Pcb1liydtkhb6c20cRQc /dev/disk/by-uuid/578ae3e9-2cab-4cd4-8ebe-ba54164bfb8b /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-nPmf9EIy8UBlrMpc9qoUZI7aETskEcvrgYFIWJLZS7N1Pcb1liydtkhb6c20cRQc", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"578ae3e9-2cab-4cd4-8ebe-ba54164bfb8b", "ID_FS_UUID_ENC"=>"578ae3e9-2cab-4cd4-8ebe-ba54164bfb8b", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39078", "nomdmonddf"=>"1", "nom
Jul 24 20:58:20 node-5 nailgun-agent: dmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.075030 #11600] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.075059 #11600] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.075073 #11600] DEBUG -- : Device dm-1 seems to be appropriate
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.075103 #11600] DEBUG -- : Getting udev properties for device: dm-2
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.077162 #11600] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-AqCulnRFfH8KyzZmuh115U3kVAxaMFdiYL6Ue7pHN1W7Wd38DoxAvIE2JpNK7Bfy /dev/disk/by-uuid/69db2484-cf27-4fbd-b233-be13b5332263 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-AqCulnRFfH8KyzZmuh115U3kVAxaMFdiYL6Ue7pHN1W7Wd38DoxAvIE2JpNK7Bfy", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"69db2484-cf27-4fbd-b233-be13b5332263", "ID_FS_UUID_ENC"=>"69db2484-cf27-4fbd-b233-be13b5332263", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4
Jul 24 20:58:20 node-5 nailgun-agent: 1403", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.077218 #11600] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.077249 #11600] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.077272 #11600] DEBUG -- : Device dm-2 seems to be appropriate
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.077286 #11600] DEBUG -- : Getting udev properties for device: dm-3
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.079041 #11600] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-EundaddZS7b2thuCrnSZLFUxnCYjIwEuBOOGSjXyPdxIBCMZ2IdTayPkSdANdktf /dev/disk/by-uuid/78a1f4a7-bf8f-4ea1-9ea9-296402cf43b7 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-EundaddZS7b2thuCrnSZLFUxnCYjIwEuBOOGSjXyPdxIBCMZ2IdTayPkSdANdktf", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"78a1f4a7-bf8f-4ea1-9ea9-296402cf43b7", "ID_FS_UUID_ENC"=>"78a1f4a7-bf8f-4ea1-9ea9-296402cf43b7", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50953", "nomdmon
Jul 24 20:58:20 node-5 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.079086 #11600] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.079115 #11600] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.079128 #11600] DEBUG -- : Device dm-3 seems to be appropriate
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.079144 #11600] DEBUG -- : Getting udev properties for device: dm-4
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.081034 #11600] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-fPf8h1Z0p9Ph00m7bzLrCIg2oGkqRGEBob1XuTGisYowlMCgjBnp0Il7gxg2YFIs /dev/disk/by-uuid/ac380e6c-5f3e-4ad5-9745-035b98891274 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-fPf8h1Z0p9Ph00m7bzLrCIg2oGkqRGEBob1XuTGisYowlMCgjBnp0Il7gxg2YFIs", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ac380e6c-5f3e-4ad5-9745-035b98891274", "ID_FS_UUID_ENC"=>"ac380e6c-5f3e-4ad5-9745-035b98891274", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62651", "nomdmonddf"=>"1",
Jul 24 20:58:20 node-5 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.081071 #11600] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.081103 #11600] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.081118 #11600] DEBUG -- : Device dm-4 seems to be appropriate
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.081142 #11600] DEBUG -- : Getting udev properties for device: dm-5
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.082818 #11600] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-jvnMCfYtO3EVO1izRXUP2FsaRZ1zLEffcxwavnfPyp3Ug9kSpiIXDoPtTt0rtc3o /dev/disk/by-uuid/0bb60b1d-e65f-4582-acfb-f09607b839f4 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-jvnMCfYtO3EVO1izRXUP2FsaRZ1zLEffcxwavnfPyp3Ug9kSpiIXDoPtTt0rtc3o", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0bb60b1d-e65f-4582-acfb-f09607b839f4", "ID_FS_UUID_ENC"=>"0bb60b1d-e65f-4582-acfb-f09607b839f4", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"69640", "nomdmonddf"=>"1", "nom
Jul 24 20:58:20 node-5 nailgun-agent: dmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.082854 #11600] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.082885 #11600] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.082899 #11600] DEBUG -- : Device dm-5 seems to be appropriate
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.082932 #11600] DEBUG -- : Getting udev properties for device: dm-6
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.084543 #11600] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-jvnMCfYtO3EVO1izRXUP2FsaRZ1zLEffncVNymY6wEIRXKBaYHM9Za3dWNFo9UC7 /dev/disk/by-uuid/95249486-bc13-4b39-90ed-cbd21dec6bf0 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-jvnMCfYtO3EVO1izRXUP2FsaRZ1zLEffncVNymY6wEIRXKBaYHM9Za3dWNFo9UC7", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"95249486-bc13-4b39-90ed-cbd21dec6bf0", "ID_FS_UUID_ENC"=>"95249486-bc13-4b39-90ed-cbd21dec6bf0", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"70063", "nomdmonddf"=>"1", "nomdmonisw
Jul 24 20:58:20 node-5 nailgun-agent: "=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.084579 #11600] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.084612 #11600] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.084645 #11600] DEBUG -- : Device dm-6 seems to be appropriate
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.084659 #11600] DEBUG -- : Getting udev properties for device: ram0
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.086408 #11600] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50272", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.086457 #11600] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.086498 #11600] DEBUG -- : Device ram0 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.086517 #11600] DEBUG -- : Getting udev properties for device: ram1
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.088483 #11600] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50287", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.088511 #11600] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.088549 #11600] DEBUG -- : Device ram1 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.088581 #11600] DEBUG -- : Getting udev properties for device: ram2
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.090244 #11600] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50417", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.090270 #11600] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.090306 #11600] DEBUG -- : Device ram2 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.090326 #11600] DEBUG -- : Getting udev properties for device: ram3
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.091924 #11600] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50436", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.091974 #11600] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.092008 #11600] DEBUG -- : Device ram3 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.092026 #11600] DEBUG -- : Getting udev properties for device: ram4
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.093569 #11600] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50456", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.093595 #11600] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.093628 #11600] DEBUG -- : Device ram4 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.093663 #11600] DEBUG -- : Getting udev properties for device: ram5
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.095220 #11600] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50476", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.095246 #11600] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.095279 #11600] DEBUG -- : Device ram5 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.095309 #11600] DEBUG -- : Getting udev properties for device: ram6
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.096992 #11600] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50494", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.097017 #11600] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.097048 #11600] DEBUG -- : Device ram6 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.097096 #11600] DEBUG -- : Getting udev properties for device: ram7
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.098639 #11600] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50511", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.098670 #11600] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.098701 #11600] DEBUG -- : Device ram7 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.098726 #11600] DEBUG -- : Getting udev properties for device: ram8
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.100231 #11600] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50529", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.100257 #11600] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.100301 #11600] DEBUG -- : Device ram8 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.100333 #11600] DEBUG -- : Getting udev properties for device: ram9
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.101850 #11600] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50550", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.101890 #11600] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.101922 #11600] DEBUG -- : Device ram9 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.101940 #11600] DEBUG -- : Getting udev properties for device: loop0
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.103457 #11600] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50152", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.103481 #11600] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.103524 #11600] DEBUG -- : Device loop0 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.103551 #11600] DEBUG -- : Getting udev properties for device: loop1
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.105163 #11600] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50164", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.105204 #11600] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.105236 #11600] DEBUG -- : Device loop1 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.105254 #11600] DEBUG -- : Getting udev properties for device: loop2
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.106947 #11600] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50180", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.106980 #11600] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.107028 #11600] DEBUG -- : Device loop2 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.107047 #11600] DEBUG -- : Getting udev properties for device: loop3
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.108661 #11600] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50193", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.108725 #11600] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.108759 #11600] DEBUG -- : Device loop3 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.108790 #11600] DEBUG -- : Getting udev properties for device: loop4
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.110314 #11600] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50204", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.110344 #11600] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.110384 #11600] DEBUG -- : Device loop4 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.110417 #11600] DEBUG -- : Getting udev properties for device: loop5
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.111997 #11600] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50218", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.112022 #11600] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.112067 #11600] DEBUG -- : Device loop5 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.112084 #11600] DEBUG -- : Getting udev properties for device: loop6
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.114380 #11600] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50236", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.114444 #11600] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.114495 #11600] DEBUG -- : Device loop6 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.114541 #11600] DEBUG -- : Getting udev properties for device: loop7
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.116652 #11600] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50255", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.122601 #11600] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.122659 #11600] DEBUG -- : Device loop7 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.122687 #11600] DEBUG -- : Getting udev properties for device: ram10
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.124775 #11600] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50303", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.124807 #11600] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.124876 #11600] DEBUG -- : Device ram10 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.124897 #11600] DEBUG -- : Getting udev properties for device: ram11
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.127063 #11600] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50318", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.127089 #11600] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.127123 #11600] DEBUG -- : Device ram11 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.127183 #11600] DEBUG -- : Getting udev properties for device: ram12
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.129065 #11600] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50334", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.129090 #11600] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.129122 #11600] DEBUG -- : Device ram12 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.129141 #11600] DEBUG -- : Getting udev properties for device: ram13
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.130823 #11600] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50353", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.130848 #11600] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.130881 #11600] DEBUG -- : Device ram13 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.130900 #11600] DEBUG -- : Getting udev properties for device: ram14
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.132534 #11600] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50371", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.132560 #11600] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.132592 #11600] DEBUG -- : Device ram14 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.132612 #11600] DEBUG -- : Getting udev properties for device: ram15
Jul 24 20:58:20 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134624 #11600] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"50387", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134650 #11600] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134682 #11600] DEBUG -- : Device ram15 removable parameter: "0"
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134785 #11600] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134801 #11600] DEBUG -- : Block device seems to be physical data storage: sda
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134840 #11600] DEBUG -- : Found block device: dm-0
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134854 #11600] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134867 #11600] DEBUG -- : Found block device: dm-1
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134878 #11600] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134888 #11600] DEBUG -- : Found block device: dm-2
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134899 #11600] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134954 #11600] DEBUG -- : Found block device: dm-3
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134965 #11600] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134974 #11600] DEBUG -- : Found block device: dm-4
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134985 #11600] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.134993 #11600] DEBUG -- : Found block device: dm-5
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135003 #11600] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135011 #11600] DEBUG -- : Found block device: dm-6
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135022 #11600] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135030 #11600] DEBUG -- : Found block device: ram0
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135104 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135113 #11600] DEBUG -- : Found block device: ram1
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135124 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135134 #11600] DEBUG -- : Found block device: ram2
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135145 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135153 #11600] DEBUG -- : Found block device: ram3
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135163 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135172 #11600] DEBUG -- : Found block device: ram4
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135213 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135223 #11600] DEBUG -- : Found block device: ram5
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135233 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135242 #11600] DEBUG -- : Found block device: ram6
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135251 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135260 #11600] DEBUG -- : Found block device: ram7
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135269 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135277 #11600] DEBUG -- : Found block device: ram8
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135287 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135296 #11600] DEBUG -- : Found block device: ram9
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135336 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135345 #11600] DEBUG -- : Found block device: loop0
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135355 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135363 #11600] DEBUG -- : Found block device: loop1
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135373 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135381 #11600] DEBUG -- : Found block device: loop2
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135390 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135398 #11600] DEBUG -- : Found block device: loop3
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135407 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135452 #11600] DEBUG -- : Found block device: loop4
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135463 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135472 #11600] DEBUG -- : Found block device: loop5
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135482 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135490 #11600] DEBUG -- : Found block device: loop6
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135500 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135508 #11600] DEBUG -- : Found block device: loop7
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135519 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135527 #11600] DEBUG -- : Found block device: ram10
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135537 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135588 #11600] DEBUG -- : Found block device: ram11
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135598 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135606 #11600] DEBUG -- : Found block device: ram12
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135615 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135624 #11600] DEBUG -- : Found block device: ram13
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135634 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135642 #11600] DEBUG -- : Found block device: ram14
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135653 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135661 #11600] DEBUG -- : Found block device: ram15
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135671 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.135724 #11600] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.215354 #11600] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 24 20:58:20 node-5 nailgun-agent: D, [2016-07-24T20:58:20.215466 #11600] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 24 20:58:32 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.240881 #11600] DEBUG -- : Trying to find block devices
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.240970 #11600] DEBUG -- : Found block device: sda
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.240998 #11600] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241046 #11600] DEBUG -- : Block device seems to be physical data storage: sda
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241068 #11600] DEBUG -- : Found block device: dm-0
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241081 #11600] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241092 #11600] DEBUG -- : Found block device: dm-1
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241102 #11600] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241112 #11600] DEBUG -- : Found block device: dm-2
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241122 #11600] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241130 #11600] DEBUG -- : Found block device: dm-3
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241140 #11600] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241187 #11600] DEBUG -- : Found block device: dm-4
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241198 #11600] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241206 #11600] DEBUG -- : Found block device: dm-5
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241216 #11600] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241224 #11600] DEBUG -- : Found block device: dm-6
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241233 #11600] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241242 #11600] DEBUG -- : Found block device: ram0
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241251 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241260 #11600] DEBUG -- : Found block device: ram1
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241285 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241295 #11600] DEBUG -- : Found block device: ram2
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241305 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241313 #11600] DEBUG -- : Found block device: ram3
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241321 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241329 #11600] DEBUG -- : Found block device: ram4
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241338 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241345 #11600] DEBUG -- : Found block device: ram5
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241354 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241382 #11600] DEBUG -- : Found block device: ram6
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241393 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241401 #11600] DEBUG -- : Found block device: ram7
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241409 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241417 #11600] DEBUG -- : Found block device: ram8
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241426 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241434 #11600] DEBUG -- : Found block device: ram9
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241443 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241451 #11600] DEBUG -- : Found block device: loop0
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241459 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241484 #11600] DEBUG -- : Found block device: loop1
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241493 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241501 #11600] DEBUG -- : Found block device: loop2
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241510 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241519 #11600] DEBUG -- : Found block device: loop3
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241528 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241553 #11600] DEBUG -- : Found block device: loop4
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241563 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241571 #11600] DEBUG -- : Found block device: loop5
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241580 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241588 #11600] DEBUG -- : Found block device: loop6
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241596 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241604 #11600] DEBUG -- : Found block device: loop7
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241612 #11600] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241640 #11600] DEBUG -- : Found block device: ram10
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241650 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241657 #11600] DEBUG -- : Found block device: ram11
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241666 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241675 #11600] DEBUG -- : Found block device: ram12
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241685 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241693 #11600] DEBUG -- : Found block device: ram13
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241702 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241710 #11600] DEBUG -- : Found block device: ram14
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241718 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241751 #11600] DEBUG -- : Found block device: ram15
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241761 #11600] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.241789 #11600] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 24 20:58:32 node-5 nailgun-agent: D, [2016-07-24T20:58:32.433271 #11600] DEBUG -- : Response: status: 200 body: {"id": 5}
Jul 24 20:58:32 node-5 nailgun-agent: I, [2016-07-24T20:58:32.433495 #11600]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 24 20:58:33 node-5 puppet-user[13018]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 24 20:58:33 node-5 puppet-user[13018]: Finished catalog run in 16.73 seconds
Jul 24 20:58:34 node-5 puppet-user[14349]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 24 20:58:34 node-5 puppet-user[14349]: Compiled catalog for node-5.domain.tld in environment production in 0.11 seconds
Jul 24 20:58:39 node-5 puppet-user[14349]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 24 20:59:01 node-5 CRON[16059]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 24 20:59:07 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 20:59:07 node-5 nailgun-agent: I, [2016-07-24T20:59:07.616688 #16062]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 20:59:13 node-5 puppet-user[14349]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 24 20:59:14 node-5 puppet-user[14349]: Finished catalog run in 39.20 seconds
Jul 24 20:59:15 node-5 puppet-user[17033]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 24 20:59:16 node-5 puppet-user[17033]: Compiled catalog for node-5.domain.tld in environment production in 0.50 seconds
Jul 24 20:59:16 node-5 puppet-user[17033]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 24 20:59:16 node-5 puppet-user[17033]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 24 20:59:16 node-5 puppet-user[17033]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 24 20:59:16 node-5 puppet-user[17033]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 24 20:59:16 node-5 puppet-user[17033]: Finished catalog run in 0.10 seconds
Jul 24 20:59:18 node-5 puppet-user[17488]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 24 20:59:18 node-5 puppet-user[17488]: Compiled catalog for node-5.domain.tld in environment production in 0.83 seconds
Jul 24 20:59:19 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 24 20:59:19 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 24 20:59:19 node-5 crontab[17926]: (root) LIST (root)
Jul 24 20:59:19 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 24 20:59:19 node-5 crontab[17927]: (root) REPLACE (root)
Jul 24 20:59:20 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 20:59:20 node-5 nailgun-agent: I, [2016-07-24T20:59:20.655182 #16062]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 24 20:59:21 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 24 20:59:23 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 24 20:59:24 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 24 20:59:24 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 24 20:59:24 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 24 20:59:24 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 24 20:59:24 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 24 20:59:24 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 24 20:59:24 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 24 20:59:24 node-5 puppet-user[17488]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 24 20:59:24 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8411" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:24 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 24 20:59:26 node-5 multipathd: uevent trigger error
<27>Jul 24 20:59:26 node-5 multipathd: uevent trigger error
<27>Jul 24 20:59:26 node-5 multipathd: uevent trigger error
<27>Jul 24 20:59:26 node-5 multipathd: uevent trigger error
<27>Jul 24 20:59:26 node-5 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-5 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-5 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-5 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-5 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-5 multipathd: uevent trigger error
<27>Jul 24 21:00:49 node-5 ntpdate[29115]: no servers can be used, exiting
<27>Jul 24 21:01:20 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:20 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:21 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:21 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:21 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:24 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:24 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:24 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:24 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:24 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:35 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:35 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:35 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:35 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:35 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:35 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:38 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:38 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:38 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:38 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:38 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:45 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:45 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:45 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:45 node-5 multipathd: uevent trigger error
<27>Jul 24 21:01:45 node-5 multipathd: uevent trigger error
<27>Jul 24 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 24 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 24 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 24 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 24 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:08 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 24 21:03:12 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:12 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:12 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:12 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:12 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:26 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:26 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:26 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:26 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:34 node-5 multipathd: uevent trigger error
<129>Jul 24 21:03:38 node-5 haproxy[18194]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:03:40 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:40 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:40 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:40 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:40 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:43 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:43 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:43 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:43 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:43 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:43 node-5 multipathd: uevent trigger error
<129>Jul 24 21:03:46 node-5 haproxy[20332]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:03:47 node-5 haproxy[20336]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:03:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:48 node-5 multipathd: uevent trigger error
<129>Jul 24 21:03:51 node-5 haproxy[21496]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:03:52 node-5 haproxy[21501]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:03:52 node-5 haproxy[21501]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:03:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:53 node-5 multipathd: uevent trigger error
<129>Jul 24 21:03:56 node-5 haproxy[22680]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:03:57 node-5 haproxy[22684]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:03:57 node-5 haproxy[22684]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:03:57 node-5 haproxy[22684]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:03:58 node-5 haproxy[22684]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:03:59 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:59 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:59 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:59 node-5 multipathd: uevent trigger error
<27>Jul 24 21:03:59 node-5 multipathd: uevent trigger error
<129>Jul 24 21:04:01 node-5 haproxy[23812]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:02 node-5 haproxy[23821]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:02 node-5 haproxy[23821]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:02 node-5 haproxy[23821]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:03 node-5 haproxy[23821]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:03 node-5 haproxy[23821]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:04 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:04 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:04 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:04 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:04 node-5 multipathd: uevent trigger error
<129>Jul 24 21:04:05 node-5 haproxy[23821]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:05 node-5 haproxy[23821]: 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 24 21:04:05 node-5 haproxy[23821]: proxy aodh has no server available!
<129>Jul 24 21:04:06 node-5 haproxy[24942]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:07 node-5 haproxy[24949]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:07 node-5 haproxy[24949]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:07 node-5 haproxy[24949]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:08 node-5 haproxy[24949]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:08 node-5 haproxy[24949]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:08 node-5 haproxy[24949]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:09 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:09 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:09 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:09 node-5 multipathd: uevent trigger error
<129>Jul 24 21:04:10 node-5 haproxy[24949]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:10 node-5 haproxy[24949]: 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 24 21:04:10 node-5 haproxy[24949]: proxy aodh has no server available!
<129>Jul 24 21:04:10 node-5 haproxy[24949]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:10 node-5 haproxy[24949]: 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 24 21:04:10 node-5 haproxy[24949]: proxy ceilometer has no server available!
<129>Jul 24 21:04:12 node-5 haproxy[26064]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:12 node-5 haproxy[26064]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:12 node-5 haproxy[26064]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:13 node-5 haproxy[26068]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:13 node-5 haproxy[26068]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:13 node-5 haproxy[26068]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:13 node-5 haproxy[26068]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:15 node-5 multipathd: uevent trigger error
<129>Jul 24 21:04:15 node-5 haproxy[26068]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:15 node-5 haproxy[26068]: 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 24 21:04:15 node-5 haproxy[26068]: proxy aodh has no server available!
<129>Jul 24 21:04:15 node-5 haproxy[26068]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:15 node-5 haproxy[26068]: 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 24 21:04:15 node-5 haproxy[26068]: proxy ceilometer has no server available!
<129>Jul 24 21:04:17 node-5 haproxy[27338]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:17 node-5 haproxy[27338]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:17 node-5 haproxy[27338]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:18 node-5 haproxy[27342]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:18 node-5 haproxy[27342]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:18 node-5 haproxy[27342]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:18 node-5 haproxy[27342]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:19 node-5 haproxy[27342]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:19 node-5 haproxy[27342]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:19 node-5 haproxy[27342]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:19 node-5 haproxy[27342]: proxy horizon has no server available!
<27>Jul 24 21:04:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:19 node-5 multipathd: uevent trigger error
<129>Jul 24 21:04:20 node-5 haproxy[27342]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:20 node-5 haproxy[27342]: 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 24 21:04:20 node-5 haproxy[27342]: proxy aodh has no server available!
<129>Jul 24 21:04:20 node-5 haproxy[27342]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:21 node-5 haproxy[27342]: 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 24 21:04:21 node-5 haproxy[27342]: proxy ceilometer has no server available!
<129>Jul 24 21:04:22 node-5 haproxy[28510]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:22 node-5 haproxy[28510]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:23 node-5 haproxy[28514]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:23 node-5 haproxy[28514]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:23 node-5 haproxy[28514]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:23 node-5 haproxy[28514]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:23 node-5 haproxy[28514]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:24 node-5 haproxy[28514]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:24 node-5 haproxy[28514]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:24 node-5 haproxy[28514]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:24 node-5 haproxy[28514]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:24 node-5 haproxy[28514]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:24 node-5 haproxy[28514]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:24 node-5 haproxy[28514]: proxy horizon has no server available!
<27>Jul 24 21:04:25 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:25 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:25 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:25 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:25 node-5 multipathd: uevent trigger error
<129>Jul 24 21:04:25 node-5 haproxy[28514]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:25 node-5 haproxy[28514]: 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 24 21:04:25 node-5 haproxy[28514]: proxy glance-registry has no server available!
<129>Jul 24 21:04:26 node-5 haproxy[28514]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:26 node-5 haproxy[28514]: 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 24 21:04:26 node-5 haproxy[28514]: proxy aodh has no server available!
<129>Jul 24 21:04:26 node-5 haproxy[28514]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:26 node-5 haproxy[28514]: 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 24 21:04:26 node-5 haproxy[28514]: proxy ceilometer has no server available!
<129>Jul 24 21:04:28 node-5 haproxy[29849]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:28 node-5 haproxy[29849]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:28 node-5 haproxy[29849]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:28 node-5 haproxy[29849]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:28 node-5 haproxy[29849]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:28 node-5 haproxy[29849]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-5 haproxy[29853]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-5 haproxy[29853]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-5 haproxy[29853]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-5 haproxy[29853]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-5 haproxy[29853]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-5 haproxy[29853]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-5 haproxy[29853]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:30 node-5 haproxy[29853]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:30 node-5 haproxy[29853]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:30 node-5 haproxy[29853]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:30 node-5 haproxy[29853]: proxy horizon has no server available!
<129>Jul 24 21:04:31 node-5 haproxy[29853]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:31 node-5 haproxy[29853]: 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 24 21:04:31 node-5 haproxy[29853]: proxy glance-registry has no server available!
<129>Jul 24 21:04:31 node-5 haproxy[29853]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:31 node-5 haproxy[29853]: 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 24 21:04:31 node-5 haproxy[29853]: proxy aodh has no server available!
<129>Jul 24 21:04:31 node-5 haproxy[29853]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:31 node-5 haproxy[29853]: 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 24 21:04:31 node-5 haproxy[29853]: proxy ceilometer has no server available!
<129>Jul 24 21:04:31 node-5 haproxy[29853]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:32 node-5 haproxy[29853]: 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 24 21:04:32 node-5 haproxy[29853]: proxy nova-novncproxy has no server available!
<27>Jul 24 21:04:32 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:32 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:32 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:32 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:32 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:32 node-5 multipathd: uevent trigger error
<129>Jul 24 21:04:34 node-5 haproxy[31013]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:35 node-5 haproxy[31017]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:35 node-5 haproxy[31017]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:35 node-5 haproxy[31017]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:35 node-5 haproxy[31017]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:35 node-5 haproxy[31017]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:35 node-5 haproxy[31017]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:35 node-5 haproxy[31017]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:35 node-5 haproxy[31017]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-5 haproxy[31017]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-5 haproxy[31017]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-5 haproxy[31017]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-5 haproxy[31017]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-5 haproxy[31017]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-5 haproxy[31017]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-5 haproxy[31017]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:36 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 24 21:04:36 node-5 haproxy[31017]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:36 node-5 haproxy[31017]: proxy horizon has no server available!
<27>Jul 24 21:04:37 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:37 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:37 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:37 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:37 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:37 node-5 multipathd: uevent trigger error
<129>Jul 24 21:04:38 node-5 haproxy[31017]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:38 node-5 haproxy[31017]: 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 24 21:04:38 node-5 haproxy[31017]: proxy glance-registry has no server available!
<129>Jul 24 21:04:38 node-5 haproxy[31017]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:38 node-5 haproxy[31017]: 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 24 21:04:38 node-5 haproxy[31017]: proxy aodh has no server available!
<129>Jul 24 21:04:38 node-5 haproxy[31017]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:38 node-5 haproxy[31017]: 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 24 21:04:38 node-5 haproxy[31017]: proxy ceilometer has no server available!
<129>Jul 24 21:04:38 node-5 haproxy[31017]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:38 node-5 haproxy[31017]: 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 24 21:04:38 node-5 haproxy[31017]: proxy nova-novncproxy has no server available!
<129>Jul 24 21:04:40 node-5 haproxy[32215]: Server horizon/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:40 node-5 haproxy[32215]: Server keystone-1/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:40 node-5 haproxy[32215]: Server keystone-2/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-5 haproxy[32219]: Server nova-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-5 haproxy[32219]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-5 haproxy[32219]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-5 haproxy[32219]: Server glance-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-5 haproxy[32219]: Server glance-glare/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-5 haproxy[32219]: Server neutron/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-5 haproxy[32219]: Server glance-registry/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-5 haproxy[32219]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-5 haproxy[32219]: Server object-storage/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-5 haproxy[32219]: Server aodh/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-5 haproxy[32219]: Server ceilometer/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-5 haproxy[32219]: Server heat-api/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-5 haproxy[32219]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-5 haproxy[32219]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-5 haproxy[32219]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-5 haproxy[32219]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-5 haproxy[32219]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:42 node-5 haproxy[32219]: proxy horizon has no server available!
<27>Jul 24 21:04:43 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:43 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:43 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:43 node-5 multipathd: uevent trigger error
<129>Jul 24 21:04:43 node-5 haproxy[32219]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:43 node-5 haproxy[32219]: 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 24 21:04:43 node-5 haproxy[32219]: proxy glance-registry has no server available!
<129>Jul 24 21:04:44 node-5 haproxy[32219]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:44 node-5 haproxy[32219]: 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 24 21:04:44 node-5 haproxy[32219]: proxy aodh has no server available!
<129>Jul 24 21:04:44 node-5 haproxy[32219]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:44 node-5 haproxy[32219]: 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 24 21:04:44 node-5 haproxy[32219]: proxy ceilometer has no server available!
<129>Jul 24 21:04:44 node-5 haproxy[32219]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:44 node-5 haproxy[32219]: 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 24 21:04:44 node-5 haproxy[32219]: proxy nova-novncproxy has no server available!
<27>Jul 24 21:04:46 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:46 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:46 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:46 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:46 node-5 multipathd: uevent trigger error
<27>Jul 24 21:04:46 node-5 multipathd: uevent trigger error
<129>Jul 24 21:04:50 node-5 haproxy[32219]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:50 node-5 haproxy[32219]: Server keystone-1/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 24 21:04:50 node-5 haproxy[32219]: proxy keystone-1 has no server available!
<129>Jul 24 21:04:50 node-5 haproxy[32219]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:50 node-5 haproxy[32219]: 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 24 21:04:50 node-5 haproxy[32219]: proxy keystone-2 has no server available!
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:51 node-5 haproxy[32219]: 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 24 21:04:51 node-5 haproxy[32219]: proxy nova-api has no server available!
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Server nova-metadata-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 24 21:04:51 node-5 haproxy[32219]: proxy nova-metadata-api has no server available!
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Backup Server cinder-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 24 21:04:51 node-5 haproxy[32219]: proxy cinder-api has no server available!
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:51 node-5 haproxy[32219]: 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 24 21:04:51 node-5 haproxy[32219]: proxy glance-api has no server available!
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Server glance-glare/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:51 node-5 haproxy[32219]: proxy glance-glare has no server available!
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:51 node-5 haproxy[32219]: 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 24 21:04:51 node-5 haproxy[32219]: proxy neutron has no server available!
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:51 node-5 haproxy[32219]: 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 24 21:04:51 node-5 haproxy[32219]: proxy mysqld has no server available!
<129>Jul 24 21:04:51 node-5 haproxy[32219]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:51 node-5 haproxy[32219]: 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 24 21:04:51 node-5 haproxy[32219]: proxy object-storage has no server available!
<129>Jul 24 21:04:52 node-5 haproxy[32219]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:52 node-5 haproxy[32219]: 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 24 21:04:52 node-5 haproxy[32219]: proxy heat-api has no server available!
<129>Jul 24 21:04:52 node-5 haproxy[32219]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:52 node-5 haproxy[32219]: 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 24 21:04:52 node-5 haproxy[32219]: proxy heat-api-cfn has no server available!
<129>Jul 24 21:04:52 node-5 haproxy[32219]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:52 node-5 haproxy[32219]: 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 24 21:04:52 node-5 haproxy[32219]: proxy heat-api-cloudwatch has no server available!
<43>Jul 24 21:05:04 node-5 apache2_error [Sun Jul 24 21:05:00.708064 2016] [mpm_event:notice] [pid 3010:tid 140534580471680] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 21:05:04 node-5 apache2_error [Sun Jul 24 21:05:00.708213 2016] [core:notice] [pid 3010:tid 140534580471680] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 21:05:04 node-5 apache2_error [Sun Jul 24 21:05:04.128424 2016] [mpm_event:notice] [pid 3010:tid 140534580471680] AH00491: caught SIGTERM, shutting down
<27>Jul 24 21:05:09 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:09 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:09 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:09 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:09 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:12 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:12 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:12 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:12 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:12 node-5 multipathd: uevent trigger error
<43>Jul 24 21:05:14 node-5 apache2_error [Sun Jul 24 21:05:05.216017 2016] [mpm_worker:notice] [pid 3454:tid 140294578169728] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 21:05:14 node-5 apache2_error [Sun Jul 24 21:05:05.216085 2016] [core:notice] [pid 3454:tid 140294578169728] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 21:05:30 node-5 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 21:05:30 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 21:05:49 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:49 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:49 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:49 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:49 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:49 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:05:53 node-5 multipathd: uevent trigger error
<43>Jul 24 21:05:54 node-5 apache2_error [Sun Jul 24 21:05:46.020870 2016] [mpm_worker:notice] [pid 3454:tid 140294578169728] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 21:05:54 node-5 apache2_error [Sun Jul 24 21:05:46.030255 2016] [mpm_worker:warn] [pid 3454:tid 140294578169728] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 21:05:54 node-5 apache2_error [Sun Jul 24 21:05:46.030691 2016] [mpm_worker:notice] [pid 3454:tid 140294578169728] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 21:05:54 node-5 apache2_error [Sun Jul 24 21:05:46.030699 2016] [core:notice] [pid 3454:tid 140294578169728] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 21:06:06 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 21:06:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:07:20 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 24 21:07:22 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 24 21:08:34 node-5 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 24 21:08:39 node-5 multipathd: uevent trigger error
<27>Jul 24 21:08:39 node-5 multipathd: uevent trigger error
<27>Jul 24 21:08:39 node-5 multipathd: uevent trigger error
<27>Jul 24 21:08:39 node-5 multipathd: uevent trigger error
<27>Jul 24 21:08:39 node-5 multipathd: uevent trigger error
<11>Jul 24 21:09:33 node-5 epmd: epmd: node name already occupied rabbitmq-cli-91
<27>Jul 24 21:09:57 node-5 multipathd: uevent trigger error
<27>Jul 24 21:09:57 node-5 multipathd: uevent trigger error
<27>Jul 24 21:09:58 node-5 multipathd: uevent trigger error
<27>Jul 24 21:09:58 node-5 multipathd: uevent trigger error
<27>Jul 24 21:09:58 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:06 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:06 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:06 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:06 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:06 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:06 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:13 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 24 21:10:21 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:21 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:21 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:21 node-5 multipathd: uevent trigger error
<27>Jul 24 21:10:21 node-5 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-5 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-5 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-5 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-5 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-5 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-5 multipathd: uevent trigger error
<43>Jul 24 21:13:45 node-5 apache2_error [Sun Jul 24 21:13:40.966902 2016] [mpm_worker:notice] [pid 3454:tid 140294578169728] AH00295: caught SIGTERM, shutting down
<43>Jul 24 21:13:45 node-5 apache2_error [Sun Jul 24 21:13:41.721551 2016] [mpm_worker:notice] [pid 16542:tid 140620879660928] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 21:13:45 node-5 apache2_error [Sun Jul 24 21:13:41.721584 2016] [core:notice] [pid 16542:tid 140620879660928] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 21:14:15 node-5 apache2_error [Sun Jul 24 21:14:13.612566 2016] [mpm_worker:notice] [pid 16542:tid 140620879660928] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 21:14:15 node-5 apache2_error [Sun Jul 24 21:14:13.617166 2016] [mpm_worker:warn] [pid 16542:tid 140620879660928] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 21:14:15 node-5 apache2_error [Sun Jul 24 21:14:13.621217 2016] [mpm_worker:notice] [pid 16542:tid 140620879660928] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 21:14:15 node-5 apache2_error [Sun Jul 24 21:14:13.621250 2016] [core:notice] [pid 16542:tid 140620879660928] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 21:14:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:14:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:14:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:14:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:14:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:15:17 node-5 multipathd: uevent trigger error
<27>Jul 24 21:15:17 node-5 multipathd: uevent trigger error
<27>Jul 24 21:15:17 node-5 multipathd: uevent trigger error
<27>Jul 24 21:15:17 node-5 multipathd: uevent trigger error
<27>Jul 24 21:15:17 node-5 multipathd: uevent trigger error
<27>Jul 24 21:15:17 node-5 multipathd: uevent trigger error
<27>Jul 24 21:16:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:16:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:16:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:16:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:16:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:21:05 node-5 multipathd: uevent trigger error
<27>Jul 24 21:21:05 node-5 multipathd: uevent trigger error
<27>Jul 24 21:21:05 node-5 multipathd: uevent trigger error
<27>Jul 24 21:21:05 node-5 multipathd: uevent trigger error
<27>Jul 24 21:21:05 node-5 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-5 multipathd: uevent trigger error
<27>Jul 24 21:23:20 node-5 multipathd: uevent trigger error
<27>Jul 24 21:23:20 node-5 multipathd: uevent trigger error
<27>Jul 24 21:24:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:24:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:24:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:24:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:24:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:03 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:13 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:13 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:13 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:13 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:13 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:25 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Jul 24 21:25:25 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Jul 24 21:25:25 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Jul 24 21:25:26 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Jul 24 21:25:26 node-5 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Jul 24 21:25:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:27 node-5 multipathd: uevent trigger error
<27>Jul 24 21:25:27 node-5 multipathd: uevent trigger error
<43>Jul 24 21:26:16 node-5 apache2_error [Sun Jul 24 21:26:13.594232 2016] [mpm_worker:notice] [pid 16542:tid 140620879660928] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 21:26:16 node-5 apache2_error [Sun Jul 24 21:26:13.980474 2016] [mpm_worker:warn] [pid 16542:tid 140620879660928] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 21:26:16 node-5 apache2_error [Sun Jul 24 21:26:13.984666 2016] [mpm_worker:notice] [pid 16542:tid 140620879660928] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 21:26:16 node-5 apache2_error [Sun Jul 24 21:26:13.984690 2016] [core:notice] [pid 16542:tid 140620879660928] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 21:26:54 node-5 multipathd: uevent trigger error
<27>Jul 24 21:26:54 node-5 multipathd: uevent trigger error
<27>Jul 24 21:26:54 node-5 multipathd: uevent trigger error
<27>Jul 24 21:26:55 node-5 multipathd: uevent trigger error
<27>Jul 24 21:26:55 node-5 multipathd: uevent trigger error
<43>Jul 24 21:26:56 node-5 apache2_error [Sun Jul 24 21:26:50.958889 2016] [mpm_worker:notice] [pid 16542:tid 140620879660928] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 21:26:56 node-5 apache2_error [Sun Jul 24 21:26:51.345178 2016] [mpm_worker:warn] [pid 16542:tid 140620879660928] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 21:26:56 node-5 apache2_error [Sun Jul 24 21:26:51.359113 2016] [mpm_worker:notice] [pid 16542:tid 140620879660928] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 21:26:56 node-5 apache2_error [Sun Jul 24 21:26:51.359152 2016] [core:notice] [pid 16542:tid 140620879660928] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 21:27:13 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:13 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:13 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:13 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:13 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:53 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:54 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:58 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:58 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:58 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:58 node-5 multipathd: uevent trigger error
<27>Jul 24 21:27:58 node-5 multipathd: uevent trigger error
<27>Jul 24 21:28:24 node-5 multipathd: uevent trigger error
<27>Jul 24 21:28:24 node-5 multipathd: uevent trigger error
<27>Jul 24 21:28:24 node-5 multipathd: uevent trigger error
<27>Jul 24 21:28:24 node-5 multipathd: uevent trigger error
<27>Jul 24 21:28:24 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:23 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:23 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:23 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:23 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:33 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:33 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:33 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:33 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:33 node-5 multipathd: uevent trigger error
<11>Jul 24 21:29:42 node-5 liberasurecode[5948]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:42 node-5 liberasurecode[5948]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:42 node-5 liberasurecode[5948]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:42 node-5 liberasurecode[5948]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:42 node-5 liberasurecode[5972]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:42 node-5 liberasurecode[5972]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:42 node-5 liberasurecode[5972]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:42 node-5 liberasurecode[5972]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:45 node-5 liberasurecode[6405]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:45 node-5 liberasurecode[6405]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:45 node-5 liberasurecode[6405]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:45 node-5 liberasurecode[6405]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8372]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8372]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8372]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8372]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8439]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8439]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8439]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8439]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8639]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8639]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8639]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:50 node-5 liberasurecode[8639]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8857]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8857]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8857]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8857]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8903]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8903]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8903]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8903]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8915]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8915]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8915]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8915]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8927]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8927]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:29:51 node-5 liberasurecode[8927]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 21:29:57 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:57 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:57 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:57 node-5 multipathd: uevent trigger error
<27>Jul 24 21:29:57 node-5 multipathd: uevent trigger error
<11>Jul 24 21:30:01 node-5 liberasurecode[12459]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:01 node-5 liberasurecode[12459]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:01 node-5 liberasurecode[12459]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:01 node-5 liberasurecode[12459]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 21:30:02 node-5 multipathd: uevent trigger error
<27>Jul 24 21:30:02 node-5 multipathd: uevent trigger error
<27>Jul 24 21:30:02 node-5 multipathd: uevent trigger error
<27>Jul 24 21:30:03 node-5 multipathd: uevent trigger error
<27>Jul 24 21:30:03 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:10 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:10 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:10 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:11 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:11 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:16 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:16 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:16 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:16 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:16 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:29 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:29 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:29 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:29 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:01 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:01 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:01 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:01 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:01 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:05 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:05 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:05 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:05 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:05 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:10 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:10 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:10 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:10 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:10 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:15 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:20 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:20 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:20 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:20 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:20 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:25 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:25 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:25 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:25 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:25 node-5 multipathd: uevent trigger error
<27>Jul 24 21:33:31 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 21:33:31 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Jul 24 21:35:02 node-5 liberasurecode[32277]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:35:02 node-5 liberasurecode[32277]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:35:02 node-5 liberasurecode[32277]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:35:02 node-5 liberasurecode[32277]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
