Jul 29 18:51:31 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8369" x-info="http://www.rsyslog.com"] start
Jul 29 18:51:31 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Jul 29 18:51:31 node-4 rsyslogd: rsyslogd's groupid changed to 104
Jul 29 18:51:31 node-4 rsyslogd: rsyslogd's userid changed to 101
Jul 29 18:51:31 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Jul 29 18:51:31 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Jul 29 18:51:31 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Jul 29 18:51:31 node-4 kernel: [    0.000000] Linux version 3.13.0-92-generic (buildd@lgw01-52) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #139-Ubuntu SMP Tue Jun 28 20:42:26 UTC 2016 (Ubuntu 3.13.0-92.139-generic 3.13.11-ckt39)
Jul 29 18:51:31 node-4 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=c841bdb3-87eb-487f-9803-dc9bbf150880 nomdmonddf nomdmonisw
Jul 29 18:51:31 node-4 kernel: [    0.000000] KERNEL supported cpus:
Jul 29 18:51:31 node-4 kernel: [    0.000000]   Intel GenuineIntel
Jul 29 18:51:31 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Jul 29 18:51:31 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Jul 29 18:51:31 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2bcfff] usable
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2bd000-0x000000006f8b7fff] reserved
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8b8000-0x000000006f904fff] ACPI data
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f905000-0x000000006fec3fff] ACPI NVS
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fec4000-0x000000007bd57fff] reserved
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jul 29 18:51:31 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Jul 29 18:51:31 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Jul 29 18:51:31 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Jul 29 18:51:31 node-4 kernel: [    0.000000] DMI: Cisco Systems Inc UCSB-B200-M4/UCSB-B200-M4, BIOS B200M4.2.2.3c.0.101420141352 10/14/2014
Jul 29 18:51:31 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jul 29 18:51:31 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Jul 29 18:51:31 node-4 kernel: [    0.000000] No AGP bridge found
Jul 29 18:51:31 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Jul 29 18:51:31 node-4 kernel: [    0.000000] MTRR default type: write-back
Jul 29 18:51:31 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Jul 29 18:51:31 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Jul 29 18:51:31 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Jul 29 18:51:31 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Jul 29 18:51:31 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Jul 29 18:51:31 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Jul 29 18:51:31 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Jul 29 18:51:31 node-4 kernel: [    0.000000]   2 disabled
Jul 29 18:51:31 node-4 kernel: [    0.000000]   3 disabled
Jul 29 18:51:31 node-4 kernel: [    0.000000]   4 disabled
Jul 29 18:51:31 node-4 kernel: [    0.000000]   5 disabled
Jul 29 18:51:31 node-4 kernel: [    0.000000]   6 disabled
Jul 29 18:51:31 node-4 kernel: [    0.000000]   7 disabled
Jul 29 18:51:31 node-4 kernel: [    0.000000]   8 disabled
Jul 29 18:51:31 node-4 kernel: [    0.000000]   9 disabled
Jul 29 18:51:31 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Jul 29 18:51:31 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Jul 29 18:51:31 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Jul 29 18:51:31 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Jul 29 18:51:31 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Jul 29 18:51:31 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Jul 29 18:51:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Jul 29 18:51:31 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Jul 29 18:51:31 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Jul 29 18:51:31 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Jul 29 18:51:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Jul 29 18:51:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Jul 29 18:51:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Jul 29 18:51:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2bcfff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2bcfff] page 4k
Jul 29 18:51:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Jul 29 18:51:31 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Jul 29 18:51:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Jul 29 18:51:31 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Jul 29 18:51:31 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35824000-0x36c09fff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8c70b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: FACP 000000006f8f24c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8c7218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: FACS 000000006fec1f80 000040
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: APIC 000000006f8f25d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f8f2720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f8f2768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f8f2808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f8f2848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f8f2888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f8f28d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: HPET 000000006f8f2900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f8f2938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f8f29c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f8f2a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f8f2a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f8f38b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f8f38f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9026a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f904420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f904488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f904590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: HEST 000000006f904698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: BERT 000000006f904740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: ERST 000000006f904770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9049a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Jul 29 18:51:31 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Jul 29 18:51:31 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Jul 29 18:51:31 node-4 kernel: [    0.000000] Zone ranges:
Jul 29 18:51:31 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] Movable zone start for each node
Jul 29 18:51:31 node-4 kernel: [    0.000000] Early memory node ranges
Jul 29 18:51:31 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2bcfff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] On node 0 totalpages: 4125820
Jul 29 18:51:31 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Jul 29 18:51:31 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Jul 29 18:51:31 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Jul 29 18:51:31 node-4 kernel: [    0.000000]   DMA32 zone: 7060 pages used for memmap
Jul 29 18:51:31 node-4 kernel: [    0.000000]   DMA32 zone: 451807 pages, LIFO batch:31
Jul 29 18:51:31 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Jul 29 18:51:31 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Jul 29 18:51:31 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Jul 29 18:51:31 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Jul 29 18:51:31 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Jul 29 18:51:31 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Jul 29 18:51:31 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Jul 29 18:51:31 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Jul 29 18:51:31 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Jul 29 18:51:31 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Jul 29 18:51:31 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Jul 29 18:51:31 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Jul 29 18:51:31 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2bd000-0x6f8b7fff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8b8000-0x6f904fff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f905000-0x6fec3fff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fec4000-0x7bd57fff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Jul 29 18:51:31 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Jul 29 18:51:31 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Jul 29 18:51:31 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Jul 29 18:51:31 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Jul 29 18:51:31 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Jul 29 18:51:31 node-4 kernel: [    0.000000] pcpu-alloc: [0] 00 01 02 03 08 09 10 11 [1] 04 05 06 07 12 13 14 15 
Jul 29 18:51:31 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190099
Jul 29 18:51:31 node-4 kernel: [    0.000000] Policy zone: Normal
Jul 29 18:51:31 node-4 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-92-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=c841bdb3-87eb-487f-9803-dc9bbf150880 nomdmonddf nomdmonisw
Jul 29 18:51:31 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Jul 29 18:51:31 node-4 kernel: [    0.000000] Checking aperture...
Jul 29 18:51:31 node-4 kernel: [    0.000000] No AGP bridge found
Jul 29 18:51:31 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Jul 29 18:51:31 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Jul 29 18:51:31 node-4 kernel: [    0.000000] Memory: 32653320K/33280496K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627176K reserved)
Jul 29 18:51:31 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Jul 29 18:51:31 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Jul 29 18:51:31 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Jul 29 18:51:31 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Jul 29 18:51:31 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Jul 29 18:51:31 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Jul 29 18:51:31 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Jul 29 18:51:31 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Jul 29 18:51:31 node-4 kernel: [    0.000000] console [tty0] enabled
Jul 29 18:51:31 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Jul 29 18:51:31 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Jul 29 18:51:31 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Jul 29 18:51:31 node-4 kernel: [    0.000000] hpet clockevent registered
Jul 29 18:51:31 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Jul 29 18:51:31 node-4 kernel: [    0.004000] tsc: Detected 3491.670 MHz processor
Jul 29 18:51:31 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6983.34 BogoMIPS (lpj=13966680)
Jul 29 18:51:31 node-4 kernel: [    0.000007] pid_max: default: 32768 minimum: 301
Jul 29 18:51:31 node-4 kernel: [    0.000047] Security Framework initialized
Jul 29 18:51:31 node-4 kernel: [    0.000065] AppArmor: AppArmor initialized
Jul 29 18:51:31 node-4 kernel: [    0.000066] Yama: becoming mindful.
Jul 29 18:51:31 node-4 kernel: [    0.001452] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.006374] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.008301] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.008330] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.008619] Initializing cgroup subsys memory
Jul 29 18:51:31 node-4 kernel: [    0.008627] Initializing cgroup subsys devices
Jul 29 18:51:31 node-4 kernel: [    0.008629] Initializing cgroup subsys freezer
Jul 29 18:51:31 node-4 kernel: [    0.008631] Initializing cgroup subsys blkio
Jul 29 18:51:31 node-4 kernel: [    0.008632] Initializing cgroup subsys perf_event
Jul 29 18:51:31 node-4 kernel: [    0.008634] Initializing cgroup subsys hugetlb
Jul 29 18:51:31 node-4 kernel: [    0.008654] CPU: Physical Processor ID: 0
Jul 29 18:51:31 node-4 kernel: [    0.008655] CPU: Processor Core ID: 0
Jul 29 18:51:31 node-4 kernel: [    0.008659] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Jul 29 18:51:31 node-4 kernel: [    0.008659] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Jul 29 18:51:31 node-4 kernel: [    0.009352] mce: CPU supports 22 MCE banks
Jul 29 18:51:31 node-4 kernel: [    0.009380] CPU0: Thermal monitoring enabled (TM1)
Jul 29 18:51:31 node-4 kernel: [    0.009400] process: using mwait in idle threads
Jul 29 18:51:31 node-4 kernel: [    0.009403] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Jul 29 18:51:31 node-4 kernel: [    0.009403] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Jul 29 18:51:31 node-4 kernel: [    0.009403] tlb_flushall_shift: 6
Jul 29 18:51:31 node-4 kernel: [    0.009493] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Jul 29 18:51:31 node-4 kernel: [    0.010217] ACPI: Core revision 20131115
Jul 29 18:51:31 node-4 kernel: [    0.022895] ACPI: All ACPI Tables successfully acquired
Jul 29 18:51:31 node-4 kernel: [    0.023055] ftrace: allocating 28617 entries in 112 pages
Jul 29 18:51:31 node-4 kernel: [    0.031865] dmar: Host address width 46
Jul 29 18:51:31 node-4 kernel: [    0.031867] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Jul 29 18:51:31 node-4 kernel: [    0.031873] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 18:51:31 node-4 kernel: [    0.031874] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Jul 29 18:51:31 node-4 kernel: [    0.031878] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Jul 29 18:51:31 node-4 kernel: [    0.031880] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Jul 29 18:51:31 node-4 kernel: [    0.031881] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Jul 29 18:51:31 node-4 kernel: [    0.031882] dmar: ATSR flags: 0x0
Jul 29 18:51:31 node-4 kernel: [    0.031883] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Jul 29 18:51:31 node-4 kernel: [    0.031884] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Jul 29 18:51:31 node-4 kernel: [    0.032000] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Jul 29 18:51:31 node-4 kernel: [    0.032001] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 18:51:31 node-4 kernel: [    0.032002] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Jul 29 18:51:31 node-4 kernel: [    0.032003] HPET id 0 under DRHD base 0xc7ffc000
Jul 29 18:51:31 node-4 kernel: [    0.032004] Your BIOS is broken and requested that x2apic be disabled.
Jul 29 18:51:31 node-4 kernel: [    0.032004] This will slightly decrease performance.
Jul 29 18:51:31 node-4 kernel: [    0.032004] Use 'intremap=no_x2apic_optout' to override BIOS request.
Jul 29 18:51:31 node-4 kernel: [    0.032437] Enabled IRQ remapping in xapic mode
Jul 29 18:51:31 node-4 kernel: [    0.032438] x2apic not enabled, IRQ remapping is in xapic mode
Jul 29 18:51:31 node-4 kernel: [    0.032442] Switched APIC routing to physical flat.
Jul 29 18:51:31 node-4 kernel: [    0.033061] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Jul 29 18:51:31 node-4 kernel: [    0.072708] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Jul 29 18:51:31 node-4 kernel: [    0.072713] TSC deadline timer enabled
Jul 29 18:51:31 node-4 kernel: [    0.072721] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Jul 29 18:51:31 node-4 kernel: [    0.072727] ... version:                3
Jul 29 18:51:31 node-4 kernel: [    0.072727] ... bit width:              48
Jul 29 18:51:31 node-4 kernel: [    0.072728] ... generic registers:      4
Jul 29 18:51:31 node-4 kernel: [    0.072729] ... value mask:             0000ffffffffffff
Jul 29 18:51:31 node-4 kernel: [    0.072730] ... max period:             0000ffffffffffff
Jul 29 18:51:31 node-4 kernel: [    0.072731] ... fixed-purpose events:   3
Jul 29 18:51:31 node-4 kernel: [    0.072732] ... event mask:             000000070000000f
Jul 29 18:51:31 node-4 kernel: [    0.074154] x86: Booting SMP configuration:
Jul 29 18:51:31 node-4 kernel: [    0.088258] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Jul 29 18:51:31 node-4 kernel: [    0.074156] .... node  #0, CPUs:        #1  #2  #3
Jul 29 18:51:31 node-4 kernel: [    0.116166] .... node  #1, CPUs:    #4  #5  #6  #7
Jul 29 18:51:31 node-4 kernel: [    0.270303] .... node  #0, CPUs:    #8  #9 #10 #11
Jul 29 18:51:31 node-4 kernel: [    0.325910] .... node  #1, CPUs:   #12 #13 #14 #15
Jul 29 18:51:31 node-4 kernel: [    0.382966] x86: Booted up 2 nodes, 16 CPUs
Jul 29 18:51:31 node-4 kernel: [    0.382969] smpboot: Total of 16 processors activated (111745.77 BogoMIPS)
Jul 29 18:51:31 node-4 kernel: [    0.406790] devtmpfs: initialized
Jul 29 18:51:31 node-4 kernel: [    0.409909] EVM: security.selinux
Jul 29 18:51:31 node-4 kernel: [    0.409911] EVM: security.SMACK64
Jul 29 18:51:31 node-4 kernel: [    0.409912] EVM: security.ima
Jul 29 18:51:31 node-4 kernel: [    0.409913] EVM: security.capability
Jul 29 18:51:31 node-4 kernel: [    0.409963] PM: Registering ACPI NVS region [mem 0x6f905000-0x6fec3fff] (6025216 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.410631] pinctrl core: initialized pinctrl subsystem
Jul 29 18:51:31 node-4 kernel: [    0.410692] regulator-dummy: no parameters
Jul 29 18:51:31 node-4 kernel: [    0.410723] RTC time: 18:50:51, date: 07/29/16
Jul 29 18:51:31 node-4 kernel: [    0.410756] NET: Registered protocol family 16
Jul 29 18:51:31 node-4 kernel: [    0.410840] cpuidle: using governor ladder
Jul 29 18:51:31 node-4 kernel: [    0.410842] cpuidle: using governor menu
Jul 29 18:51:31 node-4 kernel: [    0.410876] ACPI: bus type PCI registered
Jul 29 18:51:31 node-4 kernel: [    0.410878] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Jul 29 18:51:31 node-4 kernel: [    0.410925] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Jul 29 18:51:31 node-4 kernel: [    0.410928] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Jul 29 18:51:31 node-4 kernel: [    0.424663] PCI: Using configuration type 1 for base access
Jul 29 18:51:31 node-4 kernel: [    0.425656] bio: create slab <bio-0> at 0
Jul 29 18:51:31 node-4 kernel: [    0.425924] ACPI: Added _OSI(Module Device)
Jul 29 18:51:31 node-4 kernel: [    0.425926] ACPI: Added _OSI(Processor Device)
Jul 29 18:51:31 node-4 kernel: [    0.425927] ACPI: Added _OSI(3.0 _SCP Extensions)
Jul 29 18:51:31 node-4 kernel: [    0.425928] ACPI: Added _OSI(Processor Aggregator Device)
Jul 29 18:51:31 node-4 kernel: [    0.438615] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Jul 29 18:51:31 node-4 kernel: [    0.449145] ACPI: Interpreter enabled
Jul 29 18:51:31 node-4 kernel: [    0.449150] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Jul 29 18:51:31 node-4 kernel: [    0.449154] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Jul 29 18:51:31 node-4 kernel: [    0.449156] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Jul 29 18:51:31 node-4 kernel: [    0.449163] ACPI: (supports S0 S4 S5)
Jul 29 18:51:31 node-4 kernel: [    0.449164] ACPI: Using IOAPIC for interrupt routing
Jul 29 18:51:31 node-4 kernel: [    0.449206] HEST: Table parsing has been initialized.
Jul 29 18:51:31 node-4 kernel: [    0.449209] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Jul 29 18:51:31 node-4 kernel: [    0.449760] ACPI: No dock devices found.
Jul 29 18:51:31 node-4 kernel: [    0.461319] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Jul 29 18:51:31 node-4 kernel: [    0.461324] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 18:51:31 node-4 kernel: [    0.461328] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 18:51:31 node-4 kernel: [    0.461356] PCI host bridge to bus 0000:ff
Jul 29 18:51:31 node-4 kernel: [    0.461359] pci_bus 0000:ff: root bus resource [bus ff]
Jul 29 18:51:31 node-4 kernel: [    0.461367] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461406] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.461436] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461472] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461502] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.461532] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.461564] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461593] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461624] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461653] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461680] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461706] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461735] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461762] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461789] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461816] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461845] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461873] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461900] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.461928] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.461954] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.461980] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462007] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462037] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.462072] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462104] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462134] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462166] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462197] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462228] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462259] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462290] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462320] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462354] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462387] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462419] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462451] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462481] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462509] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462541] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462574] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462613] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462649] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462682] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462712] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462742] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462772] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462803] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462836] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462868] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462900] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462930] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462958] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.462988] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463017] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463049] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463081] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463139] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Jul 29 18:51:31 node-4 kernel: [    0.463142] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 18:51:31 node-4 kernel: [    0.463145] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Jul 29 18:51:31 node-4 kernel: [    0.463163] PCI host bridge to bus 0000:7f
Jul 29 18:51:31 node-4 kernel: [    0.463164] pci_bus 0000:7f: root bus resource [bus 7f]
Jul 29 18:51:31 node-4 kernel: [    0.463169] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463197] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.463225] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463255] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463277] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.463302] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.463329] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463355] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463378] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463406] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463431] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463456] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463482] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463506] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463532] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463557] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463579] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463602] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463624] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.463648] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463670] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.463692] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463717] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463744] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Jul 29 18:51:31 node-4 kernel: [    0.463778] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463804] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463830] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463857] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463881] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463908] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463933] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463961] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.463986] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464014] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464043] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464071] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464099] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464123] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464148] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464176] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464201] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464227] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464255] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464282] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464306] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464333] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464359] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464386] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464410] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464437] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464466] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464492] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464514] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464539] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464565] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464595] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.464621] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.465881] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Jul 29 18:51:31 node-4 kernel: [    0.465885] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 18:51:31 node-4 kernel: [    0.467001] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 18:51:31 node-4 kernel: [    0.467519] PCI host bridge to bus 0000:00
Jul 29 18:51:31 node-4 kernel: [    0.467522] pci_bus 0000:00: root bus resource [bus 00-7e]
Jul 29 18:51:31 node-4 kernel: [    0.467523] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Jul 29 18:51:31 node-4 kernel: [    0.467524] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Jul 29 18:51:31 node-4 kernel: [    0.467526] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Jul 29 18:51:31 node-4 kernel: [    0.467527] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Jul 29 18:51:31 node-4 kernel: [    0.467529] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Jul 29 18:51:31 node-4 kernel: [    0.467530] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Jul 29 18:51:31 node-4 kernel: [    0.467536] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Jul 29 18:51:31 node-4 kernel: [    0.467618] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.467649] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.467691] pci 0000:00:01.0: System wakeup disabled by ACPI
Jul 29 18:51:31 node-4 kernel: [    0.467711] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.467740] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.467780] pci 0000:00:02.0: System wakeup disabled by ACPI
Jul 29 18:51:31 node-4 kernel: [    0.467800] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.467829] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.467869] pci 0000:00:03.0: System wakeup disabled by ACPI
Jul 29 18:51:31 node-4 kernel: [    0.467887] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.467957] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.468035] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.468112] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 18:51:31 node-4 kernel: [    0.468117] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Jul 29 18:51:31 node-4 kernel: [    0.468202] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Jul 29 18:51:31 node-4 kernel: [    0.468351] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Jul 29 18:51:31 node-4 kernel: [    0.468368] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Jul 29 18:51:31 node-4 kernel: [    0.468446] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.468499] pci 0000:00:1a.0: System wakeup disabled by ACPI
Jul 29 18:51:31 node-4 kernel: [    0.468521] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.468576] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.468619] pci 0000:00:1c.0: System wakeup disabled by ACPI
Jul 29 18:51:31 node-4 kernel: [    0.468646] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.468702] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.468745] pci 0000:00:1c.7: System wakeup disabled by ACPI
Jul 29 18:51:31 node-4 kernel: [    0.468769] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Jul 29 18:51:31 node-4 kernel: [    0.468786] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Jul 29 18:51:31 node-4 kernel: [    0.468864] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.468913] pci 0000:00:1d.0: System wakeup disabled by ACPI
Jul 29 18:51:31 node-4 kernel: [    0.468939] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Jul 29 18:51:31 node-4 kernel: [    0.469185] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Jul 29 18:51:31 node-4 kernel: [    0.469191] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Jul 29 18:51:31 node-4 kernel: [    0.469197] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.469203] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.469210] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Jul 29 18:51:31 node-4 kernel: [    0.469241] pci 0000:01:00.0: supports D1 D2
Jul 29 18:51:31 node-4 kernel: [    0.479406] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 18:51:31 node-4 kernel: [    0.479413] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 18:51:31 node-4 kernel: [    0.479417] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 18:51:31 node-4 kernel: [    0.479640] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.479674] pci 0000:02:00.0: PME# supported from D0 D3hot
Jul 29 18:51:31 node-4 kernel: [    0.487402] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 18:51:31 node-4 kernel: [    0.487408] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.487412] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 18:51:31 node-4 kernel: [    0.487496] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.487569] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.487663] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.487708] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 18:51:31 node-4 kernel: [    0.487711] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.487713] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 18:51:31 node-4 kernel: [    0.487765] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.487892] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.487944] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 18:51:31 node-4 kernel: [    0.487947] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.487949] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 18:51:31 node-4 kernel: [    0.487998] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.488117] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.488155] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.488289] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.488327] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.488446] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.488483] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Jul 29 18:51:31 node-4 kernel: [    0.488602] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Jul 29 18:51:31 node-4 kernel: [    0.488644] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 18:51:31 node-4 kernel: [    0.488647] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.488649] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 18:51:31 node-4 kernel: [    0.488707] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Jul 29 18:51:31 node-4 kernel: [    0.488769] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.488823] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.488865] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Jul 29 18:51:31 node-4 kernel: [    0.488947] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Jul 29 18:51:31 node-4 kernel: [    0.489052] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 18:51:31 node-4 kernel: [    0.489054] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.489056] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 18:51:31 node-4 kernel: [    0.489112] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Jul 29 18:51:31 node-4 kernel: [    0.489165] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.489238] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.489452] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 18:51:31 node-4 kernel: [    0.489455] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 18:51:31 node-4 kernel: [    0.489517] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Jul 29 18:51:31 node-4 kernel: [    0.489570] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.489619] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.489827] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 18:51:31 node-4 kernel: [    0.489831] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 18:51:31 node-4 kernel: [    0.489889] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Jul 29 18:51:31 node-4 kernel: [    0.489949] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.490001] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Jul 29 18:51:31 node-4 kernel: [    0.490239] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 18:51:31 node-4 kernel: [    0.490243] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 18:51:31 node-4 kernel: [    0.490416] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 18:51:31 node-4 kernel: [    0.490453] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 18:51:31 node-4 kernel: [    0.490532] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Jul 29 18:51:31 node-4 kernel: [    0.490550] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Jul 29 18:51:31 node-4 kernel: [    0.490563] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Jul 29 18:51:31 node-4 kernel: [    0.490577] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Jul 29 18:51:31 node-4 kernel: [    0.490627] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Jul 29 18:51:31 node-4 kernel: [    0.495409] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 18:51:31 node-4 kernel: [    0.495418] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 18:51:31 node-4 kernel: [    0.495470] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Jul 29 18:51:31 node-4 kernel: [    0.496166] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Jul 29 18:51:31 node-4 kernel: [    0.496169] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Jul 29 18:51:31 node-4 kernel: [    0.496289] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Jul 29 18:51:31 node-4 kernel: [    0.496396] PCI host bridge to bus 0000:80
Jul 29 18:51:31 node-4 kernel: [    0.496398] pci_bus 0000:80: root bus resource [bus 80-fe]
Jul 29 18:51:31 node-4 kernel: [    0.496399] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Jul 29 18:51:31 node-4 kernel: [    0.496400] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Jul 29 18:51:31 node-4 kernel: [    0.496408] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.496471] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.496538] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Jul 29 18:51:31 node-4 kernel: [    0.496599] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Jul 29 18:51:31 node-4 kernel: [    0.496605] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Jul 29 18:51:31 node-4 kernel: [    0.496675] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Jul 29 18:51:31 node-4 kernel: [    0.496971] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Jul 29 18:51:31 node-4 kernel: [    0.497003] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Jul 29 18:51:31 node-4 kernel: [    0.497032] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Jul 29 18:51:31 node-4 kernel: [    0.497061] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Jul 29 18:51:31 node-4 kernel: [    0.497090] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 18:51:31 node-4 kernel: [    0.497120] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 18:51:31 node-4 kernel: [    0.497150] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 18:51:31 node-4 kernel: [    0.497179] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Jul 29 18:51:31 node-4 kernel: [    0.497263] ACPI: Enabled 3 GPEs in block 00 to 3F
Jul 29 18:51:31 node-4 kernel: [    0.497268] ACPI: \_SB_.UNC1: notify handler is installed
Jul 29 18:51:31 node-4 kernel: [    0.497269] ACPI: \_SB_.UNC0: notify handler is installed
Jul 29 18:51:31 node-4 kernel: [    0.497284] ACPI: \_SB_.PCI0: notify handler is installed
Jul 29 18:51:31 node-4 kernel: [    0.497337] ACPI: \_SB_.PCI1: notify handler is installed
Jul 29 18:51:31 node-4 kernel: [    0.497416] Found 4 acpi root devices
Jul 29 18:51:31 node-4 kernel: [    0.497521] vgaarb: setting as boot device: PCI:0000:0c:00.0
Jul 29 18:51:31 node-4 kernel: [    0.497523] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Jul 29 18:51:31 node-4 kernel: [    0.497525] vgaarb: loaded
Jul 29 18:51:31 node-4 kernel: [    0.497526] vgaarb: bridge control possible 0000:0c:00.0
Jul 29 18:51:31 node-4 kernel: [    0.497635] SCSI subsystem initialized
Jul 29 18:51:31 node-4 kernel: [    0.497698] libata version 3.00 loaded.
Jul 29 18:51:31 node-4 kernel: [    0.497713] ACPI: bus type USB registered
Jul 29 18:51:31 node-4 kernel: [    0.497723] usbcore: registered new interface driver usbfs
Jul 29 18:51:31 node-4 kernel: [    0.497728] usbcore: registered new interface driver hub
Jul 29 18:51:31 node-4 kernel: [    0.497751] usbcore: registered new device driver usb
Jul 29 18:51:31 node-4 kernel: [    0.497919] PCI: Using ACPI for IRQ routing
Jul 29 18:51:31 node-4 kernel: [    0.501512] PCI: pci_cache_line_size set to 64 bytes
Jul 29 18:51:31 node-4 kernel: [    0.501718] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Jul 29 18:51:31 node-4 kernel: [    0.501719] e820: reserve RAM buffer [mem 0x6f2bd000-0x6fffffff]
Jul 29 18:51:31 node-4 kernel: [    0.501720] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Jul 29 18:51:31 node-4 kernel: [    0.501784] NetLabel: Initializing
Jul 29 18:51:31 node-4 kernel: [    0.501785] NetLabel:  domain hash size = 128
Jul 29 18:51:31 node-4 kernel: [    0.501786] NetLabel:  protocols = UNLABELED CIPSOv4
Jul 29 18:51:31 node-4 kernel: [    0.501795] NetLabel:  unlabeled traffic allowed by default
Jul 29 18:51:31 node-4 kernel: [    0.501850] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Jul 29 18:51:31 node-4 kernel: [    0.501854] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Jul 29 18:51:31 node-4 kernel: [    0.503923] Switched to clocksource hpet
Jul 29 18:51:31 node-4 kernel: [    0.508298] AppArmor: AppArmor Filesystem Enabled
Jul 29 18:51:31 node-4 kernel: [    0.508336] pnp: PnP ACPI init
Jul 29 18:51:31 node-4 kernel: [    0.508348] ACPI: bus type PNP registered
Jul 29 18:51:31 node-4 kernel: [    0.508527] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Jul 29 18:51:31 node-4 kernel: [    0.508538] pnp 00:01: [dma 4]
Jul 29 18:51:31 node-4 kernel: [    0.508556] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Jul 29 18:51:31 node-4 kernel: [    0.508591] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Jul 29 18:51:31 node-4 kernel: [    0.508615] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Jul 29 18:51:31 node-4 kernel: [    0.508636] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Jul 29 18:51:31 node-4 kernel: [    0.508682] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Jul 29 18:51:31 node-4 kernel: [    0.508793] system 00:06: [io  0x0500-0x057f] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508796] system 00:06: [io  0x0400-0x047f] could not be reserved
Jul 29 18:51:31 node-4 kernel: [    0.508797] system 00:06: [io  0x0580-0x059f] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508799] system 00:06: [io  0x0600-0x061f] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508800] system 00:06: [io  0x0880-0x0883] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508802] system 00:06: [io  0x0800-0x081f] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508805] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Jul 29 18:51:31 node-4 kernel: [    0.508807] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508809] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508810] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508811] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508813] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508814] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Jul 29 18:51:31 node-4 kernel: [    0.508817] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Jul 29 18:51:31 node-4 kernel: [    0.508917] pnp 00:07: [dma 0 disabled]
Jul 29 18:51:31 node-4 kernel: [    0.508950] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 18:51:31 node-4 kernel: [    0.509032] pnp 00:08: [dma 0 disabled]
Jul 29 18:51:31 node-4 kernel: [    0.509067] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Jul 29 18:51:31 node-4 kernel: [    0.509126] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Jul 29 18:51:31 node-4 kernel: [    0.509569] pnp: PnP ACPI: found 10 devices
Jul 29 18:51:31 node-4 kernel: [    0.509571] ACPI: bus type PNP unregistered
Jul 29 18:51:31 node-4 kernel: [    0.515567] pci 0000:00:01.0: PCI bridge to [bus 01]
Jul 29 18:51:31 node-4 kernel: [    0.515571] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Jul 29 18:51:31 node-4 kernel: [    0.515574] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Jul 29 18:51:31 node-4 kernel: [    0.515579] pci 0000:05:00.0: PCI bridge to [bus 06]
Jul 29 18:51:31 node-4 kernel: [    0.515581] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.515595] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515628] pci 0000:05:01.0: PCI bridge to [bus 07]
Jul 29 18:51:31 node-4 kernel: [    0.515643] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515672] pci 0000:05:02.0: PCI bridge to [bus 08]
Jul 29 18:51:31 node-4 kernel: [    0.515686] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Jul 29 18:51:31 node-4 kernel: [    0.515715] pci 0000:05:03.0: PCI bridge to [bus 09]
Jul 29 18:51:31 node-4 kernel: [    0.515730] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Jul 29 18:51:31 node-4 kernel: [    0.515758] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Jul 29 18:51:31 node-4 kernel: [    0.515760] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.515775] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515804] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Jul 29 18:51:31 node-4 kernel: [    0.515806] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.515821] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515850] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Jul 29 18:51:31 node-4 kernel: [    0.515851] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.515854] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515859] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Jul 29 18:51:31 node-4 kernel: [    0.515861] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.515864] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515868] pci 0000:00:03.0: PCI bridge to [bus 0a]
Jul 29 18:51:31 node-4 kernel: [    0.515874] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Jul 29 18:51:31 node-4 kernel: [    0.515883] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Jul 29 18:51:31 node-4 kernel: [    0.515886] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Jul 29 18:51:31 node-4 kernel: [    0.515898] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Jul 29 18:51:31 node-4 kernel: [    0.515899] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Jul 29 18:51:31 node-4 kernel: [    0.515900] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Jul 29 18:51:31 node-4 kernel: [    0.515901] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Jul 29 18:51:31 node-4 kernel: [    0.515902] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Jul 29 18:51:31 node-4 kernel: [    0.515902] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Jul 29 18:51:31 node-4 kernel: [    0.515903] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Jul 29 18:51:31 node-4 kernel: [    0.515904] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Jul 29 18:51:31 node-4 kernel: [    0.515905] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.515906] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515907] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.515908] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515909] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.515910] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515911] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.515912] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515913] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Jul 29 18:51:31 node-4 kernel: [    0.515914] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515915] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Jul 29 18:51:31 node-4 kernel: [    0.515917] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Jul 29 18:51:31 node-4 kernel: [    0.515918] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Jul 29 18:51:31 node-4 kernel: [    0.515919] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Jul 29 18:51:31 node-4 kernel: [    0.515922] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Jul 29 18:51:31 node-4 kernel: [    0.515923] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Jul 29 18:51:31 node-4 kernel: [    0.515964] NET: Registered protocol family 2
Jul 29 18:51:31 node-4 kernel: [    0.516257] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.516626] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.516791] TCP: Hash tables configured (established 262144 bind 65536)
Jul 29 18:51:31 node-4 kernel: [    0.516832] TCP: reno registered
Jul 29 18:51:31 node-4 kernel: [    0.516864] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.516970] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.517140] NET: Registered protocol family 1
Jul 29 18:51:31 node-4 kernel: [    0.552012] pci 0000:0c:00.0: Video device with shadowed ROM
Jul 29 18:51:31 node-4 kernel: [    0.552026] PCI: CLS 64 bytes, default 64
Jul 29 18:51:31 node-4 kernel: [    0.552112] Trying to unpack rootfs image as initramfs...
Jul 29 18:51:31 node-4 kernel: [    0.774601] Freeing initrd memory: 20376K (ffff880035824000 - ffff880036c0a000)
Jul 29 18:51:31 node-4 kernel: [    0.774639] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Jul 29 18:51:31 node-4 kernel: [    0.774642] software IO TLB [mem 0x6b2bd000-0x6f2bd000] (64MB) mapped at [ffff88006b2bd000-ffff88006f2bcfff]
Jul 29 18:51:31 node-4 kernel: [    0.775056] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775070] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775083] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775095] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775105] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775112] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775119] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775125] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775134] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775146] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775160] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775173] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775183] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775191] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775196] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775202] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Jul 29 18:51:31 node-4 kernel: [    0.775250] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Jul 29 18:51:31 node-4 kernel: [    0.775253] Scanning for low memory corruption every 60 seconds
Jul 29 18:51:31 node-4 kernel: [    0.775554] Initialise system trusted keyring
Jul 29 18:51:31 node-4 kernel: [    0.775601] audit: initializing netlink socket (disabled)
Jul 29 18:51:31 node-4 kernel: [    0.775613] type=2000 audit(1469818250.728:1): initialized
Jul 29 18:51:31 node-4 kernel: [    0.793485] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Jul 29 18:51:31 node-4 kernel: [    0.794936] zbud: loaded
Jul 29 18:51:31 node-4 kernel: [    0.795061] VFS: Disk quotas dquot_6.5.2
Jul 29 18:51:31 node-4 kernel: [    0.795101] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jul 29 18:51:31 node-4 kernel: [    0.795462] fuse init (API version 7.22)
Jul 29 18:51:31 node-4 kernel: [    0.795517] msgmni has been set to 32768
Jul 29 18:51:31 node-4 kernel: [    0.795562] Key type big_key registered
Jul 29 18:51:31 node-4 kernel: [    0.796073] Key type asymmetric registered
Jul 29 18:51:31 node-4 kernel: [    0.796075] Asymmetric key parser 'x509' registered
Jul 29 18:51:31 node-4 kernel: [    0.796100] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Jul 29 18:51:31 node-4 kernel: [    0.796167] io scheduler noop registered
Jul 29 18:51:31 node-4 kernel: [    0.796169] io scheduler deadline registered (default)
Jul 29 18:51:31 node-4 kernel: [    0.796187] io scheduler cfq registered
Jul 29 18:51:31 node-4 kernel: [    0.796670] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    0.796852] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    0.796970] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    0.797085] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    0.797205] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    0.797308] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    0.797705] aer 0000:00:01.0:pcie02: service driver aer loaded
Jul 29 18:51:31 node-4 kernel: [    0.797753] aer 0000:00:02.0:pcie02: service driver aer loaded
Jul 29 18:51:31 node-4 kernel: [    0.797779] aer 0000:00:03.0:pcie02: service driver aer loaded
Jul 29 18:51:31 node-4 kernel: [    0.797803] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797807] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797814] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Jul 29 18:51:31 node-4 kernel: [    0.797824] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797828] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797831] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797835] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797839] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797843] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797847] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797851] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797854] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797858] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797862] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797866] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797871] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Jul 29 18:51:31 node-4 kernel: [    0.797891] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797897] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Jul 29 18:51:31 node-4 kernel: [    0.797916] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797923] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Jul 29 18:51:31 node-4 kernel: [    0.797941] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797946] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Jul 29 18:51:31 node-4 kernel: [    0.797952] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Jul 29 18:51:31 node-4 kernel: [    0.798007] ioapic: probe of 0000:00:05.4 failed with error -22
Jul 29 18:51:31 node-4 kernel: [    0.798012] ioapic: probe of 0000:80:05.4 failed with error -22
Jul 29 18:51:31 node-4 kernel: [    0.798016] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Jul 29 18:51:31 node-4 kernel: [    0.798024] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Jul 29 18:51:31 node-4 kernel: [    0.798061] vesafb: mode is 640x480x32, linelength=2560, pages=0
Jul 29 18:51:31 node-4 kernel: [    0.798063] vesafb: scrolling: redraw
Jul 29 18:51:31 node-4 kernel: [    0.798064] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Jul 29 18:51:31 node-4 kernel: [    0.818547] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Jul 29 18:51:31 node-4 kernel: [    0.827042] Console: switching to colour frame buffer device 80x30
Jul 29 18:51:31 node-4 kernel: [    0.835724] fb0: VESA VGA frame buffer device
Jul 29 18:51:31 node-4 kernel: [    0.835918] intel_idle: MWAIT substates: 0x2120
Jul 29 18:51:31 node-4 kernel: [    0.835919] intel_idle: v0.4 model 0x3F
Jul 29 18:51:31 node-4 kernel: [    0.835920] intel_idle: lapic_timer_reliable_states 0xffffffff
Jul 29 18:51:31 node-4 kernel: [    0.836168] ipmi message handler version 39.2
Jul 29 18:51:31 node-4 kernel: [    0.836446] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Jul 29 18:51:31 node-4 kernel: [    0.836879] ACPI: AC Adapter [P111] (on-line)
Jul 29 18:51:31 node-4 kernel: [    0.842130] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Jul 29 18:51:31 node-4 kernel: [    0.853193] ACPI: Power Button [PWRB]
Jul 29 18:51:31 node-4 kernel: [    0.859017] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Jul 29 18:51:31 node-4 kernel: [    0.870691] ACPI: Power Button [PWRF]
Jul 29 18:51:31 node-4 kernel: [    0.889460] ERST: Error Record Serialization Table (ERST) support is initialized.
Jul 29 18:51:31 node-4 kernel: [    0.901148] pstore: Registered erst as persistent store backend
Jul 29 18:51:31 node-4 kernel: [    0.907360] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Jul 29 18:51:31 node-4 kernel: [    0.919322] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Jul 29 18:51:31 node-4 kernel: [    0.946072] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Jul 29 18:51:31 node-4 kernel: [    0.979368] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Jul 29 18:51:31 node-4 kernel: [    0.993414] Linux agpgart interface v0.103
Jul 29 18:51:31 node-4 kernel: [    1.001042] brd: module loaded
Jul 29 18:51:31 node-4 kernel: [    1.008185] loop: module loaded
Jul 29 18:51:31 node-4 kernel: [    1.014896] libphy: Fixed MDIO Bus: probed
Jul 29 18:51:31 node-4 kernel: [    1.021364] tun: Universal TUN/TAP device driver, 1.6
Jul 29 18:51:31 node-4 kernel: [    1.027835] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jul 29 18:51:31 node-4 kernel: [    1.034369] PPP generic driver version 2.4.2
Jul 29 18:51:31 node-4 kernel: [    1.040767] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Jul 29 18:51:31 node-4 kernel: [    1.047213] ehci-pci: EHCI PCI platform driver
Jul 29 18:51:31 node-4 kernel: [    1.053737] ehci-pci 0000:00:1a.0: EHCI Host Controller
Jul 29 18:51:31 node-4 kernel: [    1.060143] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Jul 29 18:51:31 node-4 kernel: [    1.072681] ehci-pci 0000:00:1a.0: debug port 2
Jul 29 18:51:31 node-4 kernel: [    1.082858] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Jul 29 18:51:31 node-4 kernel: [    1.082876] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Jul 29 18:51:31 node-4 kernel: [    1.099407] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Jul 29 18:51:31 node-4 kernel: [    1.105480] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 18:51:31 node-4 kernel: [    1.111645] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 18:51:31 node-4 kernel: [    1.123564] usb usb1: Product: EHCI Host Controller
Jul 29 18:51:31 node-4 kernel: [    1.129611] usb usb1: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 18:51:31 node-4 kernel: [    1.135674] usb usb1: SerialNumber: 0000:00:1a.0
Jul 29 18:51:31 node-4 kernel: [    1.141656] hub 1-0:1.0: USB hub found
Jul 29 18:51:31 node-4 kernel: [    1.147438] hub 1-0:1.0: 2 ports detected
Jul 29 18:51:31 node-4 kernel: [    1.153233] ehci-pci 0000:00:1d.0: EHCI Host Controller
Jul 29 18:51:31 node-4 kernel: [    1.158823] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Jul 29 18:51:31 node-4 kernel: [    1.169734] ehci-pci 0000:00:1d.0: debug port 2
Jul 29 18:51:31 node-4 kernel: [    1.179057] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Jul 29 18:51:31 node-4 kernel: [    1.179060] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Jul 29 18:51:31 node-4 kernel: [    1.195325] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Jul 29 18:51:31 node-4 kernel: [    1.200531] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Jul 29 18:51:31 node-4 kernel: [    1.205842] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Jul 29 18:51:31 node-4 kernel: [    1.216420] usb usb2: Product: EHCI Host Controller
Jul 29 18:51:31 node-4 kernel: [    1.221890] usb usb2: Manufacturer: Linux 3.13.0-92-generic ehci_hcd
Jul 29 18:51:31 node-4 kernel: [    1.227441] usb usb2: SerialNumber: 0000:00:1d.0
Jul 29 18:51:31 node-4 kernel: [    1.232972] hub 2-0:1.0: USB hub found
Jul 29 18:51:31 node-4 kernel: [    1.238318] hub 2-0:1.0: 2 ports detected
Jul 29 18:51:31 node-4 kernel: [    1.243619] ehci-platform: EHCI generic platform driver
Jul 29 18:51:31 node-4 kernel: [    1.248879] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Jul 29 18:51:31 node-4 kernel: [    1.254257] ohci-pci: OHCI PCI platform driver
Jul 29 18:51:31 node-4 kernel: [    1.259637] ohci-platform: OHCI generic platform driver
Jul 29 18:51:31 node-4 kernel: [    1.264810] uhci_hcd: USB Universal Host Controller Interface driver
Jul 29 18:51:31 node-4 kernel: [    1.270144] i8042: PNP: No PS/2 controller found. Probing ports directly.
Jul 29 18:51:31 node-4 kernel: [    1.463102] usb 1-1: new high-speed USB device number 2 using ehci-pci
Jul 29 18:51:31 node-4 kernel: [    1.639263] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Jul 29 18:51:31 node-4 kernel: [    1.644764] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 18:51:31 node-4 kernel: [    1.650530] hub 1-1:1.0: USB hub found
Jul 29 18:51:31 node-4 kernel: [    1.655998] hub 1-1:1.0: 6 ports detected
Jul 29 18:51:31 node-4 kernel: [    1.770837] usb 2-1: new high-speed USB device number 2 using ehci-pci
Jul 29 18:51:31 node-4 kernel: [    1.770860] tsc: Refined TSC clocksource calibration: 3491.887 MHz
Jul 29 18:51:31 node-4 kernel: [    2.034927] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Jul 29 18:51:31 node-4 kernel: [    2.040454] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jul 29 18:51:31 node-4 kernel: [    2.046319] hub 2-1:1.0: USB hub found
Jul 29 18:51:31 node-4 kernel: [    2.051913] hub 2-1:1.0: 8 ports detected
Jul 29 18:51:31 node-4 kernel: [    2.311536] i8042: No controller found
Jul 29 18:51:31 node-4 kernel: [    2.316940] mousedev: PS/2 mouse device common for all mice
Jul 29 18:51:31 node-4 kernel: [    2.322448] rtc_cmos 00:02: RTC can wake from S4
Jul 29 18:51:31 node-4 kernel: [    2.328020] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Jul 29 18:51:31 node-4 kernel: [    2.330431] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Jul 29 18:51:31 node-4 kernel: [    2.339142] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Jul 29 18:51:31 node-4 kernel: [    2.350210] device-mapper: uevent: version 1.0.3
Jul 29 18:51:31 node-4 kernel: [    2.355833] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Jul 29 18:51:31 node-4 kernel: [    2.367030] ledtrig-cpu: registered to indicate activity on CPUs
Jul 29 18:51:31 node-4 kernel: [    2.372948] TCP: cubic registered
Jul 29 18:51:31 node-4 kernel: [    2.378828] NET: Registered protocol family 10
Jul 29 18:51:31 node-4 kernel: [    2.384779] NET: Registered protocol family 17
Jul 29 18:51:31 node-4 kernel: [    2.390442] Key type dns_resolver registered
Jul 29 18:51:31 node-4 kernel: [    2.396389] Loading compiled-in X.509 certificates
Jul 29 18:51:31 node-4 kernel: [    2.402539] Loaded X.509 cert 'Magrathea: Glacier signing key: 2a4800b94dc783d05326fae67b01b0beb73bb811'
Jul 29 18:51:31 node-4 kernel: [    2.413917] registered taskstats version 1
Jul 29 18:51:31 node-4 kernel: [    2.421819] Key type trusted registered
Jul 29 18:51:31 node-4 kernel: [    2.429334] Key type encrypted registered
Jul 29 18:51:31 node-4 kernel: [    2.434787] AppArmor: AppArmor sha1 policy hashing enabled
Jul 29 18:51:31 node-4 kernel: [    2.440275] IMA: No TPM chip found, activating TPM-bypass!
Jul 29 18:51:31 node-4 kernel: [    2.446421] regulator-dummy: disabling
Jul 29 18:51:31 node-4 kernel: [    2.451962]   Magic number: 8:882:848
Jul 29 18:51:31 node-4 kernel: [    2.457409] pci 0000:ff:16.6: hash matches
Jul 29 18:51:31 node-4 kernel: [    2.462768] acpi device:c9: hash matches
Jul 29 18:51:31 node-4 kernel: [    2.466503] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Jul 29 18:51:31 node-4 kernel: [    2.466504] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 29 18:51:31 node-4 kernel: [    2.466505] usb 2-1.4: Product: Cisco USB Composite Device-0
Jul 29 18:51:31 node-4 kernel: [    2.466506] usb 2-1.4: Manufacturer: Avocent
Jul 29 18:51:31 node-4 kernel: [    2.466506] usb 2-1.4: SerialNumber: 20111102-00000001
Jul 29 18:51:31 node-4 kernel: [    2.501000] processor cpu12: hash matches
Jul 29 18:51:31 node-4 kernel: [    2.506514] rtc_cmos 00:02: setting system clock to 2016-07-29 18:50:53 UTC (1469818253)
Jul 29 18:51:31 node-4 kernel: [    2.518857] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Jul 29 18:51:31 node-4 kernel: [    2.524391] EDD information not available.
Jul 29 18:51:31 node-4 kernel: [    2.529877] PM: Hibernation image not present or could not be loaded.
Jul 29 18:51:31 node-4 kernel: [    2.530738] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Jul 29 18:51:31 node-4 kernel: [    2.541628] Write protecting the kernel read-only data: 12288k
Jul 29 18:51:31 node-4 kernel: [    2.547669] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Jul 29 18:51:31 node-4 kernel: [    2.560244] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Jul 29 18:51:31 node-4 kernel: [    2.592785] device-mapper: multipath: version 1.6.0 loaded
Jul 29 18:51:31 node-4 kernel: [    2.600620] systemd-udevd[215]: starting version 204
Jul 29 18:51:31 node-4 kernel: [    2.625370] md: linear personality registered for level -1
Jul 29 18:51:31 node-4 kernel: [    2.640240] md: multipath personality registered for level -4
Jul 29 18:51:31 node-4 kernel: [    2.648203] md: raid0 personality registered for level 0
Jul 29 18:51:31 node-4 kernel: [    2.656480] md: raid1 personality registered for level 1
Jul 29 18:51:31 node-4 kernel: [    2.665909] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Jul 29 18:51:31 node-4 kernel: [    2.672247] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Jul 29 18:51:31 node-4 kernel: [    2.678654] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Jul 29 18:51:31 node-4 kernel: [    2.679670] megasas: FW now in Ready state
Jul 29 18:51:31 node-4 kernel: [    2.680337] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.680428] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.680547] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.680677] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.680776] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.680869] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.681004] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.681181] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.681321] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.681408] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.681568] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.681631] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.681643] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.681718] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.681781] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.681922] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.682698] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Jul 29 18:51:31 node-4 kernel: [    2.704219] hidraw: raw HID events driver (C) Jiri Kosina
Jul 29 18:51:31 node-4 kernel: [    2.712341] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:2a wq/rq 256/512 mtu 1500
Jul 29 18:51:31 node-4 kernel: [    2.721855] usbcore: registered new interface driver usbhid
Jul 29 18:51:31 node-4 kernel: [    2.721859] usbhid: USB HID core driver
Jul 29 18:51:31 node-4 kernel: [    2.730098] raid6: sse2x1   10017 MB/s
Jul 29 18:51:31 node-4 kernel: [    2.745278] 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 29 18:51:31 node-4 kernel: [    2.758445] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 18:51:31 node-4 kernel: [    2.765138] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.765142] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.765146] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.765149] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.765190] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 18:51:31 node-4 kernel: [    2.797978] raid6: sse2x2   12336 MB/s
Jul 29 18:51:31 node-4 kernel: [    2.869922] raid6: sse2x4   10135 MB/s
Jul 29 18:51:31 node-4 kernel: [    2.941853] raid6: avx2x1   14947 MB/s
Jul 29 18:51:31 node-4 kernel: [    3.013784] raid6: avx2x2   18865 MB/s
Jul 29 18:51:31 node-4 kernel: [    3.085731] raid6: avx2x4   21346 MB/s
Jul 29 18:51:31 node-4 kernel: [    3.091263] raid6: using algorithm avx2x4 (21346 MB/s)
Jul 29 18:51:31 node-4 kernel: [    3.096864] raid6: using avx2x2 recovery algorithm
Jul 29 18:51:31 node-4 kernel: [    3.102370] megasas:IOC Init cmd success
Jul 29 18:51:31 node-4 kernel: [    3.102374] Switched to clocksource tsc
Jul 29 18:51:31 node-4 kernel: [    3.112278] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:2b wq/rq 256/512 mtu 1500
Jul 29 18:51:31 node-4 kernel: [    3.112296] 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 29 18:51:31 node-4 kernel: [    3.112297] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 18:51:31 node-4 kernel: [    3.112588] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.112740] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.112902] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.112958] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.113286] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.129542] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:2c wq/rq 256/512 mtu 1500
Jul 29 18:51:31 node-4 kernel: [    3.129543] 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 29 18:51:31 node-4 kernel: [    3.129544] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 18:51:31 node-4 kernel: [    3.129852] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.129964] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.130118] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.130210] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.130436] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.143463] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:2d wq/rq 256/512 mtu 1500
Jul 29 18:51:31 node-4 kernel: [    3.143487] 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 29 18:51:31 node-4 kernel: [    3.143507] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Jul 29 18:51:31 node-4 kernel: [    3.143705] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.143846] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.143927] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.144015] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.144220] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Jul 29 18:51:31 node-4 kernel: [    3.232081] 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 29 18:51:31 node-4 kernel: [    3.244681] xor: automatically using best checksumming function:
Jul 29 18:51:31 node-4 kernel: [    3.246879] 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 29 18:51:31 node-4 kernel: [    3.248269] 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 29 18:51:31 node-4 kernel: [    3.249254] 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 29 18:51:31 node-4 kernel: [    3.250182] 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 29 18:51:31 node-4 kernel: [    3.251245] 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 29 18:51:31 node-4 kernel: [    3.253665] megasas: INIT adapter done
Jul 29 18:51:31 node-4 kernel: [    3.325594] megaraid_sas 0000:01:00.0: Controller type: iMR
Jul 29 18:51:31 node-4 kernel: [    3.325975] scsi0 : LSI SAS based MegaRAID driver
Jul 29 18:51:31 node-4 kernel: [    3.333065] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 18:51:31 node-4 kernel: [    3.344350] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Jul 29 18:51:31 node-4 kernel: [    3.348632] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Jul 29 18:51:31 node-4 kernel: [    3.348704] sd 0:2:0:0: Attached scsi generic sg0 type 0
Jul 29 18:51:31 node-4 kernel: [    3.349028] sd 0:2:0:0: [sda] Write Protect is off
Jul 29 18:51:31 node-4 kernel: [    3.349030] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Jul 29 18:51:31 node-4 kernel: [    3.349092] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Jul 29 18:51:31 node-4 kernel: [    3.371298]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9
Jul 29 18:51:31 node-4 kernel: [    3.373285] sd 0:2:0:0: [sda] Attached SCSI disk
Jul 29 18:51:31 node-4 kernel: [    3.473379]    avx       : 35730.000 MB/sec
Jul 29 18:51:31 node-4 kernel: [    3.481175] async_tx: api initialized (async)
Jul 29 18:51:31 node-4 kernel: [    3.491873] md: raid6 personality registered for level 6
Jul 29 18:51:31 node-4 kernel: [    3.498803] md: raid5 personality registered for level 5
Jul 29 18:51:31 node-4 kernel: [    3.505502] md: raid4 personality registered for level 4
Jul 29 18:51:31 node-4 kernel: [    3.515054] md: raid10 personality registered for level 10
Jul 29 18:51:31 node-4 kernel: [    3.566874] multipathd (360): /proc/360/oom_adj is deprecated, please use /proc/360/oom_score_adj instead.
Jul 29 18:51:31 node-4 kernel: [    3.577222] random: lvm urandom read with 29 bits of entropy available
Jul 29 18:51:31 node-4 kernel: [    3.702401] bio: create slab <bio-1> at 1
Jul 29 18:51:31 node-4 kernel: [    4.464536] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 18:51:31 node-4 kernel: [    5.020774] init: plymouth-upstart-bridge main process (551) terminated with status 1
Jul 29 18:51:31 node-4 kernel: [    5.032597] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 18:51:31 node-4 kernel: [    5.161400] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Jul 29 18:51:31 node-4 kernel: [    5.205239] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Jul 29 18:51:31 node-4 kernel: [    5.396650] random: nonblocking pool is initialized
Jul 29 18:51:31 node-4 kernel: [    5.403181] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Jul 29 18:51:31 node-4 kernel: [    5.452759] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Jul 29 18:51:31 node-4 kernel: [    5.546863] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 18:51:31 node-4 kernel: [    5.757798] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Jul 29 18:51:31 node-4 kernel: [    5.792141] XFS (dm-0): Mounting Filesystem
Jul 29 18:51:31 node-4 kernel: [    6.028236] XFS (dm-0): Ending clean mount
Jul 29 18:51:31 node-4 kernel: [    6.101542] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Jul 29 18:51:31 node-4 kernel: [    6.142158] XFS (dm-1): Mounting Filesystem
Jul 29 18:51:31 node-4 kernel: [    6.248441] XFS (dm-1): Ending clean mount
Jul 29 18:51:31 node-4 kernel: [    8.082121] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 29 18:51:31 node-4 kernel: [    8.110411] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 29 18:51:31 node-4 kernel: [    8.277406] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jul 29 18:51:31 node-4 kernel: [    8.277411] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Jul 29 18:51:31 node-4 kernel: [    8.277415] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Jul 29 18:51:31 node-4 kernel: [    8.277420] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Jul 29 18:51:31 node-4 kernel: [    8.306253] systemd-udevd[777]: starting version 204
Jul 29 18:51:31 node-4 kernel: [    8.476668] power_meter ACPI000D:00: Found ACPI power meter.
Jul 29 18:51:31 node-4 kernel: [    8.476691] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Jul 29 18:51:31 node-4 kernel: [    8.510793] IPMI System Interface driver.
Jul 29 18:51:31 node-4 kernel: [    8.510837] ipmi_si: probing via ACPI
Jul 29 18:51:31 node-4 kernel: [    8.510850] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Jul 29 18:51:31 node-4 kernel: [    8.510851] ipmi_si: Adding ACPI-specified kcs state machine
Jul 29 18:51:31 node-4 kernel: [    8.510860] ipmi_si: probing via SMBIOS
Jul 29 18:51:31 node-4 kernel: [    8.510861] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 18:51:31 node-4 kernel: [    8.510862] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Jul 29 18:51:31 node-4 kernel: [    8.510865] ipmi_si: probing via SPMI
Jul 29 18:51:31 node-4 kernel: [    8.510866] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Jul 29 18:51:31 node-4 kernel: [    8.510867] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Jul 29 18:51:31 node-4 kernel: [    8.510869] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Jul 29 18:51:31 node-4 kernel: [    8.521833] wmi: Mapper loaded
Jul 29 18:51:31 node-4 kernel: [    8.542210] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Jul 29 18:51:31 node-4 kernel: [    8.542215] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 18:51:31 node-4 kernel: [    8.542218] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Jul 29 18:51:31 node-4 kernel: [    8.542219] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 29 18:51:31 node-4 kernel: [    8.542238] lpc_ich: Resource conflict(s) found affecting gpio_ich
Jul 29 18:51:31 node-4 kernel: [    8.545706] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 29 18:51:31 node-4 kernel: [    8.637617] systemd-udevd[795]: renamed network interface eth0 to enp6s0
Jul 29 18:51:31 node-4 kernel: [    8.677022] systemd-udevd[806]: renamed network interface eth2 to enp8s0
Jul 29 18:51:31 node-4 kernel: [    8.713318] systemd-udevd[797]: renamed network interface eth1 to enp7s0
Jul 29 18:51:31 node-4 kernel: [    8.737249] systemd-udevd[794]: renamed network interface eth3 to enp9s0
Jul 29 18:51:31 node-4 kernel: [    8.768919] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Jul 29 18:51:31 node-4 kernel: [    8.768924] ipmi_si 00:09: IPMI kcs interface initialized
Jul 29 18:51:31 node-4 kernel: [    9.027974] type=1400 audit(1469818260.020:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1069 comm="apparmor_parser"
Jul 29 18:51:31 node-4 kernel: [    9.028124] type=1400 audit(1469818260.020:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1069 comm="apparmor_parser"
Jul 29 18:51:31 node-4 kernel: [    9.028249] type=1400 audit(1469818260.020:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1069 comm="apparmor_parser"
Jul 29 18:51:31 node-4 kernel: [    9.029678] type=1400 audit(1469818260.024:5): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1065 comm="apparmor_parser"
Jul 29 18:51:31 node-4 kernel: [    9.029816] type=1400 audit(1469818260.024:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1065 comm="apparmor_parser"
Jul 29 18:51:31 node-4 kernel: [    9.029936] type=1400 audit(1469818260.024:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1065 comm="apparmor_parser"
Jul 29 18:51:31 node-4 kernel: [    9.043329] type=1400 audit(1469818260.036:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1070 comm="apparmor_parser"
Jul 29 18:51:31 node-4 kernel: [    9.043477] type=1400 audit(1469818260.036:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1070 comm="apparmor_parser"
Jul 29 18:51:31 node-4 kernel: [    9.043595] type=1400 audit(1469818260.036:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1070 comm="apparmor_parser"
Jul 29 18:51:31 node-4 kernel: [    9.046076] type=1400 audit(1469818260.040:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1061 comm="apparmor_parser"
Jul 29 18:51:31 node-4 kernel: [    9.549762] EXT4-fs (sda9): mounting ext2 file system using the ext4 subsystem
Jul 29 18:51:31 node-4 kernel: [    9.552229] EXT4-fs (sda9): mounted filesystem without journal. Opts: (null)
Jul 29 18:51:31 node-4 kernel: [    9.717859] enic 0000:06:00.0 enp6s0: Link UP
Jul 29 18:51:31 node-4 kernel: [    9.719079] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Jul 29 18:51:31 node-4 kernel: [    9.719085] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Jul 29 18:51:31 node-4 kernel: [   18.449421] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Jul 29 18:51:32 node-4 failsafe: Failsafe of 120 seconds reached.
Jul 29 18:51:32 node-4 kernel: [   41.886151] init: failsafe main process (8396) killed by TERM signal
Jul 29 18:51:33 node-4 dbus[8422]: [system] AppArmor D-Bus mediation is enabled
Jul 29 18:51:33 node-4 kernel: [   42.139690] audit_printk_skb: 30 callbacks suppressed
Jul 29 18:51:33 node-4 kernel: [   42.139693] type=1400 audit(1469818293.208:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8520 comm="apparmor_parser"
Jul 29 18:51:33 node-4 kernel: [   42.141822] type=1400 audit(1469818293.212:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8519 comm="apparmor_parser"
Jul 29 18:51:33 node-4 kernel: [   42.141869] type=1400 audit(1469818293.212:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8519 comm="apparmor_parser"
Jul 29 18:51:33 node-4 kernel: [   42.141892] type=1400 audit(1469818293.212:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8519 comm="apparmor_parser"
Jul 29 18:51:33 node-4 kernel: [   42.142833] type=1400 audit(1469818293.212:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8519 comm="apparmor_parser"
Jul 29 18:51:33 node-4 kernel: [   42.142876] type=1400 audit(1469818293.212:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8519 comm="apparmor_parser"
Jul 29 18:51:33 node-4 kernel: [   42.143263] type=1400 audit(1469818293.212:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8519 comm="apparmor_parser"
Jul 29 18:51:33 node-4 kernel: [   42.235991] type=1400 audit(1469818293.308:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8522 comm="apparmor_parser"
Jul 29 18:51:33 node-4 cron[8554]: (CRON) INFO (pidfile fd = 3)
Jul 29 18:51:33 node-4 anacron[8573]: Anacron 2.3 started on 2016-07-29
Jul 29 18:51:33 node-4 cron[8590]: (CRON) STARTUP (fork ok)
Jul 29 18:51:33 node-4 anacron[8573]: Will run job `cron.daily' in 5 min.
Jul 29 18:51:33 node-4 anacron[8573]: Will run job `cron.weekly' in 10 min.
Jul 29 18:51:33 node-4 anacron[8573]: Will run job `cron.monthly' in 15 min.
Jul 29 18:51:33 node-4 anacron[8573]: Jobs will be executed sequentially
Jul 29 18:51:33 node-4 multipathd: path checkers start up
Jul 29 18:51:33 node-4 cron[8590]: (CRON) INFO (Running @reboot jobs)
Jul 29 18:51:33 node-4 postfix/master[8733]: daemon started -- version 2.11.0, configuration /etc/postfix
Jul 29 18:51:37 node-4 puppet-agent[8918]: Reopening log files
Jul 29 18:51:37 node-4 puppet-agent[8918]: Could not request certificate: Connection refused - connect(2)
Jul 29 18:51:47 node-4 puppet-user[9106]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Jul 29 18:51:47 node-4 puppet-user[9106]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 29 18:51:48 node-4 puppet-user[9106]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Jul 29 18:51:48 node-4 puppet-user[9106]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Jul 29 18:51:48 node-4 puppet-user[9106]: Finished catalog run in 0.61 seconds
Jul 29 18:51:49 node-4 multipathd: uevent trigger error
Jul 29 18:51:49 node-4 puppet-user[9561]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 18:51:49 node-4 puppet-user[9561]: Compiled catalog for node-4.domain.tld in environment production in 0.08 seconds
Jul 29 18:51:49 node-4 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Jul 29 18:51:49 node-4 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Jul 29 18:51:49 node-4 puppet-user[9561]: (/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 29 18:51:49 node-4 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Jul 29 18:51:49 node-4 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Jul 29 18:51:49 node-4 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Jul 29 18:51:49 node-4 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Jul 29 18:51:49 node-4 puppet-user[9561]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Jul 29 18:51:49 node-4 puppet-user[9561]: Finished catalog run in 0.06 seconds
Jul 29 18:51:51 node-4 puppet-user[10018]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Jul 29 18:51:51 node-4 puppet-user[10018]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Jul 29 18:51:51 node-4 puppet-user[10018]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Jul 29 18:51:51 node-4 puppet-user[10018]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Jul 29 18:51:51 node-4 puppet-user[10018]: Finished catalog run in 0.03 seconds
Jul 29 18:51:52 node-4 puppet-user[10481]: (Scope(Class[main])) MODULAR: configuration_symlink
Jul 29 18:51:52 node-4 puppet-user[10481]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Jul 29 18:51:53 node-4 puppet-user[10481]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Jul 29 18:51:53 node-4 puppet-user[10481]: Finished catalog run in 0.04 seconds
Jul 29 18:51:54 node-4 puppet-user[10933]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Jul 29 18:51:54 node-4 puppet-user[10933]: Compiled catalog for node-4.domain.tld in environment production in 0.17 seconds
Jul 29 18:51:54 node-4 puppet-user[10933]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Jul 29 18:51:55 node-4 puppet-user[10933]: (/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 29 18:51:55 node-4 puppet-user[10933]: (/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 29 18:51:55 node-4 puppet-user[10933]: (/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 29 18:51:55 node-4 puppet-user[10933]: Finished catalog run in 1.17 seconds
Jul 29 18:51:57 node-4 puppet-user[11468]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Jul 29 18:51:57 node-4 puppet-user[11468]: Compiled catalog for node-4.domain.tld in environment production in 0.22 seconds
Jul 29 18:51:57 node-4 puppet-user[11468]: (/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 29 18:51:57 node-4 puppet-user[11468]: (/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 29 18:51:57 node-4 puppet-user[11468]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Jul 29 18:51:57 node-4 puppet-user[11468]: (/Stage[main]/Apt/File[preferences]/ensure) created
Jul 29 18:51:57 node-4 puppet-user[11468]: (/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 29 18:51:57 node-4 puppet-user[11468]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Jul 29 18:51:57 node-4 puppet-user[11468]: Finished catalog run in 0.35 seconds
Jul 29 18:51:59 node-4 puppet-user[11946]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Jul 29 18:51:59 node-4 puppet-user[11946]: Compiled catalog for node-4.domain.tld in environment production in 0.16 seconds
Jul 29 18:51:59 node-4 puppet-user[11946]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Jul 29 18:51:59 node-4 kernel: [   68.576182] nr_pdflush_threads exported in /proc is scheduled for removal
Jul 29 18:51:59 node-4 kernel: [   68.576231] 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 29 18:51:59 node-4 puppet-user[11946]: (/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 29 18:51:59 node-4 puppet-user[11946]: Finished catalog run in 0.05 seconds
Jul 29 18:52:01 node-4 puppet-user[12579]: (Scope(Class[main])) MODULAR: sync_time
Jul 29 18:52:01 node-4 puppet-user[12579]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Jul 29 18:52:01 node-4 ntpdate[12995]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Jul 29 18:52:01 node-4 CRON[12997]: (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 29 18:52:07 node-4 ntpdate[12995]: adjust time server 10.20.0.2 offset -0.015677 sec
Jul 29 18:52:07 node-4 puppet-user[12579]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Jul 29 18:52:07 node-4 puppet-user[12579]: Finished catalog run in 6.15 seconds
Jul 29 18:52:12 node-4 kernel: [   80.901572] init: plymouth-upstart-bridge main process ended, respawning
Jul 29 18:52:12 node-4 puppet-agent[8918]: Could not run: SIGTERM
Jul 29 18:52:12 node-4 kernel: [   81.188693] ip_tables: (C) 2000-2006 Netfilter Core Team
Jul 29 18:52:12 node-4 ec2: 
Jul 29 18:52:12 node-4 ec2: #############################################################
Jul 29 18:52:12 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Jul 29 18:52:12 node-4 ec2: 1024 a9:55:d7:bb:65:a0:a4:b4:14:68:6f:56:85:92:bf:ea  root@node-4.domain.tld (DSA)
Jul 29 18:52:12 node-4 ec2: 256 ee:ce:c3:81:24:e9:48:92:54:bc:92:0a:67:ff:71:65  root@node-4.domain.tld (ECDSA)
Jul 29 18:52:12 node-4 ec2: 256 73:ff:c0:54:f8:93:b1:3b:2c:2b:eb:71:85:c4:e4:56  root@node-4.domain.tld (ED25519)
Jul 29 18:52:12 node-4 ec2: 2048 35:d7:9b:f5:63:56:3e:47:39:73:c3:34:d3:fd:ab:6d  root@node-4.domain.tld (RSA)
Jul 29 18:52:12 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Jul 29 18:52:12 node-4 ec2: #############################################################
Jul 29 18:52:26 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 18:52:26 node-4 nailgun-agent: D, [2016-07-29T18:52:01.615779 #13000] DEBUG -- : Sleep for 25 seconds before sending request
Jul 29 18:52:26 node-4 nailgun-agent: I, [2016-07-29T18:52:26.630800 #13000]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 18:52:27 node-4 nailgun-agent: D, [2016-07-29T18:52:27.032201 #13000] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.171378 #13000] DEBUG -- : Trying to find block devices
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.171599 #13000] DEBUG -- : Found block device: sda
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.171725 #13000] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.171772 #13000] DEBUG -- : Trying to get list of physical devices
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.172065 #13000] DEBUG -- : Getting udev properties for device: sda
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.175479 #13000] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837274ff201cc7880a059ea121 /dev/disk/by-id/wwn-0x618e72837274ff201cc7880a059ea121 /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"=>"0021a19e050a88c71c20ff747283728e", "ID_SERIAL"=>"3618e72837274ff201cc7880a059ea121", "ID_SERIAL_SHORT"=>"618e72837274ff201cc7880a059ea121", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837274ff20", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7880a059ea121", "ID_WWN_WITH_EXTENSION"=>"0x618e72837274ff201cc788
Jul 29 18:52:39 node-4 nailgun-agent: 0a059ea121", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"31462", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.175531 #13000] DEBUG -- : Trying to find out if device sda is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.175613 #13000] DEBUG -- : Device sda removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.175643 #13000] DEBUG -- : Device sda seems to be appropriate
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.176414 #13000] DEBUG -- : Getting udev properties for device: dm-0
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.179833 #13000] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-fpOHj5XA4tDEg4eAgienwsvx3zwNTXsvZxvm1oDZBLSylQYVgWelmR6iK4mdC0P6 /dev/disk/by-uuid/d2cf7a63-1c3e-4a30-8e74-a6d50c7c766d /dev/image/glance /dev/mapper/image-glance", "DEVNAME"=>"/dev/dm-0", "DEVPATH"=>"/devices/virtual/block/dm-0", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"glance", "DM_NAME"=>"image-glance", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-fpOHj5XA4tDEg4eAgienwsvx3zwNTXsvZxvm1oDZBLSylQYVgWelmR6iK4mdC0P6", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d2cf7a63-1c3e-4a30-8e74-a6d50c7c766d", "ID_FS_UUID_ENC"=>"d2cf7a63-1c3e-4a30-8e74-a6d50c7c766d", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61122", "nomdmonddf"=>"1", "nom
Jul 29 18:52:39 node-4 nailgun-agent: dmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.179886 #13000] DEBUG -- : Trying to find out if device dm-0 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.179945 #13000] DEBUG -- : Device dm-0 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.179972 #13000] DEBUG -- : Device dm-0 seems to be appropriate
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.180000 #13000] DEBUG -- : Getting udev properties for device: dm-1
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.183163 #13000] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-ih8lDR7rwLGrfdOAiehP4CW99EVVDMCZ20iOZmaCkhqYGaeL6zTEG29QDoZWcgq1 /dev/disk/by-uuid/1895ed19-3ba0-40cb-b092-86124ff59c5b /dev/horizon/horizontmp /dev/mapper/horizon-horizontmp", "DEVNAME"=>"/dev/dm-1", "DEVPATH"=>"/devices/virtual/block/dm-1", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"horizontmp", "DM_NAME"=>"horizon-horizontmp", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-ih8lDR7rwLGrfdOAiehP4CW99EVVDMCZ20iOZmaCkhqYGaeL6zTEG29QDoZWcgq1", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"1895ed19-3ba0-40cb-b092-86124ff59c5b", "ID_FS_UUID_ENC"=>"1895ed19-3ba0-40cb-b092-86124ff59c5b", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2
Jul 29 18:52:39 node-4 nailgun-agent: 127", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.183219 #13000] DEBUG -- : Trying to find out if device dm-1 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.183328 #13000] DEBUG -- : Device dm-1 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.183357 #13000] DEBUG -- : Device dm-1 seems to be appropriate
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.183385 #13000] DEBUG -- : Getting udev properties for device: dm-2
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.186505 #13000] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-B2iZo1TdleFZwmVJ962BM5mPRqlvvEewv8FzZeew9lkHHjNVyIzVLLaCCe3Vf89u /dev/disk/by-uuid/01985ea6-4d06-45e1-adc8-5549c0967201 /dev/mapper/mysql-root /dev/mysql/root", "DEVNAME"=>"/dev/dm-2", "DEVPATH"=>"/devices/virtual/block/dm-2", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"mysql-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-B2iZo1TdleFZwmVJ962BM5mPRqlvvEewv8FzZeew9lkHHjNVyIzVLLaCCe3Vf89u", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"01985ea6-4d06-45e1-adc8-5549c0967201", "ID_FS_UUID_ENC"=>"01985ea6-4d06-45e1-adc8-5549c0967201", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3012", "nomdmond
Jul 29 18:52:39 node-4 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.186559 #13000] DEBUG -- : Trying to find out if device dm-2 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.186620 #13000] DEBUG -- : Device dm-2 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.186647 #13000] DEBUG -- : Device dm-2 seems to be appropriate
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.186692 #13000] DEBUG -- : Getting udev properties for device: dm-3
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.189871 #13000] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-cYMoG1dJueQWkeJjkNJ8NMYVhaEvi9KXFm1jNt7x0xrAHPBwe3gsHJQD56s3TM5N /dev/disk/by-uuid/a236a497-a8d5-42e8-af0c-6eac8359c6be /dev/logs/log /dev/mapper/logs-log", "DEVNAME"=>"/dev/dm-3", "DEVPATH"=>"/devices/virtual/block/dm-3", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"log", "DM_NAME"=>"logs-log", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-cYMoG1dJueQWkeJjkNJ8NMYVhaEvi9KXFm1jNt7x0xrAHPBwe3gsHJQD56s3TM5N", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"a236a497-a8d5-42e8-af0c-6eac8359c6be", "ID_FS_UUID_ENC"=>"a236a497-a8d5-42e8-af0c-6eac8359c6be", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"5010", "nomdmonddf"=>"1", 
Jul 29 18:52:39 node-4 nailgun-agent: "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.189925 #13000] DEBUG -- : Trying to find out if device dm-3 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.189986 #13000] DEBUG -- : Device dm-3 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.190016 #13000] DEBUG -- : Device dm-3 seems to be appropriate
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.190046 #13000] DEBUG -- : Getting udev properties for device: dm-4
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.193135 #13000] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-lRHKT1ui4PzKRD1EX8cynFixMeWNN08dbKy5sHWr2cYi3ATSOJdgc1hi66yXXbC6 /dev/disk/by-uuid/c841bdb3-87eb-487f-9803-dc9bbf150880 /dev/mapper/os-root /dev/os/root", "DEVNAME"=>"/dev/dm-4", "DEVPATH"=>"/devices/virtual/block/dm-4", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"root", "DM_NAME"=>"os-root", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-lRHKT1ui4PzKRD1EX8cynFixMeWNN08dbKy5sHWr2cYi3ATSOJdgc1hi66yXXbC6", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"c841bdb3-87eb-487f-9803-dc9bbf150880", "ID_FS_UUID_ENC"=>"c841bdb3-87eb-487f-9803-dc9bbf150880", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1302", "nomdmonddf"=>"1", "nomd
Jul 29 18:52:39 node-4 nailgun-agent: monisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.193223 #13000] DEBUG -- : Trying to find out if device dm-4 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.193297 #13000] DEBUG -- : Device dm-4 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.193325 #13000] DEBUG -- : Device dm-4 seems to be appropriate
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.193353 #13000] DEBUG -- : Getting udev properties for device: dm-5
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.196786 #13000] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-lRHKT1ui4PzKRD1EX8cynFixMeWNN08di8I5h9V0qal2pjCVfhDlPAo7cmR9lO2y /dev/disk/by-uuid/2a60931e-40c8-4d2d-a11f-94fb1a41a1e1 /dev/mapper/os-swap /dev/os/swap", "DEVNAME"=>"/dev/dm-5", "DEVPATH"=>"/devices/virtual/block/dm-5", "DEVTYPE"=>"disk", "DM_LV_NAME"=>"swap", "DM_NAME"=>"os-swap", "DM_STATE"=>"ACTIVE", "DM_SUSPENDED"=>"0", "DM_TABLE_STATE"=>"LIVE", "DM_TYPE"=>"raid", "DM_UDEV_DISABLE_LIBRARY_FALLBACK_FLAG"=>"1", "DM_UDEV_PRIMARY_SOURCE_FLAG"=>"1", "DM_UDEV_RULES"=>"1", "DM_UUID"=>"LVM-lRHKT1ui4PzKRD1EX8cynFixMeWNN08di8I5h9V0qal2pjCVfhDlPAo7cmR9lO2y", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"2a60931e-40c8-4d2d-a11f-94fb1a41a1e1", "ID_FS_UUID_ENC"=>"2a60931e-40c8-4d2d-a11f-94fb1a41a1e1", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1629", "nomdmonddf"=>"1", "nomdmonisw"
Jul 29 18:52:39 node-4 nailgun-agent: =>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.196847 #13000] DEBUG -- : Trying to find out if device dm-5 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.196941 #13000] DEBUG -- : Device dm-5 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.196971 #13000] DEBUG -- : Device dm-5 seems to be appropriate
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.197041 #13000] DEBUG -- : Getting udev properties for device: ram0
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.199816 #13000] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62564", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.199867 #13000] DEBUG -- : Trying to find out if device ram0 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.199974 #13000] DEBUG -- : Device ram0 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.200016 #13000] DEBUG -- : Getting udev properties for device: ram1
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.203223 #13000] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"62858", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.203273 #13000] DEBUG -- : Trying to find out if device ram1 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.203338 #13000] DEBUG -- : Device ram1 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.203378 #13000] DEBUG -- : Getting udev properties for device: ram2
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.206393 #13000] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64865", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.206443 #13000] DEBUG -- : Trying to find out if device ram2 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.206522 #13000] DEBUG -- : Device ram2 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.206560 #13000] DEBUG -- : Getting udev properties for device: ram3
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.209409 #13000] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65402", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.209461 #13000] DEBUG -- : Trying to find out if device ram3 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.209602 #13000] DEBUG -- : Device ram3 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.209643 #13000] DEBUG -- : Getting udev properties for device: ram4
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.212539 #13000] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65549", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.212589 #13000] DEBUG -- : Trying to find out if device ram4 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.212655 #13000] DEBUG -- : Device ram4 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.212697 #13000] DEBUG -- : Getting udev properties for device: ram5
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.215560 #13000] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"65850", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.215647 #13000] DEBUG -- : Trying to find out if device ram5 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.215718 #13000] DEBUG -- : Device ram5 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.215756 #13000] DEBUG -- : Getting udev properties for device: ram6
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.218473 #13000] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"66142", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.218518 #13000] DEBUG -- : Trying to find out if device ram6 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.218576 #13000] DEBUG -- : Device ram6 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.218631 #13000] DEBUG -- : Getting udev properties for device: ram7
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.221146 #13000] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"66387", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.221206 #13000] DEBUG -- : Trying to find out if device ram7 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.221261 #13000] DEBUG -- : Device ram7 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.221312 #13000] DEBUG -- : Getting udev properties for device: ram8
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.223791 #13000] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"66930", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.223836 #13000] DEBUG -- : Trying to find out if device ram8 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.223894 #13000] DEBUG -- : Device ram8 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.223930 #13000] DEBUG -- : Getting udev properties for device: ram9
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.226582 #13000] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"66999", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.226647 #13000] DEBUG -- : Trying to find out if device ram9 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.226738 #13000] DEBUG -- : Device ram9 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.226798 #13000] DEBUG -- : Getting udev properties for device: loop0
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.229468 #13000] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60345", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.229518 #13000] DEBUG -- : Trying to find out if device loop0 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.229574 #13000] DEBUG -- : Device loop0 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.229610 #13000] DEBUG -- : Getting udev properties for device: loop1
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.232504 #13000] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60558", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.232549 #13000] DEBUG -- : Trying to find out if device loop1 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.232624 #13000] DEBUG -- : Device loop1 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.232660 #13000] DEBUG -- : Getting udev properties for device: loop2
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.236386 #13000] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60700", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.236459 #13000] DEBUG -- : Trying to find out if device loop2 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.236591 #13000] DEBUG -- : Device loop2 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.236646 #13000] DEBUG -- : Getting udev properties for device: loop3
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.239556 #13000] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60944", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.239605 #13000] DEBUG -- : Trying to find out if device loop3 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.239680 #13000] DEBUG -- : Device loop3 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.239718 #13000] DEBUG -- : Getting udev properties for device: loop4
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.242520 #13000] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"60956", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.242628 #13000] DEBUG -- : Trying to find out if device loop4 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.242711 #13000] DEBUG -- : Device loop4 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.242755 #13000] DEBUG -- : Getting udev properties for device: loop5
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.245990 #13000] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61069", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.246033 #13000] DEBUG -- : Trying to find out if device loop5 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.246106 #13000] DEBUG -- : Device loop5 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.246138 #13000] DEBUG -- : Getting udev properties for device: loop6
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.248836 #13000] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61249", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.248878 #13000] DEBUG -- : Trying to find out if device loop6 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.248936 #13000] DEBUG -- : Device loop6 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.248982 #13000] DEBUG -- : Getting udev properties for device: loop7
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.251412 #13000] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61448", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.251455 #13000] DEBUG -- : Trying to find out if device loop7 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.251526 #13000] DEBUG -- : Device loop7 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.251559 #13000] DEBUG -- : Getting udev properties for device: ram10
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.260410 #13000] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63080", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.260446 #13000] DEBUG -- : Trying to find out if device ram10 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.260488 #13000] DEBUG -- : Device ram10 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.260515 #13000] DEBUG -- : Getting udev properties for device: ram11
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.263034 #13000] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63332", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.263066 #13000] DEBUG -- : Trying to find out if device ram11 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.263111 #13000] DEBUG -- : Device ram11 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.263137 #13000] DEBUG -- : Getting udev properties for device: ram12
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.265375 #13000] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63743", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.265407 #13000] DEBUG -- : Trying to find out if device ram12 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.265452 #13000] DEBUG -- : Device ram12 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.265483 #13000] DEBUG -- : Getting udev properties for device: ram13
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.267865 #13000] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"63962", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.267938 #13000] DEBUG -- : Trying to find out if device ram13 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.268045 #13000] DEBUG -- : Device ram13 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.268098 #13000] DEBUG -- : Getting udev properties for device: ram14
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.271296 #13000] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64386", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.271437 #13000] DEBUG -- : Trying to find out if device ram14 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.271539 #13000] DEBUG -- : Device ram14 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.271593 #13000] DEBUG -- : Getting udev properties for device: ram15
Jul 29 18:52:39 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.273870 #13000] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"64722", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.273942 #13000] DEBUG -- : Trying to find out if device ram15 is removable or not
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274108 #13000] DEBUG -- : Device ram15 removable parameter: "0"
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274198 #13000] 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-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0"}]
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274239 #13000] DEBUG -- : Block device seems to be physical data storage: sda
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274325 #13000] DEBUG -- : Found block device: dm-0
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274362 #13000] DEBUG -- : Block device info: {"size"=>"4457521152", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274398 #13000] DEBUG -- : Found block device: dm-1
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274428 #13000] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274456 #13000] DEBUG -- : Found block device: dm-2
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274483 #13000] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274509 #13000] DEBUG -- : Found block device: dm-3
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274592 #13000] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274618 #13000] DEBUG -- : Found block device: dm-4
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274647 #13000] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274673 #13000] DEBUG -- : Found block device: dm-5
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274701 #13000] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274725 #13000] DEBUG -- : Found block device: ram0
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274754 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274779 #13000] DEBUG -- : Found block device: ram1
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274809 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274834 #13000] DEBUG -- : Found block device: ram2
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274923 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274953 #13000] DEBUG -- : Found block device: ram3
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.274981 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275005 #13000] DEBUG -- : Found block device: ram4
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275033 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275058 #13000] DEBUG -- : Found block device: ram5
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275088 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275111 #13000] DEBUG -- : Found block device: ram6
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275139 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275163 #13000] DEBUG -- : Found block device: ram7
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275191 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275285 #13000] DEBUG -- : Found block device: ram8
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275314 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275339 #13000] DEBUG -- : Found block device: ram9
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275368 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275391 #13000] DEBUG -- : Found block device: loop0
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275417 #13000] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275440 #13000] DEBUG -- : Found block device: loop1
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275465 #13000] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275488 #13000] DEBUG -- : Found block device: loop2
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275516 #13000] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275636 #13000] DEBUG -- : Found block device: loop3
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275667 #13000] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275691 #13000] DEBUG -- : Found block device: loop4
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275716 #13000] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275741 #13000] DEBUG -- : Found block device: loop5
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275771 #13000] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275795 #13000] DEBUG -- : Found block device: loop6
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275822 #13000] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275847 #13000] DEBUG -- : Found block device: loop7
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275960 #13000] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.275988 #13000] DEBUG -- : Found block device: ram10
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276016 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276040 #13000] DEBUG -- : Found block device: ram11
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276067 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276092 #13000] DEBUG -- : Found block device: ram12
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276120 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276145 #13000] DEBUG -- : Found block device: ram13
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276176 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276301 #13000] DEBUG -- : Found block device: ram14
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276330 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276353 #13000] DEBUG -- : Found block device: ram15
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276379 #13000] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.276455 #13000] 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-0x618e72837274ff201cc7880a059ea121", "disk/by-id/scsi-3618e72837274ff201cc7880a059ea121"], :removable=>"0", :paths=>nil}]
Jul 29 18:52:39 node-4 nailgun-agent: D, [2016-07-29T18:52:39.494780 #13000] DEBUG -- : Response: status: 200 body: {"id": 4}
Jul 29 18:52:39 node-4 nailgun-agent: I, [2016-07-29T18:52:39.508485 #13000]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 29 18:52:55 node-4 puppet-user[13677]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Jul 29 18:52:55 node-4 puppet-user[13677]: Compiled catalog for node-4.domain.tld in environment production in 0.11 seconds
Jul 29 18:52:55 node-4 puppet-user[13677]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Jul 29 18:52:55 node-4 puppet-user[13677]: (/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 29 18:52:55 node-4 puppet-user[13677]: Finished catalog run in 0.08 seconds
Jul 29 18:52:57 node-4 puppet-user[14121]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Jul 29 18:52:59 node-4 puppet-user[14121]: Compiled catalog for node-4.domain.tld in environment production in 1.47 seconds
Jul 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Jul 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Jul 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:52:59 node-4 puppet-user[14121]: (/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 29 18:53:01 node-4 CRON[14646]: (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 29 18:53:09 node-4 puppet-user[14121]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Jul 29 18:53:09 node-4 puppet-user[14121]: Finished catalog run in 10.24 seconds
Jul 29 18:53:11 node-4 puppet-user[14885]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Jul 29 18:53:11 node-4 puppet-user[14885]: Compiled catalog for node-4.domain.tld in environment production in 0.14 seconds
Jul 29 18:53:16 node-4 puppet-user[14885]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Jul 29 18:53:26 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 18:53:26 node-4 nailgun-agent: I, [2016-07-29T18:53:26.685606 #14649]  INFO -- : API URL is https://10.20.0.2:8443/api
Jul 29 18:53:39 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Jul 29 18:53:39 node-4 nailgun-agent: I, [2016-07-29T18:53:39.775663 #14649]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Jul 29 18:53:48 node-4 puppet-user[14885]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Jul 29 18:53:48 node-4 puppet-user[14885]: Finished catalog run in 36.28 seconds
Jul 29 18:53:50 node-4 puppet-user[17677]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Jul 29 18:53:50 node-4 puppet-user[17677]: Compiled catalog for node-4.domain.tld in environment production in 0.56 seconds
Jul 29 18:53:50 node-4 puppet-user[17677]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Jul 29 18:53:50 node-4 puppet-user[17677]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Jul 29 18:53:50 node-4 puppet-user[17677]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Jul 29 18:53:50 node-4 puppet-user[17677]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Jul 29 18:53:51 node-4 puppet-user[17677]: Finished catalog run in 0.12 seconds
Jul 29 18:53:52 node-4 puppet-user[18131]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Jul 29 18:53:53 node-4 puppet-user[18131]: Compiled catalog for node-4.domain.tld in environment production in 0.92 seconds
Jul 29 18:53:54 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Jul 29 18:53:54 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Jul 29 18:53:54 node-4 crontab[18568]: (root) LIST (root)
Jul 29 18:53:54 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Jul 29 18:53:54 node-4 crontab[18569]: (root) REPLACE (root)
Jul 29 18:53:56 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Jul 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Jul 29 18:53:57 node-4 puppet-user[18131]: (/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 29 18:53:57 node-4 puppet-user[18131]: (/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 29 18:53:57 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Jul 29 18:53:58 node-4 puppet-user[18131]: (/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 29 18:53:58 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8369" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Jul 29 18:53:58 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Jul 29 18:54:00 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:00 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:00 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:00 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:20 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:20 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:20 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:20 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:22 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:22 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:22 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:22 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:22 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:24 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:24 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:24 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:24 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:24 node-4 multipathd: uevent trigger error
<27>Jul 29 18:54:24 node-4 multipathd: uevent trigger error
<27>Jul 29 18:55:24 node-4 ntpdate[29325]: no servers can be used, exiting
<27>Jul 29 18:55:56 node-4 multipathd: uevent trigger error
<27>Jul 29 18:55:56 node-4 multipathd: uevent trigger error
<27>Jul 29 18:55:56 node-4 multipathd: uevent trigger error
<27>Jul 29 18:55:56 node-4 multipathd: uevent trigger error
<27>Jul 29 18:55:59 node-4 multipathd: uevent trigger error
<27>Jul 29 18:55:59 node-4 multipathd: uevent trigger error
<27>Jul 29 18:55:59 node-4 multipathd: uevent trigger error
<27>Jul 29 18:55:59 node-4 multipathd: uevent trigger error
<27>Jul 29 18:55:59 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:11 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:11 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:11 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:11 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:11 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:14 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:14 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:14 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:14 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:14 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:14 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:46 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:46 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:46 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:46 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:46 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:46 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:46 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:53 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:53 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:53 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:53 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:53 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:53 node-4 multipathd: uevent trigger error
<27>Jul 29 18:56:53 node-4 multipathd: uevent trigger error
<43>Jul 29 18:57:08 node-4 apache2_error [Fri Jul 29 18:57:05.631185 2016] [mpm_event:notice] [pid 11403:tid 140225382389632] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 18:57:08 node-4 apache2_error [Fri Jul 29 18:57:05.631284 2016] [core:notice] [pid 11403:tid 140225382389632] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 29 18:57:08 node-4 apache2_error [Fri Jul 29 18:57:08.636538 2016] [mpm_event:notice] [pid 11403:tid 140225382389632] AH00491: caught SIGTERM, shutting down
<27>Jul 29 18:57:12 node-4 multipathd: uevent trigger error
<27>Jul 29 18:57:12 node-4 multipathd: uevent trigger error
<27>Jul 29 18:57:12 node-4 multipathd: uevent trigger error
<27>Jul 29 18:57:12 node-4 multipathd: uevent trigger error
<27>Jul 29 18:57:12 node-4 multipathd: uevent trigger error
<27>Jul 29 18:57:12 node-4 multipathd: uevent trigger error
<43>Jul 29 18:57:19 node-4 apache2_error [Fri Jul 29 18:57:09.777332 2016] [mpm_worker:notice] [pid 11979:tid 140597586827136] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 18:57:19 node-4 apache2_error [Fri Jul 29 18:57:09.777358 2016] [core:notice] [pid 11979:tid 140597586827136] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 18:57:48 node-4 multipathd: uevent trigger error
<27>Jul 29 18:57:49 node-4 multipathd: uevent trigger error
<27>Jul 29 18:57:49 node-4 multipathd: uevent trigger error
<43>Jul 29 18:57:49 node-4 apache2_error [Fri Jul 29 18:57:46.092312 2016] [mpm_worker:notice] [pid 11979:tid 140597586827136] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 18:57:49 node-4 apache2_error [Fri Jul 29 18:57:46.099678 2016] [mpm_worker:warn] [pid 11979:tid 140597586827136] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 18:57:49 node-4 apache2_error [Fri Jul 29 18:57:46.100423 2016] [mpm_worker:notice] [pid 11979:tid 140597586827136] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Jul 29 18:57:49 node-4 apache2_error [Fri Jul 29 18:57:46.100436 2016] [core:notice] [pid 11979:tid 140597586827136] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 18:57:49 node-4 multipathd: uevent trigger error
<27>Jul 29 18:57:49 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:23 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Jul 29 18:58:28 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:28 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:28 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:28 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:31 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:31 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:31 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:31 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:31 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:37 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:37 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:37 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:37 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:37 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:45 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:45 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:45 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:45 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:50 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:50 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:50 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:50 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:50 node-4 multipathd: uevent trigger error
<129>Jul 29 18:58:53 node-4 haproxy[25119]: 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 29 18:58:55 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:55 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:55 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:55 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:55 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:58 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:58 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:58 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:58 node-4 multipathd: uevent trigger error
<27>Jul 29 18:58:58 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:01 node-4 haproxy[27121]: 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 29 18:59:01 node-4 haproxy[27121]: 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 29 18:59:03 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:03 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:03 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:03 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:03 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:05 node-4 haproxy[28179]: 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 29 18:59:06 node-4 haproxy[28183]: 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 29 18:59:07 node-4 haproxy[28183]: 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 29 18:59:08 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:08 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:08 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:08 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:10 node-4 haproxy[29252]: Server keystone-1/node-4 is DOWN, reason: Layer7 wrong status, code: 404, info: "Not Found", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:11 node-4 haproxy[29259]: 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 29 18:59:11 node-4 haproxy[29259]: 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 29 18:59:11 node-4 haproxy[29259]: 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 29 18:59:12 node-4 haproxy[29259]: 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 29 18:59:13 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:13 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:13 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:13 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:13 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:15 node-4 haproxy[30337]: 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 29 18:59:16 node-4 haproxy[30341]: 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 29 18:59:16 node-4 haproxy[30341]: 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 29 18:59:16 node-4 haproxy[30341]: 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 29 18:59:17 node-4 haproxy[30341]: 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 29 18:59:17 node-4 haproxy[30341]: 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 29 18:59:18 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:18 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:18 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:18 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:18 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:19 node-4 haproxy[30341]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:19 node-4 haproxy[30341]: 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 29 18:59:19 node-4 haproxy[30341]: proxy aodh has no server available!
<129>Jul 29 18:59:20 node-4 haproxy[31401]: 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 29 18:59:21 node-4 haproxy[31410]: 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 29 18:59:21 node-4 haproxy[31410]: 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 29 18:59:21 node-4 haproxy[31410]: 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 29 18:59:22 node-4 haproxy[31410]: 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 29 18:59:22 node-4 haproxy[31410]: 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 29 18:59:22 node-4 haproxy[31410]: 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 29 18:59:23 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:23 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:23 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:23 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:23 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:24 node-4 haproxy[31410]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:24 node-4 haproxy[31410]: 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 29 18:59:24 node-4 haproxy[31410]: proxy aodh has no server available!
<129>Jul 29 18:59:24 node-4 haproxy[31410]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:24 node-4 haproxy[31410]: 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 29 18:59:24 node-4 haproxy[31410]: proxy ceilometer has no server available!
<129>Jul 29 18:59:26 node-4 haproxy[32485]: 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 29 18:59:26 node-4 haproxy[32485]: 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 29 18:59:26 node-4 haproxy[32485]: 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 29 18:59:26 node-4 haproxy[32485]: 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 29 18:59:27 node-4 haproxy[32485]: 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 29 18:59:27 node-4 haproxy[32485]: 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 29 18:59:27 node-4 haproxy[32485]: 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 29 18:59:28 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:28 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:28 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:28 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:28 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:28 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:29 node-4 haproxy[32485]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:29 node-4 haproxy[32485]: 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 29 18:59:29 node-4 haproxy[32485]: proxy aodh has no server available!
<129>Jul 29 18:59:29 node-4 haproxy[32485]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:29 node-4 haproxy[32485]: 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 29 18:59:29 node-4 haproxy[32485]: proxy ceilometer has no server available!
<129>Jul 29 18:59:31 node-4 haproxy[1310]: 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 29 18:59:31 node-4 haproxy[1310]: 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 29 18:59:31 node-4 haproxy[1310]: 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 29 18:59:31 node-4 haproxy[1310]: 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 29 18:59:31 node-4 haproxy[1310]: 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 29 18:59:32 node-4 haproxy[1310]: 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 29 18:59:32 node-4 haproxy[1310]: 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 29 18:59:32 node-4 haproxy[1310]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:32 node-4 haproxy[1310]: 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 29 18:59:33 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:33 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:33 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:33 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:33 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:34 node-4 haproxy[1310]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:34 node-4 haproxy[1310]: 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 29 18:59:34 node-4 haproxy[1310]: proxy aodh has no server available!
<129>Jul 29 18:59:34 node-4 haproxy[1310]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:34 node-4 haproxy[1310]: 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 29 18:59:34 node-4 haproxy[1310]: proxy ceilometer has no server available!
<27>Jul 29 18:59:35 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Jul 29 18:59:36 node-4 haproxy[2452]: 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 29 18:59:36 node-4 haproxy[2452]: 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 29 18:59:36 node-4 haproxy[2452]: 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 29 18:59:36 node-4 haproxy[2452]: 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 29 18:59:36 node-4 haproxy[2452]: 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 29 18:59:36 node-4 haproxy[2452]: 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 29 18:59:37 node-4 haproxy[2452]: 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 29 18:59:37 node-4 haproxy[2452]: 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 29 18:59:37 node-4 haproxy[2452]: 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 29 18:59:37 node-4 haproxy[2452]: 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 29 18:59:37 node-4 haproxy[2452]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:37 node-4 haproxy[2452]: 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 29 18:59:38 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:38 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:38 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:38 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:38 node-4 haproxy[2452]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:38 node-4 haproxy[2452]: 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 29 18:59:38 node-4 haproxy[2452]: proxy glance-registry has no server available!
<129>Jul 29 18:59:39 node-4 haproxy[2452]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:39 node-4 haproxy[2452]: 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 29 18:59:39 node-4 haproxy[2452]: proxy aodh has no server available!
<129>Jul 29 18:59:39 node-4 haproxy[2452]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:39 node-4 haproxy[2452]: 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 29 18:59:39 node-4 haproxy[2452]: proxy ceilometer has no server available!
<129>Jul 29 18:59:41 node-4 haproxy[3698]: 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 29 18:59:41 node-4 haproxy[3698]: 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 29 18:59:41 node-4 haproxy[3698]: 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 29 18:59:41 node-4 haproxy[3698]: 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 29 18:59:41 node-4 haproxy[3698]: 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 29 18:59:41 node-4 haproxy[3698]: 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 29 18:59:42 node-4 haproxy[3698]: 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 29 18:59:42 node-4 haproxy[3698]: 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 29 18:59:42 node-4 haproxy[3698]: 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 29 18:59:42 node-4 haproxy[3698]: 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 29 18:59:42 node-4 haproxy[3698]: 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 29 18:59:42 node-4 haproxy[3698]: 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 29 18:59:42 node-4 haproxy[3698]: 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 29 18:59:42 node-4 haproxy[3698]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:43 node-4 haproxy[3698]: 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 29 18:59:43 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:43 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:43 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:43 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:43 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:44 node-4 haproxy[3698]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:44 node-4 haproxy[3698]: 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 29 18:59:44 node-4 haproxy[3698]: proxy glance-registry has no server available!
<129>Jul 29 18:59:44 node-4 haproxy[3698]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:44 node-4 haproxy[3698]: 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 29 18:59:44 node-4 haproxy[3698]: proxy aodh has no server available!
<129>Jul 29 18:59:44 node-4 haproxy[3698]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:44 node-4 haproxy[3698]: 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 29 18:59:44 node-4 haproxy[3698]: proxy ceilometer has no server available!
<129>Jul 29 18:59:44 node-4 haproxy[3698]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:44 node-4 haproxy[3698]: 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 29 18:59:44 node-4 haproxy[3698]: proxy nova-novncproxy has no server available!
<129>Jul 29 18:59:46 node-4 haproxy[4817]: 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 29 18:59:46 node-4 haproxy[4817]: 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 29 18:59:46 node-4 haproxy[4817]: 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 29 18:59:46 node-4 haproxy[4817]: 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 29 18:59:46 node-4 haproxy[4817]: 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 29 18:59:47 node-4 haproxy[4824]: 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 29 18:59:47 node-4 haproxy[4824]: 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 29 18:59:47 node-4 haproxy[4824]: 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 29 18:59:47 node-4 haproxy[4824]: 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 29 18:59:47 node-4 haproxy[4824]: 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 29 18:59:47 node-4 haproxy[4824]: 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 29 18:59:47 node-4 haproxy[4824]: 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 29 18:59:47 node-4 haproxy[4824]: 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 29 18:59:48 node-4 haproxy[4824]: 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 29 18:59:48 node-4 haproxy[4824]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:48 node-4 haproxy[4824]: 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 29 18:59:48 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:48 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:48 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:48 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:48 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:48 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:49 node-4 haproxy[4824]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:49 node-4 haproxy[4824]: 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 29 18:59:49 node-4 haproxy[4824]: proxy glance-registry has no server available!
<129>Jul 29 18:59:49 node-4 haproxy[4824]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:49 node-4 haproxy[4824]: 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 29 18:59:49 node-4 haproxy[4824]: proxy aodh has no server available!
<129>Jul 29 18:59:49 node-4 haproxy[4824]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:49 node-4 haproxy[4824]: 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 29 18:59:49 node-4 haproxy[4824]: proxy ceilometer has no server available!
<129>Jul 29 18:59:49 node-4 haproxy[4824]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:50 node-4 haproxy[4824]: 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 29 18:59:50 node-4 haproxy[4824]: proxy nova-novncproxy has no server available!
<129>Jul 29 18:59:51 node-4 haproxy[5988]: 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 29 18:59:51 node-4 haproxy[5988]: 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 29 18:59:52 node-4 haproxy[5992]: 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 29 18:59:52 node-4 haproxy[5992]: 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 29 18:59:52 node-4 haproxy[5992]: 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 29 18:59:52 node-4 haproxy[5992]: 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 29 18:59:52 node-4 haproxy[5992]: 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 29 18:59:52 node-4 haproxy[5992]: 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 29 18:59:52 node-4 haproxy[5992]: 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 29 18:59:52 node-4 haproxy[5992]: 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 29 18:59:52 node-4 haproxy[5992]: 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 29 18:59:53 node-4 haproxy[5992]: 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 29 18:59:53 node-4 haproxy[5992]: 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 29 18:59:53 node-4 haproxy[5992]: 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 29 18:59:53 node-4 haproxy[5992]: 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 29 18:59:53 node-4 haproxy[5992]: 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 29 18:59:53 node-4 haproxy[5992]: 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 29 18:59:53 node-4 haproxy[5992]: Server horizon/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:53 node-4 haproxy[5992]: 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 29 18:59:54 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:54 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:54 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:54 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:54 node-4 multipathd: uevent trigger error
<129>Jul 29 18:59:54 node-4 haproxy[5992]: Server glance-registry/node-2 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:54 node-4 haproxy[5992]: 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 29 18:59:54 node-4 haproxy[5992]: proxy glance-registry has no server available!
<129>Jul 29 18:59:54 node-4 haproxy[5992]: Server aodh/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:55 node-4 haproxy[5992]: 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 29 18:59:55 node-4 haproxy[5992]: proxy aodh has no server available!
<129>Jul 29 18:59:55 node-4 haproxy[5992]: Server ceilometer/node-2 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:55 node-4 haproxy[5992]: 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 29 18:59:55 node-4 haproxy[5992]: proxy ceilometer has no server available!
<129>Jul 29 18:59:55 node-4 haproxy[5992]: Server nova-novncproxy/node-2 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 18:59:55 node-4 haproxy[5992]: 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 29 18:59:55 node-4 haproxy[5992]: proxy nova-novncproxy has no server available!
<27>Jul 29 18:59:57 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:57 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:57 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:57 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:57 node-4 multipathd: uevent trigger error
<27>Jul 29 18:59:57 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:00 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:00 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:00 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:00 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:00 node-4 multipathd: uevent trigger error
<129>Jul 29 19:00:01 node-4 haproxy[5992]: Server keystone-1/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:01 node-4 haproxy[5992]: 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 29 19:00:01 node-4 haproxy[5992]: proxy keystone-1 has no server available!
<129>Jul 29 19:00:01 node-4 haproxy[5992]: Server keystone-2/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:01 node-4 haproxy[5992]: Server keystone-2/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 19:00:01 node-4 haproxy[5992]: proxy keystone-2 has no server available!
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server nova-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server nova-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 19:00:02 node-4 haproxy[5992]: proxy nova-api has no server available!
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server nova-metadata-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server nova-metadata-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 29 19:00:02 node-4 haproxy[5992]: proxy nova-metadata-api has no server available!
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server cinder-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:02 node-4 haproxy[5992]: 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 29 19:00:02 node-4 haproxy[5992]: proxy cinder-api has no server available!
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server glance-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server glance-api/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 19:00:02 node-4 haproxy[5992]: proxy glance-api has no server available!
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server glance-glare/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:02 node-4 haproxy[5992]: 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 29 19:00:02 node-4 haproxy[5992]: proxy glance-glare has no server available!
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server neutron/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:02 node-4 haproxy[5992]: 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 29 19:00:02 node-4 haproxy[5992]: proxy neutron has no server available!
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server mysqld/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 1 backup servers left. Running on backup. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Backup Server mysqld/node-3 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Jul 29 19:00:02 node-4 haproxy[5992]: proxy mysqld has no server available!
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server object-storage/node-2 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:02 node-4 haproxy[5992]: Server object-storage/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 29 19:00:02 node-4 haproxy[5992]: proxy object-storage has no server available!
<129>Jul 29 19:00:03 node-4 haproxy[5992]: Server heat-api/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:03 node-4 haproxy[5992]: Server heat-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 29 19:00:03 node-4 haproxy[5992]: proxy heat-api has no server available!
<129>Jul 29 19:00:03 node-4 haproxy[5992]: Server heat-api-cfn/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:03 node-4 haproxy[5992]: 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 29 19:00:03 node-4 haproxy[5992]: proxy heat-api-cfn has no server available!
<129>Jul 29 19:00:03 node-4 haproxy[5992]: Server heat-api-cloudwatch/node-2 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Jul 29 19:00:03 node-4 haproxy[5992]: 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 29 19:00:03 node-4 haproxy[5992]: proxy heat-api-cloudwatch has no server available!
<27>Jul 29 19:00:04 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:04 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:04 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:04 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:24 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 19:00:28 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Jul 29 19:00:37 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Jul 29 19:00:37 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 19:00:37 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Jul 29 19:00:49 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:49 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:49 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:49 node-4 multipathd: uevent trigger error
<27>Jul 29 19:00:56 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Jul 29 19:01:25 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 29 19:01:27 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Jul 29 19:03:10 node-4 multipathd: uevent trigger error
<27>Jul 29 19:03:10 node-4 multipathd: uevent trigger error
<27>Jul 29 19:03:10 node-4 multipathd: uevent trigger error
<27>Jul 29 19:03:10 node-4 multipathd: uevent trigger error
<27>Jul 29 19:03:10 node-4 multipathd: uevent trigger error
<27>Jul 29 19:03:10 node-4 multipathd: uevent trigger error
<11>Jul 29 19:04:39 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 29 19:06:24 node-4 multipathd: uevent trigger error
<27>Jul 29 19:06:24 node-4 multipathd: uevent trigger error
<27>Jul 29 19:06:24 node-4 multipathd: uevent trigger error
<27>Jul 29 19:06:24 node-4 multipathd: uevent trigger error
<27>Jul 29 19:06:24 node-4 multipathd: uevent trigger error
<43>Jul 29 19:07:39 node-4 apache2_error [Fri Jul 29 19:07:32.864250 2016] [mpm_worker:notice] [pid 11979:tid 140597586827136] AH00295: caught SIGTERM, shutting down
<43>Jul 29 19:07:39 node-4 apache2_error [Fri Jul 29 19:07:33.610757 2016] [mpm_worker:notice] [pid 10562:tid 139854711142272] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 19:07:39 node-4 apache2_error [Fri Jul 29 19:07:33.610813 2016] [core:notice] [pid 10562:tid 139854711142272] AH00094: Command line: '/usr/sbin/apache2'
<43>Jul 29 19:08:09 node-4 apache2_error [Fri Jul 29 19:08:05.699118 2016] [mpm_worker:notice] [pid 10562:tid 139854711142272] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 19:08:09 node-4 apache2_error [Fri Jul 29 19:08:05.708924 2016] [mpm_worker:warn] [pid 10562:tid 139854711142272] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 19:08:09 node-4 apache2_error [Fri Jul 29 19:08:05.714521 2016] [mpm_worker:notice] [pid 10562:tid 139854711142272] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 19:08:09 node-4 apache2_error [Fri Jul 29 19:08:05.714560 2016] [core:notice] [pid 10562:tid 139854711142272] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 19:08:11 node-4 multipathd: uevent trigger error
<27>Jul 29 19:08:11 node-4 multipathd: uevent trigger error
<27>Jul 29 19:08:11 node-4 multipathd: uevent trigger error
<27>Jul 29 19:08:11 node-4 multipathd: uevent trigger error
<27>Jul 29 19:08:11 node-4 multipathd: uevent trigger error
<11>Jul 29 19:08:31 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<11>Jul 29 19:08:35 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 29 19:09:07 node-4 multipathd: uevent trigger error
<27>Jul 29 19:09:07 node-4 multipathd: uevent trigger error
<27>Jul 29 19:09:07 node-4 multipathd: uevent trigger error
<27>Jul 29 19:09:07 node-4 multipathd: uevent trigger error
<27>Jul 29 19:10:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:10:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:10:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:10:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:10:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:14:29 node-4 multipathd: uevent trigger error
<27>Jul 29 19:14:29 node-4 multipathd: uevent trigger error
<27>Jul 29 19:14:29 node-4 multipathd: uevent trigger error
<27>Jul 29 19:14:29 node-4 multipathd: uevent trigger error
<27>Jul 29 19:14:29 node-4 multipathd: uevent trigger error
<27>Jul 29 19:16:35 node-4 multipathd: uevent trigger error
<27>Jul 29 19:16:35 node-4 multipathd: uevent trigger error
<27>Jul 29 19:16:35 node-4 multipathd: uevent trigger error
<27>Jul 29 19:16:35 node-4 multipathd: uevent trigger error
<27>Jul 29 19:16:35 node-4 multipathd: uevent trigger error
<27>Jul 29 19:16:35 node-4 multipathd: uevent trigger error
<27>Jul 29 19:17:44 node-4 multipathd: uevent trigger error
<27>Jul 29 19:17:44 node-4 multipathd: uevent trigger error
<27>Jul 29 19:17:44 node-4 multipathd: uevent trigger error
<27>Jul 29 19:17:44 node-4 multipathd: uevent trigger error
<27>Jul 29 19:17:44 node-4 multipathd: uevent trigger error
<27>Jul 29 19:17:44 node-4 multipathd: uevent trigger error
<27>Jul 29 19:17:44 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:22 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:31 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:31 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:31 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:31 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:36 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:36 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:36 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:36 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:36 node-4 multipathd: uevent trigger error
<27>Jul 29 19:18:36 node-4 multipathd: uevent trigger error
<43>Jul 29 19:19:30 node-4 apache2_error [Fri Jul 29 19:19:27.900889 2016] [mpm_worker:notice] [pid 10562:tid 139854711142272] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 19:19:30 node-4 apache2_error [Fri Jul 29 19:19:28.284497 2016] [mpm_worker:warn] [pid 10562:tid 139854711142272] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 19:19:30 node-4 apache2_error [Fri Jul 29 19:19:28.289632 2016] [mpm_worker:notice] [pid 10562:tid 139854711142272] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 19:19:30 node-4 apache2_error [Fri Jul 29 19:19:28.289654 2016] [core:notice] [pid 10562:tid 139854711142272] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 19:20:09 node-4 multipathd: uevent trigger error
<27>Jul 29 19:20:09 node-4 multipathd: uevent trigger error
<27>Jul 29 19:20:09 node-4 multipathd: uevent trigger error
<27>Jul 29 19:20:09 node-4 multipathd: uevent trigger error
<27>Jul 29 19:20:09 node-4 multipathd: uevent trigger error
<43>Jul 29 19:20:10 node-4 apache2_error [Fri Jul 29 19:20:05.254566 2016] [mpm_worker:notice] [pid 10562:tid 139854711142272] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Jul 29 19:20:10 node-4 apache2_error [Fri Jul 29 19:20:05.641651 2016] [mpm_worker:warn] [pid 10562:tid 139854711142272] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Jul 29 19:20:10 node-4 apache2_error [Fri Jul 29 19:20:05.653449 2016] [mpm_worker:notice] [pid 10562:tid 139854711142272] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Jul 29 19:20:10 node-4 apache2_error [Fri Jul 29 19:20:05.653491 2016] [core:notice] [pid 10562:tid 139854711142272] AH00094: Command line: '/usr/sbin/apache2'
<27>Jul 29 19:20:26 node-4 multipathd: uevent trigger error
<27>Jul 29 19:20:26 node-4 multipathd: uevent trigger error
<27>Jul 29 19:20:26 node-4 multipathd: uevent trigger error
<27>Jul 29 19:20:26 node-4 multipathd: uevent trigger error
<27>Jul 29 19:20:26 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:09 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:09 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:09 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:09 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:09 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:14 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:14 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:14 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:14 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:14 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:23 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:23 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:23 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:23 node-4 multipathd: uevent trigger error
<27>Jul 29 19:21:23 node-4 multipathd: uevent trigger error
<11>Jul 29 19:21:47 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<11>Jul 29 19:22:34 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 29 19:22:59 node-4 multipathd: uevent trigger error
<27>Jul 29 19:22:59 node-4 multipathd: uevent trigger error
<27>Jul 29 19:22:59 node-4 multipathd: uevent trigger error
<27>Jul 29 19:22:59 node-4 multipathd: uevent trigger error
<27>Jul 29 19:22:59 node-4 multipathd: uevent trigger error
<11>Jul 29 19:23:10 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 29 19:23:48 node-4 multipathd: uevent trigger error
<27>Jul 29 19:23:48 node-4 multipathd: uevent trigger error
<27>Jul 29 19:23:48 node-4 multipathd: uevent trigger error
<27>Jul 29 19:23:48 node-4 multipathd: uevent trigger error
<27>Jul 29 19:23:48 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:02 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:02 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:02 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:02 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:02 node-4 multipathd: uevent trigger error
<11>Jul 29 19:24:12 node-4 liberasurecode[8514]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:12 node-4 liberasurecode[8514]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:12 node-4 liberasurecode[8514]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:12 node-4 liberasurecode[8514]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:12 node-4 liberasurecode[8541]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:12 node-4 liberasurecode[8541]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:12 node-4 liberasurecode[8541]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:12 node-4 liberasurecode[8541]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:14 node-4 liberasurecode[8956]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:14 node-4 liberasurecode[8956]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:14 node-4 liberasurecode[8956]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:14 node-4 liberasurecode[8956]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9820]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9820]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9820]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9820]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9865]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9865]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9865]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9865]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9904]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9904]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9904]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:20 node-4 liberasurecode[9904]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[9975]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[9975]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[9975]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[9975]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[9987]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[9987]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[9987]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[9987]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[10000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[10000]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[10000]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[10000]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[10022]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[10022]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[10022]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:21 node-4 liberasurecode[10022]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:23 node-4 liberasurecode[10305]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:23 node-4 liberasurecode[10305]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:23 node-4 liberasurecode[10305]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:23 node-4 liberasurecode[10305]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:24:24 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 29 19:24:29 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:29 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:29 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:29 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:29 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:34 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:34 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:34 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:34 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:34 node-4 multipathd: uevent trigger error
<27>Jul 29 19:24:34 node-4 multipathd: uevent trigger error
<11>Jul 29 19:25:01 node-4 liberasurecode[17411]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:25:01 node-4 liberasurecode[17411]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:25:01 node-4 liberasurecode[17411]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:25:01 node-4 liberasurecode[17411]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Jul 29 19:25:05 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 29 19:25:39 node-4 multipathd: uevent trigger error
<27>Jul 29 19:25:39 node-4 multipathd: uevent trigger error
<27>Jul 29 19:25:39 node-4 multipathd: uevent trigger error
<27>Jul 29 19:25:39 node-4 multipathd: uevent trigger error
<27>Jul 29 19:25:39 node-4 multipathd: uevent trigger error
<11>Jul 29 19:26:33 node-4 epmd: epmd: node name already occupied rabbitmq-cli-46
<27>Jul 29 19:27:48 node-4 multipathd: uevent trigger error
<27>Jul 29 19:27:48 node-4 multipathd: uevent trigger error
<27>Jul 29 19:27:48 node-4 multipathd: uevent trigger error
<27>Jul 29 19:27:48 node-4 multipathd: uevent trigger error
<27>Jul 29 19:27:48 node-4 multipathd: uevent trigger error
<27>Jul 29 19:27:53 node-4 multipathd: uevent trigger error
<27>Jul 29 19:27:53 node-4 multipathd: uevent trigger error
<27>Jul 29 19:27:53 node-4 multipathd: uevent trigger error
<27>Jul 29 19:27:53 node-4 multipathd: uevent trigger error
<27>Jul 29 19:27:53 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:06 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:06 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:06 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:06 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:06 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:19 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:19 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:19 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:19 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:23 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:23 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:23 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:23 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:23 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:36 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:36 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:36 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:36 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:36 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:40 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:40 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:40 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:40 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:45 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:45 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:45 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:45 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:45 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:53 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:53 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:53 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:53 node-4 multipathd: uevent trigger error
<129>Jul 29 19:28:54 node-4 haproxy[5992]: Server neutron/node-4 is DOWN, reason: Layer4 connection problem, info: "Connection refused", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Jul 29 19:28:57 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:57 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:57 node-4 multipathd: uevent trigger error
<27>Jul 29 19:28:57 node-4 multipathd: uevent trigger error
<11>Jul 29 19:30:01 node-4 liberasurecode[5699]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:30:01 node-4 liberasurecode[5699]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:30:01 node-4 liberasurecode[5699]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Jul 29 19:30:01 node-4 liberasurecode[5699]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
