Sep 13 18:09:41 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8384" x-info="http://www.rsyslog.com"] start
Sep 13 18:09:41 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
Sep 13 18:09:41 node-4 rsyslogd: rsyslogd's groupid changed to 104
Sep 13 18:09:41 node-4 rsyslogd: rsyslogd's userid changed to 101
Sep 13 18:09:41 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuset
Sep 13 18:09:41 node-4 kernel: [    0.000000] Initializing cgroup subsys cpu
Sep 13 18:09:41 node-4 kernel: [    0.000000] Initializing cgroup subsys cpuacct
Sep 13 18:09:41 node-4 kernel: [    0.000000] Linux version 3.13.0-95-generic (buildd@lgw01-58) (gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ) #142-Ubuntu SMP Fri Aug 12 17:00:09 UTC 2016 (Ubuntu 3.13.0-95.142-generic 3.13.11-ckt39)
Sep 13 18:09:41 node-4 kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=10c5969a-0bee-4214-8b38-01b49ebc4211 nomdmonddf nomdmonisw
Sep 13 18:09:41 node-4 kernel: [    0.000000] KERNEL supported cpus:
Sep 13 18:09:41 node-4 kernel: [    0.000000]   Intel GenuineIntel
Sep 13 18:09:41 node-4 kernel: [    0.000000]   AMD AuthenticAMD
Sep 13 18:09:41 node-4 kernel: [    0.000000]   Centaur CentaurHauls
Sep 13 18:09:41 node-4 kernel: [    0.000000] e820: BIOS-provided physical RAM map:
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000006f2dffff] usable
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f2e0000-0x000000006f8dafff] reserved
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f8db000-0x000000006f927fff] ACPI data
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006f928000-0x000000006fee6fff] ACPI NVS
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000006fee7000-0x000000007bd57fff] reserved
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd58000-0x000000007bd58fff] usable
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bd59000-0x000000007bddefff] reserved
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x000000007bddf000-0x000000007bffffff] usable
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000080000000-0x000000008fffffff] reserved
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 13 18:09:41 node-4 kernel: [    0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000087fffffff] usable
Sep 13 18:09:41 node-4 kernel: [    0.000000] NX (Execute Disable) protection: active
Sep 13 18:09:41 node-4 kernel: [    0.000000] SMBIOS 2.8 present.
Sep 13 18:09:41 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
Sep 13 18:09:41 node-4 kernel: [    0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Sep 13 18:09:41 node-4 kernel: [    0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
Sep 13 18:09:41 node-4 kernel: [    0.000000] No AGP bridge found
Sep 13 18:09:41 node-4 kernel: [    0.000000] e820: last_pfn = 0x880000 max_arch_pfn = 0x400000000
Sep 13 18:09:41 node-4 kernel: [    0.000000] MTRR default type: write-back
Sep 13 18:09:41 node-4 kernel: [    0.000000] MTRR fixed ranges enabled:
Sep 13 18:09:41 node-4 kernel: [    0.000000]   00000-9FFFF write-back
Sep 13 18:09:41 node-4 kernel: [    0.000000]   A0000-BFFFF uncachable
Sep 13 18:09:41 node-4 kernel: [    0.000000]   C0000-FFFFF write-protect
Sep 13 18:09:41 node-4 kernel: [    0.000000] MTRR variable ranges enabled:
Sep 13 18:09:41 node-4 kernel: [    0.000000]   0 base 000080000000 mask 3FFF80000000 uncachable
Sep 13 18:09:41 node-4 kernel: [    0.000000]   1 base 038000000000 mask 3F8000000000 uncachable
Sep 13 18:09:41 node-4 kernel: [    0.000000]   2 disabled
Sep 13 18:09:41 node-4 kernel: [    0.000000]   3 disabled
Sep 13 18:09:41 node-4 kernel: [    0.000000]   4 disabled
Sep 13 18:09:41 node-4 kernel: [    0.000000]   5 disabled
Sep 13 18:09:41 node-4 kernel: [    0.000000]   6 disabled
Sep 13 18:09:41 node-4 kernel: [    0.000000]   7 disabled
Sep 13 18:09:41 node-4 kernel: [    0.000000]   8 disabled
Sep 13 18:09:41 node-4 kernel: [    0.000000]   9 disabled
Sep 13 18:09:41 node-4 kernel: [    0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
Sep 13 18:09:41 node-4 kernel: [    0.000000] e820: last_pfn = 0x7c000 max_arch_pfn = 0x400000000
Sep 13 18:09:41 node-4 kernel: [    0.000000] found SMP MP-table at [mem 0x000fd920-0x000fd92f] mapped at [ffff8800000fd920]
Sep 13 18:09:41 node-4 kernel: [    0.000000] Scanning 1 areas for low memory corruption
Sep 13 18:09:41 node-4 kernel: [    0.000000] Base memory trampoline at [ffff880000098000] 98000 size 24576
Sep 13 18:09:41 node-4 kernel: [    0.000000] Using GB pages for direct mapping
Sep 13 18:09:41 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x00000000-0x000fffff] page 4k
Sep 13 18:09:41 node-4 kernel: [    0.000000] BRK [0x01fe2000, 0x01fe2fff] PGTABLE
Sep 13 18:09:41 node-4 kernel: [    0.000000] BRK [0x01fe3000, 0x01fe3fff] PGTABLE
Sep 13 18:09:41 node-4 kernel: [    0.000000] BRK [0x01fe4000, 0x01fe4fff] PGTABLE
Sep 13 18:09:41 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87fe00000-0x87fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x87fe00000-0x87fffffff] page 1G
Sep 13 18:09:41 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x87c000000-0x87fdfffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x87c000000-0x87fdfffff] page 1G
Sep 13 18:09:41 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x800000000-0x87bffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x800000000-0x87bffffff] page 1G
Sep 13 18:09:41 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x00100000-0x6f2dffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x00100000-0x001fffff] page 4k
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x00200000-0x6f1fffff] page 2M
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x6f200000-0x6f2dffff] page 4k
Sep 13 18:09:41 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bd58000-0x7bd58fff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x7bd58000-0x7bd58fff] page 4k
Sep 13 18:09:41 node-4 kernel: [    0.000000] BRK [0x01fe5000, 0x01fe5fff] PGTABLE
Sep 13 18:09:41 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x7bddf000-0x7bffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x7bddf000-0x7bdfffff] page 4k
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x7be00000-0x7bffffff] page 2M
Sep 13 18:09:41 node-4 kernel: [    0.000000] init_memory_mapping: [mem 0x100000000-0x7ffffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [mem 0x100000000-0x7ffffffff] page 1G
Sep 13 18:09:41 node-4 kernel: [    0.000000] RAMDISK: [mem 0x35822000-0x36c08fff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: RSDP 00000000000f0530 000024 (v02  Cisco)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: XSDT 000000006f8ea0b0 0000DC (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: FACP 000000006f9154c8 00010C (v05  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: DSDT 000000006f8ea218 02B2AF (v02  Cisco CiscoUCS 01072009 INTL 20091013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: FACS 000000006fee4f80 000040
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: APIC 000000006f9155d8 000144 (v03  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: FPDT 000000006f915720 000044 (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: FIDT 000000006f915768 00009C (v01  Cisco CiscoUCS 01072009 AMI  00010013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: SPMI 000000006f915808 000040 (v05  Cisco CiscoUCS 00000000 AMI. 00000000)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: MCFG 000000006f915848 00003C (v01  Cisco CiscoUCS 01072009 MSFT 00000097)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: UEFI 000000006f915888 000042 (v01  Cisco CiscoUCS 00000000      00000000)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: BDAT 000000006f9158d0 000030 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: HPET 000000006f915900 000038 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: MSCT 000000006f915938 000090 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: PMCT 000000006f9159c8 000064 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: SLIT 000000006f915a30 000030 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: SRAT 000000006f915a60 000E58 (v03  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: WDDT 000000006f9168b8 000040 (v01  Cisco CiscoUCS 00000000 INTL 20091013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9168f8 00EDA9 (v01  Cisco    PmMgt 00000001 INTL 20120913)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f9256a8 001D72 (v02  Cisco SpsNm    00000002 INTL 20120913)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: SSDT 000000006f927420 000064 (v02  Cisco SpsNvs   00000002 INTL 20120913)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: PRAD 000000006f927488 000102 (v02  Cisco CiscoUCS 00000002 INTL 20120913)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: DMAR 000000006f927590 000102 (v01  Cisco CiscoUCS 00000001 INTL 20091013)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: HEST 000000006f927698 0000A8 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: BERT 000000006f927740 000030 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: ERST 000000006f927770 000230 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: EINJ 000000006f9279a0 000130 (v01  Cisco CiscoUCS 00000001 INTL 00000001)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x00 -> Node 0
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x02 -> Node 0
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x08 -> Node 0
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0a -> Node 0
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x10 -> Node 1
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x12 -> Node 1
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x18 -> Node 1
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1a -> Node 1
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x01 -> Node 0
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x03 -> Node 0
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x09 -> Node 0
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 0 -> APIC 0x0b -> Node 0
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x11 -> Node 1
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x13 -> Node 1
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x19 -> Node 1
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: PXM 1 -> APIC 0x1b -> Node 1
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x00000000-0x7fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: Node 0 PXM 0 [mem 0x100000000-0x47fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] SRAT: Node 1 PXM 1 [mem 0x480000000-0x87fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] NUMA: Initialized distance table, cnt=2
Sep 13 18:09:41 node-4 kernel: [    0.000000] NUMA: Node 0 [mem 0x00000000-0x7fffffff] + [mem 0x100000000-0x47fffffff] -> [mem 0x00000000-0x47fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] Initmem setup node 0 [mem 0x00000000-0x47fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x47fffb000-0x47fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] Initmem setup node 1 [mem 0x480000000-0x87fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]   NODE_DATA [mem 0x87fff8000-0x87fffcfff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [ffffea0000000000-ffffea0011ffffff] PMD -> [ffff880470000000-ffff88047fdfffff] on node 0
Sep 13 18:09:41 node-4 kernel: [    0.000000]  [ffffea0012000000-ffffea0021ffffff] PMD -> [ffff88086f600000-ffff88087f5fffff] on node 1
Sep 13 18:09:41 node-4 kernel: [    0.000000] Zone ranges:
Sep 13 18:09:41 node-4 kernel: [    0.000000]   DMA      [mem 0x00001000-0x00ffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]   DMA32    [mem 0x01000000-0xffffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]   Normal   [mem 0x100000000-0x87fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] Movable zone start for each node
Sep 13 18:09:41 node-4 kernel: [    0.000000] Early memory node ranges
Sep 13 18:09:41 node-4 kernel: [    0.000000]   node   0: [mem 0x00001000-0x0009dfff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]   node   0: [mem 0x00100000-0x6f2dffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]   node   0: [mem 0x7bd58000-0x7bd58fff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]   node   0: [mem 0x7bddf000-0x7bffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]   node   0: [mem 0x100000000-0x47fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000]   node   1: [mem 0x480000000-0x87fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] On node 0 totalpages: 4125855
Sep 13 18:09:41 node-4 kernel: [    0.000000]   DMA zone: 64 pages used for memmap
Sep 13 18:09:41 node-4 kernel: [    0.000000]   DMA zone: 21 pages reserved
Sep 13 18:09:41 node-4 kernel: [    0.000000]   DMA zone: 3997 pages, LIFO batch:0
Sep 13 18:09:41 node-4 kernel: [    0.000000]   DMA32 zone: 7061 pages used for memmap
Sep 13 18:09:41 node-4 kernel: [    0.000000]   DMA32 zone: 451842 pages, LIFO batch:31
Sep 13 18:09:41 node-4 kernel: [    0.000000]   Normal zone: 57344 pages used for memmap
Sep 13 18:09:41 node-4 kernel: [    0.000000]   Normal zone: 3670016 pages, LIFO batch:31
Sep 13 18:09:41 node-4 kernel: [    0.000000] On node 1 totalpages: 4194304
Sep 13 18:09:41 node-4 kernel: [    0.000000]   Normal zone: 65536 pages used for memmap
Sep 13 18:09:41 node-4 kernel: [    0.000000]   Normal zone: 4194304 pages, LIFO batch:31
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: PM-Timer IO Port: 0x408
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: Local APIC address 0xfee00000
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x08] lapic_id[0x08] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0a] lapic_id[0x0a] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x10] lapic_id[0x10] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x12] lapic_id[0x12] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x18] lapic_id[0x18] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1a] lapic_id[0x1a] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x03] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x09] lapic_id[0x09] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x0b] lapic_id[0x0b] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x11] lapic_id[0x11] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x13] lapic_id[0x13] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x19] lapic_id[0x19] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC (acpi_id[0x1b] lapic_id[0x1b] enabled)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x08] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0a] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x10] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x12] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x18] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1a] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x03] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x09] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x0b] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x11] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x13] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x19] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: LAPIC_NMI (acpi_id[0x1b] high edge lint[0x1])
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
Sep 13 18:09:41 node-4 kernel: [    0.000000] IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x09] address[0xfec01000] gsi_base[24])
Sep 13 18:09:41 node-4 kernel: [    0.000000] IOAPIC[1]: apic_id 9, version 32, address 0xfec01000, GSI 24-47
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: IOAPIC (id[0x0a] address[0xfec40000] gsi_base[48])
Sep 13 18:09:41 node-4 kernel: [    0.000000] IOAPIC[2]: apic_id 10, version 32, address 0xfec40000, GSI 48-71
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: IRQ0 used by override.
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: IRQ2 used by override.
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: IRQ9 used by override.
Sep 13 18:09:41 node-4 kernel: [    0.000000] Using ACPI (MADT) for SMP configuration information
Sep 13 18:09:41 node-4 kernel: [    0.000000] ACPI: HPET id: 0x8086a701 base: 0xfed00000
Sep 13 18:09:41 node-4 kernel: [    0.000000] smpboot: Allowing 16 CPUs, 0 hotplug CPUs
Sep 13 18:09:41 node-4 kernel: [    0.000000] nr_irqs_gsi: 88
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009e000-0x0009efff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000a0000-0x000dffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x000e0000-0x000fffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f2e0000-0x6f8dafff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f8db000-0x6f927fff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6f928000-0x6fee6fff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x6fee7000-0x7bd57fff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7bd59000-0x7bddefff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x7c000000-0x7fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x80000000-0x8fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0x90000000-0xfed1bfff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed1c000-0xfed1ffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xfed20000-0xfeffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] PM: Registered nosave memory: [mem 0xff000000-0xffffffff]
Sep 13 18:09:41 node-4 kernel: [    0.000000] e820: [mem 0x90000000-0xfed1bfff] available for PCI devices
Sep 13 18:09:41 node-4 kernel: [    0.000000] Booting paravirtualized kernel on bare hardware
Sep 13 18:09:41 node-4 kernel: [    0.000000] setup_percpu: NR_CPUS:256 nr_cpumask_bits:256 nr_cpu_ids:16 nr_node_ids:2
Sep 13 18:09:41 node-4 kernel: [    0.000000] PERCPU: Embedded 27 pages/cpu @ffff88046fe00000 s81536 r8192 d20864 u262144
Sep 13 18:09:41 node-4 kernel: [    0.000000] pcpu-alloc: s81536 r8192 d20864 u262144 alloc=1*2097152
Sep 13 18:09:41 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 
Sep 13 18:09:41 node-4 kernel: [    0.000000] Built 2 zonelists in Zone order, mobility grouping on.  Total pages: 8190133
Sep 13 18:09:41 node-4 kernel: [    0.000000] Policy zone: Normal
Sep 13 18:09:41 node-4 kernel: [    0.000000] Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.0-95-generic root=/dev/mapper/os-root ro console=tty0 net.ifnames=0 biosdevname=0 rootdelay=90 nomodeset root=UUID=10c5969a-0bee-4214-8b38-01b49ebc4211 nomdmonddf nomdmonisw
Sep 13 18:09:41 node-4 kernel: [    0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.000000] xsave: enabled xstate_bv 0x7, cntxt size 0x340
Sep 13 18:09:41 node-4 kernel: [    0.000000] Checking aperture...
Sep 13 18:09:41 node-4 kernel: [    0.000000] No AGP bridge found
Sep 13 18:09:41 node-4 kernel: [    0.000000] Calgary: detecting Calgary via BIOS EBDA area
Sep 13 18:09:41 node-4 kernel: [    0.000000] Calgary: Unable to locate Rio Grande table in EBDA - bailing!
Sep 13 18:09:41 node-4 kernel: [    0.000000] Memory: 32653456K/33280636K available (7419K kernel code, 1146K rwdata, 3416K rodata, 1336K init, 1448K bss, 627180K reserved)
Sep 13 18:09:41 node-4 kernel: [    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=16, Nodes=2
Sep 13 18:09:41 node-4 kernel: [    0.000000] Hierarchical RCU implementation.
Sep 13 18:09:41 node-4 kernel: [    0.000000] 	RCU dyntick-idle grace-period acceleration is enabled.
Sep 13 18:09:41 node-4 kernel: [    0.000000] 	RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=16.
Sep 13 18:09:41 node-4 kernel: [    0.000000] 	Offload RCU callbacks from all CPUs
Sep 13 18:09:41 node-4 kernel: [    0.000000] 	Offload RCU callbacks from CPUs: 0-15.
Sep 13 18:09:41 node-4 kernel: [    0.000000] NR_IRQS:16640 nr_irqs:1624 16
Sep 13 18:09:41 node-4 kernel: [    0.000000] Console: colour dummy device 80x25
Sep 13 18:09:41 node-4 kernel: [    0.000000] console [tty0] enabled
Sep 13 18:09:41 node-4 kernel: [    0.000000] allocated 133693440 bytes of page_cgroup
Sep 13 18:09:41 node-4 kernel: [    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
Sep 13 18:09:41 node-4 kernel: [    0.000000] Enabling automatic NUMA balancing. Configure with numa_balancing= or the kernel.numa_balancing sysctl
Sep 13 18:09:41 node-4 kernel: [    0.000000] hpet clockevent registered
Sep 13 18:09:41 node-4 kernel: [    0.000000] tsc: Fast TSC calibration using PIT
Sep 13 18:09:41 node-4 kernel: [    0.004000] tsc: Detected 3492.118 MHz processor
Sep 13 18:09:41 node-4 kernel: [    0.000005] Calibrating delay loop (skipped), value calculated using timer frequency.. 6984.23 BogoMIPS (lpj=13968472)
Sep 13 18:09:41 node-4 kernel: [    0.000008] pid_max: default: 32768 minimum: 301
Sep 13 18:09:41 node-4 kernel: [    0.000042] Security Framework initialized
Sep 13 18:09:41 node-4 kernel: [    0.000061] AppArmor: AppArmor initialized
Sep 13 18:09:41 node-4 kernel: [    0.000062] Yama: becoming mindful.
Sep 13 18:09:41 node-4 kernel: [    0.001451] Dentry cache hash table entries: 4194304 (order: 13, 33554432 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.006263] Inode-cache hash table entries: 2097152 (order: 12, 16777216 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.008190] Mount-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.008218] Mountpoint-cache hash table entries: 65536 (order: 7, 524288 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.008509] Initializing cgroup subsys memory
Sep 13 18:09:41 node-4 kernel: [    0.008518] Initializing cgroup subsys devices
Sep 13 18:09:41 node-4 kernel: [    0.008519] Initializing cgroup subsys freezer
Sep 13 18:09:41 node-4 kernel: [    0.008521] Initializing cgroup subsys blkio
Sep 13 18:09:41 node-4 kernel: [    0.008523] Initializing cgroup subsys perf_event
Sep 13 18:09:41 node-4 kernel: [    0.008525] Initializing cgroup subsys hugetlb
Sep 13 18:09:41 node-4 kernel: [    0.008544] CPU: Physical Processor ID: 0
Sep 13 18:09:41 node-4 kernel: [    0.008546] CPU: Processor Core ID: 0
Sep 13 18:09:41 node-4 kernel: [    0.008549] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Sep 13 18:09:41 node-4 kernel: [    0.008549] ENERGY_PERF_BIAS: View and update with x86_energy_perf_policy(8)
Sep 13 18:09:41 node-4 kernel: [    0.009243] mce: CPU supports 22 MCE banks
Sep 13 18:09:41 node-4 kernel: [    0.009270] CPU0: Thermal monitoring enabled (TM1)
Sep 13 18:09:41 node-4 kernel: [    0.009291] process: using mwait in idle threads
Sep 13 18:09:41 node-4 kernel: [    0.009294] Last level iTLB entries: 4KB 0, 2MB 0, 4MB 0
Sep 13 18:09:41 node-4 kernel: [    0.009294] Last level dTLB entries: 4KB 64, 2MB 0, 4MB 0
Sep 13 18:09:41 node-4 kernel: [    0.009294] tlb_flushall_shift: 6
Sep 13 18:09:41 node-4 kernel: [    0.009383] Freeing SMP alternatives memory: 32K (ffffffff81e6e000 - ffffffff81e76000)
Sep 13 18:09:41 node-4 kernel: [    0.010109] ACPI: Core revision 20131115
Sep 13 18:09:41 node-4 kernel: [    0.022797] ACPI: All ACPI Tables successfully acquired
Sep 13 18:09:41 node-4 kernel: [    0.022959] ftrace: allocating 28617 entries in 112 pages
Sep 13 18:09:41 node-4 kernel: [    0.031913] dmar: Host address width 46
Sep 13 18:09:41 node-4 kernel: [    0.031915] dmar: DRHD base: 0x000000fbffc000 flags: 0x0
Sep 13 18:09:41 node-4 kernel: [    0.031921] dmar: IOMMU 0: reg_base_addr fbffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 13 18:09:41 node-4 kernel: [    0.031923] dmar: DRHD base: 0x000000c7ffc000 flags: 0x1
Sep 13 18:09:41 node-4 kernel: [    0.031927] dmar: IOMMU 1: reg_base_addr c7ffc000 ver 1:0 cap d2078c106f0466 ecap f020de
Sep 13 18:09:41 node-4 kernel: [    0.031928] dmar: RMRR base: 0x0000007bbca000 end: 0x0000007bbd8fff
Sep 13 18:09:41 node-4 kernel: [    0.031929] dmar: RMRR base: 0x0000007262f000 end: 0x0000007a636fff
Sep 13 18:09:41 node-4 kernel: [    0.031930] dmar: ATSR flags: 0x0
Sep 13 18:09:41 node-4 kernel: [    0.031931] dmar: RHSA base: 0x000000c7ffc000 proximity domain: 0x0
Sep 13 18:09:41 node-4 kernel: [    0.031933] dmar: RHSA base: 0x000000fbffc000 proximity domain: 0x1
Sep 13 18:09:41 node-4 kernel: [    0.032048] IOAPIC id 10 under DRHD base  0xfbffc000 IOMMU 0
Sep 13 18:09:41 node-4 kernel: [    0.032049] IOAPIC id 8 under DRHD base  0xc7ffc000 IOMMU 1
Sep 13 18:09:41 node-4 kernel: [    0.032050] IOAPIC id 9 under DRHD base  0xc7ffc000 IOMMU 1
Sep 13 18:09:41 node-4 kernel: [    0.032051] HPET id 0 under DRHD base 0xc7ffc000
Sep 13 18:09:41 node-4 kernel: [    0.032053] Your BIOS is broken and requested that x2apic be disabled.
Sep 13 18:09:41 node-4 kernel: [    0.032053] This will slightly decrease performance.
Sep 13 18:09:41 node-4 kernel: [    0.032053] Use 'intremap=no_x2apic_optout' to override BIOS request.
Sep 13 18:09:41 node-4 kernel: [    0.032485] Enabled IRQ remapping in xapic mode
Sep 13 18:09:41 node-4 kernel: [    0.032486] x2apic not enabled, IRQ remapping is in xapic mode
Sep 13 18:09:41 node-4 kernel: [    0.032490] Switched APIC routing to physical flat.
Sep 13 18:09:41 node-4 kernel: [    0.033076] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Sep 13 18:09:41 node-4 kernel: [    0.072728] smpboot: CPU0: Intel(R) Xeon(R) CPU E5-2637 v3 @ 3.50GHz (fam: 06, model: 3f, stepping: 02)
Sep 13 18:09:41 node-4 kernel: [    0.072734] TSC deadline timer enabled
Sep 13 18:09:41 node-4 kernel: [    0.072741] Performance Events: PEBS fmt2+, 16-deep LBR, Haswell events, full-width counters, Intel PMU driver.
Sep 13 18:09:41 node-4 kernel: [    0.072747] ... version:                3
Sep 13 18:09:41 node-4 kernel: [    0.072748] ... bit width:              48
Sep 13 18:09:41 node-4 kernel: [    0.072749] ... generic registers:      4
Sep 13 18:09:41 node-4 kernel: [    0.072750] ... value mask:             0000ffffffffffff
Sep 13 18:09:41 node-4 kernel: [    0.072751] ... max period:             0000ffffffffffff
Sep 13 18:09:41 node-4 kernel: [    0.072752] ... fixed-purpose events:   3
Sep 13 18:09:41 node-4 kernel: [    0.072753] ... event mask:             000000070000000f
Sep 13 18:09:41 node-4 kernel: [    0.074132] x86: Booting SMP configuration:
Sep 13 18:09:41 node-4 kernel: [    0.088237] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
Sep 13 18:09:41 node-4 kernel: [    0.074134] .... node  #0, CPUs:        #1  #2  #3
Sep 13 18:09:41 node-4 kernel: [    0.116147] .... node  #1, CPUs:    #4  #5  #6  #7
Sep 13 18:09:41 node-4 kernel: [    0.270091] .... node  #0, CPUs:    #8  #9 #10 #11
Sep 13 18:09:41 node-4 kernel: [    0.325713] .... node  #1, CPUs:   #12 #13 #14 #15
Sep 13 18:09:41 node-4 kernel: [    0.382362] x86: Booted up 2 nodes, 16 CPUs
Sep 13 18:09:41 node-4 kernel: [    0.382366] smpboot: Total of 16 processors activated (111759.84 BogoMIPS)
Sep 13 18:09:41 node-4 kernel: [    0.405909] devtmpfs: initialized
Sep 13 18:09:41 node-4 kernel: [    0.409029] EVM: security.selinux
Sep 13 18:09:41 node-4 kernel: [    0.409031] EVM: security.SMACK64
Sep 13 18:09:41 node-4 kernel: [    0.409032] EVM: security.ima
Sep 13 18:09:41 node-4 kernel: [    0.409032] EVM: security.capability
Sep 13 18:09:41 node-4 kernel: [    0.409082] PM: Registering ACPI NVS region [mem 0x6f928000-0x6fee6fff] (6025216 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.409772] pinctrl core: initialized pinctrl subsystem
Sep 13 18:09:41 node-4 kernel: [    0.409834] regulator-dummy: no parameters
Sep 13 18:09:41 node-4 kernel: [    0.409866] RTC time: 18:09:05, date: 09/13/16
Sep 13 18:09:41 node-4 kernel: [    0.409900] NET: Registered protocol family 16
Sep 13 18:09:41 node-4 kernel: [    0.409984] cpuidle: using governor ladder
Sep 13 18:09:41 node-4 kernel: [    0.409985] cpuidle: using governor menu
Sep 13 18:09:41 node-4 kernel: [    0.410022] ACPI: bus type PCI registered
Sep 13 18:09:41 node-4 kernel: [    0.410024] acpiphp: ACPI Hot Plug PCI Controller Driver version: 0.5
Sep 13 18:09:41 node-4 kernel: [    0.410070] PCI: MMCONFIG for domain 0000 [bus 00-ff] at [mem 0x80000000-0x8fffffff] (base 0x80000000)
Sep 13 18:09:41 node-4 kernel: [    0.410072] PCI: MMCONFIG at [mem 0x80000000-0x8fffffff] reserved in E820
Sep 13 18:09:41 node-4 kernel: [    0.423802] PCI: Using configuration type 1 for base access
Sep 13 18:09:41 node-4 kernel: [    0.424800] bio: create slab <bio-0> at 0
Sep 13 18:09:41 node-4 kernel: [    0.425077] ACPI: Added _OSI(Module Device)
Sep 13 18:09:41 node-4 kernel: [    0.425079] ACPI: Added _OSI(Processor Device)
Sep 13 18:09:41 node-4 kernel: [    0.425080] ACPI: Added _OSI(3.0 _SCP Extensions)
Sep 13 18:09:41 node-4 kernel: [    0.425081] ACPI: Added _OSI(Processor Aggregator Device)
Sep 13 18:09:41 node-4 kernel: [    0.437681] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
Sep 13 18:09:41 node-4 kernel: [    0.448346] ACPI: Interpreter enabled
Sep 13 18:09:41 node-4 kernel: [    0.448351] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S1_] (20131115/hwxface-580)
Sep 13 18:09:41 node-4 kernel: [    0.448355] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S2_] (20131115/hwxface-580)
Sep 13 18:09:41 node-4 kernel: [    0.448358] ACPI Exception: AE_NOT_FOUND, While evaluating Sleep State [\_S3_] (20131115/hwxface-580)
Sep 13 18:09:41 node-4 kernel: [    0.448365] ACPI: (supports S0 S4 S5)
Sep 13 18:09:41 node-4 kernel: [    0.448366] ACPI: Using IOAPIC for interrupt routing
Sep 13 18:09:41 node-4 kernel: [    0.448411] HEST: Table parsing has been initialized.
Sep 13 18:09:41 node-4 kernel: [    0.448414] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
Sep 13 18:09:41 node-4 kernel: [    0.448969] ACPI: No dock devices found.
Sep 13 18:09:41 node-4 kernel: [    0.460663] ACPI: PCI Root Bridge [UNC1] (domain 0000 [bus ff])
Sep 13 18:09:41 node-4 kernel: [    0.460668] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 18:09:41 node-4 kernel: [    0.460671] acpi PNP0A03:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 13 18:09:41 node-4 kernel: [    0.460697] PCI host bridge to bus 0000:ff
Sep 13 18:09:41 node-4 kernel: [    0.460700] pci_bus 0000:ff: root bus resource [bus ff]
Sep 13 18:09:41 node-4 kernel: [    0.460708] pci 0000:ff:08.0: [8086:2f80] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.460746] pci 0000:ff:08.2: [8086:2f32] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.460776] pci 0000:ff:08.3: [8086:2f83] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.460810] pci 0000:ff:0b.0: [8086:2f81] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.460839] pci 0000:ff:0b.1: [8086:2f36] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.460867] pci 0000:ff:0b.2: [8086:2f37] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.460898] pci 0000:ff:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.460926] pci 0000:ff:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.460956] pci 0000:ff:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.460986] pci 0000:ff:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461012] pci 0000:ff:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461039] pci 0000:ff:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461067] pci 0000:ff:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461093] pci 0000:ff:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461119] pci 0000:ff:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461145] pci 0000:ff:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461174] pci 0000:ff:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461201] pci 0000:ff:10.0: [8086:2f1d] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461228] pci 0000:ff:10.1: [8086:2f34] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.461256] pci 0000:ff:10.5: [8086:2f1e] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461282] pci 0000:ff:10.6: [8086:2f7d] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.461309] pci 0000:ff:10.7: [8086:2f1f] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461336] pci 0000:ff:12.0: [8086:2fa0] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461368] pci 0000:ff:12.1: [8086:2f30] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.461402] pci 0000:ff:13.0: [8086:2fa8] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461433] pci 0000:ff:13.1: [8086:2f71] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461463] pci 0000:ff:13.2: [8086:2faa] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461494] pci 0000:ff:13.3: [8086:2fab] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461526] pci 0000:ff:13.4: [8086:2fac] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461558] pci 0000:ff:13.5: [8086:2fad] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461592] pci 0000:ff:13.6: [8086:2fae] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461624] pci 0000:ff:13.7: [8086:2faf] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461654] pci 0000:ff:14.0: [8086:2fb0] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461686] pci 0000:ff:14.1: [8086:2fb1] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461718] pci 0000:ff:14.2: [8086:2fb2] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461749] pci 0000:ff:14.3: [8086:2fb3] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461781] pci 0000:ff:14.6: [8086:2fbe] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461809] pci 0000:ff:14.7: [8086:2fbf] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461836] pci 0000:ff:15.0: [8086:2fb4] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461868] pci 0000:ff:15.1: [8086:2fb5] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461900] pci 0000:ff:15.2: [8086:2fb6] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461937] pci 0000:ff:15.3: [8086:2fb7] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.461971] pci 0000:ff:16.0: [8086:2f68] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462002] pci 0000:ff:16.6: [8086:2f6e] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462032] pci 0000:ff:16.7: [8086:2f6f] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462060] pci 0000:ff:17.0: [8086:2fd0] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462090] pci 0000:ff:17.4: [8086:2fb8] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462120] pci 0000:ff:17.5: [8086:2fb9] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462153] pci 0000:ff:17.6: [8086:2fba] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462183] pci 0000:ff:17.7: [8086:2fbb] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462215] pci 0000:ff:1e.0: [8086:2f98] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462244] pci 0000:ff:1e.1: [8086:2f99] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462273] pci 0000:ff:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462302] pci 0000:ff:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462331] pci 0000:ff:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462362] pci 0000:ff:1f.0: [8086:2f88] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462393] pci 0000:ff:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462451] ACPI: PCI Root Bridge [UNC0] (domain 0000 [bus 7f])
Sep 13 18:09:41 node-4 kernel: [    0.462453] acpi PNP0A03:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 18:09:41 node-4 kernel: [    0.462456] acpi PNP0A03:01: _OSC failed (AE_NOT_FOUND); disabling ASPM
Sep 13 18:09:41 node-4 kernel: [    0.462478] PCI host bridge to bus 0000:7f
Sep 13 18:09:41 node-4 kernel: [    0.462480] pci_bus 0000:7f: root bus resource [bus 7f]
Sep 13 18:09:41 node-4 kernel: [    0.462485] pci 0000:7f:08.0: [8086:2f80] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462512] pci 0000:7f:08.2: [8086:2f32] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.462540] pci 0000:7f:08.3: [8086:2f83] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462570] pci 0000:7f:0b.0: [8086:2f81] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462591] pci 0000:7f:0b.1: [8086:2f36] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.462616] pci 0000:7f:0b.2: [8086:2f37] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.462643] pci 0000:7f:0c.0: [8086:2fe0] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462669] pci 0000:7f:0c.1: [8086:2fe1] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462691] pci 0000:7f:0c.2: [8086:2fe2] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462714] pci 0000:7f:0c.3: [8086:2fe3] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462737] pci 0000:7f:0c.4: [8086:2fe4] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462759] pci 0000:7f:0c.5: [8086:2fe5] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462783] pci 0000:7f:0f.0: [8086:2ff8] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462805] pci 0000:7f:0f.1: [8086:2ff9] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462828] pci 0000:7f:0f.4: [8086:2ffc] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462854] pci 0000:7f:0f.5: [8086:2ffd] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462875] pci 0000:7f:0f.6: [8086:2ffe] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462898] pci 0000:7f:10.0: [8086:2f1d] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462921] pci 0000:7f:10.1: [8086:2f34] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.462944] pci 0000:7f:10.5: [8086:2f1e] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.462966] pci 0000:7f:10.6: [8086:2f7d] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.462988] pci 0000:7f:10.7: [8086:2f1f] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463011] pci 0000:7f:12.0: [8086:2fa0] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463037] pci 0000:7f:12.1: [8086:2f30] type 00 class 0x110100
Sep 13 18:09:41 node-4 kernel: [    0.463069] pci 0000:7f:13.0: [8086:2fa8] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463096] pci 0000:7f:13.1: [8086:2f71] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463123] pci 0000:7f:13.2: [8086:2faa] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463151] pci 0000:7f:13.3: [8086:2fab] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463176] pci 0000:7f:13.4: [8086:2fac] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463202] pci 0000:7f:13.5: [8086:2fad] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463228] pci 0000:7f:13.6: [8086:2fae] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463256] pci 0000:7f:13.7: [8086:2faf] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463280] pci 0000:7f:14.0: [8086:2fb0] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463308] pci 0000:7f:14.1: [8086:2fb1] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463336] pci 0000:7f:14.2: [8086:2fb2] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463364] pci 0000:7f:14.3: [8086:2fb3] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463392] pci 0000:7f:14.6: [8086:2fbe] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463417] pci 0000:7f:14.7: [8086:2fbf] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463444] pci 0000:7f:15.0: [8086:2fb4] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463471] pci 0000:7f:15.1: [8086:2fb5] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463497] pci 0000:7f:15.2: [8086:2fb6] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463525] pci 0000:7f:15.3: [8086:2fb7] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463555] pci 0000:7f:16.0: [8086:2f68] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463583] pci 0000:7f:16.6: [8086:2f6e] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463610] pci 0000:7f:16.7: [8086:2f6f] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463635] pci 0000:7f:17.0: [8086:2fd0] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463663] pci 0000:7f:17.4: [8086:2fb8] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463692] pci 0000:7f:17.5: [8086:2fb9] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463720] pci 0000:7f:17.6: [8086:2fba] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463748] pci 0000:7f:17.7: [8086:2fbb] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463778] pci 0000:7f:1e.0: [8086:2f98] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463805] pci 0000:7f:1e.1: [8086:2f99] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463828] pci 0000:7f:1e.2: [8086:2f9a] type 00 class 0x088000
Sep 13 18:09:41 node-4 rsyslogd-2039: Could no open output pipe '/dev/xconsole': No such file or directory [try http://www.rsyslog.com/e/2039 ]
Sep 13 18:09:41 node-4 kernel: [    0.463854] pci 0000:7f:1e.3: [8086:2fc0] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463881] pci 0000:7f:1e.4: [8086:2f9c] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463911] pci 0000:7f:1f.0: [8086:2f88] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.463938] pci 0000:7f:1f.2: [8086:2f8a] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.465194] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-7e])
Sep 13 18:09:41 node-4 kernel: [    0.465198] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 18:09:41 node-4 kernel: [    0.466323] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 13 18:09:41 node-4 kernel: [    0.466837] PCI host bridge to bus 0000:00
Sep 13 18:09:41 node-4 kernel: [    0.466840] pci_bus 0000:00: root bus resource [bus 00-7e]
Sep 13 18:09:41 node-4 kernel: [    0.466841] pci_bus 0000:00: root bus resource [io  0x0000-0x03af]
Sep 13 18:09:41 node-4 kernel: [    0.466843] pci_bus 0000:00: root bus resource [io  0x03e0-0x0cf7]
Sep 13 18:09:41 node-4 kernel: [    0.466844] pci_bus 0000:00: root bus resource [io  0x03b0-0x03df]
Sep 13 18:09:41 node-4 kernel: [    0.466845] pci_bus 0000:00: root bus resource [io  0x1000-0x7fff]
Sep 13 18:09:41 node-4 kernel: [    0.466847] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff]
Sep 13 18:09:41 node-4 kernel: [    0.466848] pci_bus 0000:00: root bus resource [mem 0x90000000-0xc7ffbfff]
Sep 13 18:09:41 node-4 kernel: [    0.466854] pci 0000:00:00.0: [8086:2f00] type 00 class 0x060000
Sep 13 18:09:41 node-4 kernel: [    0.466937] pci 0000:00:01.0: [8086:2f02] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.466968] pci 0000:00:01.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.467009] pci 0000:00:01.0: System wakeup disabled by ACPI
Sep 13 18:09:41 node-4 kernel: [    0.467032] pci 0000:00:02.0: [8086:2f04] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.467061] pci 0000:00:02.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.467102] pci 0000:00:02.0: System wakeup disabled by ACPI
Sep 13 18:09:41 node-4 kernel: [    0.467121] pci 0000:00:03.0: [8086:2f08] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.467150] pci 0000:00:03.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.467191] pci 0000:00:03.0: System wakeup disabled by ACPI
Sep 13 18:09:41 node-4 kernel: [    0.467208] pci 0000:00:05.0: [8086:2f28] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.467279] pci 0000:00:05.1: [8086:2f29] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.467358] pci 0000:00:05.2: [8086:2f2a] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.467435] pci 0000:00:05.4: [8086:2f2c] type 00 class 0x080020
Sep 13 18:09:41 node-4 kernel: [    0.467440] pci 0000:00:05.4: reg 0x10: [mem 0xc7115000-0xc7115fff]
Sep 13 18:09:41 node-4 kernel: [    0.467526] pci 0000:00:11.0: [8086:8d7c] type 00 class 0xff0000
Sep 13 18:09:41 node-4 kernel: [    0.467675] pci 0000:00:1a.0: [8086:8d2d] type 00 class 0x0c0320
Sep 13 18:09:41 node-4 kernel: [    0.467692] pci 0000:00:1a.0: reg 0x10: [mem 0xc7111000-0xc71113ff]
Sep 13 18:09:41 node-4 kernel: [    0.467770] pci 0000:00:1a.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.467823] pci 0000:00:1a.0: System wakeup disabled by ACPI
Sep 13 18:09:41 node-4 kernel: [    0.467845] pci 0000:00:1c.0: [8086:8d10] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.467900] pci 0000:00:1c.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.467944] pci 0000:00:1c.0: System wakeup disabled by ACPI
Sep 13 18:09:41 node-4 kernel: [    0.467972] pci 0000:00:1c.7: [8086:8d1e] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.468028] pci 0000:00:1c.7: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.468071] pci 0000:00:1c.7: System wakeup disabled by ACPI
Sep 13 18:09:41 node-4 kernel: [    0.468096] pci 0000:00:1d.0: [8086:8d26] type 00 class 0x0c0320
Sep 13 18:09:41 node-4 kernel: [    0.468113] pci 0000:00:1d.0: reg 0x10: [mem 0xc7110000-0xc71103ff]
Sep 13 18:09:41 node-4 kernel: [    0.468190] pci 0000:00:1d.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.468240] pci 0000:00:1d.0: System wakeup disabled by ACPI
Sep 13 18:09:41 node-4 kernel: [    0.468267] pci 0000:00:1f.0: [8086:8d44] type 00 class 0x060100
Sep 13 18:09:41 node-4 kernel: [    0.468516] pci 0000:01:00.0: [1000:005d] type 00 class 0x010400
Sep 13 18:09:41 node-4 kernel: [    0.468522] pci 0000:01:00.0: reg 0x10: [io  0x6000-0x60ff]
Sep 13 18:09:41 node-4 kernel: [    0.468528] pci 0000:01:00.0: reg 0x14: [mem 0xc7000000-0xc700ffff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.468534] pci 0000:01:00.0: reg 0x1c: [mem 0xc6f00000-0xc6ffffff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.468541] pci 0000:01:00.0: reg 0x30: [mem 0xc6e00000-0xc6efffff pref]
Sep 13 18:09:41 node-4 kernel: [    0.468571] pci 0000:01:00.0: supports D1 D2
Sep 13 18:09:41 node-4 kernel: [    0.474485] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 13 18:09:41 node-4 kernel: [    0.474492] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 13 18:09:41 node-4 kernel: [    0.474496] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 13 18:09:41 node-4 kernel: [    0.474626] pci 0000:02:00.0: [1137:004e] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.474659] pci 0000:02:00.0: PME# supported from D0 D3hot
Sep 13 18:09:41 node-4 kernel: [    0.482488] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 13 18:09:41 node-4 kernel: [    0.482491] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.482492] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:41 node-4 kernel: [    0.482547] pci 0000:03:00.0: [1137:0041] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.482629] pci 0000:03:00.0: reg 0x10: [mem 0xc6d00000-0xc6d0ffff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.482704] pci 0000:03:00.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.482750] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 13 18:09:41 node-4 kernel: [    0.482754] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.482755] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:41 node-4 kernel: [    0.482808] pci 0000:04:00.0: [1137:0040] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.482931] pci 0000:04:00.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.482985] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 13 18:09:41 node-4 kernel: [    0.482988] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.482990] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:41 node-4 kernel: [    0.483039] pci 0000:05:00.0: [1137:0041] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.483161] pci 0000:05:00.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.483200] pci 0000:05:01.0: [1137:0041] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.483319] pci 0000:05:01.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.483355] pci 0000:05:02.0: [1137:0041] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.483475] pci 0000:05:02.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.483512] pci 0000:05:03.0: [1137:0041] type 01 class 0x060400
Sep 13 18:09:41 node-4 kernel: [    0.483651] pci 0000:05:03.0: PME# supported from D0 D3hot D3cold
Sep 13 18:09:41 node-4 kernel: [    0.483692] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 13 18:09:41 node-4 kernel: [    0.483695] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.483697] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:41 node-4 kernel: [    0.483757] pci 0000:06:00.0: [1137:0043] type 00 class 0x020000
Sep 13 18:09:41 node-4 kernel: [    0.483819] pci 0000:06:00.0: reg 0x10: [mem 0xc6c10000-0xc6c17fff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.483872] pci 0000:06:00.0: reg 0x18: [mem 0xc6c18000-0xc6c19fff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.483913] pci 0000:06:00.0: reg 0x20: [io  0x5000-0x507f]
Sep 13 18:09:41 node-4 kernel: [    0.483995] pci 0000:06:00.0: reg 0x30: [mem 0xc6c00000-0xc6c0ffff pref]
Sep 13 18:09:41 node-4 kernel: [    0.484106] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 13 18:09:41 node-4 kernel: [    0.484109] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.484111] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 13 18:09:41 node-4 kernel: [    0.484166] pci 0000:07:00.0: [1137:0043] type 00 class 0x020000
Sep 13 18:09:41 node-4 kernel: [    0.484220] pci 0000:07:00.0: reg 0x10: [mem 0xc6b00000-0xc6b07fff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.484269] pci 0000:07:00.0: reg 0x18: [mem 0xc6b08000-0xc6b09fff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.484481] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 13 18:09:41 node-4 kernel: [    0.484484] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 13 18:09:41 node-4 kernel: [    0.484566] pci 0000:08:00.0: [1137:0043] type 00 class 0x020000
Sep 13 18:09:41 node-4 kernel: [    0.484627] pci 0000:08:00.0: reg 0x10: [mem 0xc6a00000-0xc6a07fff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.484676] pci 0000:08:00.0: reg 0x18: [mem 0xc6a08000-0xc6a09fff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.484885] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 13 18:09:41 node-4 kernel: [    0.484889] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 13 18:09:41 node-4 kernel: [    0.484947] pci 0000:09:00.0: [1137:0043] type 00 class 0x020000
Sep 13 18:09:41 node-4 kernel: [    0.485007] pci 0000:09:00.0: reg 0x10: [mem 0xc6900000-0xc6907fff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.485059] pci 0000:09:00.0: reg 0x18: [mem 0xc6908000-0xc6909fff 64bit]
Sep 13 18:09:41 node-4 kernel: [    0.485281] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 13 18:09:41 node-4 kernel: [    0.485285] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 13 18:09:41 node-4 kernel: [    0.485460] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 13 18:09:41 node-4 kernel: [    0.485498] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 13 18:09:41 node-4 kernel: [    0.485576] pci 0000:0c:00.0: [102b:0522] type 00 class 0x030000
Sep 13 18:09:41 node-4 kernel: [    0.485595] pci 0000:0c:00.0: reg 0x10: [mem 0xc5000000-0xc5ffffff]
Sep 13 18:09:41 node-4 kernel: [    0.485608] pci 0000:0c:00.0: reg 0x14: [mem 0xc6810000-0xc6813fff]
Sep 13 18:09:41 node-4 kernel: [    0.485621] pci 0000:0c:00.0: reg 0x18: [mem 0xc6000000-0xc67fffff]
Sep 13 18:09:41 node-4 kernel: [    0.485671] pci 0000:0c:00.0: reg 0x30: [mem 0xc6800000-0xc680ffff pref]
Sep 13 18:09:41 node-4 kernel: [    0.490490] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 13 18:09:41 node-4 kernel: [    0.490499] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 13 18:09:41 node-4 kernel: [    0.490551] pci_bus 0000:00: on NUMA node 0 (pxm 0)
Sep 13 18:09:41 node-4 kernel: [    0.491044] ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-fe])
Sep 13 18:09:41 node-4 kernel: [    0.491047] acpi PNP0A08:01: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
Sep 13 18:09:41 node-4 kernel: [    0.491166] acpi PNP0A08:01: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability]
Sep 13 18:09:41 node-4 kernel: [    0.491275] PCI host bridge to bus 0000:80
Sep 13 18:09:41 node-4 kernel: [    0.491277] pci_bus 0000:80: root bus resource [bus 80-fe]
Sep 13 18:09:41 node-4 kernel: [    0.491278] pci_bus 0000:80: root bus resource [io  0x8000-0xffff]
Sep 13 18:09:41 node-4 kernel: [    0.491280] pci_bus 0000:80: root bus resource [mem 0xc8000000-0xfbffbfff]
Sep 13 18:09:41 node-4 kernel: [    0.491288] pci 0000:80:05.0: [8086:2f28] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.491351] pci 0000:80:05.1: [8086:2f29] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.491419] pci 0000:80:05.2: [8086:2f2a] type 00 class 0x088000
Sep 13 18:09:41 node-4 kernel: [    0.491482] pci 0000:80:05.4: [8086:2f2c] type 00 class 0x080020
Sep 13 18:09:41 node-4 kernel: [    0.491487] pci 0000:80:05.4: reg 0x10: [mem 0xfbf00000-0xfbf00fff]
Sep 13 18:09:41 node-4 kernel: [    0.491558] pci_bus 0000:80: on NUMA node 1 (pxm 1)
Sep 13 18:09:41 node-4 kernel: [    0.491856] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15)
Sep 13 18:09:41 node-4 kernel: [    0.491888] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *10 11 12 14 15)
Sep 13 18:09:41 node-4 kernel: [    0.491917] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 10 11 12 14 15)
Sep 13 18:09:41 node-4 kernel: [    0.491947] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 *11 12 14 15)
Sep 13 18:09:41 node-4 kernel: [    0.491976] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 18:09:41 node-4 kernel: [    0.492006] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 18:09:41 node-4 kernel: [    0.492036] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 18:09:41 node-4 kernel: [    0.492066] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
Sep 13 18:09:41 node-4 kernel: [    0.492151] ACPI: Enabled 3 GPEs in block 00 to 3F
Sep 13 18:09:41 node-4 kernel: [    0.492156] ACPI: \_SB_.UNC1: notify handler is installed
Sep 13 18:09:41 node-4 kernel: [    0.492157] ACPI: \_SB_.UNC0: notify handler is installed
Sep 13 18:09:41 node-4 kernel: [    0.492172] ACPI: \_SB_.PCI0: notify handler is installed
Sep 13 18:09:41 node-4 kernel: [    0.492225] ACPI: \_SB_.PCI1: notify handler is installed
Sep 13 18:09:41 node-4 kernel: [    0.492303] Found 4 acpi root devices
Sep 13 18:09:41 node-4 kernel: [    0.492412] vgaarb: setting as boot device: PCI:0000:0c:00.0
Sep 13 18:09:41 node-4 kernel: [    0.492414] vgaarb: device added: PCI:0000:0c:00.0,decodes=io+mem,owns=io+mem,locks=none
Sep 13 18:09:41 node-4 kernel: [    0.492415] vgaarb: loaded
Sep 13 18:09:41 node-4 kernel: [    0.492416] vgaarb: bridge control possible 0000:0c:00.0
Sep 13 18:09:41 node-4 kernel: [    0.492536] SCSI subsystem initialized
Sep 13 18:09:41 node-4 kernel: [    0.492600] libata version 3.00 loaded.
Sep 13 18:09:41 node-4 kernel: [    0.492615] ACPI: bus type USB registered
Sep 13 18:09:41 node-4 kernel: [    0.492625] usbcore: registered new interface driver usbfs
Sep 13 18:09:41 node-4 kernel: [    0.492630] usbcore: registered new interface driver hub
Sep 13 18:09:41 node-4 kernel: [    0.492654] usbcore: registered new device driver usb
Sep 13 18:09:41 node-4 kernel: [    0.492832] PCI: Using ACPI for IRQ routing
Sep 13 18:09:41 node-4 kernel: [    0.496413] PCI: pci_cache_line_size set to 64 bytes
Sep 13 18:09:41 node-4 kernel: [    0.496622] e820: reserve RAM buffer [mem 0x0009ec00-0x0009ffff]
Sep 13 18:09:41 node-4 kernel: [    0.496623] e820: reserve RAM buffer [mem 0x6f2e0000-0x6fffffff]
Sep 13 18:09:41 node-4 kernel: [    0.496623] e820: reserve RAM buffer [mem 0x7bd59000-0x7bffffff]
Sep 13 18:09:41 node-4 kernel: [    0.496689] NetLabel: Initializing
Sep 13 18:09:41 node-4 kernel: [    0.496690] NetLabel:  domain hash size = 128
Sep 13 18:09:41 node-4 kernel: [    0.496691] NetLabel:  protocols = UNLABELED CIPSOv4
Sep 13 18:09:41 node-4 kernel: [    0.496701] NetLabel:  unlabeled traffic allowed by default
Sep 13 18:09:41 node-4 kernel: [    0.496757] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
Sep 13 18:09:41 node-4 kernel: [    0.496761] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
Sep 13 18:09:41 node-4 kernel: [    0.498818] Switched to clocksource hpet
Sep 13 18:09:41 node-4 kernel: [    0.502617] AppArmor: AppArmor Filesystem Enabled
Sep 13 18:09:41 node-4 kernel: [    0.502630] pnp: PnP ACPI init
Sep 13 18:09:41 node-4 kernel: [    0.502637] ACPI: bus type PNP registered
Sep 13 18:09:41 node-4 kernel: [    0.502750] pnp 00:00: Plug and Play ACPI device, IDs PNP0003 (active)
Sep 13 18:09:41 node-4 kernel: [    0.502758] pnp 00:01: [dma 4]
Sep 13 18:09:41 node-4 kernel: [    0.502778] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
Sep 13 18:09:41 node-4 kernel: [    0.502805] pnp 00:02: Plug and Play ACPI device, IDs PNP0b00 (active)
Sep 13 18:09:41 node-4 kernel: [    0.502830] pnp 00:03: Plug and Play ACPI device, IDs PNP0c04 (active)
Sep 13 18:09:41 node-4 kernel: [    0.502848] pnp 00:04: Plug and Play ACPI device, IDs PNP0800 (active)
Sep 13 18:09:41 node-4 kernel: [    0.502882] pnp 00:05: Plug and Play ACPI device, IDs PNP0103 (active)
Sep 13 18:09:41 node-4 kernel: [    0.502936] system 00:06: [io  0x0500-0x057f] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502938] system 00:06: [io  0x0400-0x047f] could not be reserved
Sep 13 18:09:41 node-4 kernel: [    0.502939] system 00:06: [io  0x0580-0x059f] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502941] system 00:06: [io  0x0600-0x061f] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502942] system 00:06: [io  0x0880-0x0883] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502947] system 00:06: [io  0x0800-0x081f] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502949] system 00:06: [mem 0xfed1c000-0xfed3ffff] could not be reserved
Sep 13 18:09:41 node-4 kernel: [    0.502951] system 00:06: [mem 0xfed45000-0xfed8bfff] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502952] system 00:06: [mem 0xff000000-0xffffffff] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502954] system 00:06: [mem 0xfee00000-0xfeefffff] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502955] system 00:06: [mem 0xfed12000-0xfed1200f] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502957] system 00:06: [mem 0xfed12010-0xfed1201f] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502958] system 00:06: [mem 0xfed1b000-0xfed1bfff] has been reserved
Sep 13 18:09:41 node-4 kernel: [    0.502960] system 00:06: Plug and Play ACPI device, IDs PNP0c02 (active)
Sep 13 18:09:41 node-4 kernel: [    0.503044] pnp 00:07: [dma 0 disabled]
Sep 13 18:09:41 node-4 kernel: [    0.503073] pnp 00:07: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 13 18:09:41 node-4 kernel: [    0.503147] pnp 00:08: [dma 0 disabled]
Sep 13 18:09:41 node-4 kernel: [    0.503180] pnp 00:08: Plug and Play ACPI device, IDs PNP0501 (active)
Sep 13 18:09:41 node-4 kernel: [    0.503231] pnp 00:09: Plug and Play ACPI device, IDs IPI0001 (active)
Sep 13 18:09:41 node-4 kernel: [    0.503584] pnp: PnP ACPI: found 10 devices
Sep 13 18:09:41 node-4 kernel: [    0.503586] ACPI: bus type PNP unregistered
Sep 13 18:09:41 node-4 kernel: [    0.509859] pci 0000:00:01.0: PCI bridge to [bus 01]
Sep 13 18:09:41 node-4 kernel: [    0.509861] pci 0000:00:01.0:   bridge window [io  0x6000-0x6fff]
Sep 13 18:09:41 node-4 kernel: [    0.509864] pci 0000:00:01.0:   bridge window [mem 0xc6e00000-0xc70fffff]
Sep 13 18:09:41 node-4 kernel: [    0.509868] pci 0000:05:00.0: PCI bridge to [bus 06]
Sep 13 18:09:41 node-4 kernel: [    0.509870] pci 0000:05:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.509885] pci 0000:05:00.0:   bridge window [mem 0xc6c00000-0xc6cfffff]
Sep 13 18:09:41 node-4 kernel: [    0.509914] pci 0000:05:01.0: PCI bridge to [bus 07]
Sep 13 18:09:41 node-4 kernel: [    0.509928] pci 0000:05:01.0:   bridge window [mem 0xc6b00000-0xc6bfffff]
Sep 13 18:09:41 node-4 kernel: [    0.509957] pci 0000:05:02.0: PCI bridge to [bus 08]
Sep 13 18:09:41 node-4 kernel: [    0.509972] pci 0000:05:02.0:   bridge window [mem 0xc6a00000-0xc6afffff]
Sep 13 18:09:41 node-4 kernel: [    0.510000] pci 0000:05:03.0: PCI bridge to [bus 09]
Sep 13 18:09:41 node-4 kernel: [    0.510015] pci 0000:05:03.0:   bridge window [mem 0xc6900000-0xc69fffff]
Sep 13 18:09:41 node-4 kernel: [    0.510047] pci 0000:04:00.0: PCI bridge to [bus 05-09]
Sep 13 18:09:41 node-4 kernel: [    0.510049] pci 0000:04:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.510064] pci 0000:04:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:41 node-4 kernel: [    0.510093] pci 0000:03:00.0: PCI bridge to [bus 04-09]
Sep 13 18:09:41 node-4 kernel: [    0.510095] pci 0000:03:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.510109] pci 0000:03:00.0:   bridge window [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:41 node-4 kernel: [    0.510138] pci 0000:02:00.0: PCI bridge to [bus 03-09]
Sep 13 18:09:41 node-4 kernel: [    0.510140] pci 0000:02:00.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.510142] pci 0000:02:00.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:41 node-4 kernel: [    0.510146] pci 0000:00:02.0: PCI bridge to [bus 02-09]
Sep 13 18:09:41 node-4 kernel: [    0.510148] pci 0000:00:02.0:   bridge window [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.510151] pci 0000:00:02.0:   bridge window [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:41 node-4 kernel: [    0.510154] pci 0000:00:03.0: PCI bridge to [bus 0a]
Sep 13 18:09:41 node-4 kernel: [    0.510159] pci 0000:00:1c.0: PCI bridge to [bus 0b]
Sep 13 18:09:41 node-4 kernel: [    0.510167] pci 0000:00:1c.7: PCI bridge to [bus 0c]
Sep 13 18:09:41 node-4 kernel: [    0.510170] pci 0000:00:1c.7:   bridge window [mem 0xc5000000-0xc68fffff]
Sep 13 18:09:41 node-4 kernel: [    0.510176] pci_bus 0000:00: resource 4 [io  0x0000-0x03af]
Sep 13 18:09:41 node-4 kernel: [    0.510177] pci_bus 0000:00: resource 5 [io  0x03e0-0x0cf7]
Sep 13 18:09:41 node-4 kernel: [    0.510178] pci_bus 0000:00: resource 6 [io  0x03b0-0x03df]
Sep 13 18:09:41 node-4 kernel: [    0.510179] pci_bus 0000:00: resource 7 [io  0x1000-0x7fff]
Sep 13 18:09:41 node-4 kernel: [    0.510180] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff]
Sep 13 18:09:41 node-4 kernel: [    0.510181] pci_bus 0000:00: resource 9 [mem 0x90000000-0xc7ffbfff]
Sep 13 18:09:41 node-4 kernel: [    0.510182] pci_bus 0000:01: resource 0 [io  0x6000-0x6fff]
Sep 13 18:09:41 node-4 kernel: [    0.510183] pci_bus 0000:01: resource 1 [mem 0xc6e00000-0xc70fffff]
Sep 13 18:09:41 node-4 kernel: [    0.510184] pci_bus 0000:02: resource 0 [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.510185] pci_bus 0000:02: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:41 node-4 kernel: [    0.510185] pci_bus 0000:03: resource 0 [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.510186] pci_bus 0000:03: resource 1 [mem 0xc6900000-0xc6dfffff]
Sep 13 18:09:41 node-4 kernel: [    0.510187] pci_bus 0000:04: resource 0 [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.510188] pci_bus 0000:04: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:41 node-4 kernel: [    0.510189] pci_bus 0000:05: resource 0 [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.510190] pci_bus 0000:05: resource 1 [mem 0xc6900000-0xc6cfffff]
Sep 13 18:09:41 node-4 kernel: [    0.510191] pci_bus 0000:06: resource 0 [io  0x5000-0x5fff]
Sep 13 18:09:41 node-4 kernel: [    0.510191] pci_bus 0000:06: resource 1 [mem 0xc6c00000-0xc6cfffff]
Sep 13 18:09:41 node-4 kernel: [    0.510192] pci_bus 0000:07: resource 1 [mem 0xc6b00000-0xc6bfffff]
Sep 13 18:09:41 node-4 kernel: [    0.510194] pci_bus 0000:08: resource 1 [mem 0xc6a00000-0xc6afffff]
Sep 13 18:09:41 node-4 kernel: [    0.510194] pci_bus 0000:09: resource 1 [mem 0xc6900000-0xc69fffff]
Sep 13 18:09:41 node-4 kernel: [    0.510196] pci_bus 0000:0c: resource 1 [mem 0xc5000000-0xc68fffff]
Sep 13 18:09:41 node-4 kernel: [    0.510197] pci_bus 0000:80: resource 4 [io  0x8000-0xffff]
Sep 13 18:09:41 node-4 kernel: [    0.510198] pci_bus 0000:80: resource 5 [mem 0xc8000000-0xfbffbfff]
Sep 13 18:09:41 node-4 kernel: [    0.510240] NET: Registered protocol family 2
Sep 13 18:09:41 node-4 kernel: [    0.510494] TCP established hash table entries: 262144 (order: 9, 2097152 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.510830] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.510974] TCP: Hash tables configured (established 262144 bind 65536)
Sep 13 18:09:41 node-4 kernel: [    0.511017] TCP: reno registered
Sep 13 18:09:41 node-4 kernel: [    0.511047] UDP hash table entries: 16384 (order: 7, 524288 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.511145] UDP-Lite hash table entries: 16384 (order: 7, 524288 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.511294] NET: Registered protocol family 1
Sep 13 18:09:41 node-4 kernel: [    0.546882] pci 0000:0c:00.0: Video device with shadowed ROM
Sep 13 18:09:41 node-4 kernel: [    0.546890] PCI: CLS 64 bytes, default 64
Sep 13 18:09:41 node-4 kernel: [    0.546932] Trying to unpack rootfs image as initramfs...
Sep 13 18:09:41 node-4 kernel: [    0.766807] Freeing initrd memory: 20380K (ffff880035822000 - ffff880036c09000)
Sep 13 18:09:41 node-4 kernel: [    0.766839] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
Sep 13 18:09:41 node-4 kernel: [    0.766842] software IO TLB [mem 0x6b2e0000-0x6f2e0000] (64MB) mapped at [ffff88006b2e0000-ffff88006f2dffff]
Sep 13 18:09:41 node-4 kernel: [    0.767229] microcode: CPU0 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767235] microcode: CPU1 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767239] microcode: CPU2 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767245] microcode: CPU3 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767254] microcode: CPU4 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767264] microcode: CPU5 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767273] microcode: CPU6 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767281] microcode: CPU7 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767288] microcode: CPU8 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767296] microcode: CPU9 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767302] microcode: CPU10 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767308] microcode: CPU11 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767315] microcode: CPU12 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767322] microcode: CPU13 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767329] microcode: CPU14 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767336] microcode: CPU15 sig=0x306f2, pf=0x1, revision=0x27
Sep 13 18:09:41 node-4 kernel: [    0.767405] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
Sep 13 18:09:41 node-4 kernel: [    0.767407] Scanning for low memory corruption every 60 seconds
Sep 13 18:09:41 node-4 kernel: [    0.767773] Initialise system trusted keyring
Sep 13 18:09:41 node-4 kernel: [    0.767824] audit: initializing netlink socket (disabled)
Sep 13 18:09:41 node-4 kernel: [    0.767839] type=2000 audit(1473790145.724:1): initialized
Sep 13 18:09:41 node-4 kernel: [    0.785645] HugeTLB registered 2 MB page size, pre-allocated 0 pages
Sep 13 18:09:41 node-4 kernel: [    0.787110] zbud: loaded
Sep 13 18:09:41 node-4 kernel: [    0.787240] VFS: Disk quotas dquot_6.5.2
Sep 13 18:09:41 node-4 kernel: [    0.787275] Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Sep 13 18:09:41 node-4 kernel: [    0.787635] fuse init (API version 7.22)
Sep 13 18:09:41 node-4 kernel: [    0.787689] msgmni has been set to 32768
Sep 13 18:09:41 node-4 kernel: [    0.787740] Key type big_key registered
Sep 13 18:09:41 node-4 kernel: [    0.788212] Key type asymmetric registered
Sep 13 18:09:41 node-4 kernel: [    0.788214] Asymmetric key parser 'x509' registered
Sep 13 18:09:41 node-4 kernel: [    0.788235] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
Sep 13 18:09:41 node-4 kernel: [    0.788296] io scheduler noop registered
Sep 13 18:09:41 node-4 kernel: [    0.788298] io scheduler deadline registered (default)
Sep 13 18:09:41 node-4 kernel: [    0.788315] io scheduler cfq registered
Sep 13 18:09:41 node-4 kernel: [    0.788810] pcieport 0000:00:01.0: irq 90 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    0.789016] pcieport 0000:00:02.0: irq 91 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    0.789132] pcieport 0000:00:03.0: irq 92 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    0.789241] pcieport 0000:00:1c.0: irq 93 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    0.789356] pcieport 0000:00:1c.7: irq 94 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    0.789449] pcieport 0000:02:00.0: irq 95 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    0.789885] aer 0000:00:01.0:pcie02: service driver aer loaded
Sep 13 18:09:41 node-4 kernel: [    0.789910] aer 0000:00:02.0:pcie02: service driver aer loaded
Sep 13 18:09:41 node-4 kernel: [    0.789926] aer 0000:00:03.0:pcie02: service driver aer loaded
Sep 13 18:09:41 node-4 kernel: [    0.789938] pcieport 0000:00:01.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789940] pci 0000:01:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789942] pcie_pme 0000:00:01.0:pcie01: service driver pcie_pme loaded
Sep 13 18:09:41 node-4 kernel: [    0.789947] pcieport 0000:00:02.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789949] pcieport 0000:02:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789950] pcieport 0000:03:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789952] pcieport 0000:04:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789953] pcieport 0000:05:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789955] pci 0000:06:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789956] pcieport 0000:05:01.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789958] pci 0000:07:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789959] pcieport 0000:05:02.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789960] pci 0000:08:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789961] pcieport 0000:05:03.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789963] pci 0000:09:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789965] pcie_pme 0000:00:02.0:pcie01: service driver pcie_pme loaded
Sep 13 18:09:41 node-4 kernel: [    0.789970] pcieport 0000:00:03.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789973] pcie_pme 0000:00:03.0:pcie01: service driver pcie_pme loaded
Sep 13 18:09:41 node-4 kernel: [    0.789984] pcieport 0000:00:1c.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789987] pcie_pme 0000:00:1c.0:pcie01: service driver pcie_pme loaded
Sep 13 18:09:41 node-4 kernel: [    0.789997] pcieport 0000:00:1c.7: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.789998] pci 0000:0c:00.0: Signaling PME through PCIe PME interrupt
Sep 13 18:09:41 node-4 kernel: [    0.790001] pcie_pme 0000:00:1c.7:pcie01: service driver pcie_pme loaded
Sep 13 18:09:41 node-4 kernel: [    0.790053] ioapic: probe of 0000:00:05.4 failed with error -22
Sep 13 18:09:41 node-4 kernel: [    0.790059] ioapic: probe of 0000:80:05.4 failed with error -22
Sep 13 18:09:41 node-4 kernel: [    0.790063] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
Sep 13 18:09:41 node-4 kernel: [    0.790080] pciehp: PCI Express Hot Plug Controller Driver version: 0.4
Sep 13 18:09:41 node-4 kernel: [    0.790118] vesafb: mode is 640x480x32, linelength=2560, pages=0
Sep 13 18:09:41 node-4 kernel: [    0.790120] vesafb: scrolling: redraw
Sep 13 18:09:41 node-4 kernel: [    0.790121] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
Sep 13 18:09:41 node-4 kernel: [    0.809499] vesafb: framebuffer at 0xc5000000, mapped to 0xffffc90013600000, using 1216k, total 1216k
Sep 13 18:09:41 node-4 kernel: [    0.818037] Console: switching to colour frame buffer device 80x30
Sep 13 18:09:41 node-4 kernel: [    0.826765] fb0: VESA VGA frame buffer device
Sep 13 18:09:41 node-4 kernel: [    0.826957] intel_idle: MWAIT substates: 0x2120
Sep 13 18:09:41 node-4 kernel: [    0.826959] intel_idle: v0.4 model 0x3F
Sep 13 18:09:41 node-4 kernel: [    0.826959] intel_idle: lapic_timer_reliable_states 0xffffffff
Sep 13 18:09:41 node-4 kernel: [    0.827198] ipmi message handler version 39.2
Sep 13 18:09:41 node-4 kernel: [    0.827459] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared
Sep 13 18:09:41 node-4 kernel: [    0.827892] ACPI: AC Adapter [P111] (on-line)
Sep 13 18:09:41 node-4 kernel: [    0.833162] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0
Sep 13 18:09:41 node-4 kernel: [    0.844254] ACPI: Power Button [PWRB]
Sep 13 18:09:41 node-4 kernel: [    0.850054] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input1
Sep 13 18:09:41 node-4 kernel: [    0.861763] ACPI: Power Button [PWRF]
Sep 13 18:09:41 node-4 kernel: [    0.888381] ERST: Error Record Serialization Table (ERST) support is initialized.
Sep 13 18:09:41 node-4 kernel: [    0.900119] pstore: Registered erst as persistent store backend
Sep 13 18:09:41 node-4 kernel: [    0.906358] GHES: APEI firmware first mode is enabled by APEI bit and WHEA _OSC.
Sep 13 18:09:41 node-4 kernel: [    0.918476] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Sep 13 18:09:41 node-4 kernel: [    0.945327] 00:07: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
Sep 13 18:09:41 node-4 kernel: [    0.978677] 00:08: ttyS1 at I/O 0x2f8 (irq = 3, base_baud = 115200) is a 16550A
Sep 13 18:09:41 node-4 kernel: [    0.992741] Linux agpgart interface v0.103
Sep 13 18:09:41 node-4 kernel: [    1.000357] brd: module loaded
Sep 13 18:09:41 node-4 kernel: [    1.007399] loop: module loaded
Sep 13 18:09:41 node-4 kernel: [    1.014110] libphy: Fixed MDIO Bus: probed
Sep 13 18:09:41 node-4 kernel: [    1.020589] tun: Universal TUN/TAP device driver, 1.6
Sep 13 18:09:41 node-4 kernel: [    1.027057] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Sep 13 18:09:41 node-4 kernel: [    1.033574] PPP generic driver version 2.4.2
Sep 13 18:09:41 node-4 kernel: [    1.039966] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Sep 13 18:09:41 node-4 kernel: [    1.046413] ehci-pci: EHCI PCI platform driver
Sep 13 18:09:41 node-4 kernel: [    1.052926] ehci-pci 0000:00:1a.0: EHCI Host Controller
Sep 13 18:09:41 node-4 kernel: [    1.059322] ehci-pci 0000:00:1a.0: new USB bus registered, assigned bus number 1
Sep 13 18:09:41 node-4 kernel: [    1.071834] ehci-pci 0000:00:1a.0: debug port 2
Sep 13 18:09:41 node-4 kernel: [    1.082020] ehci-pci 0000:00:1a.0: cache line size of 64 is not supported
Sep 13 18:09:41 node-4 kernel: [    1.082038] ehci-pci 0000:00:1a.0: irq 18, io mem 0xc7111000
Sep 13 18:09:41 node-4 kernel: [    1.098313] ehci-pci 0000:00:1a.0: USB 2.0 started, EHCI 1.00
Sep 13 18:09:41 node-4 kernel: [    1.104457] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
Sep 13 18:09:41 node-4 kernel: [    1.110733] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 13 18:09:41 node-4 kernel: [    1.122647] usb usb1: Product: EHCI Host Controller
Sep 13 18:09:41 node-4 kernel: [    1.128674] usb usb1: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 13 18:09:41 node-4 kernel: [    1.134730] usb usb1: SerialNumber: 0000:00:1a.0
Sep 13 18:09:41 node-4 kernel: [    1.140687] hub 1-0:1.0: USB hub found
Sep 13 18:09:41 node-4 kernel: [    1.146457] hub 1-0:1.0: 2 ports detected
Sep 13 18:09:41 node-4 kernel: [    1.152243] ehci-pci 0000:00:1d.0: EHCI Host Controller
Sep 13 18:09:41 node-4 kernel: [    1.157832] ehci-pci 0000:00:1d.0: new USB bus registered, assigned bus number 2
Sep 13 18:09:41 node-4 kernel: [    1.168745] ehci-pci 0000:00:1d.0: debug port 2
Sep 13 18:09:41 node-4 kernel: [    1.178037] ehci-pci 0000:00:1d.0: cache line size of 64 is not supported
Sep 13 18:09:41 node-4 kernel: [    1.178043] ehci-pci 0000:00:1d.0: irq 18, io mem 0xc7110000
Sep 13 18:09:41 node-4 kernel: [    1.194232] ehci-pci 0000:00:1d.0: USB 2.0 started, EHCI 1.00
Sep 13 18:09:41 node-4 kernel: [    1.199438] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
Sep 13 18:09:41 node-4 kernel: [    1.204739] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
Sep 13 18:09:41 node-4 kernel: [    1.215315] usb usb2: Product: EHCI Host Controller
Sep 13 18:09:41 node-4 kernel: [    1.220794] usb usb2: Manufacturer: Linux 3.13.0-95-generic ehci_hcd
Sep 13 18:09:41 node-4 kernel: [    1.226342] usb usb2: SerialNumber: 0000:00:1d.0
Sep 13 18:09:41 node-4 kernel: [    1.231853] hub 2-0:1.0: USB hub found
Sep 13 18:09:41 node-4 kernel: [    1.237209] hub 2-0:1.0: 2 ports detected
Sep 13 18:09:41 node-4 kernel: [    1.242515] ehci-platform: EHCI generic platform driver
Sep 13 18:09:41 node-4 kernel: [    1.247748] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
Sep 13 18:09:41 node-4 kernel: [    1.253063] ohci-pci: OHCI PCI platform driver
Sep 13 18:09:41 node-4 kernel: [    1.258364] ohci-platform: OHCI generic platform driver
Sep 13 18:09:41 node-4 kernel: [    1.263562] uhci_hcd: USB Universal Host Controller Interface driver
Sep 13 18:09:41 node-4 kernel: [    1.268898] i8042: PNP: No PS/2 controller found. Probing ports directly.
Sep 13 18:09:41 node-4 kernel: [    1.462010] usb 1-1: new high-speed USB device number 2 using ehci-pci
Sep 13 18:09:41 node-4 kernel: [    1.622197] usb 1-1: New USB device found, idVendor=8087, idProduct=800a
Sep 13 18:09:41 node-4 kernel: [    1.627715] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 13 18:09:41 node-4 kernel: [    1.633463] hub 1-1:1.0: USB hub found
Sep 13 18:09:41 node-4 kernel: [    1.638932] hub 1-1:1.0: 6 ports detected
Sep 13 18:09:41 node-4 kernel: [    1.753755] usb 2-1: new high-speed USB device number 2 using ehci-pci
Sep 13 18:09:41 node-4 kernel: [    1.765798] tsc: Refined TSC clocksource calibration: 3491.913 MHz
Sep 13 18:09:41 node-4 kernel: [    2.021857] usb 2-1: New USB device found, idVendor=8087, idProduct=8002
Sep 13 18:09:41 node-4 kernel: [    2.027390] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 13 18:09:41 node-4 kernel: [    2.033251] hub 2-1:1.0: USB hub found
Sep 13 18:09:41 node-4 kernel: [    2.038968] hub 2-1:1.0: 8 ports detected
Sep 13 18:09:41 node-4 kernel: [    2.310288] i8042: No controller found
Sep 13 18:09:41 node-4 kernel: [    2.315704] mousedev: PS/2 mouse device common for all mice
Sep 13 18:09:41 node-4 kernel: [    2.317392] usb 2-1.4: new full-speed USB device number 3 using ehci-pci
Sep 13 18:09:41 node-4 kernel: [    2.326851] rtc_cmos 00:02: RTC can wake from S4
Sep 13 18:09:41 node-4 kernel: [    2.332603] rtc_cmos 00:02: rtc core: registered rtc_cmos as rtc0
Sep 13 18:09:41 node-4 kernel: [    2.338232] rtc_cmos 00:02: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
Sep 13 18:09:41 node-4 kernel: [    2.349320] device-mapper: uevent: version 1.0.3
Sep 13 18:09:41 node-4 kernel: [    2.354955] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-devel@redhat.com
Sep 13 18:09:41 node-4 kernel: [    2.366163] ledtrig-cpu: registered to indicate activity on CPUs
Sep 13 18:09:41 node-4 kernel: [    2.372082] TCP: cubic registered
Sep 13 18:09:41 node-4 kernel: [    2.377966] NET: Registered protocol family 10
Sep 13 18:09:41 node-4 kernel: [    2.383935] NET: Registered protocol family 17
Sep 13 18:09:41 node-4 kernel: [    2.389612] Key type dns_resolver registered
Sep 13 18:09:41 node-4 kernel: [    2.395562] Loading compiled-in X.509 certificates
Sep 13 18:09:41 node-4 kernel: [    2.401722] Loaded X.509 cert 'Magrathea: Glacier signing key: 51d5d773f107ba1bc09d336838c43cde749e4e05'
Sep 13 18:09:41 node-4 kernel: [    2.413097] registered taskstats version 1
Sep 13 18:09:41 node-4 kernel: [    2.420993] Key type trusted registered
Sep 13 18:09:41 node-4 kernel: [    2.428560] Key type encrypted registered
Sep 13 18:09:41 node-4 kernel: [    2.434010] AppArmor: AppArmor sha1 policy hashing enabled
Sep 13 18:09:41 node-4 kernel: [    2.439491] IMA: No TPM chip found, activating TPM-bypass!
Sep 13 18:09:41 node-4 kernel: [    2.445638] regulator-dummy: disabling
Sep 13 18:09:41 node-4 kernel: [    2.450068] usb 2-1.4: New USB device found, idVendor=0624, idProduct=0402
Sep 13 18:09:41 node-4 kernel: [    2.450069] usb 2-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep 13 18:09:41 node-4 kernel: [    2.450070] usb 2-1.4: Product: Cisco USB Composite Device-0
Sep 13 18:09:41 node-4 kernel: [    2.450070] usb 2-1.4: Manufacturer: Avocent
Sep 13 18:09:41 node-4 kernel: [    2.450071] usb 2-1.4: SerialNumber: 20111102-00000001
Sep 13 18:09:41 node-4 kernel: [    2.484768]   Magic number: 0:521:190
Sep 13 18:09:41 node-4 kernel: [    2.490468] acpi device:49: hash matches
Sep 13 18:09:41 node-4 kernel: [    2.495930] acpi device:1c: hash matches
Sep 13 18:09:41 node-4 kernel: [    2.501374] rtc_cmos 00:02: setting system clock to 2016-09-13 18:09:07 UTC (1473790147)
Sep 13 18:09:41 node-4 kernel: [    2.513533] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
Sep 13 18:09:41 node-4 kernel: [    2.519013] EDD information not available.
Sep 13 18:09:41 node-4 kernel: [    2.524447] PM: Hibernation image not present or could not be loaded.
Sep 13 18:09:41 node-4 kernel: [    2.525311] Freeing unused kernel memory: 1336K (ffffffff81d20000 - ffffffff81e6e000)
Sep 13 18:09:41 node-4 kernel: [    2.536248] Write protecting the kernel read-only data: 12288k
Sep 13 18:09:41 node-4 kernel: [    2.542221] Freeing unused kernel memory: 760K (ffff880001742000 - ffff880001800000)
Sep 13 18:09:41 node-4 kernel: [    2.554340] Freeing unused kernel memory: 680K (ffff880001b56000 - ffff880001c00000)
Sep 13 18:09:41 node-4 kernel: [    2.586498] device-mapper: multipath: version 1.6.0 loaded
Sep 13 18:09:41 node-4 kernel: [    2.594343] systemd-udevd[215]: starting version 204
Sep 13 18:09:41 node-4 kernel: [    2.615257] md: linear personality registered for level -1
Sep 13 18:09:41 node-4 kernel: [    2.629760] md: multipath personality registered for level -4
Sep 13 18:09:41 node-4 kernel: [    2.637728] md: raid0 personality registered for level 0
Sep 13 18:09:41 node-4 kernel: [    2.646074] md: raid1 personality registered for level 1
Sep 13 18:09:41 node-4 kernel: [    2.656494] megasas: 06.700.06.00-rc1 Sat. Aug. 31 17:00:00 PDT 2013
Sep 13 18:09:41 node-4 kernel: [    2.662712] enic: Cisco VIC Ethernet NIC Driver, ver 2.1.1.50
Sep 13 18:09:41 node-4 kernel: [    2.662718] megasas: 0x1000:0x005d:0x1137:0x0124: bus 1:slot 0:func 0
Sep 13 18:09:41 node-4 kernel: [    2.663361] megasas: FW now in Ready state
Sep 13 18:09:41 node-4 kernel: [    2.663417] megaraid_sas 0000:01:00.0: irq 96 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663452] megaraid_sas 0000:01:00.0: irq 97 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663485] megaraid_sas 0000:01:00.0: irq 98 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663521] megaraid_sas 0000:01:00.0: irq 99 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663559] megaraid_sas 0000:01:00.0: irq 100 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663598] megaraid_sas 0000:01:00.0: irq 101 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663602] megaraid_sas 0000:01:00.0: irq 102 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663641] megaraid_sas 0000:01:00.0: irq 103 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663672] megaraid_sas 0000:01:00.0: irq 104 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663709] megaraid_sas 0000:01:00.0: irq 105 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663748] megaraid_sas 0000:01:00.0: irq 106 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663785] megaraid_sas 0000:01:00.0: irq 107 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663822] megaraid_sas 0000:01:00.0: irq 108 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663859] megaraid_sas 0000:01:00.0: irq 109 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663892] megaraid_sas 0000:01:00.0: irq 110 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.663930] megaraid_sas 0000:01:00.0: irq 111 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.664106] megaraid_sas 0000:01:00.0: [scsi0]: FW supports<96> MSIX vector,Online CPUs: <16>,Current MSIX <16>
Sep 13 18:09:41 node-4 kernel: [    2.693440] hidraw: raw HID events driver (C) Jiri Kosina
Sep 13 18:09:41 node-4 kernel: [    2.702146] enic 0000:06:00.0: vNIC MAC addr 00:25:b5:a0:00:4a wq/rq 256/512 mtu 1500
Sep 13 18:09:41 node-4 kernel: [    2.715004] 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
Sep 13 18:09:41 node-4 kernel: [    2.721193] raid6: sse2x1    8097 MB/s
Sep 13 18:09:41 node-4 kernel: [    2.735394] enic 0000:06:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 18:09:41 node-4 kernel: [    2.742261] enic 0000:06:00.0: irq 112 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.742266] enic 0000:06:00.0: irq 113 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.742270] enic 0000:06:00.0: irq 114 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.742274] enic 0000:06:00.0: irq 115 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.742311] enic 0000:06:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 18:09:41 node-4 kernel: [    2.756971] usbcore: registered new interface driver usbhid
Sep 13 18:09:41 node-4 kernel: [    2.763662] usbhid: USB HID core driver
Sep 13 18:09:41 node-4 kernel: [    2.771046] enic 0000:07:00.0: vNIC MAC addr 00:25:b5:a0:00:4b wq/rq 256/512 mtu 1500
Sep 13 18:09:41 node-4 kernel: [    2.784132] 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
Sep 13 18:09:41 node-4 kernel: [    2.789164] raid6: sse2x2    1129 MB/s
Sep 13 18:09:41 node-4 kernel: [    2.804005] enic 0000:07:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 18:09:41 node-4 kernel: [    2.856830] raid6: sse2x4    7733 MB/s
Sep 13 18:09:41 node-4 kernel: [    2.928770] raid6: avx2x1   14947 MB/s
Sep 13 18:09:41 node-4 kernel: [    3.000711] raid6: avx2x2   18916 MB/s
Sep 13 18:09:41 node-4 kernel: [    3.072652] raid6: avx2x4   21371 MB/s
Sep 13 18:09:41 node-4 kernel: [    3.078700] raid6: using algorithm avx2x4 (21371 MB/s)
Sep 13 18:09:41 node-4 kernel: [    3.084771] raid6: using avx2x2 recovery algorithm
Sep 13 18:09:41 node-4 kernel: [    3.090937] megasas:IOC Init cmd success
Sep 13 18:09:41 node-4 kernel: [    3.090940] Switched to clocksource tsc
Sep 13 18:09:41 node-4 kernel: [    3.102978] enic 0000:07:00.0: irq 116 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.102985] enic 0000:07:00.0: irq 117 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.102988] enic 0000:07:00.0: irq 118 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.102992] enic 0000:07:00.0: irq 119 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.103050] enic 0000:07:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.115242] xor: automatically using best checksumming function:
Sep 13 18:09:41 node-4 kernel: [    3.121509] 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
Sep 13 18:09:41 node-4 kernel: [    3.124430] enic 0000:08:00.0: vNIC MAC addr 00:25:b5:a0:00:4c wq/rq 256/512 mtu 1500
Sep 13 18:09:41 node-4 kernel: [    3.124454] 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
Sep 13 18:09:41 node-4 kernel: [    3.124481] enic 0000:08:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 18:09:41 node-4 kernel: [    3.124949] enic 0000:08:00.0: irq 120 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.125049] enic 0000:08:00.0: irq 121 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.125150] enic 0000:08:00.0: irq 122 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.125260] enic 0000:08:00.0: irq 123 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.125579] enic 0000:08:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.137586] enic 0000:09:00.0: vNIC MAC addr 00:25:b5:a0:00:4d wq/rq 256/512 mtu 1500
Sep 13 18:09:41 node-4 kernel: [    3.137599] 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
Sep 13 18:09:41 node-4 kernel: [    3.137617] enic 0000:09:00.0: vNIC resources avail: wq 1 rq 1 cq 2 intr 4
Sep 13 18:09:41 node-4 kernel: [    3.137850] megasas: INIT adapter done
Sep 13 18:09:41 node-4 kernel: [    3.138099] enic 0000:09:00.0: irq 124 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.138156] enic 0000:09:00.0: irq 125 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.138240] enic 0000:09:00.0: irq 126 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.138336] enic 0000:09:00.0: irq 127 for MSI/MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.138571] enic 0000:09:00.0: vNIC resources used:  wq 1 rq 1 cq 2 intr 4 intr mode MSI-X
Sep 13 18:09:41 node-4 kernel: [    3.160572]    avx       : 36446.000 MB/sec
Sep 13 18:09:41 node-4 kernel: [    3.208787] megaraid_sas 0000:01:00.0: Controller type: iMR
Sep 13 18:09:41 node-4 kernel: [    3.210746] scsi0 : LSI SAS based MegaRAID driver
Sep 13 18:09:41 node-4 kernel: [    3.217984] scsi 0:0:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 13 18:09:41 node-4 kernel: [    3.259799] 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
Sep 13 18:09:41 node-4 kernel: [    3.273669] async_tx: api initialized (async)
Sep 13 18:09:41 node-4 kernel: [    3.273708] 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
Sep 13 18:09:41 node-4 kernel: [    3.273776] 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
Sep 13 18:09:41 node-4 kernel: [    3.273847] 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
Sep 13 18:09:41 node-4 kernel: [    3.273910] 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
Sep 13 18:09:41 node-4 kernel: [    3.279114] scsi 0:2:0:0: Direct-Access     LSI      UCSB-MRAID12G    4.25 PQ: 0 ANSI: 5
Sep 13 18:09:41 node-4 kernel: [    3.283150] sd 0:2:0:0: Attached scsi generic sg0 type 0
Sep 13 18:09:41 node-4 kernel: [    3.283256] sd 0:2:0:0: [sda] 4683591680 512-byte logical blocks: (2.39 TB/2.18 TiB)
Sep 13 18:09:41 node-4 kernel: [    3.283563] sd 0:2:0:0: [sda] Write Protect is off
Sep 13 18:09:41 node-4 kernel: [    3.283564] sd 0:2:0:0: [sda] Mode Sense: 1f 00 10 08
Sep 13 18:09:41 node-4 kernel: [    3.283633] sd 0:2:0:0: [sda] Write cache: disabled, read cache: disabled, supports DPO and FUA
Sep 13 18:09:41 node-4 kernel: [    3.310887]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10
Sep 13 18:09:41 node-4 kernel: [    3.311464] sd 0:2:0:0: [sda] Attached SCSI disk
Sep 13 18:09:41 node-4 kernel: [    3.415441] md: raid6 personality registered for level 6
Sep 13 18:09:41 node-4 kernel: [    3.422527] md: raid5 personality registered for level 5
Sep 13 18:09:41 node-4 kernel: [    3.429423] md: raid4 personality registered for level 4
Sep 13 18:09:41 node-4 kernel: [    3.433012] random: lvm urandom read with 25 bits of entropy available
Sep 13 18:09:41 node-4 kernel: [    3.446056] md: raid10 personality registered for level 10
Sep 13 18:09:41 node-4 kernel: [    3.502159] multipathd (371): /proc/371/oom_adj is deprecated, please use /proc/371/oom_score_adj instead.
Sep 13 18:09:41 node-4 kernel: [    3.563142] bio: create slab <bio-1> at 1
Sep 13 18:09:41 node-4 kernel: [    4.321365] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 18:09:41 node-4 kernel: [    4.841753] init: plymouth-upstart-bridge main process (555) terminated with status 1
Sep 13 18:09:41 node-4 kernel: [    4.854130] init: plymouth-upstart-bridge main process ended, respawning
Sep 13 18:09:41 node-4 kernel: [    5.007062] EXT4-fs (dm-4): re-mounted. Opts: errors=panic
Sep 13 18:09:41 node-4 kernel: [    5.046451] Adding 16777212k swap on /dev/mapper/os-swap.  Priority:-1 extents:1 across:16777212k FS
Sep 13 18:09:41 node-4 kernel: [    5.196159] random: nonblocking pool is initialized
Sep 13 18:09:41 node-4 kernel: [    5.202843] EXT4-fs (sda3): mounting ext2 file system using the ext4 subsystem
Sep 13 18:09:41 node-4 kernel: [    5.291688] EXT4-fs (sda3): mounted filesystem without journal. Opts: (null)
Sep 13 18:09:41 node-4 kernel: [    5.390905] EXT4-fs (dm-3): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 18:09:41 node-4 kernel: [    5.603319] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled
Sep 13 18:09:41 node-4 kernel: [    5.640420] XFS (dm-0): Mounting Filesystem
Sep 13 18:09:41 node-4 kernel: [    5.810227] XFS (dm-0): Ending clean mount
Sep 13 18:09:41 node-4 kernel: [    5.851839] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 18:09:41 node-4 kernel: [    5.897781] XFS (dm-1): Mounting Filesystem
Sep 13 18:09:41 node-4 kernel: [    6.064030] XFS (dm-1): Ending clean mount
Sep 13 18:09:41 node-4 kernel: [    7.955316] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 13 18:09:41 node-4 kernel: [    7.969349] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 13 18:09:41 node-4 kernel: [    8.156089] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
Sep 13 18:09:41 node-4 kernel: [    8.156094] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
Sep 13 18:09:41 node-4 kernel: [    8.156098] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 13 18:09:41 node-4 kernel: [    8.156102] IPv6: ADDRCONF(NETDEV_UP): eth3: link is not ready
Sep 13 18:09:41 node-4 kernel: [    8.187294] systemd-udevd[780]: starting version 204
Sep 13 18:09:41 node-4 kernel: [    8.424636] power_meter ACPI000D:00: Found ACPI power meter.
Sep 13 18:09:41 node-4 kernel: [    8.424662] power_meter ACPI000D:00: Ignoring unsafe software power cap!
Sep 13 18:09:41 node-4 kernel: [    8.435903] wmi: Mapper loaded
Sep 13 18:09:41 node-4 kernel: [    8.438243] IPMI System Interface driver.
Sep 13 18:09:41 node-4 kernel: [    8.438311] ipmi_si: probing via ACPI
Sep 13 18:09:41 node-4 kernel: [    8.438323] ipmi_si 00:09: [io  0x0ca2] regsize 1 spacing 1 irq 0
Sep 13 18:09:41 node-4 kernel: [    8.438324] ipmi_si: Adding ACPI-specified kcs state machine
Sep 13 18:09:41 node-4 kernel: [    8.438336] ipmi_si: probing via SMBIOS
Sep 13 18:09:41 node-4 kernel: [    8.438337] ipmi_si: SMBIOS: io 0xca2 regsize 1 spacing 1 irq 0
Sep 13 18:09:41 node-4 kernel: [    8.438338] ipmi_si: Adding SMBIOS-specified kcs state machine duplicate interface
Sep 13 18:09:41 node-4 kernel: [    8.438339] ipmi_si: probing via SPMI
Sep 13 18:09:41 node-4 kernel: [    8.438340] ipmi_si: SPMI: io 0xca2 regsize 1 spacing 1 irq 0
Sep 13 18:09:41 node-4 kernel: [    8.438341] ipmi_si: Adding SPMI-specified kcs state machine duplicate interface
Sep 13 18:09:41 node-4 kernel: [    8.438342] ipmi_si: Trying ACPI-specified kcs state machine at i/o address 0xca2, slave address 0x0, irq 0
Sep 13 18:09:41 node-4 kernel: [    8.439689] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \GPE0 1 (20131115/utaddress-251)
Sep 13 18:09:41 node-4 kernel: [    8.439694] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 13 18:09:41 node-4 kernel: [    8.439697] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIV 1 (20131115/utaddress-251)
Sep 13 18:09:41 node-4 kernel: [    8.439699] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Sep 13 18:09:41 node-4 kernel: [    8.439734] lpc_ich: Resource conflict(s) found affecting gpio_ich
Sep 13 18:09:41 node-4 kernel: [    8.452966] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Sep 13 18:09:41 node-4 kernel: [    8.524515] systemd-udevd[809]: renamed network interface eth1 to enp7s0
Sep 13 18:09:41 node-4 kernel: [    8.540416] systemd-udevd[828]: renamed network interface eth2 to enp8s0
Sep 13 18:09:41 node-4 kernel: [    8.568387] systemd-udevd[802]: renamed network interface eth0 to enp6s0
Sep 13 18:09:41 node-4 kernel: [    8.580319] ipmi_si 00:09: Found new BMC (man_id: 0x00168b, prod_id: 0x0018, dev_id: 0x20)
Sep 13 18:09:41 node-4 kernel: [    8.580325] ipmi_si 00:09: IPMI kcs interface initialized
Sep 13 18:09:41 node-4 kernel: [    8.596353] systemd-udevd[799]: renamed network interface eth3 to enp9s0
Sep 13 18:09:41 node-4 kernel: [    8.941132] type=1400 audit(1473790153.939:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/sbin/dhclient" pid=1058 comm="apparmor_parser"
Sep 13 18:09:41 node-4 kernel: [    8.941290] type=1400 audit(1473790153.939:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1058 comm="apparmor_parser"
Sep 13 18:09:41 node-4 kernel: [    8.941389] type=1400 audit(1473790153.939:4): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1060 comm="apparmor_parser"
Sep 13 18:09:41 node-4 kernel: [    8.941415] type=1400 audit(1473790153.939:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1058 comm="apparmor_parser"
Sep 13 18:09:41 node-4 kernel: [    8.941543] type=1400 audit(1473790153.939:6): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1060 comm="apparmor_parser"
Sep 13 18:09:41 node-4 kernel: [    8.941670] type=1400 audit(1473790153.939:7): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1060 comm="apparmor_parser"
Sep 13 18:09:41 node-4 kernel: [    8.950025] type=1400 audit(1473790153.947:8): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1056 comm="apparmor_parser"
Sep 13 18:09:41 node-4 kernel: [    8.950165] type=1400 audit(1473790153.947:9): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1056 comm="apparmor_parser"
Sep 13 18:09:41 node-4 kernel: [    8.950288] type=1400 audit(1473790153.947:10): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=1056 comm="apparmor_parser"
Sep 13 18:09:41 node-4 kernel: [    8.950626] type=1400 audit(1473790153.947:11): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=1057 comm="apparmor_parser"
Sep 13 18:09:41 node-4 kernel: [    9.570847] EXT4-fs (sda10): mounting ext2 file system using the ext4 subsystem
Sep 13 18:09:41 node-4 kernel: [    9.571733] EXT4-fs (sda10): mounted filesystem without journal. Opts: (null)
Sep 13 18:09:41 node-4 kernel: [    9.763399] enic 0000:06:00.0 enp6s0: Link UP
Sep 13 18:09:41 node-4 kernel: [    9.763920] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
Sep 13 18:09:41 node-4 kernel: [    9.763926] IPv6: ADDRCONF(NETDEV_CHANGE): enp6s0: link becomes ready
Sep 13 18:09:41 node-4 kernel: [   19.290890] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
Sep 13 18:09:42 node-4 failsafe: Failsafe of 120 seconds reached.
Sep 13 18:09:42 node-4 kernel: [   36.950049] init: failsafe main process (8411) killed by TERM signal
Sep 13 18:09:43 node-4 dbus[8448]: [system] AppArmor D-Bus mediation is enabled
Sep 13 18:09:43 node-4 kernel: [   37.235843] audit_printk_skb: 30 callbacks suppressed
Sep 13 18:09:43 node-4 kernel: [   37.235844] type=1400 audit(1473790183.190:22): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/ntpd" pid=8539 comm="apparmor_parser"
Sep 13 18:09:43 node-4 kernel: [   37.239890] type=1400 audit(1473790183.194:23): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/sbin/dhclient" pid=8538 comm="apparmor_parser"
Sep 13 18:09:43 node-4 kernel: [   37.239895] type=1400 audit(1473790183.194:24): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8538 comm="apparmor_parser"
Sep 13 18:09:43 node-4 kernel: [   37.239898] type=1400 audit(1473790183.194:25): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Sep 13 18:09:43 node-4 kernel: [   37.240114] type=1400 audit(1473790183.194:26): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=8538 comm="apparmor_parser"
Sep 13 18:09:43 node-4 kernel: [   37.240116] type=1400 audit(1473790183.194:27): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Sep 13 18:09:43 node-4 kernel: [   37.240229] type=1400 audit(1473790183.194:28): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/connman/scripts/dhclient-script" pid=8538 comm="apparmor_parser"
Sep 13 18:09:43 node-4 kernel: [   37.321146] type=1400 audit(1473790183.274:29): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=8541 comm="apparmor_parser"
Sep 13 18:09:43 node-4 anacron[8591]: Anacron 2.3 started on 2016-09-13
Sep 13 18:09:43 node-4 cron[8569]: (CRON) INFO (pidfile fd = 3)
Sep 13 18:09:43 node-4 cron[8609]: (CRON) STARTUP (fork ok)
Sep 13 18:09:43 node-4 anacron[8591]: Will run job `cron.daily' in 5 min.
Sep 13 18:09:43 node-4 anacron[8591]: Will run job `cron.weekly' in 10 min.
Sep 13 18:09:43 node-4 anacron[8591]: Will run job `cron.monthly' in 15 min.
Sep 13 18:09:43 node-4 anacron[8591]: Jobs will be executed sequentially
Sep 13 18:09:43 node-4 multipathd: path checkers start up
Sep 13 18:09:43 node-4 cron[8609]: (CRON) INFO (Running @reboot jobs)
Sep 13 18:09:43 node-4 postfix/master[8748]: daemon started -- version 2.11.0, configuration /etc/postfix
Sep 13 18:09:47 node-4 puppet-agent[8932]: Reopening log files
Sep 13 18:09:47 node-4 puppet-agent[8932]: Could not request certificate: Connection refused - connect(2)
Sep 13 18:10:01 node-4 CRON[9092]: (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")
Sep 13 18:10:03 node-4 puppet-user[9151]: (Scope(Class[main])) MODULAR: rsync_core_puppet
Sep 13 18:10:03 node-4 puppet-user[9151]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Sep 13 18:10:04 node-4 puppet-user[9151]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) skipping non-regular file "osnailyfacter/modular/master"
Sep 13 18:10:04 node-4 puppet-user[9151]: (/Stage[main]/Main/Exec[rsync_core_puppet_shell]/returns) executed successfully
Sep 13 18:10:04 node-4 puppet-user[9151]: Finished catalog run in 0.46 seconds
Sep 13 18:10:05 node-4 multipathd: uevent trigger error
Sep 13 18:10:06 node-4 puppet-user[9591]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 13 18:10:06 node-4 puppet-user[9591]: Compiled catalog for node-4.domain.tld in environment production in 0.09 seconds
Sep 13 18:10:06 node-4 puppet-user[9591]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/ensure) created
Sep 13 18:10:06 node-4 puppet-user[9591]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/data_dir) data_dir changed '' to '/etc/hiera'
Sep 13 18:10:06 node-4 puppet-user[9591]: (/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"]'
Sep 13 18:10:06 node-4 puppet-user[9591]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/logger) logger changed '' to 'noop'
Sep 13 18:10:06 node-4 puppet-user[9591]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/merge_behavior) merge_behavior changed '' to 'deeper'
Sep 13 18:10:06 node-4 puppet-user[9591]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_puppet_config]/ensure) ensure changed 'file' to 'link'
Sep 13 18:10:06 node-4 puppet-user[9591]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_astute]/ensure) created
Sep 13 18:10:06 node-4 puppet-user[9591]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_override_dir]/ensure) created
Sep 13 18:10:06 node-4 puppet-user[9591]: Finished catalog run in 0.06 seconds
Sep 13 18:10:07 node-4 puppet-user[10061]: (Scope(Class[Osnailyfacter::Hiera::Override_configuration])) MODULAR: hiera/override_configuration.pp
Sep 13 18:10:07 node-4 puppet-user[10061]: Compiled catalog for node-4.domain.tld in environment production in 0.07 seconds
Sep 13 18:10:07 node-4 puppet-user[10061]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override]/ensure) created
Sep 13 18:10:07 node-4 puppet-user[10061]: (/Stage[main]/Osnailyfacter::Hiera::Override_configuration/File[/etc/hiera/override/configuration]/ensure) created
Sep 13 18:10:07 node-4 puppet-user[10061]: Finished catalog run in 0.03 seconds
Sep 13 18:10:09 node-4 puppet-user[10533]: (Scope(Class[main])) MODULAR: configuration_symlink
Sep 13 18:10:09 node-4 puppet-user[10533]: Compiled catalog for node-4.domain.tld in environment production in 0.03 seconds
Sep 13 18:10:09 node-4 puppet-user[10533]: (/Stage[main]/Main/Exec[configuration_symlink_shell]/returns) executed successfully
Sep 13 18:10:09 node-4 puppet-user[10533]: Finished catalog run in 0.03 seconds
Sep 13 18:10:10 node-4 puppet-user[11178]: (Scope(Class[Osnailyfacter::Plugins::Plugins_rsync])) MODULAR: plugins/plugins_rsync.pp
Sep 13 18:10:10 node-4 puppet-user[11178]: Compiled catalog for node-4.domain.tld in environment production in 0.18 seconds
Sep 13 18:10:10 node-4 puppet-user[11178]: (/Stage[main]/Osnailyfacter::Plugins::Plugins_rsync/File[/etc/fuel/plugins/]/ensure) created
Sep 13 18:10:11 node-4 puppet-user[11178]: (/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
Sep 13 18:10:11 node-4 puppet-user[11178]: (/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
Sep 13 18:10:11 node-4 puppet-user[11178]: Finished catalog run in 0.79 seconds
Sep 13 18:10:12 node-4 puppet-user[11694]: (Scope(Class[Osnailyfacter::Plugins::Plugins_setup_repositories])) MODULAR: plugins/plugins_setup_repositories.pp
Sep 13 18:10:13 node-4 puppet-user[11694]: Compiled catalog for node-4.domain.tld in environment production in 0.21 seconds
Sep 13 18:10:13 node-4 puppet-user[11694]: (/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
Sep 13 18:10:13 node-4 puppet-user[11694]: (/Stage[main]/Apt/Apt::Setting[conf-update-stamp]/File[/etc/apt/apt.conf.d/15update-stamp]/ensure) defined content as '{md5}0962d70c4ec78bbfa6f3544ae0c41974'
Sep 13 18:10:13 node-4 puppet-user[11694]: (/Stage[main]/Apt/File[preferences]/ensure) created
Sep 13 18:10:13 node-4 puppet-user[11694]: (/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
Sep 13 18:10:13 node-4 puppet-user[11694]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 1 events
Sep 13 18:10:13 node-4 puppet-user[11694]: Finished catalog run in 0.29 seconds
Sep 13 18:10:14 node-4 puppet-user[12181]: (Scope(Class[Osnailyfacter::Netconfig::Reserved_ports])) MODULAR: netconfig/reserved_ports.pp
Sep 13 18:10:14 node-4 puppet-user[12181]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Sep 13 18:10:14 node-4 puppet-user[12181]: (/Stage[main]/Openstack::Reserved_ports/Sysctl::Value[net.ipv4.ip_local_reserved_ports]/Sysctl[net.ipv4.ip_local_reserved_ports]/ensure) created
Sep 13 18:10:15 node-4 kernel: [   69.013094] nr_pdflush_threads exported in /proc is scheduled for removal
Sep 13 18:10:15 node-4 kernel: [   69.013146] 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.
Sep 13 18:10:15 node-4 puppet-user[12181]: (/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'
Sep 13 18:10:15 node-4 puppet-user[12181]: Finished catalog run in 0.06 seconds
Sep 13 18:10:16 node-4 puppet-user[12642]: (Scope(Class[main])) MODULAR: sync_time
Sep 13 18:10:16 node-4 puppet-user[12642]: Compiled catalog for node-4.domain.tld in environment production in 0.02 seconds
Sep 13 18:10:16 node-4 ntpdate[13062]: ntpdate 4.2.6p5@1.2349-o Thu Feb 11 18:30:41 UTC 2016 (1)
Sep 13 18:10:21 node-4 kernel: [   75.383177] init: plymouth-upstart-bridge main process ended, respawning
Sep 13 18:10:21 node-4 puppet-agent[8932]: Could not run: SIGTERM
Sep 13 18:10:21 node-4 kernel: [   75.665567] ip_tables: (C) 2000-2006 Netfilter Core Team
Sep 13 18:10:21 node-4 ec2: 
Sep 13 18:10:21 node-4 ec2: #############################################################
Sep 13 18:10:21 node-4 ec2: -----BEGIN SSH HOST KEY FINGERPRINTS-----
Sep 13 18:10:21 node-4 ec2: 1024 f7:90:bd:ff:4a:4d:75:e0:23:da:e7:e8:2f:f7:5e:b7  root@node-4.domain.tld (DSA)
Sep 13 18:10:21 node-4 ec2: 256 49:ff:f4:39:80:60:47:eb:68:ef:f0:01:da:8c:82:80  root@node-4.domain.tld (ECDSA)
Sep 13 18:10:21 node-4 ec2: 256 d1:3a:ae:24:bd:37:d6:64:b2:dc:ff:1c:17:09:23:85  root@node-4.domain.tld (ED25519)
Sep 13 18:10:21 node-4 ec2: 2048 f4:c6:e9:a0:74:ca:c9:13:0e:ac:b2:67:a3:8c:f6:c4  root@node-4.domain.tld (RSA)
Sep 13 18:10:21 node-4 ec2: -----END SSH HOST KEY FINGERPRINTS-----
Sep 13 18:10:21 node-4 ec2: #############################################################
Sep 13 18:10:22 node-4 ntpdate[13062]: adjust time server 10.20.0.2 offset -0.467466 sec
Sep 13 18:10:22 node-4 puppet-user[12642]: (/Stage[main]/Main/Exec[sync_time_shell]/returns) executed successfully
Sep 13 18:10:22 node-4 puppet-user[12642]: Finished catalog run in 6.16 seconds
Sep 13 18:10:28 node-4 puppet-user[13440]: (Scope(Class[Osnailyfacter::Hiera::Hiera])) MODULAR: hiera/hiera.pp
Sep 13 18:10:29 node-4 puppet-user[13440]: Compiled catalog for node-4.domain.tld in environment production in 0.10 seconds
Sep 13 18:10:29 node-4 puppet-user[13440]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/File[hiera_data_dir]/mode) mode changed '0700' to '0755'
Sep 13 18:10:29 node-4 puppet-user[13440]: (/Stage[main]/Osnailyfacter::Hiera::Hiera/Hiera_config[/etc/hiera.yaml]/hierarchy_override) hierarchy_override changed '[]' to '["plugins/fuel-plugin-ovs", "plugins/opendaylight"]'
Sep 13 18:10:29 node-4 puppet-user[13440]: Finished catalog run in 0.07 seconds
Sep 13 18:10:30 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 18:10:30 node-4 nailgun-agent: D, [2016-09-13T18:10:01.673853 #9095] DEBUG -- : Sleep for 29 seconds before sending request
Sep 13 18:10:30 node-4 nailgun-agent: I, [2016-09-13T18:10:30.688688 #9095]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 13 18:10:30 node-4 puppet-user[13911]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Setup_repositories])) MODULAR: fuel_pkgs/setup_repositories.pp
Sep 13 18:10:31 node-4 nailgun-agent: D, [2016-09-13T18:10:31.127166 #9095] DEBUG -- : Trying to put host info into https://10.20.0.2:8443/api
Sep 13 18:10:31 node-4 puppet-user[13911]: Compiled catalog for node-4.domain.tld in environment production in 1.21 seconds
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[mos]/Apt::Setting[pref-mos]/File[/etc/apt/preferences.d/mos.pref]/ensure) created
Sep 13 18:10:32 node-4 puppet-user[13911]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[mos]/Apt::Setting[list-mos]/File[/etc/apt/sources.list.d/mos.list]/ensure) created
Sep 13 18:10:32 node-4 puppet-user[13911]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Pin[Auxiliary]/Apt::Setting[pref-Auxiliary]/File[/etc/apt/preferences.d/Auxiliary.pref]/ensure) created
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[ubuntu]/Apt::Setting[list-ubuntu]/File[/etc/apt/sources.list.d/ubuntu.list]/ensure) created
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/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
Sep 13 18:10:32 node-4 puppet-user[13911]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Setup_repositories/Apt::Source[Auxiliary]/Apt::Setting[list-Auxiliary]/File[/etc/apt/sources.list.d/Auxiliary.list]/ensure) created
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.111324 #9095] DEBUG -- : Trying to find block devices
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.111428 #9095] DEBUG -- : Found block device: sda
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.111472 #9095] DEBUG -- : Block device info: {"size"=>"4683591680", "removable"=>"0", "model"=>"UCSB-MRAID12G", "rev"=>"4.25", "state"=>"running", "timeout"=>"90", "vendor"=>"LSI"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.111540 #9095] DEBUG -- : Trying to get list of physical devices
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.111690 #9095] DEBUG -- : Getting udev properties for device: sda
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.113715 #9095] DEBUG -- : Device sda udev properties: {"DEVLINKS"=>"/dev/disk/by-id/scsi-3618e72837273a7701cc7886005a67804 /dev/disk/by-id/wwn-0x618e72837273a7701cc7886005a67804 /dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", "DEVNAME"=>"/dev/sda", "DEVPATH"=>"/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:2:0/0:2:0:0/block/sda", "DEVTYPE"=>"disk", "ID_BUS"=>"scsi", "ID_MODEL"=>"UCSB-MRAID12G", "ID_MODEL_ENC"=>"UCSB-MRAID12G\\x20\\x20\\x20", "ID_PART_TABLE_TYPE"=>"gpt", "ID_PATH"=>"pci-0000:01:00.0-scsi-0:2:0:0", "ID_PATH_TAG"=>"pci-0000_01_00_0-scsi-0_2_0_0", "ID_REVISION"=>"4.25", "ID_SCSI"=>"1", "ID_SCSI_SERIAL"=>"000478a6056088c71c70a7737283728e", "ID_SERIAL"=>"3618e72837273a7701cc7886005a67804", "ID_SERIAL_SHORT"=>"618e72837273a7701cc7886005a67804", "ID_TYPE"=>"disk", "ID_VENDOR"=>"LSI", "ID_VENDOR_ENC"=>"LSI\\x20\\x20\\x20\\x20\\x20", "ID_WWN"=>"0x618e72837273a770", "ID_WWN_VENDOR_EXTENSION"=>"0x1cc7886005a67804", "ID_WWN_WITH_EXTENSION"=>"0x618e72837273a7701cc7886
Sep 13 18:10:43 node-4 nailgun-agent: 005a67804", "MAJOR"=>"8", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"70692", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.113743 #9095] DEBUG -- : Trying to find out if device sda is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.113792 #9095] DEBUG -- : Device sda removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.113837 #9095] DEBUG -- : Device sda seems to be appropriate
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.114297 #9095] DEBUG -- : Getting udev properties for device: dm-0
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.115979 #9095] DEBUG -- : Device dm-0 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-image-glance /dev/disk/by-id/dm-uuid-LVM-9cXzcJ4b3YWx6rkKRQHCi1eQQF2fVR8HA1euaLcAMDftOWiLiwIZ0BglQjqYpbrU /dev/disk/by-uuid/8991bfc0-8fa9-4b47-9c50-149fc0aa3feb /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-9cXzcJ4b3YWx6rkKRQHCi1eQQF2fVR8HA1euaLcAMDftOWiLiwIZ0BglQjqYpbrU", "DM_VG_NAME"=>"image", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"8991bfc0-8fa9-4b47-9c50-149fc0aa3feb", "ID_FS_UUID_ENC"=>"8991bfc0-8fa9-4b47-9c50-149fc0aa3feb", "MAJOR"=>"252", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"22865", "nomdmonddf"=>"1", "nomd
Sep 13 18:10:43 node-4 nailgun-agent: monisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.116018 #9095] DEBUG -- : Trying to find out if device dm-0 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.116067 #9095] DEBUG -- : Device dm-0 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.116082 #9095] DEBUG -- : Device dm-0 seems to be appropriate
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.116098 #9095] DEBUG -- : Getting udev properties for device: dm-1
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.117784 #9095] DEBUG -- : Device dm-1 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-horizon-horizontmp /dev/disk/by-id/dm-uuid-LVM-u0Mmnts7mBi2AoXU93Q6X0PkM4PnCN2sR9leyLjPf0L3EMMmq7KoMBXgFQ7YpwB0 /dev/disk/by-uuid/f74f9341-7c1a-4684-9a88-8e312f703908 /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-u0Mmnts7mBi2AoXU93Q6X0PkM4PnCN2sR9leyLjPf0L3EMMmq7KoMBXgFQ7YpwB0", "DM_VG_NAME"=>"horizon", "ID_FS_TYPE"=>"xfs", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"f74f9341-7c1a-4684-9a88-8e312f703908", "ID_FS_UUID_ENC"=>"f74f9341-7c1a-4684-9a88-8e312f703908", "MAJOR"=>"252", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"38
Sep 13 18:10:43 node-4 nailgun-agent: 060", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.117827 #9095] DEBUG -- : Trying to find out if device dm-1 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.117884 #9095] DEBUG -- : Device dm-1 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.117899 #9095] DEBUG -- : Device dm-1 seems to be appropriate
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.117939 #9095] DEBUG -- : Getting udev properties for device: dm-2
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.119595 #9095] DEBUG -- : Device dm-2 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-mysql-root /dev/disk/by-id/dm-uuid-LVM-7prBlztBdqViAX8n6GeGMikDgo48aAXixUFRR2BNaLf19BKVf5DgMRlX4R69Wrq3 /dev/disk/by-uuid/cb983535-c761-4428-bf7e-c53f73e65d4d /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-7prBlztBdqViAX8n6GeGMikDgo48aAXixUFRR2BNaLf19BKVf5DgMRlX4R69Wrq3", "DM_VG_NAME"=>"mysql", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"cb983535-c761-4428-bf7e-c53f73e65d4d", "ID_FS_UUID_ENC"=>"cb983535-c761-4428-bf7e-c53f73e65d4d", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"49852", "nomdmond
Sep 13 18:10:43 node-4 nailgun-agent: df"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.119635 #9095] DEBUG -- : Trying to find out if device dm-2 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.119683 #9095] DEBUG -- : Device dm-2 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.119698 #9095] DEBUG -- : Device dm-2 seems to be appropriate
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.119714 #9095] DEBUG -- : Getting udev properties for device: dm-3
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.121399 #9095] DEBUG -- : Device dm-3 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-logs-log /dev/disk/by-id/dm-uuid-LVM-m3XeydOyEbGOBR2jeOpgG8GCoUJoImSizm0b7Jv6bL8NoUQB2lQx0eqFQokp458z /dev/disk/by-uuid/d9be9086-8635-4351-92d1-6d3b41e76fc2 /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-m3XeydOyEbGOBR2jeOpgG8GCoUJoImSizm0b7Jv6bL8NoUQB2lQx0eqFQokp458z", "DM_VG_NAME"=>"logs", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"d9be9086-8635-4351-92d1-6d3b41e76fc2", "ID_FS_UUID_ENC"=>"d9be9086-8635-4351-92d1-6d3b41e76fc2", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"61097", "nomdmonddf"=>"1", 
Sep 13 18:10:43 node-4 nailgun-agent: "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.121427 #9095] DEBUG -- : Trying to find out if device dm-3 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.121458 #9095] DEBUG -- : Device dm-3 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.121474 #9095] DEBUG -- : Device dm-3 seems to be appropriate
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.121506 #9095] DEBUG -- : Getting udev properties for device: dm-4
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.123143 #9095] DEBUG -- : Device dm-4 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-root /dev/disk/by-id/dm-uuid-LVM-c0FjIfZceoTUANZHZI4Qxafp5l7O35gvyjZTBXdz6SNFBhnX9iYbEuiRsXI0263A /dev/disk/by-uuid/10c5969a-0bee-4214-8b38-01b49ebc4211 /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-c0FjIfZceoTUANZHZI4Qxafp5l7O35gvyjZTBXdz6SNFBhnX9iYbEuiRsXI0263A", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"ext4", "ID_FS_USAGE"=>"filesystem", "ID_FS_UUID"=>"10c5969a-0bee-4214-8b38-01b49ebc4211", "ID_FS_UUID_ENC"=>"10c5969a-0bee-4214-8b38-01b49ebc4211", "ID_FS_VERSION"=>"1.0", "MAJOR"=>"252", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79323", "nomdmonddf"=>"1", "nomd
Sep 13 18:10:43 node-4 nailgun-agent: monisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.123194 #9095] DEBUG -- : Trying to find out if device dm-4 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.123227 #9095] DEBUG -- : Device dm-4 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.123241 #9095] DEBUG -- : Device dm-4 seems to be appropriate
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.123265 #9095] DEBUG -- : Getting udev properties for device: dm-5
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.124962 #9095] DEBUG -- : Device dm-5 udev properties: {"DEVLINKS"=>"/dev/disk/by-id/dm-name-os-swap /dev/disk/by-id/dm-uuid-LVM-c0FjIfZceoTUANZHZI4Qxafp5l7O35gvotfWWNpz3WfZ52E0pDRLfFNrMtxOilBW /dev/disk/by-uuid/99c94040-ccbf-4990-8d51-774eb22d4bcb /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-c0FjIfZceoTUANZHZI4Qxafp5l7O35gvotfWWNpz3WfZ52E0pDRLfFNrMtxOilBW", "DM_VG_NAME"=>"os", "ID_FS_TYPE"=>"swap", "ID_FS_USAGE"=>"other", "ID_FS_UUID"=>"99c94040-ccbf-4990-8d51-774eb22d4bcb", "ID_FS_UUID_ENC"=>"99c94040-ccbf-4990-8d51-774eb22d4bcb", "ID_FS_VERSION"=>"2", "MAJOR"=>"252", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"79796", "nomdmonddf"=>"1", "nomdmonisw"
Sep 13 18:10:43 node-4 nailgun-agent: =>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.125008 #9095] DEBUG -- : Trying to find out if device dm-5 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.125052 #9095] DEBUG -- : Device dm-5 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.125079 #9095] DEBUG -- : Device dm-5 seems to be appropriate
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.125095 #9095] DEBUG -- : Getting udev properties for device: ram0
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.126607 #9095] DEBUG -- : Device ram0 udev properties: {"DEVNAME"=>"/dev/ram0", "DEVPATH"=>"/devices/virtual/block/ram0", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2923", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.126634 #9095] DEBUG -- : Trying to find out if device ram0 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.126683 #9095] DEBUG -- : Device ram0 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.126704 #9095] DEBUG -- : Getting udev properties for device: ram1
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.128243 #9095] DEBUG -- : Device ram1 udev properties: {"DEVNAME"=>"/dev/ram1", "DEVPATH"=>"/devices/virtual/block/ram1", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3067", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.128269 #9095] DEBUG -- : Trying to find out if device ram1 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.128309 #9095] DEBUG -- : Device ram1 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.128336 #9095] DEBUG -- : Getting udev properties for device: ram2
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.130260 #9095] DEBUG -- : Device ram2 udev properties: {"DEVNAME"=>"/dev/ram2", "DEVPATH"=>"/devices/virtual/block/ram2", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3666", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.130287 #9095] DEBUG -- : Trying to find out if device ram2 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.130326 #9095] DEBUG -- : Device ram2 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.130374 #9095] DEBUG -- : Getting udev properties for device: ram3
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.131877 #9095] DEBUG -- : Device ram3 udev properties: {"DEVNAME"=>"/dev/ram3", "DEVPATH"=>"/devices/virtual/block/ram3", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3731", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.131911 #9095] DEBUG -- : Trying to find out if device ram3 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.131953 #9095] DEBUG -- : Device ram3 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.131985 #9095] DEBUG -- : Getting udev properties for device: ram4
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.133646 #9095] DEBUG -- : Device ram4 udev properties: {"DEVNAME"=>"/dev/ram4", "DEVPATH"=>"/devices/virtual/block/ram4", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3820", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.133675 #9095] DEBUG -- : Trying to find out if device ram4 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.133710 #9095] DEBUG -- : Device ram4 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.133768 #9095] DEBUG -- : Getting udev properties for device: ram5
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.135333 #9095] DEBUG -- : Device ram5 udev properties: {"DEVNAME"=>"/dev/ram5", "DEVPATH"=>"/devices/virtual/block/ram5", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3888", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.135360 #9095] DEBUG -- : Trying to find out if device ram5 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.135425 #9095] DEBUG -- : Device ram5 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.135448 #9095] DEBUG -- : Getting udev properties for device: ram6
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.137003 #9095] DEBUG -- : Device ram6 udev properties: {"DEVNAME"=>"/dev/ram6", "DEVPATH"=>"/devices/virtual/block/ram6", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4350", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.137029 #9095] DEBUG -- : Trying to find out if device ram6 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.137076 #9095] DEBUG -- : Device ram6 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.137099 #9095] DEBUG -- : Getting udev properties for device: ram7
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.138892 #9095] DEBUG -- : Device ram7 udev properties: {"DEVNAME"=>"/dev/ram7", "DEVPATH"=>"/devices/virtual/block/ram7", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4449", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.138918 #9095] DEBUG -- : Trying to find out if device ram7 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.138965 #9095] DEBUG -- : Device ram7 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.138987 #9095] DEBUG -- : Getting udev properties for device: ram8
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.140430 #9095] DEBUG -- : Device ram8 udev properties: {"DEVNAME"=>"/dev/ram8", "DEVPATH"=>"/devices/virtual/block/ram8", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"8", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4512", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.140455 #9095] DEBUG -- : Trying to find out if device ram8 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.140501 #9095] DEBUG -- : Device ram8 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.140523 #9095] DEBUG -- : Getting udev properties for device: ram9
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.141994 #9095] DEBUG -- : Device ram9 udev properties: {"DEVNAME"=>"/dev/ram9", "DEVPATH"=>"/devices/virtual/block/ram9", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"9", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"4593", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.142027 #9095] DEBUG -- : Trying to find out if device ram9 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.147412 #9095] DEBUG -- : Device ram9 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.147438 #9095] DEBUG -- : Getting udev properties for device: loop0
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.149054 #9095] DEBUG -- : Device loop0 udev properties: {"DEVNAME"=>"/dev/loop0", "DEVPATH"=>"/devices/virtual/block/loop0", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"0", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1817", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.149081 #9095] DEBUG -- : Trying to find out if device loop0 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.149114 #9095] DEBUG -- : Device loop0 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.149160 #9095] DEBUG -- : Getting udev properties for device: loop1
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.150607 #9095] DEBUG -- : Device loop1 udev properties: {"DEVNAME"=>"/dev/loop1", "DEVPATH"=>"/devices/virtual/block/loop1", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"1", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1901", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.150633 #9095] DEBUG -- : Trying to find out if device loop1 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.150668 #9095] DEBUG -- : Device loop1 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.150688 #9095] DEBUG -- : Getting udev properties for device: loop2
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.152588 #9095] DEBUG -- : Device loop2 udev properties: {"DEVNAME"=>"/dev/loop2", "DEVPATH"=>"/devices/virtual/block/loop2", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"2", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"1992", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.152614 #9095] DEBUG -- : Trying to find out if device loop2 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.152652 #9095] DEBUG -- : Device loop2 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.152674 #9095] DEBUG -- : Getting udev properties for device: loop3
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.154212 #9095] DEBUG -- : Device loop3 udev properties: {"DEVNAME"=>"/dev/loop3", "DEVPATH"=>"/devices/virtual/block/loop3", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"3", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2079", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.154237 #9095] DEBUG -- : Trying to find out if device loop3 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.154272 #9095] DEBUG -- : Device loop3 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.154293 #9095] DEBUG -- : Getting udev properties for device: loop4
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.155738 #9095] DEBUG -- : Device loop4 udev properties: {"DEVNAME"=>"/dev/loop4", "DEVPATH"=>"/devices/virtual/block/loop4", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"4", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2190", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.155764 #9095] DEBUG -- : Trying to find out if device loop4 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.155803 #9095] DEBUG -- : Device loop4 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.155823 #9095] DEBUG -- : Getting udev properties for device: loop5
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.157536 #9095] DEBUG -- : Device loop5 udev properties: {"DEVNAME"=>"/dev/loop5", "DEVPATH"=>"/devices/virtual/block/loop5", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"5", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2259", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.157600 #9095] DEBUG -- : Trying to find out if device loop5 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.157647 #9095] DEBUG -- : Device loop5 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.157668 #9095] DEBUG -- : Getting udev properties for device: loop6
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.159092 #9095] DEBUG -- : Device loop6 udev properties: {"DEVNAME"=>"/dev/loop6", "DEVPATH"=>"/devices/virtual/block/loop6", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"6", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2395", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.159118 #9095] DEBUG -- : Trying to find out if device loop6 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.159187 #9095] DEBUG -- : Device loop6 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.159208 #9095] DEBUG -- : Getting udev properties for device: loop7
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.160945 #9095] DEBUG -- : Device loop7 udev properties: {"DEVNAME"=>"/dev/loop7", "DEVPATH"=>"/devices/virtual/block/loop7", "DEVTYPE"=>"disk", "MAJOR"=>"7", "MINOR"=>"7", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"2521", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.160971 #9095] DEBUG -- : Trying to find out if device loop7 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.161002 #9095] DEBUG -- : Device loop7 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.161024 #9095] DEBUG -- : Getting udev properties for device: ram10
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.162475 #9095] DEBUG -- : Device ram10 udev properties: {"DEVNAME"=>"/dev/ram10", "DEVPATH"=>"/devices/virtual/block/ram10", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"10", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3164", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.162501 #9095] DEBUG -- : Trying to find out if device ram10 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.162533 #9095] DEBUG -- : Device ram10 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.162557 #9095] DEBUG -- : Getting udev properties for device: ram11
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.164029 #9095] DEBUG -- : Device ram11 udev properties: {"DEVNAME"=>"/dev/ram11", "DEVPATH"=>"/devices/virtual/block/ram11", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"11", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3250", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.164055 #9095] DEBUG -- : Trying to find out if device ram11 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.164092 #9095] DEBUG -- : Device ram11 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.164114 #9095] DEBUG -- : Getting udev properties for device: ram12
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.165575 #9095] DEBUG -- : Device ram12 udev properties: {"DEVNAME"=>"/dev/ram12", "DEVPATH"=>"/devices/virtual/block/ram12", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"12", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3322", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.165600 #9095] DEBUG -- : Trying to find out if device ram12 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.165642 #9095] DEBUG -- : Device ram12 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.165663 #9095] DEBUG -- : Getting udev properties for device: ram13
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.167170 #9095] DEBUG -- : Device ram13 udev properties: {"DEVNAME"=>"/dev/ram13", "DEVPATH"=>"/devices/virtual/block/ram13", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"13", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3416", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.167196 #9095] DEBUG -- : Trying to find out if device ram13 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.167232 #9095] DEBUG -- : Device ram13 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.167253 #9095] DEBUG -- : Getting udev properties for device: ram14
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.168880 #9095] DEBUG -- : Device ram14 udev properties: {"DEVNAME"=>"/dev/ram14", "DEVPATH"=>"/devices/virtual/block/ram14", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"14", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3490", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.168905 #9095] DEBUG -- : Trying to find out if device ram14 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.168948 #9095] DEBUG -- : Device ram14 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.168969 #9095] DEBUG -- : Getting udev properties for device: ram15
Sep 13 18:10:43 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.170754 #9095] DEBUG -- : Device ram15 udev properties: {"DEVNAME"=>"/dev/ram15", "DEVPATH"=>"/devices/virtual/block/ram15", "DEVTYPE"=>"disk", "MAJOR"=>"1", "MINOR"=>"15", "SUBSYSTEM"=>"block", "USEC_INITIALIZED"=>"3589", "nomdmonddf"=>"1", "nomdmonisw"=>"1"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.170813 #9095] DEBUG -- : Trying to find out if device ram15 is removable or not
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.170857 #9095] DEBUG -- : Device ram15 removable parameter: "0"
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.170892 #9095] DEBUG -- : Final list of physical devices is: [{:name=>"sda", :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0"}]
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.170907 #9095] DEBUG -- : Block device seems to be physical data storage: sda
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.170954 #9095] DEBUG -- : Found block device: dm-0
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.170968 #9095] DEBUG -- : Block device info: {"size"=>"2228764672", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.170982 #9095] DEBUG -- : Found block device: dm-1
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.170993 #9095] DEBUG -- : Block device info: {"size"=>"23068672", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171002 #9095] DEBUG -- : Found block device: dm-2
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171047 #9095] DEBUG -- : Block device info: {"size"=>"41943040", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171057 #9095] DEBUG -- : Found block device: dm-3
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171066 #9095] DEBUG -- : Block device info: {"size"=>"20971520", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171074 #9095] DEBUG -- : Found block device: dm-4
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171084 #9095] DEBUG -- : Block device info: {"size"=>"104857600", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171092 #9095] DEBUG -- : Found block device: dm-5
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171102 #9095] DEBUG -- : Block device info: {"size"=>"33554432", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171110 #9095] DEBUG -- : Found block device: ram0
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171119 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171127 #9095] DEBUG -- : Found block device: ram1
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171170 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171180 #9095] DEBUG -- : Found block device: ram2
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171190 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171199 #9095] DEBUG -- : Found block device: ram3
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171208 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171216 #9095] DEBUG -- : Found block device: ram4
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171226 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171235 #9095] DEBUG -- : Found block device: ram5
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171244 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171252 #9095] DEBUG -- : Found block device: ram6
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171290 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171299 #9095] DEBUG -- : Found block device: ram7
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171309 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171317 #9095] DEBUG -- : Found block device: ram8
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171327 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171335 #9095] DEBUG -- : Found block device: ram9
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171344 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171352 #9095] DEBUG -- : Found block device: loop0
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171361 #9095] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171370 #9095] DEBUG -- : Found block device: loop1
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171403 #9095] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171412 #9095] DEBUG -- : Found block device: loop2
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171421 #9095] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171430 #9095] DEBUG -- : Found block device: loop3
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171439 #9095] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171449 #9095] DEBUG -- : Found block device: loop4
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171459 #9095] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171467 #9095] DEBUG -- : Found block device: loop5
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171476 #9095] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171484 #9095] DEBUG -- : Found block device: loop6
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171527 #9095] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171535 #9095] DEBUG -- : Found block device: loop7
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171546 #9095] DEBUG -- : Block device info: {"size"=>"0", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171554 #9095] DEBUG -- : Found block device: ram10
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171564 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171572 #9095] DEBUG -- : Found block device: ram11
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171581 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171590 #9095] DEBUG -- : Found block device: ram12
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171599 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171607 #9095] DEBUG -- : Found block device: ram13
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171616 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171662 #9095] DEBUG -- : Found block device: ram14
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171672 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171679 #9095] DEBUG -- : Found block device: ram15
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171690 #9095] DEBUG -- : Block device info: {"size"=>"131072", "removable"=>"0"}
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.171718 #9095] DEBUG -- : Detailed meta disks: [{:name=>"sda", :model=>"UCSB-MRAID12G", :size=>2397998940160, :disk=>"disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0", :extra=>["disk/by-id/wwn-0x618e72837273a7701cc7886005a67804", "disk/by-id/scsi-3618e72837273a7701cc7886005a67804"], :removable=>"0", :paths=>nil}]
Sep 13 18:10:43 node-4 nailgun-agent: D, [2016-09-13T18:10:43.353481 #9095] DEBUG -- : Response: status: 200 body: {"id": 4}
Sep 13 18:10:43 node-4 nailgun-agent: I, [2016-09-13T18:10:43.353664 #9095]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Sep 13 18:10:48 node-4 puppet-user[13911]: (/Stage[main]/Apt::Update/Exec[apt_update]) Triggered 'refresh' from 9 events
Sep 13 18:10:48 node-4 puppet-user[13911]: Finished catalog run in 16.74 seconds
Sep 13 18:10:50 node-4 puppet-user[15260]: (Scope(Class[Osnailyfacter::Fuel_pkgs::Fuel_pkgs])) MODULAR: fuel_pkgs/fuel_pkgs.pp
Sep 13 18:10:51 node-4 puppet-user[15260]: Compiled catalog for node-4.domain.tld in environment production in 0.13 seconds
Sep 13 18:10:55 node-4 puppet-user[15260]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-misc]/ensure) ensure changed 'purged' to 'present'
Sep 13 18:11:01 node-4 CRON[16480]: (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")
Sep 13 18:11:07 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 18:11:07 node-4 nailgun-agent: I, [2016-09-13T18:11:07.539653 #16483]  INFO -- : API URL is https://10.20.0.2:8443/api
Sep 13 18:11:20 node-4 nailgun-agent: at depth 0 - 18: self signed certificate
Sep 13 18:11:20 node-4 nailgun-agent: I, [2016-09-13T18:11:20.805507 #16483]  INFO -- : Wrote data to file '/etc/nailgun_uid'. Data: 4
Sep 13 18:11:25 node-4 puppet-user[15260]: (/Stage[main]/Osnailyfacter::Fuel_pkgs::Fuel_pkgs/Package[fuel-ha-utils]/ensure) ensure changed 'purged' to 'present'
Sep 13 18:11:25 node-4 puppet-user[15260]: Finished catalog run in 34.10 seconds
Sep 13 18:11:27 node-4 puppet-user[18065]: (Scope(Class[Osnailyfacter::Globals::Globals])) MODULAR: globals/globals.pp
Sep 13 18:11:27 node-4 puppet-user[18065]: Compiled catalog for node-4.domain.tld in environment production in 0.61 seconds
Sep 13 18:11:27 node-4 puppet-user[18065]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/hiera/globals.yaml]/ensure) created
Sep 13 18:11:27 node-4 puppet-user[18065]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter]/ensure) created
Sep 13 18:11:27 node-4 puppet-user[18065]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d]/ensure) created
Sep 13 18:11:27 node-4 puppet-user[18065]: (/Stage[main]/Osnailyfacter::Globals::Globals/File[/etc/facter/facts.d/os_package_type.txt]/ensure) created
Sep 13 18:11:28 node-4 puppet-user[18065]: Finished catalog run in 0.10 seconds
Sep 13 18:11:29 node-4 puppet-user[18531]: (Scope(Class[Osnailyfacter::Logging::Logging])) MODULAR: logging/logging.pp
Sep 13 18:11:30 node-4 puppet-user[18531]: Compiled catalog for node-4.domain.tld in environment production in 0.94 seconds
Sep 13 18:11:31 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/fuel.nodaily]/ensure) defined content as '{md5}3cea7c4993ed214ad011f778d59cd8d0'
Sep 13 18:11:31 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/upstart]/ensure) removed
Sep 13 18:11:31 node-4 crontab[18971]: (root) LIST (root)
Sep 13 18:11:31 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logrotate/Cron[fuel-logrotate]/ensure) created
Sep 13 18:11:31 node-4 crontab[18972]: (root) REPLACE (root)
Sep 13 18:11:33 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-relp]/ensure) ensure changed 'purged' to 'latest'
Sep 13 18:11:34 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Install/Package[rsyslog-gnutls]/ensure) ensure changed 'purged' to 'latest'
Sep 13 18:11:34 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/content) content changed '{md5}85a6fb16706f325b4cc9c84657526bd3' to '{md5}b1ed110d3c9d063897698be603ac4ef5'
Sep 13 18:11:34 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/content) content changed '{md5}c7af23c348917e877399baea1849727a' to '{md5}c61af26f2942c5706792c9cc23fd29b0'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Config/File[/etc/default/rsyslog]/group) group changed 'root' to 'syslog'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/]/group) group changed 'root' to 'syslog'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/21-cloudinit.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/20-ufw.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logrotate/File[/etc/logrotate.d/puppet]/ensure) defined content as '{md5}37fb575d510223595003675d7885ea5e'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-tabooext]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-compress]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-delaycompress]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-minsize]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logrotate/File_line[logrotate-maxsize]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Config/File[/etc/rsyslog.d/postfix.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Cluster::Haproxy::Rsyslog/File[/etc/rsyslog.d/haproxy.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Config/File[/var/spool/rsyslog]/group) group changed 'adm' to 'syslog'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[02-ha]/File[/etc/rsyslog.d/02-ha.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[54-heat]/File[/etc/rsyslog.d/54-heat.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[04-mysql]/File[/etc/rsyslog.d/04-mysql.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[62-mongod]/File[/etc/rsyslog.d/62-mongod.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/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
Sep 13 18:11:35 node-4 puppet-user[18531]: (/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
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[90-local]/File[/etc/rsyslog.d/90-local.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/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
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Rsyslog::Client/Rsyslog::Snippet[client]/File[/etc/rsyslog.d/client.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-disable-EscapeControlCharactersOnReceive]/File[/etc/rsyslog.d/00-disable-EscapeControlCharactersOnReceive.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[03-dashboard]/File[/etc/rsyslog.d/03-dashboard.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[30-cinder]/File[/etc/rsyslog.d/30-cinder.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/content) content changed '{md5}3c4b8bf33523fbb60a630ef8bba60514' to '{md5}df819c790cc71644feb6eb0e453b2fdc'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[00-remote]/File[/etc/rsyslog.d/00-remote.conf]/mode) mode changed '0644' to '0640'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[20-keystone]/File[/etc/rsyslog.d/20-keystone.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/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
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq]/Rsyslog::Snippet[04-rabbitmq]/File[/etc/rsyslog.d/04-rabbitmq.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/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
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[40-glance]/File[/etc/rsyslog.d/40-glance.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[80-swift]/File[/etc/rsyslog.d/80-swift.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[53-aodh]/File[/etc/rsyslog.d/53-aodh.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_error]/Rsyslog::Snippet[11-horizon_error]/File[/etc/rsyslog.d/11-horizon_error.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[55-murano]/File[/etc/rsyslog.d/55-murano.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/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
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[04-rabbitmq-sasl]/Rsyslog::Snippet[04-rabbitmq-sasl]/File[/etc/rsyslog.d/04-rabbitmq-sasl.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[11-horizon_access]/Rsyslog::Snippet[11-horizon_access]/File[/etc/rsyslog.d/11-horizon_access.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/content) content changed '{md5}80de10a8b9f13365de8cc4bbf8efec5e' to '{md5}4afe5e45558050f7185797c0c21e0f4e'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/group) group changed 'root' to 'syslog'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-default]/File[/etc/rsyslog.d/50-default.conf]/mode) mode changed '0644' to '0640'
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[10-nova]/File[/etc/rsyslog.d/10-nova.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[60-puppet-apply]/File[/etc/rsyslog.d/60-puppet-apply.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/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
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[51-ceilometer]/File[/etc/rsyslog.d/51-ceilometer.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/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
Sep 13 18:11:35 node-4 puppet-user[18531]: (/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
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[50-neutron]/File[/etc/rsyslog.d/50-neutron.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Snippet[61-mco-nailgun-agent]/File[/etc/rsyslog.d/61-mco-nailgun-agent.conf]/ensure) created
Sep 13 18:11:35 node-4 puppet-user[18531]: (/Stage[main]/Openstack::Logging/Rsyslog::Imfile[05-apache2-error]/Rsyslog::Snippet[05-apache2-error]/File[/etc/rsyslog.d/05-apache2-error.conf]/ensure) created
Sep 13 18:11:36 node-4 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="8384" x-info="http://www.rsyslog.com"] exiting on signal 15.
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2221: module 'imfile' already in this config, cannot be added
 [try http://www.rsyslog.com/e/2221 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try http://www.rsyslog.com/e/2307 ]
<43>Sep 13 18:11:36 node-4 rsyslogd: cannot create '/var/lib/haproxy/dev/log': No such file or directory
<27>Sep 13 18:11:38 node-4 multipathd: uevent trigger error
<27>Sep 13 18:11:38 node-4 multipathd: uevent trigger error
<27>Sep 13 18:11:38 node-4 multipathd: uevent trigger error
<27>Sep 13 18:11:38 node-4 multipathd: uevent trigger error
<27>Sep 13 18:11:38 node-4 multipathd: uevent trigger error
<27>Sep 13 18:11:38 node-4 multipathd: uevent trigger error
<27>Sep 13 18:11:58 node-4 multipathd: uevent trigger error
<27>Sep 13 18:11:58 node-4 multipathd: uevent trigger error
<27>Sep 13 18:11:58 node-4 multipathd: uevent trigger error
<27>Sep 13 18:11:58 node-4 multipathd: uevent trigger error
<27>Sep 13 18:11:58 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:00 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:00 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:00 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:00 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:00 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:00 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-4 multipathd: uevent trigger error
<27>Sep 13 18:12:02 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:02 node-4 ntpdate[30620]: no servers can be used, exiting
<27>Sep 13 18:13:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:36 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:36 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:36 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:36 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:36 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:48 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:48 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:48 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:48 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:48 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:58 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:58 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:58 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:58 node-4 multipathd: uevent trigger error
<27>Sep 13 18:13:58 node-4 multipathd: uevent trigger error
<43>Sep 13 18:14:15 node-4 apache2_error [Tue Sep 13 18:14:10.656213 2016] [mpm_event:notice] [pid 8441:tid 140578923526016] AH00489: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 13 18:14:15 node-4 apache2_error [Tue Sep 13 18:14:10.656295 2016] [core:notice] [pid 8441:tid 140578923526016] AH00094: Command line: '/usr/sbin/apache2'
<43>Sep 13 18:14:15 node-4 apache2_error [Tue Sep 13 18:14:13.668721 2016] [mpm_event:notice] [pid 8441:tid 140578923526016] AH00491: caught SIGTERM, shutting down
<43>Sep 13 18:14:15 node-4 apache2_error [Tue Sep 13 18:14:14.759852 2016] [mpm_worker:notice] [pid 8957:tid 140561123473280] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 13 18:14:15 node-4 apache2_error [Tue Sep 13 18:14:14.759909 2016] [core:notice] [pid 8957:tid 140561123473280] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:14:18 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:18 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:18 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:18 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:18 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:54 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:54 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:54 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:54 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:54 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:54 node-4 multipathd: uevent trigger error
<27>Sep 13 18:14:54 node-4 multipathd: uevent trigger error
<43>Sep 13 18:14:55 node-4 apache2_error [Tue Sep 13 18:14:51.656899 2016] [mpm_worker:notice] [pid 8957:tid 140561123473280] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 18:14:55 node-4 apache2_error [Tue Sep 13 18:14:51.660240 2016] [mpm_worker:warn] [pid 8957:tid 140561123473280] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 18:14:55 node-4 apache2_error [Tue Sep 13 18:14:51.660537 2016] [mpm_worker:notice] [pid 8957:tid 140561123473280] AH00292: Apache/2.4.7 (Ubuntu) configured -- resuming normal operations
<43>Sep 13 18:14:55 node-4 apache2_error [Tue Sep 13 18:14:51.660542 2016] [core:notice] [pid 8957:tid 140561123473280] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:15:14 node-4 multipathd: uevent trigger error
<27>Sep 13 18:15:48 node-4 ocf-ns_haproxy: ERROR: sysctl: cannot stat /proc/sys/net/ipv4/ip_nonlocal_bind: No such file or directory
<27>Sep 13 18:15:53 node-4 multipathd: uevent trigger error
<27>Sep 13 18:15:53 node-4 multipathd: uevent trigger error
<27>Sep 13 18:15:53 node-4 multipathd: uevent trigger error
<27>Sep 13 18:15:53 node-4 multipathd: uevent trigger error
<27>Sep 13 18:15:53 node-4 multipathd: uevent trigger error
<27>Sep 13 18:15:57 node-4 multipathd: uevent trigger error
<27>Sep 13 18:15:57 node-4 multipathd: uevent trigger error
<27>Sep 13 18:15:57 node-4 multipathd: uevent trigger error
<27>Sep 13 18:15:57 node-4 multipathd: uevent trigger error
<27>Sep 13 18:15:57 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:10 node-4 multipathd: uevent trigger error
<129>Sep 13 18:16:16 node-4 haproxy[26713]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:16 node-4 haproxy[26713]: proxy odl-jetty has no server available!
<27>Sep 13 18:16:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:16 node-4 multipathd: uevent trigger error
<129>Sep 13 18:16:18 node-4 haproxy[26713]: Server odl-neutron-endpoint/node-5 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:18 node-4 haproxy[26713]: proxy odl-neutron-endpoint has no server available!
<129>Sep 13 18:16:18 node-4 haproxy[28041]: 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>Sep 13 18:16:21 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:21 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:21 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:21 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:21 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:21 node-4 multipathd: uevent trigger error
<129>Sep 13 18:16:22 node-4 haproxy[28055]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:22 node-4 haproxy[28055]: proxy odl-jetty has no server available!
<27>Sep 13 18:16:25 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:25 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:25 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:25 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:25 node-4 multipathd: uevent trigger error
<129>Sep 13 18:16:26 node-4 haproxy[28055]: Server odl-neutron-endpoint/node-5 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:26 node-4 haproxy[28055]: proxy odl-neutron-endpoint has no server available!
<129>Sep 13 18:16:27 node-4 haproxy[30235]: 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>Sep 13 18:16:28 node-4 haproxy[30244]: 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>Sep 13 18:16:30 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:30 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:30 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:30 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:30 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:30 node-4 multipathd: uevent trigger error
<129>Sep 13 18:16:31 node-4 haproxy[30244]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:31 node-4 haproxy[30244]: proxy odl-jetty has no server available!
<129>Sep 13 18:16:32 node-4 haproxy[31391]: 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>Sep 13 18:16:33 node-4 haproxy[31400]: 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>Sep 13 18:16:33 node-4 haproxy[31400]: 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>Sep 13 18:16:35 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:35 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:35 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:35 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:35 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:35 node-4 multipathd: uevent trigger error
<129>Sep 13 18:16:36 node-4 haproxy[31400]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:36 node-4 haproxy[31400]: proxy odl-jetty has no server available!
<129>Sep 13 18:16:38 node-4 haproxy[32585]: 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>Sep 13 18:16:38 node-4 haproxy[32585]: 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>Sep 13 18:16:38 node-4 haproxy[32585]: 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>Sep 13 18:16:39 node-4 haproxy[32585]: 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>Sep 13 18:16:39 node-4 haproxy[32585]: 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>Sep 13 18:16:40 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:40 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:40 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:40 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:40 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:40 node-4 multipathd: uevent trigger error
<129>Sep 13 18:16:41 node-4 haproxy[32585]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:41 node-4 haproxy[32585]: proxy odl-jetty has no server available!
<129>Sep 13 18:16:43 node-4 haproxy[1329]: 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>Sep 13 18:16:43 node-4 haproxy[1329]: 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>Sep 13 18:16:43 node-4 haproxy[1329]: 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>Sep 13 18:16:44 node-4 haproxy[1338]: 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>Sep 13 18:16:44 node-4 haproxy[1338]: 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>Sep 13 18:16:44 node-4 haproxy[1338]: 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>Sep 13 18:16:46 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:46 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:46 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:46 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:46 node-4 multipathd: uevent trigger error
<129>Sep 13 18:16:46 node-4 haproxy[1338]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:46 node-4 haproxy[1338]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:46 node-4 haproxy[1338]: proxy aodh has no server available!
<129>Sep 13 18:16:47 node-4 haproxy[1338]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:47 node-4 haproxy[1338]: proxy odl-jetty has no server available!
<129>Sep 13 18:16:48 node-4 haproxy[2509]: 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>Sep 13 18:16:49 node-4 haproxy[2518]: 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>Sep 13 18:16:49 node-4 haproxy[2518]: 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>Sep 13 18:16:49 node-4 haproxy[2518]: 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>Sep 13 18:16:49 node-4 haproxy[2518]: 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>Sep 13 18:16:50 node-4 haproxy[2518]: 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>Sep 13 18:16:50 node-4 haproxy[2518]: 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>Sep 13 18:16:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:51 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:51 node-4 multipathd: uevent trigger error
<129>Sep 13 18:16:51 node-4 haproxy[2518]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:52 node-4 haproxy[2518]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:52 node-4 haproxy[2518]: proxy aodh has no server available!
<129>Sep 13 18:16:52 node-4 haproxy[2518]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:52 node-4 haproxy[2518]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:52 node-4 haproxy[2518]: proxy ceilometer has no server available!
<129>Sep 13 18:16:52 node-4 haproxy[2518]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:52 node-4 haproxy[2518]: proxy odl-jetty has no server available!
<129>Sep 13 18:16:54 node-4 haproxy[3653]: 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>Sep 13 18:16:54 node-4 haproxy[3653]: 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>Sep 13 18:16:54 node-4 haproxy[3653]: 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>Sep 13 18:16:54 node-4 haproxy[3653]: 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>Sep 13 18:16:55 node-4 haproxy[3662]: 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>Sep 13 18:16:55 node-4 haproxy[3662]: 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>Sep 13 18:16:55 node-4 haproxy[3662]: 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>Sep 13 18:16:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:57 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:57 node-4 multipathd: uevent trigger error
<27>Sep 13 18:16:57 node-4 multipathd: uevent trigger error
<129>Sep 13 18:16:57 node-4 haproxy[3662]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:57 node-4 haproxy[3662]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:57 node-4 haproxy[3662]: proxy aodh has no server available!
<129>Sep 13 18:16:57 node-4 haproxy[3662]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:16:57 node-4 haproxy[3662]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:57 node-4 haproxy[3662]: proxy ceilometer has no server available!
<129>Sep 13 18:16:57 node-4 haproxy[3662]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:16:57 node-4 haproxy[3662]: proxy odl-jetty has no server available!
<129>Sep 13 18:16:59 node-4 haproxy[4811]: 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>Sep 13 18:16:59 node-4 haproxy[4811]: 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>Sep 13 18:16:59 node-4 haproxy[4811]: 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>Sep 13 18:17:00 node-4 haproxy[4825]: 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>Sep 13 18:17:00 node-4 haproxy[4825]: 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>Sep 13 18:17:00 node-4 haproxy[4825]: 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>Sep 13 18:17:00 node-4 haproxy[4825]: 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>Sep 13 18:17:01 node-4 haproxy[4825]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:01 node-4 haproxy[4825]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 13 18:17:02 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:02 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:02 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:02 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:02 node-4 multipathd: uevent trigger error
<129>Sep 13 18:17:02 node-4 haproxy[4825]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:02 node-4 haproxy[4825]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:02 node-4 haproxy[4825]: proxy aodh has no server available!
<129>Sep 13 18:17:02 node-4 haproxy[4825]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:02 node-4 haproxy[4825]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:02 node-4 haproxy[4825]: proxy ceilometer has no server available!
<129>Sep 13 18:17:03 node-4 haproxy[4825]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:03 node-4 haproxy[4825]: proxy odl-jetty has no server available!
<129>Sep 13 18:17:05 node-4 haproxy[6029]: 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>Sep 13 18:17:05 node-4 haproxy[6029]: 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>Sep 13 18:17:05 node-4 haproxy[6029]: 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>Sep 13 18:17:05 node-4 haproxy[6029]: 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>Sep 13 18:17:06 node-4 haproxy[6038]: 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>Sep 13 18:17:06 node-4 haproxy[6038]: 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>Sep 13 18:17:06 node-4 haproxy[6038]: 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>Sep 13 18:17:06 node-4 haproxy[6038]: 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>Sep 13 18:17:06 node-4 haproxy[6038]: 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>Sep 13 18:17:06 node-4 haproxy[6038]: 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>Sep 13 18:17:07 node-4 haproxy[6038]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:07 node-4 haproxy[6038]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:08 node-4 haproxy[6038]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 13 18:17:08 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:08 node-4 multipathd: uevent trigger error
<129>Sep 13 18:17:08 node-4 haproxy[6038]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:08 node-4 haproxy[6038]: proxy glance-registry has no server available!
<27>Sep 13 18:17:08 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:08 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:08 node-4 multipathd: uevent trigger error
<129>Sep 13 18:17:08 node-4 haproxy[6038]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:08 node-4 haproxy[6038]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:08 node-4 haproxy[6038]: proxy aodh has no server available!
<129>Sep 13 18:17:08 node-4 haproxy[6038]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:09 node-4 haproxy[6038]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:09 node-4 haproxy[6038]: proxy ceilometer has no server available!
<129>Sep 13 18:17:09 node-4 haproxy[6038]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:09 node-4 haproxy[6038]: proxy odl-jetty has no server available!
<129>Sep 13 18:17:11 node-4 haproxy[7266]: 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>Sep 13 18:17:11 node-4 haproxy[7266]: 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>Sep 13 18:17:11 node-4 haproxy[7266]: 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>Sep 13 18:17:11 node-4 haproxy[7266]: 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>Sep 13 18:17:11 node-4 haproxy[7266]: 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>Sep 13 18:17:11 node-4 haproxy[7266]: 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>Sep 13 18:17:12 node-4 haproxy[7275]: 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>Sep 13 18:17:12 node-4 haproxy[7275]: 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>Sep 13 18:17:12 node-4 haproxy[7275]: 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>Sep 13 18:17:12 node-4 haproxy[7275]: 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>Sep 13 18:17:12 node-4 haproxy[7275]: 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>Sep 13 18:17:12 node-4 haproxy[7275]: 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>Sep 13 18:17:12 node-4 haproxy[7275]: 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>Sep 13 18:17:13 node-4 haproxy[7275]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:13 node-4 haproxy[7275]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 13 18:17:14 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:14 node-4 multipathd: uevent trigger error
<129>Sep 13 18:17:14 node-4 haproxy[7275]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2002ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 13 18:17:14 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:14 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:14 node-4 multipathd: uevent trigger error
<129>Sep 13 18:17:14 node-4 haproxy[7275]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:14 node-4 haproxy[7275]: proxy glance-registry has no server available!
<129>Sep 13 18:17:14 node-4 haproxy[7275]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:14 node-4 haproxy[7275]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:14 node-4 haproxy[7275]: proxy aodh has no server available!
<129>Sep 13 18:17:14 node-4 haproxy[7275]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:14 node-4 haproxy[7275]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:14 node-4 haproxy[7275]: proxy ceilometer has no server available!
<129>Sep 13 18:17:14 node-4 haproxy[7275]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:14 node-4 haproxy[7275]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:14 node-4 haproxy[7275]: proxy nova-novncproxy has no server available!
<129>Sep 13 18:17:15 node-4 haproxy[7275]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:15 node-4 haproxy[7275]: proxy odl-jetty has no server available!
<129>Sep 13 18:17:16 node-4 haproxy[8423]: 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.
<27>Sep 13 18:17:16 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<129>Sep 13 18:17:16 node-4 haproxy[8423]: 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>Sep 13 18:17:16 node-4 haproxy[8423]: 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>Sep 13 18:17:17 node-4 haproxy[8434]: 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>Sep 13 18:17:17 node-4 haproxy[8434]: 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>Sep 13 18:17:17 node-4 haproxy[8434]: 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>Sep 13 18:17:17 node-4 haproxy[8434]: 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>Sep 13 18:17:17 node-4 haproxy[8434]: 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>Sep 13 18:17:17 node-4 haproxy[8434]: 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>Sep 13 18:17:17 node-4 haproxy[8434]: 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>Sep 13 18:17:17 node-4 haproxy[8434]: 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>Sep 13 18:17:18 node-4 haproxy[8434]: 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>Sep 13 18:17:18 node-4 haproxy[8434]: 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>Sep 13 18:17:18 node-4 haproxy[8434]: 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>Sep 13 18:17:18 node-4 haproxy[8434]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:18 node-4 haproxy[8434]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 13 18:17:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:19 node-4 multipathd: uevent trigger error
<129>Sep 13 18:17:19 node-4 haproxy[8434]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:19 node-4 haproxy[8434]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:19 node-4 haproxy[8434]: proxy glance-registry has no server available!
<129>Sep 13 18:17:20 node-4 haproxy[8434]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:20 node-4 haproxy[8434]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:20 node-4 haproxy[8434]: proxy aodh has no server available!
<129>Sep 13 18:17:20 node-4 haproxy[8434]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:20 node-4 haproxy[8434]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:20 node-4 haproxy[8434]: proxy ceilometer has no server available!
<129>Sep 13 18:17:20 node-4 haproxy[8434]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:20 node-4 haproxy[8434]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:20 node-4 haproxy[8434]: proxy nova-novncproxy has no server available!
<129>Sep 13 18:17:20 node-4 haproxy[8434]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:20 node-4 haproxy[8434]: proxy odl-jetty has no server available!
<129>Sep 13 18:17:22 node-4 haproxy[9799]: 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>Sep 13 18:17:22 node-4 haproxy[9799]: 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>Sep 13 18:17:22 node-4 haproxy[9799]: 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>Sep 13 18:17:22 node-4 haproxy[9799]: 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>Sep 13 18:17:22 node-4 haproxy[9799]: 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>Sep 13 18:17:22 node-4 haproxy[9799]: 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>Sep 13 18:17:23 node-4 haproxy[9810]: 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>Sep 13 18:17:23 node-4 haproxy[9810]: 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>Sep 13 18:17:23 node-4 haproxy[9810]: 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>Sep 13 18:17:23 node-4 haproxy[9810]: 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>Sep 13 18:17:23 node-4 haproxy[9810]: 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>Sep 13 18:17:23 node-4 haproxy[9810]: 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>Sep 13 18:17:23 node-4 haproxy[9810]: 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>Sep 13 18:17:23 node-4 haproxy[9810]: 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>Sep 13 18:17:23 node-4 haproxy[9810]: 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>Sep 13 18:17:23 node-4 haproxy[9810]: 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>Sep 13 18:17:24 node-4 haproxy[9810]: 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>Sep 13 18:17:24 node-4 haproxy[9810]: Server horizon/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:24 node-4 haproxy[9810]: Server horizon/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 13 18:17:25 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:25 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:25 node-4 multipathd: uevent trigger error
<129>Sep 13 18:17:25 node-4 haproxy[9810]: Server glance-registry/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<27>Sep 13 18:17:25 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:25 node-4 multipathd: uevent trigger error
<129>Sep 13 18:17:25 node-4 haproxy[9810]: Server glance-registry/node-5 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:25 node-4 haproxy[9810]: proxy glance-registry has no server available!
<129>Sep 13 18:17:25 node-4 haproxy[9810]: Server aodh/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:25 node-4 haproxy[9810]: Server aodh/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:25 node-4 haproxy[9810]: proxy aodh has no server available!
<129>Sep 13 18:17:25 node-4 haproxy[9810]: Server ceilometer/node-1 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:25 node-4 haproxy[9810]: Server ceilometer/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:25 node-4 haproxy[9810]: proxy ceilometer has no server available!
<129>Sep 13 18:17:26 node-4 haproxy[9810]: Server nova-novncproxy/node-1 is DOWN, reason: Layer4 timeout, check duration: 2000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:26 node-4 haproxy[9810]: Server nova-novncproxy/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:26 node-4 haproxy[9810]: proxy nova-novncproxy has no server available!
<129>Sep 13 18:17:26 node-4 haproxy[9810]: Server odl-jetty/node-5 is DOWN, reason: Layer4 timeout, check duration: 2001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:26 node-4 haproxy[9810]: proxy odl-jetty has no server available!
<27>Sep 13 18:17:28 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:28 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:28 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:28 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:28 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:28 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:31 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:31 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:31 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:31 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:31 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:31 node-4 multipathd: uevent trigger error
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server odl-neutron-endpoint/node-5 is DOWN, reason: Layer4 timeout, check duration: 5001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:32 node-4 haproxy[9810]: proxy odl-neutron-endpoint has no server available!
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server keystone-1/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server keystone-1/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:32 node-4 haproxy[9810]: proxy keystone-1 has no server available!
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server keystone-2/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server keystone-2/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:32 node-4 haproxy[9810]: proxy keystone-2 has no server available!
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server nova-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server nova-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:32 node-4 haproxy[9810]: proxy nova-api has no server available!
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server nova-metadata-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server nova-metadata-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:32 node-4 haproxy[9810]: proxy nova-metadata-api has no server available!
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server cinder-api/node-1 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>Sep 13 18:17:32 node-4 haproxy[9810]: Backup Server cinder-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:32 node-4 haproxy[9810]: proxy cinder-api has no server available!
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server glance-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server glance-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:32 node-4 haproxy[9810]: proxy glance-api has no server available!
<129>Sep 13 18:17:32 node-4 haproxy[9810]: Server glance-glare/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server glance-glare/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:33 node-4 haproxy[9810]: proxy glance-glare has no server available!
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server neutron/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server neutron/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:33 node-4 haproxy[9810]: proxy neutron has no server available!
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server mysqld/node-1 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>Sep 13 18:17:33 node-4 haproxy[9810]: Backup Server mysqld/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:33 node-4 haproxy[9810]: proxy mysqld has no server available!
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server object-storage/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server object-storage/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:33 node-4 haproxy[9810]: proxy object-storage has no server available!
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server heat-api/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server heat-api/node-5 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:33 node-4 haproxy[9810]: proxy heat-api has no server available!
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server heat-api-cfn/node-1 is DOWN, reason: Layer4 timeout, check duration: 10000ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server heat-api-cfn/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:33 node-4 haproxy[9810]: proxy heat-api-cfn has no server available!
<129>Sep 13 18:17:33 node-4 haproxy[9810]: Server heat-api-cloudwatch/node-1 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 1 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<129>Sep 13 18:17:34 node-4 haproxy[9810]: Server heat-api-cloudwatch/node-5 is DOWN, reason: Layer4 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
<128>Sep 13 18:17:34 node-4 haproxy[9810]: proxy heat-api-cloudwatch has no server available!
<27>Sep 13 18:17:35 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:35 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:35 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:35 node-4 multipathd: uevent trigger error
<27>Sep 13 18:17:35 node-4 multipathd: uevent trigger error
<27>Sep 13 18:18:13 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 13 18:18:13 node-4 ocf-ns_conntrackd: ERROR: Device "conntrd" does not exist.
<27>Sep 13 18:18:17 node-4 ocf-ns_IPaddr2: ERROR: exec of "undef" failed: No such file or directory
<27>Sep 13 18:18:17 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 13 18:18:17 node-4 ocf-ns_IPaddr2: ERROR: Error: an inet prefix is expected rather than "undef".
<27>Sep 13 18:18:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:18:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:18:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:18:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:18:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:18:44 node-4 ocf-mysql-wss: ERROR: Setup problem: couldn't find command: /usr/bin/mysqld_safe
<27>Sep 13 18:19:47 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>Sep 13 18:19:49 node-4 ocf-mysql-wss: ERROR: p_mysqld: mysql_status(): MySQL is not running
<27>Sep 13 18:21:04 node-4 multipathd: uevent trigger error
<27>Sep 13 18:21:04 node-4 multipathd: uevent trigger error
<27>Sep 13 18:21:04 node-4 multipathd: uevent trigger error
<27>Sep 13 18:21:04 node-4 multipathd: uevent trigger error
<27>Sep 13 18:21:04 node-4 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-4 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-4 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-4 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-4 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-4 multipathd: uevent trigger error
<27>Sep 13 18:24:18 node-4 multipathd: uevent trigger error
<43>Sep 13 18:25:36 node-4 apache2_error [Tue Sep 13 18:25:27.340582 2016] [mpm_worker:notice] [pid 8957:tid 140561123473280] AH00295: caught SIGTERM, shutting down
<43>Sep 13 18:25:36 node-4 apache2_error [Tue Sep 13 18:25:28.097764 2016] [mpm_worker:notice] [pid 13817:tid 139948476192640] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 18:25:36 node-4 apache2_error [Tue Sep 13 18:25:28.097792 2016] [core:notice] [pid 13817:tid 139948476192640] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:26:05 node-4 multipathd: uevent trigger error
<27>Sep 13 18:26:05 node-4 multipathd: uevent trigger error
<27>Sep 13 18:26:05 node-4 multipathd: uevent trigger error
<27>Sep 13 18:26:05 node-4 multipathd: uevent trigger error
<27>Sep 13 18:26:05 node-4 multipathd: uevent trigger error
<43>Sep 13 18:26:06 node-4 apache2_error [Tue Sep 13 18:26:00.006973 2016] [mpm_worker:notice] [pid 13817:tid 139948476192640] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 18:26:06 node-4 apache2_error [Tue Sep 13 18:26:00.016711 2016] [mpm_worker:warn] [pid 13817:tid 139948476192640] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 18:26:06 node-4 apache2_error [Tue Sep 13 18:26:00.021841 2016] [mpm_worker:notice] [pid 13817:tid 139948476192640] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 18:26:06 node-4 apache2_error [Tue Sep 13 18:26:00.021870 2016] [core:notice] [pid 13817:tid 139948476192640] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:27:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:27:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:28:20 node-4 multipathd: uevent trigger error
<27>Sep 13 18:28:20 node-4 multipathd: uevent trigger error
<27>Sep 13 18:28:20 node-4 multipathd: uevent trigger error
<27>Sep 13 18:28:20 node-4 multipathd: uevent trigger error
<27>Sep 13 18:28:20 node-4 multipathd: uevent trigger error
<27>Sep 13 18:28:20 node-4 multipathd: uevent trigger error
<27>Sep 13 18:33:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:33:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:33:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:33:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:33:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:35:25 node-4 multipathd: uevent trigger error
<27>Sep 13 18:35:25 node-4 multipathd: uevent trigger error
<27>Sep 13 18:35:25 node-4 multipathd: uevent trigger error
<27>Sep 13 18:35:26 node-4 multipathd: uevent trigger error
<27>Sep 13 18:35:26 node-4 multipathd: uevent trigger error
<27>Sep 13 18:35:26 node-4 multipathd: uevent trigger error
<27>Sep 13 18:35:26 node-4 multipathd: uevent trigger error
<27>Sep 13 18:35:26 node-4 multipathd: uevent trigger error
<27>Sep 13 18:36:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:36:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:36:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:36:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:36:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:36:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:24 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:24 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:24 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:24 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:24 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:42 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:48 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:48 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:48 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:48 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:48 node-4 multipathd: uevent trigger error
<27>Sep 13 18:37:48 node-4 multipathd: uevent trigger error
<43>Sep 13 18:38:37 node-4 apache2_error [Tue Sep 13 18:38:35.325441 2016] [mpm_worker:notice] [pid 13817:tid 139948476192640] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 18:38:37 node-4 apache2_error [Tue Sep 13 18:38:35.711022 2016] [mpm_worker:warn] [pid 13817:tid 139948476192640] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 18:38:37 node-4 apache2_error [Tue Sep 13 18:38:35.716461 2016] [mpm_worker:notice] [pid 13817:tid 139948476192640] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 18:38:37 node-4 apache2_error [Tue Sep 13 18:38:35.716482 2016] [core:notice] [pid 13817:tid 139948476192640] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:39:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:16 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:16 node-4 multipathd: uevent trigger error
<43>Sep 13 18:39:17 node-4 apache2_error [Tue Sep 13 18:39:12.360542 2016] [mpm_worker:notice] [pid 13817:tid 139948476192640] AH00297: SIGUSR1 received.  Doing graceful restart
<43>Sep 13 18:39:17 node-4 apache2_error [Tue Sep 13 18:39:12.746721 2016] [mpm_worker:warn] [pid 13817:tid 139948476192640] AH00317: MaxRequestWorkers of 3191 is not an integer multiple of ThreadsPerChild of 25, decreasing to nearest multiple 3175
<43>Sep 13 18:39:17 node-4 apache2_error [Tue Sep 13 18:39:12.754844 2016] [mpm_worker:notice] [pid 13817:tid 139948476192640] AH00292: Apache/2.4.7 (Ubuntu) mod_wsgi/4.4.15 Python/2.7.6 configured -- resuming normal operations
<43>Sep 13 18:39:17 node-4 apache2_error [Tue Sep 13 18:39:12.754873 2016] [core:notice] [pid 13817:tid 139948476192640] AH00094: Command line: '/usr/sbin/apache2'
<27>Sep 13 18:39:32 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:44 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:44 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:44 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:44 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:44 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:44 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:44 node-4 multipathd: uevent trigger error
<27>Sep 13 18:39:45 node-4 multipathd: sda: spurious uevent, path already in pathvec
<27>Sep 13 18:40:32 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:32 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:32 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:32 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:33 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:37 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:37 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:37 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:37 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:37 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:49 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:49 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:49 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:49 node-4 multipathd: uevent trigger error
<27>Sep 13 18:40:49 node-4 multipathd: uevent trigger error
<27>Sep 13 18:41:30 node-4 multipathd: uevent trigger error
<27>Sep 13 18:41:30 node-4 multipathd: uevent trigger error
<27>Sep 13 18:41:30 node-4 multipathd: uevent trigger error
<27>Sep 13 18:41:30 node-4 multipathd: uevent trigger error
<27>Sep 13 18:41:30 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:19 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:31 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:31 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:31 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:32 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:32 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:32 node-4 multipathd: uevent trigger error
<11>Sep 13 18:42:41 node-4 liberasurecode[53567]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:41 node-4 liberasurecode[53567]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:41 node-4 liberasurecode[53567]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:41 node-4 liberasurecode[53567]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:41 node-4 liberasurecode[53596]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:41 node-4 liberasurecode[53596]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:41 node-4 liberasurecode[53596]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:41 node-4 liberasurecode[53596]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:43 node-4 liberasurecode[54045]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:43 node-4 liberasurecode[54045]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:43 node-4 liberasurecode[54045]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:43 node-4 liberasurecode[54045]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54673]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54673]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54673]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54673]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54714]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54714]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54714]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54714]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54753]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54753]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54753]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54753]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54815]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54815]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54815]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:49 node-4 liberasurecode[54815]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54834]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54834]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54834]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54834]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54846]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54846]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54846]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54846]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54889]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54889]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54889]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:42:50 node-4 liberasurecode[54889]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 13 18:42:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:42:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:43:01 node-4 multipathd: uevent trigger error
<27>Sep 13 18:43:01 node-4 multipathd: uevent trigger error
<27>Sep 13 18:43:01 node-4 multipathd: uevent trigger error
<27>Sep 13 18:43:01 node-4 multipathd: uevent trigger error
<27>Sep 13 18:43:01 node-4 multipathd: uevent trigger error
<27>Sep 13 18:44:04 node-4 multipathd: uevent trigger error
<27>Sep 13 18:44:04 node-4 multipathd: uevent trigger error
<27>Sep 13 18:44:04 node-4 multipathd: uevent trigger error
<27>Sep 13 18:44:04 node-4 multipathd: uevent trigger error
<27>Sep 13 18:44:04 node-4 multipathd: uevent trigger error
<11>Sep 13 18:45:01 node-4 liberasurecode[74808]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:45:01 node-4 liberasurecode[74808]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:45:01 node-4 liberasurecode[74808]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:45:01 node-4 liberasurecode[74808]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
<27>Sep 13 18:46:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:03 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:08 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:08 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:08 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:08 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:08 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:22 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:22 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:22 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:22 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:22 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:36 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:36 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:37 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:37 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:37 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:37 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:49 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:49 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:49 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:49 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:49 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:46:56 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:01 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:01 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:01 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:01 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:01 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:05 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:05 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:05 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:05 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:05 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:09 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:10 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:14 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:14 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:14 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:14 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:14 node-4 multipathd: uevent trigger error
<27>Sep 13 18:47:14 node-4 multipathd: uevent trigger error
<11>Sep 13 18:50:01 node-4 liberasurecode[126382]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:50:01 node-4 liberasurecode[126382]: liberasurecode_backend_open: dynamic linking error libJerasure.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:50:01 node-4 liberasurecode[126382]: liberasurecode_backend_open: dynamic linking error libisal.so.2: cannot open shared object file: No such file or directory
<11>Sep 13 18:50:01 node-4 liberasurecode[126382]: liberasurecode_backend_open: dynamic linking error libshss.so.1: cannot open shared object file: No such file or directory
