Jul 28 15:24:56 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8407" x-info="http://www.rsyslog.com"] start
Jul 28 15:24:56 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 28 15:24:56 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 28 15:24:56 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 28 15:24:56 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 28 15:24:56 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 28 15:24:56 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 28 15:24:56 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 28 15:24:56 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=58df8f29-78be-4481-bc4b-3ae02f2b343c nomdmonddf nomdmonisw
Jul 28 15:24:56 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 28 15:24:56 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 28 15:24:56 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 28 15:24:56 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 28 15:24:56 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 28 15:24:56 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 28 15:24:56 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 28 15:24:56 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 28 15:24:56 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 28 15:24:56 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 28 15:24:56 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 28 15:24:56 node-4 kernel: [    0.000000] No AGP bridge found
Jul 28 15:24:56 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 28 15:24:56 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 28 15:24:56 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 28 15:24:56 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 28 15:24:56 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 28 15:24:56 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 28 15:24:56 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 28 15:24:56 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 28 15:24:56 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 28 15:24:56 node-4 kernel: [    0.000000]   2 disabled
Jul 28 15:24:56 node-4 kernel: [    0.000000]   3 disabled
Jul 28 15:24:56 node-4 kernel: [    0.000000]   4 disabled
Jul 28 15:24:56 node-4 kernel: [    0.000000]   5 disabled
Jul 28 15:24:56 node-4 kernel: [    0.000000]   6 disabled
Jul 28 15:24:56 node-4 kernel: [    0.000000]   7 disabled
Jul 28 15:24:56 node-4 kernel: [    0.000000]   8 disabled
Jul 28 15:24:56 node-4 kernel: [    0.000000]   9 disabled
Jul 28 15:24:56 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 28 15:24:56 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 28 15:24:56 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 28 15:24:56 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 28 15:24:56 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 28 15:24:56 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 28 15:24:56 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 28 15:24:56 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 28 15:24:56 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 28 15:24:56 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 28 15:24:56 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 28 15:24:56 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 28 15:24:56 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 28 15:24:56 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 28 15:24:56 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 28 15:24:56 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 28 15:24:56 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 28 15:24:56 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 28 15:24:56 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 28 15:24:56 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 28 15:24:56 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 28 15:24:56 node-4 kernel: [    0.000000] Zone ranges:
Jul 28 15:24:56 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 28 15:24:56 node-4 kernel: [    0.000000] Early memory node ranges
Jul 28 15:24:56 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 28 15:24:56 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 28 15:24:56 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 28 15:24:56 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 28 15:24:56 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 28 15:24:56 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 28 15:24:56 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 28 15:24:56 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 28 15:24:56 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 28 15:24:56 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 28 15:24:56 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 28 15:24:56 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 28 15:24:56 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 28 15:24:56 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 28 15:24:56 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 28 15:24:56 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 28 15:24:56 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 28 15:24:56 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 28 15:24:56 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 28 15:24:56 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 28 15:24:56 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 28 15:24:56 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 28 15:24:56 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 28 15:24:56 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 28 15:24:56 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 28 15:24:56 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 28 15:24:56 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=58df8f29-78be-4481-bc4b-3ae02f2b343c nomdmonddf nomdmonisw
Jul 28 15:24:56 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 28 15:24:56 node-4 kernel: [    0.000000] Checking aperture...
Jul 28 15:24:56 node-4 kernel: [    0.000000] No AGP bridge found
Jul 28 15:24:56 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 28 15:24:56 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 28 15:24:56 node-4 kernel: [    0.000000] Memory: 32653316K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Jul 28 15:24:56 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 28 15:24:56 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 28 15:24:56 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 28 15:24:56 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 28 15:24:56 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 28 15:24:56 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 28 15:24:56 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 28 15:24:56 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 28 15:24:56 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 28 15:24:56 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 28 15:24:56 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 28 15:24:56 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 28 15:24:56 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 28 15:24:56 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 28 15:24:56 node-4 kernel: [    0.004000] tsc: Detected 3491.833 MHz processor
Jul 28 15:24:56 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.66 BogoMIPS (lpj=13967332)
Jul 28 15:24:56 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Jul 28 15:24:56 node-4 kernel: [    0.000047] Security Framework initialized
Jul 28 15:24:56 node-4 kernel: [    0.000065] AppArmor: AppArmor initialized
Jul 28 15:24:56 node-4 kernel: [    0.000067] Yama: becoming mindful.
Jul 28 15:24:56 node-4 kernel: [    0.001447] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.006331] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.008263] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.008290] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.008578] Initializing cgroup subsys memory
Jul 28 15:24:56 node-4 kernel: [    0.008586] Initializing cgroup subsys devices
Jul 28 15:24:56 node-4 kernel: [    0.008588] Initializing cgroup subsys freezer
Jul 28 15:24:56 node-4 kernel: [    0.008590] Initializing cgroup subsys blkio
Jul 28 15:24:56 node-4 kernel: [    0.008591] Initializing cgroup subsys perf_event
Jul 28 15:24:56 node-4 kernel: [    0.008594] Initializing cgroup subsys hugetlb
Jul 28 15:24:56 node-4 kernel: [    0.008613] CPU: Physical Processor ID: 0
Jul 28 15:24:56 node-4 kernel: [    0.008614] CPU: Processor Core ID: 0
Jul 28 15:24:56 node-4 kernel: [    0.008618] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 28 15:24:56 node-4 kernel: [    0.008618] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 28 15:24:56 node-4 kernel: [    0.009312] mce: CPU supports 22 MCE banks
Jul 28 15:24:56 node-4 kernel: [    0.009339] CPU0: Thermal monitoring enabled (TM1)
Jul 28 15:24:56 node-4 kernel: [    0.009360] process: using mwait in idle threads
Jul 28 15:24:56 node-4 kernel: [    0.009363] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 28 15:24:56 node-4 kernel: [    0.009363] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 28 15:24:56 node-4 kernel: [    0.009363] tlb_flushall_shift: 6
Jul 28 15:24:56 node-4 kernel: [    0.009451] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 28 15:24:56 node-4 kernel: [    0.010175] ACPI: Core revision 20131115
Jul 28 15:24:56 node-4 kernel: [    0.022860] ACPI: All ACPI Tables successfully acquired
Jul 28 15:24:56 node-4 kernel: [    0.023021] ftrace: allocating 28617 entries in 112 pages
Jul 28 15:24:56 node-4 kernel: [    0.031836] dmar: Host address width 46
Jul 28 15:24:56 node-4 kernel: [    0.031838] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 28 15:24:56 node-4 kernel: [    0.031844] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 15:24:56 node-4 kernel: [    0.031846] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 28 15:24:56 node-4 kernel: [    0.031849] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 28 15:24:56 node-4 kernel: [    0.031851] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 28 15:24:56 node-4 kernel: [    0.031852] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 28 15:24:56 node-4 kernel: [    0.031853] dmar: ATSR flags: 0x0
Jul 28 15:24:56 node-4 kernel: [    0.031854] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 28 15:24:56 node-4 kernel: [    0.031856] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 28 15:24:56 node-4 kernel: [    0.031971] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 28 15:24:56 node-4 kernel: [    0.031972] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 15:24:56 node-4 kernel: [    0.031973] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 28 15:24:56 node-4 kernel: [    0.031974] HPET id 0 under DRHD base 0xc7ffc000
Jul 28 15:24:56 node-4 kernel: [    0.031976] Your BIOS is broken and requested that x2apic be disabled.
Jul 28 15:24:56 node-4 kernel: [    0.031976] This will slightly decrease performance.
Jul 28 15:24:56 node-4 kernel: [    0.031976] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 28 15:24:56 node-4 kernel: [    0.032406] Enabled IRQ remapping in xapic mode
Jul 28 15:24:56 node-4 kernel: [    0.032408] x2apic not enabled, IRQ remapping is in xapic mode
Jul 28 15:24:56 node-4 kernel: [    0.032411] Switched APIC routing to physical flat.
Jul 28 15:24:56 node-4 kernel: [    0.033046] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 28 15:24:56 node-4 kernel: [    0.072695] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 28 15:24:56 node-4 kernel: [    0.072701] TSC deadline timer enabled
Jul 28 15:24:56 node-4 kernel: [    0.072708] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 28 15:24:56 node-4 kernel: [    0.072714] ... version:                3
Jul 28 15:24:56 node-4 kernel: [    0.072715] ... bit width:              48
Jul 28 15:24:56 node-4 kernel: [    0.072716] ... generic registers:      4
Jul 28 15:24:56 node-4 kernel: [    0.072717] ... value mask:             0000ffffffffffff
Jul 28 15:24:56 node-4 kernel: [    0.072718] ... max period:             0000ffffffffffff
Jul 28 15:24:56 node-4 kernel: [    0.072719] ... fixed-purpose events:   3
Jul 28 15:24:56 node-4 kernel: [    0.072720] ... event mask:             000000070000000f
Jul 28 15:24:56 node-4 kernel: [    0.074147] x86: Booting SMP configuration:
Jul 28 15:24:56 node-4 kernel: [    0.088254] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 28 15:24:56 node-4 kernel: [    0.074149] .... node  #0, CPUs:        #1  #2  #3
Jul 28 15:24:56 node-4 kernel: [    0.116166] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 28 15:24:56 node-4 kernel: [    0.270300] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 28 15:24:56 node-4 kernel: [    0.325914] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 28 15:24:56 node-4 kernel: [    0.382962] x86: Booted up 2 nodes, 16 CPUs
Jul 28 15:24:56 node-4 kernel: [    0.382966] smpboot: Total of 16 processors activated (111750.62 BogoMIPS)
Jul 28 15:24:56 node-4 kernel: [    0.407427] devtmpfs: initialized
Jul 28 15:24:56 node-4 kernel: [    0.410528] EVM: security.selinux
Jul 28 15:24:56 node-4 kernel: [    0.410530] EVM: security.SMACK64
Jul 28 15:24:56 node-4 kernel: [    0.410531] EVM: security.ima
Jul 28 15:24:56 node-4 kernel: [    0.410532] EVM: security.capability
Jul 28 15:24:56 node-4 kernel: [    0.410583] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.411274] pinctrl core: initialized pinctrl subsystem
Jul 28 15:24:56 node-4 kernel: [    0.411338] regulator-dummy: no parameters
Jul 28 15:24:56 node-4 kernel: [    0.411370] RTC time: 15:24:19, date: 07/28/16
Jul 28 15:24:56 node-4 kernel: [    0.411405] NET: Registered protocol family 16
Jul 28 15:24:56 node-4 kernel: [    0.411496] cpuidle: using governor ladder
Jul 28 15:24:56 node-4 kernel: [    0.411498] cpuidle: using governor menu
Jul 28 15:24:56 node-4 kernel: [    0.411532] ACPI: bus type PCI registered
Jul 28 15:24:56 node-4 kernel: [    0.411534] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 28 15:24:56 node-4 kernel: [    0.411581] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 28 15:24:56 node-4 kernel: [    0.411583] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 28 15:24:56 node-4 kernel: [    0.425319] PCI: Using configuration type 1 for base access
Jul 28 15:24:56 node-4 kernel: [    0.426333] bio: create slab <bio-0> at 0
Jul 28 15:24:56 node-4 kernel: [    0.426618] ACPI: Added _OSI(Module Device)
Jul 28 15:24:56 node-4 kernel: [    0.426620] ACPI: Added _OSI(Processor Device)
Jul 28 15:24:56 node-4 kernel: [    0.426621] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 28 15:24:56 node-4 kernel: [    0.426622] ACPI: Added _OSI(Processor Aggregator Device)
Jul 28 15:24:56 node-4 kernel: [    0.439275] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 28 15:24:56 node-4 kernel: [    0.449736] ACPI: Interpreter enabled
Jul 28 15:24:56 node-4 kernel: [    0.449741] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 28 15:24:56 node-4 kernel: [    0.449745] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 28 15:24:56 node-4 kernel: [    0.449748] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 28 15:24:56 node-4 kernel: [    0.449754] ACPI: (supports S0 S4 S5)
Jul 28 15:24:56 node-4 kernel: [    0.449756] ACPI: Using IOAPIC for interrupt routing
Jul 28 15:24:56 node-4 kernel: [    0.449796] HEST: Table parsing has been initialized.
Jul 28 15:24:56 node-4 kernel: [    0.449799] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 28 15:24:56 node-4 kernel: [    0.450348] ACPI: No dock devices found.
Jul 28 15:24:56 node-4 kernel: [    0.461938] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 28 15:24:56 node-4 kernel: [    0.461944] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 15:24:56 node-4 kernel: [    0.461947] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 15:24:56 node-4 kernel: [    0.461973] PCI host bridge to bus 0000:ff
Jul 28 15:24:56 node-4 kernel: [    0.461975] pci_bus 0000:ff: root bus resource [bus ff]
Jul 28 15:24:56 node-4 kernel: [    0.461984] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462022] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.462052] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462087] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462116] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.462146] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.462175] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462202] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462232] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462260] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462287] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462314] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462342] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462368] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462395] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462422] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462451] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462479] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462506] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.462534] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462560] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.462586] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462613] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462643] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.462678] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462710] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462740] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462771] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462802] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462833] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462864] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462894] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462925] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462958] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.462990] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463023] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463056] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463086] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463114] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463145] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463177] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463215] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463251] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463283] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463313] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463342] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463372] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463401] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463431] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463462] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463493] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463522] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463550] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463578] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463607] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463638] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463669] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463726] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 28 15:24:56 node-4 kernel: [    0.463728] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 15:24:56 node-4 kernel: [    0.463731] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 28 15:24:56 node-4 kernel: [    0.463748] PCI host bridge to bus 0000:7f
Jul 28 15:24:56 node-4 kernel: [    0.463750] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 28 15:24:56 node-4 kernel: [    0.463755] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463782] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.463809] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463839] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463860] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.463885] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.463911] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463938] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463960] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.463982] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464004] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464026] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464050] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464077] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464102] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464127] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464148] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464173] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464198] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.464221] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464243] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.464265] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464287] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464313] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 28 15:24:56 node-4 kernel: [    0.464345] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464371] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464397] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464423] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464448] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464474] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464500] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464527] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464551] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464577] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464603] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464630] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464658] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464684] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464708] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464736] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464761] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464787] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464815] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464843] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464867] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464891] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464918] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464946] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464973] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.464999] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.465028] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.465053] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.465075] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.465101] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.465126] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.465154] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.465180] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.466422] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 28 15:24:56 node-4 kernel: [    0.466425] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 15:24:56 node-4 kernel: [    0.467555] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 15:24:56 node-4 kernel: [    0.468067] PCI host bridge to bus 0000:00
Jul 28 15:24:56 node-4 kernel: [    0.468069] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 28 15:24:56 node-4 kernel: [    0.468071] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 28 15:24:56 node-4 kernel: [    0.468072] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 28 15:24:56 node-4 kernel: [    0.468074] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 28 15:24:56 node-4 kernel: [    0.468075] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 28 15:24:56 node-4 kernel: [    0.468077] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 28 15:24:56 node-4 kernel: [    0.468078] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 28 15:24:56 node-4 kernel: [    0.468084] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 28 15:24:56 node-4 kernel: [    0.468166] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.468197] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.468238] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 28 15:24:56 node-4 kernel: [    0.468258] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.468287] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.468327] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 28 15:24:56 node-4 kernel: [    0.468345] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.468375] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.468415] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 28 15:24:56 node-4 kernel: [    0.468431] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.468501] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.468577] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.468651] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 15:24:56 node-4 kernel: [    0.468656] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 28 15:24:56 node-4 kernel: [    0.468741] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 28 15:24:56 node-4 kernel: [    0.468888] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 28 15:24:56 node-4 kernel: [    0.468906] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 28 15:24:56 node-4 kernel: [    0.468983] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.469038] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 28 15:24:56 node-4 kernel: [    0.469059] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.469115] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.469158] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 28 15:24:56 node-4 kernel: [    0.469184] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.469240] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.469283] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 28 15:24:56 node-4 kernel: [    0.469307] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 28 15:24:56 node-4 kernel: [    0.469324] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 28 15:24:56 node-4 kernel: [    0.469401] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.469451] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 28 15:24:56 node-4 kernel: [    0.469476] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 28 15:24:56 node-4 kernel: [    0.469723] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 28 15:24:56 node-4 kernel: [    0.469729] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 28 15:24:56 node-4 kernel: [    0.469735] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.469741] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.469748] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 28 15:24:56 node-4 kernel: [    0.469778] pci 0000:01:00.0: supports D1 D2
Jul 28 15:24:56 node-4 kernel: [    0.480067] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 15:24:56 node-4 kernel: [    0.480073] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 15:24:56 node-4 kernel: [    0.480077] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 15:24:56 node-4 kernel: [    0.480277] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.480310] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 28 15:24:56 node-4 kernel: [    0.492061] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 15:24:56 node-4 kernel: [    0.492068] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.492083] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 15:24:56 node-4 kernel: [    0.492139] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.492207] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.492283] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.492328] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 15:24:56 node-4 kernel: [    0.492332] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.492333] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 15:24:56 node-4 kernel: [    0.492385] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.492512] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.492565] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 15:24:56 node-4 kernel: [    0.492568] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.492570] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 15:24:56 node-4 kernel: [    0.492619] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.492738] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.492776] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.492919] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.492955] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.493075] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.493112] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 28 15:24:56 node-4 kernel: [    0.493231] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 28 15:24:56 node-4 kernel: [    0.493274] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 15:24:56 node-4 kernel: [    0.493276] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.493278] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 15:24:56 node-4 kernel: [    0.493338] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 28 15:24:56 node-4 kernel: [    0.493403] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.493456] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.493497] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 28 15:24:56 node-4 kernel: [    0.493579] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 28 15:24:56 node-4 kernel: [    0.493684] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 15:24:56 node-4 kernel: [    0.493687] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.493689] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 15:24:56 node-4 kernel: [    0.493745] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 28 15:24:56 node-4 kernel: [    0.493798] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.493846] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.494086] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 15:24:56 node-4 kernel: [    0.494090] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 15:24:56 node-4 kernel: [    0.494153] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 28 15:24:56 node-4 kernel: [    0.494206] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.494255] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.494465] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 15:24:56 node-4 kernel: [    0.494468] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 15:24:56 node-4 kernel: [    0.494527] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 28 15:24:56 node-4 kernel: [    0.494587] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.494639] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 28 15:24:56 node-4 kernel: [    0.494875] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 15:24:56 node-4 kernel: [    0.494879] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 15:24:56 node-4 kernel: [    0.495055] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 15:24:56 node-4 kernel: [    0.495093] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 15:24:56 node-4 kernel: [    0.495169] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 28 15:24:56 node-4 kernel: [    0.495188] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 28 15:24:56 node-4 kernel: [    0.495201] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 28 15:24:56 node-4 kernel: [    0.495215] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 28 15:24:56 node-4 kernel: [    0.495265] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 28 15:24:56 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 28 15:24:56 node-4 kernel: [    0.500068] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 15:24:56 node-4 kernel: [    0.500085] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 15:24:56 node-4 kernel: [    0.500117] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 28 15:24:56 node-4 kernel: [    0.500608] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 28 15:24:56 node-4 kernel: [    0.500611] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 28 15:24:56 node-4 kernel: [    0.500731] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 28 15:24:56 node-4 kernel: [    0.500838] PCI host bridge to bus 0000:80
Jul 28 15:24:56 node-4 kernel: [    0.500840] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 28 15:24:56 node-4 kernel: [    0.500841] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 28 15:24:56 node-4 kernel: [    0.500843] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 28 15:24:56 node-4 kernel: [    0.500851] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.500913] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.500981] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 28 15:24:56 node-4 kernel: [    0.501043] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 28 15:24:56 node-4 kernel: [    0.501048] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 28 15:24:56 node-4 kernel: [    0.501118] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 28 15:24:56 node-4 kernel: [    0.501415] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 28 15:24:56 node-4 kernel: [    0.501446] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 28 15:24:56 node-4 kernel: [    0.501476] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 28 15:24:56 node-4 kernel: [    0.501505] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 28 15:24:56 node-4 kernel: [    0.501534] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 15:24:56 node-4 kernel: [    0.501564] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 15:24:56 node-4 kernel: [    0.501594] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 15:24:56 node-4 kernel: [    0.501624] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 28 15:24:56 node-4 kernel: [    0.501710] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 28 15:24:56 node-4 kernel: [    0.501714] ACPI: \_SB_.UNC1: notify handler is installed
Jul 28 15:24:56 node-4 kernel: [    0.501715] ACPI: \_SB_.UNC0: notify handler is installed
Jul 28 15:24:56 node-4 kernel: [    0.501731] ACPI: \_SB_.PCI0: notify handler is installed
Jul 28 15:24:56 node-4 kernel: [    0.501784] ACPI: \_SB_.PCI1: notify handler is installed
Jul 28 15:24:56 node-4 kernel: [    0.501863] Found 4 acpi root devices
Jul 28 15:24:56 node-4 kernel: [    0.501980] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 28 15:24:56 node-4 kernel: [    0.501983] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 28 15:24:56 node-4 kernel: [    0.501984] vgaarb: loaded
Jul 28 15:24:56 node-4 kernel: [    0.501985] vgaarb: bridge control possible 0000:0c:00.0
Jul 28 15:24:56 node-4 kernel: [    0.502102] SCSI subsystem initialized
Jul 28 15:24:56 node-4 kernel: [    0.502165] libata version 3.00 loaded.
Jul 28 15:24:56 node-4 kernel: [    0.502180] ACPI: bus type USB registered
Jul 28 15:24:56 node-4 kernel: [    0.502190] usbcore: registered new interface driver usbfs
Jul 28 15:24:56 node-4 kernel: [    0.502195] usbcore: registered new interface driver hub
Jul 28 15:24:56 node-4 kernel: [    0.502217] usbcore: registered new device driver usb
Jul 28 15:24:56 node-4 kernel: [    0.502377] PCI: Using ACPI for IRQ routing
Jul 28 15:24:56 node-4 kernel: [    0.505990] PCI: pci_cache_line_size set to 64 bytes
Jul 28 15:24:56 node-4 kernel: [    0.506192] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 28 15:24:56 node-4 kernel: [    0.506193] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 28 15:24:56 node-4 kernel: [    0.506194] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 28 15:24:56 node-4 kernel: [    0.506258] NetLabel: Initializing
Jul 28 15:24:56 node-4 kernel: [    0.506260] NetLabel:  domain hash size = 128
Jul 28 15:24:56 node-4 kernel: [    0.506261] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 28 15:24:56 node-4 kernel: [    0.506270] NetLabel:  unlabeled traffic allowed by default
Jul 28 15:24:56 node-4 kernel: [    0.506326] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 28 15:24:56 node-4 kernel: [    0.506330] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 28 15:24:56 node-4 kernel: [    0.508399] Switched to clocksource hpet
Jul 28 15:24:56 node-4 kernel: [    0.512929] AppArmor: AppArmor Filesystem Enabled
Jul 28 15:24:56 node-4 kernel: [    0.512967] pnp: PnP ACPI init
Jul 28 15:24:56 node-4 kernel: [    0.512979] ACPI: bus type PNP registered
Jul 28 15:24:56 node-4 kernel: [    0.513157] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 28 15:24:56 node-4 kernel: [    0.513168] pnp 00:01: [dma 4]
Jul 28 15:24:56 node-4 kernel: [    0.513186] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 28 15:24:56 node-4 kernel: [    0.513220] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 28 15:24:56 node-4 kernel: [    0.513244] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 28 15:24:56 node-4 kernel: [    0.513265] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 28 15:24:56 node-4 kernel: [    0.513312] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 28 15:24:56 node-4 kernel: [    0.513424] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513427] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 28 15:24:56 node-4 kernel: [    0.513429] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513430] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513432] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513433] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513436] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 28 15:24:56 node-4 kernel: [    0.513438] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513440] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513441] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513443] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513444] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513446] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 28 15:24:56 node-4 kernel: [    0.513448] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 28 15:24:56 node-4 kernel: [    0.513550] pnp 00:07: [dma 0 disabled]
Jul 28 15:24:56 node-4 kernel: [    0.513582] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 15:24:56 node-4 kernel: [    0.513664] pnp 00:08: [dma 0 disabled]
Jul 28 15:24:56 node-4 kernel: [    0.513699] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 28 15:24:56 node-4 kernel: [    0.513757] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 28 15:24:56 node-4 kernel: [    0.514201] pnp: PnP ACPI: found 10 devices
Jul 28 15:24:56 node-4 kernel: [    0.514203] ACPI: bus type PNP unregistered
Jul 28 15:24:56 node-4 kernel: [    0.520209] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 28 15:24:56 node-4 kernel: [    0.520213] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 28 15:24:56 node-4 kernel: [    0.520215] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 28 15:24:56 node-4 kernel: [    0.520221] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 28 15:24:56 node-4 kernel: [    0.520223] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.520237] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520269] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 28 15:24:56 node-4 kernel: [    0.520284] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520313] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 28 15:24:56 node-4 kernel: [    0.520327] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 28 15:24:56 node-4 kernel: [    0.520356] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 28 15:24:56 node-4 kernel: [    0.520375] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 28 15:24:56 node-4 kernel: [    0.520404] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 28 15:24:56 node-4 kernel: [    0.520406] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.520421] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520450] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 28 15:24:56 node-4 kernel: [    0.520452] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.520466] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520495] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 28 15:24:56 node-4 kernel: [    0.520497] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.520500] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520505] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 28 15:24:56 node-4 kernel: [    0.520507] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.520509] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520514] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 28 15:24:56 node-4 kernel: [    0.520520] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 28 15:24:56 node-4 kernel: [    0.520528] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 28 15:24:56 node-4 kernel: [    0.520532] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 28 15:24:56 node-4 kernel: [    0.520539] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 28 15:24:56 node-4 kernel: [    0.520540] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 28 15:24:56 node-4 kernel: [    0.520541] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 28 15:24:56 node-4 kernel: [    0.520542] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 28 15:24:56 node-4 kernel: [    0.520543] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 28 15:24:56 node-4 kernel: [    0.520544] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 28 15:24:56 node-4 kernel: [    0.520545] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 28 15:24:56 node-4 kernel: [    0.520546] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 28 15:24:56 node-4 kernel: [    0.520547] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.520548] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520549] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.520550] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520551] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.520552] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520553] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.520553] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520554] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 28 15:24:56 node-4 kernel: [    0.520555] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520556] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 28 15:24:56 node-4 kernel: [    0.520558] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 28 15:24:56 node-4 kernel: [    0.520559] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 28 15:24:56 node-4 kernel: [    0.520560] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 28 15:24:56 node-4 kernel: [    0.520563] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 28 15:24:56 node-4 kernel: [    0.520564] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 28 15:24:56 node-4 kernel: [    0.520604] NET: Registered protocol family 2
Jul 28 15:24:56 node-4 kernel: [    0.520902] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.521281] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.521447] TCP: Hash tables configured (established 262144 bind 65536)
Jul 28 15:24:56 node-4 kernel: [    0.521493] TCP: reno registered
Jul 28 15:24:56 node-4 kernel: [    0.521526] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.521634] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.521792] NET: Registered protocol family 1
Jul 28 15:24:56 node-4 kernel: [    0.560485] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 28 15:24:56 node-4 kernel: [    0.560499] PCI: CLS 64 bytes, default 64
Jul 28 15:24:56 node-4 kernel: [    0.560585] Trying to unpack rootfs image as initramfs...
Jul 28 15:24:56 node-4 kernel: [    0.782034] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Jul 28 15:24:56 node-4 kernel: [    0.782090] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 28 15:24:56 node-4 kernel: [    0.782100] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 28 15:24:56 node-4 kernel: [    0.782636] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782642] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782650] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782657] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782666] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782674] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782685] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782693] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782700] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782708] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782715] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782721] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782728] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782763] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782769] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782776] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 28 15:24:56 node-4 kernel: [    0.782869] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 28 15:24:56 node-4 kernel: [    0.782872] Scanning for low memory corruption every 60 seconds
Jul 28 15:24:56 node-4 kernel: [    0.783226] Initialise system trusted keyring
Jul 28 15:24:56 node-4 kernel: [    0.783275] audit: initializing netlink socket (disabled)
Jul 28 15:24:56 node-4 kernel: [    0.783289] type=2000 audit(1469719459.736:1): initialized
Jul 28 15:24:56 node-4 kernel: [    0.801172] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 28 15:24:56 node-4 kernel: [    0.802648] zbud: loaded
Jul 28 15:24:56 node-4 kernel: [    0.802765] VFS: Disk quotas dquot_6.5.2
Jul 28 15:24:56 node-4 kernel: [    0.802799] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 28 15:24:56 node-4 kernel: [    0.803163] fuse init (API version 7.22)
Jul 28 15:24:56 node-4 kernel: [    0.803218] msgmni has been set to 32768
Jul 28 15:24:56 node-4 kernel: [    0.803264] Key type big_key registered
Jul 28 15:24:56 node-4 kernel: [    0.803759] Key type asymmetric registered
Jul 28 15:24:56 node-4 kernel: [    0.803761] Asymmetric key parser 'x509' registered
Jul 28 15:24:56 node-4 kernel: [    0.803781] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 28 15:24:56 node-4 kernel: [    0.803847] io scheduler noop registered
Jul 28 15:24:56 node-4 kernel: [    0.803849] io scheduler deadline registered (default)
Jul 28 15:24:56 node-4 kernel: [    0.803868] io scheduler cfq registered
Jul 28 15:24:56 node-4 kernel: [    0.804302] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    0.804545] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    0.804700] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    0.804824] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    0.804955] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    0.805061] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    0.805467] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 28 15:24:56 node-4 kernel: [    0.805506] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 28 15:24:56 node-4 kernel: [    0.805533] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 28 15:24:56 node-4 kernel: [    0.805551] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805556] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805562] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 28 15:24:56 node-4 kernel: [    0.805572] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805576] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805580] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805584] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805588] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805592] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805596] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805600] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805603] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805607] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805611] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805615] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805620] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 28 15:24:56 node-4 kernel: [    0.805631] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805636] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 28 15:24:56 node-4 kernel: [    0.805661] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805667] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 28 15:24:56 node-4 kernel: [    0.805686] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805690] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 28 15:24:56 node-4 kernel: [    0.805696] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 28 15:24:56 node-4 kernel: [    0.805760] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 28 15:24:56 node-4 kernel: [    0.805766] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 28 15:24:56 node-4 kernel: [    0.805769] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 28 15:24:56 node-4 kernel: [    0.805778] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 28 15:24:56 node-4 kernel: [    0.805817] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 28 15:24:56 node-4 kernel: [    0.805818] vesafb: scrolling: redraw
Jul 28 15:24:56 node-4 kernel: [    0.805820] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 28 15:24:56 node-4 kernel: [    0.826232] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 28 15:24:56 node-4 kernel: [    0.834713] Console: switching to colour frame buffer device 80x30
Jul 28 15:24:56 node-4 kernel: [    0.843359] fb0: VESA VGA frame buffer device
Jul 28 15:24:56 node-4 kernel: [    0.843556] intel_idle: MWAIT substates: 0x2120
Jul 28 15:24:56 node-4 kernel: [    0.843557] intel_idle: v0.4 model 0x3F
Jul 28 15:24:56 node-4 kernel: [    0.843557] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 28 15:24:56 node-4 kernel: [    0.843792] ipmi message handler version 39.2
Jul 28 15:24:56 node-4 kernel: [    0.844069] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 28 15:24:56 node-4 kernel: [    0.844507] ACPI: AC Adapter [P111] (on-line)
Jul 28 15:24:56 node-4 kernel: [    0.849763] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 28 15:24:56 node-4 kernel: [    0.860773] ACPI: Power Button [PWRB]
Jul 28 15:24:56 node-4 kernel: [    0.866539] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 28 15:24:56 node-4 kernel: [    0.878184] ACPI: Power Button [PWRF]
Jul 28 15:24:56 node-4 kernel: [    0.897958] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 28 15:24:56 node-4 kernel: [    0.909725] pstore: Registered erst as persistent store backend
Jul 28 15:24:56 node-4 kernel: [    0.915992] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 28 15:24:56 node-4 kernel: [    0.928050] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 28 15:24:56 node-4 kernel: [    0.954860] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 28 15:24:56 node-4 kernel: [    0.988323] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 28 15:24:56 node-4 kernel: [    1.002558] Linux agpgart interface v0.103
Jul 28 15:24:56 node-4 kernel: [    1.010280] brd: module loaded
Jul 28 15:24:56 node-4 kernel: [    1.017390] loop: module loaded
Jul 28 15:24:56 node-4 kernel: [    1.024179] libphy: Fixed MDIO Bus: probed
Jul 28 15:24:56 node-4 kernel: [    1.030779] tun: Universal TUN/TAP device driver, 1.6
Jul 28 15:24:56 node-4 kernel: [    1.037363] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 28 15:24:56 node-4 kernel: [    1.043961] PPP generic driver version 2.4.2
Jul 28 15:24:56 node-4 kernel: [    1.050425] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 28 15:24:56 node-4 kernel: [    1.056948] ehci-pci: EHCI PCI platform driver
Jul 28 15:24:56 node-4 kernel: [    1.063523] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 28 15:24:56 node-4 kernel: [    1.070056] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 28 15:24:56 node-4 kernel: [    1.082733] ehci-pci 0000:00:1a.0: debug port 2
Jul 28 15:24:56 node-4 kernel: [    1.093015] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 28 15:24:56 node-4 kernel: [    1.093033] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 28 15:24:56 node-4 kernel: [    1.107880] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 28 15:24:56 node-4 kernel: [    1.114000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 15:24:56 node-4 kernel: [    1.120227] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 15:24:56 node-4 kernel: [    1.132227] usb usb1: Product: EHCI Host Controller
Jul 28 15:24:56 node-4 kernel: [    1.138309] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 15:24:56 node-4 kernel: [    1.144385] usb usb1: SerialNumber: 0000:00:1a.0
Jul 28 15:24:56 node-4 kernel: [    1.150411] hub 1-0:1.0: USB hub found
Jul 28 15:24:56 node-4 kernel: [    1.156260] hub 1-0:1.0: 2 ports detected
Jul 28 15:24:56 node-4 kernel: [    1.162092] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 28 15:24:56 node-4 kernel: [    1.167719] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 28 15:24:56 node-4 kernel: [    1.178729] ehci-pci 0000:00:1d.0: debug port 2
Jul 28 15:24:56 node-4 kernel: [    1.188053] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 28 15:24:56 node-4 kernel: [    1.188056] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 28 15:24:56 node-4 kernel: [    1.203799] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 28 15:24:56 node-4 kernel: [    1.209036] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 28 15:24:56 node-4 kernel: [    1.214383] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 28 15:24:56 node-4 kernel: [    1.225115] usb usb2: Product: EHCI Host Controller
Jul 28 15:24:56 node-4 kernel: [    1.230666] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 28 15:24:56 node-4 kernel: [    1.236304] usb usb2: SerialNumber: 0000:00:1d.0
Jul 28 15:24:56 node-4 kernel: [    1.241904] hub 2-0:1.0: USB hub found
Jul 28 15:24:56 node-4 kernel: [    1.247330] hub 2-0:1.0: 2 ports detected
Jul 28 15:24:56 node-4 kernel: [    1.252696] ehci-platform: EHCI generic platform driver
Jul 28 15:24:56 node-4 kernel: [    1.257963] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 28 15:24:56 node-4 kernel: [    1.263315] ohci-pci: OHCI PCI platform driver
Jul 28 15:24:56 node-4 kernel: [    1.268663] ohci-platform: OHCI generic platform driver
Jul 28 15:24:56 node-4 kernel: [    1.273896] uhci_hcd: USB Universal Host Controller Interface driver
Jul 28 15:24:56 node-4 kernel: [    1.279295] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 28 15:24:56 node-4 kernel: [    1.479562] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 28 15:24:56 node-4 kernel: [    1.799292] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Jul 28 15:24:56 node-4 kernel: [    1.811614] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 28 15:24:56 node-4 kernel: [    1.817219] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 15:24:56 node-4 kernel: [    1.822878] hub 1-1:1.0: USB hub found
Jul 28 15:24:56 node-4 kernel: [    1.828351] hub 1-1:1.0: 6 ports detected
Jul 28 15:24:56 node-4 kernel: [    1.943169] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 28 15:24:56 node-4 kernel: [    2.317634] i8042: No controller found
Jul 28 15:24:56 node-4 kernel: [    2.323161] mousedev: PS/2 mouse device common for all mice
Jul 28 15:24:56 node-4 kernel: [    2.328861] rtc_cmos 00:02: RTC can wake from S4
Jul 28 15:24:56 node-4 kernel: [    2.331614] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 28 15:24:56 node-4 kernel: [    2.331614] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 28 15:24:56 node-4 kernel: [    2.332117] hub 2-1:1.0: USB hub found
Jul 28 15:24:56 node-4 kernel: [    2.332367] hub 2-1:1.0: 8 ports detected
Jul 28 15:24:56 node-4 kernel: [    2.357312] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 28 15:24:56 node-4 kernel: [    2.363122] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 28 15:24:56 node-4 kernel: [    2.374499] device-mapper: uevent: version 1.0.3
Jul 28 15:24:56 node-4 kernel: [    2.380257] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 28 15:24:56 node-4 kernel: [    2.391739] ledtrig-cpu: registered to indicate activity on CPUs
Jul 28 15:24:56 node-4 kernel: [    2.397790] TCP: cubic registered
Jul 28 15:24:56 node-4 kernel: [    2.403699] NET: Registered protocol family 10
Jul 28 15:24:56 node-4 kernel: [    2.409833] NET: Registered protocol family 17
Jul 28 15:24:56 node-4 kernel: [    2.415660] Key type dns_resolver registered
Jul 28 15:24:56 node-4 kernel: [    2.421689] Loading compiled-in X.509 certificates
Jul 28 15:24:56 node-4 kernel: [    2.427876] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 28 15:24:56 node-4 kernel: [    2.439435] registered taskstats version 1
Jul 28 15:24:56 node-4 kernel: [    2.447553] Key type trusted registered
Jul 28 15:24:56 node-4 kernel: [    2.455203] Key type encrypted registered
Jul 28 15:24:56 node-4 kernel: [    2.460707] AppArmor: AppArmor sha1 policy hashing enabled
Jul 28 15:24:56 node-4 kernel: [    2.466227] IMA: No TPM chip found, activating TPM-bypass!
Jul 28 15:24:56 node-4 kernel: [    2.472334] regulator-dummy: disabling
Jul 28 15:24:56 node-4 kernel: [    2.477854]   Magic number: 8:77:438
Jul 28 15:24:56 node-4 kernel: [    2.483577] rtc_cmos 00:02: setting system clock to 2016-07-28 15:24:21 UTC (1469719461)
Jul 28 15:24:56 node-4 kernel: [    2.496113] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 28 15:24:56 node-4 kernel: [    2.501828] EDD information not available.
Jul 28 15:24:56 node-4 kernel: [    2.507536] PM: Hibernation image not present or could not be loaded.
Jul 28 15:24:56 node-4 kernel: [    2.508408] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 28 15:24:56 node-4 kernel: [    2.519844] Write protecting the kernel read-only data: 12288k
Jul 28 15:24:56 node-4 kernel: [    2.526154] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 28 15:24:56 node-4 kernel: [    2.539074] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 28 15:24:56 node-4 kernel: [    2.571605] device-mapper: multipath: version 1.6.0 loaded
Jul 28 15:24:56 node-4 kernel: [    2.579532] systemd-udevd[214]: starting version 204
Jul 28 15:24:56 node-4 kernel: [    2.604989] md: linear personality registered for level -1
Jul 28 15:24:56 node-4 kernel: [    2.606900] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 28 15:24:56 node-4 kernel: [    2.625179] md: multipath personality registered for level -4
Jul 28 15:24:56 node-4 kernel: [    2.633351] md: raid0 personality registered for level 0
Jul 28 15:24:56 node-4 kernel: [    2.639997] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 28 15:24:56 node-4 kernel: [    2.646583] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 28 15:24:56 node-4 kernel: [    2.653054] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 28 15:24:56 node-4 kernel: [    2.655016] megasas: FW now in Ready state
Jul 28 15:24:56 node-4 kernel: [    2.655356] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.655443] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.655544] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.655705] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.655855] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.655969] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.656202] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.656311] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.656510] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.656624] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.656783] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.656946] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.657079] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.657210] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.657347] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.657549] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.658197] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 28 15:24:56 node-4 kernel: [    2.678901] md: raid1 personality registered for level 1
Jul 28 15:24:56 node-4 kernel: [    2.688472] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:3a wq/rq 256/512 mtu 1500
Jul 28 15:24:56 node-4 kernel: [    2.701968] 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 28 15:24:56 node-4 kernel: [    2.716047] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 15:24:56 node-4 kernel: [    2.723293] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.723299] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.723305] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.723311] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.723353] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.740327] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 28 15:24:56 node-4 kernel: [    2.747317] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 28 15:24:56 node-4 kernel: [    2.748870] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:3b wq/rq 256/512 mtu 1500
Jul 28 15:24:56 node-4 kernel: [    2.748872] 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 28 15:24:56 node-4 kernel: [    2.748873] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 15:24:56 node-4 kernel: [    2.749368] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.749500] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.749674] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.749761] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.750015] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.754552] raid6: sse2x1    7818 MB/s
Jul 28 15:24:56 node-4 kernel: [    2.766789] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:3c wq/rq 256/512 mtu 1500
Jul 28 15:24:56 node-4 kernel: [    2.766808] 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 28 15:24:56 node-4 kernel: [    2.766842] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 15:24:56 node-4 kernel: [    2.767078] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.767245] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.767287] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.767381] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.767810] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.782925] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:3d wq/rq 256/512 mtu 1500
Jul 28 15:24:56 node-4 kernel: [    2.782949] 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 28 15:24:56 node-4 kernel: [    2.782979] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 28 15:24:56 node-4 kernel: [    2.783259] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.783358] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.783442] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.783577] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.783800] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 28 15:24:56 node-4 kernel: [    2.822567] raid6: sse2x2   12245 MB/s
Jul 28 15:24:56 node-4 kernel: [    2.890603] raid6: sse2x4    9560 MB/s
Jul 28 15:24:56 node-4 kernel: [    2.924433] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 28 15:24:56 node-4 kernel: [    2.931025] usb 2-1.4: Manufacturer: Avocent
Jul 28 15:24:56 node-4 kernel: [    2.937466] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 28 15:24:56 node-4 kernel: [    2.958323] raid6: avx2x1   14310 MB/s
Jul 28 15:24:56 node-4 kernel: [    3.030261] raid6: avx2x2   18845 MB/s
Jul 28 15:24:56 node-4 kernel: [    3.102195] raid6: avx2x4   21320 MB/s
Jul 28 15:24:56 node-4 kernel: [    3.108170] raid6: using algorithm avx2x4 (21320 MB/s)
Jul 28 15:24:56 node-4 kernel: [    3.114078] raid6: using avx2x2 recovery algorithm
Jul 28 15:24:56 node-4 kernel: [    3.119765] megasas:IOC Init cmd success
Jul 28 15:24:56 node-4 kernel: [    3.119767] Switched to clocksource tsc
Jul 28 15:24:56 node-4 kernel: [    3.131481] xor: automatically using best checksumming function:
Jul 28 15:24:56 node-4 kernel: [    3.137150] hidraw: raw HID events driver (C) Jiri Kosina
Jul 28 15:24:56 node-4 kernel: [    3.145277] usbcore: registered new interface driver usbhid
Jul 28 15:24:56 node-4 kernel: [    3.150886] usbhid: USB HID core driver
Jul 28 15:24:56 node-4 kernel: [    3.156354] megasas: INIT adapter done
Jul 28 15:24:56 node-4 kernel: [    3.162512] 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 28 15:24:56 node-4 kernel: [    3.173355] 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 28 15:24:56 node-4 kernel: [    3.174118]    avx       : 35578.000 MB/sec
Jul 28 15:24:56 node-4 kernel: [    3.190170] 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 28 15:24:56 node-4 kernel: [    3.201499] async_tx: api initialized (async)
Jul 28 15:24:56 node-4 kernel: [    3.201665] 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 28 15:24:56 node-4 kernel: [    3.201723] 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 28 15:24:56 node-4 kernel: [    3.202021] 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 28 15:24:56 node-4 kernel: [    3.230096] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 28 15:24:56 node-4 kernel: [    3.230472] scsi0 : LSI SAS based MegaRAID driver
Jul 28 15:24:56 node-4 kernel: [    3.237602] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 15:24:56 node-4 kernel: [    3.249144] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 28 15:24:56 node-4 kernel: [    3.253378] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 28 15:24:56 node-4 kernel: [    3.253514] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 28 15:24:56 node-4 kernel: [    3.253841] sd 0:2:0:0: [sda] Write Protect is off
Jul 28 15:24:56 node-4 kernel: [    3.253842] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 28 15:24:56 node-4 kernel: [    3.253940] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 28 15:24:56 node-4 kernel: [    3.280418]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Jul 28 15:24:56 node-4 kernel: [    3.282077] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 28 15:24:56 node-4 kernel: [    3.340239] md: raid6 personality registered for level 6
Jul 28 15:24:56 node-4 kernel: [    3.347444] md: raid5 personality registered for level 5
Jul 28 15:24:56 node-4 kernel: [    3.354433] md: raid4 personality registered for level 4
Jul 28 15:24:56 node-4 kernel: [    3.364155] md: raid10 personality registered for level 10
Jul 28 15:24:56 node-4 kernel: [    3.419128] multipathd (361): /proc/361/oom_adj is deprecated, please use /proc/361/oom_score_adj instead.
Jul 28 15:24:56 node-4 kernel: [    3.459996] random: lvm urandom read with 30 bits of entropy available
Jul 28 15:24:56 node-4 kernel: [    3.652354] bio: create slab <bio-1> at 1
Jul 28 15:24:56 node-4 kernel: [    4.602169] EXT4-fs (dm-5): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 15:24:56 node-4 kernel: [    5.288060] random: nonblocking pool is initialized
Jul 28 15:24:56 node-4 kernel: [    5.316488] EXT4-fs (dm-5): re-mounted. Opts: errors=panic
Jul 28 15:24:56 node-4 kernel: [    5.397546] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 28 15:24:56 node-4 kernel: [    5.522183] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 28 15:24:56 node-4 kernel: [    5.564088] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 28 15:24:56 node-4 kernel: [    5.621813] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 15:24:56 node-4 kernel: [    5.823832] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 28 15:24:56 node-4 kernel: [    5.898523] XFS (dm-1): Mounting Filesystem
Jul 28 15:24:56 node-4 kernel: [    6.227810] XFS (dm-1): Ending clean mount
Jul 28 15:24:56 node-4 kernel: [    6.268379] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 15:24:56 node-4 kernel: [    6.297857] XFS (dm-2): Mounting Filesystem
Jul 28 15:24:56 node-4 kernel: [    6.378253] XFS (dm-2): Ending clean mount
Jul 28 15:24:56 node-4 kernel: [    6.529167] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
Jul 28 15:24:56 node-4 kernel: [    8.229693] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 28 15:24:56 node-4 kernel: [    8.255949] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 28 15:24:56 node-4 kernel: [    8.404158] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 28 15:24:56 node-4 kernel: [    8.404168] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 28 15:24:56 node-4 kernel: [    8.404176] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 28 15:24:56 node-4 kernel: [    8.404183] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 28 15:24:56 node-4 kernel: [    8.439414] systemd-udevd[804]: starting version 204
Jul 28 15:24:56 node-4 kernel: [    8.629344] power_meter ACPI000D:00: Found ACPI power meter.
Jul 28 15:24:56 node-4 kernel: [    8.629368] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 28 15:24:56 node-4 kernel: [    8.637823] IPMI System Interface driver.
Jul 28 15:24:56 node-4 kernel: [    8.637913] ipmi_si: probing via ACPI
Jul 28 15:24:56 node-4 kernel: [    8.637931] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 28 15:24:56 node-4 kernel: [    8.637932] ipmi_si: Adding ACPI-specified kcs state machine
Jul 28 15:24:56 node-4 kernel: [    8.637953] ipmi_si: probing via SMBIOS
Jul 28 15:24:56 node-4 kernel: [    8.637955] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 15:24:56 node-4 kernel: [    8.637956] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 28 15:24:56 node-4 kernel: [    8.637958] ipmi_si: probing via SPMI
Jul 28 15:24:56 node-4 kernel: [    8.637959] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 28 15:24:56 node-4 kernel: [    8.637960] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 28 15:24:56 node-4 kernel: [    8.637962] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 28 15:24:56 node-4 kernel: [    8.680330] wmi: Mapper loaded
Jul 28 15:24:56 node-4 kernel: [    8.713585] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 28 15:24:56 node-4 kernel: [    8.725708] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 28 15:24:56 node-4 kernel: [    8.725713] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 15:24:56 node-4 kernel: [    8.725715] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 28 15:24:56 node-4 kernel: [    8.725717] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 28 15:24:56 node-4 kernel: [    8.725729] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 28 15:24:56 node-4 kernel: [    8.777825] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 28 15:24:56 node-4 kernel: [    8.777829] ipmi_si 00:09: IPMI kcs interface initialized
Jul 28 15:24:56 node-4 kernel: [    8.797818] systemd-udevd[822]: renamed network interface eth1 to enp7s0
Jul 28 15:24:56 node-4 kernel: [    8.821759] systemd-udevd[823]: renamed network interface eth2 to enp8s0
Jul 28 15:24:56 node-4 kernel: [    8.845725] systemd-udevd[832]: renamed network interface eth0 to enp6s0
Jul 28 15:24:56 node-4 kernel: [    8.877678] systemd-udevd[848]: renamed network interface eth3 to enp9s0
Jul 28 15:24:56 node-4 kernel: [    9.161921] type=1400 audit(1469719468.179:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1096 comm="apparmor_parser"
Jul 28 15:24:56 node-4 kernel: [    9.162075] type=1400 audit(1469719468.179:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1096 comm="apparmor_parser"
Jul 28 15:24:56 node-4 kernel: [    9.162205] type=1400 audit(1469719468.179:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1096 comm="apparmor_parser"
Jul 28 15:24:56 node-4 kernel: [    9.168587] type=1400 audit(1469719468.183:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1093 comm="apparmor_parser"
Jul 28 15:24:56 node-4 kernel: [    9.168735] type=1400 audit(1469719468.183:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1093 comm="apparmor_parser"
Jul 28 15:24:56 node-4 kernel: [    9.168854] type=1400 audit(1469719468.183:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1093 comm="apparmor_parser"
Jul 28 15:24:56 node-4 kernel: [    9.180243] type=1400 audit(1469719468.195:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1095 comm="apparmor_parser"
Jul 28 15:24:56 node-4 kernel: [    9.180487] type=1400 audit(1469719468.195:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1095 comm="apparmor_parser"
Jul 28 15:24:56 node-4 kernel: [    9.180699] type=1400 audit(1469719468.195:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1095 comm="apparmor_parser"
Jul 28 15:24:56 node-4 kernel: [    9.184839] type=1400 audit(1469719468.199:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1094 comm="apparmor_parser"
Jul 28 15:24:56 node-4 kernel: [    9.760830] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Jul 28 15:24:56 node-4 kernel: [    9.769596] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Jul 28 15:24:56 node-4 kernel: [    9.986427] enic 0000:06:00.0 enp6s0: Link UP
Jul 28 15:24:56 node-4 kernel: [    9.987648] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 28 15:24:56 node-4 kernel: [    9.987653] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 28 15:24:56 node-4 kernel: [   20.236181] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 28 15:24:57 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 28 15:24:58 node-4 kernel: [   38.241369] init: failsafe main process (8434) killed by TERM signal
Jul 28 15:24:58 node-4 dbus[8456]: [system] AppArmor D-Bus mediation is enabled
Jul 28 15:24:58 node-4 kernel: [   38.423316] audit_printk_skb: 30 callbacks suppressed
Jul 28 15:24:58 node-4 kernel: [   38.423317] type=1400 audit(1469719498.247:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8559 comm="apparmor_parser"
Jul 28 15:24:58 node-4 kernel: [   38.423321] type=1400 audit(1469719498.247:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8559 comm="apparmor_parser"
Jul 28 15:24:58 node-4 kernel: [   38.423323] type=1400 audit(1469719498.247:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8559 comm="apparmor_parser"
Jul 28 15:24:58 node-4 kernel: [   38.423548] type=1400 audit(1469719498.247:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8559 comm="apparmor_parser"
Jul 28 15:24:58 node-4 kernel: [   38.423549] type=1400 audit(1469719498.247:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8559 comm="apparmor_parser"
Jul 28 15:24:58 node-4 kernel: [   38.423680] type=1400 audit(1469719498.247:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8559 comm="apparmor_parser"
Jul 28 15:24:58 node-4 kernel: [   38.426493] type=1400 audit(1469719498.251:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8560 comm="apparmor_parser"
Jul 28 15:24:58 node-4 kernel: [   38.524945] type=1400 audit(1469719498.351:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8562 comm="apparmor_parser"
Jul 28 15:24:58 node-4 anacron[8626]: Anacron 2.3 started on 2016-07-28
Jul 28 15:24:58 node-4 cron[8592]: (CRON) INFO (pidfile fd = 3)
Jul 28 15:24:58 node-4 cron[8634]: (CRON) STARTUP (fork ok)
Jul 28 15:24:58 node-4 anacron[8626]: Will run job `cron.daily' in 5 min.
Jul 28 15:24:58 node-4 anacron[8626]: Will run job `cron.weekly' in 10 min.
Jul 28 15:24:58 node-4 anacron[8626]: Will run job `cron.monthly' in 15 min.
Jul 28 15:24:58 node-4 anacron[8626]: Jobs will be executed sequentially
Jul 28 15:24:58 node-4 cron[8634]: (CRON) INFO (Running @reboot jobs)
Jul 28 15:24:58 node-4 multipathd: path checkers start up
Jul 28 15:24:59 node-4 postfix/master[8771]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 28 15:25:01 node-4 CRON[8946]: (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 28 15:25:02 node-4 puppet-agent[8966]: Reopening log files
Jul 28 15:25:04 node-4 puppet-agent[8966]: Could not request certificate: Connection refused - connect(2)
Jul 28 15:25:14 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 15:25:14 node-4 nailgun-agent: D, [2016-07-28T15:25:01.738648 #8949] DEBUG -- : Sleep for 13 seconds before sending request
Jul 28 15:25:14 node-4 nailgun-agent: I, [2016-07-28T15:25:14.386307 #8949]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 15:25:14 node-4 puppet-user[9045]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 28 15:25:14 node-4 puppet-user[9045]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 28 15:25:15 node-4 nailgun-agent: D, [2016-07-28T15:25:15.241295 #8949] DEBUG -- : Trying to create host using https://10.20.0.2:8443/api
Jul 28 15:25:15 node-4 puppet-user[9045]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 28 15:25:15 node-4 puppet-user[9045]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 28 15:25:15 node-4 puppet-user[9045]: Finished catalog run in 0.50 seconds
Jul 28 15:25:16 node-4 multipathd: uevent trigger error
Jul 28 15:25:16 node-4 puppet-user[9599]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 15:25:16 node-4 puppet-user[9599]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Jul 28 15:25:17 node-4 puppet-user[9599]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 28 15:25:17 node-4 puppet-user[9599]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 28 15:25:17 node-4 puppet-user[9599]: (/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 28 15:25:17 node-4 puppet-user[9599]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 28 15:25:17 node-4 puppet-user[9599]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 28 15:25:17 node-4 puppet-user[9599]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 28 15:25:17 node-4 puppet-user[9599]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 28 15:25:17 node-4 puppet-user[9599]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 28 15:25:17 node-4 puppet-user[9599]: Finished catalog run in 0.08 seconds
Jul 28 15:25:18 node-4 puppet-user[10057]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 28 15:25:18 node-4 puppet-user[10057]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Jul 28 15:25:18 node-4 puppet-user[10057]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 28 15:25:18 node-4 puppet-user[10057]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 28 15:25:18 node-4 puppet-user[10057]: Finished catalog run in 0.04 seconds
Jul 28 15:25:20 node-4 puppet-user[10651]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 28 15:25:20 node-4 puppet-user[10651]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 28 15:25:20 node-4 puppet-user[10651]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 28 15:25:20 node-4 puppet-user[10651]: Finished catalog run in 0.04 seconds
Jul 28 15:25:21 node-4 puppet-user[11109]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 28 15:25:21 node-4 puppet-user[11109]: Compiled catalog for node-4.domain.tld in environment production in 0.20 seconds
Jul 28 15:25:21 node-4 puppet-user[11109]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 28 15:25:22 node-4 puppet-user[11109]: (/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 28 15:25:22 node-4 puppet-user[11109]: (/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 28 15:25:23 node-4 puppet-user[11109]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/Rsync::Get[/etc/fuel/plugins/bgpvpn-0.9/]/Exec[rsync /etc/fuel/plugins/bgpvpn-0.9/]/returns) executed successfully
Jul 28 15:25:23 node-4 puppet-user[11109]: Finished catalog run in 1.19 seconds
Jul 28 15:25:24 node-4 puppet-user[11650]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 28 15:25:24 node-4 puppet-user[11650]: Compiled catalog for node-4.domain.tld in environment production in 0.30 seconds
Jul 28 15:25:24 node-4 puppet-user[11650]: (/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 28 15:25:24 node-4 puppet-user[11650]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_setup_repositories/Apt::Source[bgpvpn-0.9.0]/Apt::Setting[list-bgpvpn-0.9.0]/File[/etc/apt/sources.list.d/bgpvpn-0.9.0.list]/ensure) created
Jul 28 15:25:25 node-4 puppet-user[11650]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 28 15:25:25 node-4 puppet-user[11650]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 28 15:25:25 node-4 puppet-user[11650]: (/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 28 15:25:25 node-4 puppet-user[11650]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 28 15:25:25 node-4 puppet-user[11650]: Finished catalog run in 0.42 seconds
Jul 28 15:25:26 node-4 puppet-user[12135]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 28 15:25:26 node-4 puppet-user[12135]: Compiled catalog for node-4.domain.tld in environment production in 0.17 seconds
Jul 28 15:25:27 node-4 puppet-user[12135]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 28 15:25:27 node-4 kernel: [   67.656849] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 28 15:25:27 node-4 kernel: [   67.656902] 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 28 15:25:27 node-4 puppet-user[12135]: (/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 28 15:25:27 node-4 puppet-user[12135]: Finished catalog run in 0.08 seconds
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.394286 #8949] DEBUG -- : Trying to find block devices
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.394390 #8949] DEBUG -- : Found block device: sda
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.394428 #8949] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.394451 #8949] DEBUG -- : Trying to get list of physical devices
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.394605 #8949] DEBUG -- : Getting udev properties for device: sda
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.396346 #8949] 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"=>"0x618e72837273a8901cc7884
Jul 28 15:25:27 node-4 nailgun-agent: d05b001c0", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"40229", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.396374 #8949] DEBUG -- : Trying to find out if device sda is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.396434 #8949] DEBUG -- : Device sda removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.396451 #8949] DEBUG -- : Device sda seems to be appropriate
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.396862 #8949] DEBUG -- : Getting udev properties for device: dm-0
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.398324 #8949] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mongo-mongodb /dev/disk/by-id/dm-uuid-LVM-pjFFnKBdVO9NM7LsQQ3Tx4u2pKSDqegL3x6i3tGDvvCJ4IO4Re8C0LHsdjyYLwyF /dev/disk/by-uuid/b86d5e9e-ad0c-4e16-b942-905bdeeae0c8 /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-pjFFnKBdVO9NM7LsQQ3Tx4u2pKSDqegL3x6i3tGDvvCJ4IO4Re8C0LHsdjyYLwyF", "DM_VG_NAME"=>"mongo", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"b86d5e9e-ad0c-4e16-b942-905bdeeae0c8", "ID_FS_UUID_ENC"=>"b86d5e9e-ad0c-4e16-b942-905bdeeae0c8", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"10
Jul 28 15:25:27 node-4 nailgun-agent: 515", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.398349 #8949] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.398379 #8949] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.398409 #8949] DEBUG -- : Device dm-0 seems to be appropriate
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.398440 #8949] DEBUG -- : Getting udev properties for device: dm-1
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.399853 #8949] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-V3x3x2Xuu7QnILvSHV3PswA3JSXsf1Vw68xYLVS35enGkKroCECFVgawfNq6tQ18 /dev/disk/by-uuid/73785b65-ec07-430a-be38-fad9ed591dca /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-V3x3x2Xuu7QnILvSHV3PswA3JSXsf1Vw68xYLVS35enGkKroCECFVgawfNq6tQ18", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"73785b65-ec07-430a-be38-fad9ed591dca", "ID_FS_UUID_ENC"=>"73785b65-ec07-430a-be38-fad9ed591dca", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"39349", "nomdmonddf"=>"1", "nomd
Jul 28 15:25:27 node-4 nailgun-agent: monisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.399946 #8949] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.399978 #8949] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.399991 #8949] DEBUG -- : Device dm-1 seems to be appropriate
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.400007 #8949] DEBUG -- : Getting udev properties for device: dm-2
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.401443 #8949] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-Y0GpsSKQCSHW44hMwXmLVNKmIq8ympwrCaCSmkQPRhcImuU81n3pY1t3ASG5RfRW /dev/disk/by-uuid/21401627-4d4f-46bd-98a1-aca8cf9d989b /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-Y0GpsSKQCSHW44hMwXmLVNKmIq8ympwrCaCSmkQPRhcImuU81n3pY1t3ASG5RfRW", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"21401627-4d4f-46bd-98a1-aca8cf9d989b", "ID_FS_UUID_ENC"=>"21401627-4d4f-46bd-98a1-aca8cf9d989b", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60
Jul 28 15:25:27 node-4 nailgun-agent: 052", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.401471 #8949] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.401514 #8949] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.401540 #8949] DEBUG -- : Device dm-2 seems to be appropriate
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.401555 #8949] DEBUG -- : Getting udev properties for device: dm-3
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.402990 #8949] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-yr65utmZaFkmXbGHWc2G7hDfwUJ5rbJ3c7NMXe7HB3Y2kkPwwIplQUm7w372Fo3g /dev/disk/by-uuid/9d1da32a-2c81-44e4-95d2-1dc3e5f2ec73 /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-yr65utmZaFkmXbGHWc2G7hDfwUJ5rbJ3c7NMXe7HB3Y2kkPwwIplQUm7w372Fo3g", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"9d1da32a-2c81-44e4-95d2-1dc3e5f2ec73", "ID_FS_UUID_ENC"=>"9d1da32a-2c81-44e4-95d2-1dc3e5f2ec73", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61215", "nomdmond
Jul 28 15:25:27 node-4 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.403033 #8949] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.403077 #8949] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.403092 #8949] DEBUG -- : Device dm-3 seems to be appropriate
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.403107 #8949] DEBUG -- : Getting udev properties for device: dm-4
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.404543 #8949] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-W2q8VEamPIBcZUrOSvtNuTPLXgv0GZX92N4EExQwp3QeS2e8BYD36J8MI0OxzWSV /dev/disk/by-uuid/5cd6f398-cb86-4d02-8b39-7701849b5af9 /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-W2q8VEamPIBcZUrOSvtNuTPLXgv0GZX92N4EExQwp3QeS2e8BYD36J8MI0OxzWSV", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"5cd6f398-cb86-4d02-8b39-7701849b5af9", "ID_FS_UUID_ENC"=>"5cd6f398-cb86-4d02-8b39-7701849b5af9", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"72160", "nomdmonddf"=>"1", 
Jul 28 15:25:27 node-4 nailgun-agent: "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.404587 #8949] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.404630 #8949] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.404645 #8949] DEBUG -- : Device dm-4 seems to be appropriate
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.404661 #8949] DEBUG -- : Getting udev properties for device: dm-5
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.406107 #8949] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-MU98lJQ0n4oZ00R9F6bEFZEBqnLoLLtFzT0fFddgB5S9LZ0v2xVUclenlR3DbNvb /dev/disk/by-uuid/58df8f29-78be-4481-bc4b-3ae02f2b343c /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-MU98lJQ0n4oZ00R9F6bEFZEBqnLoLLtFzT0fFddgB5S9LZ0v2xVUclenlR3DbNvb", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"58df8f29-78be-4481-bc4b-3ae02f2b343c", "ID_FS_UUID_ENC"=>"58df8f29-78be-4481-bc4b-3ae02f2b343c", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79538", "nomdmonddf"=>"1", "nomd
Jul 28 15:25:27 node-4 nailgun-agent: monisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.406135 #8949] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.406196 #8949] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.406211 #8949] DEBUG -- : Device dm-5 seems to be appropriate
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.406227 #8949] DEBUG -- : Getting udev properties for device: dm-6
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.407645 #8949] DEBUG -- : Device dm-6 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-MU98lJQ0n4oZ00R9F6bEFZEBqnLoLLtFIFPjkHRReJ168x9XMlAkQhUADmsj6bUB /dev/disk/by-uuid/8a488225-e1c9-4f5a-a55a-273569500ab1 /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-MU98lJQ0n4oZ00R9F6bEFZEBqnLoLLtFIFPjkHRReJ168x9XMlAkQhUADmsj6bUB", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"8a488225-e1c9-4f5a-a55a-273569500ab1", "ID_FS_UUID_ENC"=>"8a488225-e1c9-4f5a-a55a-273569500ab1", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79896", "nomdmonddf"=>"1", "nomdmonisw"
Jul 28 15:25:27 node-4 nailgun-agent: =>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.407671 #8949] DEBUG -- : Trying to find out if device dm-6 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.407715 #8949] DEBUG -- : Device dm-6 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.407731 #8949] DEBUG -- : Device dm-6 seems to be appropriate
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.407760 #8949] DEBUG -- : Getting udev properties for device: ram0
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.409072 #8949] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57737", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.409098 #8949] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.409158 #8949] DEBUG -- : Device ram0 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.409179 #8949] DEBUG -- : Getting udev properties for device: ram1
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.410463 #8949] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57833", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.410485 #8949] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.410517 #8949] DEBUG -- : Device ram1 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.410536 #8949] DEBUG -- : Getting udev properties for device: ram2
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.411800 #8949] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59111", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.411821 #8949] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.411878 #8949] DEBUG -- : Device ram2 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.411897 #8949] DEBUG -- : Getting udev properties for device: ram3
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.413210 #8949] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59198", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.413231 #8949] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.413268 #8949] DEBUG -- : Device ram3 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.413298 #8949] DEBUG -- : Getting udev properties for device: ram4
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.414583 #8949] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59299", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.414603 #8949] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.414634 #8949] DEBUG -- : Device ram4 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.414669 #8949] DEBUG -- : Getting udev properties for device: ram5
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.415916 #8949] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59425", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.415945 #8949] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.415987 #8949] DEBUG -- : Device ram5 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.416008 #8949] DEBUG -- : Getting udev properties for device: ram6
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.417331 #8949] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59465", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.417356 #8949] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.417403 #8949] DEBUG -- : Device ram6 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.417424 #8949] DEBUG -- : Getting udev properties for device: ram7
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.418730 #8949] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59570", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.418754 #8949] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.418798 #8949] DEBUG -- : Device ram7 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.418819 #8949] DEBUG -- : Getting udev properties for device: ram8
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.420109 #8949] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59813", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.420144 #8949] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.420177 #8949] DEBUG -- : Device ram8 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.420195 #8949] DEBUG -- : Getting udev properties for device: ram9
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.421485 #8949] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59945", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.421525 #8949] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.421558 #8949] DEBUG -- : Device ram9 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.421576 #8949] DEBUG -- : Getting udev properties for device: loop0
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.422883 #8949] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56738", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.422904 #8949] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.422948 #8949] DEBUG -- : Device loop0 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.422972 #8949] DEBUG -- : Getting udev properties for device: loop1
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.424249 #8949] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56910", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.424269 #8949] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.424314 #8949] DEBUG -- : Device loop1 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.424332 #8949] DEBUG -- : Getting udev properties for device: loop2
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.425624 #8949] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"56987", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.425643 #8949] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.425683 #8949] DEBUG -- : Device loop2 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.425701 #8949] DEBUG -- : Getting udev properties for device: loop3
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.426966 #8949] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57083", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.426987 #8949] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.427028 #8949] DEBUG -- : Device loop3 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.427056 #8949] DEBUG -- : Getting udev properties for device: loop4
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.428316 #8949] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57281", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.428335 #8949] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.428370 #8949] DEBUG -- : Device loop4 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.428397 #8949] DEBUG -- : Getting udev properties for device: loop5
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.429689 #8949] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57371", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.429718 #8949] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.434853 #8949] DEBUG -- : Device loop5 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.434875 #8949] DEBUG -- : Getting udev properties for device: loop6
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.436289 #8949] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57482", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.436310 #8949] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.436340 #8949] DEBUG -- : Device loop6 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.436387 #8949] DEBUG -- : Getting udev properties for device: loop7
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.438113 #8949] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57554", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.438134 #8949] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.438160 #8949] DEBUG -- : Device loop7 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.438179 #8949] DEBUG -- : Getting udev properties for device: ram10
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.439452 #8949] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"57933", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.439471 #8949] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.439500 #8949] DEBUG -- : Device ram10 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.439517 #8949] DEBUG -- : Getting udev properties for device: ram11
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.440786 #8949] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58500", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.440807 #8949] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.440838 #8949] DEBUG -- : Device ram11 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.440856 #8949] DEBUG -- : Getting udev properties for device: ram12
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.442178 #8949] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58651", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.442197 #8949] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.442226 #8949] DEBUG -- : Device ram12 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.442242 #8949] DEBUG -- : Getting udev properties for device: ram13
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.443505 #8949] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58814", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.443525 #8949] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.443554 #8949] DEBUG -- : Device ram13 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.443571 #8949] DEBUG -- : Getting udev properties for device: ram14
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.444814 #8949] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"58897", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.444833 #8949] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.444897 #8949] DEBUG -- : Device ram14 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.444914 #8949] DEBUG -- : Getting udev properties for device: ram15
Jul 28 15:25:27 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446182 #8949] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"59028", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446204 #8949] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446231 #8949] DEBUG -- : Device ram15 removable parameter: "0"
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446292 #8949] 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 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446306 #8949] DEBUG -- : Block device seems to be physical data storage: sda
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446343 #8949] DEBUG -- : Found block device: dm-0
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446357 #8949] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446381 #8949] DEBUG -- : Found block device: dm-1
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446392 #8949] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446401 #8949] DEBUG -- : Found block device: dm-2
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446410 #8949] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446418 #8949] DEBUG -- : Found block device: dm-3
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446427 #8949] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446473 #8949] DEBUG -- : Found block device: dm-4
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446484 #8949] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446493 #8949] DEBUG -- : Found block device: dm-5
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446503 #8949] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446512 #8949] DEBUG -- : Found block device: dm-6
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446523 #8949] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446531 #8949] DEBUG -- : Found block device: ram0
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446541 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446549 #8949] DEBUG -- : Found block device: ram1
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446559 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446603 #8949] DEBUG -- : Found block device: ram2
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446613 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446621 #8949] DEBUG -- : Found block device: ram3
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446631 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446639 #8949] DEBUG -- : Found block device: ram4
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446648 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446656 #8949] DEBUG -- : Found block device: ram5
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446665 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446674 #8949] DEBUG -- : Found block device: ram6
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446707 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446716 #8949] DEBUG -- : Found block device: ram7
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446727 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446734 #8949] DEBUG -- : Found block device: ram8
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446744 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446752 #8949] DEBUG -- : Found block device: ram9
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446761 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446769 #8949] DEBUG -- : Found block device: loop0
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446778 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446787 #8949] DEBUG -- : Found block device: loop1
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446830 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446839 #8949] DEBUG -- : Found block device: loop2
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446848 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446856 #8949] DEBUG -- : Found block device: loop3
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446866 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446874 #8949] DEBUG -- : Found block device: loop4
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446883 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446891 #8949] DEBUG -- : Found block device: loop5
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446901 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446947 #8949] DEBUG -- : Found block device: loop6
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446956 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446964 #8949] DEBUG -- : Found block device: loop7
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446972 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446980 #8949] DEBUG -- : Found block device: ram10
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446988 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.446996 #8949] DEBUG -- : Found block device: ram11
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.447005 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.447014 #8949] DEBUG -- : Found block device: ram12
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.447048 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.447057 #8949] DEBUG -- : Found block device: ram13
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.447067 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.447074 #8949] DEBUG -- : Found block device: ram14
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.447083 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.447092 #8949] DEBUG -- : Found block device: ram15
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.447101 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.447130 #8949] 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 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.525460 #8949] DEBUG -- : Response: status: 403 body: {"message": "Only bootstrap nodes are allowed to be registered.", "errors": []}
Jul 28 15:25:27 node-4 nailgun-agent: D, [2016-07-28T15:25:27.525531 #8949] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 28 15:25:28 node-4 puppet-user[12785]: (Scope(Class[main])) MODULAR: sync_time
Jul 28 15:25:28 node-4 puppet-user[12785]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 28 15:25:29 node-4 ntpdate[13208]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 28 15:25:35 node-4 ntpdate[13208]: adjust time server 10.20.0.2 offset 0.001133 sec
Jul 28 15:25:35 node-4 puppet-user[12785]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 28 15:25:35 node-4 puppet-user[12785]: Finished catalog run in 6.19 seconds
Jul 28 15:25:39 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407315 #8949] DEBUG -- : Trying to find block devices
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407400 #8949] DEBUG -- : Found block device: sda
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407428 #8949] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407446 #8949] DEBUG -- : Block device seems to be physical data storage: sda
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407466 #8949] DEBUG -- : Found block device: dm-0
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407479 #8949] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407515 #8949] DEBUG -- : Found block device: dm-1
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407527 #8949] DEBUG -- : Block device info: {"size"=>"2228699136", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407537 #8949] DEBUG -- : Found block device: dm-2
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407548 #8949] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407557 #8949] DEBUG -- : Found block device: dm-3
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407566 #8949] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407575 #8949] DEBUG -- : Found block device: dm-4
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407585 #8949] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407594 #8949] DEBUG -- : Found block device: dm-5
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407616 #8949] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407641 #8949] DEBUG -- : Found block device: dm-6
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407651 #8949] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407660 #8949] DEBUG -- : Found block device: ram0
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407670 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407678 #8949] DEBUG -- : Found block device: ram1
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407688 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407717 #8949] DEBUG -- : Found block device: ram2
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407726 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407735 #8949] DEBUG -- : Found block device: ram3
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407745 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407754 #8949] DEBUG -- : Found block device: ram4
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407763 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407772 #8949] DEBUG -- : Found block device: ram5
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407782 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407809 #8949] DEBUG -- : Found block device: ram6
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407819 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407828 #8949] DEBUG -- : Found block device: ram7
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407837 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407845 #8949] DEBUG -- : Found block device: ram8
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407854 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407863 #8949] DEBUG -- : Found block device: ram9
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407884 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407892 #8949] DEBUG -- : Found block device: loop0
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407901 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407910 #8949] DEBUG -- : Found block device: loop1
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407931 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407940 #8949] DEBUG -- : Found block device: loop2
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407949 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407970 #8949] DEBUG -- : Found block device: loop3
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407979 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407988 #8949] DEBUG -- : Found block device: loop4
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.407998 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408021 #8949] DEBUG -- : Found block device: loop5
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408031 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408040 #8949] DEBUG -- : Found block device: loop6
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408049 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408057 #8949] DEBUG -- : Found block device: loop7
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408081 #8949] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408090 #8949] DEBUG -- : Found block device: ram10
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408100 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408108 #8949] DEBUG -- : Found block device: ram11
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408130 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408139 #8949] DEBUG -- : Found block device: ram12
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408149 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408175 #8949] DEBUG -- : Found block device: ram13
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408184 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408193 #8949] DEBUG -- : Found block device: ram14
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408202 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408210 #8949] DEBUG -- : Found block device: ram15
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408219 #8949] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.408269 #8949] 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 28 15:25:39 node-4 nailgun-agent: D, [2016-07-28T15:25:39.541214 #8949] DEBUG -- : Response: status: 200 body: {"id": 4}
Jul 28 15:25:39 node-4 nailgun-agent: I, [2016-07-28T15:25:39.541418 #8949]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 28 15:25:43 node-4 kernel: [   83.870282] init: plymouth-upstart-bridge main process ended, respawning
Jul 28 15:25:43 node-4 puppet-agent[8966]: Could not run: SIGTERM
Jul 28 15:25:43 node-4 kernel: [   84.174367] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 28 15:25:43 node-4 ec2: 
Jul 28 15:25:43 node-4 ec2: #############################################################
Jul 28 15:25:43 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 28 15:25:43 node-4 ec2: 1024 c3:e7:c2:c7:43:a5:b4:51:a0:68:74:14:5e:82:4f:55  root@node-4.domain.tld (DSA)
Jul 28 15:25:43 node-4 ec2: 256 77:16:01:bf:0e:38:b7:a6:e5:41:96:9e:5f:3f:9a:43  root@node-4.domain.tld (ECDSA)
Jul 28 15:25:43 node-4 ec2: 256 12:96:27:aa:ec:e5:f1:c1:c4:1c:ed:18:d5:33:90:81  root@node-4.domain.tld (ED25519)
Jul 28 15:25:43 node-4 ec2: 2048 36:a5:a5:ea:cb:ae:d2:79:86:9b:2a:c2:3a:5f:9f:90  root@node-4.domain.tld (RSA)
Jul 28 15:25:43 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 28 15:25:43 node-4 ec2: #############################################################
Jul 28 15:26:01 node-4 CRON[13867]: (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 28 15:26:12 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 15:26:12 node-4 nailgun-agent: I, [2016-07-28T15:26:12.723672 #13870]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 15:26:25 node-4 puppet-user[14026]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 28 15:26:25 node-4 puppet-user[14026]: Compiled catalog for node-4.domain.tld in environment production in 0.10 seconds
Jul 28 15:26:25 node-4 puppet-user[14026]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 28 15:26:25 node-4 puppet-user[14026]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/bgpvpn", "plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Jul 28 15:26:25 node-4 puppet-user[14026]: Finished catalog run in 0.08 seconds
Jul 28 15:26:25 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 15:26:25 node-4 nailgun-agent: I, [2016-07-28T15:26:25.797396 #13870]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 28 15:26:27 node-4 puppet-user[14651]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 28 15:26:28 node-4 puppet-user[14651]: Compiled catalog for node-4.domain.tld in environment production in 1.17 seconds
Jul 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:29 node-4 puppet-user[14651]: (/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 28 15:26:45 node-4 puppet-user[14651]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 28 15:26:45 node-4 puppet-user[14651]: Finished catalog run in 16.92 seconds
Jul 28 15:26:47 node-4 puppet-user[15535]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 28 15:26:48 node-4 puppet-user[15535]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Jul 28 15:26:53 node-4 puppet-user[15535]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 28 15:27:01 node-4 CRON[16830]: (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 28 15:27:20 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 15:27:20 node-4 nailgun-agent: I, [2016-07-28T15:27:20.978378 #16833]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 28 15:27:26 node-4 puppet-user[15535]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 28 15:27:26 node-4 puppet-user[15535]: Finished catalog run in 38.12 seconds
Jul 28 15:27:28 node-4 puppet-user[18164]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 28 15:27:28 node-4 puppet-user[18164]: Compiled catalog for node-4.domain.tld in environment production in 0.57 seconds
Jul 28 15:27:28 node-4 puppet-user[18164]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 28 15:27:28 node-4 puppet-user[18164]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 28 15:27:28 node-4 puppet-user[18164]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 28 15:27:28 node-4 puppet-user[18164]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 28 15:27:28 node-4 puppet-user[18164]: Finished catalog run in 0.13 seconds
Jul 28 15:27:30 node-4 puppet-user[18638]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 28 15:27:31 node-4 puppet-user[18638]: Compiled catalog for node-4.domain.tld in environment production in 0.84 seconds
Jul 28 15:27:31 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 28 15:27:31 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 28 15:27:31 node-4 crontab[19075]: (root) LIST (root)
Jul 28 15:27:31 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 28 15:27:31 node-4 crontab[19079]: (root) REPLACE (root)
Jul 28 15:27:33 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 28 15:27:34 node-4 nailgun-agent: I, [2016-07-28T15:27:33.993534 #16833]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 28 15:27:34 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 28 15:27:35 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 28 15:27:36 node-4 puppet-user[18638]: (/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 28 15:27:36 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8407" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 28 15:27:36 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 28 15:27:38 node-4 multipathd: uevent trigger error
<27>Jul 28 15:27:38 node-4 multipathd: uevent trigger error
<27>Jul 28 15:27:38 node-4 multipathd: uevent trigger error
<27>Jul 28 15:27:38 node-4 multipathd: uevent trigger error
<27>Jul 28 15:27:38 node-4 multipathd: uevent trigger error
<27>Jul 28 15:27:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:27:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:27:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:27:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:28:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:28:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:28:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:28:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:28:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:01 node-4 ntpdate[29249]: no servers can be used, exiting
<27>Jul 28 15:29:32 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:32 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:32 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:32 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:32 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:32 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:36 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:36 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:36 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:36 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:36 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:51 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:51 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:51 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:51 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:51 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:51 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:29:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:30:40 node-4 multipathd: uevent trigger error
<27>Jul 28 15:30:40 node-4 multipathd: uevent trigger error
<27>Jul 28 15:30:40 node-4 multipathd: uevent trigger error
<27>Jul 28 15:30:40 node-4 multipathd: uevent trigger error
<27>Jul 28 15:30:40 node-4 multipathd: uevent trigger error
<43>Jul 28 15:30:57 node-4 apache2_error [Thu Jul 28 15:30:53.640596 2016] [mpm_event:notice] [pid 8841:tid 139779991861120] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 15:30:57 node-4 apache2_error [Thu Jul 28 15:30:53.640744 2016] [core:notice] [pid 8841:tid 139779991861120] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 15:30:57 node-4 apache2_error [Thu Jul 28 15:30:56.739740 2016] [mpm_event:notice] [pid 8841:tid 139779991861120] AH00491: caught SIGTERM, shutting down
<27>Jul 28 15:31:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:01 node-4 multipathd: uevent trigger error
<43>Jul 28 15:31:07 node-4 apache2_error [Thu Jul 28 15:30:57.832157 2016] [mpm_worker:notice] [pid 9149:tid 140658979149696] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 15:31:07 node-4 apache2_error [Thu Jul 28 15:30:57.832202 2016] [core:notice] [pid 9149:tid 140658979149696] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 15:31:39 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 28 15:31:44 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:44 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:44 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:44 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:44 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:31:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:07 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:07 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:07 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:07 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:07 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:07 node-4 haproxy[19323]: Server odl-jetty/node-1 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 28 15:32:07 node-4 haproxy[19323]: proxy odl-jetty has no server available!
<129>Jul 28 15:32:09 node-4 haproxy[19323]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer4 timeout, check duration: 5000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 15:32:09 node-4 haproxy[19323]: proxy odl-neutron-endpoint has no server available!
<129>Jul 28 15:32:10 node-4 haproxy[20375]: 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 28 15:32:12 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:12 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:12 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:12 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:12 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:12 node-4 haproxy[20375]: Server odl-jetty/node-1 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 28 15:32:12 node-4 haproxy[20375]: proxy odl-jetty has no server available!
<27>Jul 28 15:32:15 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:15 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:15 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:15 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:15 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:15 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:17 node-4 haproxy[20375]: Server odl-neutron-endpoint/node-1 is DOWN, reason: Layer4 timeout, check duration: 5000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 28 15:32:17 node-4 haproxy[20375]: proxy odl-neutron-endpoint has no server available!
<129>Jul 28 15:32:18 node-4 haproxy[22392]: 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 28 15:32:18 node-4 haproxy[22392]: 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 28 15:32:20 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:20 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:20 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:20 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:20 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:21 node-4 haproxy[22392]: Server odl-jetty/node-1 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 28 15:32:21 node-4 haproxy[22392]: proxy odl-jetty has no server available!
<129>Jul 28 15:32:22 node-4 haproxy[23577]: 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 28 15:32:23 node-4 haproxy[23583]: 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 28 15:32:23 node-4 haproxy[23583]: 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 28 15:32:25 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:25 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:25 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:25 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:25 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:26 node-4 haproxy[23583]: Server odl-jetty/node-1 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 28 15:32:26 node-4 haproxy[23583]: proxy odl-jetty has no server available!
<129>Jul 28 15:32:27 node-4 haproxy[24677]: 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 28 15:32:28 node-4 haproxy[24681]: 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 28 15:32:28 node-4 haproxy[24681]: 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 28 15:32:28 node-4 haproxy[24681]: 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 28 15:32:29 node-4 haproxy[24681]: 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 28 15:32:30 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:30 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:30 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:30 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:30 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:30 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:31 node-4 haproxy[24681]: Server odl-jetty/node-1 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 28 15:32:31 node-4 haproxy[24681]: proxy odl-jetty has no server available!
<129>Jul 28 15:32:32 node-4 haproxy[25744]: 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 28 15:32:32 node-4 haproxy[25744]: 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 28 15:32:32 node-4 haproxy[25744]: 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 28 15:32:33 node-4 haproxy[25750]: 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 28 15:32:33 node-4 haproxy[25750]: 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 28 15:32:33 node-4 haproxy[25750]: 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 28 15:32:35 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:35 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:35 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:35 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:35 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:35 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:35 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:35 node-4 haproxy[25750]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:35 node-4 haproxy[25750]: 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 28 15:32:35 node-4 haproxy[25750]: proxy aodh has no server available!
<129>Jul 28 15:32:36 node-4 haproxy[25750]: Server odl-jetty/node-1 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 28 15:32:36 node-4 haproxy[25750]: proxy odl-jetty has no server available!
<129>Jul 28 15:32:37 node-4 haproxy[26986]: 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 28 15:32:37 node-4 haproxy[26986]: 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 28 15:32:37 node-4 haproxy[26986]: 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 28 15:32:38 node-4 haproxy[26990]: 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 28 15:32:38 node-4 haproxy[26990]: 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 28 15:32:38 node-4 haproxy[26990]: 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 28 15:32:39 node-4 haproxy[26990]: 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 28 15:32:40 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:40 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:40 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:40 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:40 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:40 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:40 node-4 haproxy[26990]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:40 node-4 haproxy[26990]: 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 28 15:32:40 node-4 haproxy[26990]: proxy aodh has no server available!
<129>Jul 28 15:32:40 node-4 haproxy[26990]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:40 node-4 haproxy[26990]: 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 28 15:32:40 node-4 haproxy[26990]: proxy ceilometer has no server available!
<129>Jul 28 15:32:41 node-4 haproxy[26990]: Server odl-jetty/node-1 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 28 15:32:41 node-4 haproxy[26990]: proxy odl-jetty has no server available!
<129>Jul 28 15:32:42 node-4 haproxy[28046]: 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 28 15:32:42 node-4 haproxy[28046]: 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 28 15:32:43 node-4 haproxy[28050]: 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 28 15:32:43 node-4 haproxy[28050]: 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 28 15:32:43 node-4 haproxy[28050]: 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 28 15:32:43 node-4 haproxy[28050]: 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 28 15:32:44 node-4 haproxy[28050]: 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 28 15:32:45 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:45 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:45 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:45 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:45 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:45 node-4 haproxy[28050]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:45 node-4 haproxy[28050]: 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 28 15:32:45 node-4 haproxy[28050]: proxy aodh has no server available!
<129>Jul 28 15:32:45 node-4 haproxy[28050]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:45 node-4 haproxy[28050]: 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 28 15:32:45 node-4 haproxy[28050]: proxy ceilometer has no server available!
<129>Jul 28 15:32:46 node-4 haproxy[28050]: Server odl-jetty/node-1 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 28 15:32:46 node-4 haproxy[28050]: proxy odl-jetty has no server available!
<129>Jul 28 15:32:47 node-4 haproxy[29127]: 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 28 15:32:47 node-4 haproxy[29127]: 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 28 15:32:48 node-4 haproxy[29131]: 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 28 15:32:48 node-4 haproxy[29131]: 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 28 15:32:48 node-4 haproxy[29131]: 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 28 15:32:48 node-4 haproxy[29131]: 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 28 15:32:49 node-4 haproxy[29131]: 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 28 15:32:49 node-4 haproxy[29131]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:49 node-4 haproxy[29131]: 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 28 15:32:50 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:50 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:50 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:50 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:50 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:50 node-4 haproxy[29131]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:50 node-4 haproxy[29131]: 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 28 15:32:50 node-4 haproxy[29131]: proxy aodh has no server available!
<129>Jul 28 15:32:50 node-4 haproxy[29131]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:51 node-4 haproxy[29131]: 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 28 15:32:51 node-4 haproxy[29131]: proxy ceilometer has no server available!
<129>Jul 28 15:32:51 node-4 haproxy[29131]: Server odl-jetty/node-1 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 28 15:32:51 node-4 haproxy[29131]: proxy odl-jetty has no server available!
<129>Jul 28 15:32:53 node-4 haproxy[30249]: 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 28 15:32:53 node-4 haproxy[30249]: 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 28 15:32:53 node-4 haproxy[30249]: 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 28 15:32:53 node-4 haproxy[30249]: 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 28 15:32:53 node-4 haproxy[30249]: 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 28 15:32:54 node-4 haproxy[30249]: 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 28 15:32:54 node-4 haproxy[30249]: 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 28 15:32:54 node-4 haproxy[30249]: 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 28 15:32:54 node-4 haproxy[30249]: 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 28 15:32:54 node-4 haproxy[30249]: 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 28 15:32:54 node-4 haproxy[30249]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:54 node-4 haproxy[30249]: 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 28 15:32:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:32:55 node-4 multipathd: uevent trigger error
<129>Jul 28 15:32:55 node-4 haproxy[30249]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:55 node-4 haproxy[30249]: 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 28 15:32:55 node-4 haproxy[30249]: proxy glance-registry has no server available!
<129>Jul 28 15:32:56 node-4 haproxy[30249]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:56 node-4 haproxy[30249]: 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 28 15:32:56 node-4 haproxy[30249]: proxy aodh has no server available!
<129>Jul 28 15:32:56 node-4 haproxy[30249]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:32:56 node-4 haproxy[30249]: 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 28 15:32:56 node-4 haproxy[30249]: proxy ceilometer has no server available!
<129>Jul 28 15:32:56 node-4 haproxy[30249]: Server odl-jetty/node-1 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 28 15:32:56 node-4 haproxy[30249]: proxy odl-jetty has no server available!
<129>Jul 28 15:32:58 node-4 haproxy[31340]: 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 28 15:32:58 node-4 haproxy[31340]: 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 28 15:32:58 node-4 haproxy[31340]: 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 28 15:32:59 node-4 haproxy[31346]: 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 28 15:32:59 node-4 haproxy[31346]: 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 28 15:32:59 node-4 haproxy[31346]: 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 28 15:32:59 node-4 haproxy[31346]: 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 28 15:32:59 node-4 haproxy[31346]: 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 28 15:32:59 node-4 haproxy[31346]: 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 28 15:32:59 node-4 haproxy[31346]: 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 28 15:32:59 node-4 haproxy[31346]: 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 28 15:33:00 node-4 haproxy[31346]: 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 28 15:33:00 node-4 haproxy[31346]: 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 28 15:33:00 node-4 haproxy[31346]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:00 node-4 haproxy[31346]: 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 28 15:33:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:01 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:01 node-4 multipathd: uevent trigger error
<129>Jul 28 15:33:01 node-4 haproxy[31346]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:01 node-4 haproxy[31346]: 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 28 15:33:01 node-4 haproxy[31346]: proxy glance-registry has no server available!
<129>Jul 28 15:33:01 node-4 haproxy[31346]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:01 node-4 haproxy[31346]: 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 28 15:33:01 node-4 haproxy[31346]: proxy aodh has no server available!
<129>Jul 28 15:33:02 node-4 haproxy[31346]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:02 node-4 haproxy[31346]: 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 28 15:33:02 node-4 haproxy[31346]: proxy ceilometer has no server available!
<129>Jul 28 15:33:02 node-4 haproxy[31346]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:02 node-4 haproxy[31346]: 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 28 15:33:02 node-4 haproxy[31346]: proxy nova-novncproxy has no server available!
<129>Jul 28 15:33:02 node-4 haproxy[31346]: Server odl-jetty/node-1 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 28 15:33:02 node-4 haproxy[31346]: proxy odl-jetty has no server available!
<129>Jul 28 15:33:03 node-4 haproxy[32406]: 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 28 15:33:03 node-4 haproxy[32406]: 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 28 15:33:03 node-4 haproxy[32406]: 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 28 15:33:04 node-4 haproxy[32410]: 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 28 15:33:04 node-4 haproxy[32410]: 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 28 15:33:04 node-4 haproxy[32410]: 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 28 15:33:04 node-4 haproxy[32410]: 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 28 15:33:04 node-4 haproxy[32410]: 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 28 15:33:04 node-4 haproxy[32410]: 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 28 15:33:04 node-4 haproxy[32410]: 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 28 15:33:04 node-4 haproxy[32410]: 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 28 15:33:05 node-4 haproxy[32410]: 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 28 15:33:05 node-4 haproxy[32410]: 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 28 15:33:05 node-4 haproxy[32410]: 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 28 15:33:05 node-4 haproxy[32410]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:05 node-4 haproxy[32410]: 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 28 15:33:06 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:06 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:06 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:06 node-4 multipathd: uevent trigger error
<129>Jul 28 15:33:06 node-4 haproxy[32410]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:06 node-4 haproxy[32410]: 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 28 15:33:06 node-4 haproxy[32410]: proxy glance-registry has no server available!
<129>Jul 28 15:33:06 node-4 haproxy[32410]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:07 node-4 haproxy[32410]: 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 28 15:33:07 node-4 haproxy[32410]: proxy aodh has no server available!
<129>Jul 28 15:33:07 node-4 haproxy[32410]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:07 node-4 haproxy[32410]: 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 28 15:33:07 node-4 haproxy[32410]: proxy ceilometer has no server available!
<129>Jul 28 15:33:07 node-4 haproxy[32410]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:07 node-4 haproxy[32410]: Server nova-novncproxy/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 28 15:33:07 node-4 haproxy[32410]: proxy nova-novncproxy has no server available!
<129>Jul 28 15:33:07 node-4 haproxy[32410]: Server odl-jetty/node-1 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 28 15:33:07 node-4 haproxy[32410]: proxy odl-jetty has no server available!
<129>Jul 28 15:33:08 node-4 haproxy[1091]: 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 28 15:33:09 node-4 haproxy[1096]: 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 28 15:33:09 node-4 haproxy[1096]: 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 28 15:33:09 node-4 haproxy[1096]: 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 28 15:33:09 node-4 haproxy[1096]: 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 28 15:33:09 node-4 haproxy[1096]: 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 28 15:33:09 node-4 haproxy[1096]: 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 28 15:33:09 node-4 haproxy[1096]: 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 28 15:33:09 node-4 haproxy[1096]: 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 28 15:33:09 node-4 haproxy[1096]: 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 28 15:33:10 node-4 haproxy[1096]: 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 28 15:33:10 node-4 haproxy[1096]: 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 28 15:33:10 node-4 haproxy[1096]: 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 28 15:33:10 node-4 haproxy[1096]: 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 28 15:33:10 node-4 haproxy[1096]: 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 28 15:33:10 node-4 haproxy[1096]: 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 28 15:33:10 node-4 haproxy[1096]: 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 28 15:33:10 node-4 haproxy[1096]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:10 node-4 haproxy[1096]: 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 28 15:33:11 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:11 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:11 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:11 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:11 node-4 multipathd: uevent trigger error
<129>Jul 28 15:33:11 node-4 haproxy[1096]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:11 node-4 haproxy[1096]: 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 28 15:33:11 node-4 haproxy[1096]: proxy glance-registry has no server available!
<129>Jul 28 15:33:12 node-4 haproxy[1096]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:12 node-4 haproxy[1096]: 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 28 15:33:12 node-4 haproxy[1096]: proxy aodh has no server available!
<129>Jul 28 15:33:12 node-4 haproxy[1096]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:12 node-4 haproxy[1096]: 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 28 15:33:12 node-4 haproxy[1096]: proxy ceilometer has no server available!
<129>Jul 28 15:33:12 node-4 haproxy[1096]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:12 node-4 haproxy[1096]: Server nova-novncproxy/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 28 15:33:12 node-4 haproxy[1096]: proxy nova-novncproxy has no server available!
<129>Jul 28 15:33:12 node-4 haproxy[1096]: Server odl-jetty/node-1 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 28 15:33:12 node-4 haproxy[1096]: proxy odl-jetty has no server available!
<27>Jul 28 15:33:14 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:14 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:14 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:14 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:14 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:14 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:17 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:17 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:17 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:17 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:17 node-4 multipathd: uevent trigger error
<129>Jul 28 15:33:18 node-4 haproxy[1096]: Server odl-neutron-endpoint/node-1 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 28 15:33:18 node-4 haproxy[1096]: proxy odl-neutron-endpoint has no server available!
<129>Jul 28 15:33:18 node-4 haproxy[1096]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:18 node-4 haproxy[1096]: 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 28 15:33:18 node-4 haproxy[1096]: proxy keystone-1 has no server available!
<129>Jul 28 15:33:18 node-4 haproxy[1096]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server keystone-2/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 28 15:33:19 node-4 haproxy[1096]: proxy keystone-2 has no server available!
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server nova-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 28 15:33:19 node-4 haproxy[1096]: proxy nova-api has no server available!
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:19 node-4 haproxy[1096]: 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 28 15:33:19 node-4 haproxy[1096]: proxy nova-metadata-api has no server available!
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server cinder-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:19 node-4 haproxy[1096]: 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 28 15:33:19 node-4 haproxy[1096]: proxy cinder-api has no server available!
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server glance-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 28 15:33:19 node-4 haproxy[1096]: proxy glance-api has no server available!
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:19 node-4 haproxy[1096]: 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 28 15:33:19 node-4 haproxy[1096]: proxy glance-glare has no server available!
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server neutron/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 28 15:33:19 node-4 haproxy[1096]: proxy neutron has no server available!
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server mysqld/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Backup Server mysqld/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 28 15:33:19 node-4 haproxy[1096]: proxy mysqld has no server available!
<129>Jul 28 15:33:19 node-4 haproxy[1096]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:19 node-4 haproxy[1096]: 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 28 15:33:19 node-4 haproxy[1096]: proxy object-storage has no server available!
<129>Jul 28 15:33:20 node-4 haproxy[1096]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:20 node-4 haproxy[1096]: 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 28 15:33:20 node-4 haproxy[1096]: proxy heat-api has no server available!
<129>Jul 28 15:33:20 node-4 haproxy[1096]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:20 node-4 haproxy[1096]: 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 28 15:33:20 node-4 haproxy[1096]: proxy heat-api-cfn has no server available!
<129>Jul 28 15:33:20 node-4 haproxy[1096]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 28 15:33:20 node-4 haproxy[1096]: Server heat-api-cloudwatch/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 28 15:33:20 node-4 haproxy[1096]: proxy heat-api-cloudwatch has no server available!
<27>Jul 28 15:33:28 node-4 ocf-ns_conntrackd: ERROR: Setup problem: couldn't find command: conntrackd
<27>Jul 28 15:33:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:56 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<43>Jul 28 15:33:57 node-4 apache2_error [Thu Jul 28 15:33:50.800836 2016] [mpm_worker:notice] [pid 9149:tid 140658979149696] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 15:33:57 node-4 apache2_error [Thu Jul 28 15:33:50.806577 2016] [mpm_worker:warn] [pid 9149:tid 140658979149696] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 15:33:57 node-4 apache2_error [Thu Jul 28 15:33:50.806924 2016] [mpm_worker:notice] [pid 9149:tid 140658979149696] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 28 15:33:57 node-4 apache2_error [Thu Jul 28 15:33:50.806930 2016] [core:notice] [pid 9149:tid 140658979149696] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 15:33:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:33:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:34:19 node-4 multipathd: uevent trigger error
<27>Jul 28 15:34:50 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 28 15:34:50 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 28 15:34:54 node-4 multipathd: uevent trigger error
<27>Jul 28 15:34:54 node-4 multipathd: uevent trigger error
<27>Jul 28 15:34:54 node-4 multipathd: uevent trigger error
<27>Jul 28 15:34:54 node-4 multipathd: uevent trigger error
<27>Jul 28 15:34:54 node-4 multipathd: uevent trigger error
<27>Jul 28 15:34:54 node-4 multipathd: uevent trigger error
<27>Jul 28 15:35:15 node-4 multipathd: uevent trigger error
<27>Jul 28 15:35:15 node-4 multipathd: uevent trigger error
<27>Jul 28 15:35:15 node-4 multipathd: uevent trigger error
<27>Jul 28 15:35:15 node-4 multipathd: uevent trigger error
<27>Jul 28 15:35:15 node-4 multipathd: uevent trigger error
<27>Jul 28 15:35:21 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 28 15:35:57 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 28 15:35:59 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 28 15:37:41 node-4 multipathd: uevent trigger error
<27>Jul 28 15:37:41 node-4 multipathd: uevent trigger error
<27>Jul 28 15:37:41 node-4 multipathd: uevent trigger error
<27>Jul 28 15:37:41 node-4 multipathd: uevent trigger error
<27>Jul 28 15:37:41 node-4 multipathd: uevent trigger error
<11>Jul 28 15:40:54 node-4 epmd: epmd: node name already occupied rabbitmq-cli-68
<27>Jul 28 15:40:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:40:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:40:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:40:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:40:55 node-4 multipathd: uevent trigger error
<11>Jul 28 15:41:47 node-4 epmd: epmd: node name already occupied rabbitmq-cli-68
<43>Jul 28 15:42:17 node-4 apache2_error [Thu Jul 28 15:42:10.176676 2016] [mpm_worker:notice] [pid 9149:tid 140658979149696] AH00295: caught SIGTERM, shutting down
<43>Jul 28 15:42:17 node-4 apache2_error [Thu Jul 28 15:42:10.930840 2016] [mpm_worker:notice] [pid 10354:tid 139637135075200] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 15:42:17 node-4 apache2_error [Thu Jul 28 15:42:10.930865 2016] [core:notice] [pid 10354:tid 139637135075200] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 28 15:42:48 node-4 apache2_error [Thu Jul 28 15:42:42.932544 2016] [mpm_worker:notice] [pid 10354:tid 139637135075200] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 15:42:48 node-4 apache2_error [Thu Jul 28 15:42:42.946671 2016] [mpm_worker:warn] [pid 10354:tid 139637135075200] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 15:42:48 node-4 apache2_error [Thu Jul 28 15:42:42.951303 2016] [mpm_worker:notice] [pid 10354:tid 139637135075200] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 15:42:48 node-4 apache2_error [Thu Jul 28 15:42:42.951325 2016] [core:notice] [pid 10354:tid 139637135075200] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 15:42:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:42:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:42:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:42:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:42:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:42:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:42:48 node-4 multipathd: uevent trigger error
<27>Jul 28 15:43:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:43:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:43:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:43:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:43:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:43:47 node-4 multipathd: uevent trigger error
<27>Jul 28 15:45:03 node-4 multipathd: uevent trigger error
<27>Jul 28 15:45:03 node-4 multipathd: uevent trigger error
<27>Jul 28 15:45:03 node-4 multipathd: uevent trigger error
<27>Jul 28 15:45:03 node-4 multipathd: uevent trigger error
<27>Jul 28 15:45:03 node-4 multipathd: uevent trigger error
<27>Jul 28 15:48:51 node-4 multipathd: uevent trigger error
<27>Jul 28 15:48:51 node-4 multipathd: uevent trigger error
<27>Jul 28 15:48:51 node-4 multipathd: uevent trigger error
<27>Jul 28 15:48:51 node-4 multipathd: uevent trigger error
<27>Jul 28 15:48:51 node-4 multipathd: uevent trigger error
<11>Jul 28 15:50:43 node-4 epmd: epmd: node name already occupied rabbitmq-cli-68
<27>Jul 28 15:50:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:50:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:50:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:50:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:50:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:50:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:50:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:50:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:50:59 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:09 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:09 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:09 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:09 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:09 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:09 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:46 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:46 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:46 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:46 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:46 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:46 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:46 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:52:55 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:00 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:00 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:00 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:00 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:00 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:20 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:20 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:20 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:20 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:20 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:25 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:25 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:25 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:25 node-4 multipathd: uevent trigger error
<27>Jul 28 15:53:25 node-4 multipathd: uevent trigger error
<11>Jul 28 15:53:40 node-4 epmd: epmd: node name already occupied rabbitmq-cli-68
<11>Jul 28 15:54:10 node-4 epmd: epmd: node name already occupied rabbitmq-cli-68
<43>Jul 28 15:54:18 node-4 apache2_error [Thu Jul 28 15:54:14.900203 2016] [mpm_worker:notice] [pid 10354:tid 139637135075200] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 15:54:18 node-4 apache2_error [Thu Jul 28 15:54:15.286379 2016] [mpm_worker:warn] [pid 10354:tid 139637135075200] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 15:54:18 node-4 apache2_error [Thu Jul 28 15:54:15.291058 2016] [mpm_worker:notice] [pid 10354:tid 139637135075200] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 15:54:18 node-4 apache2_error [Thu Jul 28 15:54:15.291075 2016] [core:notice] [pid 10354:tid 139637135075200] AH00094: Command line: '/usr/sbin/apache2'
<11>Jul 28 15:54:20 node-4 epmd: epmd: node name already occupied rabbitmq-cli-68
<27>Jul 28 15:54:56 node-4 multipathd: uevent trigger error
<27>Jul 28 15:54:56 node-4 multipathd: uevent trigger error
<27>Jul 28 15:54:56 node-4 multipathd: uevent trigger error
<27>Jul 28 15:54:56 node-4 multipathd: uevent trigger error
<27>Jul 28 15:54:56 node-4 multipathd: uevent trigger error
<43>Jul 28 15:54:58 node-4 apache2_error [Thu Jul 28 15:54:52.060127 2016] [mpm_worker:notice] [pid 10354:tid 139637135075200] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 28 15:54:58 node-4 apache2_error [Thu Jul 28 15:54:52.450795 2016] [mpm_worker:warn] [pid 10354:tid 139637135075200] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 28 15:54:58 node-4 apache2_error [Thu Jul 28 15:54:52.463493 2016] [mpm_worker:notice] [pid 10354:tid 139637135075200] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 28 15:54:58 node-4 apache2_error [Thu Jul 28 15:54:52.463526 2016] [core:notice] [pid 10354:tid 139637135075200] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 28 15:55:29 node-4 multipathd: uevent trigger error
<27>Jul 28 15:55:29 node-4 multipathd: uevent trigger error
<27>Jul 28 15:55:29 node-4 multipathd: uevent trigger error
<27>Jul 28 15:55:29 node-4 multipathd: uevent trigger error
<27>Jul 28 15:55:29 node-4 multipathd: uevent trigger error
<27>Jul 28 15:55:29 node-4 multipathd: uevent trigger error
<27>Jul 28 15:55:33 node-4 multipathd: uevent trigger error
<27>Jul 28 15:55:33 node-4 multipathd: uevent trigger error
<27>Jul 28 15:55:33 node-4 multipathd: uevent trigger error
<27>Jul 28 15:55:33 node-4 multipathd: uevent trigger error
<27>Jul 28 15:55:33 node-4 multipathd: uevent trigger error
<11>Jul 28 15:56:21 node-4 epmd: epmd: node name already occupied rabbitmq-cli-68
<27>Jul 28 15:56:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:56:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:56:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:56:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:56:53 node-4 multipathd: uevent trigger error
<27>Jul 28 15:57:43 node-4 multipathd: uevent trigger error
<27>Jul 28 15:57:43 node-4 multipathd: uevent trigger error
<27>Jul 28 15:57:43 node-4 multipathd: uevent trigger error
<27>Jul 28 15:57:43 node-4 multipathd: uevent trigger error
<27>Jul 28 15:57:43 node-4 multipathd: uevent trigger error
<27>Jul 28 15:57:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:57:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:57:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:57:57 node-4 multipathd: uevent trigger error
<27>Jul 28 15:57:57 node-4 multipathd: uevent trigger error
<11>Jul 28 15:58:07 node-4 liberasurecode[29446]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:07 node-4 liberasurecode[29446]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:07 node-4 liberasurecode[29446]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:07 node-4 liberasurecode[29446]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:07 node-4 liberasurecode[29470]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:07 node-4 liberasurecode[29470]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:07 node-4 liberasurecode[29470]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:07 node-4 liberasurecode[29470]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:10 node-4 liberasurecode[30175]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:10 node-4 liberasurecode[30175]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:10 node-4 liberasurecode[30175]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:10 node-4 liberasurecode[30175]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:15 node-4 liberasurecode[30718]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:15 node-4 liberasurecode[30718]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:15 node-4 liberasurecode[30718]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:15 node-4 liberasurecode[30718]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:15 node-4 liberasurecode[30756]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:15 node-4 liberasurecode[30756]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:15 node-4 liberasurecode[30756]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:15 node-4 liberasurecode[30756]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30800]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30800]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30800]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30800]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30860]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30860]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30860]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30860]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30874]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30874]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30874]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30874]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30891]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30891]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30891]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30891]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30903]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30903]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30903]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 15:58:16 node-4 liberasurecode[30903]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Jul 28 15:58:22 node-4 multipathd: uevent trigger error
<27>Jul 28 15:58:22 node-4 multipathd: uevent trigger error
<27>Jul 28 15:58:22 node-4 multipathd: uevent trigger error
<27>Jul 28 15:58:22 node-4 multipathd: uevent trigger error
<27>Jul 28 15:58:22 node-4 multipathd: uevent trigger error
<27>Jul 28 15:58:22 node-4 multipathd: uevent trigger error
<27>Jul 28 15:58:26 node-4 multipathd: uevent trigger error
<27>Jul 28 15:58:26 node-4 multipathd: uevent trigger error
<27>Jul 28 15:58:27 node-4 multipathd: uevent trigger error
<27>Jul 28 15:58:27 node-4 multipathd: uevent trigger error
<27>Jul 28 15:58:27 node-4 multipathd: uevent trigger error
<27>Jul 28 15:59:34 node-4 multipathd: uevent trigger error
<27>Jul 28 15:59:34 node-4 multipathd: uevent trigger error
<27>Jul 28 15:59:34 node-4 multipathd: uevent trigger error
<27>Jul 28 15:59:34 node-4 multipathd: uevent trigger error
<27>Jul 28 15:59:34 node-4 multipathd: uevent trigger error
<11>Jul 28 16:00:01 node-4 liberasurecode[16225]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 16:00:01 node-4 liberasurecode[16225]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 16:00:01 node-4 liberasurecode[16225]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 16:00:01 node-4 liberasurecode[16225]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 28 16:00:29 node-4 epmd: epmd: node name already occupied rabbitmq-cli-68
<27>Jul 28 16:01:30 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:30 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:30 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:30 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:30 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:35 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:35 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:35 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:35 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:35 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:35 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:48 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:48 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:48 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:48 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:48 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:48 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:53 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:53 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:53 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:53 node-4 multipathd: uevent trigger error
<27>Jul 28 16:01:53 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:07 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:07 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:07 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:07 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:07 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:19 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:19 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:19 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:19 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:19 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:23 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:23 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:23 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:24 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:24 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:24 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:28 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:28 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:28 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:28 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:28 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:32 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:32 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:32 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:32 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:32 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:41 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:41 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:41 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:41 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:41 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:41 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:41 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:46 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:46 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:46 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:46 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:51 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:51 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:51 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:51 node-4 multipathd: uevent trigger error
<27>Jul 28 16:02:51 node-4 multipathd: uevent trigger error
<27>Jul 28 16:03:04 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 28 16:03:04 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<11>Jul 28 16:05:01 node-4 liberasurecode[1005]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 16:05:01 node-4 liberasurecode[1005]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 16:05:01 node-4 liberasurecode[1005]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 28 16:05:01 node-4 liberasurecode[1005]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
