Jul 24 20:57:31 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8381" x-info="http://www.rsyslog.com"] start
Jul 24 20:57:31 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 24 20:57:31 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 24 20:57:31 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 24 20:57:31 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 24 20:57:31 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 24 20:57:31 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 24 20:57:31 node-4 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 24 20:57:31 node-4 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=0bb60b1d-e65f-4582-acfb-f09607b839f4 nomdmonddf nomdmonisw
Jul 24 20:57:31 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 24 20:57:31 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 24 20:57:31 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 24 20:57:31 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 24 20:57:31 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 24 20:57:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 24 20:57:31 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 24 20:57:31 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 24 20:57:31 node-4 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 24 20:57:31 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 24 20:57:31 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 24 20:57:31 node-4 kernel: [    0.000000] No AGP bridge found
Jul 24 20:57:31 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 24 20:57:31 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 24 20:57:31 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 24 20:57:31 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 24 20:57:31 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 24 20:57:31 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 24 20:57:31 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 24 20:57:31 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 24 20:57:31 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 24 20:57:31 node-4 kernel: [    0.000000]   2 disabled
Jul 24 20:57:31 node-4 kernel: [    0.000000]   3 disabled
Jul 24 20:57:31 node-4 kernel: [    0.000000]   4 disabled
Jul 24 20:57:31 node-4 kernel: [    0.000000]   5 disabled
Jul 24 20:57:31 node-4 kernel: [    0.000000]   6 disabled
Jul 24 20:57:31 node-4 kernel: [    0.000000]   7 disabled
Jul 24 20:57:31 node-4 kernel: [    0.000000]   8 disabled
Jul 24 20:57:31 node-4 kernel: [    0.000000]   9 disabled
Jul 24 20:57:31 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 24 20:57:31 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 24 20:57:31 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 24 20:57:31 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 24 20:57:31 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 24 20:57:31 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 24 20:57:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 24 20:57:31 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 24 20:57:31 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 24 20:57:31 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 24 20:57:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 24 20:57:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 24 20:57:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 24 20:57:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Jul 24 20:57:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 24 20:57:31 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 24 20:57:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 24 20:57:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 24 20:57:31 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 24 20:57:31 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 24 20:57:31 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 24 20:57:31 node-4 kernel: [    0.000000] Zone ranges:
Jul 24 20:57:31 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 24 20:57:31 node-4 kernel: [    0.000000] Early memory node ranges
Jul 24 20:57:31 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] On node 0 totalpages: 4125855
Jul 24 20:57:31 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 24 20:57:31 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 24 20:57:31 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 24 20:57:31 node-4 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Jul 24 20:57:31 node-4 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Jul 24 20:57:31 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 24 20:57:31 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 24 20:57:31 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 24 20:57:31 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 24 20:57:31 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 24 20:57:31 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 24 20:57:31 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 24 20:57:31 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 24 20:57:31 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 24 20:57:31 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 24 20:57:31 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 24 20:57:31 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 24 20:57:31 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 24 20:57:31 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 24 20:57:31 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 24 20:57:31 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 24 20:57:31 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 24 20:57:31 node-4 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 24 20:57:31 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Jul 24 20:57:31 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 24 20:57:31 node-4 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=0bb60b1d-e65f-4582-acfb-f09607b839f4 nomdmonddf nomdmonisw
Jul 24 20:57:31 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 24 20:57:31 node-4 kernel: [    0.000000] Checking aperture...
Jul 24 20:57:31 node-4 kernel: [    0.000000] No AGP bridge found
Jul 24 20:57:31 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 24 20:57:31 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 24 20:57:31 node-4 kernel: [    0.000000] Memory: 32653460K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 24 20:57:31 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 24 20:57:31 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 24 20:57:31 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 24 20:57:31 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 24 20:57:31 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 24 20:57:31 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 24 20:57:31 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 24 20:57:31 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 24 20:57:31 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 24 20:57:31 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 24 20:57:31 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 24 20:57:31 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 24 20:57:31 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 24 20:57:31 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 24 20:57:31 node-4 kernel: [    0.004000] tsc: Detected 3492.018 MHz processor
Jul 24 20:57:31 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.03 BogoMIPS (lpj=13968072)
Jul 24 20:57:31 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 24 20:57:31 node-4 kernel: [    0.000047] Security Framework initialized
Jul 24 20:57:31 node-4 kernel: [    0.000065] AppArmor: AppArmor initialized
Jul 24 20:57:31 node-4 kernel: [    0.000066] Yama: becoming mindful.
Jul 24 20:57:31 node-4 kernel: [    0.001458] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.006361] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.008293] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.008320] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.008608] Initializing cgroup subsys memory
Jul 24 20:57:31 node-4 kernel: [    0.008616] Initializing cgroup subsys devices
Jul 24 20:57:31 node-4 kernel: [    0.008617] Initializing cgroup subsys freezer
Jul 24 20:57:31 node-4 kernel: [    0.008619] Initializing cgroup subsys blkio
Jul 24 20:57:31 node-4 kernel: [    0.008621] Initializing cgroup subsys perf_event
Jul 24 20:57:31 node-4 kernel: [    0.008623] Initializing cgroup subsys hugetlb
Jul 24 20:57:31 node-4 kernel: [    0.008643] CPU: Physical Processor ID: 0
Jul 24 20:57:31 node-4 kernel: [    0.008644] CPU: Processor Core ID: 0
Jul 24 20:57:31 node-4 kernel: [    0.008648] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 24 20:57:31 node-4 kernel: [    0.008648] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 24 20:57:31 node-4 kernel: [    0.009342] mce: CPU supports 22 MCE banks
Jul 24 20:57:31 node-4 kernel: [    0.009369] CPU0: Thermal monitoring enabled (TM1)
Jul 24 20:57:31 node-4 kernel: [    0.009390] process: using mwait in idle threads
Jul 24 20:57:31 node-4 kernel: [    0.009393] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 24 20:57:31 node-4 kernel: [    0.009393] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 24 20:57:31 node-4 kernel: [    0.009393] tlb_flushall_shift: 6
Jul 24 20:57:31 node-4 kernel: [    0.009483] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 24 20:57:31 node-4 kernel: [    0.010205] ACPI: Core revision 20131115
Jul 24 20:57:31 node-4 kernel: [    0.022888] ACPI: All ACPI Tables successfully acquired
Jul 24 20:57:31 node-4 kernel: [    0.023051] ftrace: allocating 28617 entries in 112 pages
Jul 24 20:57:31 node-4 kernel: [    0.031880] dmar: Host address width 46
Jul 24 20:57:31 node-4 kernel: [    0.031882] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 24 20:57:31 node-4 kernel: [    0.031888] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 20:57:31 node-4 kernel: [    0.031890] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 24 20:57:31 node-4 kernel: [    0.031894] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 24 20:57:31 node-4 kernel: [    0.031895] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 24 20:57:31 node-4 kernel: [    0.031897] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 24 20:57:31 node-4 kernel: [    0.031898] dmar: ATSR flags: 0x0
Jul 24 20:57:31 node-4 kernel: [    0.031899] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 24 20:57:31 node-4 kernel: [    0.031900] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 24 20:57:31 node-4 kernel: [    0.032016] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 24 20:57:31 node-4 kernel: [    0.032017] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 20:57:31 node-4 kernel: [    0.032018] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 24 20:57:31 node-4 kernel: [    0.032019] HPET id 0 under DRHD base 0xc7ffc000
Jul 24 20:57:31 node-4 kernel: [    0.032020] Your BIOS is broken and requested that x2apic be disabled.
Jul 24 20:57:31 node-4 kernel: [    0.032020] This will slightly decrease performance.
Jul 24 20:57:31 node-4 kernel: [    0.032020] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 24 20:57:31 node-4 kernel: [    0.032451] Enabled IRQ remapping in xapic mode
Jul 24 20:57:31 node-4 kernel: [    0.032452] x2apic not enabled, IRQ remapping is in xapic mode
Jul 24 20:57:31 node-4 kernel: [    0.032456] Switched APIC routing to physical flat.
Jul 24 20:57:31 node-4 kernel: [    0.033030] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 24 20:57:31 node-4 kernel: [    0.072681] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 24 20:57:31 node-4 kernel: [    0.072687] TSC deadline timer enabled
Jul 24 20:57:31 node-4 kernel: [    0.072694] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 24 20:57:31 node-4 kernel: [    0.072700] ... version:                3
Jul 24 20:57:31 node-4 kernel: [    0.072701] ... bit width:              48
Jul 24 20:57:31 node-4 kernel: [    0.072702] ... generic registers:      4
Jul 24 20:57:31 node-4 kernel: [    0.072703] ... value mask:             0000ffffffffffff
Jul 24 20:57:31 node-4 kernel: [    0.072704] ... max period:             0000ffffffffffff
Jul 24 20:57:31 node-4 kernel: [    0.072705] ... fixed-purpose events:   3
Jul 24 20:57:31 node-4 kernel: [    0.072706] ... event mask:             000000070000000f
Jul 24 20:57:31 node-4 kernel: [    0.074161] x86: Booting SMP configuration:
Jul 24 20:57:31 node-4 kernel: [    0.088389] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 24 20:57:31 node-4 kernel: [    0.074163] .... node  #0, CPUs:        #1  #2  #3
Jul 24 20:57:31 node-4 kernel: [    0.116304] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 24 20:57:31 node-4 kernel: [    0.270260] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 24 20:57:31 node-4 kernel: [    0.325875] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 24 20:57:31 node-4 kernel: [    0.382730] x86: Booted up 2 nodes, 16 CPUs
Jul 24 20:57:31 node-4 kernel: [    0.382734] smpboot: Total of 16 processors activated (111756.75 BogoMIPS)
Jul 24 20:57:31 node-4 kernel: [    0.406902] devtmpfs: initialized
Jul 24 20:57:31 node-4 kernel: [    0.410008] EVM: security.selinux
Jul 24 20:57:31 node-4 kernel: [    0.410010] EVM: security.SMACK64
Jul 24 20:57:31 node-4 kernel: [    0.410011] EVM: security.ima
Jul 24 20:57:31 node-4 kernel: [    0.410011] EVM: security.capability
Jul 24 20:57:31 node-4 kernel: [    0.410061] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.410728] pinctrl core: initialized pinctrl subsystem
Jul 24 20:57:31 node-4 kernel: [    0.410789] regulator-dummy: no parameters
Jul 24 20:57:31 node-4 kernel: [    0.410820] RTC time: 20:56:56, date: 07/24/16
Jul 24 20:57:31 node-4 kernel: [    0.410855] NET: Registered protocol family 16
Jul 24 20:57:31 node-4 kernel: [    0.410937] cpuidle: using governor ladder
Jul 24 20:57:31 node-4 kernel: [    0.410938] cpuidle: using governor menu
Jul 24 20:57:31 node-4 kernel: [    0.410972] ACPI: bus type PCI registered
Jul 24 20:57:31 node-4 kernel: [    0.410974] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 24 20:57:31 node-4 kernel: [    0.411019] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 24 20:57:31 node-4 kernel: [    0.411022] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 24 20:57:31 node-4 kernel: [    0.424757] PCI: Using configuration type 1 for base access
Jul 24 20:57:31 node-4 kernel: [    0.425754] bio: create slab <bio-0> at 0
Jul 24 20:57:31 node-4 kernel: [    0.426030] ACPI: Added _OSI(Module Device)
Jul 24 20:57:31 node-4 kernel: [    0.426031] ACPI: Added _OSI(Processor Device)
Jul 24 20:57:31 node-4 kernel: [    0.426033] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 24 20:57:31 node-4 kernel: [    0.426034] ACPI: Added _OSI(Processor Aggregator Device)
Jul 24 20:57:31 node-4 kernel: [    0.438718] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 24 20:57:31 node-4 kernel: [    0.449182] ACPI: Interpreter enabled
Jul 24 20:57:31 node-4 kernel: [    0.449188] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 24 20:57:31 node-4 kernel: [    0.449192] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 24 20:57:31 node-4 kernel: [    0.449195] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 24 20:57:31 node-4 kernel: [    0.449201] ACPI: (supports S0 S4 S5)
Jul 24 20:57:31 node-4 kernel: [    0.449203] ACPI: Using IOAPIC for interrupt routing
Jul 24 20:57:31 node-4 kernel: [    0.449245] HEST: Table parsing has been initialized.
Jul 24 20:57:31 node-4 kernel: [    0.449248] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 24 20:57:31 node-4 kernel: [    0.449802] ACPI: No dock devices found.
Jul 24 20:57:31 node-4 kernel: [    0.461424] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 24 20:57:31 node-4 kernel: [    0.461429] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 20:57:31 node-4 kernel: [    0.461433] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 20:57:31 node-4 kernel: [    0.461464] PCI host bridge to bus 0000:ff
Jul 24 20:57:31 node-4 kernel: [    0.461466] pci_bus 0000:ff: root bus resource [bus ff]
Jul 24 20:57:31 node-4 kernel: [    0.461474] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 20:57:31 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 24 20:57:31 node-4 kernel: [    0.461513] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.461543] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461578] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461608] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.461637] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.461668] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461697] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461726] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461754] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461780] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461806] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461833] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461859] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461885] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461911] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461939] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461966] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.461993] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.462020] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462046] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.462073] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462102] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462133] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.462168] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462200] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462230] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462260] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462291] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462323] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462356] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462388] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462418] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462451] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462484] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462517] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462551] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462581] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462608] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462639] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462672] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462713] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462748] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462781] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462812] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462841] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462870] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462905] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462938] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.462970] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463001] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463031] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463059] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463089] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463119] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463150] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463183] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463240] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 24 20:57:31 node-4 kernel: [    0.463243] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 20:57:31 node-4 kernel: [    0.463246] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 24 20:57:31 node-4 kernel: [    0.463264] PCI host bridge to bus 0000:7f
Jul 24 20:57:31 node-4 kernel: [    0.463266] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 24 20:57:31 node-4 kernel: [    0.463271] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463298] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.463327] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463357] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463379] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.463404] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.463430] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463457] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463480] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463502] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463531] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463555] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463581] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463606] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463631] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463660] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463682] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463704] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463727] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.463751] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463773] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.463795] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463819] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463845] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 24 20:57:31 node-4 kernel: [    0.463879] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463905] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463931] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463959] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.463984] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464012] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464039] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464067] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464093] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464121] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464149] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464178] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464206] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464233] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464258] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464286] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464311] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464337] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464367] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464395] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464422] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464448] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464474] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464500] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464527] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464554] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464584] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464609] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464632] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464658] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464684] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464713] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.464743] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.466000] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 24 20:57:31 node-4 kernel: [    0.466004] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 20:57:31 node-4 kernel: [    0.467120] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 20:57:31 node-4 kernel: [    0.467638] PCI host bridge to bus 0000:00
Jul 24 20:57:31 node-4 kernel: [    0.467641] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 24 20:57:31 node-4 kernel: [    0.467642] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 24 20:57:31 node-4 kernel: [    0.467643] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 24 20:57:31 node-4 kernel: [    0.467645] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 24 20:57:31 node-4 kernel: [    0.467646] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 24 20:57:31 node-4 kernel: [    0.467648] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 24 20:57:31 node-4 kernel: [    0.467649] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 24 20:57:31 node-4 kernel: [    0.467655] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 24 20:57:31 node-4 kernel: [    0.467737] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.467767] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.467809] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 24 20:57:31 node-4 kernel: [    0.467828] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.467858] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.467898] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 24 20:57:31 node-4 kernel: [    0.467916] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.467945] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.467985] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 24 20:57:31 node-4 kernel: [    0.468001] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.468070] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.468148] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.468223] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 20:57:31 node-4 kernel: [    0.468227] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 24 20:57:31 node-4 kernel: [    0.468312] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 24 20:57:31 node-4 kernel: [    0.468459] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 24 20:57:31 node-4 kernel: [    0.468477] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 24 20:57:31 node-4 kernel: [    0.468554] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.468609] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 24 20:57:31 node-4 kernel: [    0.468630] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.468685] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.468728] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 24 20:57:31 node-4 kernel: [    0.468754] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.468810] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.468853] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 24 20:57:31 node-4 kernel: [    0.468876] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 24 20:57:31 node-4 kernel: [    0.468894] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 24 20:57:31 node-4 kernel: [    0.468971] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.469020] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 24 20:57:31 node-4 kernel: [    0.469046] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 24 20:57:31 node-4 kernel: [    0.469291] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 24 20:57:31 node-4 kernel: [    0.469297] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 24 20:57:31 node-4 kernel: [    0.469303] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.469309] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.469316] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 24 20:57:31 node-4 kernel: [    0.469346] pci 0000:01:00.0: supports D1 D2
Jul 24 20:57:31 node-4 kernel: [    0.479522] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 20:57:31 node-4 kernel: [    0.479528] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 20:57:31 node-4 kernel: [    0.479532] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 20:57:31 node-4 kernel: [    0.479793] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.479852] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 24 20:57:31 node-4 kernel: [    0.487519] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 20:57:31 node-4 kernel: [    0.487525] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.487540] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:31 node-4 kernel: [    0.487594] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.487662] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.487738] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.487802] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 20:57:31 node-4 kernel: [    0.487806] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.487807] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:31 node-4 kernel: [    0.487860] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.487982] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.488035] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 20:57:31 node-4 kernel: [    0.488037] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.488040] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:31 node-4 kernel: [    0.488088] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.488207] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.488248] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.488367] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.488405] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.488525] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.488561] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 24 20:57:31 node-4 kernel: [    0.488680] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 24 20:57:31 node-4 kernel: [    0.488720] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 20:57:31 node-4 kernel: [    0.488723] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.488725] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:31 node-4 kernel: [    0.488800] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 24 20:57:31 node-4 kernel: [    0.488863] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.488916] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.488957] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 24 20:57:31 node-4 kernel: [    0.489039] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 24 20:57:31 node-4 kernel: [    0.489144] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 20:57:31 node-4 kernel: [    0.489146] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.489148] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 20:57:31 node-4 kernel: [    0.489204] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 24 20:57:31 node-4 kernel: [    0.489260] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.489309] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.489520] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 20:57:31 node-4 kernel: [    0.489524] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 20:57:31 node-4 kernel: [    0.489587] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 24 20:57:31 node-4 kernel: [    0.489640] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.489688] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.489927] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 20:57:31 node-4 kernel: [    0.489930] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 20:57:31 node-4 kernel: [    0.489989] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 24 20:57:31 node-4 kernel: [    0.490049] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.490101] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 24 20:57:31 node-4 kernel: [    0.490323] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 20:57:31 node-4 kernel: [    0.490327] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 20:57:31 node-4 kernel: [    0.490501] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 20:57:31 node-4 kernel: [    0.490539] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 20:57:31 node-4 kernel: [    0.490617] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 24 20:57:31 node-4 kernel: [    0.490636] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 24 20:57:31 node-4 kernel: [    0.490649] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 24 20:57:31 node-4 kernel: [    0.490662] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 24 20:57:31 node-4 kernel: [    0.490712] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 24 20:57:31 node-4 kernel: [    0.495526] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 20:57:31 node-4 kernel: [    0.495535] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 20:57:31 node-4 kernel: [    0.495581] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 24 20:57:31 node-4 kernel: [    0.496071] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 24 20:57:31 node-4 kernel: [    0.496074] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 24 20:57:31 node-4 kernel: [    0.496194] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 24 20:57:31 node-4 kernel: [    0.496303] PCI host bridge to bus 0000:80
Jul 24 20:57:31 node-4 kernel: [    0.496305] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 24 20:57:31 node-4 kernel: [    0.496306] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 24 20:57:31 node-4 kernel: [    0.496308] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 24 20:57:31 node-4 kernel: [    0.496316] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.496379] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.496447] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 24 20:57:31 node-4 kernel: [    0.496509] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 24 20:57:31 node-4 kernel: [    0.496515] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 24 20:57:31 node-4 kernel: [    0.496585] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 24 20:57:31 node-4 kernel: [    0.496882] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 24 20:57:31 node-4 kernel: [    0.496913] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 24 20:57:31 node-4 kernel: [    0.496943] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 24 20:57:31 node-4 kernel: [    0.496972] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 24 20:57:31 node-4 kernel: [    0.497001] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 20:57:31 node-4 kernel: [    0.497031] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 20:57:31 node-4 kernel: [    0.497061] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 20:57:31 node-4 kernel: [    0.497090] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 24 20:57:31 node-4 kernel: [    0.497176] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 24 20:57:31 node-4 kernel: [    0.497180] ACPI: \_SB_.UNC1: notify handler is installed
Jul 24 20:57:31 node-4 kernel: [    0.497181] ACPI: \_SB_.UNC0: notify handler is installed
Jul 24 20:57:31 node-4 kernel: [    0.497196] ACPI: \_SB_.PCI0: notify handler is installed
Jul 24 20:57:31 node-4 kernel: [    0.497250] ACPI: \_SB_.PCI1: notify handler is installed
Jul 24 20:57:31 node-4 kernel: [    0.497329] Found 4 acpi root devices
Jul 24 20:57:31 node-4 kernel: [    0.497452] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 24 20:57:31 node-4 kernel: [    0.497454] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 24 20:57:31 node-4 kernel: [    0.497455] vgaarb: loaded
Jul 24 20:57:31 node-4 kernel: [    0.497456] vgaarb: bridge control possible 0000:0c:00.0
Jul 24 20:57:31 node-4 kernel: [    0.497580] SCSI subsystem initialized
Jul 24 20:57:31 node-4 kernel: [    0.497642] libata version 3.00 loaded.
Jul 24 20:57:31 node-4 kernel: [    0.497661] ACPI: bus type USB registered
Jul 24 20:57:31 node-4 kernel: [    0.497671] usbcore: registered new interface driver usbfs
Jul 24 20:57:31 node-4 kernel: [    0.497676] usbcore: registered new interface driver hub
Jul 24 20:57:31 node-4 kernel: [    0.497697] usbcore: registered new device driver usb
Jul 24 20:57:31 node-4 kernel: [    0.497862] PCI: Using ACPI for IRQ routing
Jul 24 20:57:31 node-4 kernel: [    0.501447] PCI: pci_cache_line_size set to 64 bytes
Jul 24 20:57:31 node-4 kernel: [    0.501649] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 24 20:57:31 node-4 kernel: [    0.501650] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Jul 24 20:57:31 node-4 kernel: [    0.501651] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 24 20:57:31 node-4 kernel: [    0.501718] NetLabel: Initializing
Jul 24 20:57:31 node-4 kernel: [    0.501719] NetLabel:  domain hash size = 128
Jul 24 20:57:31 node-4 kernel: [    0.501720] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 24 20:57:31 node-4 kernel: [    0.501730] NetLabel:  unlabeled traffic allowed by default
Jul 24 20:57:31 node-4 kernel: [    0.501787] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 24 20:57:31 node-4 kernel: [    0.501791] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 24 20:57:31 node-4 kernel: [    0.503860] Switched to clocksource hpet
Jul 24 20:57:31 node-4 kernel: [    0.508227] AppArmor: AppArmor Filesystem Enabled
Jul 24 20:57:31 node-4 kernel: [    0.508265] pnp: PnP ACPI init
Jul 24 20:57:31 node-4 kernel: [    0.508277] ACPI: bus type PNP registered
Jul 24 20:57:31 node-4 kernel: [    0.508458] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 24 20:57:31 node-4 kernel: [    0.508469] pnp 00:01: [dma 4]
Jul 24 20:57:31 node-4 kernel: [    0.508487] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 24 20:57:31 node-4 kernel: [    0.508522] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 24 20:57:31 node-4 kernel: [    0.508546] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 24 20:57:31 node-4 kernel: [    0.508568] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 24 20:57:31 node-4 kernel: [    0.508613] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 24 20:57:31 node-4 kernel: [    0.508725] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508728] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 24 20:57:31 node-4 kernel: [    0.508730] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508731] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508733] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508734] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508738] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 24 20:57:31 node-4 kernel: [    0.508739] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508741] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508743] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508744] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508746] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508747] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 24 20:57:31 node-4 kernel: [    0.508750] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 24 20:57:31 node-4 kernel: [    0.508849] pnp 00:07: [dma 0 disabled]
Jul 24 20:57:31 node-4 kernel: [    0.508882] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 20:57:31 node-4 kernel: [    0.508963] pnp 00:08: [dma 0 disabled]
Jul 24 20:57:31 node-4 kernel: [    0.508998] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 24 20:57:31 node-4 kernel: [    0.509057] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 24 20:57:31 node-4 kernel: [    0.509502] pnp: PnP ACPI: found 10 devices
Jul 24 20:57:31 node-4 kernel: [    0.509504] ACPI: bus type PNP unregistered
Jul 24 20:57:31 node-4 kernel: [    0.515537] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 24 20:57:31 node-4 kernel: [    0.515541] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 24 20:57:31 node-4 kernel: [    0.515544] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 24 20:57:31 node-4 kernel: [    0.515549] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 24 20:57:31 node-4 kernel: [    0.515551] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.515566] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515595] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 24 20:57:31 node-4 kernel: [    0.515610] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515639] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 24 20:57:31 node-4 kernel: [    0.515653] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 24 20:57:31 node-4 kernel: [    0.515683] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 24 20:57:31 node-4 kernel: [    0.515697] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 24 20:57:31 node-4 kernel: [    0.515726] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 24 20:57:31 node-4 kernel: [    0.515728] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.515758] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515786] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 24 20:57:31 node-4 kernel: [    0.515788] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.515803] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515839] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 24 20:57:31 node-4 kernel: [    0.515841] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.515844] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515849] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 24 20:57:31 node-4 kernel: [    0.515850] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.515853] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515857] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 24 20:57:31 node-4 kernel: [    0.515863] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 24 20:57:31 node-4 kernel: [    0.515872] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 24 20:57:31 node-4 kernel: [    0.515876] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 24 20:57:31 node-4 kernel: [    0.515883] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 24 20:57:31 node-4 kernel: [    0.515884] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 24 20:57:31 node-4 kernel: [    0.515885] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 24 20:57:31 node-4 kernel: [    0.515886] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 24 20:57:31 node-4 kernel: [    0.515887] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 24 20:57:31 node-4 kernel: [    0.515888] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 24 20:57:31 node-4 kernel: [    0.515889] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 24 20:57:31 node-4 kernel: [    0.515889] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 24 20:57:31 node-4 kernel: [    0.515891] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.515892] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515893] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.515894] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515895] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.515896] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515897] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.515897] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515898] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 24 20:57:31 node-4 kernel: [    0.515899] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515901] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 24 20:57:31 node-4 kernel: [    0.515902] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 24 20:57:31 node-4 kernel: [    0.515903] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 24 20:57:31 node-4 kernel: [    0.515904] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 24 20:57:31 node-4 kernel: [    0.515907] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 24 20:57:31 node-4 kernel: [    0.515908] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 24 20:57:31 node-4 kernel: [    0.515949] NET: Registered protocol family 2
Jul 24 20:57:31 node-4 kernel: [    0.516248] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.516621] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.516787] TCP: Hash tables configured (established 262144 bind 65536)
Jul 24 20:57:31 node-4 kernel: [    0.516830] TCP: reno registered
Jul 24 20:57:31 node-4 kernel: [    0.516862] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.516970] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.517140] NET: Registered protocol family 1
Jul 24 20:57:31 node-4 kernel: [    0.555949] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 24 20:57:31 node-4 kernel: [    0.555963] PCI: CLS 64 bytes, default 64
Jul 24 20:57:31 node-4 kernel: [    0.556048] Trying to unpack rootfs image as initramfs...
Jul 24 20:57:31 node-4 kernel: [    0.777477] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 24 20:57:31 node-4 kernel: [    0.777524] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 24 20:57:31 node-4 kernel: [    0.777527] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Jul 24 20:57:31 node-4 kernel: [    0.777935] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.777943] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.777951] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.777958] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.777966] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.777973] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.777978] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.777984] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.777991] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.777998] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.778007] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.778013] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.778019] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.778026] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.778032] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.778038] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 24 20:57:31 node-4 kernel: [    0.778083] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 24 20:57:31 node-4 kernel: [    0.778085] Scanning for low memory corruption every 60 seconds
Jul 24 20:57:31 node-4 kernel: [    0.778376] Initialise system trusted keyring
Jul 24 20:57:31 node-4 kernel: [    0.778422] audit: initializing netlink socket (disabled)
Jul 24 20:57:31 node-4 kernel: [    0.778433] type=2000 audit(1469393815.728:1): initialized
Jul 24 20:57:31 node-4 kernel: [    0.796351] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 24 20:57:31 node-4 kernel: [    0.797812] zbud: loaded
Jul 24 20:57:31 node-4 kernel: [    0.797941] VFS: Disk quotas dquot_6.5.2
Jul 24 20:57:31 node-4 kernel: [    0.797980] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 24 20:57:31 node-4 kernel: [    0.798339] fuse init (API version 7.22)
Jul 24 20:57:31 node-4 kernel: [    0.798393] msgmni has been set to 32768
Jul 24 20:57:31 node-4 kernel: [    0.798439] Key type big_key registered
Jul 24 20:57:31 node-4 kernel: [    0.798996] Key type asymmetric registered
Jul 24 20:57:31 node-4 kernel: [    0.798998] Asymmetric key parser 'x509' registered
Jul 24 20:57:31 node-4 kernel: [    0.799020] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 24 20:57:31 node-4 kernel: [    0.799084] io scheduler noop registered
Jul 24 20:57:31 node-4 kernel: [    0.799085] io scheduler deadline registered (default)
Jul 24 20:57:31 node-4 kernel: [    0.799103] io scheduler cfq registered
Jul 24 20:57:31 node-4 kernel: [    0.799646] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    0.799816] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    0.799944] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    0.800056] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    0.800169] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    0.800258] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    0.800631] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 24 20:57:31 node-4 kernel: [    0.800657] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 24 20:57:31 node-4 kernel: [    0.800679] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 24 20:57:31 node-4 kernel: [    0.800691] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800693] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800696] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 24 20:57:31 node-4 kernel: [    0.800701] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800703] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800704] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800706] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800707] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800708] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800709] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800711] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800712] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800714] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800715] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800717] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800719] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 24 20:57:31 node-4 kernel: [    0.800730] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800732] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 24 20:57:31 node-4 kernel: [    0.800743] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800746] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 24 20:57:31 node-4 kernel: [    0.800757] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800758] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 24 20:57:31 node-4 kernel: [    0.800761] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 24 20:57:31 node-4 kernel: [    0.800790] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 24 20:57:31 node-4 kernel: [    0.800795] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 24 20:57:31 node-4 kernel: [    0.800799] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 24 20:57:31 node-4 kernel: [    0.800807] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 24 20:57:31 node-4 kernel: [    0.800845] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 24 20:57:31 node-4 kernel: [    0.800847] vesafb: scrolling: redraw
Jul 24 20:57:31 node-4 kernel: [    0.800848] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 24 20:57:31 node-4 kernel: [    0.821252] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 24 20:57:31 node-4 kernel: [    0.829739] Console: switching to colour frame buffer device 80x30
Jul 24 20:57:31 node-4 kernel: [    0.838415] fb0: VESA VGA frame buffer device
Jul 24 20:57:31 node-4 kernel: [    0.838613] intel_idle: MWAIT substates: 0x2120
Jul 24 20:57:31 node-4 kernel: [    0.838614] intel_idle: v0.4 model 0x3F
Jul 24 20:57:31 node-4 kernel: [    0.838615] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 24 20:57:31 node-4 kernel: [    0.838839] ipmi message handler version 39.2
Jul 24 20:57:31 node-4 kernel: [    0.839108] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 24 20:57:31 node-4 kernel: [    0.839540] ACPI: AC Adapter [P111] (on-line)
Jul 24 20:57:31 node-4 kernel: [    0.844779] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 24 20:57:31 node-4 kernel: [    0.855766] ACPI: Power Button [PWRB]
Jul 24 20:57:31 node-4 kernel: [    0.861532] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 24 20:57:31 node-4 kernel: [    0.873239] ACPI: Power Button [PWRF]
Jul 24 20:57:31 node-4 kernel: [    0.889411] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 24 20:57:31 node-4 kernel: [    0.901060] pstore: Registered erst as persistent store backend
Jul 24 20:57:31 node-4 kernel: [    0.907258] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 24 20:57:31 node-4 kernel: [    0.919196] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 24 20:57:31 node-4 kernel: [    0.945929] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 24 20:57:31 node-4 kernel: [    0.979220] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 24 20:57:31 node-4 kernel: [    0.993325] Linux agpgart interface v0.103
Jul 24 20:57:31 node-4 kernel: [    1.000999] brd: module loaded
Jul 24 20:57:31 node-4 kernel: [    1.008071] loop: module loaded
Jul 24 20:57:31 node-4 kernel: [    1.014799] libphy: Fixed MDIO Bus: probed
Jul 24 20:57:31 node-4 kernel: [    1.021291] tun: Universal TUN/TAP device driver, 1.6
Jul 24 20:57:31 node-4 kernel: [    1.027793] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 24 20:57:31 node-4 kernel: [    1.034411] PPP generic driver version 2.4.2
Jul 24 20:57:31 node-4 kernel: [    1.040803] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 24 20:57:31 node-4 kernel: [    1.047281] ehci-pci: EHCI PCI platform driver
Jul 24 20:57:31 node-4 kernel: [    1.053816] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 24 20:57:31 node-4 kernel: [    1.060237] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 24 20:57:31 node-4 kernel: [    1.072779] ehci-pci 0000:00:1a.0: debug port 2
Jul 24 20:57:31 node-4 kernel: [    1.082980] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 24 20:57:31 node-4 kernel: [    1.082999] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 24 20:57:31 node-4 kernel: [    1.099347] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 24 20:57:31 node-4 kernel: [    1.105415] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 20:57:31 node-4 kernel: [    1.111588] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 20:57:31 node-4 kernel: [    1.123596] usb usb1: Product: EHCI Host Controller
Jul 24 20:57:31 node-4 kernel: [    1.129702] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 20:57:31 node-4 kernel: [    1.135753] usb usb1: SerialNumber: 0000:00:1a.0
Jul 24 20:57:31 node-4 kernel: [    1.141725] hub 1-0:1.0: USB hub found
Jul 24 20:57:31 node-4 kernel: [    1.147504] hub 1-0:1.0: 2 ports detected
Jul 24 20:57:31 node-4 kernel: [    1.153328] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 24 20:57:31 node-4 kernel: [    1.158909] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 24 20:57:31 node-4 kernel: [    1.169822] ehci-pci 0000:00:1d.0: debug port 2
Jul 24 20:57:31 node-4 kernel: [    1.179120] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 24 20:57:31 node-4 kernel: [    1.179123] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 24 20:57:31 node-4 kernel: [    1.195266] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 24 20:57:31 node-4 kernel: [    1.200470] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 24 20:57:31 node-4 kernel: [    1.205778] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 24 20:57:31 node-4 kernel: [    1.216357] usb usb2: Product: EHCI Host Controller
Jul 24 20:57:31 node-4 kernel: [    1.221824] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 24 20:57:31 node-4 kernel: [    1.227369] usb usb2: SerialNumber: 0000:00:1d.0
Jul 24 20:57:31 node-4 kernel: [    1.232916] hub 2-0:1.0: USB hub found
Jul 24 20:57:31 node-4 kernel: [    1.238261] hub 2-0:1.0: 2 ports detected
Jul 24 20:57:31 node-4 kernel: [    1.243586] ehci-platform: EHCI generic platform driver
Jul 24 20:57:31 node-4 kernel: [    1.248837] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 24 20:57:31 node-4 kernel: [    1.254154] ohci-pci: OHCI PCI platform driver
Jul 24 20:57:31 node-4 kernel: [    1.259469] ohci-platform: OHCI generic platform driver
Jul 24 20:57:31 node-4 kernel: [    1.264677] uhci_hcd: USB Universal Host Controller Interface driver
Jul 24 20:57:31 node-4 kernel: [    1.270028] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 24 20:57:31 node-4 kernel: [    1.463046] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 24 20:57:31 node-4 kernel: [    1.635267] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 24 20:57:31 node-4 kernel: [    1.640791] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 20:57:31 node-4 kernel: [    1.646534] hub 1-1:1.0: USB hub found
Jul 24 20:57:31 node-4 kernel: [    1.652004] hub 1-1:1.0: 6 ports detected
Jul 24 20:57:31 node-4 kernel: [    1.766781] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 24 20:57:31 node-4 kernel: [    2.034928] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 24 20:57:31 node-4 kernel: [    2.040457] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 24 20:57:31 node-4 kernel: [    2.046070] hub 2-1:1.0: USB hub found
Jul 24 20:57:31 node-4 kernel: [    2.051664] hub 2-1:1.0: 8 ports detected
Jul 24 20:57:31 node-4 kernel: [    2.310708] i8042: No controller found
Jul 24 20:57:31 node-4 kernel: [    2.316136] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 24 20:57:31 node-4 kernel: [    2.317400] mousedev: PS/2 mouse device common for all mice
Jul 24 20:57:31 node-4 kernel: [    2.319311] rtc_cmos 00:02: RTC can wake from S4
Jul 24 20:57:31 node-4 kernel: [    2.321006] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 24 20:57:31 node-4 kernel: [    2.321591] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 24 20:57:31 node-4 kernel: [    2.322526] device-mapper: uevent: version 1.0.3
Jul 24 20:57:31 node-4 kernel: [    2.323655] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 24 20:57:31 node-4 kernel: [    2.323864] ledtrig-cpu: registered to indicate activity on CPUs
Jul 24 20:57:31 node-4 kernel: [    2.325715] TCP: cubic registered
Jul 24 20:57:31 node-4 kernel: [    2.326395] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 24 20:57:31 node-4 kernel: [    2.327069] NET: Registered protocol family 10
Jul 24 20:57:31 node-4 kernel: [    2.329640] NET: Registered protocol family 17
Jul 24 20:57:31 node-4 kernel: [    2.329784] Key type dns_resolver registered
Jul 24 20:57:31 node-4 kernel: [    2.336309] Loading compiled-in X.509 certificates
Jul 24 20:57:31 node-4 kernel: [    2.338209] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 24 20:57:31 node-4 kernel: [    2.338692] registered taskstats version 1
Jul 24 20:57:31 node-4 kernel: [    2.366740] Key type trusted registered
Jul 24 20:57:31 node-4 kernel: [    2.374672] Key type encrypted registered
Jul 24 20:57:31 node-4 kernel: [    2.374675] AppArmor: AppArmor sha1 policy hashing enabled
Jul 24 20:57:31 node-4 kernel: [    2.374711] IMA: No TPM chip found, activating TPM-bypass!
Jul 24 20:57:31 node-4 kernel: [    2.383389] regulator-dummy: disabling
Jul 24 20:57:31 node-4 kernel: [    2.384062]   Magic number: 8:822:953
Jul 24 20:57:31 node-4 kernel: [    2.386913] processor cpu8: hash matches
Jul 24 20:57:31 node-4 kernel: [    2.387624] memory memory6: hash matches
Jul 24 20:57:31 node-4 kernel: [    2.466767] rtc_cmos 00:02: setting system clock to 2016-07-24 20:56:58 UTC (1469393818)
Jul 24 20:57:31 node-4 kernel: [    2.479110] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 24 20:57:31 node-4 kernel: [    2.484736] EDD information not available.
Jul 24 20:57:31 node-4 kernel: [    2.490312] PM: Hibernation image not present or could not be loaded.
Jul 24 20:57:31 node-4 kernel: [    2.491178] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 24 20:57:31 node-4 kernel: [    2.502501] Write protecting the kernel read-only data: 12288k
Jul 24 20:57:31 node-4 kernel: [    2.508812] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 24 20:57:31 node-4 kernel: [    2.521463] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 24 20:57:31 node-4 kernel: [    2.527618] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 24 20:57:31 node-4 kernel: [    2.527619] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 24 20:57:31 node-4 kernel: [    2.527620] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 24 20:57:31 node-4 kernel: [    2.527621] usb 2-1.4: Manufacturer: Avocent
Jul 24 20:57:31 node-4 kernel: [    2.527621] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 24 20:57:31 node-4 kernel: [    2.590286] device-mapper: multipath: version 1.6.0 loaded
Jul 24 20:57:31 node-4 kernel: [    2.598244] systemd-udevd[214]: starting version 204
Jul 24 20:57:31 node-4 kernel: [    2.623058] md: linear personality registered for level -1
Jul 24 20:57:31 node-4 kernel: [    2.636928] md: multipath personality registered for level -4
Jul 24 20:57:31 node-4 kernel: [    2.644951] md: raid0 personality registered for level 0
Jul 24 20:57:31 node-4 kernel: [    2.654144] md: raid1 personality registered for level 1
Jul 24 20:57:31 node-4 kernel: [    2.660495] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 24 20:57:31 node-4 kernel: [    2.666865] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 24 20:57:31 node-4 kernel: [    2.667114] hidraw: raw HID events driver (C) Jiri Kosina
Jul 24 20:57:31 node-4 kernel: [    2.679697] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 24 20:57:31 node-4 kernel: [    2.680200] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Jul 24 20:57:31 node-4 kernel: [    2.680204] enic 0000:06:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 20:57:31 node-4 kernel: [    2.680206] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 20:57:31 node-4 kernel: [    2.680608] enic 0000:06:00.0: irq 96 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.680704] enic 0000:06:00.0: irq 97 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.680857] enic 0000:06:00.0: irq 98 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.681034] enic 0000:06:00.0: irq 99 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.681399] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.701009] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Jul 24 20:57:31 node-4 kernel: [    2.701055] enic 0000:07:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 20:57:31 node-4 kernel: [    2.701081] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 20:57:31 node-4 kernel: [    2.701594] enic 0000:07:00.0: irq 100 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.701747] enic 0000:07:00.0: irq 101 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.701903] enic 0000:07:00.0: irq 102 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.702307] enic 0000:07:00.0: irq 103 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.702639] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.719744] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Jul 24 20:57:31 node-4 kernel: [    2.719748] enic 0000:08:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 20:57:31 node-4 kernel: [    2.719754] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 20:57:31 node-4 kernel: [    2.719974] enic 0000:08:00.0: irq 104 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.720079] enic 0000:08:00.0: irq 105 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.720202] enic 0000:08:00.0: irq 106 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.720338] enic 0000:08:00.0: irq 107 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.720596] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.734300] raid6: sse2x1     523 MB/s
Jul 24 20:57:31 node-4 kernel: [    2.734580] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Jul 24 20:57:31 node-4 kernel: [    2.734596] enic 0000:09:00.0: vNIC csum tx/rx yes/yes tso/lro yes/yes rss no intr mode any type min timer 125 usec loopback tag 0x0000
Jul 24 20:57:31 node-4 kernel: [    2.734612] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 24 20:57:31 node-4 kernel: [    2.734940] enic 0000:09:00.0: irq 108 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.735083] enic 0000:09:00.0: irq 109 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.735166] enic 0000:09:00.0: irq 110 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.735308] enic 0000:09:00.0: irq 111 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.735550] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.802072] raid6: sse2x2     721 MB/s
Jul 24 20:57:31 node-4 kernel: [    2.869966] raid6: sse2x4     948 MB/s
Jul 24 20:57:31 node-4 kernel: [    2.892120] megasas: FW now in Ready state
Jul 24 20:57:31 node-4 kernel: [    2.898525] megaraid_sas 0000:01:00.0: irq 112 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898530] megaraid_sas 0000:01:00.0: irq 113 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898533] megaraid_sas 0000:01:00.0: irq 114 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898537] megaraid_sas 0000:01:00.0: irq 115 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898542] megaraid_sas 0000:01:00.0: irq 116 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898546] megaraid_sas 0000:01:00.0: irq 117 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898549] megaraid_sas 0000:01:00.0: irq 118 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898553] megaraid_sas 0000:01:00.0: irq 119 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898557] megaraid_sas 0000:01:00.0: irq 120 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898561] megaraid_sas 0000:01:00.0: irq 121 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898564] megaraid_sas 0000:01:00.0: irq 122 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898568] megaraid_sas 0000:01:00.0: irq 123 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898572] megaraid_sas 0000:01:00.0: irq 124 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898575] megaraid_sas 0000:01:00.0: irq 125 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898579] megaraid_sas 0000:01:00.0: irq 126 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898583] megaraid_sas 0000:01:00.0: irq 127 for MSI/MSI-X
Jul 24 20:57:31 node-4 kernel: [    2.898612] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 24 20:57:31 node-4 kernel: [    2.912606] usbcore: registered new interface driver usbhid
Jul 24 20:57:31 node-4 kernel: [    2.919146] usbhid: USB HID core driver
Jul 24 20:57:31 node-4 kernel: [    2.926628] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.0/input/input2
Jul 24 20:57:31 node-4 kernel: [    2.937895] raid6: avx2x1    2249 MB/s
Jul 24 20:57:31 node-4 kernel: [    2.946057] hid-generic 0003:0624:0402.0001: input,hidraw0: USB HID v1.00 Keyboard [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input0
Jul 24 20:57:31 node-4 kernel: [    2.959077] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.1/input/input3
Jul 24 20:57:31 node-4 kernel: [    2.972488] hid-generic 0003:0624:0402.0002: input,hidraw1: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input1
Jul 24 20:57:31 node-4 kernel: [    2.985998] input: Avocent Cisco USB Composite Device-0 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.4/2-1.4:1.2/input/input4
Jul 24 20:57:31 node-4 kernel: [    2.999597] hid-generic 0003:0624:0402.0003: input,hidraw2: USB HID v1.00 Mouse [Avocent Cisco USB Composite Device-0] on usb-0000:00:1d.0-1.4/input2
Jul 24 20:57:31 node-4 kernel: [    3.005784] raid6: avx2x2   23744 MB/s
Jul 24 20:57:31 node-4 kernel: [    3.081678] raid6: avx2x4   28891 MB/s
Jul 24 20:57:31 node-4 kernel: [    3.088476] raid6: using algorithm avx2x4 (28891 MB/s)
Jul 24 20:57:31 node-4 kernel: [    3.095240] raid6: using avx2x2 recovery algorithm
Jul 24 20:57:31 node-4 kernel: [    3.102669] xor: automatically using best checksumming function:
Jul 24 20:57:31 node-4 kernel: [    3.145603]    avx       : 35708.000 MB/sec
Jul 24 20:57:31 node-4 kernel: [    3.152775] async_tx: api initialized (async)
Jul 24 20:57:31 node-4 kernel: [    3.163259] md: raid6 personality registered for level 6
Jul 24 20:57:31 node-4 kernel: [    3.169767] md: raid5 personality registered for level 5
Jul 24 20:57:31 node-4 kernel: [    3.176047] md: raid4 personality registered for level 4
Jul 24 20:57:31 node-4 kernel: [    3.185348] md: raid10 personality registered for level 10
Jul 24 20:57:31 node-4 kernel: [    3.238477] multipathd (353): /proc/353/oom_adj is deprecated, please use /proc/353/oom_score_adj instead.
Jul 24 20:57:31 node-4 kernel: [    3.246232] megasas:IOC Init cmd success
Jul 24 20:57:31 node-4 kernel: [    3.269559] megasas: INIT adapter done
Jul 24 20:57:31 node-4 kernel: [    3.369465] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 24 20:57:31 node-4 kernel: [    3.375621] scsi0 : LSI SAS based MegaRAID driver
Jul 24 20:57:31 node-4 kernel: [    3.383197] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 20:57:31 node-4 kernel: [    3.400821] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 24 20:57:31 node-4 kernel: [    3.414799] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 24 20:57:31 node-4 kernel: [    3.420548] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 24 20:57:31 node-4 kernel: [    3.431977] sd 0:2:0:0: [sda] Write Protect is off
Jul 24 20:57:31 node-4 kernel: [    3.437726] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 24 20:57:31 node-4 kernel: [    3.437750] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 24 20:57:31 node-4 kernel: [    3.465542] Switched to clocksource tsc
Jul 24 20:57:31 node-4 kernel: [    3.476373]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 24 20:57:31 node-4 kernel: [    3.482615] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 24 20:57:31 node-4 kernel: [    3.610428] random: lvm urandom read with 25 bits of entropy available
Jul 24 20:57:31 node-4 kernel: [    3.740568] bio: create slab <bio-1> at 1
Jul 24 20:57:31 node-4 kernel: [    4.491484] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 20:57:31 node-4 kernel: [    5.014717] init: plymouth-upstart-bridge main process (552) terminated with status 1
Jul 24 20:57:31 node-4 kernel: [    5.027128] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 20:57:31 node-4 kernel: [    5.036596] init: plymouth-upstart-bridge main process (563) terminated with status 1
Jul 24 20:57:31 node-4 kernel: [    5.049255] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 20:57:31 node-4 kernel: [    5.058504] init: plymouth-upstart-bridge main process (565) terminated with status 1
Jul 24 20:57:31 node-4 kernel: [    5.071110] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 20:57:31 node-4 kernel: [    5.212173] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 24 20:57:31 node-4 kernel: [    5.251664] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 24 20:57:31 node-4 kernel: [    5.363877] random: nonblocking pool is initialized
Jul 24 20:57:31 node-4 kernel: [    5.383093] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 24 20:57:31 node-4 kernel: [    5.454945] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 24 20:57:31 node-4 kernel: [    5.518139] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 20:57:31 node-4 kernel: [    5.697120] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 24 20:57:31 node-4 kernel: [    5.758030] XFS (dm-0): Mounting Filesystem
Jul 24 20:57:31 node-4 kernel: [    5.983623] XFS (dm-0): Ending clean mount
Jul 24 20:57:31 node-4 kernel: [    6.027027] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 24 20:57:31 node-4 kernel: [    6.075172] XFS (dm-1): Mounting Filesystem
Jul 24 20:57:31 node-4 kernel: [    6.221283] XFS (dm-1): Ending clean mount
Jul 24 20:57:31 node-4 kernel: [    8.059413] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 20:57:31 node-4 kernel: [    8.084461] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 20:57:31 node-4 kernel: [    8.249077] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 24 20:57:31 node-4 kernel: [    8.249082] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 24 20:57:31 node-4 kernel: [    8.249085] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 24 20:57:31 node-4 kernel: [    8.249089] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 24 20:57:31 node-4 kernel: [    8.296713] systemd-udevd[781]: starting version 204
Jul 24 20:57:31 node-4 kernel: [    8.520138] wmi: Mapper loaded
Jul 24 20:57:31 node-4 kernel: [    8.527942] IPMI System Interface driver.
Jul 24 20:57:31 node-4 kernel: [    8.528044] ipmi_si: probing via ACPI
Jul 24 20:57:31 node-4 kernel: [    8.528056] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 24 20:57:31 node-4 kernel: [    8.528057] ipmi_si: Adding ACPI-specified kcs state machine
Jul 24 20:57:31 node-4 kernel: [    8.528071] ipmi_si: probing via SMBIOS
Jul 24 20:57:31 node-4 kernel: [    8.528072] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 20:57:31 node-4 kernel: [    8.528073] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 24 20:57:31 node-4 kernel: [    8.528075] ipmi_si: probing via SPMI
Jul 24 20:57:31 node-4 kernel: [    8.528076] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 24 20:57:31 node-4 kernel: [    8.528076] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 24 20:57:31 node-4 kernel: [    8.528077] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 24 20:57:31 node-4 kernel: [    8.528096] power_meter ACPI000D:00: Found ACPI power meter.
Jul 24 20:57:31 node-4 kernel: [    8.528114] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 24 20:57:31 node-4 kernel: [    8.597537] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 24 20:57:31 node-4 kernel: [    8.597543] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 20:57:31 node-4 kernel: [    8.597546] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 24 20:57:31 node-4 kernel: [    8.597547] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 24 20:57:31 node-4 kernel: [    8.597560] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 24 20:57:31 node-4 kernel: [    8.625117] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 24 20:57:31 node-4 kernel: [    8.676646] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 24 20:57:31 node-4 kernel: [    8.676655] ipmi_si 00:09: IPMI kcs interface initialized
Jul 24 20:57:31 node-4 kernel: [    8.697494] systemd-udevd[802]: renamed network interface eth0 to enp6s0
Jul 24 20:57:31 node-4 kernel: [    8.733538] systemd-udevd[799]: renamed network interface eth1 to enp7s0
Jul 24 20:57:31 node-4 kernel: [    8.769372] systemd-udevd[809]: renamed network interface eth2 to enp8s0
Jul 24 20:57:31 node-4 kernel: [    8.789325] systemd-udevd[817]: renamed network interface eth3 to enp9s0
Jul 24 20:57:31 node-4 kernel: [    9.005252] type=1400 audit(1469393825.119:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1072 comm="apparmor_parser"
Jul 24 20:57:31 node-4 kernel: [    9.005411] type=1400 audit(1469393825.119:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1072 comm="apparmor_parser"
Jul 24 20:57:31 node-4 kernel: [    9.005538] type=1400 audit(1469393825.119:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1072 comm="apparmor_parser"
Jul 24 20:57:31 node-4 kernel: [    9.006237] type=1400 audit(1469393825.119:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1073 comm="apparmor_parser"
Jul 24 20:57:31 node-4 kernel: [    9.006408] type=1400 audit(1469393825.119:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1073 comm="apparmor_parser"
Jul 24 20:57:31 node-4 kernel: [    9.006538] type=1400 audit(1469393825.119:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1073 comm="apparmor_parser"
Jul 24 20:57:31 node-4 kernel: [    9.019760] type=1400 audit(1469393825.131:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1070 comm="apparmor_parser"
Jul 24 20:57:31 node-4 kernel: [    9.019903] type=1400 audit(1469393825.131:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1070 comm="apparmor_parser"
Jul 24 20:57:31 node-4 kernel: [    9.020023] type=1400 audit(1469393825.131:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1070 comm="apparmor_parser"
Jul 24 20:57:31 node-4 kernel: [    9.023081] type=1400 audit(1469393825.135:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1076 comm="apparmor_parser"
Jul 24 20:57:31 node-4 kernel: [    9.644170] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 24 20:57:31 node-4 kernel: [    9.644927] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 24 20:57:31 node-4 kernel: [    9.951419] enic 0000:06:00.0 enp6s0: Link UP
Jul 24 20:57:31 node-4 kernel: [    9.951872] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 24 20:57:31 node-4 kernel: [    9.951879] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 24 20:57:31 node-4 kernel: [   19.029453] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 24 20:57:33 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 24 20:57:33 node-4 kernel: [   37.710167] init: failsafe main process (8408) killed by TERM signal
Jul 24 20:57:33 node-4 dbus[8445]: [system] AppArmor D-Bus mediation is enabled
Jul 24 20:57:33 node-4 kernel: [   37.907109] audit_printk_skb: 30 callbacks suppressed
Jul 24 20:57:33 node-4 kernel: [   37.907110] type=1400 audit(1469393853.318:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8533 comm="apparmor_parser"
Jul 24 20:57:33 node-4 kernel: [   37.907115] type=1400 audit(1469393853.318:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8533 comm="apparmor_parser"
Jul 24 20:57:33 node-4 kernel: [   37.907118] type=1400 audit(1469393853.318:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8533 comm="apparmor_parser"
Jul 24 20:57:33 node-4 kernel: [   37.907336] type=1400 audit(1469393853.318:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8533 comm="apparmor_parser"
Jul 24 20:57:33 node-4 kernel: [   37.907338] type=1400 audit(1469393853.318:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8533 comm="apparmor_parser"
Jul 24 20:57:33 node-4 kernel: [   37.907453] type=1400 audit(1469393853.318:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8533 comm="apparmor_parser"
Jul 24 20:57:33 node-4 kernel: [   37.908367] type=1400 audit(1469393853.322:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8534 comm="apparmor_parser"
Jul 24 20:57:33 node-4 kernel: [   37.988891] type=1400 audit(1469393853.402:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8536 comm="apparmor_parser"
Jul 24 20:57:33 node-4 cron[8566]: (CRON) INFO (pidfile fd = 3)
Jul 24 20:57:33 node-4 anacron[8601]: Anacron 2.3 started on 2016-07-24
Jul 24 20:57:33 node-4 cron[8608]: (CRON) STARTUP (fork ok)
Jul 24 20:57:33 node-4 anacron[8601]: Will run job `cron.daily' in 5 min.
Jul 24 20:57:33 node-4 anacron[8601]: Will run job `cron.weekly' in 10 min.
Jul 24 20:57:33 node-4 anacron[8601]: Will run job `cron.monthly' in 15 min.
Jul 24 20:57:33 node-4 anacron[8601]: Jobs will be executed sequentially
Jul 24 20:57:33 node-4 multipathd: path checkers start up
Jul 24 20:57:33 node-4 cron[8608]: (CRON) INFO (Running @reboot jobs)
Jul 24 20:57:34 node-4 postfix/master[8745]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 24 20:57:37 node-4 puppet-agent[8930]: Reopening log files
Jul 24 20:57:38 node-4 puppet-agent[8930]: Could not request certificate: Connection refused - connect(2)
Jul 24 20:57:53 node-4 puppet-user[9138]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 24 20:57:53 node-4 puppet-user[9138]: Compiled catalog for node-4.domain.tld in environment production in 0.04 seconds
Jul 24 20:57:53 node-4 puppet-user[9138]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 24 20:57:53 node-4 puppet-user[9138]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 24 20:57:53 node-4 puppet-user[9138]: Finished catalog run in 0.43 seconds
Jul 24 20:57:55 node-4 multipathd: uevent trigger error
Jul 24 20:57:55 node-4 puppet-user[9563]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 20:57:55 node-4 puppet-user[9563]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Jul 24 20:57:55 node-4 puppet-user[9563]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 24 20:57:55 node-4 puppet-user[9563]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 24 20:57:55 node-4 puppet-user[9563]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy) hierarchy changed '["defaults", "%{clientcert}", "%{environment}", "global"]' to '["override/node/%{::fqdn}", "override/class/%{calling_class}", "override/module/%{calling_module}", "override/plugins", "override/common", "override/configuration/%{::fqdn}", "override/configuration/role", "override/configuration/cluster", "override/configuration/default_route", "class/%{calling_class}", "module/%{calling_module}", "deleted_nodes", "nodes", "globals%{disable_globals_yaml}", "astute"]'
Jul 24 20:57:55 node-4 puppet-user[9563]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 24 20:57:55 node-4 puppet-user[9563]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 24 20:57:55 node-4 puppet-user[9563]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 24 20:57:55 node-4 puppet-user[9563]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 24 20:57:55 node-4 puppet-user[9563]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 24 20:57:55 node-4 puppet-user[9563]: Finished catalog run in 0.06 seconds
Jul 24 20:57:56 node-4 puppet-user[10028]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 24 20:57:57 node-4 puppet-user[10028]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Jul 24 20:57:57 node-4 puppet-user[10028]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 24 20:57:57 node-4 puppet-user[10028]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 24 20:57:57 node-4 puppet-user[10028]: Finished catalog run in 0.04 seconds
Jul 24 20:57:58 node-4 puppet-user[10505]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 24 20:57:58 node-4 puppet-user[10505]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 24 20:57:58 node-4 puppet-user[10505]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 24 20:57:59 node-4 puppet-user[10505]: Finished catalog run in 0.03 seconds
Jul 24 20:58:00 node-4 puppet-user[11144]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 24 20:58:00 node-4 puppet-user[11144]: Compiled catalog for node-4.domain.tld in environment production in 0.19 seconds
Jul 24 20:58:01 node-4 puppet-user[11144]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 24 20:58:01 node-4 kernel: [   65.587837] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 24 20:58:01 node-4 kernel: [   65.587887] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case.  If you have one, please send an email to linux-mm@kvack.org.
Jul 24 20:58:01 node-4 puppet-user[11144]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl_runtime[net.ipv4.ip_local_reserved_ports]/val) val changed '' to '35357,41055-41056,49000-49001,55572,58882'
Jul 24 20:58:01 node-4 puppet-user[11144]: Finished catalog run in 0.05 seconds
Jul 24 20:58:01 node-4 CRON[11596]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 24 20:58:02 node-4 puppet-user[11612]: (Scope(Class[main])) MODULAR: sync_time
Jul 24 20:58:02 node-4 puppet-user[11612]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 24 20:58:02 node-4 ntpdate[12039]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 24 20:58:08 node-4 ntpdate[12039]: adjust time server 10.20.0.2 offset 0.361537 sec
Jul 24 20:58:08 node-4 puppet-user[11612]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 24 20:58:09 node-4 puppet-user[11612]: Finished catalog run in 6.19 seconds
Jul 24 20:58:10 node-4 kernel: [   75.176539] init: plymouth-upstart-bridge main process ended, respawning
Jul 24 20:58:10 node-4 puppet-agent[8930]: Could not run: SIGTERM
Jul 24 20:58:10 node-4 kernel: [   75.436689] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 24 20:58:10 node-4 ec2: 
Jul 24 20:58:10 node-4 ec2: #############################################################
Jul 24 20:58:10 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 24 20:58:10 node-4 ec2: 1024 96:0d:86:bc:80:fa:a4:1b:bb:42:80:bc:7a:e9:6b:71  root@node-4.domain.tld (DSA)
Jul 24 20:58:10 node-4 ec2: 256 c9:74:3e:54:9e:cc:6c:06:98:7f:73:48:30:8e:ee:56  root@node-4.domain.tld (ECDSA)
Jul 24 20:58:10 node-4 ec2: 256 51:4a:94:c8:1e:4c:44:13:c8:f6:b9:0a:e8:81:ce:5c  root@node-4.domain.tld (ED25519)
Jul 24 20:58:10 node-4 ec2: 2048 c4:34:42:ff:09:13:ca:a9:1c:bf:fa:5b:1c:ae:5b:f9  root@node-4.domain.tld (RSA)
Jul 24 20:58:10 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 24 20:58:10 node-4 ec2: #############################################################
Jul 24 20:58:13 node-4 puppet-user[12407]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 24 20:58:13 node-4 puppet-user[12407]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Jul 24 20:58:13 node-4 puppet-user[12407]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 24 20:58:13 node-4 puppet-user[12407]: Finished catalog run in 0.07 seconds
Jul 24 20:58:14 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 20:58:14 node-4 nailgun-agent: D, [2016-07-24T20:58:01.800126 #11601] DEBUG -- : Sleep for 13 seconds before sending request
Jul 24 20:58:14 node-4 nailgun-agent: I, [2016-07-24T20:58:14.815727 #11601]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 20:58:15 node-4 puppet-user[12866]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 24 20:58:15 node-4 nailgun-agent: D, [2016-07-24T20:58:15.237733 #11601] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 24 20:58:16 node-4 puppet-user[12866]: Compiled catalog for node-4.domain.tld in environment production in 0.95 seconds
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[allow-unathenticated]/Apt::Setting[conf-allow-unathenticated]/File[/etc/apt/apt.conf.d/02allow-unathenticated]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-recommends]/Apt::Setting[conf-install-recommends]/File[/etc/apt/apt.conf.d/02install-recommends]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Conf[install-suggests]/Apt::Setting[conf-install-suggests]/File[/etc/apt/apt.conf.d/02install-suggests]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-security]/Apt::Setting[list-mos-security]/File[/etc/apt/sources.list.d/mos-security.list]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-security]/Apt::Setting[list-ubuntu-security]/File[/etc/apt/sources.list.d/ubuntu-security.list]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-updates]/Apt::Setting[list-mos-updates]/File[/etc/apt/sources.list.d/mos-updates.list]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-updates]/Apt::Setting[pref-mos-updates]/File[/etc/apt/preferences.d/mos-updates.pref]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos-holdback]/Apt::Setting[list-mos-holdback]/File[/etc/apt/sources.list.d/mos-holdback.list]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-security]/Apt::Setting[pref-mos-security]/File[/etc/apt/preferences.d/mos-security.pref]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu-updates]/Apt::Setting[list-ubuntu-updates]/File[/etc/apt/sources.list.d/ubuntu-updates.list]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos-holdback]/Apt::Setting[pref-mos-holdback]/File[/etc/apt/preferences.d/mos-holdback.pref]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 24 20:58:16 node-4 puppet-user[12866]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.275596 #11601] DEBUG -- : Trying to find block devices
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.275715 #11601] DEBUG -- : Found block device: sda
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.275776 #11601] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.275802 #11601] DEBUG -- : Trying to get list of physical devices
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.275972 #11601] DEBUG -- : Getting udev properties for device: sda
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.277873 #11601] 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"=>"0x618e72837273a7701cc788
Jul 24 20:58:27 node-4 nailgun-agent: 6005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"37136", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.277952 #11601] DEBUG -- : Trying to find out if device sda is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.277997 #11601] DEBUG -- : Device sda removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.278012 #11601] DEBUG -- : Device sda seems to be appropriate
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.278468 #11601] DEBUG -- : Getting udev properties for device: dm-0
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.280130 #11601] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-ERs5KGbxbV1adTs4SCOg5tOkZWeIa2McqZoGNkDajU7inxWGgNIQqmr6JqsADTnx /dev/disk/by-uuid/b65d7c01-495f-452b-92cd-f8bba76ab00e /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-ERs5KGbxbV1adTs4SCOg5tOkZWeIa2McqZoGNkDajU7inxWGgNIQqmr6JqsADTnx", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b65d7c01-495f-452b-92cd-f8bba76ab00e", "ID_FS_UUID_ENC"=>"b65d7c01-495f-452b-92cd-f8bba76ab00e", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"95506", "nomdmonddf"=>"1", "nom
Jul 24 20:58:27 node-4 nailgun-agent: dmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.280166 #11601] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.280196 #11601] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.280209 #11601] DEBUG -- : Device dm-0 seems to be appropriate
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.280225 #11601] DEBUG -- : Getting udev properties for device: dm-1
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.282057 #11601] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-lTPEEv4ge54CKxlZTYhNVYDDjS0I1YPuOgBu7WbCy3EhffALPy28r1lklLkdpvE2 /dev/disk/by-uuid/208fc041-8700-4e0e-b4bc-efbea208d90a /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-lTPEEv4ge54CKxlZTYhNVYDDjS0I1YPuOgBu7WbCy3EhffALPy28r1lklLkdpvE2", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"208fc041-8700-4e0e-b4bc-efbea208d90a", "ID_FS_UUID_ENC"=>"208fc041-8700-4e0e-b4bc-efbea208d90a", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2
Jul 24 20:58:27 node-4 nailgun-agent: 7374", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.282082 #11601] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.282137 #11601] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.282172 #11601] DEBUG -- : Device dm-1 seems to be appropriate
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.282187 #11601] DEBUG -- : Getting udev properties for device: dm-2
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.284159 #11601] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-GI3yFgOwx2tiIhhhlJa00T0uwH6r9ZheasYGeU981fSnV4s4OLLZJTHZQTRrh6jf /dev/disk/by-uuid/a5b7d389-e6b9-46c8-9919-8d8322a28a56 /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-GI3yFgOwx2tiIhhhlJa00T0uwH6r9ZheasYGeU981fSnV4s4OLLZJTHZQTRrh6jf", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a5b7d389-e6b9-46c8-9919-8d8322a28a56", "ID_FS_UUID_ENC"=>"a5b7d389-e6b9-46c8-9919-8d8322a28a56", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31854", "nomdmon
Jul 24 20:58:27 node-4 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.284220 #11601] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.284250 #11601] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.284264 #11601] DEBUG -- : Device dm-2 seems to be appropriate
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.284279 #11601] DEBUG -- : Getting udev properties for device: dm-3
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.286081 #11601] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-jIlZ1mbtlavYM5CcYv7jvBzd3E3kV6hsw9KWc6Sj5LKJcTue4lQ3oSGnFtWLfpas /dev/disk/by-uuid/ad51f896-24db-4bcf-b8e9-b465d54261f1 /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-jIlZ1mbtlavYM5CcYv7jvBzd3E3kV6hsw9KWc6Sj5LKJcTue4lQ3oSGnFtWLfpas", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"ad51f896-24db-4bcf-b8e9-b465d54261f1", "ID_FS_UUID_ENC"=>"ad51f896-24db-4bcf-b8e9-b465d54261f1", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"29995", "nomdmonddf"=>"1",
Jul 24 20:58:27 node-4 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.286118 #11601] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.286148 #11601] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.286162 #11601] DEBUG -- : Device dm-3 seems to be appropriate
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.286190 #11601] DEBUG -- : Getting udev properties for device: dm-4
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.288084 #11601] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-IzISaASfNXXr83XSFgP6STQiMt3geVPKNivR1gWbVcH4fn3kUMbjfjDgD6cJq4Sn /dev/disk/by-uuid/0bb60b1d-e65f-4582-acfb-f09607b839f4 /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-IzISaASfNXXr83XSFgP6STQiMt3geVPKNivR1gWbVcH4fn3kUMbjfjDgD6cJq4Sn", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"0bb60b1d-e65f-4582-acfb-f09607b839f4", "ID_FS_UUID_ENC"=>"0bb60b1d-e65f-4582-acfb-f09607b839f4", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"32428", "nomdmonddf"=>"1", "nom
Jul 24 20:58:27 node-4 nailgun-agent: dmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.288122 #11601] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.288151 #11601] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.288180 #11601] DEBUG -- : Device dm-4 seems to be appropriate
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.288195 #11601] DEBUG -- : Getting udev properties for device: dm-5
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.290265 #11601] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-IzISaASfNXXr83XSFgP6STQiMt3geVPKBywDAVoD6iaHk3dLdBvVmXavw17YgC8j /dev/disk/by-uuid/0ee40725-6d61-4925-b512-f9fccd462aa1 /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-IzISaASfNXXr83XSFgP6STQiMt3geVPKBywDAVoD6iaHk3dLdBvVmXavw17YgC8j", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"0ee40725-6d61-4925-b512-f9fccd462aa1", "ID_FS_UUID_ENC"=>"0ee40725-6d61-4925-b512-f9fccd462aa1", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"32899", "nomdmonddf"=>"1", "nomdmonisw
Jul 24 20:58:27 node-4 nailgun-agent: "=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.290314 #11601] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.290347 #11601] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.290375 #11601] DEBUG -- : Device dm-5 seems to be appropriate
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.290391 #11601] DEBUG -- : Getting udev properties for device: ram0
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.292041 #11601] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84303", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.292065 #11601] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.292100 #11601] DEBUG -- : Device ram0 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.292120 #11601] DEBUG -- : Getting udev properties for device: ram1
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.293674 #11601] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84405", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.293697 #11601] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.293744 #11601] DEBUG -- : Device ram1 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.293764 #11601] DEBUG -- : Getting udev properties for device: ram2
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.295286 #11601] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85015", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.295307 #11601] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.295380 #11601] DEBUG -- : Device ram2 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.295398 #11601] DEBUG -- : Getting udev properties for device: ram3
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.296881 #11601] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85090", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.296901 #11601] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.296931 #11601] DEBUG -- : Device ram3 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.296949 #11601] DEBUG -- : Getting udev properties for device: ram4
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.298469 #11601] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85191", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.298503 #11601] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.298534 #11601] DEBUG -- : Device ram4 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.298551 #11601] DEBUG -- : Getting udev properties for device: ram5
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.300067 #11601] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85287", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.300114 #11601] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.300151 #11601] DEBUG -- : Device ram5 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.300168 #11601] DEBUG -- : Getting udev properties for device: ram6
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.301743 #11601] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85392", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.301764 #11601] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.301795 #11601] DEBUG -- : Device ram6 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.301812 #11601] DEBUG -- : Getting udev properties for device: ram7
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.303427 #11601] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85479", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.303459 #11601] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.303489 #11601] DEBUG -- : Device ram7 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.303515 #11601] DEBUG -- : Getting udev properties for device: ram8
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.305077 #11601] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85588", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.305098 #11601] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.305139 #11601] DEBUG -- : Device ram8 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.305158 #11601] DEBUG -- : Getting udev properties for device: ram9
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.306763 #11601] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"85686", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.306784 #11601] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.306835 #11601] DEBUG -- : Device ram9 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.306854 #11601] DEBUG -- : Getting udev properties for device: loop0
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.308389 #11601] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83136", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.308424 #11601] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.308474 #11601] DEBUG -- : Device loop0 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.308491 #11601] DEBUG -- : Getting udev properties for device: loop1
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.310017 #11601] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83224", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.310038 #11601] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.310080 #11601] DEBUG -- : Device loop1 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.310098 #11601] DEBUG -- : Getting udev properties for device: loop2
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.311642 #11601] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83309", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.311672 #11601] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.311721 #11601] DEBUG -- : Device loop2 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.311738 #11601] DEBUG -- : Getting udev properties for device: loop3
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.313311 #11601] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83395", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.313343 #11601] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.313371 #11601] DEBUG -- : Device loop3 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.313398 #11601] DEBUG -- : Getting udev properties for device: loop4
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.314913 #11601] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83536", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.314948 #11601] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.314989 #11601] DEBUG -- : Device loop4 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.315006 #11601] DEBUG -- : Getting udev properties for device: loop5
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.316510 #11601] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83711", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.316531 #11601] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.316559 #11601] DEBUG -- : Device loop5 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.316596 #11601] DEBUG -- : Getting udev properties for device: loop6
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.318046 #11601] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83812", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.318068 #11601] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.318110 #11601] DEBUG -- : Device loop6 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.318128 #11601] DEBUG -- : Getting udev properties for device: loop7
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.325238 #11601] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"83989", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.325266 #11601] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.325308 #11601] DEBUG -- : Device loop7 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.325326 #11601] DEBUG -- : Getting udev properties for device: ram10
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.327105 #11601] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84487", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.327125 #11601] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.327161 #11601] DEBUG -- : Device ram10 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.327179 #11601] DEBUG -- : Getting udev properties for device: ram11
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.328687 #11601] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84573", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.328740 #11601] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.328777 #11601] DEBUG -- : Device ram11 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.328794 #11601] DEBUG -- : Getting udev properties for device: ram12
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.331004 #11601] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84683", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.331053 #11601] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.331165 #11601] DEBUG -- : Device ram12 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.331196 #11601] DEBUG -- : Getting udev properties for device: ram13
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.333215 #11601] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84750", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.333250 #11601] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.333296 #11601] DEBUG -- : Device ram13 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.333366 #11601] DEBUG -- : Getting udev properties for device: ram14
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.335400 #11601] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84854", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.335432 #11601] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.335472 #11601] DEBUG -- : Device ram14 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.335498 #11601] DEBUG -- : Getting udev properties for device: ram15
Jul 24 20:58:27 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337290 #11601] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"84937", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337321 #11601] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337372 #11601] DEBUG -- : Device ram15 removable parameter: "0"
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337431 #11601] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337515 #11601] DEBUG -- : Block device seems to be physical data storage: sda
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337560 #11601] DEBUG -- : Found block device: dm-0
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337578 #11601] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337594 #11601] DEBUG -- : Found block device: dm-1
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337605 #11601] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337616 #11601] DEBUG -- : Found block device: dm-2
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337627 #11601] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337637 #11601] DEBUG -- : Found block device: dm-3
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337649 #11601] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337719 #11601] DEBUG -- : Found block device: dm-4
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337731 #11601] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337741 #11601] DEBUG -- : Found block device: dm-5
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337752 #11601] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337761 #11601] DEBUG -- : Found block device: ram0
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337772 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337782 #11601] DEBUG -- : Found block device: ram1
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337793 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337865 #11601] DEBUG -- : Found block device: ram2
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337878 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337887 #11601] DEBUG -- : Found block device: ram3
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337901 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337911 #11601] DEBUG -- : Found block device: ram4
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337923 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337932 #11601] DEBUG -- : Found block device: ram5
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337944 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.337954 #11601] DEBUG -- : Found block device: ram6
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338019 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338029 #11601] DEBUG -- : Found block device: ram7
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338041 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338051 #11601] DEBUG -- : Found block device: ram8
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338063 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338072 #11601] DEBUG -- : Found block device: ram9
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338084 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338093 #11601] DEBUG -- : Found block device: loop0
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338168 #11601] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338179 #11601] DEBUG -- : Found block device: loop1
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338192 #11601] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338202 #11601] DEBUG -- : Found block device: loop2
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338213 #11601] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338223 #11601] DEBUG -- : Found block device: loop3
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338235 #11601] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338246 #11601] DEBUG -- : Found block device: loop4
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338311 #11601] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338322 #11601] DEBUG -- : Found block device: loop5
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338333 #11601] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338343 #11601] DEBUG -- : Found block device: loop6
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338354 #11601] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338364 #11601] DEBUG -- : Found block device: loop7
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338375 #11601] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338384 #11601] DEBUG -- : Found block device: ram10
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338395 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338405 #11601] DEBUG -- : Found block device: ram11
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338455 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338466 #11601] DEBUG -- : Found block device: ram12
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338477 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338486 #11601] DEBUG -- : Found block device: ram13
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338498 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338507 #11601] DEBUG -- : Found block device: ram14
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338517 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338527 #11601] DEBUG -- : Found block device: ram15
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338538 #11601] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.338607 #11601] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Jul 24 20:58:27 node-4 nailgun-agent: D, [2016-07-24T20:58:27.531194 #11601] DEBUG -- : Response: status: 200 body: {"id": 4}
Jul 24 20:58:27 node-4 nailgun-agent: I, [2016-07-24T20:58:27.531374 #11601]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 24 20:58:37 node-4 puppet-user[12866]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 24 20:58:37 node-4 puppet-user[12866]: Finished catalog run in 21.60 seconds
Jul 24 20:58:40 node-4 puppet-user[14323]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 24 20:58:40 node-4 puppet-user[14323]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Jul 24 20:58:45 node-4 puppet-user[14323]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 24 20:59:01 node-4 CRON[15929]: (root) CMD (flock -w 0 -o /var/lock/nailgun-agent.lock -c "/usr/bin/nailgun-agent 2>&1 | tee -a /var/log/nailgun-agent.log  | /usr/bin/logger -t nailgun-agent")
Jul 24 20:59:07 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 20:59:07 node-4 nailgun-agent: I, [2016-07-24T20:59:07.722170 #15932]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 24 20:59:15 node-4 puppet-user[14323]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 24 20:59:15 node-4 puppet-user[14323]: Finished catalog run in 35.15 seconds
Jul 24 20:59:17 node-4 puppet-user[16924]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 24 20:59:17 node-4 puppet-user[16924]: Compiled catalog for node-4.domain.tld in environment production in 0.58 seconds
Jul 24 20:59:17 node-4 puppet-user[16924]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 24 20:59:17 node-4 puppet-user[16924]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 24 20:59:17 node-4 puppet-user[16924]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 24 20:59:17 node-4 puppet-user[16924]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 24 20:59:17 node-4 puppet-user[16924]: Finished catalog run in 0.12 seconds
Jul 24 20:59:19 node-4 puppet-user[17390]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 24 20:59:20 node-4 puppet-user[17390]: Compiled catalog for node-4.domain.tld in environment production in 0.95 seconds
Jul 24 20:59:20 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 24 20:59:20 node-4 nailgun-agent: I, [2016-07-24T20:59:20.791042 #15932]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 24 20:59:20 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 24 20:59:20 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 24 20:59:20 node-4 crontab[18008]: (root) LIST (root)
Jul 24 20:59:20 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 24 20:59:20 node-4 crontab[18009]: (root) REPLACE (root)
Jul 24 20:59:23 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 24 20:59:24 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_log]/Rsyslog::Snippet[04-rabbitmq-startup_log]/File[/etc/rsyslog.d/04-rabbitmq-startup_log.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_access]/Rsyslog::Snippet[12-keystone_wsgi_admin_access]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_access.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[61-mco_agent_debug]/Rsyslog::Snippet[61-mco_agent_debug]/File[/etc/rsyslog.d/61-mco_agent_debug.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_access]/Rsyslog::Snippet[13-keystone_wsgi_main_access]/File[/etc/rsyslog.d/13-keystone_wsgi_main_access.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[12-keystone_wsgi_admin_error]/Rsyslog::Snippet[12-keystone_wsgi_admin_error]/File[/etc/rsyslog.d/12-keystone_wsgi_admin_error.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[13-keystone_wsgi_main_error]/Rsyslog::Snippet[13-keystone_wsgi_main_error]/File[/etc/rsyslog.d/13-keystone_wsgi_main_error.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_err]/Rsyslog::Snippet[04-rabbitmq-shutdown_err]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_err.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-startup_err]/Rsyslog::Snippet[04-rabbitmq-startup_err]/File[/etc/rsyslog.d/04-rabbitmq-startup_err.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-shutdown_log]/Rsyslog::Snippet[04-rabbitmq-shutdown_log]/File[/etc/rsyslog.d/04-rabbitmq-shutdown_log.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 24 20:59:25 node-4 puppet-user[17390]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Jul 24 20:59:25 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8381" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 24 20:59:25 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 24 20:59:27 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:27 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:27 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:27 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:46 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:49 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:49 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:49 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:49 node-4 multipathd: uevent trigger error
<27>Jul 24 20:59:49 node-4 multipathd: uevent trigger error
<27>Jul 24 21:00:50 node-4 ntpdate[29408]: no servers can be used, exiting
<27>Jul 24 21:00:50 node-4 ntpdate[29762]: no servers can be used, exiting
<27>Jul 24 21:01:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:36 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:36 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:36 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:36 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:36 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:36 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:39 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:39 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:39 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:39 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:39 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:46 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:46 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:46 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:46 node-4 multipathd: uevent trigger error
<27>Jul 24 21:01:46 node-4 multipathd: uevent trigger error
<43>Jul 24 21:02:06 node-4 apache2_error [Sun Jul 24 21:01:58.490160 2016] [mpm_event:notice] [pid 6999:tid 139695048234880] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 21:02:06 node-4 apache2_error [Sun Jul 24 21:01:58.490299 2016] [core:notice] [pid 6999:tid 139695048234880] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 21:02:06 node-4 apache2_error [Sun Jul 24 21:02:01.526277 2016] [mpm_event:notice] [pid 6999:tid 139695048234880] AH00491: caught SIGTERM, shutting down
<43>Jul 24 21:02:06 node-4 apache2_error [Sun Jul 24 21:02:02.624938 2016] [mpm_worker:notice] [pid 7375:tid 139666366404480] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 21:02:06 node-4 apache2_error [Sun Jul 24 21:02:02.624990 2016] [core:notice] [pid 7375:tid 139666366404480] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 21:02:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:02:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:02:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:02:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:02:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:02:42 node-4 multipathd: uevent trigger error
<27>Jul 24 21:02:42 node-4 multipathd: uevent trigger error
<27>Jul 24 21:02:42 node-4 multipathd: uevent trigger error
<27>Jul 24 21:02:42 node-4 multipathd: uevent trigger error
<27>Jul 24 21:02:42 node-4 multipathd: uevent trigger error
<27>Jul 24 21:02:42 node-4 multipathd: uevent trigger error
<43>Jul 24 21:02:46 node-4 apache2_error [Sun Jul 24 21:02:39.864137 2016] [mpm_worker:notice] [pid 7375:tid 139666366404480] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 21:02:46 node-4 apache2_error [Sun Jul 24 21:02:39.871131 2016] [mpm_worker:warn] [pid 7375:tid 139666366404480] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 21:02:46 node-4 apache2_error [Sun Jul 24 21:02:39.871865 2016] [mpm_worker:notice] [pid 7375:tid 139666366404480] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 24 21:02:46 node-4 apache2_error [Sun Jul 24 21:02:39.871882 2016] [core:notice] [pid 7375:tid 139666366404480] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 21:03:18 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 24 21:03:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:32 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:32 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:32 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:33 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:33 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:40 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:40 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:40 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:40 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:40 node-4 multipathd: uevent trigger error
<129>Jul 24 21:03:43 node-4 haproxy[20772]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:03:45 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:45 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:45 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:45 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:49 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:49 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:49 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:49 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:49 node-4 multipathd: uevent trigger error
<129>Jul 24 21:03:52 node-4 haproxy[22936]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:03:53 node-4 haproxy[22936]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:03:54 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:54 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:54 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:54 node-4 multipathd: uevent trigger error
<129>Jul 24 21:03:57 node-4 haproxy[24075]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:03:57 node-4 haproxy[24075]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:03:58 node-4 haproxy[24075]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:03:59 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:59 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:59 node-4 multipathd: uevent trigger error
<27>Jul 24 21:03:59 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:02 node-4 haproxy[25255]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:02 node-4 haproxy[25255]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:03 node-4 haproxy[25259]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:03 node-4 haproxy[25259]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:04 node-4 haproxy[25259]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:05 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:05 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:05 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:05 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:05 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:07 node-4 haproxy[26383]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:08 node-4 haproxy[26387]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:08 node-4 haproxy[26387]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:08 node-4 haproxy[26387]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:09 node-4 haproxy[26387]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:09 node-4 haproxy[26387]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:10 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:10 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:10 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:10 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:10 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:10 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:11 node-4 haproxy[26387]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:11 node-4 haproxy[26387]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:11 node-4 haproxy[26387]: proxy aodh has no server available!
<129>Jul 24 21:04:13 node-4 haproxy[27663]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:13 node-4 haproxy[27663]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:13 node-4 haproxy[27663]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:13 node-4 haproxy[27663]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:14 node-4 haproxy[27667]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:14 node-4 haproxy[27667]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:14 node-4 haproxy[27667]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:16 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:16 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:16 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:16 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:16 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:16 node-4 haproxy[27667]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:16 node-4 haproxy[27667]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:16 node-4 haproxy[27667]: proxy aodh has no server available!
<129>Jul 24 21:04:16 node-4 haproxy[27667]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:16 node-4 haproxy[27667]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:16 node-4 haproxy[27667]: proxy ceilometer has no server available!
<129>Jul 24 21:04:18 node-4 haproxy[28781]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:18 node-4 haproxy[28781]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:18 node-4 haproxy[28781]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:19 node-4 haproxy[28788]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:19 node-4 haproxy[28788]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:19 node-4 haproxy[28788]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:20 node-4 haproxy[28788]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:21 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:21 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:21 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:21 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:21 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:21 node-4 haproxy[28788]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:21 node-4 haproxy[28788]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:21 node-4 haproxy[28788]: proxy aodh has no server available!
<129>Jul 24 21:04:21 node-4 haproxy[28788]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:22 node-4 haproxy[28788]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:22 node-4 haproxy[28788]: proxy ceilometer has no server available!
<129>Jul 24 21:04:23 node-4 haproxy[29909]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:23 node-4 haproxy[29909]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:24 node-4 haproxy[29913]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:24 node-4 haproxy[29913]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:24 node-4 haproxy[29913]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:24 node-4 haproxy[29913]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:25 node-4 haproxy[29913]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:25 node-4 haproxy[29913]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:25 node-4 haproxy[29913]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:26 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:26 node-4 haproxy[29913]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:27 node-4 haproxy[29913]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:27 node-4 haproxy[29913]: proxy aodh has no server available!
<129>Jul 24 21:04:27 node-4 haproxy[29913]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:27 node-4 haproxy[29913]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:27 node-4 haproxy[29913]: proxy ceilometer has no server available!
<129>Jul 24 21:04:29 node-4 haproxy[31267]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-4 haproxy[31267]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-4 haproxy[31267]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-4 haproxy[31267]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:29 node-4 haproxy[31267]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:30 node-4 haproxy[31267]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:30 node-4 haproxy[31267]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:30 node-4 haproxy[31267]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:30 node-4 haproxy[31267]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:30 node-4 haproxy[31267]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:30 node-4 haproxy[31267]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:31 node-4 haproxy[31267]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:31 node-4 haproxy[31267]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:32 node-4 haproxy[31267]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:32 node-4 haproxy[31267]: proxy glance-registry has no server available!
<129>Jul 24 21:04:32 node-4 haproxy[31267]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:32 node-4 haproxy[31267]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:32 node-4 haproxy[31267]: proxy aodh has no server available!
<129>Jul 24 21:04:32 node-4 haproxy[31267]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:32 node-4 haproxy[31267]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:32 node-4 haproxy[31267]: proxy ceilometer has no server available!
<27>Jul 24 21:04:32 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:32 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:32 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:32 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:32 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:36 node-4 haproxy[32424]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-4 haproxy[32424]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-4 haproxy[32424]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-4 haproxy[32424]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-4 haproxy[32424]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-4 haproxy[32424]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:36 node-4 haproxy[32424]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:36 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 24 21:04:37 node-4 haproxy[32424]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:37 node-4 haproxy[32424]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:37 node-4 haproxy[32424]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:37 node-4 haproxy[32424]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:37 node-4 haproxy[32424]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:37 node-4 haproxy[32424]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:37 node-4 haproxy[32424]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:37 node-4 haproxy[32424]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:38 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:38 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:38 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:38 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:38 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:38 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:38 node-4 haproxy[32424]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:39 node-4 haproxy[32424]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:39 node-4 haproxy[32424]: proxy glance-registry has no server available!
<129>Jul 24 21:04:39 node-4 haproxy[32424]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:39 node-4 haproxy[32424]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:39 node-4 haproxy[32424]: proxy aodh has no server available!
<129>Jul 24 21:04:39 node-4 haproxy[32424]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:39 node-4 haproxy[32424]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:39 node-4 haproxy[32424]: proxy ceilometer has no server available!
<129>Jul 24 21:04:39 node-4 haproxy[32424]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:39 node-4 haproxy[32424]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:39 node-4 haproxy[32424]: proxy nova-novncproxy has no server available!
<129>Jul 24 21:04:41 node-4 haproxy[1173]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-4 haproxy[1173]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-4 haproxy[1173]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-4 haproxy[1173]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-4 haproxy[1173]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:41 node-4 haproxy[1173]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-4 haproxy[1177]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-4 haproxy[1177]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-4 haproxy[1177]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-4 haproxy[1177]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-4 haproxy[1177]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-4 haproxy[1177]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-4 haproxy[1177]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:42 node-4 haproxy[1177]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:43 node-4 haproxy[1177]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:43 node-4 haproxy[1177]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:43 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:43 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:44 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:44 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:44 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:44 node-4 haproxy[1177]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:44 node-4 haproxy[1177]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:44 node-4 haproxy[1177]: proxy glance-registry has no server available!
<129>Jul 24 21:04:44 node-4 haproxy[1177]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:44 node-4 haproxy[1177]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:44 node-4 haproxy[1177]: proxy aodh has no server available!
<129>Jul 24 21:04:44 node-4 haproxy[1177]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:44 node-4 haproxy[1177]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:44 node-4 haproxy[1177]: proxy ceilometer has no server available!
<129>Jul 24 21:04:44 node-4 haproxy[1177]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:45 node-4 haproxy[1177]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:45 node-4 haproxy[1177]: proxy nova-novncproxy has no server available!
<129>Jul 24 21:04:47 node-4 haproxy[2361]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:47 node-4 haproxy[2361]: Server keystone-2/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:47 node-4 haproxy[2361]: Server nova-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:47 node-4 haproxy[2361]: Server nova-metadata-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:47 node-4 haproxy[2361]: Backup Server cinder-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:47 node-4 haproxy[2361]: Server glance-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:47 node-4 haproxy[2361]: Server glance-glare/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:47 node-4 haproxy[2361]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:47 node-4 haproxy[2361]: Server glance-registry/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:48 node-4 haproxy[2361]: Backup Server mysqld/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 1 active and 1 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:48 node-4 haproxy[2361]: Server object-storage/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:48 node-4 haproxy[2361]: Server aodh/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:48 node-4 haproxy[2361]: Server ceilometer/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:48 node-4 haproxy[2361]: Server heat-api/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:48 node-4 haproxy[2361]: Server heat-api-cfn/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:48 node-4 haproxy[2361]: Server heat-api-cloudwatch/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:48 node-4 haproxy[2361]: Server nova-novncproxy/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:48 node-4 haproxy[2361]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:49 node-4 haproxy[2361]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:49 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:49 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:49 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:49 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:49 node-4 haproxy[2361]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 24 21:04:49 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:49 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:50 node-4 haproxy[2361]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:50 node-4 haproxy[2361]: proxy glance-registry has no server available!
<129>Jul 24 21:04:50 node-4 haproxy[2361]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:50 node-4 haproxy[2361]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:50 node-4 haproxy[2361]: proxy aodh has no server available!
<129>Jul 24 21:04:50 node-4 haproxy[2361]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:50 node-4 haproxy[2361]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:50 node-4 haproxy[2361]: proxy ceilometer has no server available!
<129>Jul 24 21:04:50 node-4 haproxy[2361]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:50 node-4 haproxy[2361]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:50 node-4 haproxy[2361]: proxy nova-novncproxy has no server available!
<27>Jul 24 21:04:53 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:53 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:53 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:53 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:53 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:04:56 node-4 multipathd: uevent trigger error
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server keystone-1/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:57 node-4 haproxy[2361]: proxy keystone-1 has no server available!
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server keystone-2/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:57 node-4 haproxy[2361]: proxy keystone-2 has no server available!
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server nova-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:57 node-4 haproxy[2361]: proxy nova-api has no server available!
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:57 node-4 haproxy[2361]: proxy nova-metadata-api has no server available!
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:57 node-4 haproxy[2361]: proxy cinder-api has no server available!
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server glance-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:57 node-4 haproxy[2361]: proxy glance-api has no server available!
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server glance-glare/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:57 node-4 haproxy[2361]: proxy glance-glare has no server available!
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:57 node-4 haproxy[2361]: Server neutron/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:57 node-4 haproxy[2361]: proxy neutron has no server available!
<129>Jul 24 21:04:58 node-4 haproxy[2361]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:58 node-4 haproxy[2361]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:58 node-4 haproxy[2361]: proxy mysqld has no server available!
<129>Jul 24 21:04:58 node-4 haproxy[2361]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:58 node-4 haproxy[2361]: Server object-storage/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:58 node-4 haproxy[2361]: proxy object-storage has no server available!
<129>Jul 24 21:04:58 node-4 haproxy[2361]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:58 node-4 haproxy[2361]: Server heat-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:58 node-4 haproxy[2361]: proxy heat-api has no server available!
<129>Jul 24 21:04:58 node-4 haproxy[2361]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:58 node-4 haproxy[2361]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:58 node-4 haproxy[2361]: proxy heat-api-cfn has no server available!
<129>Jul 24 21:04:58 node-4 haproxy[2361]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 24 21:04:58 node-4 haproxy[2361]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 24 21:04:58 node-4 haproxy[2361]: proxy heat-api-cloudwatch has no server available!
<27>Jul 24 21:05:00 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:00 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:00 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:00 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:00 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:30 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 21:05:30 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 24 21:05:34 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 24 21:05:35 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 21:05:35 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 24 21:05:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:05:56 node-4 multipathd: uevent trigger error
<27>Jul 24 21:06:06 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 24 21:06:33 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): PIDFile /var/run/resource-agents/mysql-wss/mysql-wss.pid of MySQL server not found. Sleeping for 2 seconds. 0 retries left
<27>Jul 24 21:06:35 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 24 21:07:50 node-4 multipathd: uevent trigger error
<27>Jul 24 21:07:50 node-4 multipathd: uevent trigger error
<27>Jul 24 21:07:50 node-4 multipathd: uevent trigger error
<27>Jul 24 21:07:50 node-4 multipathd: uevent trigger error
<27>Jul 24 21:07:50 node-4 multipathd: uevent trigger error
<11>Jul 24 21:08:41 node-4 epmd: epmd: node name already occupied rabbitmq-cli-33
<27>Jul 24 21:09:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:09:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:09:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:09:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:09:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-4 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-4 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-4 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-4 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-4 multipathd: uevent trigger error
<27>Jul 24 21:12:23 node-4 multipathd: uevent trigger error
<43>Jul 24 21:13:37 node-4 apache2_error [Sun Jul 24 21:13:33.337492 2016] [mpm_worker:notice] [pid 7375:tid 139666366404480] AH00295: caught SIGTERM, shutting down
<43>Jul 24 21:13:37 node-4 apache2_error [Sun Jul 24 21:13:34.084153 2016] [mpm_worker:notice] [pid 20462:tid 140418405443456] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 21:13:37 node-4 apache2_error [Sun Jul 24 21:13:34.084176 2016] [core:notice] [pid 20462:tid 140418405443456] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 24 21:14:07 node-4 apache2_error [Sun Jul 24 21:14:06.248832 2016] [mpm_worker:notice] [pid 20462:tid 140418405443456] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 21:14:07 node-4 apache2_error [Sun Jul 24 21:14:06.264082 2016] [mpm_worker:warn] [pid 20462:tid 140418405443456] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 21:14:07 node-4 apache2_error [Sun Jul 24 21:14:06.269878 2016] [mpm_worker:notice] [pid 20462:tid 140418405443456] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 21:14:07 node-4 apache2_error [Sun Jul 24 21:14:06.269907 2016] [core:notice] [pid 20462:tid 140418405443456] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 21:14:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:14:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:14:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:14:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:14:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:14:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:14:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:15:08 node-4 multipathd: uevent trigger error
<27>Jul 24 21:15:08 node-4 multipathd: uevent trigger error
<27>Jul 24 21:15:08 node-4 multipathd: uevent trigger error
<27>Jul 24 21:15:08 node-4 multipathd: uevent trigger error
<27>Jul 24 21:15:08 node-4 multipathd: uevent trigger error
<27>Jul 24 21:16:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:16:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:16:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:16:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:16:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:16:22 node-4 multipathd: uevent trigger error
<27>Jul 24 21:21:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:21:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:21:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:21:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:21:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:21:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:23:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:24:28 node-4 multipathd: uevent trigger error
<27>Jul 24 21:24:29 node-4 multipathd: uevent trigger error
<27>Jul 24 21:24:29 node-4 multipathd: uevent trigger error
<27>Jul 24 21:24:29 node-4 multipathd: uevent trigger error
<27>Jul 24 21:24:29 node-4 multipathd: uevent trigger error
<27>Jul 24 21:24:29 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:04 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:14 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:14 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:14 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:14 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:14 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:26 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Interface
<27>Jul 24 21:25:26 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "int-br-floating" in table Port
<27>Jul 24 21:25:26 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "phy-br-floating" in table Port
<27>Jul 24 21:25:27 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-tun" in table Port
<27>Jul 24 21:25:27 node-4 ovs-vsctl: ovs|00001|vsctl|ERR|no row "patch-int" in table Port
<27>Jul 24 21:25:27 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:27 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:27 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:27 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:27 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:27 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:45 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:45 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:45 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:45 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:45 node-4 multipathd: uevent trigger error
<27>Jul 24 21:25:45 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:01 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:02 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:02 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:26:15 node-4 multipathd: sda: spurious uevent, path already in pathvec
<27>Jul 24 21:27:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:27:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:27:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:27:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:27:26 node-4 multipathd: uevent trigger error
<27>Jul 24 21:27:31 node-4 multipathd: uevent trigger error
<27>Jul 24 21:27:31 node-4 multipathd: uevent trigger error
<27>Jul 24 21:27:31 node-4 multipathd: uevent trigger error
<27>Jul 24 21:27:31 node-4 multipathd: uevent trigger error
<27>Jul 24 21:27:31 node-4 multipathd: uevent trigger error
<43>Jul 24 21:28:28 node-4 apache2_error [Sun Jul 24 21:28:21.696602 2016] [mpm_worker:notice] [pid 20462:tid 140418405443456] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 21:28:28 node-4 apache2_error [Sun Jul 24 21:28:22.082683 2016] [mpm_worker:warn] [pid 20462:tid 140418405443456] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 21:28:28 node-4 apache2_error [Sun Jul 24 21:28:22.086890 2016] [mpm_worker:notice] [pid 20462:tid 140418405443456] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 21:28:28 node-4 apache2_error [Sun Jul 24 21:28:22.086920 2016] [core:notice] [pid 20462:tid 140418405443456] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 21:29:02 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:02 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:02 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:02 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:03 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:07 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:07 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:07 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:07 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:07 node-4 multipathd: uevent trigger error
<43>Jul 24 21:29:08 node-4 apache2_error [Sun Jul 24 21:28:58.760930 2016] [mpm_worker:notice] [pid 20462:tid 140418405443456] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 24 21:29:08 node-4 apache2_error [Sun Jul 24 21:28:59.517231 2016] [mpm_worker:warn] [pid 20462:tid 140418405443456] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 24 21:29:08 node-4 apache2_error [Sun Jul 24 21:28:59.527558 2016] [mpm_worker:notice] [pid 20462:tid 140418405443456] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 24 21:29:08 node-4 apache2_error [Sun Jul 24 21:28:59.527606 2016] [core:notice] [pid 20462:tid 140418405443456] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 24 21:29:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:29:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:09 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:09 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:09 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:09 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:19 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:19 node-4 multipathd: uevent trigger error
<11>Jul 24 21:30:28 node-4 liberasurecode[83993]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:28 node-4 liberasurecode[83993]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:28 node-4 liberasurecode[83993]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:28 node-4 liberasurecode[83993]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:28 node-4 liberasurecode[84023]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:28 node-4 liberasurecode[84023]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:28 node-4 liberasurecode[84023]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:28 node-4 liberasurecode[84023]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:31 node-4 liberasurecode[84447]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:31 node-4 liberasurecode[84447]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:31 node-4 liberasurecode[84447]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:31 node-4 liberasurecode[84447]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86808]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86808]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86808]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86808]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86849]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86849]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86849]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86849]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86915]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86915]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86915]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[86915]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[87149]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[87149]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[87149]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:36 node-4 liberasurecode[87149]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87162]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87162]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87162]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87162]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87178]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87178]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87178]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87178]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87190]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87190]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87190]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:30:37 node-4 liberasurecode[87190]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 24 21:30:43 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:43 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:43 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:43 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:43 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:43 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:48 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:48 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:48 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:48 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:48 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:52 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:52 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:52 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:53 node-4 multipathd: uevent trigger error
<27>Jul 24 21:30:53 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:11 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:17 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:17 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:17 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:17 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:17 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:29 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:29 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:29 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:29 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:29 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:34 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-4 multipathd: uevent trigger error
<27>Jul 24 21:32:48 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:01 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:01 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:01 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:01 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:01 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:06 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:10 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:10 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:10 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:10 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:10 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:15 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:25 node-4 multipathd: uevent trigger error
<27>Jul 24 21:33:25 node-4 multipathd: uevent trigger error
<11>Jul 24 21:35:01 node-4 liberasurecode[135593]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:35:01 node-4 liberasurecode[135593]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:35:01 node-4 liberasurecode[135593]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 24 21:35:01 node-4 liberasurecode[135593]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
