Jul 30 20:35:52 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8370" x-info="http://www.rsyslog.com"] start
Jul 30 20:35:52 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 30 20:35:52 node-5 rsyslogd: rsyslogd's groupid changed to 104
Jul 30 20:35:52 node-5 rsyslogd: rsyslogd's userid changed to 101
Jul 30 20:35:52 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 30 20:35:52 node-5 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 30 20:35:52 node-5 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 30 20:35:52 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 30 20:35:52 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=ca26f6af-2f05-437d-b34b-d9e008c02ce6 nomdmonddf nomdmonisw
Jul 30 20:35:52 node-5 kernel: [    0.000000] KERNEL supported cpus:
Jul 30 20:35:52 node-5 kernel: [    0.000000]   Intel GenuineIntel
Jul 30 20:35:52 node-5 kernel: [    0.000000]   AMD AuthenticAMD
Jul 30 20:35:52 node-5 kernel: [    0.000000]   Centaur CentaurHauls
Jul 30 20:35:52 node-5 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 30 20:35:52 node-5 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 30 20:35:52 node-5 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 30 20:35:52 node-5 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 30 20:35:52 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 30 20:35:52 node-5 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 30 20:35:52 node-5 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 30 20:35:52 node-5 kernel: [    0.000000] No AGP bridge found
Jul 30 20:35:52 node-5 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 30 20:35:52 node-5 kernel: [    0.000000] MTRR default type: write-back
Jul 30 20:35:52 node-5 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 30 20:35:52 node-5 kernel: [    0.000000]   00000-9FFFF write-back
Jul 30 20:35:52 node-5 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 30 20:35:52 node-5 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 30 20:35:52 node-5 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 30 20:35:52 node-5 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 30 20:35:52 node-5 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 30 20:35:52 node-5 kernel: [    0.000000]   2 disabled
Jul 30 20:35:52 node-5 kernel: [    0.000000]   3 disabled
Jul 30 20:35:52 node-5 kernel: [    0.000000]   4 disabled
Jul 30 20:35:52 node-5 kernel: [    0.000000]   5 disabled
Jul 30 20:35:52 node-5 kernel: [    0.000000]   6 disabled
Jul 30 20:35:52 node-5 kernel: [    0.000000]   7 disabled
Jul 30 20:35:52 node-5 kernel: [    0.000000]   8 disabled
Jul 30 20:35:52 node-5 kernel: [    0.000000]   9 disabled
Jul 30 20:35:52 node-5 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 30 20:35:52 node-5 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 30 20:35:52 node-5 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 30 20:35:52 node-5 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 30 20:35:52 node-5 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 30 20:35:52 node-5 kernel: [    0.000000] Using GB pages for direct mapping
Jul 30 20:35:52 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 30 20:35:52 node-5 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 30 20:35:52 node-5 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 30 20:35:52 node-5 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 30 20:35:52 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 30 20:35:52 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 30 20:35:52 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 30 20:35:52 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 30 20:35:52 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 30 20:35:52 node-5 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 30 20:35:52 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 30 20:35:52 node-5 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 30 20:35:52 node-5 kernel: [    0.000000] RAMDISK: [mem 0x35826000-0x36c0afff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 30 20:35:52 node-5 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 30 20:35:52 node-5 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 30 20:35:52 node-5 kernel: [    0.000000] Zone ranges:
Jul 30 20:35:52 node-5 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] Movable zone start for each node
Jul 30 20:35:52 node-5 kernel: [    0.000000] Early memory node ranges
Jul 30 20:35:52 node-5 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 30 20:35:52 node-5 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 30 20:35:52 node-5 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 30 20:35:52 node-5 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 30 20:35:52 node-5 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 30 20:35:52 node-5 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 30 20:35:52 node-5 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 30 20:35:52 node-5 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 30 20:35:52 node-5 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 30 20:35:52 node-5 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 30 20:35:52 node-5 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 30 20:35:52 node-5 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 30 20:35:52 node-5 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 30 20:35:52 node-5 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 30 20:35:52 node-5 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 30 20:35:52 node-5 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 30 20:35:52 node-5 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 30 20:35:52 node-5 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 30 20:35:52 node-5 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 30 20:35:52 node-5 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 30 20:35:52 node-5 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 30 20:35:52 node-5 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 30 20:35:52 node-5 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 30 20:35:52 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 30 20:35:52 node-5 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 30 20:35:52 node-5 kernel: [    0.000000] Policy zone: Normal
Jul 30 20:35:52 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=ca26f6af-2f05-437d-b34b-d9e008c02ce6 nomdmonddf nomdmonisw
Jul 30 20:35:52 node-5 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 30 20:35:52 node-5 kernel: [    0.000000] Checking aperture...
Jul 30 20:35:52 node-5 kernel: [    0.000000] No AGP bridge found
Jul 30 20:35:52 node-5 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 30 20:35:52 node-5 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 30 20:35:52 node-5 kernel: [    0.000000] Memory: 32653464K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627172K reserved)
Jul 30 20:35:52 node-5 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 30 20:35:52 node-5 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 30 20:35:52 node-5 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 30 20:35:52 node-5 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 30 20:35:52 node-5 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 30 20:35:52 node-5 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 30 20:35:52 node-5 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 30 20:35:52 node-5 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 30 20:35:52 node-5 kernel: [    0.000000] console [tty0] enabled
Jul 30 20:35:52 node-5 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 30 20:35:52 node-5 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 30 20:35:52 node-5 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 30 20:35:52 node-5 kernel: [    0.000000] hpet clockevent registered
Jul 30 20:35:52 node-5 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 30 20:35:52 node-5 kernel: [    0.004000] tsc: Detected 3492.228 MHz processor
Jul 30 20:35:52 node-5 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.45 BogoMIPS (lpj=13968912)
Jul 30 20:35:52 node-5 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 30 20:35:52 node-5 kernel: [    0.000044] Security Framework initialized
Jul 30 20:35:52 node-5 kernel: [    0.000062] AppArmor: AppArmor initialized
Jul 30 20:35:52 node-5 kernel: [    0.000063] Yama: becoming mindful.
Jul 30 20:35:52 node-5 kernel: [    0.001453] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.006367] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.008298] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.008325] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.008615] Initializing cgroup subsys memory
Jul 30 20:35:52 node-5 kernel: [    0.008623] Initializing cgroup subsys devices
Jul 30 20:35:52 node-5 kernel: [    0.008625] Initializing cgroup subsys freezer
Jul 30 20:35:52 node-5 kernel: [    0.008627] Initializing cgroup subsys blkio
Jul 30 20:35:52 node-5 kernel: [    0.008628] Initializing cgroup subsys perf_event
Jul 30 20:35:52 node-5 kernel: [    0.008631] Initializing cgroup subsys hugetlb
Jul 30 20:35:52 node-5 kernel: [    0.008650] CPU: Physical Processor ID: 0
Jul 30 20:35:52 node-5 kernel: [    0.008651] CPU: Processor Core ID: 0
Jul 30 20:35:52 node-5 kernel: [    0.008655] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 30 20:35:52 node-5 kernel: [    0.008655] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 30 20:35:52 node-5 kernel: [    0.009348] mce: CPU supports 22 MCE banks
Jul 30 20:35:52 node-5 kernel: [    0.009376] CPU0: Thermal monitoring enabled (TM1)
Jul 30 20:35:52 node-5 kernel: [    0.009397] process: using mwait in idle threads
Jul 30 20:35:52 node-5 kernel: [    0.009400] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 30 20:35:52 node-5 kernel: [    0.009400] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 30 20:35:52 node-5 kernel: [    0.009400] tlb_flushall_shift: 6
Jul 30 20:35:52 node-5 kernel: [    0.009489] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 30 20:35:52 node-5 kernel: [    0.010215] ACPI: Core revision 20131115
Jul 30 20:35:52 node-5 kernel: [    0.022872] ACPI: All ACPI Tables successfully acquired
Jul 30 20:35:52 node-5 kernel: [    0.023035] ftrace: allocating 28617 entries in 112 pages
Jul 30 20:35:52 node-5 kernel: [    0.031845] dmar: Host address width 46
Jul 30 20:35:52 node-5 kernel: [    0.031847] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 30 20:35:52 node-5 kernel: [    0.031853] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 30 20:35:52 node-5 kernel: [    0.031855] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 30 20:35:52 node-5 kernel: [    0.031859] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 30 20:35:52 node-5 kernel: [    0.031860] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 30 20:35:52 node-5 kernel: [    0.031862] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 30 20:35:52 node-5 kernel: [    0.031863] dmar: ATSR flags: 0x0
Jul 30 20:35:52 node-5 kernel: [    0.031864] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 30 20:35:52 node-5 kernel: [    0.031865] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 30 20:35:52 node-5 kernel: [    0.031981] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 30 20:35:52 node-5 kernel: [    0.031982] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 30 20:35:52 node-5 kernel: [    0.031983] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 30 20:35:52 node-5 kernel: [    0.031984] HPET id 0 under DRHD base 0xc7ffc000
Jul 30 20:35:52 node-5 kernel: [    0.031985] Your BIOS is broken and requested that x2apic be disabled.
Jul 30 20:35:52 node-5 kernel: [    0.031985] This will slightly decrease performance.
Jul 30 20:35:52 node-5 kernel: [    0.031985] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 30 20:35:52 node-5 kernel: [    0.032417] Enabled IRQ remapping in xapic mode
Jul 30 20:35:52 node-5 kernel: [    0.032419] x2apic not enabled, IRQ remapping is in xapic mode
Jul 30 20:35:52 node-5 kernel: [    0.032422] Switched APIC routing to physical flat.
Jul 30 20:35:52 node-5 kernel: [    0.033047] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 30 20:35:52 node-5 kernel: [    0.072700] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 30 20:35:52 node-5 kernel: [    0.072706] TSC deadline timer enabled
Jul 30 20:35:52 node-5 kernel: [    0.072713] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 30 20:35:52 node-5 kernel: [    0.072719] ... version:                3
Jul 30 20:35:52 node-5 kernel: [    0.072720] ... bit width:              48
Jul 30 20:35:52 node-5 kernel: [    0.072721] ... generic registers:      4
Jul 30 20:35:52 node-5 kernel: [    0.072722] ... value mask:             0000ffffffffffff
Jul 30 20:35:52 node-5 kernel: [    0.072723] ... max period:             0000ffffffffffff
Jul 30 20:35:52 node-5 kernel: [    0.072724] ... fixed-purpose events:   3
Jul 30 20:35:52 node-5 kernel: [    0.072725] ... event mask:             000000070000000f
Jul 30 20:35:52 node-5 kernel: [    0.074168] x86: Booting SMP configuration:
Jul 30 20:35:52 node-5 kernel: [    0.088273] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 30 20:35:52 node-5 kernel: [    0.074170] .... node  #0, CPUs:        #1  #2  #3
Jul 30 20:35:52 node-5 kernel: [    0.116183] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 30 20:35:52 node-5 kernel: [    0.270151] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 30 20:35:52 node-5 kernel: [    0.325778] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 30 20:35:52 node-5 kernel: [    0.382437] x86: Booted up 2 nodes, 16 CPUs
Jul 30 20:35:52 node-5 kernel: [    0.382441] smpboot: Total of 16 processors activated (111763.48 BogoMIPS)
Jul 30 20:35:52 node-5 kernel: [    0.406469] devtmpfs: initialized
Jul 30 20:35:52 node-5 kernel: [    0.409572] EVM: security.selinux
Jul 30 20:35:52 node-5 kernel: [    0.409574] EVM: security.SMACK64
Jul 30 20:35:52 node-5 kernel: [    0.409575] EVM: security.ima
Jul 30 20:35:52 node-5 kernel: [    0.409576] EVM: security.capability
Jul 30 20:35:52 node-5 kernel: [    0.409625] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.410302] pinctrl core: initialized pinctrl subsystem
Jul 30 20:35:52 node-5 kernel: [    0.410362] regulator-dummy: no parameters
Jul 30 20:35:52 node-5 kernel: [    0.410393] RTC time: 20:35:16, date: 07/30/16
Jul 30 20:35:52 node-5 kernel: [    0.410427] NET: Registered protocol family 16
Jul 30 20:35:52 node-5 kernel: [    0.410509] cpuidle: using governor ladder
Jul 30 20:35:52 node-5 kernel: [    0.410510] cpuidle: using governor menu
Jul 30 20:35:52 node-5 kernel: [    0.410543] ACPI: bus type PCI registered
Jul 30 20:35:52 node-5 kernel: [    0.410545] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 30 20:35:52 node-5 kernel: [    0.410590] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 30 20:35:52 node-5 kernel: [    0.410593] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 30 20:35:52 node-5 kernel: [    0.424319] PCI: Using configuration type 1 for base access
Jul 30 20:35:52 node-5 kernel: [    0.425320] bio: create slab <bio-0> at 0
Jul 30 20:35:52 node-5 kernel: [    0.425600] ACPI: Added _OSI(Module Device)
Jul 30 20:35:52 node-5 kernel: [    0.425602] ACPI: Added _OSI(Processor Device)
Jul 30 20:35:52 node-5 kernel: [    0.425603] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 30 20:35:52 node-5 kernel: [    0.425604] ACPI: Added _OSI(Processor Aggregator Device)
Jul 30 20:35:52 node-5 kernel: [    0.438212] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 30 20:35:52 node-5 kernel: [    0.448731] ACPI: Interpreter enabled
Jul 30 20:35:52 node-5 kernel: [    0.448736] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 30 20:35:52 node-5 kernel: [    0.448740] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 30 20:35:52 node-5 kernel: [    0.448743] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 30 20:35:52 node-5 kernel: [    0.448750] ACPI: (supports S0 S4 S5)
Jul 30 20:35:52 node-5 kernel: [    0.448751] ACPI: Using IOAPIC for interrupt routing
Jul 30 20:35:52 node-5 kernel: [    0.448794] HEST: Table parsing has been initialized.
Jul 30 20:35:52 node-5 kernel: [    0.448796] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 30 20:35:52 node-5 kernel: [    0.449347] ACPI: No dock devices found.
Jul 30 20:35:52 node-5 kernel: [    0.460948] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 30 20:35:52 node-5 kernel: [    0.460953] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 20:35:52 node-5 kernel: [    0.460956] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 30 20:35:52 node-5 kernel: [    0.460988] PCI host bridge to bus 0000:ff
Jul 30 20:35:52 node-5 kernel: [    0.460990] pci_bus 0000:ff: root bus resource [bus ff]
Jul 30 20:35:52 node-5 kernel: [    0.460998] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461037] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.461067] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461102] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461132] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.461161] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.461192] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461220] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461251] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461278] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461304] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461330] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461358] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461384] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461410] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461436] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461464] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461491] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461517] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.461545] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461571] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.461596] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461622] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461651] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.461685] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461716] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461745] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461776] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461806] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461836] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461868] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461900] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461930] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461963] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.461994] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462024] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462055] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462085] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462113] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462145] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462178] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462215] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462250] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462283] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462313] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462344] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462373] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462402] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462432] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462463] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462494] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462524] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462551] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462580] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462609] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462640] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462671] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462727] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 30 20:35:52 node-5 kernel: [    0.462730] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 20:35:52 node-5 kernel: [    0.462733] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 30 20:35:52 node-5 kernel: [    0.462750] PCI host bridge to bus 0000:7f
Jul 30 20:35:52 node-5 kernel: [    0.462751] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 30 20:35:52 node-5 kernel: [    0.462756] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462783] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.462811] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462840] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462861] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.462885] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.462910] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462936] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462958] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.462980] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463008] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463031] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463056] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463078] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463101] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463127] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463148] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463171] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463193] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.463216] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463238] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.463260] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463282] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463307] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 30 20:35:52 node-5 kernel: [    0.463340] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463367] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463394] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463421] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463446] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463471] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463497] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463524] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463548] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463575] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463602] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463629] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463657] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463683] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463708] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463737] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463762] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463789] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463819] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463845] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463870] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463894] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463919] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463946] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.463974] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.464000] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.464029] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.464054] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.464076] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.464101] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.464126] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.464154] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.464179] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.465419] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 30 20:35:52 node-5 kernel: [    0.465423] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 20:35:52 node-5 kernel: [    0.466540] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 30 20:35:52 node-5 kernel: [    0.467051] PCI host bridge to bus 0000:00
Jul 30 20:35:52 node-5 kernel: [    0.467054] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 30 20:35:52 node-5 kernel: [    0.467055] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 30 20:35:52 node-5 kernel: [    0.467057] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 30 20:35:52 node-5 kernel: [    0.467058] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 30 20:35:52 node-5 kernel: [    0.467059] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 30 20:35:52 node-5 kernel: [    0.467061] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 30 20:35:52 node-5 kernel: [    0.467062] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 30 20:35:52 node-5 kernel: [    0.467068] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 30 20:35:52 node-5 kernel: [    0.467150] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.467181] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.467222] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-5 kernel: [    0.467241] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.467270] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.467310] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-5 kernel: [    0.467328] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.467357] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.467397] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-5 kernel: [    0.467414] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.467483] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.467560] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.467635] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 30 20:35:52 node-5 kernel: [    0.467640] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 30 20:35:52 node-5 kernel: [    0.467724] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 30 20:35:52 node-5 kernel: [    0.467872] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 30 20:35:52 node-5 kernel: [    0.467889] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 30 20:35:52 node-5 kernel: [    0.467967] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.468020] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-5 kernel: [    0.468041] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.468097] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.468140] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-5 kernel: [    0.468167] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.468223] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.468266] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 30 20:35:52 node-5 kernel: [    0.468290] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 30 20:35:52 node-5 kernel: [    0.468307] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 30 20:35:52 node-5 kernel: [    0.468385] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.468434] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 30 20:35:52 node-5 kernel: [    0.468461] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 30 20:35:52 node-5 kernel: [    0.468707] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 30 20:35:52 node-5 kernel: [    0.468713] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 30 20:35:52 node-5 kernel: [    0.468719] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.468725] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.468732] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 30 20:35:52 node-5 kernel: [    0.468762] pci 0000:01:00.0: supports D1 D2
Jul 30 20:35:52 node-5 kernel: [    0.479009] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 30 20:35:52 node-5 kernel: [    0.479015] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 30 20:35:52 node-5 kernel: [    0.479020] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 30 20:35:52 node-5 kernel: [    0.479281] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.479341] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 30 20:35:52 node-5 kernel: [    0.491005] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 30 20:35:52 node-5 kernel: [    0.491011] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.491015] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-5 kernel: [    0.491099] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.491181] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.491257] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.491302] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 30 20:35:52 node-5 kernel: [    0.491305] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.491307] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-5 kernel: [    0.491359] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.491481] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.491534] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 30 20:35:52 node-5 kernel: [    0.491537] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.491539] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-5 kernel: [    0.491588] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.491723] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.491763] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.491883] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.491920] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.492040] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.492077] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 30 20:35:52 node-5 kernel: [    0.492198] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 30 20:35:52 node-5 kernel: [    0.492241] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 30 20:35:52 node-5 kernel: [    0.492243] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.492245] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-5 kernel: [    0.492305] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 30 20:35:52 node-5 kernel: [    0.492367] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.492420] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.492461] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 30 20:35:52 node-5 kernel: [    0.492543] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 30 20:35:52 node-5 kernel: [    0.492648] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 30 20:35:52 node-5 kernel: [    0.492651] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.492653] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 30 20:35:52 node-5 kernel: [    0.492729] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 30 20:35:52 node-5 kernel: [    0.492790] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.492839] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.493051] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 30 20:35:52 node-5 kernel: [    0.493055] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 30 20:35:52 node-5 kernel: [    0.493118] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 30 20:35:52 node-5 kernel: [    0.493171] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.493220] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.493430] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 30 20:35:52 node-5 kernel: [    0.493434] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 30 20:35:52 node-5 kernel: [    0.493493] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 30 20:35:52 node-5 kernel: [    0.493553] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.493605] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 30 20:35:52 node-5 kernel: [    0.493854] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 30 20:35:52 node-5 kernel: [    0.493858] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 30 20:35:52 node-5 kernel: [    0.494032] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 30 20:35:52 node-5 kernel: [    0.494070] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 30 20:35:52 node-5 kernel: [    0.494147] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 30 20:35:52 node-5 kernel: [    0.494166] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 30 20:35:52 node-5 kernel: [    0.494179] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 30 20:35:52 node-5 kernel: [    0.494192] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 30 20:35:52 node-5 kernel: [    0.494242] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 30 20:35:52 node-5 kernel: [    0.499017] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 30 20:35:52 node-5 kernel: [    0.499026] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 30 20:35:52 node-5 kernel: [    0.499078] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 30 20:35:52 node-5 kernel: [    0.499699] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 30 20:35:52 node-5 kernel: [    0.499702] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 30 20:35:52 node-5 kernel: [    0.499822] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 30 20:35:52 node-5 kernel: [    0.499930] PCI host bridge to bus 0000:80
Jul 30 20:35:52 node-5 kernel: [    0.499932] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 30 20:35:52 node-5 kernel: [    0.499933] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 30 20:35:52 node-5 kernel: [    0.499935] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 30 20:35:52 node-5 kernel: [    0.499943] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.500005] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.500075] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 30 20:35:52 node-5 kernel: [    0.500136] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 30 20:35:52 node-5 kernel: [    0.500141] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 30 20:35:52 node-5 kernel: [    0.500213] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 30 20:35:52 node-5 kernel: [    0.500510] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 30 20:35:52 node-5 kernel: [    0.500542] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 30 20:35:52 node-5 kernel: [    0.500571] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 30 20:35:52 node-5 kernel: [    0.500600] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 30 20:35:52 node-5 kernel: [    0.500630] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 20:35:52 node-5 kernel: [    0.500659] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 20:35:52 node-5 kernel: [    0.500689] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 20:35:52 node-5 kernel: [    0.500719] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 30 20:35:52 node-5 kernel: [    0.500803] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 30 20:35:52 node-5 kernel: [    0.500807] ACPI: \_SB_.UNC1: notify handler is installed
Jul 30 20:35:52 node-5 kernel: [    0.500808] ACPI: \_SB_.UNC0: notify handler is installed
Jul 30 20:35:52 node-5 kernel: [    0.500823] ACPI: \_SB_.PCI0: notify handler is installed
Jul 30 20:35:52 node-5 kernel: [    0.500876] ACPI: \_SB_.PCI1: notify handler is installed
Jul 30 20:35:52 node-5 kernel: [    0.500955] Found 4 acpi root devices
Jul 30 20:35:52 node-5 kernel: [    0.501061] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 30 20:35:52 node-5 kernel: [    0.501063] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 30 20:35:52 node-5 kernel: [    0.501064] vgaarb: loaded
Jul 30 20:35:52 node-5 kernel: [    0.501065] vgaarb: bridge control possible 0000:0c:00.0
Jul 30 20:35:52 node-5 kernel: [    0.501179] SCSI subsystem initialized
Jul 30 20:35:52 node-5 kernel: [    0.501243] libata version 3.00 loaded.
Jul 30 20:35:52 node-5 kernel: [    0.501258] ACPI: bus type USB registered
Jul 30 20:35:52 node-5 kernel: [    0.501268] usbcore: registered new interface driver usbfs
Jul 30 20:35:52 node-5 kernel: [    0.501273] usbcore: registered new interface driver hub
Jul 30 20:35:52 node-5 kernel: [    0.501296] usbcore: registered new device driver usb
Jul 30 20:35:52 node-5 kernel: [    0.501463] PCI: Using ACPI for IRQ routing
Jul 30 20:35:52 node-5 kernel: [    0.505082] PCI: pci_cache_line_size set to 64 bytes
Jul 30 20:35:52 node-5 kernel: [    0.505284] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 30 20:35:52 node-5 kernel: [    0.505285] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 30 20:35:52 node-5 kernel: [    0.505286] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 30 20:35:52 node-5 kernel: [    0.505351] NetLabel: Initializing
Jul 30 20:35:52 node-5 kernel: [    0.505353] NetLabel:  domain hash size = 128
Jul 30 20:35:52 node-5 kernel: [    0.505353] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 30 20:35:52 node-5 kernel: [    0.505363] NetLabel:  unlabeled traffic allowed by default
Jul 30 20:35:52 node-5 kernel: [    0.505431] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 30 20:35:52 node-5 kernel: [    0.505435] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 30 20:35:52 node-5 kernel: [    0.507490] Switched to clocksource hpet
Jul 30 20:35:52 node-5 kernel: [    0.511460] AppArmor: AppArmor Filesystem Enabled
Jul 30 20:35:52 node-5 kernel: [    0.511475] pnp: PnP ACPI init
Jul 30 20:35:52 node-5 kernel: [    0.511487] ACPI: bus type PNP registered
Jul 30 20:35:52 node-5 kernel: [    0.511596] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 30 20:35:52 node-5 kernel: [    0.511604] pnp 00:01: [dma 4]
Jul 30 20:35:52 node-5 kernel: [    0.511615] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 30 20:35:52 node-5 kernel: [    0.511642] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 30 20:35:52 node-5 kernel: [    0.511661] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 30 20:35:52 node-5 kernel: [    0.511679] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 30 20:35:52 node-5 kernel: [    0.511712] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 30 20:35:52 node-5 kernel: [    0.511766] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511768] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 30 20:35:52 node-5 kernel: [    0.511770] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511771] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511773] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511777] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511780] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 30 20:35:52 node-5 kernel: [    0.511781] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511783] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511784] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511786] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511787] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511789] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 30 20:35:52 node-5 kernel: [    0.511791] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 30 20:35:52 node-5 kernel: [    0.511874] pnp 00:07: [dma 0 disabled]
Jul 30 20:35:52 node-5 kernel: [    0.511902] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 30 20:35:52 node-5 kernel: [    0.511977] pnp 00:08: [dma 0 disabled]
Jul 30 20:35:52 node-5 kernel: [    0.512008] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 30 20:35:52 node-5 kernel: [    0.512059] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 30 20:35:52 node-5 kernel: [    0.512405] pnp: PnP ACPI: found 10 devices
Jul 30 20:35:52 node-5 kernel: [    0.512406] ACPI: bus type PNP unregistered
Jul 30 20:35:52 node-5 kernel: [    0.518772] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 30 20:35:52 node-5 kernel: [    0.518776] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 30 20:35:52 node-5 kernel: [    0.518778] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 30 20:35:52 node-5 kernel: [    0.518782] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 30 20:35:52 node-5 kernel: [    0.518784] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.518799] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 30 20:35:52 node-5 kernel: [    0.518828] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 30 20:35:52 node-5 kernel: [    0.518842] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 30 20:35:52 node-5 kernel: [    0.518871] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 30 20:35:52 node-5 kernel: [    0.518885] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 30 20:35:52 node-5 kernel: [    0.518914] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 30 20:35:52 node-5 kernel: [    0.518929] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 30 20:35:52 node-5 kernel: [    0.518957] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 30 20:35:52 node-5 kernel: [    0.518959] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.518974] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-5 kernel: [    0.519003] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 30 20:35:52 node-5 kernel: [    0.519005] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.519019] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-5 kernel: [    0.519051] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 30 20:35:52 node-5 kernel: [    0.519053] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.519056] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-5 kernel: [    0.519060] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 30 20:35:52 node-5 kernel: [    0.519061] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.519064] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-5 kernel: [    0.519067] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 30 20:35:52 node-5 kernel: [    0.519072] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 30 20:35:52 node-5 kernel: [    0.519080] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 30 20:35:52 node-5 kernel: [    0.519084] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 30 20:35:52 node-5 kernel: [    0.519090] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 30 20:35:52 node-5 kernel: [    0.519091] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 30 20:35:52 node-5 kernel: [    0.519092] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 30 20:35:52 node-5 kernel: [    0.519093] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 30 20:35:52 node-5 kernel: [    0.519094] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 30 20:35:52 node-5 kernel: [    0.519094] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 30 20:35:52 node-5 kernel: [    0.519095] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 30 20:35:52 node-5 kernel: [    0.519096] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 30 20:35:52 node-5 kernel: [    0.519097] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.519098] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-5 kernel: [    0.519099] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.519100] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 30 20:35:52 node-5 kernel: [    0.519101] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.519102] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-5 kernel: [    0.519102] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.519103] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 30 20:35:52 node-5 kernel: [    0.519104] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 30 20:35:52 node-5 kernel: [    0.519105] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 30 20:35:52 node-5 kernel: [    0.519106] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 30 20:35:52 node-5 kernel: [    0.519107] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 30 20:35:52 node-5 kernel: [    0.519108] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 30 20:35:52 node-5 kernel: [    0.519109] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 30 20:35:52 node-5 kernel: [    0.519111] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 30 20:35:52 node-5 kernel: [    0.519112] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 30 20:35:52 node-5 kernel: [    0.519153] NET: Registered protocol family 2
Jul 30 20:35:52 node-5 kernel: [    0.519411] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.519751] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.519897] TCP: Hash tables configured (established 262144 bind 65536)
Jul 30 20:35:52 node-5 kernel: [    0.519940] TCP: reno registered
Jul 30 20:35:52 node-5 kernel: [    0.519968] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.520063] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.520209] NET: Registered protocol family 1
Jul 30 20:35:52 node-5 kernel: [    0.555591] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 30 20:35:52 node-5 kernel: [    0.555604] PCI: CLS 64 bytes, default 64
Jul 30 20:35:52 node-5 kernel: [    0.555679] Trying to unpack rootfs image as initramfs...
Jul 30 20:35:52 node-5 kernel: [    0.774799] Freeing initrd memory: 20372K (ffff880035826000 - ffff880036c0b000)
Jul 30 20:35:52 node-5 kernel: [    0.774835] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 30 20:35:52 node-5 kernel: [    0.774837] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 30 20:35:52 node-5 kernel: [    0.775242] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775248] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775253] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775258] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775278] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775296] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775312] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775328] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775339] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775349] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775355] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775362] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775371] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775384] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775397] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775410] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 30 20:35:52 node-5 kernel: [    0.775521] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 30 20:35:52 node-5 kernel: [    0.775527] Scanning for low memory corruption every 60 seconds
Jul 30 20:35:52 node-5 kernel: [    0.775972] Initialise system trusted keyring
Jul 30 20:35:52 node-5 kernel: [    0.776026] audit: initializing netlink socket (disabled)
Jul 30 20:35:52 node-5 kernel: [    0.776041] type=2000 audit(1469910915.732:1): initialized
Jul 30 20:35:52 node-5 kernel: [    0.793937] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 30 20:35:52 node-5 kernel: [    0.795468] zbud: loaded
Jul 30 20:35:52 node-5 kernel: [    0.795595] VFS: Disk quotas dquot_6.5.2
Jul 30 20:35:52 node-5 kernel: [    0.795631] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 30 20:35:52 node-5 kernel: [    0.795999] fuse init (API version 7.22)
Jul 30 20:35:52 node-5 kernel: [    0.796061] msgmni has been set to 32768
Jul 30 20:35:52 node-5 kernel: [    0.796110] Key type big_key registered
Jul 30 20:35:52 node-5 kernel: [    0.796636] Key type asymmetric registered
Jul 30 20:35:52 node-5 kernel: [    0.796638] Asymmetric key parser 'x509' registered
Jul 30 20:35:52 node-5 kernel: [    0.796659] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 30 20:35:52 node-5 kernel: [    0.796729] io scheduler noop registered
Jul 30 20:35:52 node-5 kernel: [    0.796731] io scheduler deadline registered (default)
Jul 30 20:35:52 node-5 kernel: [    0.796749] io scheduler cfq registered
Jul 30 20:35:52 node-5 kernel: [    0.797297] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    0.797440] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    0.797557] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    0.797667] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    0.797781] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    0.797877] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    0.798257] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 30 20:35:52 node-5 kernel: [    0.798283] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 30 20:35:52 node-5 kernel: [    0.798299] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 30 20:35:52 node-5 kernel: [    0.798307] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798310] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798312] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 30 20:35:52 node-5 kernel: [    0.798317] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798319] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798320] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798322] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798323] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798325] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798326] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798327] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798328] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798330] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798331] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798332] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798334] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 30 20:35:52 node-5 kernel: [    0.798339] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798341] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 30 20:35:52 node-5 kernel: [    0.798354] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798357] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 30 20:35:52 node-5 kernel: [    0.798367] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798369] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 30 20:35:52 node-5 kernel: [    0.798372] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 30 20:35:52 node-5 kernel: [    0.798408] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 30 20:35:52 node-5 kernel: [    0.798414] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 30 20:35:52 node-5 kernel: [    0.798418] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 30 20:35:52 node-5 kernel: [    0.798428] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 30 20:35:52 node-5 kernel: [    0.798468] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 30 20:35:52 node-5 kernel: [    0.798469] vesafb: scrolling: redraw
Jul 30 20:35:52 node-5 kernel: [    0.798470] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 30 20:35:52 node-5 kernel: [    0.819158] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 30 20:35:52 node-5 kernel: [    0.827664] Console: switching to colour frame buffer device 80x30
Jul 30 20:35:52 node-5 kernel: [    0.836332] fb0: VESA VGA frame buffer device
Jul 30 20:35:52 node-5 kernel: [    0.836527] intel_idle: MWAIT substates: 0x2120
Jul 30 20:35:52 node-5 kernel: [    0.836528] intel_idle: v0.4 model 0x3F
Jul 30 20:35:52 node-5 kernel: [    0.836529] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 30 20:35:52 node-5 kernel: [    0.836768] ipmi message handler version 39.2
Jul 30 20:35:52 node-5 kernel: [    0.837035] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 30 20:35:52 node-5 kernel: [    0.837467] ACPI: AC Adapter [P111] (on-line)
Jul 30 20:35:52 node-5 kernel: [    0.842688] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 30 20:35:52 node-5 kernel: [    0.853687] ACPI: Power Button [PWRB]
Jul 30 20:35:52 node-5 kernel: [    0.859445] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 30 20:35:52 node-5 kernel: [    0.871069] ACPI: Power Button [PWRF]
Jul 30 20:35:52 node-5 kernel: [    0.896987] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 30 20:35:52 node-5 kernel: [    0.908638] pstore: Registered erst as persistent store backend
Jul 30 20:35:52 node-5 kernel: [    0.914824] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 30 20:35:52 node-5 kernel: [    0.926775] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 30 20:35:52 node-5 kernel: [    0.953510] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 30 20:35:52 node-5 kernel: [    0.986875] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 30 20:35:52 node-5 kernel: [    1.000948] Linux agpgart interface v0.103
Jul 30 20:35:52 node-5 kernel: [    1.008558] brd: module loaded
Jul 30 20:35:52 node-5 kernel: [    1.015583] loop: module loaded
Jul 30 20:35:52 node-5 kernel: [    1.022307] libphy: Fixed MDIO Bus: probed
Jul 30 20:35:52 node-5 kernel: [    1.028771] tun: Universal TUN/TAP device driver, 1.6
Jul 30 20:35:52 node-5 kernel: [    1.035237] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 30 20:35:52 node-5 kernel: [    1.041761] PPP generic driver version 2.4.2
Jul 30 20:35:52 node-5 kernel: [    1.048150] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 30 20:35:52 node-5 kernel: [    1.054581] ehci-pci: EHCI PCI platform driver
Jul 30 20:35:52 node-5 kernel: [    1.061093] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 30 20:35:52 node-5 kernel: [    1.067502] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 30 20:35:52 node-5 kernel: [    1.080010] ehci-pci 0000:00:1a.0: debug port 2
Jul 30 20:35:52 node-5 kernel: [    1.090182] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 30 20:35:52 node-5 kernel: [    1.090201] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 30 20:35:52 node-5 kernel: [    1.106988] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 30 20:35:52 node-5 kernel: [    1.113053] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 30 20:35:52 node-5 kernel: [    1.119223] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 30 20:35:52 node-5 kernel: [    1.131114] usb usb1: Product: EHCI Host Controller
Jul 30 20:35:52 node-5 kernel: [    1.137131] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 30 20:35:52 node-5 kernel: [    1.143159] usb usb1: SerialNumber: 0000:00:1a.0
Jul 30 20:35:52 node-5 kernel: [    1.149099] hub 1-0:1.0: USB hub found
Jul 30 20:35:52 node-5 kernel: [    1.154853] hub 1-0:1.0: 2 ports detected
Jul 30 20:35:52 node-5 kernel: [    1.160609] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 30 20:35:52 node-5 kernel: [    1.166175] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 30 20:35:52 node-5 kernel: [    1.177036] ehci-pci 0000:00:1d.0: debug port 2
Jul 30 20:35:52 node-5 kernel: [    1.186321] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 30 20:35:52 node-5 kernel: [    1.186324] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 30 20:35:52 node-5 kernel: [    1.202906] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 30 20:35:52 node-5 kernel: [    1.208098] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 30 20:35:52 node-5 kernel: [    1.213390] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 30 20:35:52 node-5 kernel: [    1.223972] usb usb2: Product: EHCI Host Controller
Jul 30 20:35:52 node-5 kernel: [    1.229441] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 30 20:35:52 node-5 kernel: [    1.234980] usb usb2: SerialNumber: 0000:00:1d.0
Jul 30 20:35:52 node-5 kernel: [    1.240499] hub 2-0:1.0: USB hub found
Jul 30 20:35:52 node-5 kernel: [    1.245851] hub 2-0:1.0: 2 ports detected
Jul 30 20:35:52 node-5 kernel: [    1.251153] ehci-platform: EHCI generic platform driver
Jul 30 20:35:52 node-5 kernel: [    1.256381] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 30 20:35:52 node-5 kernel: [    1.261695] ohci-pci: OHCI PCI platform driver
Jul 30 20:35:52 node-5 kernel: [    1.266995] ohci-platform: OHCI generic platform driver
Jul 30 20:35:52 node-5 kernel: [    1.272185] uhci_hcd: USB Universal Host Controller Interface driver
Jul 30 20:35:52 node-5 kernel: [    1.277514] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 30 20:35:52 node-5 kernel: [    1.470686] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 30 20:35:52 node-5 kernel: [    1.770494] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 30 20:35:52 node-5 kernel: [    1.786716] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 30 20:35:52 node-5 kernel: [    1.792312] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 30 20:35:52 node-5 kernel: [    1.797987] hub 1-1:1.0: USB hub found
Jul 30 20:35:52 node-5 kernel: [    1.803577] hub 1-1:1.0: 6 ports detected
Jul 30 20:35:52 node-5 kernel: [    1.918327] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 30 20:35:52 node-5 kernel: [    2.316273] i8042: No controller found
Jul 30 20:35:52 node-5 kernel: [    2.321840] mousedev: PS/2 mouse device common for all mice
Jul 30 20:35:52 node-5 kernel: [    2.327598] rtc_cmos 00:02: RTC can wake from S4
Jul 30 20:35:52 node-5 kernel: [    2.330821] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 30 20:35:52 node-5 kernel: [    2.330822] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 30 20:35:52 node-5 kernel: [    2.331576] hub 2-1:1.0: USB hub found
Jul 30 20:35:52 node-5 kernel: [    2.331825] hub 2-1:1.0: 8 ports detected
Jul 30 20:35:52 node-5 kernel: [    2.355948] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 30 20:35:52 node-5 kernel: [    2.361721] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 30 20:35:52 node-5 kernel: [    2.373065] device-mapper: uevent: version 1.0.3
Jul 30 20:35:52 node-5 kernel: [    2.378781] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 30 20:35:52 node-5 kernel: [    2.390157] ledtrig-cpu: registered to indicate activity on CPUs
Jul 30 20:35:52 node-5 kernel: [    2.396116] TCP: cubic registered
Jul 30 20:35:52 node-5 kernel: [    2.401962] NET: Registered protocol family 10
Jul 30 20:35:52 node-5 kernel: [    2.408025] NET: Registered protocol family 17
Jul 30 20:35:52 node-5 kernel: [    2.413784] Key type dns_resolver registered
Jul 30 20:35:52 node-5 kernel: [    2.419832] Loading compiled-in X.509 certificates
Jul 30 20:35:52 node-5 kernel: [    2.426038] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 30 20:35:52 node-5 kernel: [    2.437663] registered taskstats version 1
Jul 30 20:35:52 node-5 kernel: [    2.445689] Key type trusted registered
Jul 30 20:35:52 node-5 kernel: [    2.453317] Key type encrypted registered
Jul 30 20:35:52 node-5 kernel: [    2.458811] AppArmor: AppArmor sha1 policy hashing enabled
Jul 30 20:35:52 node-5 kernel: [    2.464328] IMA: No TPM chip found, activating TPM-bypass!
Jul 30 20:35:52 node-5 kernel: [    2.470467] regulator-dummy: disabling
Jul 30 20:35:52 node-5 kernel: [    2.476019]   Magic number: 8:413:600
Jul 30 20:35:52 node-5 kernel: [    2.481755] rtc_cmos 00:02: setting system clock to 2016-07-30 20:35:18 UTC (1469910918)
Jul 30 20:35:52 node-5 kernel: [    2.494300] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 30 20:35:52 node-5 kernel: [    2.499988] EDD information not available.
Jul 30 20:35:52 node-5 kernel: [    2.505658] PM: Hibernation image not present or could not be loaded.
Jul 30 20:35:52 node-5 kernel: [    2.506528] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 30 20:35:52 node-5 kernel: [    2.517866] Write protecting the kernel read-only data: 12288k
Jul 30 20:35:52 node-5 kernel: [    2.524162] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 30 20:35:52 node-5 kernel: [    2.537118] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 30 20:35:52 node-5 kernel: [    2.570037] device-mapper: multipath: version 1.6.0 loaded
Jul 30 20:35:52 node-5 kernel: [    2.578235] systemd-udevd[216]: starting version 204
Jul 30 20:35:52 node-5 kernel: [    2.602038] md: linear personality registered for level -1
Jul 30 20:35:52 node-5 kernel: [    2.610480] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 30 20:35:52 node-5 kernel: [    2.622645] md: multipath personality registered for level -4
Jul 30 20:35:52 node-5 kernel: [    2.630815] md: raid0 personality registered for level 0
Jul 30 20:35:52 node-5 kernel: [    2.639023] md: raid1 personality registered for level 1
Jul 30 20:35:52 node-5 kernel: [    2.645446] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 30 20:35:52 node-5 kernel: [    2.651745] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 30 20:35:52 node-5 kernel: [    2.660191] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 30 20:35:52 node-5 kernel: [    2.672889] 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 30 20:35:52 node-5 kernel: [    2.686209] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 20:35:52 node-5 kernel: [    2.693053] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.693058] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.693062] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.693066] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.693106] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.706986] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 30 20:35:52 node-5 kernel: [    2.715714] megasas: FW now in Ready state
Jul 30 20:35:52 node-5 kernel: [    2.717931] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 30 20:35:52 node-5 kernel: [    2.717938] 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 30 20:35:52 node-5 kernel: [    2.717952] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 20:35:52 node-5 kernel: [    2.718748] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.718993] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.719094] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.719193] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.719422] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.725832] raid6: sse2x1    1095 MB/s
Jul 30 20:35:52 node-5 kernel: [    2.733368] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 30 20:35:52 node-5 kernel: [    2.733382] 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 30 20:35:52 node-5 kernel: [    2.733383] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 20:35:52 node-5 kernel: [    2.733748] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.733816] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.733881] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.733980] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.734230] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.744782] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 30 20:35:52 node-5 kernel: [    2.744802] 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 30 20:35:52 node-5 kernel: [    2.744816] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 30 20:35:52 node-5 kernel: [    2.745108] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.745199] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.745264] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.745344] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.745544] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.793728] raid6: sse2x2    1011 MB/s
Jul 30 20:35:52 node-5 kernel: [    2.861618] raid6: sse2x4    1236 MB/s
Jul 30 20:35:52 node-5 kernel: [    2.882530] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882535] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882540] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882545] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882550] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882555] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882559] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882564] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882569] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882574] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882580] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882585] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882589] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882594] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882599] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882604] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 30 20:35:52 node-5 kernel: [    2.882639] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 30 20:35:52 node-5 kernel: [    2.922501] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 30 20:35:52 node-5 kernel: [    2.929214] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 30 20:35:52 node-5 kernel: [    2.929598] raid6: avx2x1   10578 MB/s
Jul 30 20:35:52 node-5 kernel: [    2.948758] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 30 20:35:52 node-5 kernel: [    2.955215] usb 2-1.4: Manufacturer: Avocent
Jul 30 20:35:52 node-5 kernel: [    2.961530] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 30 20:35:52 node-5 kernel: [    2.970686] hidraw: raw HID events driver (C) Jiri Kosina
Jul 30 20:35:52 node-5 kernel: [    2.979500] usbcore: registered new interface driver usbhid
Jul 30 20:35:52 node-5 kernel: [    2.985769] usbhid: USB HID core driver
Jul 30 20:35:52 node-5 kernel: [    2.992860] 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 30 20:35:52 node-5 kernel: [    2.997516] raid6: avx2x2    4300 MB/s
Jul 30 20:35:52 node-5 kernel: [    3.011943] 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 30 20:35:52 node-5 kernel: [    3.024640] 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 30 20:35:52 node-5 kernel: [    3.037533] 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 30 20:35:52 node-5 kernel: [    3.050769] 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 30 20:35:52 node-5 kernel: [    3.063990] 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 30 20:35:52 node-5 kernel: [    3.065379] raid6: avx2x4   24812 MB/s
Jul 30 20:35:52 node-5 kernel: [    3.065380] raid6: using algorithm avx2x4 (24812 MB/s)
Jul 30 20:35:52 node-5 kernel: [    3.065380] raid6: using avx2x2 recovery algorithm
Jul 30 20:35:52 node-5 kernel: [    3.097377] Switched to clocksource tsc
Jul 30 20:35:52 node-5 kernel: [    3.104244] xor: automatically using best checksumming function:
Jul 30 20:35:52 node-5 kernel: [    3.149243]    avx       : 35714.000 MB/sec
Jul 30 20:35:52 node-5 kernel: [    3.156483] async_tx: api initialized (async)
Jul 30 20:35:52 node-5 kernel: [    3.166681] md: raid6 personality registered for level 6
Jul 30 20:35:52 node-5 kernel: [    3.173232] md: raid5 personality registered for level 5
Jul 30 20:35:52 node-5 kernel: [    3.179547] md: raid4 personality registered for level 4
Jul 30 20:35:52 node-5 kernel: [    3.188735] md: raid10 personality registered for level 10
Jul 30 20:35:52 node-5 kernel: [    3.241186] megasas:IOC Init cmd success
Jul 30 20:35:52 node-5 kernel: [    3.241199] multipathd (355): /proc/355/oom_adj is deprecated, please use /proc/355/oom_score_adj instead.
Jul 30 20:35:52 node-5 kernel: [    3.281212] megasas: INIT adapter done
Jul 30 20:35:52 node-5 kernel: [    3.357123] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 30 20:35:52 node-5 kernel: [    3.363478] scsi0 : LSI SAS based MegaRAID driver
Jul 30 20:35:52 node-5 kernel: [    3.370416] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 30 20:35:52 node-5 kernel: [    3.390609] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 30 20:35:52 node-5 kernel: [    3.404256] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 30 20:35:52 node-5 kernel: [    3.409926] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 30 20:35:52 node-5 kernel: [    3.421278] sd 0:2:0:0: [sda] Write Protect is off
Jul 30 20:35:52 node-5 kernel: [    3.427000] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 30 20:35:52 node-5 kernel: [    3.427019] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 30 20:35:52 node-5 kernel: [    3.466019]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 30 20:35:52 node-5 kernel: [    3.472393] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 30 20:35:52 node-5 kernel: [    3.599853] random: lvm urandom read with 28 bits of entropy available
Jul 30 20:35:52 node-5 kernel: [    3.700406] bio: create slab <bio-1> at 1
Jul 30 20:35:52 node-5 kernel: [    4.452854] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 30 20:35:52 node-5 kernel: [    5.093041] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 30 20:35:52 node-5 kernel: [    5.122653] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 30 20:35:52 node-5 kernel: [    5.293812] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 30 20:35:52 node-5 kernel: [    5.371611] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 30 20:35:52 node-5 kernel: [    5.452949] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 30 20:35:52 node-5 kernel: [    5.471693] random: nonblocking pool is initialized
Jul 30 20:35:52 node-5 kernel: [    5.652661] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 30 20:35:52 node-5 kernel: [    5.699829] XFS (dm-0): Mounting Filesystem
Jul 30 20:35:52 node-5 kernel: [    5.936336] XFS (dm-0): Ending clean mount
Jul 30 20:35:52 node-5 kernel: [    5.979733] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 30 20:35:52 node-5 kernel: [    6.028906] XFS (dm-1): Mounting Filesystem
Jul 30 20:35:52 node-5 kernel: [    6.155945] XFS (dm-1): Ending clean mount
Jul 30 20:35:52 node-5 kernel: [    7.953191] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 30 20:35:52 node-5 kernel: [    7.977243] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 30 20:35:52 node-5 kernel: [    8.158188] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 30 20:35:52 node-5 kernel: [    8.158198] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 30 20:35:52 node-5 kernel: [    8.158206] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 30 20:35:52 node-5 kernel: [    8.158214] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 30 20:35:52 node-5 kernel: [    8.210921] systemd-udevd[779]: starting version 204
Jul 30 20:35:52 node-5 kernel: [    8.378418] power_meter ACPI000D:00: Found ACPI power meter.
Jul 30 20:35:52 node-5 kernel: [    8.378426] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 30 20:35:52 node-5 kernel: [    8.385216] IPMI System Interface driver.
Jul 30 20:35:52 node-5 kernel: [    8.385305] ipmi_si: probing via ACPI
Jul 30 20:35:52 node-5 kernel: [    8.385317] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 30 20:35:52 node-5 kernel: [    8.385318] ipmi_si: Adding ACPI-specified kcs state machine
Jul 30 20:35:52 node-5 kernel: [    8.385335] ipmi_si: probing via SMBIOS
Jul 30 20:35:52 node-5 kernel: [    8.385336] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 30 20:35:52 node-5 kernel: [    8.385336] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 30 20:35:52 node-5 kernel: [    8.385338] ipmi_si: probing via SPMI
Jul 30 20:35:52 node-5 kernel: [    8.385339] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 30 20:35:52 node-5 kernel: [    8.385339] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 30 20:35:52 node-5 kernel: [    8.385341] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 30 20:35:52 node-5 kernel: [    8.425020] wmi: Mapper loaded
Jul 30 20:35:52 node-5 kernel: [    8.450307] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 30 20:35:52 node-5 kernel: [    8.450312] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 30 20:35:52 node-5 kernel: [    8.450315] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 30 20:35:52 node-5 kernel: [    8.450317] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 30 20:35:52 node-5 kernel: [    8.450359] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 30 20:35:52 node-5 kernel: [    8.450422] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 30 20:35:52 node-5 kernel: [    8.513208] systemd-udevd[810]: renamed network interface eth0 to enp6s0
Jul 30 20:35:52 node-5 kernel: [    8.529047] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 30 20:35:52 node-5 kernel: [    8.529055] ipmi_si 00:09: IPMI kcs interface initialized
Jul 30 20:35:52 node-5 kernel: [    8.537052] systemd-udevd[796]: renamed network interface eth1 to enp7s0
Jul 30 20:35:52 node-5 kernel: [    8.553041] systemd-udevd[828]: renamed network interface eth2 to enp8s0
Jul 30 20:35:52 node-5 kernel: [    8.585099] systemd-udevd[821]: renamed network interface eth3 to enp9s0
Jul 30 20:35:52 node-5 kernel: [    8.900983] type=1400 audit(1469910924.920:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1056 comm="apparmor_parser"
Jul 30 20:35:52 node-5 kernel: [    8.901137] type=1400 audit(1469910924.920:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1056 comm="apparmor_parser"
Jul 30 20:35:52 node-5 kernel: [    8.901267] type=1400 audit(1469910924.920:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1056 comm="apparmor_parser"
Jul 30 20:35:52 node-5 kernel: [    8.901601] type=1400 audit(1469910924.920:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1054 comm="apparmor_parser"
Jul 30 20:35:52 node-5 kernel: [    8.901747] type=1400 audit(1469910924.920:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1054 comm="apparmor_parser"
Jul 30 20:35:52 node-5 kernel: [    8.901881] type=1400 audit(1469910924.920:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1054 comm="apparmor_parser"
Jul 30 20:35:52 node-5 kernel: [    8.921113] type=1400 audit(1469910924.940:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1057 comm="apparmor_parser"
Jul 30 20:35:52 node-5 kernel: [    8.921255] type=1400 audit(1469910924.940:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1057 comm="apparmor_parser"
Jul 30 20:35:52 node-5 kernel: [    8.921377] type=1400 audit(1469910924.940:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1057 comm="apparmor_parser"
Jul 30 20:35:52 node-5 kernel: [    8.925031] type=1400 audit(1469910924.944:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1053 comm="apparmor_parser"
Jul 30 20:35:52 node-5 kernel: [    9.569972] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 30 20:35:52 node-5 kernel: [    9.570747] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 30 20:35:52 node-5 kernel: [    9.747975] enic 0000:06:00.0 enp6s0: Link UP
Jul 30 20:35:52 node-5 kernel: [    9.749692] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 30 20:35:52 node-5 kernel: [    9.749697] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 30 20:35:52 node-5 kernel: [   19.086524] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 30 20:35:52 node-5 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 30 20:35:53 node-5 failsafe: Failsafe of 120 seconds reached.
Jul 30 20:35:53 node-5 kernel: [   38.353933] init: failsafe main process (8397) killed by TERM signal
Jul 30 20:35:53 node-5 dbus[8430]: [system] AppArmor D-Bus mediation is enabled
Jul 30 20:35:54 node-5 kernel: [   38.592604] audit_printk_skb: 30 callbacks suppressed
Jul 30 20:35:54 node-5 kernel: [   38.592606] type=1400 audit(1469910954.102:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8523 comm="apparmor_parser"
Jul 30 20:35:54 node-5 kernel: [   38.592850] type=1400 audit(1469910954.102:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8522 comm="apparmor_parser"
Jul 30 20:35:54 node-5 kernel: [   38.592855] type=1400 audit(1469910954.102:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8522 comm="apparmor_parser"
Jul 30 20:35:54 node-5 kernel: [   38.592858] type=1400 audit(1469910954.102:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 30 20:35:54 node-5 kernel: [   38.593092] type=1400 audit(1469910954.102:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8522 comm="apparmor_parser"
Jul 30 20:35:54 node-5 kernel: [   38.593094] type=1400 audit(1469910954.102:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 30 20:35:54 node-5 kernel: [   38.593207] type=1400 audit(1469910954.102:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8522 comm="apparmor_parser"
Jul 30 20:35:54 node-5 kernel: [   38.655668] type=1400 audit(1469910954.166:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8525 comm="apparmor_parser"
Jul 30 20:35:54 node-5 cron[8555]: (CRON) INFO (pidfile fd = 3)
Jul 30 20:35:54 node-5 anacron[8573]: Anacron 2.3 started on 2016-07-30
Jul 30 20:35:54 node-5 cron[8590]: (CRON) STARTUP (fork ok)
Jul 30 20:35:54 node-5 anacron[8573]: Will run job `cron.daily' in 5 min.
Jul 30 20:35:54 node-5 anacron[8573]: Will run job `cron.weekly' in 10 min.
Jul 30 20:35:54 node-5 anacron[8573]: Will run job `cron.monthly' in 15 min.
Jul 30 20:35:54 node-5 anacron[8573]: Jobs will be executed sequentially
Jul 30 20:35:54 node-5 cron[8590]: (CRON) INFO (Running @reboot jobs)
Jul 30 20:35:54 node-5 multipathd: path checkers start up
Jul 30 20:35:54 node-5 postfix/master[8734]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 30 20:35:58 node-5 puppet-agent[8918]: Reopening log files
Jul 30 20:36:00 node-5 puppet-agent[8918]: Could not request certificate: Connection refused - connect(2)
Jul 30 20:36:01 node-5 CRON[8949]: (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 30 20:36:11 node-5 puppet-user[9137]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 30 20:36:11 node-5 puppet-user[9137]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 30 20:36:12 node-5 puppet-user[9137]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 30 20:36:12 node-5 puppet-user[9137]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 30 20:36:12 node-5 puppet-user[9137]: Finished catalog run in 0.81 seconds
Jul 30 20:36:14 node-5 multipathd: uevent trigger error
Jul 30 20:36:14 node-5 puppet-user[9577]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 30 20:36:14 node-5 puppet-user[9577]: Compiled catalog for node-5.domain.tld in environment production in 0.08 seconds
Jul 30 20:36:14 node-5 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 30 20:36:14 node-5 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 30 20:36:14 node-5 puppet-user[9577]: (/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 30 20:36:14 node-5 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 30 20:36:14 node-5 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 30 20:36:14 node-5 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 30 20:36:14 node-5 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 30 20:36:14 node-5 puppet-user[9577]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 30 20:36:14 node-5 puppet-user[9577]: Finished catalog run in 0.06 seconds
Jul 30 20:36:15 node-5 puppet-user[10042]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 30 20:36:15 node-5 puppet-user[10042]: Compiled catalog for node-5.domain.tld in environment production in 0.07 seconds
Jul 30 20:36:15 node-5 puppet-user[10042]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 30 20:36:15 node-5 puppet-user[10042]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 30 20:36:15 node-5 puppet-user[10042]: Finished catalog run in 0.03 seconds
Jul 30 20:36:17 node-5 puppet-user[10694]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 30 20:36:17 node-5 puppet-user[10694]: Compiled catalog for node-5.domain.tld in environment production in 0.02 seconds
Jul 30 20:36:17 node-5 puppet-user[10694]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 30 20:36:17 node-5 puppet-user[10694]: Finished catalog run in 0.04 seconds
Jul 30 20:36:19 node-5 puppet-user[11150]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 30 20:36:19 node-5 puppet-user[11150]: Compiled catalog for node-5.domain.tld in environment production in 0.18 seconds
Jul 30 20:36:19 node-5 puppet-user[11150]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 30 20:36:19 node-5 puppet-user[11150]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 30 20:36:20 node-5 puppet-user[11150]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 30 20:36:20 node-5 puppet-user[11150]: Finished catalog run in 0.83 seconds
Jul 30 20:36:21 node-5 puppet-user[11666]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 30 20:36:21 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:36:21 node-5 nailgun-agent: D, [2016-07-30T20:36:01.591879 #8952] DEBUG -- : Sleep for 20 seconds before sending request
Jul 30 20:36:21 node-5 nailgun-agent: I, [2016-07-30T20:36:21.609312 #8952]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 30 20:36:21 node-5 puppet-user[11666]: Compiled catalog for node-5.domain.tld in environment production in 0.23 seconds
Jul 30 20:36:21 node-5 puppet-user[11666]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 30 20:36:21 node-5 puppet-user[11666]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 30 20:36:21 node-5 puppet-user[11666]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 30 20:36:21 node-5 puppet-user[11666]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 30 20:36:22 node-5 puppet-user[11666]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 30 20:36:22 node-5 puppet-user[11666]: Finished catalog run in 0.35 seconds
Jul 30 20:36:22 node-5 nailgun-agent: D, [2016-07-30T20:36:22.103285 #8952] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 30 20:36:23 node-5 puppet-user[12282]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 30 20:36:23 node-5 puppet-user[12282]: Compiled catalog for node-5.domain.tld in environment production in 0.19 seconds
Jul 30 20:36:23 node-5 puppet-user[12282]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 30 20:36:23 node-5 kernel: [   68.396905] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 30 20:36:23 node-5 kernel: [   68.396954] 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 30 20:36:23 node-5 puppet-user[12282]: (/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 30 20:36:23 node-5 puppet-user[12282]: Finished catalog run in 0.05 seconds
Jul 30 20:36:25 node-5 puppet-user[12752]: (Scope(Class[main])) MODULAR: sync_time
Jul 30 20:36:25 node-5 puppet-user[12752]: Compiled catalog for node-5.domain.tld in environment production in 0.03 seconds
Jul 30 20:36:26 node-5 ntpdate[13177]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 30 20:36:28 node-5 kernel: [   72.554370] init: plymouth-upstart-bridge main process ended, respawning
Jul 30 20:36:28 node-5 puppet-agent[8918]: Could not run: SIGTERM
Jul 30 20:36:28 node-5 kernel: [   72.831658] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 30 20:36:28 node-5 ec2: 
Jul 30 20:36:28 node-5 ec2: #############################################################
Jul 30 20:36:28 node-5 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 30 20:36:28 node-5 ec2: 1024 c7:03:d3:af:2e:a2:4d:1f:24:13:da:fb:11:89:f4:6b  root@node-5.domain.tld (DSA)
Jul 30 20:36:28 node-5 ec2: 256 bb:fc:46:64:19:fa:ff:d9:2f:6b:71:cc:d2:6b:7b:d0  root@node-5.domain.tld (ECDSA)
Jul 30 20:36:28 node-5 ec2: 256 3c:70:73:fc:1a:e0:6a:10:65:97:2c:bf:bb:48:98:69  root@node-5.domain.tld (ED25519)
Jul 30 20:36:28 node-5 ec2: 2048 01:b0:d4:24:4b:5e:6c:c7:d5:84:06:a3:aa:8a:06:88  root@node-5.domain.tld (RSA)
Jul 30 20:36:28 node-5 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 30 20:36:28 node-5 ec2: #############################################################
Jul 30 20:36:32 node-5 ntpdate[13177]: adjust time server 10.20.0.2 offset 0.268680 sec
Jul 30 20:36:32 node-5 puppet-user[12752]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 30 20:36:32 node-5 puppet-user[12752]: Finished catalog run in 6.16 seconds
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.287752 #8952] DEBUG -- : Trying to find block devices
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.287871 #8952] DEBUG -- : Found block device: sda
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.287910 #8952] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.287934 #8952] DEBUG -- : Trying to get list of physical devices
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.288102 #8952] DEBUG -- : Getting udev properties for device: sda
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.290245 #8952] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Jul 30 20:36:34 node-5 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31268", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.290305 #8952] DEBUG -- : Trying to find out if device sda is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.290354 #8952] DEBUG -- : Device sda removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.290384 #8952] DEBUG -- : Device sda seems to be appropriate
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.290838 #8952] DEBUG -- : Getting udev properties for device: dm-0
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.292577 #8952] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-ZixXdo2Xni1I0hdJ8w7uShG1CsJ7fhaT3b2S6MlHqdgrtq0l2qY8clvFJbw8XV83 /dev/disk/by-uuid/24a0c651-7636-4f90-b294-78ff6c251904 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-ZixXdo2Xni1I0hdJ8w7uShG1CsJ7fhaT3b2S6MlHqdgrtq0l2qY8clvFJbw8XV83", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"24a0c651-7636-4f90-b294-78ff6c251904", "ID_FS_UUID_ENC"=>"24a0c651-7636-4f90-b294-78ff6c251904", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59544", "nomdmonddf"=>"1", "nomd
Jul 30 20:36:34 node-5 nailgun-agent: monisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.292605 #8952] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.292647 #8952] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.292663 #8952] DEBUG -- : Device dm-0 seems to be appropriate
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.292686 #8952] DEBUG -- : Getting udev properties for device: dm-1
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.294315 #8952] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-aGn0uUye3hSTQ56yQYmCcv42GJHGtkK96VaBLQtF5E8VyvmidtlOAwbCdWLwxfmB /dev/disk/by-uuid/e7004be1-a208-42f9-91af-af89eaa05cee /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-aGn0uUye3hSTQ56yQYmCcv42GJHGtkK96VaBLQtF5E8VyvmidtlOAwbCdWLwxfmB", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"e7004be1-a208-42f9-91af-af89eaa05cee", "ID_FS_UUID_ENC"=>"e7004be1-a208-42f9-91af-af89eaa05cee", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"90
Jul 30 20:36:34 node-5 nailgun-agent: 736", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.294357 #8952] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.294433 #8952] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.294448 #8952] DEBUG -- : Device dm-1 seems to be appropriate
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.294464 #8952] DEBUG -- : Getting udev properties for device: dm-2
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.296440 #8952] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-fi8hg1uhilK0J8KI8Be1YzKZ1OSs3lrklHrhTOVaXEtDxLJsNFa3W2xLX1qMYUrC /dev/disk/by-uuid/18db55a5-409a-4981-b1c7-72b0f8aa3119 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-fi8hg1uhilK0J8KI8Be1YzKZ1OSs3lrklHrhTOVaXEtDxLJsNFa3W2xLX1qMYUrC", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"18db55a5-409a-4981-b1c7-72b0f8aa3119", "ID_FS_UUID_ENC"=>"18db55a5-409a-4981-b1c7-72b0f8aa3119", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2716", "nomdmondd
Jul 30 20:36:34 node-5 nailgun-agent: f"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.296481 #8952] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.296511 #8952] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.296526 #8952] DEBUG -- : Device dm-2 seems to be appropriate
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.296561 #8952] DEBUG -- : Getting udev properties for device: dm-3
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.298404 #8952] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-JrkLVzOMHH7LJFKo7T4kXEshmkjFdgZcVviK9ls5YjMNha4mLBdniANH13idZ0zo /dev/disk/by-uuid/c9afc563-9296-4a07-967b-ef23193cec80 /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-JrkLVzOMHH7LJFKo7T4kXEshmkjFdgZcVviK9ls5YjMNha4mLBdniANH13idZ0zo", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c9afc563-9296-4a07-967b-ef23193cec80", "ID_FS_UUID_ENC"=>"c9afc563-9296-4a07-967b-ef23193cec80", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"6624", "nomdmonddf"=>"1", "
Jul 30 20:36:34 node-5 nailgun-agent: nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.298432 #8952] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.298481 #8952] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.298496 #8952] DEBUG -- : Device dm-3 seems to be appropriate
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.298511 #8952] DEBUG -- : Getting udev properties for device: dm-4
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.300256 #8952] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-OCjxGJNYjzD7s1imSRh3isAKRLr0D1LTGUzsTlSLXCW3ETdvqvpFG1j5xU9Oh6qq /dev/disk/by-uuid/ca26f6af-2f05-437d-b34b-d9e008c02ce6 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-OCjxGJNYjzD7s1imSRh3isAKRLr0D1LTGUzsTlSLXCW3ETdvqvpFG1j5xU9Oh6qq", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ca26f6af-2f05-437d-b34b-d9e008c02ce6", "ID_FS_UUID_ENC"=>"ca26f6af-2f05-437d-b34b-d9e008c02ce6", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14542", "nomdmonddf"=>"1", "nomd
Jul 30 20:36:34 node-5 nailgun-agent: monisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.300284 #8952] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.300314 #8952] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.300344 #8952] DEBUG -- : Device dm-4 seems to be appropriate
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.300357 #8952] DEBUG -- : Getting udev properties for device: dm-5
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.302398 #8952] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-OCjxGJNYjzD7s1imSRh3isAKRLr0D1LTexvp1QECFRd47pLWWA4cmPscUpdt63MV /dev/disk/by-uuid/985b6980-2863-4e3e-b1c3-b1178f00d000 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-OCjxGJNYjzD7s1imSRh3isAKRLr0D1LTexvp1QECFRd47pLWWA4cmPscUpdt63MV", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"985b6980-2863-4e3e-b1c3-b1178f00d000", "ID_FS_UUID_ENC"=>"985b6980-2863-4e3e-b1c3-b1178f00d000", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"14913", "nomdmonddf"=>"1", "nomdmonisw"
Jul 30 20:36:34 node-5 nailgun-agent: =>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.302425 #8952] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.302469 #8952] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.302484 #8952] DEBUG -- : Device dm-5 seems to be appropriate
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.302521 #8952] DEBUG -- : Getting udev properties for device: ram0
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.304239 #8952] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60325", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.304265 #8952] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.304304 #8952] DEBUG -- : Device ram0 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.304339 #8952] DEBUG -- : Getting udev properties for device: ram1
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.306061 #8952] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60442", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.306087 #8952] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.306124 #8952] DEBUG -- : Device ram1 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.306143 #8952] DEBUG -- : Getting udev properties for device: ram2
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.307807 #8952] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61353", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.307833 #8952] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.307901 #8952] DEBUG -- : Device ram2 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.307922 #8952] DEBUG -- : Getting udev properties for device: ram3
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.309888 #8952] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61455", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.309922 #8952] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.309959 #8952] DEBUG -- : Device ram3 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.309987 #8952] DEBUG -- : Getting udev properties for device: ram4
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.311716 #8952] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61554", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.311754 #8952] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.311799 #8952] DEBUG -- : Device ram4 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.311821 #8952] DEBUG -- : Getting udev properties for device: ram5
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.313430 #8952] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61644", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.313455 #8952] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.313493 #8952] DEBUG -- : Device ram5 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.313527 #8952] DEBUG -- : Getting udev properties for device: ram6
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.315126 #8952] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61729", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.315151 #8952] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.315197 #8952] DEBUG -- : Device ram6 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.315217 #8952] DEBUG -- : Getting udev properties for device: ram7
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.316704 #8952] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61792", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.316744 #8952] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.316778 #8952] DEBUG -- : Device ram7 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.316799 #8952] DEBUG -- : Getting udev properties for device: ram8
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.318688 #8952] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61882", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.318713 #8952] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.318749 #8952] DEBUG -- : Device ram8 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.318771 #8952] DEBUG -- : Getting udev properties for device: ram9
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.320495 #8952] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61999", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.320537 #8952] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.320573 #8952] DEBUG -- : Device ram9 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.320601 #8952] DEBUG -- : Getting udev properties for device: loop0
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.322272 #8952] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59258", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.322306 #8952] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.322342 #8952] DEBUG -- : Device loop0 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.322386 #8952] DEBUG -- : Getting udev properties for device: loop1
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.324066 #8952] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59356", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.324091 #8952] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.324128 #8952] DEBUG -- : Device loop1 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.324148 #8952] DEBUG -- : Getting udev properties for device: loop2
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.325619 #8952] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59464", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.325647 #8952] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.325713 #8952] DEBUG -- : Device loop2 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.325733 #8952] DEBUG -- : Getting udev properties for device: loop3
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.327225 #8952] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59548", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.327250 #8952] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.327286 #8952] DEBUG -- : Device loop3 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.327316 #8952] DEBUG -- : Getting udev properties for device: loop4
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.328769 #8952] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59631", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.328812 #8952] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.328850 #8952] DEBUG -- : Device loop4 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.328871 #8952] DEBUG -- : Getting udev properties for device: loop5
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.330703 #8952] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59674", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.330729 #8952] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.330770 #8952] DEBUG -- : Device loop5 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.330790 #8952] DEBUG -- : Getting udev properties for device: loop6
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.332802 #8952] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59763", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.332827 #8952] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.332874 #8952] DEBUG -- : Device loop6 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.332895 #8952] DEBUG -- : Getting udev properties for device: loop7
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.334394 #8952] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59882", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.334420 #8952] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.334465 #8952] DEBUG -- : Device loop7 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.334493 #8952] DEBUG -- : Getting udev properties for device: ram10
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.336024 #8952] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60547", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.336050 #8952] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.336086 #8952] DEBUG -- : Device ram10 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.336115 #8952] DEBUG -- : Getting udev properties for device: ram11
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.337989 #8952] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60711", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.338028 #8952] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.338064 #8952] DEBUG -- : Device ram11 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.338093 #8952] DEBUG -- : Getting udev properties for device: ram12
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.344454 #8952] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60847", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.344486 #8952] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.344528 #8952] DEBUG -- : Device ram12 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.344549 #8952] DEBUG -- : Getting udev properties for device: ram13
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.346529 #8952] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60956", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.346557 #8952] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.346628 #8952] DEBUG -- : Device ram13 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.346648 #8952] DEBUG -- : Getting udev properties for device: ram14
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.348342 #8952] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61079", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.348368 #8952] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.348402 #8952] DEBUG -- : Device ram14 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.348480 #8952] DEBUG -- : Getting udev properties for device: ram15
Jul 30 20:36:34 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350201 #8952] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61190", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350226 #8952] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350260 #8952] DEBUG -- : Device ram15 removable parameter: "0"
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350355 #8952] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350372 #8952] DEBUG -- : Block device seems to be physical data storage: sda
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350419 #8952] DEBUG -- : Found block device: dm-0
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350432 #8952] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350445 #8952] DEBUG -- : Found block device: dm-1
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350456 #8952] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350465 #8952] DEBUG -- : Found block device: dm-2
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350477 #8952] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350538 #8952] DEBUG -- : Found block device: dm-3
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350549 #8952] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350558 #8952] DEBUG -- : Found block device: dm-4
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350569 #8952] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350578 #8952] DEBUG -- : Found block device: dm-5
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350587 #8952] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350596 #8952] DEBUG -- : Found block device: ram0
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350606 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350615 #8952] DEBUG -- : Found block device: ram1
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350675 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350684 #8952] DEBUG -- : Found block device: ram2
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350693 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350701 #8952] DEBUG -- : Found block device: ram3
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350712 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350720 #8952] DEBUG -- : Found block device: ram4
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350731 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350739 #8952] DEBUG -- : Found block device: ram5
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350791 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350800 #8952] DEBUG -- : Found block device: ram6
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350810 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350818 #8952] DEBUG -- : Found block device: ram7
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350828 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350836 #8952] DEBUG -- : Found block device: ram8
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350846 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350854 #8952] DEBUG -- : Found block device: ram9
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350903 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350913 #8952] DEBUG -- : Found block device: loop0
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350924 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350934 #8952] DEBUG -- : Found block device: loop1
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350944 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350953 #8952] DEBUG -- : Found block device: loop2
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350962 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350971 #8952] DEBUG -- : Found block device: loop3
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.350983 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351032 #8952] DEBUG -- : Found block device: loop4
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351043 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351051 #8952] DEBUG -- : Found block device: loop5
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351059 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351068 #8952] DEBUG -- : Found block device: loop6
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351078 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351085 #8952] DEBUG -- : Found block device: loop7
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351094 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351103 #8952] DEBUG -- : Found block device: ram10
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351140 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351148 #8952] DEBUG -- : Found block device: ram11
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351161 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351170 #8952] DEBUG -- : Found block device: ram12
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351179 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351187 #8952] DEBUG -- : Found block device: ram13
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351196 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351204 #8952] DEBUG -- : Found block device: ram14
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351214 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351253 #8952] DEBUG -- : Found block device: ram15
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351264 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.351292 #8952] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.428791 #8952] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 30 20:36:34 node-5 nailgun-agent: D, [2016-07-30T20:36:34.428837 #8952] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 30 20:36:46 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573700 #8952] DEBUG -- : Trying to find block devices
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573821 #8952] DEBUG -- : Found block device: sda
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573851 #8952] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573881 #8952] DEBUG -- : Block device seems to be physical data storage: sda
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573902 #8952] DEBUG -- : Found block device: dm-0
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573913 #8952] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573925 #8952] DEBUG -- : Found block device: dm-1
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573965 #8952] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573976 #8952] DEBUG -- : Found block device: dm-2
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573986 #8952] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.573995 #8952] DEBUG -- : Found block device: dm-3
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574005 #8952] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574014 #8952] DEBUG -- : Found block device: dm-4
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574024 #8952] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574033 #8952] DEBUG -- : Found block device: dm-5
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574043 #8952] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574051 #8952] DEBUG -- : Found block device: ram0
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574060 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574101 #8952] DEBUG -- : Found block device: ram1
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574111 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574120 #8952] DEBUG -- : Found block device: ram2
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574129 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574138 #8952] DEBUG -- : Found block device: ram3
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574148 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574156 #8952] DEBUG -- : Found block device: ram4
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574165 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574173 #8952] DEBUG -- : Found block device: ram5
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574182 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574190 #8952] DEBUG -- : Found block device: ram6
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574229 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574239 #8952] DEBUG -- : Found block device: ram7
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574249 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574256 #8952] DEBUG -- : Found block device: ram8
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574265 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574273 #8952] DEBUG -- : Found block device: ram9
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574282 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574290 #8952] DEBUG -- : Found block device: loop0
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574300 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574308 #8952] DEBUG -- : Found block device: loop1
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574359 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574371 #8952] DEBUG -- : Found block device: loop2
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574381 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574389 #8952] DEBUG -- : Found block device: loop3
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574400 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574408 #8952] DEBUG -- : Found block device: loop4
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574417 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574426 #8952] DEBUG -- : Found block device: loop5
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574436 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574445 #8952] DEBUG -- : Found block device: loop6
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574454 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574490 #8952] DEBUG -- : Found block device: loop7
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574500 #8952] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574509 #8952] DEBUG -- : Found block device: ram10
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574519 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574527 #8952] DEBUG -- : Found block device: ram11
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574536 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574545 #8952] DEBUG -- : Found block device: ram12
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574555 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574563 #8952] DEBUG -- : Found block device: ram13
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574572 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574580 #8952] DEBUG -- : Found block device: ram14
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574632 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574641 #8952] DEBUG -- : Found block device: ram15
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574650 #8952] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.574679 #8952] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Jul 30 20:36:46 node-5 nailgun-agent: D, [2016-07-30T20:36:46.738976 #8952] DEBUG -- : Response: status: 200 body: {"id": 5}
Jul 30 20:36:46 node-5 nailgun-agent: I, [2016-07-30T20:36:46.739156 #8952]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 30 20:37:01 node-5 CRON[13847]: (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 30 20:37:16 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:37:16 node-5 nailgun-agent: I, [2016-07-30T20:37:16.921116 #13850]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 30 20:37:19 node-5 puppet-user[14006]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 30 20:37:19 node-5 puppet-user[14006]: Compiled catalog for node-5.domain.tld in environment production in 0.10 seconds
Jul 30 20:37:19 node-5 puppet-user[14006]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 30 20:37:20 node-5 puppet-user[14006]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 30 20:37:20 node-5 puppet-user[14006]: Finished catalog run in 0.07 seconds
Jul 30 20:37:21 node-5 puppet-user[14463]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 30 20:37:23 node-5 puppet-user[14463]: Compiled catalog for node-5.domain.tld in environment production in 1.36 seconds
Jul 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:23 node-5 puppet-user[14463]: (/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 30 20:37:29 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:37:29 node-5 nailgun-agent: I, [2016-07-30T20:37:29.862657 #13850]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 30 20:37:41 node-5 puppet-user[14463]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 30 20:37:41 node-5 puppet-user[14463]: Finished catalog run in 18.22 seconds
Jul 30 20:37:43 node-5 puppet-user[15576]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 30 20:37:43 node-5 puppet-user[15576]: Compiled catalog for node-5.domain.tld in environment production in 0.15 seconds
Jul 30 20:37:48 node-5 puppet-user[15576]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 30 20:38:01 node-5 CRON[17130]: (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 30 20:38:10 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:38:10 node-5 nailgun-agent: I, [2016-07-30T20:38:10.041532 #17134]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 30 20:38:19 node-5 puppet-user[15576]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 30 20:38:19 node-5 puppet-user[15576]: Finished catalog run in 35.52 seconds
Jul 30 20:38:21 node-5 puppet-user[18207]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 30 20:38:22 node-5 puppet-user[18207]: Compiled catalog for node-5.domain.tld in environment production in 0.57 seconds
Jul 30 20:38:22 node-5 puppet-user[18207]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 30 20:38:22 node-5 puppet-user[18207]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 30 20:38:22 node-5 puppet-user[18207]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 30 20:38:22 node-5 puppet-user[18207]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 30 20:38:22 node-5 puppet-user[18207]: Finished catalog run in 0.12 seconds
Jul 30 20:38:23 node-5 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 30 20:38:23 node-5 nailgun-agent: I, [2016-07-30T20:38:23.315219 #17134]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 5
Jul 30 20:38:24 node-5 puppet-user[18680]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 30 20:38:24 node-5 puppet-user[18680]: Compiled catalog for node-5.domain.tld in environment production in 0.87 seconds
Jul 30 20:38:25 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 30 20:38:25 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 30 20:38:25 node-5 crontab[19292]: (root) LIST (root)
Jul 30 20:38:25 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 30 20:38:25 node-5 crontab[19293]: (root) REPLACE (root)
Jul 30 20:38:27 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 30 20:38:28 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 30 20:38:28 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 30 20:38:28 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 30 20:38:29 node-5 puppet-user[18680]: (/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 30 20:38:30 node-5 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8370" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 30 20:38:30 node-5 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 30 20:38:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:52 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:52 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:52 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:52 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:52 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:54 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:56 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:56 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:56 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:56 node-5 multipathd: uevent trigger error
<27>Jul 30 20:38:56 node-5 multipathd: uevent trigger error
<27>Jul 30 20:39:56 node-5 ntpdate[30700]: no servers can be used, exiting
<27>Jul 30 20:40:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:31 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:31 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:31 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:31 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:31 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:31 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:43 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:43 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:43 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:43 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:43 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:46 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:46 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:46 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:46 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:46 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:53 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:53 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:53 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:53 node-5 multipathd: uevent trigger error
<27>Jul 30 20:40:53 node-5 multipathd: uevent trigger error
<43>Jul 30 20:41:10 node-5 apache2_error [Sat Jul 30 20:41:06.042208 2016] [mpm_event:notice] [pid 8462:tid 140558692611968] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 30 20:41:10 node-5 apache2_error [Sat Jul 30 20:41:06.042345 2016] [core:notice] [pid 8462:tid 140558692611968] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 30 20:41:10 node-5 apache2_error [Sat Jul 30 20:41:08.976953 2016] [mpm_event:notice] [pid 8462:tid 140558692611968] AH00491: caught SIGTERM, shutting down
<43>Jul 30 20:41:10 node-5 apache2_error [Sat Jul 30 20:41:10.064398 2016] [mpm_worker:notice] [pid 8842:tid 139704337237888] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 30 20:41:10 node-5 apache2_error [Sat Jul 30 20:41:10.064502 2016] [core:notice] [pid 8842:tid 139704337237888] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 20:41:14 node-5 multipathd: uevent trigger error
<27>Jul 30 20:41:14 node-5 multipathd: uevent trigger error
<27>Jul 30 20:41:14 node-5 multipathd: uevent trigger error
<27>Jul 30 20:41:14 node-5 multipathd: uevent trigger error
<27>Jul 30 20:41:14 node-5 multipathd: uevent trigger error
<27>Jul 30 20:41:14 node-5 multipathd: uevent trigger error
<43>Jul 30 20:41:50 node-5 apache2_error [Sat Jul 30 20:41:47.563431 2016] [mpm_worker:notice] [pid 8842:tid 139704337237888] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 20:41:50 node-5 apache2_error [Sat Jul 30 20:41:47.570832 2016] [mpm_worker:warn] [pid 8842:tid 139704337237888] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 20:41:50 node-5 apache2_error [Sat Jul 30 20:41:47.571176 2016] [mpm_worker:notice] [pid 8842:tid 139704337237888] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 30 20:41:50 node-5 apache2_error [Sat Jul 30 20:41:47.571183 2016] [core:notice] [pid 8842:tid 139704337237888] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 20:41:50 node-5 multipathd: uevent trigger error
<27>Jul 30 20:41:50 node-5 multipathd: uevent trigger error
<27>Jul 30 20:41:50 node-5 multipathd: uevent trigger error
<27>Jul 30 20:41:50 node-5 multipathd: uevent trigger error
<27>Jul 30 20:41:50 node-5 multipathd: uevent trigger error
<27>Jul 30 20:41:50 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:09 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:43 node-5 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 30 20:42:48 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:48 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:48 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:48 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:48 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:52 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:52 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:52 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:52 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:52 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-5 multipathd: uevent trigger error
<27>Jul 30 20:42:59 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:07 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:07 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:07 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:07 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:07 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:07 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:12 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:12 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:12 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:12 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:12 node-5 multipathd: uevent trigger error
<129>Jul 30 20:43:12 node-5 haproxy[26467]: Server odl-jetty/node-4 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:12 node-5 haproxy[26467]: proxy odl-jetty has no server available!
<129>Jul 30 20:43:15 node-5 haproxy[27662]: 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 30 20:43:17 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:17 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:17 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:17 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:17 node-5 multipathd: uevent trigger error
<129>Jul 30 20:43:18 node-5 haproxy[27662]: Server odl-jetty/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 30 20:43:18 node-5 haproxy[27662]: proxy odl-jetty has no server available!
<27>Jul 30 20:43:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:21 node-5 multipathd: uevent trigger error
<129>Jul 30 20:43:22 node-5 haproxy[27662]: Server odl-neutron-endpoint/node-4 is DOWN, reason: Layer4 timeout, check duration: 5002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:22 node-5 haproxy[27662]: proxy odl-neutron-endpoint has no server available!
<129>Jul 30 20:43:24 node-5 haproxy[30125]: 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 30 20:43:24 node-5 haproxy[30125]: 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 30 20:43:26 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:26 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:26 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:26 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:26 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:26 node-5 multipathd: uevent trigger error
<129>Jul 30 20:43:27 node-5 haproxy[30125]: Server odl-jetty/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 30 20:43:27 node-5 haproxy[30125]: proxy odl-jetty has no server available!
<129>Jul 30 20:43:29 node-5 haproxy[31343]: 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 30 20:43:29 node-5 haproxy[31343]: 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 30 20:43:30 node-5 haproxy[31343]: 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 30 20:43:31 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:31 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:31 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:31 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:31 node-5 multipathd: uevent trigger error
<129>Jul 30 20:43:32 node-5 haproxy[31343]: Server odl-jetty/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 30 20:43:32 node-5 haproxy[31343]: proxy odl-jetty has no server available!
<129>Jul 30 20:43:34 node-5 haproxy[32568]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:34 node-5 haproxy[32568]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:35 node-5 haproxy[32577]: 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 30 20:43:35 node-5 haproxy[32577]: 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 30 20:43:35 node-5 haproxy[32577]: 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 30 20:43:37 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:37 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:37 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:37 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:37 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:37 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:37 node-5 multipathd: uevent trigger error
<129>Jul 30 20:43:38 node-5 haproxy[32577]: Server odl-jetty/node-4 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:43:38 node-5 haproxy[32577]: proxy odl-jetty has no server available!
<129>Jul 30 20:43:39 node-5 haproxy[1363]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:40 node-5 haproxy[1372]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:40 node-5 haproxy[1372]: 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 30 20:43:40 node-5 haproxy[1372]: 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 30 20:43:41 node-5 haproxy[1372]: 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 30 20:43:41 node-5 haproxy[1372]: 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 30 20:43:42 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:42 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:42 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:42 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:42 node-5 multipathd: uevent trigger error
<129>Jul 30 20:43:43 node-5 haproxy[1372]: Server aodh/node-3 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 30 20:43:43 node-5 haproxy[1372]: 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 30 20:43:43 node-5 haproxy[1372]: proxy aodh has no server available!
<129>Jul 30 20:43:43 node-5 haproxy[1372]: Server odl-jetty/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 30 20:43:43 node-5 haproxy[1372]: proxy odl-jetty has no server available!
<129>Jul 30 20:43:45 node-5 haproxy[2584]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:45 node-5 haproxy[2584]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:45 node-5 haproxy[2584]: 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 30 20:43:46 node-5 haproxy[2597]: 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 30 20:43:46 node-5 haproxy[2597]: 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 30 20:43:46 node-5 haproxy[2597]: 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 30 20:43:46 node-5 haproxy[2597]: 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 30 20:43:48 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:48 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:48 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:48 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:48 node-5 multipathd: uevent trigger error
<129>Jul 30 20:43:48 node-5 haproxy[2597]: Server aodh/node-3 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 30 20:43:48 node-5 haproxy[2597]: 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 30 20:43:48 node-5 haproxy[2597]: proxy aodh has no server available!
<129>Jul 30 20:43:48 node-5 haproxy[2597]: Server ceilometer/node-3 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 30 20:43:48 node-5 haproxy[2597]: 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 30 20:43:48 node-5 haproxy[2597]: proxy ceilometer has no server available!
<129>Jul 30 20:43:49 node-5 haproxy[2597]: Server odl-jetty/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 30 20:43:49 node-5 haproxy[2597]: proxy odl-jetty has no server available!
<129>Jul 30 20:43:50 node-5 haproxy[3817]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:50 node-5 haproxy[3817]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:51 node-5 haproxy[3826]: 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 30 20:43:51 node-5 haproxy[3826]: 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 30 20:43:51 node-5 haproxy[3826]: 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 30 20:43:51 node-5 haproxy[3826]: 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 30 20:43:52 node-5 haproxy[3826]: 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 30 20:43:53 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:53 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:53 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:53 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:53 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:53 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:53 node-5 multipathd: uevent trigger error
<129>Jul 30 20:43:53 node-5 haproxy[3826]: Server aodh/node-3 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 30 20:43:53 node-5 haproxy[3826]: 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 30 20:43:53 node-5 haproxy[3826]: proxy aodh has no server available!
<129>Jul 30 20:43:54 node-5 haproxy[3826]: Server ceilometer/node-3 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 30 20:43:54 node-5 haproxy[3826]: 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 30 20:43:54 node-5 haproxy[3826]: proxy ceilometer has no server available!
<129>Jul 30 20:43:54 node-5 haproxy[3826]: Server odl-jetty/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 30 20:43:54 node-5 haproxy[3826]: proxy odl-jetty has no server available!
<129>Jul 30 20:43:56 node-5 haproxy[5053]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:56 node-5 haproxy[5053]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:56 node-5 haproxy[5053]: 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 30 20:43:56 node-5 haproxy[5053]: 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 30 20:43:57 node-5 haproxy[5053]: 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 30 20:43:57 node-5 haproxy[5053]: 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 30 20:43:57 node-5 haproxy[5053]: 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 30 20:43:57 node-5 haproxy[5053]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:43:57 node-5 haproxy[5053]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 30 20:43:58 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:58 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:58 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:58 node-5 multipathd: uevent trigger error
<27>Jul 30 20:43:58 node-5 multipathd: uevent trigger error
<129>Jul 30 20:43:59 node-5 haproxy[5053]: Server aodh/node-3 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 30 20:43:59 node-5 haproxy[5053]: 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 30 20:43:59 node-5 haproxy[5053]: proxy aodh has no server available!
<129>Jul 30 20:43:59 node-5 haproxy[5053]: Server ceilometer/node-3 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 30 20:43:59 node-5 haproxy[5053]: 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 30 20:43:59 node-5 haproxy[5053]: proxy ceilometer has no server available!
<129>Jul 30 20:43:59 node-5 haproxy[5053]: Server odl-jetty/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 30 20:43:59 node-5 haproxy[5053]: proxy odl-jetty has no server available!
<129>Jul 30 20:44:01 node-5 haproxy[6327]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:01 node-5 haproxy[6327]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:02 node-5 haproxy[6336]: 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 30 20:44:02 node-5 haproxy[6336]: 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 30 20:44:02 node-5 haproxy[6336]: 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 30 20:44:02 node-5 haproxy[6336]: 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 30 20:44:02 node-5 haproxy[6336]: 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 30 20:44:02 node-5 haproxy[6336]: 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 30 20:44:03 node-5 haproxy[6336]: 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 30 20:44:03 node-5 haproxy[6336]: 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 30 20:44:03 node-5 haproxy[6336]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:03 node-5 haproxy[6336]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:04 node-5 haproxy[6336]: Server glance-registry/node-3 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 30 20:44:04 node-5 haproxy[6336]: 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 30 20:44:04 node-5 haproxy[6336]: proxy glance-registry has no server available!
<27>Jul 30 20:44:04 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:04 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:04 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:04 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:04 node-5 multipathd: uevent trigger error
<129>Jul 30 20:44:05 node-5 haproxy[6336]: Server aodh/node-3 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 30 20:44:05 node-5 haproxy[6336]: 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 30 20:44:05 node-5 haproxy[6336]: proxy aodh has no server available!
<129>Jul 30 20:44:05 node-5 haproxy[6336]: Server ceilometer/node-3 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 30 20:44:05 node-5 haproxy[6336]: 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 30 20:44:05 node-5 haproxy[6336]: proxy ceilometer has no server available!
<129>Jul 30 20:44:05 node-5 haproxy[6336]: Server odl-jetty/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 30 20:44:05 node-5 haproxy[6336]: proxy odl-jetty has no server available!
<129>Jul 30 20:44:07 node-5 haproxy[7616]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:07 node-5 haproxy[7616]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:07 node-5 haproxy[7616]: 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 30 20:44:08 node-5 haproxy[7628]: 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 30 20:44:08 node-5 haproxy[7628]: 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 30 20:44:08 node-5 haproxy[7628]: 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 30 20:44:08 node-5 haproxy[7628]: 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 30 20:44:08 node-5 haproxy[7628]: 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 30 20:44:08 node-5 haproxy[7628]: 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 30 20:44:08 node-5 haproxy[7628]: 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 30 20:44:09 node-5 haproxy[7628]: 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 30 20:44:09 node-5 haproxy[7628]: 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 30 20:44:09 node-5 haproxy[7628]: 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 30 20:44:09 node-5 haproxy[7628]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:09 node-5 haproxy[7628]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 30 20:44:10 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:10 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:10 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:10 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:10 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:10 node-5 multipathd: uevent trigger error
<129>Jul 30 20:44:10 node-5 haproxy[7628]: Server glance-registry/node-3 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 30 20:44:10 node-5 haproxy[7628]: 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 30 20:44:10 node-5 haproxy[7628]: proxy glance-registry has no server available!
<27>Jul 30 20:44:10 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 30 20:44:10 node-5 haproxy[7628]: Server aodh/node-3 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 30 20:44:10 node-5 haproxy[7628]: 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 30 20:44:10 node-5 haproxy[7628]: proxy aodh has no server available!
<129>Jul 30 20:44:11 node-5 haproxy[7628]: Server ceilometer/node-3 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 30 20:44:11 node-5 haproxy[7628]: 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 30 20:44:11 node-5 haproxy[7628]: proxy ceilometer has no server available!
<129>Jul 30 20:44:11 node-5 haproxy[7628]: Server nova-novncproxy/node-3 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 30 20:44:11 node-5 haproxy[7628]: 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 30 20:44:11 node-5 haproxy[7628]: proxy nova-novncproxy has no server available!
<129>Jul 30 20:44:11 node-5 haproxy[7628]: Server odl-jetty/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 30 20:44:11 node-5 haproxy[7628]: proxy odl-jetty has no server available!
<129>Jul 30 20:44:12 node-5 haproxy[8869]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:13 node-5 haproxy[8883]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:13 node-5 haproxy[8883]: 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 30 20:44:13 node-5 haproxy[8883]: 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 30 20:44:13 node-5 haproxy[8883]: 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 30 20:44:13 node-5 haproxy[8883]: 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 30 20:44:13 node-5 haproxy[8883]: 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 30 20:44:13 node-5 haproxy[8883]: 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 30 20:44:13 node-5 haproxy[8883]: 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 30 20:44:14 node-5 haproxy[8883]: 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 30 20:44:14 node-5 haproxy[8883]: 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 30 20:44:14 node-5 haproxy[8883]: 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 30 20:44:14 node-5 haproxy[8883]: 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 30 20:44:14 node-5 haproxy[8883]: 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 30 20:44:14 node-5 haproxy[8883]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:14 node-5 haproxy[8883]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 30 20:44:15 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:15 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:15 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:15 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:15 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:15 node-5 multipathd: uevent trigger error
<129>Jul 30 20:44:15 node-5 haproxy[8883]: Server glance-registry/node-3 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 30 20:44:15 node-5 haproxy[8883]: 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 30 20:44:15 node-5 haproxy[8883]: proxy glance-registry has no server available!
<129>Jul 30 20:44:16 node-5 haproxy[8883]: Server aodh/node-3 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 30 20:44:16 node-5 haproxy[8883]: 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 30 20:44:16 node-5 haproxy[8883]: proxy aodh has no server available!
<129>Jul 30 20:44:16 node-5 haproxy[8883]: Server ceilometer/node-3 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 30 20:44:16 node-5 haproxy[8883]: 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 30 20:44:16 node-5 haproxy[8883]: proxy ceilometer has no server available!
<129>Jul 30 20:44:16 node-5 haproxy[8883]: Server nova-novncproxy/node-3 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 30 20:44:16 node-5 haproxy[8883]: 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 30 20:44:16 node-5 haproxy[8883]: proxy nova-novncproxy has no server available!
<129>Jul 30 20:44:16 node-5 haproxy[8883]: Server odl-jetty/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 30 20:44:16 node-5 haproxy[8883]: proxy odl-jetty has no server available!
<129>Jul 30 20:44:18 node-5 haproxy[10135]: Server keystone-1/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:18 node-5 haproxy[10135]: Server keystone-2/node-5 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:18 node-5 haproxy[10135]: 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 30 20:44:18 node-5 haproxy[10135]: 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 30 20:44:19 node-5 haproxy[10149]: 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 30 20:44:19 node-5 haproxy[10149]: 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 30 20:44:19 node-5 haproxy[10149]: 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 30 20:44:19 node-5 haproxy[10149]: 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 30 20:44:19 node-5 haproxy[10149]: 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 30 20:44:19 node-5 haproxy[10149]: 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 30 20:44:19 node-5 haproxy[10149]: 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 30 20:44:19 node-5 haproxy[10149]: 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 30 20:44:19 node-5 haproxy[10149]: 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 30 20:44:20 node-5 haproxy[10149]: 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 30 20:44:20 node-5 haproxy[10149]: 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 30 20:44:20 node-5 haproxy[10149]: 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 30 20:44:20 node-5 haproxy[10149]: 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 30 20:44:20 node-5 haproxy[10149]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:20 node-5 haproxy[10149]: Server horizon/node-4 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 30 20:44:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:21 node-5 multipathd: uevent trigger error
<129>Jul 30 20:44:21 node-5 haproxy[10149]: Server glance-registry/node-3 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 30 20:44:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:21 node-5 multipathd: uevent trigger error
<129>Jul 30 20:44:21 node-5 haproxy[10149]: 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 30 20:44:21 node-5 haproxy[10149]: proxy glance-registry has no server available!
<27>Jul 30 20:44:21 node-5 multipathd: uevent trigger error
<129>Jul 30 20:44:21 node-5 haproxy[10149]: Server aodh/node-3 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 30 20:44:21 node-5 haproxy[10149]: 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 30 20:44:21 node-5 haproxy[10149]: proxy aodh has no server available!
<129>Jul 30 20:44:21 node-5 haproxy[10149]: Server ceilometer/node-3 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 30 20:44:21 node-5 haproxy[10149]: 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 30 20:44:21 node-5 haproxy[10149]: proxy ceilometer has no server available!
<129>Jul 30 20:44:22 node-5 haproxy[10149]: Server nova-novncproxy/node-3 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 30 20:44:22 node-5 haproxy[10149]: 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 30 20:44:22 node-5 haproxy[10149]: proxy nova-novncproxy has no server available!
<129>Jul 30 20:44:22 node-5 haproxy[10149]: Server odl-jetty/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 30 20:44:22 node-5 haproxy[10149]: proxy odl-jetty has no server available!
<27>Jul 30 20:44:24 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:24 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:24 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:24 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:24 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:28 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:28 node-5 multipathd: uevent trigger error
<129>Jul 30 20:44:28 node-5 haproxy[10149]: Server odl-neutron-endpoint/node-4 is DOWN, reason: Layer4 timeout, check duration: 5000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:44:28 node-5 haproxy[10149]: proxy odl-neutron-endpoint has no server available!
<129>Jul 30 20:44:28 node-5 haproxy[10149]: Server keystone-1/node-3 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 30 20:44:28 node-5 haproxy[10149]: 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 30 20:44:28 node-5 haproxy[10149]: proxy keystone-1 has no server available!
<129>Jul 30 20:44:28 node-5 haproxy[10149]: Server keystone-2/node-3 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 30 20:44:28 node-5 haproxy[10149]: Server keystone-2/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 30 20:44:28 node-5 haproxy[10149]: proxy keystone-2 has no server available!
<129>Jul 30 20:44:28 node-5 haproxy[10149]: Server nova-api/node-3 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 30 20:44:28 node-5 haproxy[10149]: 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 30 20:44:28 node-5 haproxy[10149]: proxy nova-api has no server available!
<129>Jul 30 20:44:28 node-5 haproxy[10149]: Server nova-metadata-api/node-3 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 30 20:44:28 node-5 haproxy[10149]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:44:28 node-5 haproxy[10149]: proxy nova-metadata-api has no server available!
<129>Jul 30 20:44:29 node-5 haproxy[10149]: Server cinder-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:29 node-5 haproxy[10149]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:44:29 node-5 haproxy[10149]: proxy cinder-api has no server available!
<129>Jul 30 20:44:29 node-5 haproxy[10149]: Server glance-api/node-3 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 30 20:44:29 node-5 haproxy[10149]: 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 30 20:44:29 node-5 haproxy[10149]: proxy glance-api has no server available!
<129>Jul 30 20:44:29 node-5 haproxy[10149]: Server glance-glare/node-3 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 30 20:44:29 node-5 haproxy[10149]: 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 30 20:44:29 node-5 haproxy[10149]: proxy glance-glare has no server available!
<129>Jul 30 20:44:29 node-5 haproxy[10149]: Server neutron/node-3 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 30 20:44:29 node-5 haproxy[10149]: 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 30 20:44:29 node-5 haproxy[10149]: proxy neutron has no server available!
<129>Jul 30 20:44:29 node-5 haproxy[10149]: Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 30 20:44:29 node-5 haproxy[10149]: 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 30 20:44:29 node-5 haproxy[10149]: proxy mysqld has no server available!
<129>Jul 30 20:44:29 node-5 haproxy[10149]: Server object-storage/node-3 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 30 20:44:29 node-5 haproxy[10149]: 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 30 20:44:29 node-5 haproxy[10149]: proxy object-storage has no server available!
<129>Jul 30 20:44:30 node-5 haproxy[10149]: Server heat-api/node-3 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 30 20:44:30 node-5 haproxy[10149]: Server heat-api/node-4 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 30 20:44:30 node-5 haproxy[10149]: proxy heat-api has no server available!
<129>Jul 30 20:44:30 node-5 haproxy[10149]: Server heat-api-cfn/node-3 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 30 20:44:30 node-5 haproxy[10149]: 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 30 20:44:30 node-5 haproxy[10149]: proxy heat-api-cfn has no server available!
<129>Jul 30 20:44:30 node-5 haproxy[10149]: Server heat-api-cloudwatch/node-3 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 30 20:44:30 node-5 haproxy[10149]: Server heat-api-cloudwatch/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 30 20:44:30 node-5 haproxy[10149]: proxy heat-api-cloudwatch has no server available!
<27>Jul 30 20:44:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:44:32 node-5 multipathd: uevent trigger error
<27>Jul 30 20:45:07 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 30 20:45:07 node-5 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 30 20:45:38 node-5 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 30 20:45:42 node-5 multipathd: uevent trigger error
<27>Jul 30 20:45:42 node-5 multipathd: uevent trigger error
<27>Jul 30 20:45:42 node-5 multipathd: uevent trigger error
<27>Jul 30 20:45:42 node-5 multipathd: uevent trigger error
<27>Jul 30 20:45:42 node-5 multipathd: uevent trigger error
<27>Jul 30 20:46:19 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 30 20:46:21 node-5 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 30 20:48:00 node-5 multipathd: uevent trigger error
<27>Jul 30 20:48:00 node-5 multipathd: uevent trigger error
<27>Jul 30 20:48:00 node-5 multipathd: uevent trigger error
<27>Jul 30 20:48:00 node-5 multipathd: uevent trigger error
<27>Jul 30 20:48:00 node-5 multipathd: uevent trigger error
<11>Jul 30 20:48:55 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<27>Jul 30 20:51:24 node-5 multipathd: uevent trigger error
<27>Jul 30 20:51:24 node-5 multipathd: uevent trigger error
<27>Jul 30 20:51:24 node-5 multipathd: uevent trigger error
<27>Jul 30 20:51:24 node-5 multipathd: uevent trigger error
<27>Jul 30 20:51:24 node-5 multipathd: uevent trigger error
<43>Jul 30 20:52:41 node-5 apache2_error [Sat Jul 30 20:52:33.373573 2016] [mpm_worker:notice] [pid 8842:tid 139704337237888] AH00295: caught SIGTERM, shutting down
<43>Jul 30 20:52:41 node-5 apache2_error [Sat Jul 30 20:52:34.129144 2016] [mpm_worker:notice] [pid 8334:tid 140526510929792] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 20:52:41 node-5 apache2_error [Sat Jul 30 20:52:34.129204 2016] [core:notice] [pid 8334:tid 140526510929792] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 30 20:53:11 node-5 apache2_error [Sat Jul 30 20:53:06.000868 2016] [mpm_worker:notice] [pid 8334:tid 140526510929792] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 20:53:11 node-5 apache2_error [Sat Jul 30 20:53:06.009935 2016] [mpm_worker:warn] [pid 8334:tid 140526510929792] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 20:53:11 node-5 apache2_error [Sat Jul 30 20:53:06.016072 2016] [mpm_worker:notice] [pid 8334:tid 140526510929792] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 20:53:11 node-5 apache2_error [Sat Jul 30 20:53:06.016095 2016] [core:notice] [pid 8334:tid 140526510929792] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 20:53:11 node-5 multipathd: uevent trigger error
<27>Jul 30 20:53:11 node-5 multipathd: uevent trigger error
<27>Jul 30 20:53:11 node-5 multipathd: uevent trigger error
<27>Jul 30 20:53:11 node-5 multipathd: uevent trigger error
<27>Jul 30 20:53:11 node-5 multipathd: uevent trigger error
<27>Jul 30 20:54:10 node-5 multipathd: uevent trigger error
<27>Jul 30 20:54:10 node-5 multipathd: uevent trigger error
<27>Jul 30 20:54:10 node-5 multipathd: uevent trigger error
<27>Jul 30 20:54:10 node-5 multipathd: uevent trigger error
<27>Jul 30 20:54:10 node-5 multipathd: uevent trigger error
<27>Jul 30 20:55:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:55:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:55:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:55:21 node-5 multipathd: uevent trigger error
<27>Jul 30 20:55:21 node-5 multipathd: uevent trigger error
<11>Jul 30 20:55:51 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<11>Jul 30 20:57:00 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<11>Jul 30 20:58:39 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<11>Jul 30 21:00:01 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<11>Jul 30 21:00:02 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<27>Jul 30 21:00:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:00:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:00:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:00:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:00:22 node-5 multipathd: uevent trigger error
<11>Jul 30 21:01:00 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<27>Jul 30 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 30 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 30 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 30 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 30 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 30 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 30 21:02:28 node-5 multipathd: uevent trigger error
<27>Jul 30 21:03:37 node-5 multipathd: uevent trigger error
<27>Jul 30 21:03:37 node-5 multipathd: uevent trigger error
<27>Jul 30 21:03:37 node-5 multipathd: uevent trigger error
<27>Jul 30 21:03:37 node-5 multipathd: uevent trigger error
<27>Jul 30 21:03:37 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:13 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:13 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:13 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:13 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:13 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:13 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:22 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:27 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:27 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:27 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:27 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:27 node-5 multipathd: uevent trigger error
<27>Jul 30 21:04:27 node-5 multipathd: uevent trigger error
<43>Jul 30 21:05:22 node-5 apache2_error [Sat Jul 30 21:05:18.647332 2016] [mpm_worker:notice] [pid 8334:tid 140526510929792] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 21:05:22 node-5 apache2_error [Sat Jul 30 21:05:19.028340 2016] [mpm_worker:warn] [pid 8334:tid 140526510929792] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 21:05:22 node-5 apache2_error [Sat Jul 30 21:05:19.032605 2016] [mpm_worker:notice] [pid 8334:tid 140526510929792] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 21:05:22 node-5 apache2_error [Sat Jul 30 21:05:19.032622 2016] [core:notice] [pid 8334:tid 140526510929792] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 30 21:06:00 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:00 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:00 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:00 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:00 node-5 multipathd: uevent trigger error
<43>Jul 30 21:06:02 node-5 apache2_error [Sat Jul 30 21:05:55.957556 2016] [mpm_worker:notice] [pid 8334:tid 140526510929792] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 30 21:06:02 node-5 apache2_error [Sat Jul 30 21:05:56.718677 2016] [mpm_worker:warn] [pid 8334:tid 140526510929792] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 30 21:06:02 node-5 apache2_error [Sat Jul 30 21:05:56.732067 2016] [mpm_worker:notice] [pid 8334:tid 140526510929792] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 30 21:06:02 node-5 apache2_error [Sat Jul 30 21:05:56.732115 2016] [core:notice] [pid 8334:tid 140526510929792] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 30 21:06:10 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<27>Jul 30 21:06:18 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:18 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:18 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:18 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:18 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:18 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:34 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:35 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:35 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:50 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:50 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:51 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:51 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:51 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:51 node-5 multipathd: uevent trigger error
<27>Jul 30 21:06:51 node-5 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 30 21:07:39 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:39 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:39 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:39 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:39 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:44 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:44 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:44 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:44 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:44 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:49 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:49 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:49 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:49 node-5 multipathd: uevent trigger error
<27>Jul 30 21:07:49 node-5 multipathd: uevent trigger error
<27>Jul 30 21:08:01 node-5 multipathd: uevent trigger error
<27>Jul 30 21:08:01 node-5 multipathd: uevent trigger error
<27>Jul 30 21:08:01 node-5 multipathd: uevent trigger error
<27>Jul 30 21:08:01 node-5 multipathd: uevent trigger error
<27>Jul 30 21:08:01 node-5 multipathd: uevent trigger error
<27>Jul 30 21:08:36 node-5 multipathd: uevent trigger error
<27>Jul 30 21:08:36 node-5 multipathd: uevent trigger error
<27>Jul 30 21:08:36 node-5 multipathd: uevent trigger error
<27>Jul 30 21:08:36 node-5 multipathd: uevent trigger error
<27>Jul 30 21:08:36 node-5 multipathd: uevent trigger error
<27>Jul 30 21:09:25 node-5 multipathd: uevent trigger error
<27>Jul 30 21:09:25 node-5 multipathd: uevent trigger error
<27>Jul 30 21:09:25 node-5 multipathd: uevent trigger error
<27>Jul 30 21:09:25 node-5 multipathd: uevent trigger error
<27>Jul 30 21:09:25 node-5 multipathd: uevent trigger error
<27>Jul 30 21:09:40 node-5 multipathd: uevent trigger error
<27>Jul 30 21:09:40 node-5 multipathd: uevent trigger error
<27>Jul 30 21:09:40 node-5 multipathd: uevent trigger error
<27>Jul 30 21:09:40 node-5 multipathd: uevent trigger error
<27>Jul 30 21:09:41 node-5 multipathd: uevent trigger error
<11>Jul 30 21:09:43 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<11>Jul 30 21:09:50 node-5 liberasurecode[70142]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:50 node-5 liberasurecode[70142]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:50 node-5 liberasurecode[70142]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:50 node-5 liberasurecode[70142]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:50 node-5 liberasurecode[70171]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:50 node-5 liberasurecode[70171]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:50 node-5 liberasurecode[70171]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:50 node-5 liberasurecode[70171]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:52 node-5 liberasurecode[70598]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:52 node-5 liberasurecode[70598]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:52 node-5 liberasurecode[70598]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:52 node-5 liberasurecode[70598]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71354]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71354]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71354]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71354]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71511]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71511]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71511]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71511]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71604]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71604]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71604]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71604]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71807]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71807]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71807]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71807]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71845]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71845]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71845]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71845]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71869]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71869]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71869]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71869]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71881]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71881]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71881]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:09:58 node-5 liberasurecode[71881]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:10:02 node-5 liberasurecode[73286]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:10:02 node-5 liberasurecode[73286]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:10:02 node-5 liberasurecode[73286]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:10:02 node-5 liberasurecode[73286]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 30 21:10:04 node-5 multipathd: uevent trigger error
<27>Jul 30 21:10:04 node-5 multipathd: uevent trigger error
<27>Jul 30 21:10:04 node-5 multipathd: uevent trigger error
<27>Jul 30 21:10:04 node-5 multipathd: uevent trigger error
<27>Jul 30 21:10:04 node-5 multipathd: uevent trigger error
<27>Jul 30 21:10:04 node-5 multipathd: uevent trigger error
<27>Jul 30 21:10:09 node-5 multipathd: uevent trigger error
<27>Jul 30 21:10:09 node-5 multipathd: uevent trigger error
<27>Jul 30 21:10:09 node-5 multipathd: uevent trigger error
<27>Jul 30 21:10:09 node-5 multipathd: uevent trigger error
<27>Jul 30 21:10:09 node-5 multipathd: uevent trigger error
<11>Jul 30 21:10:38 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<27>Jul 30 21:11:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:11:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:11:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:11:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:11:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:11:17 node-5 multipathd: uevent trigger error
<11>Jul 30 21:12:45 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<27>Jul 30 21:13:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:17 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:23 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:23 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:23 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:23 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:23 node-5 multipathd: uevent trigger error
<11>Jul 30 21:13:23 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
<27>Jul 30 21:13:36 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:36 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:36 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:36 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:36 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:41 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:41 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:41 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:41 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:41 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:41 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:54 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:54 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:54 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:54 node-5 multipathd: uevent trigger error
<27>Jul 30 21:13:54 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:02 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:02 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:02 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:02 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:02 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:02 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:06 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:06 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:06 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:06 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:06 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:11 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:11 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:11 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:11 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:11 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:15 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:15 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:15 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:15 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:15 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:20 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:20 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:20 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:20 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:20 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:20 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:25 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:25 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:25 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:25 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:25 node-5 multipathd: uevent trigger error
<27>Jul 30 21:14:59 node-5 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 30 21:14:59 node-5 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Jul 30 21:15:01 node-5 liberasurecode[123708]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:15:01 node-5 liberasurecode[123708]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:15:01 node-5 liberasurecode[123708]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 30 21:15:01 node-5 liberasurecode[123708]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 30 21:15:22 node-5 epmd: epmd: node name already occupied rabbitmq-cli-41
