Jul 22 14:38:34 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8413" x-info="http://www.rsyslog.com"] start
Jul 22 14:38:34 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 22 14:38:34 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 22 14:38:34 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 22 14:38:34 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 22 14:38:34 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 22 14:38:34 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 22 14:38:34 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 22 14:38:34 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=b6d1ec0a-fcc0-4452-9de1-5fd577d3154f nomdmonddf nomdmonisw
Jul 22 14:38:34 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 22 14:38:34 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 22 14:38:34 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 22 14:38:34 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 22 14:38:34 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 22 14:38:34 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 22 14:38:34 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 22 14:38:34 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 22 14:38:34 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 22 14:38:34 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 22 14:38:34 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 22 14:38:34 node-4 kernel: [    0.000000] No AGP bridge found
Jul 22 14:38:34 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 22 14:38:34 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 22 14:38:34 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 22 14:38:34 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 22 14:38:34 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 22 14:38:34 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 22 14:38:34 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 22 14:38:34 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 22 14:38:34 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 22 14:38:34 node-4 kernel: [    0.000000]   2 disabled
Jul 22 14:38:34 node-4 kernel: [    0.000000]   3 disabled
Jul 22 14:38:34 node-4 kernel: [    0.000000]   4 disabled
Jul 22 14:38:34 node-4 kernel: [    0.000000]   5 disabled
Jul 22 14:38:34 node-4 kernel: [    0.000000]   6 disabled
Jul 22 14:38:34 node-4 kernel: [    0.000000]   7 disabled
Jul 22 14:38:34 node-4 kernel: [    0.000000]   8 disabled
Jul 22 14:38:34 node-4 kernel: [    0.000000]   9 disabled
Jul 22 14:38:34 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 22 14:38:34 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 22 14:38:34 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 22 14:38:34 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 22 14:38:34 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 22 14:38:34 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 22 14:38:34 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 22 14:38:34 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 22 14:38:34 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 22 14:38:34 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 22 14:38:34 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 22 14:38:34 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 22 14:38:34 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 22 14:38:34 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 22 14:38:34 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 22 14:38:34 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 22 14:38:34 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 22 14:38:34 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 22 14:38:34 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 22 14:38:34 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 22 14:38:34 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 22 14:38:34 node-4 kernel: [    0.000000] Zone ranges:
Jul 22 14:38:34 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 22 14:38:34 node-4 kernel: [    0.000000] Early memory node ranges
Jul 22 14:38:34 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 22 14:38:34 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 22 14:38:34 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 22 14:38:34 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 22 14:38:34 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 22 14:38:34 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 22 14:38:34 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 22 14:38:34 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 22 14:38:34 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 22 14:38:34 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 22 14:38:34 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 22 14:38:34 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 22 14:38:34 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 22 14:38:34 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 22 14:38:34 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 22 14:38:34 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 22 14:38:34 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 22 14:38:34 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 22 14:38:34 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 22 14:38:34 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 22 14:38:34 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 22 14:38:34 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 22 14:38:34 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 22 14:38:34 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 22 14:38:34 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 22 14:38:34 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 22 14:38:34 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=b6d1ec0a-fcc0-4452-9de1-5fd577d3154f nomdmonddf nomdmonisw
Jul 22 14:38:34 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 22 14:38:34 node-4 kernel: [    0.000000] Checking aperture...
Jul 22 14:38:34 node-4 kernel: [    0.000000] No AGP bridge found
Jul 22 14:38:34 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 22 14:38:34 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 22 14:38:34 node-4 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 22 14:38:34 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 22 14:38:34 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 22 14:38:34 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 22 14:38:34 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 22 14:38:34 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 22 14:38:34 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 22 14:38:34 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 22 14:38:34 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 22 14:38:34 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 22 14:38:34 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 22 14:38:34 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 22 14:38:34 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 22 14:38:34 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 22 14:38:34 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 22 14:38:34 node-4 kernel: [    0.004000] tsc: Detected 3492.101 MHz processor
Jul 22 14:38:34 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.20 BogoMIPS (lpj=13968404)
Jul 22 14:38:34 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 22 14:38:34 node-4 kernel: [    0.000043] Security Framework initialized
Jul 22 14:38:34 node-4 kernel: [    0.000061] AppArmor: AppArmor initialized
Jul 22 14:38:34 node-4 kernel: [    0.000062] Yama: becoming mindful.
Jul 22 14:38:34 node-4 kernel: [    0.001457] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.006270] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.008197] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.008223] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.008512] Initializing cgroup subsys memory
Jul 22 14:38:34 node-4 kernel: [    0.008520] Initializing cgroup subsys devices
Jul 22 14:38:34 node-4 kernel: [    0.008522] Initializing cgroup subsys freezer
Jul 22 14:38:34 node-4 kernel: [    0.008524] Initializing cgroup subsys blkio
Jul 22 14:38:34 node-4 kernel: [    0.008525] Initializing cgroup subsys perf_event
Jul 22 14:38:34 node-4 kernel: [    0.008527] Initializing cgroup subsys hugetlb
Jul 22 14:38:34 node-4 kernel: [    0.008547] CPU: Physical Processor ID: 0
Jul 22 14:38:34 node-4 kernel: [    0.008548] CPU: Processor Core ID: 0
Jul 22 14:38:34 node-4 kernel: [    0.008552] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 22 14:38:34 node-4 kernel: [    0.008552] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 22 14:38:34 node-4 kernel: [    0.009246] mce: CPU supports 22 MCE banks
Jul 22 14:38:34 node-4 kernel: [    0.009273] CPU0: Thermal monitoring enabled (TM1)
Jul 22 14:38:34 node-4 kernel: [    0.009294] process: using mwait in idle threads
Jul 22 14:38:34 node-4 kernel: [    0.009296] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 22 14:38:34 node-4 kernel: [    0.009296] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 22 14:38:34 node-4 kernel: [    0.009296] tlb_flushall_shift: 6
Jul 22 14:38:34 node-4 kernel: [    0.009385] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 22 14:38:34 node-4 kernel: [    0.010109] ACPI: Core revision 20131115
Jul 22 14:38:34 node-4 kernel: [    0.022783] ACPI: All ACPI Tables successfully acquired
Jul 22 14:38:34 node-4 kernel: [    0.022955] ftrace: allocating 28617 entries in 112 pages
Jul 22 14:38:34 node-4 kernel: [    0.031752] dmar: Host address width 46
Jul 22 14:38:34 node-4 kernel: [    0.031754] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 22 14:38:34 node-4 kernel: [    0.031760] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 22 14:38:34 node-4 kernel: [    0.031762] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 22 14:38:34 node-4 kernel: [    0.031765] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 22 14:38:34 node-4 kernel: [    0.031767] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 22 14:38:34 node-4 kernel: [    0.031768] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 22 14:38:34 node-4 kernel: [    0.031769] dmar: ATSR flags: 0x0
Jul 22 14:38:34 node-4 kernel: [    0.031771] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 22 14:38:34 node-4 kernel: [    0.031772] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 22 14:38:34 node-4 kernel: [    0.031888] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 22 14:38:34 node-4 kernel: [    0.031889] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 22 14:38:34 node-4 kernel: [    0.031890] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 22 14:38:34 node-4 kernel: [    0.031891] HPET id 0 under DRHD base 0xc7ffc000
Jul 22 14:38:34 node-4 kernel: [    0.031892] Your BIOS is broken and requested that x2apic be disabled.
Jul 22 14:38:34 node-4 kernel: [    0.031892] This will slightly decrease performance.
Jul 22 14:38:34 node-4 kernel: [    0.031892] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 22 14:38:34 node-4 kernel: [    0.032324] Enabled IRQ remapping in xapic mode
Jul 22 14:38:34 node-4 kernel: [    0.032325] x2apic not enabled, IRQ remapping is in xapic mode
Jul 22 14:38:34 node-4 kernel: [    0.032329] Switched APIC routing to physical flat.
Jul 22 14:38:34 node-4 kernel: [    0.032955] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 22 14:38:34 node-4 kernel: [    0.072607] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 22 14:38:34 node-4 kernel: [    0.072612] TSC deadline timer enabled
Jul 22 14:38:34 node-4 kernel: [    0.072620] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 22 14:38:34 node-4 kernel: [    0.072625] ... version:                3
Jul 22 14:38:34 node-4 kernel: [    0.072626] ... bit width:              48
Jul 22 14:38:34 node-4 kernel: [    0.072627] ... generic registers:      4
Jul 22 14:38:34 node-4 kernel: [    0.072628] ... value mask:             0000ffffffffffff
Jul 22 14:38:34 node-4 kernel: [    0.072629] ... max period:             0000ffffffffffff
Jul 22 14:38:34 node-4 kernel: [    0.072630] ... fixed-purpose events:   3
Jul 22 14:38:34 node-4 kernel: [    0.072631] ... event mask:             000000070000000f
Jul 22 14:38:34 node-4 kernel: [    0.074061] x86: Booting SMP configuration:
Jul 22 14:38:34 node-4 kernel: [    0.088165] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 22 14:38:34 node-4 kernel: [    0.074062] .... node  #0, CPUs:        #1  #2  #3
Jul 22 14:38:34 node-4 kernel: [    0.116075] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 22 14:38:34 node-4 kernel: [    0.270226] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 22 14:38:34 node-4 kernel: [    0.325845] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 22 14:38:34 node-4 kernel: [    0.382699] x86: Booted up 2 nodes, 16 CPUs
Jul 22 14:38:34 node-4 kernel: [    0.382702] smpboot: Total of 16 processors activated (111759.21 BogoMIPS)
Jul 22 14:38:34 node-4 kernel: [    0.406690] devtmpfs: initialized
Jul 22 14:38:34 node-4 kernel: [    0.409760] EVM: security.selinux
Jul 22 14:38:34 node-4 kernel: [    0.409761] EVM: security.SMACK64
Jul 22 14:38:34 node-4 kernel: [    0.409762] EVM: security.ima
Jul 22 14:38:34 node-4 kernel: [    0.409763] EVM: security.capability
Jul 22 14:38:34 node-4 kernel: [    0.409813] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.410501] pinctrl core: initialized pinctrl subsystem
Jul 22 14:38:34 node-4 kernel: [    0.410563] regulator-dummy: no parameters
Jul 22 14:38:34 node-4 kernel: [    0.410594] RTC time: 14:37:57, date: 07/22/16
Jul 22 14:38:34 node-4 kernel: [    0.410628] NET: Registered protocol family 16
Jul 22 14:38:34 node-4 kernel: [    0.410711] cpuidle: using governor ladder
Jul 22 14:38:34 node-4 kernel: [    0.410712] cpuidle: using governor menu
Jul 22 14:38:34 node-4 kernel: [    0.410746] ACPI: bus type PCI registered
Jul 22 14:38:34 node-4 kernel: [    0.410748] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 22 14:38:34 node-4 kernel: [    0.410793] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 22 14:38:34 node-4 kernel: [    0.410796] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 22 14:38:34 node-4 kernel: [    0.424531] PCI: Using configuration type 1 for base access
Jul 22 14:38:34 node-4 kernel: [    0.425525] bio: create slab <bio-0> at 0
Jul 22 14:38:34 node-4 kernel: [    0.425800] ACPI: Added _OSI(Module Device)
Jul 22 14:38:34 node-4 kernel: [    0.425802] ACPI: Added _OSI(Processor Device)
Jul 22 14:38:34 node-4 kernel: [    0.425803] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 22 14:38:34 node-4 kernel: [    0.425804] ACPI: Added _OSI(Processor Aggregator Device)
Jul 22 14:38:34 node-4 kernel: [    0.438480] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 22 14:38:34 node-4 kernel: [    0.449991] ACPI: Interpreter enabled
Jul 22 14:38:34 node-4 kernel: [    0.449997] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 22 14:38:34 node-4 kernel: [    0.450001] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 22 14:38:34 node-4 kernel: [    0.450003] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 22 14:38:34 node-4 kernel: [    0.450010] ACPI: (supports S0 S4 S5)
Jul 22 14:38:34 node-4 kernel: [    0.450011] ACPI: Using IOAPIC for interrupt routing
Jul 22 14:38:34 node-4 kernel: [    0.450053] HEST: Table parsing has been initialized.
Jul 22 14:38:34 node-4 kernel: [    0.450056] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 22 14:38:34 node-4 kernel: [    0.450607] ACPI: No dock devices found.
Jul 22 14:38:34 node-4 kernel: [    0.462198] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 22 14:38:34 node-4 kernel: [    0.462203] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 14:38:34 node-4 kernel: [    0.462206] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 22 14:38:34 node-4 kernel: [    0.462232] PCI host bridge to bus 0000:ff
Jul 22 14:38:34 node-4 kernel: [    0.462234] pci_bus 0000:ff: root bus resource [bus ff]
Jul 22 14:38:34 node-4 kernel: [    0.462242] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 22 14:38:34 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 22 14:38:34 node-4 kernel: [    0.462281] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.462311] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462346] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462375] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.462404] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.462434] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462462] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462490] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462517] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462543] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462569] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462597] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462625] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462651] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462678] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462706] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462733] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462761] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.462790] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462817] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.462843] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462869] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462898] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.462932] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462963] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.462993] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463023] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463053] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463084] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463114] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463144] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463174] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463205] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463238] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463271] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463304] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463333] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463360] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463391] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463426] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463464] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463500] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463533] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463564] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463592] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463624] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463655] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463688] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463720] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463751] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463781] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463809] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463838] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463868] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463900] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463932] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.463990] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 22 14:38:34 node-4 kernel: [    0.463993] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 14:38:34 node-4 kernel: [    0.463995] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 22 14:38:34 node-4 kernel: [    0.464014] PCI host bridge to bus 0000:7f
Jul 22 14:38:34 node-4 kernel: [    0.464015] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 22 14:38:34 node-4 kernel: [    0.464020] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464048] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.464075] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464102] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464124] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.464149] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.464175] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464201] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464226] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464249] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464271] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464294] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464325] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464349] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464375] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464403] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464425] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464448] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464470] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.464494] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464516] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.464538] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464562] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464591] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 22 14:38:34 node-4 kernel: [    0.464625] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464651] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464677] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464704] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464729] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464757] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464785] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464815] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464840] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464868] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464896] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464925] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464953] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.464980] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465006] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465035] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465060] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465086] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465116] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465144] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465171] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465196] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465222] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465248] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465278] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465305] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465333] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465359] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465381] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465407] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465432] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465461] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.465486] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.466727] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 22 14:38:34 node-4 kernel: [    0.466730] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 14:38:34 node-4 kernel: [    0.467847] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 22 14:38:34 node-4 kernel: [    0.468357] PCI host bridge to bus 0000:00
Jul 22 14:38:34 node-4 kernel: [    0.468360] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 22 14:38:34 node-4 kernel: [    0.468361] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 22 14:38:34 node-4 kernel: [    0.468363] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 22 14:38:34 node-4 kernel: [    0.468364] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 22 14:38:34 node-4 kernel: [    0.468365] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 22 14:38:34 node-4 kernel: [    0.468367] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 22 14:38:34 node-4 kernel: [    0.468368] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 22 14:38:34 node-4 kernel: [    0.468374] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 22 14:38:34 node-4 kernel: [    0.468458] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.468489] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.468531] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 22 14:38:34 node-4 kernel: [    0.468550] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.468579] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.468619] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 22 14:38:34 node-4 kernel: [    0.468637] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.468666] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.468706] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 22 14:38:34 node-4 kernel: [    0.468723] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.468793] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.468870] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.468945] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 22 14:38:34 node-4 kernel: [    0.468950] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 22 14:38:34 node-4 kernel: [    0.469034] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 22 14:38:34 node-4 kernel: [    0.469181] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 22 14:38:34 node-4 kernel: [    0.469198] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 22 14:38:34 node-4 kernel: [    0.469276] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.469331] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 22 14:38:34 node-4 kernel: [    0.469352] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.469408] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.469451] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 22 14:38:34 node-4 kernel: [    0.469478] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.469534] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.469577] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 22 14:38:34 node-4 kernel: [    0.469601] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 22 14:38:34 node-4 kernel: [    0.469618] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 22 14:38:34 node-4 kernel: [    0.469696] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.469745] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 22 14:38:34 node-4 kernel: [    0.469770] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 22 14:38:34 node-4 kernel: [    0.470016] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 22 14:38:34 node-4 kernel: [    0.470022] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 22 14:38:34 node-4 kernel: [    0.470028] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.470034] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.470041] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 22 14:38:34 node-4 kernel: [    0.470071] pci 0000:01:00.0: supports D1 D2
Jul 22 14:38:34 node-4 kernel: [    0.480322] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 22 14:38:34 node-4 kernel: [    0.480329] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 22 14:38:34 node-4 kernel: [    0.480333] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 22 14:38:34 node-4 kernel: [    0.480534] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.480567] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 22 14:38:34 node-4 kernel: [    0.492318] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 22 14:38:34 node-4 kernel: [    0.492325] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.492329] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 14:38:34 node-4 kernel: [    0.492413] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.492489] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.492584] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.492665] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 22 14:38:34 node-4 kernel: [    0.492673] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.492677] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 14:38:34 node-4 kernel: [    0.492756] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.492892] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.492945] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 22 14:38:34 node-4 kernel: [    0.492947] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.492950] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 14:38:34 node-4 kernel: [    0.493017] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.493140] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.493181] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.493300] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.493336] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.493456] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.493491] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 22 14:38:34 node-4 kernel: [    0.493612] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 22 14:38:34 node-4 kernel: [    0.493653] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 22 14:38:34 node-4 kernel: [    0.493656] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.493658] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 14:38:34 node-4 kernel: [    0.493719] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 22 14:38:34 node-4 kernel: [    0.493782] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.493834] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.493875] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 22 14:38:34 node-4 kernel: [    0.493957] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 22 14:38:34 node-4 kernel: [    0.494083] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 22 14:38:34 node-4 kernel: [    0.494086] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.494088] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 22 14:38:34 node-4 kernel: [    0.494144] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 22 14:38:34 node-4 kernel: [    0.494201] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.494249] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.494462] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 22 14:38:34 node-4 kernel: [    0.494466] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 22 14:38:34 node-4 kernel: [    0.494529] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 22 14:38:34 node-4 kernel: [    0.494582] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.494633] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.494842] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 22 14:38:34 node-4 kernel: [    0.494846] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 22 14:38:34 node-4 kernel: [    0.494904] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 22 14:38:34 node-4 kernel: [    0.494964] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.495041] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 22 14:38:34 node-4 kernel: [    0.495265] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 22 14:38:34 node-4 kernel: [    0.495268] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 22 14:38:34 node-4 kernel: [    0.495442] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 22 14:38:34 node-4 kernel: [    0.495480] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 22 14:38:34 node-4 kernel: [    0.495558] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 22 14:38:34 node-4 kernel: [    0.495577] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 22 14:38:34 node-4 kernel: [    0.495590] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 22 14:38:34 node-4 kernel: [    0.495604] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 22 14:38:34 node-4 kernel: [    0.495654] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 22 14:38:34 node-4 kernel: [    0.500327] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 22 14:38:34 node-4 kernel: [    0.500336] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 22 14:38:34 node-4 kernel: [    0.500396] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 22 14:38:34 node-4 kernel: [    0.500886] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 22 14:38:34 node-4 kernel: [    0.500889] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 22 14:38:34 node-4 kernel: [    0.501008] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 22 14:38:34 node-4 kernel: [    0.501118] PCI host bridge to bus 0000:80
Jul 22 14:38:34 node-4 kernel: [    0.501121] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 22 14:38:34 node-4 kernel: [    0.501122] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 22 14:38:34 node-4 kernel: [    0.501123] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 22 14:38:34 node-4 kernel: [    0.501132] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.501195] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.501263] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 22 14:38:34 node-4 kernel: [    0.501326] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 22 14:38:34 node-4 kernel: [    0.501331] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 22 14:38:34 node-4 kernel: [    0.501404] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 22 14:38:34 node-4 kernel: [    0.501701] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 22 14:38:34 node-4 kernel: [    0.501732] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 22 14:38:34 node-4 kernel: [    0.501762] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 22 14:38:34 node-4 kernel: [    0.501790] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 22 14:38:34 node-4 kernel: [    0.501820] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 14:38:34 node-4 kernel: [    0.501849] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 14:38:34 node-4 kernel: [    0.501879] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 14:38:34 node-4 kernel: [    0.501908] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 22 14:38:34 node-4 kernel: [    0.501993] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 22 14:38:34 node-4 kernel: [    0.501998] ACPI: \_SB_.UNC1: notify handler is installed
Jul 22 14:38:34 node-4 kernel: [    0.501999] ACPI: \_SB_.UNC0: notify handler is installed
Jul 22 14:38:34 node-4 kernel: [    0.502014] ACPI: \_SB_.PCI0: notify handler is installed
Jul 22 14:38:34 node-4 kernel: [    0.502066] ACPI: \_SB_.PCI1: notify handler is installed
Jul 22 14:38:34 node-4 kernel: [    0.502146] Found 4 acpi root devices
Jul 22 14:38:34 node-4 kernel: [    0.502257] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 22 14:38:34 node-4 kernel: [    0.502259] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 22 14:38:34 node-4 kernel: [    0.502260] vgaarb: loaded
Jul 22 14:38:34 node-4 kernel: [    0.502261] vgaarb: bridge control possible 0000:0c:00.0
Jul 22 14:38:34 node-4 kernel: [    0.502378] SCSI subsystem initialized
Jul 22 14:38:34 node-4 kernel: [    0.502441] libata version 3.00 loaded.
Jul 22 14:38:34 node-4 kernel: [    0.502457] ACPI: bus type USB registered
Jul 22 14:38:34 node-4 kernel: [    0.502467] usbcore: registered new interface driver usbfs
Jul 22 14:38:34 node-4 kernel: [    0.502472] usbcore: registered new interface driver hub
Jul 22 14:38:34 node-4 kernel: [    0.502496] usbcore: registered new device driver usb
Jul 22 14:38:34 node-4 kernel: [    0.502661] PCI: Using ACPI for IRQ routing
Jul 22 14:38:34 node-4 kernel: [    0.506275] PCI: pci_cache_line_size set to 64 bytes
Jul 22 14:38:34 node-4 kernel: [    0.506482] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 22 14:38:34 node-4 kernel: [    0.506483] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 22 14:38:34 node-4 kernel: [    0.506484] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 22 14:38:34 node-4 kernel: [    0.506550] NetLabel: Initializing
Jul 22 14:38:34 node-4 kernel: [    0.506551] NetLabel:  domain hash size = 128
Jul 22 14:38:34 node-4 kernel: [    0.506552] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 22 14:38:34 node-4 kernel: [    0.506562] NetLabel:  unlabeled traffic allowed by default
Jul 22 14:38:34 node-4 kernel: [    0.506619] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 22 14:38:34 node-4 kernel: [    0.506624] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 22 14:38:34 node-4 kernel: [    0.508681] Switched to clocksource hpet
Jul 22 14:38:34 node-4 kernel: [    0.512658] AppArmor: AppArmor Filesystem Enabled
Jul 22 14:38:34 node-4 kernel: [    0.512678] pnp: PnP ACPI init
Jul 22 14:38:34 node-4 kernel: [    0.512685] ACPI: bus type PNP registered
Jul 22 14:38:34 node-4 kernel: [    0.512796] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 22 14:38:34 node-4 kernel: [    0.512804] pnp 00:01: [dma 4]
Jul 22 14:38:34 node-4 kernel: [    0.512816] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 22 14:38:34 node-4 kernel: [    0.512843] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 22 14:38:34 node-4 kernel: [    0.512862] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 22 14:38:34 node-4 kernel: [    0.512880] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 22 14:38:34 node-4 kernel: [    0.512913] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 22 14:38:34 node-4 kernel: [    0.512967] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512969] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 22 14:38:34 node-4 kernel: [    0.512971] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512972] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512974] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512978] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512981] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 22 14:38:34 node-4 kernel: [    0.512982] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512984] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512985] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512987] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512988] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512990] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 22 14:38:34 node-4 kernel: [    0.512992] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 22 14:38:34 node-4 kernel: [    0.513076] pnp 00:07: [dma 0 disabled]
Jul 22 14:38:34 node-4 kernel: [    0.513104] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 22 14:38:34 node-4 kernel: [    0.513179] pnp 00:08: [dma 0 disabled]
Jul 22 14:38:34 node-4 kernel: [    0.513211] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 22 14:38:34 node-4 kernel: [    0.513262] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 22 14:38:34 node-4 kernel: [    0.513624] pnp: PnP ACPI: found 10 devices
Jul 22 14:38:34 node-4 kernel: [    0.513625] ACPI: bus type PNP unregistered
Jul 22 14:38:34 node-4 kernel: [    0.519872] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 22 14:38:34 node-4 kernel: [    0.519874] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 22 14:38:34 node-4 kernel: [    0.519877] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 22 14:38:34 node-4 kernel: [    0.519881] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 22 14:38:34 node-4 kernel: [    0.519883] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.519898] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 22 14:38:34 node-4 kernel: [    0.519927] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 22 14:38:34 node-4 kernel: [    0.519941] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 22 14:38:34 node-4 kernel: [    0.519970] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 22 14:38:34 node-4 kernel: [    0.519998] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 22 14:38:34 node-4 kernel: [    0.520027] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 22 14:38:34 node-4 kernel: [    0.520041] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 22 14:38:34 node-4 kernel: [    0.520070] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 22 14:38:34 node-4 kernel: [    0.520072] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.520087] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 14:38:34 node-4 kernel: [    0.520119] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 22 14:38:34 node-4 kernel: [    0.520121] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.520136] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 22 14:38:34 node-4 kernel: [    0.520164] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 22 14:38:34 node-4 kernel: [    0.520166] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.520169] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 14:38:34 node-4 kernel: [    0.520173] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 22 14:38:34 node-4 kernel: [    0.520175] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.520177] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 22 14:38:34 node-4 kernel: [    0.520181] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 22 14:38:34 node-4 kernel: [    0.520185] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 22 14:38:34 node-4 kernel: [    0.520193] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 22 14:38:34 node-4 kernel: [    0.520197] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 22 14:38:34 node-4 kernel: [    0.520203] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 22 14:38:34 node-4 kernel: [    0.520204] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 22 14:38:34 node-4 kernel: [    0.520205] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 22 14:38:34 node-4 kernel: [    0.520206] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 22 14:38:34 node-4 kernel: [    0.520207] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 22 14:38:34 node-4 kernel: [    0.520208] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 22 14:38:34 node-4 kernel: [    0.520208] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 22 14:38:34 node-4 kernel: [    0.520209] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 22 14:38:34 node-4 kernel: [    0.520210] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.520211] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 22 14:38:34 node-4 kernel: [    0.520212] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.520213] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 22 14:38:34 node-4 kernel: [    0.520214] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.520215] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 22 14:38:34 node-4 kernel: [    0.520216] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.520216] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 22 14:38:34 node-4 kernel: [    0.520217] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 22 14:38:34 node-4 kernel: [    0.520218] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 22 14:38:34 node-4 kernel: [    0.520219] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 22 14:38:34 node-4 kernel: [    0.520220] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 22 14:38:34 node-4 kernel: [    0.520221] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 22 14:38:34 node-4 kernel: [    0.520222] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 22 14:38:34 node-4 kernel: [    0.520224] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 22 14:38:34 node-4 kernel: [    0.520225] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 22 14:38:34 node-4 kernel: [    0.520264] NET: Registered protocol family 2
Jul 22 14:38:34 node-4 kernel: [    0.520522] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.520863] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.521008] TCP: Hash tables configured (established 262144 bind 65536)
Jul 22 14:38:34 node-4 kernel: [    0.521051] TCP: reno registered
Jul 22 14:38:34 node-4 kernel: [    0.521080] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.521175] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.521322] NET: Registered protocol family 1
Jul 22 14:38:34 node-4 kernel: [    0.560777] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 22 14:38:34 node-4 kernel: [    0.560791] PCI: CLS 64 bytes, default 64
Jul 22 14:38:34 node-4 kernel: [    0.560860] Trying to unpack rootfs image as initramfs...
Jul 22 14:38:34 node-4 kernel: [    0.780137] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 22 14:38:34 node-4 kernel: [    0.780174] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 22 14:38:34 node-4 kernel: [    0.780176] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 22 14:38:34 node-4 kernel: [    0.780597] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780604] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780608] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780614] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780626] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780644] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780659] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780674] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780686] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780695] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780701] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780707] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780716] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780728] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780741] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780754] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 22 14:38:34 node-4 kernel: [    0.780848] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 22 14:38:34 node-4 kernel: [    0.780851] Scanning for low memory corruption every 60 seconds
Jul 22 14:38:34 node-4 kernel: [    0.781226] Initialise system trusted keyring
Jul 22 14:38:34 node-4 kernel: [    0.781279] audit: initializing netlink socket (disabled)
Jul 22 14:38:34 node-4 kernel: [    0.781294] type=2000 audit(1469198277.736:1): initialized
Jul 22 14:38:34 node-4 kernel: [    0.799195] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 22 14:38:34 node-4 kernel: [    0.800731] zbud: loaded
Jul 22 14:38:34 node-4 kernel: [    0.800850] VFS: Disk quotas dquot_6.5.2
Jul 22 14:38:34 node-4 kernel: [    0.800886] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 22 14:38:34 node-4 kernel: [    0.801258] fuse init (API version 7.22)
Jul 22 14:38:34 node-4 kernel: [    0.801317] msgmni has been set to 32768
Jul 22 14:38:34 node-4 kernel: [    0.801365] Key type big_key registered
Jul 22 14:38:34 node-4 kernel: [    0.801911] Key type asymmetric registered
Jul 22 14:38:34 node-4 kernel: [    0.801913] Asymmetric key parser 'x509' registered
Jul 22 14:38:34 node-4 kernel: [    0.801935] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 22 14:38:34 node-4 kernel: [    0.802006] io scheduler noop registered
Jul 22 14:38:34 node-4 kernel: [    0.802008] io scheduler deadline registered (default)
Jul 22 14:38:34 node-4 kernel: [    0.802026] io scheduler cfq registered
Jul 22 14:38:34 node-4 kernel: [    0.802440] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    0.802568] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    0.802684] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    0.802794] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    0.802908] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    0.803009] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    0.803403] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 22 14:38:34 node-4 kernel: [    0.803429] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 22 14:38:34 node-4 kernel: [    0.803445] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 22 14:38:34 node-4 kernel: [    0.803454] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803456] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803459] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 22 14:38:34 node-4 kernel: [    0.803470] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803472] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803473] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803475] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803476] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803478] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803479] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803481] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803482] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803484] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803485] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803486] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803489] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 22 14:38:34 node-4 kernel: [    0.803494] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803496] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 22 14:38:34 node-4 kernel: [    0.803509] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803512] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 22 14:38:34 node-4 kernel: [    0.803522] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803524] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 22 14:38:34 node-4 kernel: [    0.803527] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 22 14:38:34 node-4 kernel: [    0.803564] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 22 14:38:34 node-4 kernel: [    0.803570] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 22 14:38:34 node-4 kernel: [    0.803574] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 22 14:38:34 node-4 kernel: [    0.803583] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 22 14:38:34 node-4 kernel: [    0.803625] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 22 14:38:34 node-4 kernel: [    0.803626] vesafb: scrolling: redraw
Jul 22 14:38:34 node-4 kernel: [    0.803628] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 22 14:38:34 node-4 kernel: [    0.824288] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 22 14:38:34 node-4 kernel: [    0.832933] Console: switching to colour frame buffer device 80x30
Jul 22 14:38:34 node-4 kernel: [    0.841621] fb0: VESA VGA frame buffer device
Jul 22 14:38:34 node-4 kernel: [    0.841828] intel_idle: MWAIT substates: 0x2120
Jul 22 14:38:34 node-4 kernel: [    0.841829] intel_idle: v0.4 model 0x3F
Jul 22 14:38:34 node-4 kernel: [    0.841829] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 22 14:38:34 node-4 kernel: [    0.842049] ipmi message handler version 39.2
Jul 22 14:38:34 node-4 kernel: [    0.842328] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 22 14:38:34 node-4 kernel: [    0.842765] ACPI: AC Adapter [P111] (on-line)
Jul 22 14:38:34 node-4 kernel: [    0.848005] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 22 14:38:34 node-4 kernel: [    0.858987] ACPI: Power Button [PWRB]
Jul 22 14:38:34 node-4 kernel: [    0.864777] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 22 14:38:34 node-4 kernel: [    0.876388] ACPI: Power Button [PWRF]
Jul 22 14:38:34 node-4 kernel: [    0.894143] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 22 14:38:34 node-4 kernel: [    0.905783] pstore: Registered erst as persistent store backend
Jul 22 14:38:34 node-4 kernel: [    0.911951] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 22 14:38:34 node-4 kernel: [    0.923860] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 22 14:38:34 node-4 kernel: [    0.950589] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 22 14:38:34 node-4 kernel: [    0.983853] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 22 14:38:34 node-4 kernel: [    0.997968] Linux agpgart interface v0.103
Jul 22 14:38:34 node-4 kernel: [    1.005629] brd: module loaded
Jul 22 14:38:34 node-4 kernel: [    1.012671] loop: module loaded
Jul 22 14:38:34 node-4 kernel: [    1.019370] libphy: Fixed MDIO Bus: probed
Jul 22 14:38:34 node-4 kernel: [    1.025817] tun: Universal TUN/TAP device driver, 1.6
Jul 22 14:38:34 node-4 kernel: [    1.032293] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 22 14:38:34 node-4 kernel: [    1.038811] PPP generic driver version 2.4.2
Jul 22 14:38:34 node-4 kernel: [    1.045199] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 22 14:38:34 node-4 kernel: [    1.051627] ehci-pci: EHCI PCI platform driver
Jul 22 14:38:34 node-4 kernel: [    1.058150] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 22 14:38:34 node-4 kernel: [    1.064552] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 22 14:38:34 node-4 kernel: [    1.077057] ehci-pci 0000:00:1a.0: debug port 2
Jul 22 14:38:34 node-4 kernel: [    1.087248] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 22 14:38:34 node-4 kernel: [    1.087267] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 22 14:38:34 node-4 kernel: [    1.104180] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 22 14:38:34 node-4 kernel: [    1.110252] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 22 14:38:34 node-4 kernel: [    1.116425] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 22 14:38:34 node-4 kernel: [    1.128327] usb usb1: Product: EHCI Host Controller
Jul 22 14:38:34 node-4 kernel: [    1.134360] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 22 14:38:34 node-4 kernel: [    1.140408] usb usb1: SerialNumber: 0000:00:1a.0
Jul 22 14:38:34 node-4 kernel: [    1.146401] hub 1-0:1.0: USB hub found
Jul 22 14:38:34 node-4 kernel: [    1.152178] hub 1-0:1.0: 2 ports detected
Jul 22 14:38:34 node-4 kernel: [    1.157964] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 22 14:38:34 node-4 kernel: [    1.163544] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 22 14:38:34 node-4 kernel: [    1.174420] ehci-pci 0000:00:1d.0: debug port 2
Jul 22 14:38:34 node-4 kernel: [    1.183720] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 22 14:38:34 node-4 kernel: [    1.183723] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 22 14:38:34 node-4 kernel: [    1.200099] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 22 14:38:34 node-4 kernel: [    1.205297] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 22 14:38:34 node-4 kernel: [    1.210592] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 22 14:38:34 node-4 kernel: [    1.221139] usb usb2: Product: EHCI Host Controller
Jul 22 14:38:34 node-4 kernel: [    1.226672] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 22 14:38:34 node-4 kernel: [    1.232235] usb usb2: SerialNumber: 0000:00:1d.0
Jul 22 14:38:34 node-4 kernel: [    1.237770] hub 2-0:1.0: USB hub found
Jul 22 14:38:34 node-4 kernel: [    1.243113] hub 2-0:1.0: 2 ports detected
Jul 22 14:38:34 node-4 kernel: [    1.248408] ehci-platform: EHCI generic platform driver
Jul 22 14:38:34 node-4 kernel: [    1.253692] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 22 14:38:34 node-4 kernel: [    1.259103] ohci-pci: OHCI PCI platform driver
Jul 22 14:38:34 node-4 kernel: [    1.264481] ohci-platform: OHCI generic platform driver
Jul 22 14:38:34 node-4 kernel: [    1.269725] uhci_hcd: USB Universal Host Controller Interface driver
Jul 22 14:38:34 node-4 kernel: [    1.275048] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 22 14:38:34 node-4 kernel: [    1.467878] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 22 14:38:34 node-4 kernel: [    1.640044] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 22 14:38:34 node-4 kernel: [    1.645605] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 22 14:38:34 node-4 kernel: [    1.651435] hub 1-1:1.0: USB hub found
Jul 22 14:38:34 node-4 kernel: [    1.656905] hub 1-1:1.0: 6 ports detected
Jul 22 14:38:34 node-4 kernel: [    1.771612] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 22 14:38:34 node-4 kernel: [    1.775956] tsc: Refined TSC clocksource calibration: 3491.886 MHz
Jul 22 14:38:34 node-4 kernel: [    2.039705] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 22 14:38:34 node-4 kernel: [    2.045245] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 22 14:38:34 node-4 kernel: [    2.051098] hub 2-1:1.0: USB hub found
Jul 22 14:38:34 node-4 kernel: [    2.056817] hub 2-1:1.0: 8 ports detected
Jul 22 14:38:34 node-4 kernel: [    2.316841] i8042: No controller found
Jul 22 14:38:34 node-4 kernel: [    2.322272] mousedev: PS/2 mouse device common for all mice
Jul 22 14:38:34 node-4 kernel: [    2.327793] rtc_cmos 00:02: RTC can wake from S4
Jul 22 14:38:34 node-4 kernel: [    2.333365] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 22 14:38:34 node-4 kernel: [    2.335207] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 22 14:38:34 node-4 kernel: [    2.344504] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 22 14:38:34 node-4 kernel: [    2.355596] device-mapper: uevent: version 1.0.3
Jul 22 14:38:34 node-4 kernel: [    2.361234] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 22 14:38:34 node-4 kernel: [    2.372465] ledtrig-cpu: registered to indicate activity on CPUs
Jul 22 14:38:34 node-4 kernel: [    2.378389] TCP: cubic registered
Jul 22 14:38:34 node-4 kernel: [    2.384265] NET: Registered protocol family 10
Jul 22 14:38:34 node-4 kernel: [    2.390251] NET: Registered protocol family 17
Jul 22 14:38:34 node-4 kernel: [    2.395919] Key type dns_resolver registered
Jul 22 14:38:34 node-4 kernel: [    2.401914] Loading compiled-in X.509 certificates
Jul 22 14:38:34 node-4 kernel: [    2.408057] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 22 14:38:34 node-4 kernel: [    2.419427] registered taskstats version 1
Jul 22 14:38:34 node-4 kernel: [    2.427363] Key type trusted registered
Jul 22 14:38:34 node-4 kernel: [    2.434905] Key type encrypted registered
Jul 22 14:38:34 node-4 kernel: [    2.440377] AppArmor: AppArmor sha1 policy hashing enabled
Jul 22 14:38:34 node-4 kernel: [    2.445870] IMA: No TPM chip found, activating TPM-bypass!
Jul 22 14:38:34 node-4 kernel: [    2.452021] regulator-dummy: disabling
Jul 22 14:38:34 node-4 kernel: [    2.457612]   Magic number: 8:724:637
Jul 22 14:38:34 node-4 kernel: [    2.463295] rtc_cmos 00:02: setting system clock to 2016-07-22 14:37:59 UTC (1469198279)
Jul 22 14:38:34 node-4 kernel: [    2.475704] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 22 14:38:34 node-4 kernel: [    2.481310] EDD information not available.
Jul 22 14:38:34 node-4 kernel: [    2.484015] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 22 14:38:34 node-4 kernel: [    2.484017] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 22 14:38:34 node-4 kernel: [    2.484017] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 22 14:38:34 node-4 kernel: [    2.484018] usb 2-1.4: Manufacturer: Avocent
Jul 22 14:38:34 node-4 kernel: [    2.484019] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 22 14:38:34 node-4 kernel: [    2.522058] PM: Hibernation image not present or could not be loaded.
Jul 22 14:38:34 node-4 kernel: [    2.522912] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 22 14:38:34 node-4 kernel: [    2.534297] Write protecting the kernel read-only data: 12288k
Jul 22 14:38:34 node-4 kernel: [    2.540607] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 22 14:38:34 node-4 kernel: [    2.553130] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 22 14:38:34 node-4 kernel: [    2.584858] device-mapper: multipath: version 1.6.0 loaded
Jul 22 14:38:34 node-4 kernel: [    2.593043] systemd-udevd[215]: starting version 204
Jul 22 14:38:34 node-4 kernel: [    2.614973] md: linear personality registered for level -1
Jul 22 14:38:34 node-4 kernel: [    2.629847] md: multipath personality registered for level -4
Jul 22 14:38:34 node-4 kernel: [    2.637812] md: raid0 personality registered for level 0
Jul 22 14:38:34 node-4 kernel: [    2.646198] md: raid1 personality registered for level 1
Jul 22 14:38:34 node-4 kernel: [    2.652573] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 22 14:38:34 node-4 kernel: [    2.659005] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 22 14:38:34 node-4 kernel: [    2.665468] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 22 14:38:34 node-4 kernel: [    2.665534] megasas: FW now in Ready state
Jul 22 14:38:34 node-4 kernel: [    2.665599] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665639] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665679] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665701] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665735] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665776] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665813] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665849] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665886] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665921] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665959] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.665995] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.666094] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.666198] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.666241] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.666278] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.666438] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 22 14:38:34 node-4 kernel: [    2.691164] hidraw: raw HID events driver (C) Jiri Kosina
Jul 22 14:38:34 node-4 kernel: [    2.699448] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 22 14:38:34 node-4 kernel: [    2.712286] 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 22 14:38:34 node-4 kernel: [    2.725636] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 14:38:34 node-4 kernel: [    2.727045] raid6: sse2x1    6300 MB/s
Jul 22 14:38:34 node-4 kernel: [    2.739153] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.739157] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.739161] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.739165] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.739205] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.754180] usbcore: registered new interface driver usbhid
Jul 22 14:38:34 node-4 kernel: [    2.761049] usbhid: USB HID core driver
Jul 22 14:38:34 node-4 kernel: [    2.764246] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 22 14:38:34 node-4 kernel: [    2.764250] 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 22 14:38:34 node-4 kernel: [    2.764251] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 14:38:34 node-4 kernel: [    2.764686] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.764748] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.764827] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.764918] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.765230] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 14:38:34 node-4 kernel: [    2.781306] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 22 14:38:34 node-4 kernel: [    2.781334] 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 22 14:38:34 node-4 kernel: [    2.781361] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 14:38:34 node-4 kernel: [    2.795023] raid6: sse2x2    1186 MB/s
Jul 22 14:38:34 node-4 kernel: [    2.862705] raid6: sse2x4    2348 MB/s
Jul 22 14:38:34 node-4 kernel: [    2.934631] raid6: avx2x1   14947 MB/s
Jul 22 14:38:34 node-4 kernel: [    3.006581] raid6: avx2x2   18885 MB/s
Jul 22 14:38:34 node-4 kernel: [    3.078516] raid6: avx2x4   21310 MB/s
Jul 22 14:38:34 node-4 kernel: [    3.084966] raid6: using algorithm avx2x4 (21310 MB/s)
Jul 22 14:38:34 node-4 kernel: [    3.091339] raid6: using avx2x2 recovery algorithm
Jul 22 14:38:34 node-4 kernel: [    3.097627] megasas:IOC Init cmd success
Jul 22 14:38:34 node-4 kernel: [    3.097629] Switched to clocksource tsc
Jul 22 14:38:34 node-4 kernel: [    3.097709] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    3.097749] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    3.097788] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    3.097837] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    3.097929] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 14:38:34 node-4 kernel: [    3.122388] xor: automatically using best checksumming function:
Jul 22 14:38:34 node-4 kernel: [    3.128533] 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 22 14:38:34 node-4 kernel: [    3.134524] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 22 14:38:34 node-4 kernel: [    3.134526] 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 22 14:38:34 node-4 kernel: [    3.134527] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 22 14:38:34 node-4 kernel: [    3.134596] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    3.134637] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    3.134677] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    3.134718] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 22 14:38:34 node-4 kernel: [    3.134806] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 22 14:38:34 node-4 kernel: [    3.142485] megasas: INIT adapter done
Jul 22 14:38:34 node-4 kernel: [    3.166432]    avx       : 36851.000 MB/sec
Jul 22 14:38:34 node-4 kernel: [    3.195311] 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 22 14:38:34 node-4 kernel: [    3.207369] async_tx: api initialized (async)
Jul 22 14:38:34 node-4 kernel: [    3.207418] 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 22 14:38:34 node-4 kernel: [    3.207470] 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 22 14:38:34 node-4 kernel: [    3.207527] 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 22 14:38:34 node-4 kernel: [    3.207580] 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 22 14:38:34 node-4 kernel: [    3.214597] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 22 14:38:34 node-4 kernel: [    3.216483] scsi0 : LSI SAS based MegaRAID driver
Jul 22 14:38:34 node-4 kernel: [    3.224956] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 22 14:38:34 node-4 kernel: [    3.295121] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 22 14:38:34 node-4 kernel: [    3.310918] md: raid6 personality registered for level 6
Jul 22 14:38:34 node-4 kernel: [    3.318256] md: raid5 personality registered for level 5
Jul 22 14:38:34 node-4 kernel: [    3.325398] md: raid4 personality registered for level 4
Jul 22 14:38:34 node-4 kernel: [    3.327782] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 22 14:38:34 node-4 kernel: [    3.328534] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 22 14:38:34 node-4 kernel: [    3.329541] sd 0:2:0:0: [sda] Write Protect is off
Jul 22 14:38:34 node-4 kernel: [    3.329583] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 22 14:38:34 node-4 kernel: [    3.329928] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 22 14:38:34 node-4 kernel: [    3.364106]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 22 14:38:34 node-4 kernel: [    3.370045] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 22 14:38:34 node-4 kernel: [    3.387790] md: raid10 personality registered for level 10
Jul 22 14:38:34 node-4 kernel: [    3.442169] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Jul 22 14:38:34 node-4 kernel: [    3.501214] random: lvm urandom read with 26 bits of entropy available
Jul 22 14:38:34 node-4 kernel: [    3.631533] bio: create slab <bio-1> at 1
Jul 22 14:38:34 node-4 kernel: [    4.465160] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 14:38:34 node-4 kernel: [    5.187396] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 22 14:38:34 node-4 kernel: [    5.217612] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 22 14:38:34 node-4 kernel: [    5.271260] random: nonblocking pool is initialized
Jul 22 14:38:34 node-4 kernel: [    5.339256] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 22 14:38:34 node-4 kernel: [    5.375136] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 22 14:38:34 node-4 kernel: [    5.474910] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 14:38:34 node-4 kernel: [    5.643192] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 22 14:38:34 node-4 kernel: [    5.688214] XFS (dm-1): Mounting Filesystem
Jul 22 14:38:34 node-4 kernel: [    5.853414] XFS (dm-1): Ending clean mount
Jul 22 14:38:34 node-4 kernel: [    5.905960] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 14:38:34 node-4 kernel: [    5.955906] XFS (dm-2): Mounting Filesystem
Jul 22 14:38:34 node-4 kernel: [    6.082712] XFS (dm-2): Ending clean mount
Jul 22 14:38:34 node-4 kernel: [    6.220845] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 22 14:38:34 node-4 kernel: [    7.909495] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 22 14:38:34 node-4 kernel: [    7.923450] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 22 14:38:34 node-4 kernel: [    8.073285] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 22 14:38:34 node-4 kernel: [    8.073290] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 22 14:38:34 node-4 kernel: [    8.073294] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 22 14:38:34 node-4 kernel: [    8.073299] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 22 14:38:34 node-4 kernel: [    8.107947] systemd-udevd[801]: starting version 204
Jul 22 14:38:34 node-4 kernel: [    8.259938] power_meter ACPI000D:00: Found ACPI power meter.
Jul 22 14:38:34 node-4 kernel: [    8.259951] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 22 14:38:34 node-4 kernel: [    8.271448] wmi: Mapper loaded
Jul 22 14:38:34 node-4 kernel: [    8.303589] IPMI System Interface driver.
Jul 22 14:38:34 node-4 kernel: [    8.303629] ipmi_si: probing via ACPI
Jul 22 14:38:34 node-4 kernel: [    8.303642] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 22 14:38:34 node-4 kernel: [    8.303643] ipmi_si: Adding ACPI-specified kcs state machine
Jul 22 14:38:34 node-4 kernel: [    8.303652] ipmi_si: probing via SMBIOS
Jul 22 14:38:34 node-4 kernel: [    8.303653] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 22 14:38:34 node-4 kernel: [    8.303654] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 22 14:38:34 node-4 kernel: [    8.303657] ipmi_si: probing via SPMI
Jul 22 14:38:34 node-4 kernel: [    8.303658] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 22 14:38:34 node-4 kernel: [    8.303658] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 22 14:38:34 node-4 kernel: [    8.303659] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 22 14:38:34 node-4 kernel: [    8.327478] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 22 14:38:34 node-4 kernel: [    8.327484] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 22 14:38:34 node-4 kernel: [    8.327487] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 22 14:38:34 node-4 kernel: [    8.327490] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 22 14:38:34 node-4 kernel: [    8.327562] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 22 14:38:34 node-4 kernel: [    8.334812] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 22 14:38:34 node-4 kernel: [    8.402420] systemd-udevd[821]: renamed network interface eth1 to enp7s0
Jul 22 14:38:34 node-4 kernel: [    8.434283] systemd-udevd[842]: renamed network interface eth0 to enp6s0
Jul 22 14:38:34 node-4 kernel: [    8.437920] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 22 14:38:34 node-4 kernel: [    8.437928] ipmi_si 00:09: IPMI kcs interface initialized
Jul 22 14:38:34 node-4 kernel: [    8.454284] systemd-udevd[848]: renamed network interface eth2 to enp8s0
Jul 22 14:38:34 node-4 kernel: [    8.474261] systemd-udevd[832]: renamed network interface eth3 to enp9s0
Jul 22 14:38:34 node-4 kernel: [    8.770291] type=1400 audit(1469198285.810:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1075 comm="apparmor_parser"
Jul 22 14:38:34 node-4 kernel: [    8.770449] type=1400 audit(1469198285.810:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1075 comm="apparmor_parser"
Jul 22 14:38:34 node-4 kernel: [    8.770575] type=1400 audit(1469198285.810:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1075 comm="apparmor_parser"
Jul 22 14:38:34 node-4 kernel: [    8.772870] type=1400 audit(1469198285.810:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1076 comm="apparmor_parser"
Jul 22 14:38:34 node-4 kernel: [    8.773014] type=1400 audit(1469198285.810:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1076 comm="apparmor_parser"
Jul 22 14:38:34 node-4 kernel: [    8.773135] type=1400 audit(1469198285.810:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1076 comm="apparmor_parser"
Jul 22 14:38:34 node-4 kernel: [    8.781159] type=1400 audit(1469198285.818:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1080 comm="apparmor_parser"
Jul 22 14:38:34 node-4 kernel: [    8.781315] type=1400 audit(1469198285.818:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1080 comm="apparmor_parser"
Jul 22 14:38:34 node-4 kernel: [    8.781434] type=1400 audit(1469198285.818:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1080 comm="apparmor_parser"
Jul 22 14:38:34 node-4 kernel: [    8.785960] type=1400 audit(1469198285.826:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1074 comm="apparmor_parser"
Jul 22 14:38:34 node-4 kernel: [    9.335915] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 22 14:38:34 node-4 kernel: [    9.336829] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 22 14:38:34 node-4 kernel: [    9.506200] enic 0000:06:00.0 enp6s0: Link UP
Jul 22 14:38:34 node-4 kernel: [    9.506724] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 22 14:38:34 node-4 kernel: [    9.506734] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 22 14:38:34 node-4 kernel: [   20.127117] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 22 14:38:35 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 22 14:38:35 node-4 kernel: [   38.520918] init: failsafe main process (8440) killed by TERM signal
Jul 22 14:38:36 node-4 dbus[8479]: [system] AppArmor D-Bus mediation is enabled
Jul 22 14:38:36 node-4 kernel: [   38.851384] audit_printk_skb: 30 callbacks suppressed
Jul 22 14:38:36 node-4 kernel: [   38.851385] type=1400 audit(1469198316.260:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8568 comm="apparmor_parser"
Jul 22 14:38:36 node-4 kernel: [   38.851653] type=1400 audit(1469198316.260:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8567 comm="apparmor_parser"
Jul 22 14:38:36 node-4 kernel: [   38.851657] type=1400 audit(1469198316.260:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8567 comm="apparmor_parser"
Jul 22 14:38:36 node-4 kernel: [   38.851659] type=1400 audit(1469198316.260:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8567 comm="apparmor_parser"
Jul 22 14:38:36 node-4 kernel: [   38.851875] type=1400 audit(1469198316.260:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8567 comm="apparmor_parser"
Jul 22 14:38:36 node-4 kernel: [   38.851877] type=1400 audit(1469198316.260:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8567 comm="apparmor_parser"
Jul 22 14:38:36 node-4 kernel: [   38.851989] type=1400 audit(1469198316.260:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8567 comm="apparmor_parser"
Jul 22 14:38:36 node-4 kernel: [   38.943237] type=1400 audit(1469198316.352:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8570 comm="apparmor_parser"
Jul 22 14:38:36 node-4 anacron[8633]: Anacron 2.3 started on 2016-07-22
Jul 22 14:38:36 node-4 anacron[8633]: Will run job `cron.daily' in 5 min.
Jul 22 14:38:36 node-4 anacron[8633]: Will run job `cron.weekly' in 10 min.
Jul 22 14:38:36 node-4 anacron[8633]: Will run job `cron.monthly' in 15 min.
Jul 22 14:38:36 node-4 anacron[8633]: Jobs will be executed sequentially
Jul 22 14:38:36 node-4 cron[8598]: (CRON) INFO (pidfile fd = 3)
Jul 22 14:38:36 node-4 cron[8642]: (CRON) STARTUP (fork ok)
Jul 22 14:38:36 node-4 multipathd: path checkers start up
Jul 22 14:38:36 node-4 cron[8642]: (CRON) INFO (Running @reboot jobs)
Jul 22 14:38:37 node-4 postfix/master[8777]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 22 14:38:40 node-4 puppet-agent[8961]: Reopening log files
Jul 22 14:38:41 node-4 puppet-agent[8961]: Could not request certificate: Connection refused - connect(2)
Jul 22 14:38:53 node-4 puppet-user[9169]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 22 14:38:53 node-4 puppet-user[9169]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 22 14:38:53 node-4 puppet-user[9169]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 22 14:38:53 node-4 puppet-user[9169]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 22 14:38:53 node-4 puppet-user[9169]: Finished catalog run in 0.43 seconds
Jul 22 14:38:55 node-4 multipathd: uevent trigger error
Jul 22 14:38:55 node-4 puppet-user[9584]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 22 14:38:55 node-4 puppet-user[9584]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Jul 22 14:38:55 node-4 puppet-user[9584]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 22 14:38:55 node-4 puppet-user[9584]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 22 14:38:55 node-4 puppet-user[9584]: (/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 22 14:38:55 node-4 puppet-user[9584]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 22 14:38:55 node-4 puppet-user[9584]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 22 14:38:55 node-4 puppet-user[9584]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 22 14:38:55 node-4 puppet-user[9584]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 22 14:38:55 node-4 puppet-user[9584]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 22 14:38:55 node-4 puppet-user[9584]: Finished catalog run in 0.05 seconds
Jul 22 14:38:56 node-4 puppet-user[10043]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 22 14:38:56 node-4 puppet-user[10043]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Jul 22 14:38:56 node-4 puppet-user[10043]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 22 14:38:56 node-4 puppet-user[10043]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 22 14:38:56 node-4 puppet-user[10043]: Finished catalog run in 0.04 seconds
Jul 22 14:38:58 node-4 puppet-user[10503]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 22 14:38:58 node-4 puppet-user[10503]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 22 14:38:58 node-4 puppet-user[10503]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 22 14:38:58 node-4 puppet-user[10503]: Finished catalog run in 0.03 seconds
Jul 22 14:38:59 node-4 puppet-user[10952]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 22 14:38:59 node-4 puppet-user[10952]: Compiled catalog for node-4.domain.tld in environment production in 0.18 seconds
Jul 22 14:38:59 node-4 puppet-user[10952]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 22 14:39:00 node-4 puppet-user[10952]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/fuel-plugin-ovs-0.9/]/Exec[rsync /etc/fuel/plugins/fuel-plugin-ovs-0.9/]/returns) executed successfully
Jul 22 14:39:00 node-4 puppet-user[10952]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/opendaylight-0.9/]/Exec[rsync /etc/fuel/plugins/opendaylight-0.9/]/returns) executed successfully
Jul 22 14:39:00 node-4 puppet-user[10952]: Finished catalog run in 0.81 seconds
Jul 22 14:39:01 node-4 CRON[11681]: (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 22 14:39:01 node-4 puppet-user[11456]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 22 14:39:02 node-4 puppet-user[11456]: Compiled catalog for node-4.domain.tld in environment production in 0.21 seconds
Jul 22 14:39:02 node-4 puppet-user[11456]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[fuel-plugin-ovs-0.9.0]/Apt::Setting[list-fuel-plugin-ovs-0.9.0]/File[/etc/apt/sources.list.d/fuel-plugin-ovs-0.9.0.list]/ensure) created
Jul 22 14:39:02 node-4 puppet-user[11456]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 22 14:39:02 node-4 puppet-user[11456]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 22 14:39:02 node-4 puppet-user[11456]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[opendaylight-0.9.0]/Apt::Setting[list-opendaylight-0.9.0]/File[/etc/apt/sources.list.d/opendaylight-0.9.0.list]/ensure) created
Jul 22 14:39:02 node-4 puppet-user[11456]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 22 14:39:02 node-4 puppet-user[11456]: Finished catalog run in 0.31 seconds
Jul 22 14:39:03 node-4 puppet-user[12124]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 22 14:39:03 node-4 puppet-user[12124]: Compiled catalog for node-4.domain.tld in environment production in 0.14 seconds
Jul 22 14:39:04 node-4 puppet-user[12124]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 22 14:39:04 node-4 kernel: [   66.668773] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 22 14:39:04 node-4 kernel: [   66.668831] 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 22 14:39:04 node-4 puppet-user[12124]: (/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 22 14:39:04 node-4 puppet-user[12124]: Finished catalog run in 0.05 seconds
Jul 22 14:39:05 node-4 puppet-user[12583]: (Scope(Class[main])) MODULAR: sync_time
Jul 22 14:39:05 node-4 puppet-user[12583]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 22 14:39:05 node-4 ntpdate[12996]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 22 14:39:11 node-4 ntpdate[12996]: adjust time server 10.20.0.2 offset -0.005861 sec
Jul 22 14:39:11 node-4 puppet-user[12583]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 22 14:39:11 node-4 puppet-user[12583]: Finished catalog run in 6.17 seconds
Jul 22 14:39:14 node-4 kernel: [   77.333443] init: plymouth-upstart-bridge main process ended, respawning
Jul 22 14:39:14 node-4 puppet-agent[8961]: Could not run: SIGTERM
Jul 22 14:39:15 node-4 kernel: [   77.611689] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 22 14:39:15 node-4 ec2: 
Jul 22 14:39:15 node-4 ec2: #############################################################
Jul 22 14:39:15 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 22 14:39:15 node-4 ec2: 1024 61:14:40:59:93:fc:b3:47:2c:b1:0e:14:34:ee:de:5d  root@node-4.domain.tld (DSA)
Jul 22 14:39:15 node-4 ec2: 256 26:4f:95:2a:f8:d8:85:06:cf:a2:40:89:34:ed:c2:bf  root@node-4.domain.tld (ECDSA)
Jul 22 14:39:15 node-4 ec2: 256 53:eb:d7:18:5c:82:e9:18:b6:e0:7b:3c:de:69:db:6a  root@node-4.domain.tld (ED25519)
Jul 22 14:39:15 node-4 ec2: 2048 03:19:21:62:15:59:70:b5:31:c4:89:4e:e8:12:5c:5f  root@node-4.domain.tld (RSA)
Jul 22 14:39:15 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 22 14:39:15 node-4 ec2: #############################################################
Jul 22 14:39:28 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 14:39:28 node-4 nailgun-agent: D, [2016-07-22T14:39:01.732554 #11684] DEBUG -- : Sleep for 27 seconds before sending request
Jul 22 14:39:28 node-4 nailgun-agent: I, [2016-07-22T14:39:28.743150 #11684]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 22 14:39:29 node-4 nailgun-agent: D, [2016-07-22T14:39:29.155863 #11684] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.333525 #11684] DEBUG -- : Trying to find block devices
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.333726 #11684] DEBUG -- : Found block device: sda
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.333880 #11684] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.333939 #11684] DEBUG -- : Trying to get list of physical devices
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.334317 #11684] DEBUG -- : Getting udev properties for device: sda
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.338280 #11684] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0 /dev/disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"00c001b0054d88c71c90a8737283728e", "ID_SERIAL"=>"3618e72837273a8901cc7884d05b001c0", "ID_SERIAL_SHORT"=>"618e72837273a8901cc7884d05b001c0", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a890", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7884d05b001c0", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a8901cc788
Jul 22 14:39:41 node-4 nailgun-agent: 4d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"25524", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.338427 #11684] DEBUG -- : Trying to find out if device sda is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.338529 #11684] DEBUG -- : Device sda removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.338566 #11684] DEBUG -- : Device sda seems to be appropriate
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.339738 #11684] DEBUG -- : Getting udev properties for device: dm-0
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.343346 #11684] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-mZmNNVpLZdYH5LoosNjeGG01m0uMbBwZvhrLbKpmyLkYij5Fwzn6ga4D1XdFcPx8 /dev/disk/by-uuid/4ca0dee0-e05c-4dac-ae54-3566dafca863 /dev/mapper/mongo-mongodb /dev/mongo/mongodb", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"mongodb", "DM_NAME"=>"mongo-mongodb", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-mZmNNVpLZdYH5LoosNjeGG01m0uMbBwZvhrLbKpmyLkYij5Fwzn6ga4D1XdFcPx8", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"4ca0dee0-e05c-4dac-ae54-3566dafca863", "ID_FS_UUID_ENC"=>"4ca0dee0-e05c-4dac-ae54-3566dafca863", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"8
Jul 22 14:39:41 node-4 nailgun-agent: 9478", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.343414 #11684] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.343492 #11684] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.343530 #11684] DEBUG -- : Device dm-0 seems to be appropriate
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.343572 #11684] DEBUG -- : Getting udev properties for device: dm-1
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.347228 #11684] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-kTclur9HxZL46l4b2ECdE9cyfR9YP9fKs76c7xeWOceVN5gmBasKQTcDTwMGX0SA /dev/disk/by-uuid/1b095a2a-a24e-4045-8a10-308202da2d29 /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-kTclur9HxZL46l4b2ECdE9cyfR9YP9fKs76c7xeWOceVN5gmBasKQTcDTwMGX0SA", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"1b095a2a-a24e-4045-8a10-308202da2d29", "ID_FS_UUID_ENC"=>"1b095a2a-a24e-4045-8a10-308202da2d29", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"23734", "nomdmonddf"=>"1", "nom
Jul 22 14:39:41 node-4 nailgun-agent: dmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.347289 #11684] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.347359 #11684] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.347433 #11684] DEBUG -- : Device dm-1 seems to be appropriate
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.347463 #11684] DEBUG -- : Getting udev properties for device: dm-2
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.350872 #11684] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-y7KWS5uBO49oA9lRgzwbmDQd3dfwVQTjRAVHBdmP1URuePs3B6D9qJZfDw1f6iRU /dev/disk/by-uuid/a509936a-35cf-4919-b2cd-44c00b930ab3 /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-y7KWS5uBO49oA9lRgzwbmDQd3dfwVQTjRAVHBdmP1URuePs3B6D9qJZfDw1f6iRU", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a509936a-35cf-4919-b2cd-44c00b930ab3", "ID_FS_UUID_ENC"=>"a509936a-35cf-4919-b2cd-44c00b930ab3", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4
Jul 22 14:39:41 node-4 nailgun-agent: 7486", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.350981 #11684] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.351048 #11684] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.351079 #11684] DEBUG -- : Device dm-2 seems to be appropriate
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.351111 #11684] DEBUG -- : Getting udev properties for device: dm-3
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.354326 #11684] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-3kDt1wyYII3PZCGYQJbH7vHpga6KQmK4PsiIOepJe4YkY1xBke9rArTdud6Oq45Q /dev/disk/by-uuid/592fd124-ce69-44d4-972f-5bff653413aa /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-3kDt1wyYII3PZCGYQJbH7vHpga6KQmK4PsiIOepJe4YkY1xBke9rArTdud6Oq45Q", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"592fd124-ce69-44d4-972f-5bff653413aa", "ID_FS_UUID_ENC"=>"592fd124-ce69-44d4-972f-5bff653413aa", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"52305", "nomdmon
Jul 22 14:39:41 node-4 nailgun-agent: ddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.354417 #11684] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.354489 #11684] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.354519 #11684] DEBUG -- : Device dm-3 seems to be appropriate
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.354552 #11684] DEBUG -- : Getting udev properties for device: dm-4
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.358025 #11684] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-huaKFJnoKQ6uf6T23T2tjwH8p3NR5Mr6l49SseDWnybFv3f3zWYry1tjJnZAdvUc /dev/disk/by-uuid/00ce2239-0f1b-4321-bd8f-ba03c7ada56f /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-huaKFJnoKQ6uf6T23T2tjwH8p3NR5Mr6l49SseDWnybFv3f3zWYry1tjJnZAdvUc", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"00ce2239-0f1b-4321-bd8f-ba03c7ada56f", "ID_FS_UUID_ENC"=>"00ce2239-0f1b-4321-bd8f-ba03c7ada56f", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58667", "nomdmonddf"=>"1",
Jul 22 14:39:41 node-4 nailgun-agent:  "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.358086 #11684] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.358186 #11684] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.358217 #11684] DEBUG -- : Device dm-4 seems to be appropriate
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.358262 #11684] DEBUG -- : Getting udev properties for device: dm-5
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.361700 #11684] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-v5mSkG9UjszJdq9xmFzyq3goDn7aGI4khCpoVQeC73VQMnGEJxxERctPNC1ahst3 /dev/disk/by-uuid/b6d1ec0a-fcc0-4452-9de1-5fd577d3154f /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-v5mSkG9UjszJdq9xmFzyq3goDn7aGI4khCpoVQeC73VQMnGEJxxERctPNC1ahst3", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b6d1ec0a-fcc0-4452-9de1-5fd577d3154f", "ID_FS_UUID_ENC"=>"b6d1ec0a-fcc0-4452-9de1-5fd577d3154f", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63414", "nomdmonddf"=>"1", "nom
Jul 22 14:39:41 node-4 nailgun-agent: dmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.361759 #11684] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.361872 #11684] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.361905 #11684] DEBUG -- : Device dm-5 seems to be appropriate
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.361970 #11684] DEBUG -- : Getting udev properties for device: dm-6
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.365328 #11684] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-v5mSkG9UjszJdq9xmFzyq3goDn7aGI4k7wjR6Md25GTSYevh5jJqgPB1Tc6IGBCG /dev/disk/by-uuid/407500ca-2bdb-49f5-a1dd-8200b6b08cce /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-6", "DEVPATH"=>"/devices/virtual/block/dm-6", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-v5mSkG9UjszJdq9xmFzyq3goDn7aGI4k7wjR6Md25GTSYevh5jJqgPB1Tc6IGBCG", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"407500ca-2bdb-49f5-a1dd-8200b6b08cce", "ID_FS_UUID_ENC"=>"407500ca-2bdb-49f5-a1dd-8200b6b08cce", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63793", "nomdmonddf"=>"1", "nomdmonisw
Jul 22 14:39:41 node-4 nailgun-agent: "=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.365392 #11684] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.365460 #11684] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.365489 #11684] DEBUG -- : Device dm-6 seems to be appropriate
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.365522 #11684] DEBUG -- : Getting udev properties for device: ram0
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.368688 #11684] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97313", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.368745 #11684] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.368876 #11684] DEBUG -- : Device ram0 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.368919 #11684] DEBUG -- : Getting udev properties for device: ram1
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.372067 #11684] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97473", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.372140 #11684] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.372229 #11684] DEBUG -- : Device ram1 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.372329 #11684] DEBUG -- : Getting udev properties for device: ram2
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.375461 #11684] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98179", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.375523 #11684] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.375604 #11684] DEBUG -- : Device ram2 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.375691 #11684] DEBUG -- : Getting udev properties for device: ram3
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.378967 #11684] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98302", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.379032 #11684] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.379188 #11684] DEBUG -- : Device ram3 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.379240 #11684] DEBUG -- : Getting udev properties for device: ram4
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.382245 #11684] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98405", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.382319 #11684] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.382434 #11684] DEBUG -- : Device ram4 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.382494 #11684] DEBUG -- : Getting udev properties for device: ram5
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.385675 #11684] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98533", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.385751 #11684] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.385826 #11684] DEBUG -- : Device ram5 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.385875 #11684] DEBUG -- : Getting udev properties for device: ram6
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.389939 #11684] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98597", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.390028 #11684] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.390109 #11684] DEBUG -- : Device ram6 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.390197 #11684] DEBUG -- : Getting udev properties for device: ram7
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.393243 #11684] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98692", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.393323 #11684] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.393422 #11684] DEBUG -- : Device ram7 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.393467 #11684] DEBUG -- : Getting udev properties for device: ram8
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.396777 #11684] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98790", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.396899 #11684] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.396977 #11684] DEBUG -- : Device ram8 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.397052 #11684] DEBUG -- : Getting udev properties for device: ram9
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.400324 #11684] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98889", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.400388 #11684] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.400503 #11684] DEBUG -- : Device ram9 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.400579 #11684] DEBUG -- : Getting udev properties for device: loop0
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.403615 #11684] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96518", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.403766 #11684] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.403896 #11684] DEBUG -- : Device loop0 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.403946 #11684] DEBUG -- : Getting udev properties for device: loop1
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.407078 #11684] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96621", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.407144 #11684] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.407267 #11684] DEBUG -- : Device loop1 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.407340 #11684] DEBUG -- : Getting udev properties for device: loop2
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.410621 #11684] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96725", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.410692 #11684] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.410788 #11684] DEBUG -- : Device loop2 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.410930 #11684] DEBUG -- : Getting udev properties for device: loop3
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.414122 #11684] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96805", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.414197 #11684] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.414367 #11684] DEBUG -- : Device loop3 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.414423 #11684] DEBUG -- : Getting udev properties for device: loop4
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.417546 #11684] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96914", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.417620 #11684] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.417738 #11684] DEBUG -- : Device loop4 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.417793 #11684] DEBUG -- : Getting udev properties for device: loop5
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.420875 #11684] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"96992", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.428255 #11684] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.428342 #11684] DEBUG -- : Device loop5 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.428381 #11684] DEBUG -- : Getting udev properties for device: loop6
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.431345 #11684] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97076", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.431380 #11684] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.431487 #11684] DEBUG -- : Device loop6 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.431514 #11684] DEBUG -- : Getting udev properties for device: loop7
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.434792 #11684] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97176", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.434849 #11684] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.434957 #11684] DEBUG -- : Device loop7 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.434988 #11684] DEBUG -- : Getting udev properties for device: ram10
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.438128 #11684] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97547", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.438170 #11684] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.438221 #11684] DEBUG -- : Device ram10 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.438296 #11684] DEBUG -- : Getting udev properties for device: ram11
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.441546 #11684] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97655", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.441590 #11684] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.441640 #11684] DEBUG -- : Device ram11 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.441672 #11684] DEBUG -- : Getting udev properties for device: ram12
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.445048 #11684] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97761", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.445124 #11684] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.445221 #11684] DEBUG -- : Device ram12 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.445275 #11684] DEBUG -- : Getting udev properties for device: ram13
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.448593 #11684] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97885", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.448664 #11684] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.448800 #11684] DEBUG -- : Device ram13 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.448859 #11684] DEBUG -- : Getting udev properties for device: ram14
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.451893 #11684] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"97995", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.451966 #11684] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.452079 #11684] DEBUG -- : Device ram14 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.452132 #11684] DEBUG -- : Getting udev properties for device: ram15
Jul 22 14:39:41 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455153 #11684] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"98094", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455205 #11684] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455295 #11684] DEBUG -- : Device ram15 removable parameter: "0"
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455375 #11684] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0"}]
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455410 #11684] DEBUG -- : Block device seems to be physical data storage: sda
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455610 #11684] DEBUG -- : Found block device: dm-0
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455646 #11684] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455678 #11684] DEBUG -- : Found block device: dm-1
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455703 #11684] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455725 #11684] DEBUG -- : Found block device: dm-2
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455751 #11684] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455774 #11684] DEBUG -- : Found block device: dm-3
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455799 #11684] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455920 #11684] DEBUG -- : Found block device: dm-4
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455946 #11684] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455968 #11684] DEBUG -- : Found block device: dm-5
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.455993 #11684] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456015 #11684] DEBUG -- : Found block device: dm-6
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456039 #11684] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456060 #11684] DEBUG -- : Found block device: ram0
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456083 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456216 #11684] DEBUG -- : Found block device: ram1
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456243 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456264 #11684] DEBUG -- : Found block device: ram2
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456289 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456311 #11684] DEBUG -- : Found block device: ram3
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456335 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456355 #11684] DEBUG -- : Found block device: ram4
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456383 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456404 #11684] DEBUG -- : Found block device: ram5
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456500 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456522 #11684] DEBUG -- : Found block device: ram6
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456546 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456568 #11684] DEBUG -- : Found block device: ram7
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456592 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456612 #11684] DEBUG -- : Found block device: ram8
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456635 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456656 #11684] DEBUG -- : Found block device: ram9
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456679 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456765 #11684] DEBUG -- : Found block device: loop0
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456790 #11684] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456811 #11684] DEBUG -- : Found block device: loop1
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456835 #11684] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456857 #11684] DEBUG -- : Found block device: loop2
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456881 #11684] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456901 #11684] DEBUG -- : Found block device: loop3
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456923 #11684] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456944 #11684] DEBUG -- : Found block device: loop4
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.456968 #11684] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457039 #11684] DEBUG -- : Found block device: loop5
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457064 #11684] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457086 #11684] DEBUG -- : Found block device: loop6
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457110 #11684] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457130 #11684] DEBUG -- : Found block device: loop7
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457155 #11684] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457177 #11684] DEBUG -- : Found block device: ram10
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457201 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457221 #11684] DEBUG -- : Found block device: ram11
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457242 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457323 #11684] DEBUG -- : Found block device: ram12
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457346 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457366 #11684] DEBUG -- : Found block device: ram13
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457389 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457410 #11684] DEBUG -- : Found block device: ram14
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457436 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457456 #11684] DEBUG -- : Found block device: ram15
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457479 #11684] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.457544 #11684] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a8901cc7884d05b001c0", "disk/by-id/scsi-3618e72837273a8901cc7884d05b001c0"], :removable=>"0", :paths=>nil}]
Jul 22 14:39:41 node-4 nailgun-agent: D, [2016-07-22T14:39:41.795673 #11684] DEBUG -- : Response: status: 200 body: {"id": 4}
Jul 22 14:39:41 node-4 nailgun-agent: I, [2016-07-22T14:39:41.796061 #11684]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 22 14:39:59 node-4 puppet-user[13675]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 22 14:39:59 node-4 puppet-user[13675]: Compiled catalog for node-4.domain.tld in environment production in 0.12 seconds
Jul 22 14:40:00 node-4 puppet-user[13675]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 22 14:40:00 node-4 puppet-user[13675]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 22 14:40:00 node-4 puppet-user[13675]: Finished catalog run in 0.08 seconds
Jul 22 14:40:01 node-4 CRON[14539]: (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 22 14:40:01 node-4 puppet-user[14125]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 22 14:40:02 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 14:40:02 node-4 nailgun-agent: I, [2016-07-22T14:40:02.990619 #14542]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 22 14:40:03 node-4 puppet-user[14125]: Compiled catalog for node-4.domain.tld in environment production in 1.38 seconds
Jul 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:03 node-4 puppet-user[14125]: (/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 22 14:40:15 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 14:40:15 node-4 nailgun-agent: I, [2016-07-22T14:40:15.941176 #14542]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 22 14:40:21 node-4 puppet-user[14125]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 22 14:40:21 node-4 puppet-user[14125]: Finished catalog run in 18.22 seconds
Jul 22 14:40:23 node-4 puppet-user[15364]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 22 14:40:23 node-4 puppet-user[15364]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Jul 22 14:40:28 node-4 puppet-user[15364]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 22 14:41:01 node-4 CRON[17789]: (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 22 14:41:04 node-4 puppet-user[15364]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 22 14:41:04 node-4 puppet-user[15364]: Finished catalog run in 40.59 seconds
Jul 22 14:41:06 node-4 puppet-user[17915]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 22 14:41:06 node-4 puppet-user[17915]: Compiled catalog for node-4.domain.tld in environment production in 0.64 seconds
Jul 22 14:41:07 node-4 puppet-user[17915]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 22 14:41:07 node-4 puppet-user[17915]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 22 14:41:07 node-4 puppet-user[17915]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 22 14:41:07 node-4 puppet-user[17915]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 22 14:41:07 node-4 puppet-user[17915]: Finished catalog run in 0.10 seconds
Jul 22 14:41:08 node-4 puppet-user[18369]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 22 14:41:09 node-4 puppet-user[18369]: Compiled catalog for node-4.domain.tld in environment production in 0.94 seconds
Jul 22 14:41:10 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 22 14:41:10 node-4 nailgun-agent: I, [2016-07-22T14:41:10.119231 #17792]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 22 14:41:10 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 22 14:41:10 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 22 14:41:10 node-4 crontab[18856]: (root) LIST (root)
Jul 22 14:41:10 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 22 14:41:10 node-4 crontab[18869]: (root) REPLACE (root)
Jul 22 14:41:12 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 22 14:41:13 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/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 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 22 14:41:14 node-4 puppet-user[18369]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 22 14:41:15 node-4 puppet-user[18369]: (/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 22 14:41:15 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8413" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 22 14:41:15 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 22 14:41:17 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:17 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:17 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:17 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:17 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:35 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:35 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:35 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:39 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:39 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:39 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:39 node-4 multipathd: uevent trigger error
<27>Jul 22 14:41:39 node-4 multipathd: uevent trigger error
<27>Jul 22 14:42:40 node-4 ntpdate[29727]: no servers can be used, exiting
<27>Jul 22 14:42:40 node-4 ntpdate[29987]: no servers can be used, exiting
<27>Jul 22 14:43:11 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:12 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:12 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:12 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:12 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:43:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:44:19 node-4 multipathd: uevent trigger error
<27>Jul 22 14:44:19 node-4 multipathd: uevent trigger error
<27>Jul 22 14:44:20 node-4 multipathd: uevent trigger error
<27>Jul 22 14:44:20 node-4 multipathd: uevent trigger error
<27>Jul 22 14:44:20 node-4 multipathd: uevent trigger error
<43>Jul 22 14:44:35 node-4 apache2_error [Fri Jul 22 14:44:33.258350 2016] [mpm_event:notice] [pid 10972:tid 140162297857920] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 22 14:44:35 node-4 apache2_error [Fri Jul 22 14:44:33.258487 2016] [core:notice] [pid 10972:tid 140162297857920] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 14:44:41 node-4 multipathd: uevent trigger error
<27>Jul 22 14:44:41 node-4 multipathd: uevent trigger error
<27>Jul 22 14:44:41 node-4 multipathd: uevent trigger error
<27>Jul 22 14:44:41 node-4 multipathd: uevent trigger error
<27>Jul 22 14:44:41 node-4 multipathd: uevent trigger error
<43>Jul 22 14:44:45 node-4 apache2_error [Fri Jul 22 14:44:36.451642 2016] [mpm_event:notice] [pid 10972:tid 140162297857920] AH00491: caught SIGTERM, shutting down
<43>Jul 22 14:44:45 node-4 apache2_error [Fri Jul 22 14:44:37.540966 2016] [mpm_worker:notice] [pid 11279:tid 140641749792640] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 22 14:44:45 node-4 apache2_error [Fri Jul 22 14:44:37.541014 2016] [core:notice] [pid 11279:tid 140641749792640] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 14:45:23 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 22 14:45:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:37 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:37 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:37 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:37 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:37 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:40 node-4 ntpdate[20281]: the NTP socket is in use, exiting
<27>Jul 22 14:45:45 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:45 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:45 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:45 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:45 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:45 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:50 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:50 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:50 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:50 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:50 node-4 multipathd: uevent trigger error
<129>Jul 22 14:45:50 node-4 haproxy[22070]: Server odl-jetty/node-3 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 14:45:50 node-4 haproxy[22070]: proxy odl-jetty has no server available!
<129>Jul 22 14:45:52 node-4 haproxy[22070]: Server odl-neutron-endpoint/node-3 is DOWN, reason: Layer4 timeout, check duration: 5002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 14:45:52 node-4 haproxy[22070]: proxy odl-neutron-endpoint has no server available!
<129>Jul 22 14:45:53 node-4 haproxy[23255]: 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 22 14:45:55 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:55 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:55 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:55 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:55 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:55 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:55 node-4 multipathd: uevent trigger error
<129>Jul 22 14:45:56 node-4 haproxy[23259]: Server odl-jetty/node-3 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 14:45:56 node-4 haproxy[23259]: proxy odl-jetty has no server available!
<27>Jul 22 14:45:59 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:59 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:59 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:59 node-4 multipathd: uevent trigger error
<27>Jul 22 14:45:59 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:01 node-4 haproxy[23259]: Server odl-neutron-endpoint/node-3 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 14:46:01 node-4 haproxy[23259]: proxy odl-neutron-endpoint has no server available!
<129>Jul 22 14:46:02 node-4 haproxy[25529]: 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 22 14:46:03 node-4 haproxy[25529]: 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 22 14:46:04 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:04 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:04 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:04 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:04 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:04 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:05 node-4 haproxy[25529]: Server odl-jetty/node-3 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 22 14:46:05 node-4 haproxy[25529]: proxy odl-jetty has no server available!
<129>Jul 22 14:46:07 node-4 haproxy[26725]: 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 22 14:46:07 node-4 haproxy[26725]: 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 22 14:46:08 node-4 haproxy[26725]: 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 22 14:46:09 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:09 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:09 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:09 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:09 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:10 node-4 haproxy[26725]: Server odl-jetty/node-3 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 22 14:46:10 node-4 haproxy[26725]: proxy odl-jetty has no server available!
<129>Jul 22 14:46:12 node-4 haproxy[28054]: 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 22 14:46:12 node-4 haproxy[28054]: 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 22 14:46:13 node-4 haproxy[28063]: 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 22 14:46:13 node-4 haproxy[28063]: 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 22 14:46:13 node-4 haproxy[28063]: 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 22 14:46:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:15 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:15 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:16 node-4 haproxy[28063]: Server odl-jetty/node-3 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 22 14:46:16 node-4 haproxy[28063]: proxy odl-jetty has no server available!
<129>Jul 22 14:46:17 node-4 haproxy[29252]: 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 22 14:46:17 node-4 haproxy[29252]: 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 22 14:46:18 node-4 haproxy[29257]: 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 22 14:46:18 node-4 haproxy[29257]: 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 22 14:46:18 node-4 haproxy[29257]: 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 22 14:46:19 node-4 haproxy[29257]: 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 22 14:46:20 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:20 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:20 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:20 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:20 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:20 node-4 haproxy[29257]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:21 node-4 haproxy[29257]: Server aodh/node-3 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 22 14:46:21 node-4 haproxy[29257]: proxy aodh has no server available!
<129>Jul 22 14:46:21 node-4 haproxy[29257]: Server odl-jetty/node-3 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 22 14:46:21 node-4 haproxy[29257]: proxy odl-jetty has no server available!
<129>Jul 22 14:46:22 node-4 haproxy[30448]: 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 22 14:46:23 node-4 haproxy[30452]: 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 22 14:46:23 node-4 haproxy[30452]: 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 22 14:46:23 node-4 haproxy[30452]: 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 22 14:46:23 node-4 haproxy[30452]: 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 22 14:46:24 node-4 haproxy[30452]: 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 22 14:46:24 node-4 haproxy[30452]: 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 22 14:46:25 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:25 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:25 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:25 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:25 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:25 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:25 node-4 haproxy[30452]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:26 node-4 haproxy[30452]: Server aodh/node-3 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 22 14:46:26 node-4 haproxy[30452]: proxy aodh has no server available!
<129>Jul 22 14:46:26 node-4 haproxy[30452]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:26 node-4 haproxy[30452]: Server ceilometer/node-3 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 22 14:46:26 node-4 haproxy[30452]: proxy ceilometer has no server available!
<129>Jul 22 14:46:26 node-4 haproxy[30452]: Server odl-jetty/node-3 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 22 14:46:26 node-4 haproxy[30452]: proxy odl-jetty has no server available!
<129>Jul 22 14:46:28 node-4 haproxy[31809]: 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 22 14:46:28 node-4 haproxy[31809]: 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 22 14:46:28 node-4 haproxy[31809]: 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 22 14:46:28 node-4 haproxy[31809]: 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 22 14:46:29 node-4 haproxy[31809]: 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 22 14:46:29 node-4 haproxy[31809]: 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 22 14:46:29 node-4 haproxy[31809]: 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 22 14:46:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:30 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:30 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:31 node-4 haproxy[31809]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:31 node-4 haproxy[31809]: Server aodh/node-3 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 22 14:46:31 node-4 haproxy[31809]: proxy aodh has no server available!
<129>Jul 22 14:46:31 node-4 haproxy[31809]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:31 node-4 haproxy[31809]: Server ceilometer/node-3 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 22 14:46:31 node-4 haproxy[31809]: proxy ceilometer has no server available!
<129>Jul 22 14:46:31 node-4 haproxy[31809]: Server odl-jetty/node-3 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 22 14:46:31 node-4 haproxy[31809]: proxy odl-jetty has no server available!
<129>Jul 22 14:46:33 node-4 haproxy[568]: 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 22 14:46:33 node-4 haproxy[568]: 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 22 14:46:34 node-4 haproxy[572]: 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 22 14:46:34 node-4 haproxy[572]: 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 22 14:46:34 node-4 haproxy[572]: 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 22 14:46:34 node-4 haproxy[572]: 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 22 14:46:35 node-4 haproxy[572]: 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 22 14:46:35 node-4 haproxy[572]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:35 node-4 haproxy[572]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 22 14:46:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:36 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:36 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:36 node-4 haproxy[572]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:36 node-4 haproxy[572]: Server aodh/node-3 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 22 14:46:36 node-4 haproxy[572]: proxy aodh has no server available!
<129>Jul 22 14:46:36 node-4 haproxy[572]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:36 node-4 haproxy[572]: Server ceilometer/node-3 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 22 14:46:36 node-4 haproxy[572]: proxy ceilometer has no server available!
<129>Jul 22 14:46:37 node-4 haproxy[572]: Server odl-jetty/node-3 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 22 14:46:37 node-4 haproxy[572]: proxy odl-jetty has no server available!
<129>Jul 22 14:46:39 node-4 haproxy[1859]: 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 22 14:46:39 node-4 haproxy[1859]: 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 22 14:46:39 node-4 haproxy[1859]: 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 22 14:46:39 node-4 haproxy[1859]: 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 22 14:46:39 node-4 haproxy[1859]: 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 22 14:46:40 node-4 haproxy[1859]: 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 22 14:46:40 node-4 haproxy[1859]: 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 22 14:46:40 node-4 haproxy[1859]: 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 22 14:46:40 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 22 14:46:40 node-4 haproxy[1859]: 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 22 14:46:40 node-4 haproxy[1859]: 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 22 14:46:40 node-4 haproxy[1859]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:41 node-4 haproxy[1859]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:42 node-4 haproxy[1859]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 22 14:46:42 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:42 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:42 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:42 node-4 haproxy[1859]: Server glance-registry/node-3 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 22 14:46:42 node-4 haproxy[1859]: proxy glance-registry has no server available!
<27>Jul 22 14:46:42 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:42 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:42 node-4 haproxy[1859]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:42 node-4 haproxy[1859]: Server aodh/node-3 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 22 14:46:42 node-4 haproxy[1859]: proxy aodh has no server available!
<129>Jul 22 14:46:42 node-4 haproxy[1859]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:42 node-4 haproxy[1859]: Server ceilometer/node-3 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 22 14:46:42 node-4 haproxy[1859]: proxy ceilometer has no server available!
<129>Jul 22 14:46:42 node-4 haproxy[1859]: Server odl-jetty/node-3 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 22 14:46:42 node-4 haproxy[1859]: proxy odl-jetty has no server available!
<129>Jul 22 14:46:45 node-4 haproxy[3132]: 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 22 14:46:45 node-4 haproxy[3132]: 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 22 14:46:45 node-4 haproxy[3132]: 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 22 14:46:45 node-4 haproxy[3132]: 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 22 14:46:45 node-4 haproxy[3132]: 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 22 14:46:45 node-4 haproxy[3132]: 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 22 14:46:46 node-4 haproxy[3139]: 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 22 14:46:46 node-4 haproxy[3139]: 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 22 14:46:46 node-4 haproxy[3139]: 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 22 14:46:46 node-4 haproxy[3139]: 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 22 14:46:46 node-4 haproxy[3139]: 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 22 14:46:46 node-4 haproxy[3139]: 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 22 14:46:46 node-4 haproxy[3139]: 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 22 14:46:47 node-4 haproxy[3139]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:47 node-4 haproxy[3139]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 22 14:46:47 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:47 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:47 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:47 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:47 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:47 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:47 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:48 node-4 haproxy[3139]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:48 node-4 haproxy[3139]: Server glance-registry/node-3 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 22 14:46:48 node-4 haproxy[3139]: proxy glance-registry has no server available!
<129>Jul 22 14:46:48 node-4 haproxy[3139]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:48 node-4 haproxy[3139]: Server aodh/node-3 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 22 14:46:48 node-4 haproxy[3139]: proxy aodh has no server available!
<129>Jul 22 14:46:48 node-4 haproxy[3139]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:48 node-4 haproxy[3139]: Server ceilometer/node-3 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 22 14:46:48 node-4 haproxy[3139]: proxy ceilometer has no server available!
<129>Jul 22 14:46:48 node-4 haproxy[3139]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:48 node-4 haproxy[3139]: Server nova-novncproxy/node-3 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 22 14:46:48 node-4 haproxy[3139]: proxy nova-novncproxy has no server available!
<129>Jul 22 14:46:49 node-4 haproxy[3139]: Server odl-jetty/node-3 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 22 14:46:49 node-4 haproxy[3139]: proxy odl-jetty has no server available!
<129>Jul 22 14:46:50 node-4 haproxy[4346]: 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 22 14:46:50 node-4 haproxy[4346]: 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 22 14:46:50 node-4 haproxy[4346]: 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 22 14:46:50 node-4 haproxy[4346]: 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 22 14:46:51 node-4 haproxy[4350]: 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 22 14:46:51 node-4 haproxy[4350]: 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 22 14:46:51 node-4 haproxy[4350]: 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 22 14:46:51 node-4 haproxy[4350]: 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 22 14:46:51 node-4 haproxy[4350]: 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 22 14:46:51 node-4 haproxy[4350]: 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 22 14:46:51 node-4 haproxy[4350]: 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 22 14:46:51 node-4 haproxy[4350]: 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 22 14:46:52 node-4 haproxy[4350]: 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 22 14:46:52 node-4 haproxy[4350]: 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 22 14:46:52 node-4 haproxy[4350]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:52 node-4 haproxy[4350]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 22 14:46:53 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:53 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:53 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:53 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:53 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:53 node-4 haproxy[4350]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:53 node-4 haproxy[4350]: Server glance-registry/node-3 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 22 14:46:53 node-4 haproxy[4350]: proxy glance-registry has no server available!
<129>Jul 22 14:46:53 node-4 haproxy[4350]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:53 node-4 haproxy[4350]: Server aodh/node-3 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 22 14:46:53 node-4 haproxy[4350]: proxy aodh has no server available!
<129>Jul 22 14:46:53 node-4 haproxy[4350]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:53 node-4 haproxy[4350]: Server ceilometer/node-3 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 22 14:46:53 node-4 haproxy[4350]: proxy ceilometer has no server available!
<129>Jul 22 14:46:54 node-4 haproxy[4350]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:54 node-4 haproxy[4350]: Server nova-novncproxy/node-3 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 22 14:46:54 node-4 haproxy[4350]: proxy nova-novncproxy has no server available!
<129>Jul 22 14:46:54 node-4 haproxy[4350]: Server odl-jetty/node-3 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 22 14:46:54 node-4 haproxy[4350]: proxy odl-jetty has no server available!
<129>Jul 22 14:46:56 node-4 haproxy[5643]: 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 22 14:46:56 node-4 haproxy[5643]: 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 22 14:46:56 node-4 haproxy[5643]: 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 22 14:46:56 node-4 haproxy[5643]: 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 22 14:46:56 node-4 haproxy[5643]: 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 22 14:46:56 node-4 haproxy[5643]: 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 22 14:46:56 node-4 haproxy[5643]: 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 22 14:46:56 node-4 haproxy[5643]: 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 22 14:46:57 node-4 haproxy[5652]: 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 22 14:46:57 node-4 haproxy[5652]: 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 22 14:46:57 node-4 haproxy[5652]: 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 22 14:46:57 node-4 haproxy[5652]: 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 22 14:46:57 node-4 haproxy[5652]: 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 22 14:46:57 node-4 haproxy[5652]: 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 22 14:46:57 node-4 haproxy[5652]: 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 22 14:46:57 node-4 haproxy[5652]: 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 22 14:46:57 node-4 haproxy[5652]: 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 22 14:46:58 node-4 haproxy[5652]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:58 node-4 haproxy[5652]: Server horizon/node-3 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 22 14:46:58 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:58 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:58 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:58 node-4 multipathd: uevent trigger error
<27>Jul 22 14:46:58 node-4 multipathd: uevent trigger error
<129>Jul 22 14:46:58 node-4 haproxy[5652]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:59 node-4 haproxy[5652]: Server glance-registry/node-3 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 22 14:46:59 node-4 haproxy[5652]: proxy glance-registry has no server available!
<129>Jul 22 14:46:59 node-4 haproxy[5652]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:59 node-4 haproxy[5652]: Server aodh/node-3 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 22 14:46:59 node-4 haproxy[5652]: proxy aodh has no server available!
<129>Jul 22 14:46:59 node-4 haproxy[5652]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:59 node-4 haproxy[5652]: Server ceilometer/node-3 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 22 14:46:59 node-4 haproxy[5652]: proxy ceilometer has no server available!
<129>Jul 22 14:46:59 node-4 haproxy[5652]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:46:59 node-4 haproxy[5652]: Server nova-novncproxy/node-3 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 22 14:46:59 node-4 haproxy[5652]: proxy nova-novncproxy has no server available!
<129>Jul 22 14:46:59 node-4 haproxy[5652]: Server odl-jetty/node-3 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 22 14:46:59 node-4 haproxy[5652]: proxy odl-jetty has no server available!
<27>Jul 22 14:47:02 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:02 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:02 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:02 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:02 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:05 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:05 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:05 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:05 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:05 node-4 multipathd: uevent trigger error
<129>Jul 22 14:47:05 node-4 haproxy[5652]: Server odl-neutron-endpoint/node-3 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 22 14:47:05 node-4 haproxy[5652]: proxy odl-neutron-endpoint has no server available!
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server keystone-1/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server keystone-1/node-3 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 22 14:47:06 node-4 haproxy[5652]: proxy keystone-1 has no server available!
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server keystone-2/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server keystone-2/node-3 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 22 14:47:06 node-4 haproxy[5652]: proxy keystone-2 has no server available!
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server nova-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server nova-api/node-3 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 22 14:47:06 node-4 haproxy[5652]: proxy nova-api has no server available!
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server nova-metadata-api/node-3 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 22 14:47:06 node-4 haproxy[5652]: proxy nova-metadata-api has no server available!
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server cinder-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Backup Server cinder-api/node-3 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 22 14:47:06 node-4 haproxy[5652]: proxy cinder-api has no server available!
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server glance-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server glance-api/node-3 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 22 14:47:06 node-4 haproxy[5652]: proxy glance-api has no server available!
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server glance-glare/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server glance-glare/node-3 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 22 14:47:06 node-4 haproxy[5652]: proxy glance-glare has no server available!
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server neutron/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:06 node-4 haproxy[5652]: Server neutron/node-3 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 22 14:47:06 node-4 haproxy[5652]: proxy neutron has no server available!
<129>Jul 22 14:47:07 node-4 haproxy[5652]: Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:07 node-4 haproxy[5652]: Backup Server mysqld/node-3 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 22 14:47:07 node-4 haproxy[5652]: proxy mysqld has no server available!
<129>Jul 22 14:47:07 node-4 haproxy[5652]: Server object-storage/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:07 node-4 haproxy[5652]: Server object-storage/node-3 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 22 14:47:07 node-4 haproxy[5652]: proxy object-storage has no server available!
<129>Jul 22 14:47:07 node-4 haproxy[5652]: Server heat-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:07 node-4 haproxy[5652]: Server heat-api/node-3 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 22 14:47:07 node-4 haproxy[5652]: proxy heat-api has no server available!
<129>Jul 22 14:47:07 node-4 haproxy[5652]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:07 node-4 haproxy[5652]: Server heat-api-cfn/node-3 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 22 14:47:07 node-4 haproxy[5652]: proxy heat-api-cfn has no server available!
<129>Jul 22 14:47:07 node-4 haproxy[5652]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 22 14:47:07 node-4 haproxy[5652]: Server heat-api-cloudwatch/node-3 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 22 14:47:07 node-4 haproxy[5652]: proxy heat-api-cloudwatch has no server available!
<27>Jul 22 14:47:28 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 22 14:47:42 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:42 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:42 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:42 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:42 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:42 node-4 multipathd: uevent trigger error
<43>Jul 22 14:47:45 node-4 apache2_error [Fri Jul 22 14:47:39.122546 2016] [mpm_worker:notice] [pid 11279:tid 140641749792640] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 14:47:45 node-4 apache2_error [Fri Jul 22 14:47:39.128765 2016] [mpm_worker:warn] [pid 11279:tid 140641749792640] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 14:47:45 node-4 apache2_error [Fri Jul 22 14:47:39.129113 2016] [mpm_worker:notice] [pid 11279:tid 140641749792640] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 22 14:47:45 node-4 apache2_error [Fri Jul 22 14:47:39.129119 2016] [core:notice] [pid 11279:tid 140641749792640] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 14:47:46 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:46 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:46 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:46 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:46 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:46 node-4 multipathd: uevent trigger error
<27>Jul 22 14:47:55 node-4 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 14:47:59 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 22 14:48:08 node-4 multipathd: uevent trigger error
<27>Jul 22 14:48:55 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 22 14:48:57 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 22 14:50:32 node-4 multipathd: uevent trigger error
<27>Jul 22 14:50:32 node-4 multipathd: uevent trigger error
<27>Jul 22 14:50:32 node-4 multipathd: uevent trigger error
<27>Jul 22 14:50:32 node-4 multipathd: uevent trigger error
<27>Jul 22 14:50:32 node-4 multipathd: uevent trigger error
<27>Jul 22 14:50:32 node-4 multipathd: uevent trigger error
<27>Jul 22 14:50:59 node-4 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 22 14:52:02 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:02 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:02 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:02 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:02 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:11 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:12 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:12 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:12 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:12 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:12 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:18 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 22 14:52:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:26 node-4 multipathd: uevent trigger error
<27>Jul 22 14:52:26 node-4 multipathd: uevent trigger error
<11>Jul 22 14:53:43 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
<27>Jul 22 14:54:01 node-4 multipathd: uevent trigger error
<27>Jul 22 14:54:01 node-4 multipathd: uevent trigger error
<27>Jul 22 14:54:01 node-4 multipathd: uevent trigger error
<27>Jul 22 14:54:01 node-4 multipathd: uevent trigger error
<27>Jul 22 14:54:01 node-4 multipathd: uevent trigger error
<43>Jul 22 14:55:26 node-4 apache2_error [Fri Jul 22 14:55:19.585928 2016] [mpm_worker:notice] [pid 11279:tid 140641749792640] AH00295: caught SIGTERM, shutting down
<43>Jul 22 14:55:26 node-4 apache2_error [Fri Jul 22 14:55:20.333878 2016] [mpm_worker:notice] [pid 19178:tid 139737316538240] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 14:55:26 node-4 apache2_error [Fri Jul 22 14:55:20.333925 2016] [core:notice] [pid 19178:tid 139737316538240] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 22 14:55:56 node-4 apache2_error [Fri Jul 22 14:55:52.334906 2016] [mpm_worker:notice] [pid 19178:tid 139737316538240] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 14:55:56 node-4 apache2_error [Fri Jul 22 14:55:52.349311 2016] [mpm_worker:warn] [pid 19178:tid 139737316538240] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 14:55:56 node-4 apache2_error [Fri Jul 22 14:55:52.353522 2016] [mpm_worker:notice] [pid 19178:tid 139737316538240] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 14:55:56 node-4 apache2_error [Fri Jul 22 14:55:52.353541 2016] [core:notice] [pid 19178:tid 139737316538240] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 14:55:58 node-4 multipathd: uevent trigger error
<27>Jul 22 14:55:58 node-4 multipathd: uevent trigger error
<27>Jul 22 14:55:58 node-4 multipathd: uevent trigger error
<27>Jul 22 14:55:58 node-4 multipathd: uevent trigger error
<27>Jul 22 14:55:58 node-4 multipathd: uevent trigger error
<27>Jul 22 14:56:57 node-4 multipathd: uevent trigger error
<27>Jul 22 14:56:57 node-4 multipathd: uevent trigger error
<27>Jul 22 14:56:57 node-4 multipathd: uevent trigger error
<27>Jul 22 14:56:57 node-4 multipathd: uevent trigger error
<27>Jul 22 14:56:57 node-4 multipathd: uevent trigger error
<27>Jul 22 14:56:57 node-4 multipathd: uevent trigger error
<27>Jul 22 14:56:57 node-4 multipathd: uevent trigger error
<27>Jul 22 14:58:17 node-4 multipathd: uevent trigger error
<27>Jul 22 14:58:17 node-4 multipathd: uevent trigger error
<27>Jul 22 14:58:17 node-4 multipathd: uevent trigger error
<27>Jul 22 14:58:17 node-4 multipathd: uevent trigger error
<27>Jul 22 14:58:17 node-4 multipathd: uevent trigger error
<11>Jul 22 14:59:19 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
<27>Jul 22 15:02:01 node-4 multipathd: uevent trigger error
<27>Jul 22 15:02:01 node-4 multipathd: uevent trigger error
<27>Jul 22 15:02:01 node-4 multipathd: uevent trigger error
<27>Jul 22 15:02:01 node-4 multipathd: uevent trigger error
<27>Jul 22 15:02:01 node-4 multipathd: uevent trigger error
<27>Jul 22 15:02:01 node-4 multipathd: uevent trigger error
<11>Jul 22 15:02:19 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
<11>Jul 22 15:02:59 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
<27>Jul 22 15:04:10 node-4 multipathd: uevent trigger error
<27>Jul 22 15:04:10 node-4 multipathd: uevent trigger error
<27>Jul 22 15:04:10 node-4 multipathd: uevent trigger error
<27>Jul 22 15:04:10 node-4 multipathd: uevent trigger error
<27>Jul 22 15:04:10 node-4 multipathd: uevent trigger error
<27>Jul 22 15:04:10 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:18 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:18 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:18 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:18 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:18 node-4 multipathd: uevent trigger error
<11>Jul 22 15:05:35 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
<27>Jul 22 15:05:54 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:54 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:54 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:54 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:54 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:54 node-4 multipathd: uevent trigger error
<27>Jul 22 15:05:54 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:03 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:03 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:03 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:03 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:03 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:03 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:08 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:08 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:08 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:08 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:08 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:08 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:27 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:27 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:27 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:27 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:27 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:27 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:37 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:37 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:37 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:37 node-4 multipathd: uevent trigger error
<27>Jul 22 15:06:37 node-4 multipathd: uevent trigger error
<11>Jul 22 15:06:59 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
<43>Jul 22 15:07:27 node-4 apache2_error [Fri Jul 22 15:07:23.918121 2016] [mpm_worker:notice] [pid 19178:tid 139737316538240] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 15:07:27 node-4 apache2_error [Fri Jul 22 15:07:24.304810 2016] [mpm_worker:warn] [pid 19178:tid 139737316538240] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 15:07:27 node-4 apache2_error [Fri Jul 22 15:07:24.310542 2016] [mpm_worker:notice] [pid 19178:tid 139737316538240] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 15:07:27 node-4 apache2_error [Fri Jul 22 15:07:24.310567 2016] [core:notice] [pid 19178:tid 139737316538240] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 15:08:05 node-4 multipathd: uevent trigger error
<27>Jul 22 15:08:05 node-4 multipathd: uevent trigger error
<27>Jul 22 15:08:05 node-4 multipathd: uevent trigger error
<27>Jul 22 15:08:05 node-4 multipathd: uevent trigger error
<27>Jul 22 15:08:05 node-4 multipathd: uevent trigger error
<27>Jul 22 15:08:05 node-4 multipathd: uevent trigger error
<43>Jul 22 15:08:07 node-4 apache2_error [Fri Jul 22 15:08:01.168389 2016] [mpm_worker:notice] [pid 19178:tid 139737316538240] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 22 15:08:07 node-4 apache2_error [Fri Jul 22 15:08:01.365902 2016] [mpm_worker:warn] [pid 19178:tid 139737316538240] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 22 15:08:07 node-4 apache2_error [Fri Jul 22 15:08:01.374580 2016] [mpm_worker:notice] [pid 19178:tid 139737316538240] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 22 15:08:07 node-4 apache2_error [Fri Jul 22 15:08:01.374610 2016] [core:notice] [pid 19178:tid 139737316538240] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 22 15:08:47 node-4 multipathd: uevent trigger error
<27>Jul 22 15:08:47 node-4 multipathd: uevent trigger error
<27>Jul 22 15:08:47 node-4 multipathd: uevent trigger error
<27>Jul 22 15:08:47 node-4 multipathd: uevent trigger error
<27>Jul 22 15:08:59 node-4 multipathd: uevent trigger error
<27>Jul 22 15:09:00 node-4 multipathd: uevent trigger error
<27>Jul 22 15:09:00 node-4 multipathd: uevent trigger error
<27>Jul 22 15:09:00 node-4 multipathd: uevent trigger error
<27>Jul 22 15:09:00 node-4 multipathd: uevent trigger error
<11>Jul 22 15:09:48 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
<27>Jul 22 15:10:44 node-4 multipathd: uevent trigger error
<27>Jul 22 15:10:44 node-4 multipathd: uevent trigger error
<27>Jul 22 15:10:44 node-4 multipathd: uevent trigger error
<27>Jul 22 15:10:44 node-4 multipathd: uevent trigger error
<27>Jul 22 15:10:44 node-4 multipathd: uevent trigger error
<11>Jul 22 15:11:04 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
<27>Jul 22 15:11:32 node-4 multipathd: uevent trigger error
<27>Jul 22 15:11:32 node-4 multipathd: uevent trigger error
<27>Jul 22 15:11:32 node-4 multipathd: uevent trigger error
<27>Jul 22 15:11:32 node-4 multipathd: uevent trigger error
<27>Jul 22 15:11:32 node-4 multipathd: uevent trigger error
<27>Jul 22 15:11:32 node-4 multipathd: uevent trigger error
<27>Jul 22 15:11:45 node-4 multipathd: uevent trigger error
<27>Jul 22 15:11:45 node-4 multipathd: uevent trigger error
<27>Jul 22 15:11:45 node-4 multipathd: uevent trigger error
<27>Jul 22 15:11:45 node-4 multipathd: uevent trigger error
<11>Jul 22 15:11:55 node-4 liberasurecode[11380]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:55 node-4 liberasurecode[11380]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:55 node-4 liberasurecode[11380]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:55 node-4 liberasurecode[11380]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:55 node-4 liberasurecode[11404]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:55 node-4 liberasurecode[11404]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:55 node-4 liberasurecode[11404]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:55 node-4 liberasurecode[11404]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:57 node-4 liberasurecode[11812]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:57 node-4 liberasurecode[11812]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:57 node-4 liberasurecode[11812]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:11:57 node-4 liberasurecode[11812]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12510]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12510]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12510]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12510]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12551]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12551]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12551]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12551]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12594]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12594]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12594]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12594]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12652]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12652]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12652]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12652]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12665]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12665]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12665]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12665]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12678]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12678]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12678]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:03 node-4 liberasurecode[12678]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:04 node-4 liberasurecode[12726]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:04 node-4 liberasurecode[12726]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:04 node-4 liberasurecode[12726]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:12:04 node-4 liberasurecode[12726]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 22 15:12:09 node-4 multipathd: uevent trigger error
<27>Jul 22 15:12:09 node-4 multipathd: uevent trigger error
<27>Jul 22 15:12:09 node-4 multipathd: uevent trigger error
<27>Jul 22 15:12:09 node-4 multipathd: uevent trigger error
<27>Jul 22 15:12:09 node-4 multipathd: uevent trigger error
<27>Jul 22 15:12:09 node-4 multipathd: uevent trigger error
<27>Jul 22 15:12:14 node-4 multipathd: uevent trigger error
<27>Jul 22 15:12:14 node-4 multipathd: uevent trigger error
<27>Jul 22 15:12:14 node-4 multipathd: uevent trigger error
<27>Jul 22 15:12:14 node-4 multipathd: uevent trigger error
<27>Jul 22 15:12:14 node-4 multipathd: uevent trigger error
<27>Jul 22 15:14:42 node-4 multipathd: uevent trigger error
<27>Jul 22 15:14:42 node-4 multipathd: uevent trigger error
<27>Jul 22 15:14:42 node-4 multipathd: uevent trigger error
<27>Jul 22 15:14:42 node-4 multipathd: uevent trigger error
<27>Jul 22 15:14:47 node-4 multipathd: uevent trigger error
<27>Jul 22 15:14:47 node-4 multipathd: uevent trigger error
<27>Jul 22 15:14:47 node-4 multipathd: uevent trigger error
<27>Jul 22 15:14:47 node-4 multipathd: uevent trigger error
<27>Jul 22 15:14:47 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:01 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:01 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:01 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:01 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:01 node-4 multipathd: uevent trigger error
<11>Jul 22 15:15:01 node-4 liberasurecode[8431]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:15:01 node-4 liberasurecode[8431]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:15:01 node-4 liberasurecode[8431]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 22 15:15:01 node-4 liberasurecode[8431]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 22 15:15:05 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
<27>Jul 22 15:15:15 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:15 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:15 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:15 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:15 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:34 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:34 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:34 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:34 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:41 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:41 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:41 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:41 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:41 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:41 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:46 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:46 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:46 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:46 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:46 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:51 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:51 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:51 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:51 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:51 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:51 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:55 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:55 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:55 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:55 node-4 multipathd: uevent trigger error
<27>Jul 22 15:15:55 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:00 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:00 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:00 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:00 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:00 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:04 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:05 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:05 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:05 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:05 node-4 multipathd: uevent trigger error
<27>Jul 22 15:16:05 node-4 multipathd: uevent trigger error
<11>Jul 22 15:17:03 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
<11>Jul 22 15:18:28 node-4 epmd: epmd: node name already occupied rabbitmq-cli-53
